Related
(i made sure to do a backup)
Let me sum up what I have done:
I've managed to follow a guide on a wiki(I lost the link however, since I ATTEMPTED to give up on this) that involved me downgrading my firmware, then do some steps to install cyanogen 1.4. Afterwards, I got to step that required me to rename some file to update.zip. I followed that step and noticed my computer didn't convert the file to a zip file(it remained as a img file) but continued anyway while finding that odd.
Afterwards, cyanogen tells me that it cannot find the zip file. I've search most of google and a bit of this site, and i've seen various solutions that failed me such as:
-renaming the update.zip to update
-using android sdk(which i have no clue on how to use)
Anyways, finding out that I was foolish to do all of this without prior knowledge, I decided to go back to my original firmware. However, on the phone's reboot, cyanogen came up again for some reason, and didn't let the update be applied.(I don't recall the error)
Anyways, I selected reboot and got to my phone's main menu then some music started playing automatically. I should note, before I did the update, I placed all of my backed up data(while still having the original copy on my pc) on my phone so it might've been some music that the original owner had. Now, on the menu, i'm getting this error "The process android.process.acore has stopped unexpectedly. Please try again." all the time. Since this error constantly pops up, I can't do anything.
So if you managed to read my long and boring story, let me ask one question:
How do I get my phone back to normal if rooting is impossible at this point?
First question is what firmware is your htc magic currently on? And by reading everything I guess your phone isnt rooted...
Dataslycer said:
First question is what firmware is your htc magic currently on? And by reading everything I guess your phone isnt rooted...
Click to expand...
Click to collapse
It's on 1.5 currently. Also as a little update:
I fixed the "not being able to do anything on the menu" problem by doing a factory reset. Afterwards, I learned the SDK a little bit more and have the tools, pc driver, and fastboot on my pc. However, i'm getting the error:
FAILED (remote: not allow)
Just a bump. I need all the help I can get on this one. Even a premade update.zip would help me GREATLY.
One last bump. I promise.
Hello, please help me.
I rooted my phone few months back and it was working fine.
I had the brilliant idea of trying to back everything up so i can install the stock rom to get the new 4.1.2 update on my note 2 from verizon.
I downloaded this recommended back up app that only works on rooted phones.
After i downloaded and installed, it went blank and it said i had an invalid system something and i needed to take to the verizon store.
I did that, they told me they cant help obviously because its a rooted phone
i tried following steps in installing the stock rom such as:
Getting odin:
Installing the driver:
But when i download the file from various sources and extract, it does not become a valid file name to load into odin.
I tried many roms and none of them work.
I tried extracting with 7zip win zip winrar, and nothing works.
I keep getting the file .xz
someone please help me get my phone back to work.
I cant do anything...now i get a new message saying the firware is invalid or something.
Im so desperate im not sure what else to do.
Thank you for reading this.
the .xz is fine. click on pda, then click on file extension and types, select all, the file should show up. select it, hit start and odin will verify the md5.
New member but long time lurker.
Hoping somebody can help with a UK Nabi issue
I have previously used nabi lab to flash, root and install gapps. This worked great until I got a mail about the UK OTA. I then started to search for my stock back up and remember losing it in a hard drive disaster.
This led to updating using what I could find and nabi lab. End result at one point being Nabi reporting US Nabi version
Long story short. Managed to find another thread with a UK stock backup v2. Got this loaded and can update to v2.1 with no issue. Then I tried to go to v2.2 and I constantly get the dead android. And back to 2.1
The nabi has been wiped several times and at one point had no OS at all. I used the stock recovery in nabi lab and now wondering if the recovery files have an influence on the OTA? I have read that the earlier forcing gapps may have wiped some files needed for the OTA although I would assume that the very action of wiping everything via TWRP would have got around this I.e restoring via stock would have put them back on?
The nabi is currently running fine on v2.1 but can't get to 2.2 despite trying to find every solution found via search. Would have posted in the nabi section but don't have enough posts yet
Thanks in advance
Ste
Ste_J said:
New member but long time lurker.
Hoping somebody can help with a UK Nabi issue
I have previously used nabi lab to flash, root and install gapps. This worked great until I got a mail about the UK OTA. I then started to search for my stock back up and remember losing it in a hard drive disaster.
This led to updating using what I could find and nabi lab. End result at one point being Nabi reporting US Nabi version
Long story short. Managed to find another thread with a UK stock backup v2. Got this loaded and can update to v2.1 with no issue. Then I tried to go to v2.2 and I constantly get the dead android. And back to 2.1
The nabi has been wiped several times and at one point had no OS at all. I used the stock recovery in nabi lab and now wondering if the recovery files have an influence on the OTA? I have read that the earlier forcing gapps may have wiped some files needed for the OTA although I would assume that the very action of wiping everything via TWRP would have got around this I.e restoring via stock would have put them back on?
The nabi is currently running fine on v2.1 but can't get to 2.2 despite trying to find every solution found via search. Would have posted in the nabi section but don't have enough posts yet
Thanks in advance
Ste
Click to expand...
Click to collapse
I posted a question 2 days ago- can't even do first update so I'm following this with interest in the hope of getting info on how to unroot and just do ota updates with no dead android.
Floralina123 said:
I posted a question 2 days ago- can't even do first update so I'm following this with interest in the hope of getting info on how to unroot and just do ota updates with no dead android.
Click to expand...
Click to collapse
Hi,
what nabi version do you have? I have been able to unroot and get back to stock by using a UK v2 back up and a combination of nabi lab and twrp.
If you was looking for UK then I could probably point you in the right direction to get to the same point as me
Ste_J said:
Hi,
what nabi version do you have? I have been able to unroot and get back to stock by using a UK v2 back up and a combination of nabi lab and twrp.
If you was looking for UK then I could probably point you in the right direction to get to the same point as me
Click to expand...
Click to collapse
Hi Ste_j, thanks for the reply. I unrooted it already, or so I thought using nabilabs but it looks like twrp was removed and gapps remains - which I'm happy about seeing as I can't update it using ota update with google playstore- that could have been a disaster.
Here is my question I posted -
I Apologise for my ignorance in android in general.
I have rooted a Nabi 2 successfully installing Gapps etc using Nabilab, which was a pleasure to use. Now that the new OTA update is available which includes the Googleplaystore I would like to unroot and get the OTA updates. I thought I had unrooted it - using Nabilabs (twrp would not work, can't remember why but I think the touchscreen part wouldn't work for me). I returned to stock using (option 1. -1.9.37. Android can boot.) recovery using Nabilabs. I think I did a factory reset after that -sorry but it was weeks ago. Anyway, I suspected something wasn't right when I still had Gapps. I don't have TWRP on it now.
When I do the OTA update I get the dead android on reboot. Nabi is working fine apart from that. I read a lot of pages on this website but it ended up confusing me more than helping me unfortunately as I'm not android savvy.
I just need someone to tell me exactly what to do to properly unroot the Nabi so that it is truly back to original so I can use the OTA updates. I have no need to root the nabi again as the google play store is now officially available. And I've got a UK Nabi 2.
Ste_j,
I assumed I had a Uk nabi because I'm in Ireland. I don't know how to check this as it doesn't say uk here but the
model no is NABI2-NV7A-IE
Android version 4.0.4
Kernel version 3.1.10-00298-ge08b99f
[email protected] #2
SMP PREEMPT Tue Feb 26 17:21:35 HKT 2013
Build no IMM76L
Product version: 2.0-release-keys
I don't want to unroot any further unless I can get the latest ota update that gives me the google play store. I would rather leave it as it is now(gapps still on it) until you get yours working successfully I will gladly follow your lead from start to finish then. I just hope someone in the know replies with the solution. I too had been reading the nabi forum but cannot post there.
Tnx
Sounds like one of my recent 1am going on for 2 adventures in nabi land!
Hopefully there will be a UK stock 2.2 being uploaded tonight and if I get it working then I will let you know.
Ste_J said:
Sounds like one of my recent 1am going on for 2 adventures in nabi land!
Hopefully there will be a UK stock 2.2 being uploaded tonight and if I get it working then I will let you know.
Click to expand...
Click to collapse
Did you ever sort this one out mate? If I can atleast get my hands on the 2.2 OTA update zip file then atleast I can force it to upgrade from recovery mode.
metalheadkicks said:
Did you ever sort this one out mate? If I can atleast get my hands on the 2.2 OTA update zip file then atleast I can force it to upgrade from recovery mode.
Click to expand...
Click to collapse
Not yet. Waiting on 2.2 to be uploaded on the other thread. Hopefully the guy will get chance to upload over the weekend
So all 3 of you have UK Nabi's that can't get to 2.2 and are stuck somewhere at 2.0 or 2.1? Is that correct?
In theory restoring either of these(2.0 stock or 2.1 stock) http://forum.xda-developers.com/showpost.php?p=50158865&postcount=67
should then allow you to take the OTA. The US version did it as a 2 part update and the first wiped the system partition and installed a base ROM which got everyone on the same page and the did the second update to 2.3(2.2 for you guys if I understand correctly). Maybe the UK version doesn't do it like that.
Where is everyone failing at? TWRP usually fails for a "assert error in some file" If the backups are truly stock then this should work fine. Sometimes people who make backups mess up and TWRP set the file recovery-from-boot.p to recovery-from-boot.bak then the update can find that file and errors. Any other files will cause the same issue. Some other issues are the addon partition, the OTA's do edit stuff on the addon partition, if you have skipped around OTA's this can cause a mismatch too.
A stock 2.2 ROM would be great but anyone on 2.1 would still be stuck with ICS bootloader which won't boot 2.2UK. You would also want an addon partion backup to restore too.
Oops I get it.. You guys don't know where you are failing at because the stock recovery(dead android) doesn't give you any info. TWRP 2.6.3 can install OTA updates. Put TWRP backon. Use it to install the OTA it will have a log that will say why it's failing.
aicjofs said:
So all 3 of you have UK Nabi's that can't get to 2.2 and are stuck somewhere at 2.0 or 2.1? Is that correct?
In theory restoring either of these(2.0 stock or 2.1 stock) http://forum.xda-developers.com/showpost.php?p=50158865&postcount=67
should then allow you to take the OTA. The US version did it as a 2 part update and the first wiped the system partition and installed a base ROM which got everyone on the same page and the did the second update to 2.3(2.2 for you guys if I understand correctly). Maybe the UK version doesn't do it like that.
Where is everyone failing at? TWRP usually fails for a "assert error in some file" If the backups are truly stock then this should work fine. Sometimes people who make backups mess up and TWRP set the file recovery-from-boot.p to recovery-from-boot.bak then the update can find that file and errors. Any other files will cause the same issue. Some other issues are the addon partition, the OTA's do edit stuff on the addon partition, if you have skipped around OTA's this can cause a mismatch too.
A stock 2.2 ROM would be great but anyone on 2.1 would still be stuck with ICS bootloader which won't boot 2.2UK. You would also want an addon partion backup to restore too.
Oops I get it.. You guys don't know where you are failing at because the stock recovery(dead android) doesn't give you any info. TWRP 2.6.3 can install OTA updates. Put TWRP backon. Use it to install the OTA it will have a log that will say why it's failing.
Click to expand...
Click to collapse
Thank you. I have restored 2.0 from that post
Am I correct in thinking that the OTA will be stored in internal memory and that TWRP should be able to locate the file? Is there anyway of repairing the addon partition if that is corrupt?
Ste_J said:
Thank you. I have restored 2.0 from that post
Am I correct in thinking that the OTA will be stored in internal memory and that TWRP should be able to locate the file? Is there anyway of repairing the addon partition if that is corrupt?
Click to expand...
Click to collapse
Yes the ota is stored in internal memory. On data/media(internal). Its in a folder called ota or something intuitive like that. A forum search will find it, I'm drawing a blank. Do the ota download but when it says to update, back out of settings at that point and you will have the OTA zip.
Its kind of hard to repair addon. If there was a backup of addon from an early software version you could let the otas update it properly. I didn't really think to add that ability to twrp until late in the game though. The other option is to have someone that has successfully progressed through the otas make a backup and share. Then we could cook something up where you just use a 2.2 ROM and restore, update the bootloader and restore a 2.2 add-on. The last option is a custom OTA, similar to what I did with the US Nabi, and even that hasn't went perfectly. I'm not sure if its my update or people doing it a little different then the instructions but there have been a few failures with it. Although we figure it out eventually, just like we will with the UK Nabi.
aicjofs said:
Yes the ota is stored in internal memory. On data/media(internal). Its in a folder called ota or something intuitive like that. A forum search will find it, I'm drawing a blank. Do the ota download but when it says to update, back out of settings at that point and you will have the OTA zip.
Its kind of hard to repair addon. If there was a backup of addon from an early software version you could let the otas update it properly. I didn't really think to add that ability to twrp until late in the game though. The other option is to have someone that has successfully progressed through the otas make a backup and share. Then we could cook something up where you just use a 2.2 ROM and restore, update the bootloader and restore a 2.2 add-on. The last option is a custom OTA, similar to what I did with the US Nabi, and even that hasn't went perfectly. I'm not sure if its my update or people doing it a little different then the instructions but there have been a few failures with it. Although we figure it out eventually, just like we will with the UK Nabi.
Click to expand...
Click to collapse
TWRP installed and OTA attempted. log file attached . still not sure what is going wrong but hopefully somebody who is used to reading the logs will point me in the right direction
Ste_J said:
TWRP installed and OTA attempted. log file attached . still not sure what is going wrong but hopefully somebody who is used to reading the logs will point me in the right direction
Click to expand...
Click to collapse
Looks like it fails for fuhu_nabiMD_uk.apk. Never seen it fail a vendor app before. This was going from 2.0 to 2.1?
I see the 2.2 with addons got uploaded in the other thread. That's going to be the easiest route, except like I said previously I have this thinking that if you restore that(boot,addon,system) it's going to be stuck at Nabi symbol when you reboot because the bootloader wasnt updated to Jellybean. We will have to see I guess.
aicjofs said:
Looks like it fails for fuhu_nabiMD_uk.apk. Never seen it fail a vendor app before. This was going from 2.0 to 2.1?
I see the 2.2 with addons got uploaded in the other thread. That's going to be the easiest route, except like I said previously I have this thinking that if you restore that(boot,addon,system) it's going to be stuck at Nabi symbol when you reboot because the bootloader wasnt updated to Jellybean. We will have to see I guess.
Click to expand...
Click to collapse
That was going from 2.1 to 2.2
And yes i appear to be cross threading at the moment. Grabbed the 2.2 update and just spent the last hour trying to get past the stuck nabi screen. Got back to 2.1 eventually. Fastboot and Nabilab with just enough time to fire over previous TWRP and get back to the restore
Any ideas on how to update the boot loader?
Moving back to the other thread http://forum.xda-developers.com/showthread.php?t=2041224&page=9
aicjofs said:
Looks like it fails for fuhu_nabiMD_uk.apk. Never seen it fail a vendor app before. This was going from 2.0 to 2.1?
I see the 2.2 with addons got uploaded in the other thread. That's going to be the easiest route, except like I said previously I have this thinking that if you restore that(boot,addon,system) it's going to be stuck at Nabi symbol when you reboot because the bootloader wasnt updated to Jellybean. We will have to see I guess.
Click to expand...
Click to collapse
I get this issue also. I had rooted and added Google services - happy enough but no ability to move Apps to SD and I wanted to see if the Kernel update added this option. Anyway, I restored my backup - but the updates didn't apply cleanly. I swapped the boot loader back and things still weren't right and I didn't know then how to troubleshoot it. I was tired/had a wailing 3 year old wanting his tablet and I elected to wipe and reinstall from scratch using NabiLabFull. Initialised well enough through initial setup - completed setup and changed the recovery back to stock and it boot looped... Ugh. Reapplied stock image through twrp and changed to recovery back immediately - setup the Nabi from scratch and update 2.1 applied successfully. Update 2.2 fails however using stock everything with the error message:
Finding update package. . .
Opening update package. . .
Verifying update package. . .
Installing update. . .
Verifying current system. . ,
assert failed: apply_patch_check("/system/vendor/app/fuhu_nabiMD_uk.apk", "c4cd5edbc3f980c806a4fb8dd1d182f5c81b35f3", " eea145bf7f4a7b314ef15a3f3b0b9e8a9bc6efe7")
E:Error in /cache/nabi2-update.zip
(Status 7)
Installation aborted
So. The presence of two, what appear to be, md5 hash values makes me think the app in the system partition is not what it should be. Absent a file manager and root access I haven't delved deeper but I can only think the stock image I loaded isn't close enough to the UK stock image such that the UK specific apps correctly update in the 2.1 update (NabiMD is no longer installed after applying the 2.1 patch - dead link launcher icon on Parent home screen). My problem is I forgot to copy the pre-rooted backup before wiping - so I might have lost it. Anyway. Need to go shopping now and I'll dig more later. Long story short - I'm not sure a stock root path via NabiLab is viable for UK Nabi 2s.
Uk nabi update - leaving nabi as is until it's solved
I'm sorry this is not helpful but I just wanted to say that until the uk nabi is restored successfully and can update normally using ota, I'm leaving mine as it is. Basically, it works fine and my 4 yr old gets endless fun out of it. In saying that, I will restore it to normal someday when it can be done. I await one of you smart nabi gurus to come up with the answer.
MattP79 said:
I get this issue also. I had rooted and added Google services - happy enough but no ability to move Apps to SD and I wanted to see if the Kernel update added this option. Anyway, I restored my backup - but the updates didn't apply cleanly. I swapped the boot loader back and things still weren't right and I didn't know then how to troubleshoot it. I was tired/had a wailing 3 year old wanting his tablet and I elected to wipe and reinstall from scratch using NabiLabFull. Initialised well enough through initial setup - completed setup and changed the recovery back to stock and it boot looped... Ugh. Reapplied stock image through twrp and changed to recovery back immediately - setup the Nabi from scratch and update 2.1 applied successfully. Update 2.2 fails however using stock everything with the error message:
Finding update package. . .
Opening update package. . .
Verifying update package. . .
Installing update. . .
Verifying current system. . ,
assert failed: apply_patch_check("/system/vendor/app/fuhu_nabiMD_uk.apk", "c4cd5edbc3f980c806a4fb8dd1d182f5c81b35f3", " eea145bf7f4a7b314ef15a3f3b0b9e8a9bc6efe7")
E:Error in /cache/nabi2-update.zip
(Status 7)
Installation aborted
So. The presence of two, what appear to be, md5 hash values makes me think the app in the system partition is not what it should be. Absent a file manager and root access I haven't delved deeper but I can only think the stock image I loaded isn't close enough to the UK stock image such that the UK specific apps correctly update in the 2.1 update (NabiMD is no longer installed after applying the 2.1 patch - dead link launcher icon on Parent home screen). My problem is I forgot to copy the pre-rooted backup before wiping - so I might have lost it. Anyway. Need to go shopping now and I'll dig more later. Long story short - I'm not sure a stock root path via NabiLab is viable for UK Nabi 2s.
Click to expand...
Click to collapse
Floralina123 said:
I'm sorry this is not helpful but I just wanted to say that until the uk nabi is restored successfully and can update normally using ota, I'm leaving mine as it is. Basically, it works fine and my 4 yr old gets endless fun out of it. In saying that, I will restore it to normal someday when it can be done. I await one of you smart nabi gurus to come up with the answer.
Click to expand...
Click to collapse
Have you tried this? http://forum.xda-developers.com/showpost.php?p=50431606&postcount=98
It has to be done manually but should get a UK Nabi to complete stock version 2.2.
In case you need to know for some reason in the future that is a SHA1 hash not md5.
[SOLVED]
My device: OnePlus5 A5000
First of all I want to mention that I am kind of a novice on rooting so please do not go hard on me, mistakes happen. So I was running the lastest version of Android on my phone (Version 5.1.7) and decided to root my phone and use Magisk. So I unlocked my bootloader and I was going to work with TWRP. But I did a terrible mistake and wiped the system while experimenting. I know this is a very stupid mistake but it sadly happened. So my phone is basicly empty and has no OS running everytime with a black screen whenever I enter the system . The only thing I am able of doing is transfering files from my PC to my phone and using TWRP. I downloaded the original and latest OS version from OnePlus' site and moved it inside my phone. I then went on to install it via TWRP but I faced "Error 7". I did a research on that and I found out that it happens because it detects if it is a compatible ROM with the whole "assert" thing in META-INF in the "updater-script". I went on to unzip it and edit it with NotePad++to remove "assert" but "assert" was no where to be found since it was the original version. I then went on to try installing the lineage version for OnePLus 5 not knowing if it was going to work and it turned out to not work at all. I also want to mention that whenever I tried removing the "assert" from the lineage version I got an error of "Invalid zip file format!". Finally I want to mention that in order for me to view the files I worked by repairing the partition and converting it to FAT and exFAT(I did NOT convert it back to EXT4 yet). In case I am missing something or there is a way of solving it please let me know, I would really appreciate it! Also if you do not mind be as decscriptive as possible since I am a novice and I do not know everything like other individuals. I will though make a deep research on every single comment I get, I am not waiting for an easy solution on such a subject. I hope I can fix my phone with your help in the near future. Thanks in advance!
Files that I have downloaded (if necessary):
1)ADB Files
2)Original version of latest OnePlus 5 Update (5.1.7) (.zip file)
3)Lineage ROM for One Plus 5 (15.1-20181127-nightly-cheeseburger-signed)
4)TWRP (3.2.3-0-cheeseburger)
Hi Interweb!
I was wondering just how many people were still "in the know" on the topic of rooting, unlocking bootloader and general Android development for the Tesco hudl2 [HTFA4B] tablet. Obviously with Tesco's little trick of shutting down the servers, two thirds of us were left with Kitkat, and having had enough of it, I decided to root. Everything went fine. I booted back into Android KitKat (stock) and then installed Xposed Framework. Presumably the installation failed, as upon rebooting, the tablet booted straight into stock recovery. I have been seeing this for two months now, having removed the battery several times, refitting it and trying to reinstall android with the ROM form this link:
hudl2_ota_rel.android-build.20150803.092218_to_rel.android-build.20150917.142239.zip | GEM-FLASH Firmware
firmware.gem-flash.com
Either way, I am now faced with a soft brick. Does anyone know how to fix? The exact text displayed in Stock Recovery is down below.
To be clear, I occasionally DO see the "powered by android" screen before booting into recovery, but not every time.
A possible solution would be if there is a fastboot mode I can access, I may can use Odin and flash a Custom ROM onto the tab. Or, alternatively, if anyone has, or knows someone who may have Tesco's key signature, that too would be useful in building a ROM.
I've had this tablet since I was 7 years old, and it's been part of my life for many years now. If anyone can help please do
Many Thanks.
[TAGGING SOME PEOPLE WHO MAY BE ABLE TO HELP]
@Rickav
@droident
People not on XDA who may can help:
Kirwan Lyster - Head of Facebook's Android department and former head of Tesco Connected Devices (hudl) software team. [email protected]
The Guardian Consumer Champions
BBC Watchdog
Martin Lewis - Money Saving Expert.
Android system recovery <3e>
K0T49H.rel.android-build.20151102.170607 release-keys
Volume up/down to move highlight:
power button to select.
reboot system now
wipe data/factory reset
wipe cache partition
apply update from ADB
apply update from external storage
apply update from cache
[ANDROID WITH OPEN BELLY]
No Command.
Click to expand...
Click to collapse
Hey, just got pinged by XDA after a long time. It's all so sleek-looking now.
I'll cut to the chase—Unfortunately, I've got nothing to help with here. I'm a fan of the Hudl2 as well and still have it around as a backup ebook reader as the screen works reliably. It's running walking stock Lollipop and it occasionally throws up Play Services errors (which appears to be resolvable).
Following the dead download link on the MoDaCo forum post, I searched for stock ROMs and landed on the same Gem Flash site that you linked. Specifically, I found 3 results linked to the Hudl2. For the sake of future visitors, I've downloaded and attached all 3 of them to this post (in case it's locked, the password is "www.gem-flash.com").
I wouldn't get my hopes up, but it might be worth giving each a go. Honestly, I wouldn't even know where to begin with flashing but I think you're way ahead of me here.
Genuinely wishing you the best of luck, and I really hope it works out.
Rickav said:
Hey, just got pinged by XDA after a long time. It's all so sleek-looking now.
I'll cut to the chase—Unfortunately, I've got nothing to help with here. I'm a fan of the Hudl2 as well and still have it around as a backup ebook reader as the screen works reliably. It's running walking stock Lollipop and it occasionally throws up Play Services errors (which appears to be resolvable).
Following the dead download link on the MoDaCo forum post, I searched for stock ROMs and landed on the same Gem Flash site that you linked. Specifically, I found 3 results linked to the Hudl2. For the sake of future visitors, I've downloaded and attached all 3 of them to this post (in case it's locked, the password is "www.gem-flash.com").
I wouldn't get my hopes up, but it might be worth giving each a go. Honestly, I wouldn't even know where to begin with flashing but I think you're way ahead of me here.
Genuinely wishing you the best of luck, and I really hope it works out.
Click to expand...
Click to collapse
Thanks @Rickav . Presumably you saw my DM.
All three come out with:
Code:
Finding update package...
Opening update package...
Verifying update package...
E:end of footer from /tmp/update.zip not 0xFFF (File exists)
E:signature verification failed
Installation aborted
once adb sideloaded in stock recovery (all I have access to).
Is there any chance of you making a nandroid backup zip using the CWM fastboot custom recovery in "hudl2 root stuff.zip" on MoDaCo? I know it's asking a lot. @paulobrien might send me a system image and couple of OTA zips and other assorteds for a start which may help. Before I attempted Xposed I was trying to get Lollipop but the OTA server has been decommissioned (confirmed by Kirwan Lyster, head of hudl2 software), so if I can do that by other means that'd be great. Fist priority though: get it running. You can see by the video what is happening.
Many thanks,
Cessna
If can't do this, may need to try to unlock bootloader. Any ideas, also useful.
@Rickav I really appreciate your assistance, but going by this link:
New update Sept 15
www.modaco.com
It looks like my tablet is dead. What do you think of this?
Hi,
In case anyone is looking for clear instructions on how to overcome the problem after a factory reset of the Tesco Hudl 1 & 2 you will find them here (works for Hudl 2 as well). Use a date between 27 June 2019 and 26 June 2020 :
HUDL bricked after factory reset and how to fix it - Hey Munky!
I did a factory reset on my HUDL and bricked it. Here's a quick step-by-step guide on how to unbrick it after a factory reset.
www.heymunky.co.uk
Or the same with pictures but remember to use a date between 27 June 2019 and 26 June 2020 :
Rob's stuff - Hudl - Fix
Update 23 May 2023: This mechanism for recovery of a factory reset Hudl 1 no longer works. Due to the Tesco server at https://device.tesco.mobile.com/ no longer responding correctly to requests this technique no longer works and will fail after Step 18. As far as I know my Custom ROM is now the
rob.themayfamily.me.uk
(If this date solution ever fails then another option is to create a new user in the settings menu and reboot into it.)
Post if it works for you
I am going to try and update my hudl 2 to lollipop android 5. ADB sideload fails so i need to update from sdcard or from cache folder, just a case of where the cache folders are and how to add to them.
Hi @ushilives
Whatever you do, please don't do that! Doing so causes your device to become unbootable, and unrecoverable!!!
It will end up like mine did, and, trust me, you ain't getting it back, KitKat, Lollipop, or else.
Sorry to let you down, I just don't want to see another Hudl killed.
Regards,
Cessna
Did yours brick before or after you installed xposed?
CessnaBroon said:
Hi @ushilives
Whatever you do, please don't do that! Doing so causes your device to become unbootable, and unrecoverable!!!
It will end up like mine did, and, trust me, you ain't getting it back, KitKat, Lollipop, or else.
Sorry to let you down, I just don't want to see another Hudl killed.
Regards,
Cessna
Click to expand...
Click to collapse
Did yours brick before or after you installed xposed?
ushilives said:
Did yours brick before or after you installed xposed?
Click to expand...
Click to collapse
When I rebooted after installing xposed. I also know people who bricked it from sideloading other builds in ADB, due to Tesco's locked bootloader having extra security measures.
CessnaBroon said:
When I rebooted after installing xposed. I also know people who bricked it from sideloading other builds in ADB, due to Tesco's locked bootloader having extra security measures.
Click to expand...
Click to collapse
Ah OK thanks. I'll have a read more into it Rather than using recovery
Please do. Just check for me please, does it still boot? If yes, what have you attempted so far? Thanks