Related
Nexus 7, 2013, 16 gigs, wifi model.
Every few days(sometimes once a day) I get a 'new' android 4.3 update, which once it reboots into the teamwin bootloader, and finishes installing the update(which always seems to work for first 2 steps but says no contents in file, then 2 errors after) I lose root access and it asks if I want to reapply(which I do) and it loads as normal on a restart. I am with build number JWR66N now, but the info page on the TWRP window shows it updates JWR66N to (And I forgot the number here, but its different)
So I'd like to know, is it normal to have 'constant' android updates like this, and if not, what build number should I have?
I have had this issue since about a week after I got my nexus, its been rooted ever since, but in an attempt to fix this issue(Which is just annoying, I doubt its causing any real damage) I unrooted the nexus, updated it(Manually) and re-rooted it using the wugfresh rootkit.
What exactly is the issue here, and how can I fix it?
AtmaDarkwolf said:
Nexus 7, 2013, 16 gigs, wifi model.
Every few days(sometimes once a day) I get a 'new' android 4.3 update, which once it reboots into the teamwin bootloader, and finishes installing the update(which always seems to work for first 2 steps but says no contents in file, then 2 errors after) I lose root access and it asks if I want to reapply(which I do) and it loads as normal on a restart. I am with build number JWR66N now, but the info page on the TWRP window shows it updates JWR66N to (And I forgot the number here, but its different)
So I'd like to know, is it normal to have 'constant' android updates like this, and if not, what build number should I have?
I have had this issue since about a week after I got my nexus, its been rooted ever since, but in an attempt to fix this issue(Which is just annoying, I doubt its causing any real damage) I unrooted the nexus, updated it(Manually) and re-rooted it using the wugfresh rootkit.
What exactly is the issue here, and how can I fix it?
Click to expand...
Click to collapse
really this is just an issue I have and nobody else has seen it? Nobody at all has had this problem and knows the fix? Well gee!
Another bump just incase, its happened again: Update yet nothings actually changed, had to 'swipe to fix' root permissions in bootlader menu.
Here we are again, and i REALLY want to get this fixed, and i just can't accept that 'I'm the only bloody nexus 7 user world frakin wide who has this issue.
So here I am again hoping for some help.
Build JWR66N currently, every few days it tries to update android OS, and it FAILS TO UPDATE, (IT wants to update to JSS15R i think)
New update is 53.8 mb,
Someone please help me out here, how do I get it to either accept the update, or stop freaking out about it?
AtmaDarkwolf said:
Here we are again, and i REALLY want to get this fixed, and i just can't accept that 'I'm the only bloody nexus 7 user world frakin wide who has this issue.
So here I am again hoping for some help.
Build JWR66N currently, every few days it tries to update android OS, and it FAILS TO UPDATE, (IT wants to update to JSS15R i think)
New update is 53.8 mb,
Someone please help me out here, how do I get it to either accept the update, or stop freaking out about it?
Click to expand...
Click to collapse
So from all this time, you weren't able to find your answer using the power of internet?
Stock OTA updates cannot be applied with custom recoveries. That's why it's failing.
JSS15R is 8MB though, not 53.8MB. Either way, you can go back to full stock, recovery included after backing up your stuff. Then update, and reroot + re-install a custom recovery.
Aside from that, you're not really in the good section so don't be surprised you don't get any answer. This is strictly a N7 question, and XDA has a N7 sub section...
http://forum.xda-developers.com/forumdisplay.php?f=1673
polobunny said:
So from all this time, you weren't able to find your answer using the power of internet?
Stock OTA updates cannot be applied with custom recoveries. That's why it's failing.
JSS15R is 8MB though, not 53.8MB. Either way, you can go back to full stock, recovery included after backing up your stuff. Then update, and reroot + re-install a custom recovery.
Aside from that, you're not really in the good section so don't be surprised you don't get any answer. This is strictly a N7 question, and XDA has a N7 sub section...
http://forum.xda-developers.com/forumdisplay.php?f=1673
Click to expand...
Click to collapse
Yes, Must that I foolishly thought this was a ANDROID device and this may have been a similar issue(searched n7 forums and saw nothing) - and even with all the googling, I got nothing. BUT Now that I have 'followed your advice' (God I hope I can get my stuff back, backup didn't go as smooth as I had hoped, and 2 of my fav games I had to copy/paste myself to save them) All I've managed to do now was reset my device back to complete stock settings.... and this morning, Low and behold: SYSTEM UPDATE, ONCE AGAIN, same bloody one, same bloody problem, WILL NOT INSTALL.
So thanks. Next please? (Sorry if I sound a little angry, but I am, this forum, at least I THOUGHT, was full of people who liked to help others and KNEW what they were talking about, not trolls who tell people to 'use the search button' or go elsewhere for help. Honestly, after 2-3 hours a night googling this issue, for 3 weeks give or take now, trust me, I know its not like I have anywhere but here to go, the only reason I'm HERE, in THIS subforum, was because similar issues were posted about right here... more similar than anywhere else.)
Anyways, now I got a wiped device which I hope I can at least get back to where I was. Knowing NOW it had nothing to do with being stock or not, its simply unable to install update.
AtmaDarkwolf said:
Yes, Must that I foolishly thought this was a ANDROID device and this may have been a similar issue(searched n7 forums and saw nothing) - and even with all the googling, I got nothing. BUT Now that I have 'followed your advice' (God I hope I can get my stuff back, backup didn't go as smooth as I had hoped, and 2 of my fav games I had to copy/paste myself to save them) All I've managed to do now was reset my device back to complete stock settings.... and this morning, Low and behold: SYSTEM UPDATE, ONCE AGAIN, same bloody one, same bloody problem, WILL NOT INSTALL.
So thanks. Next please? (Sorry if I sound a little angry, but I am, this forum, at least I THOUGHT, was full of people who liked to help others and KNEW what they were talking about, not trolls who tell people to 'use the search button' or go elsewhere for help. Honestly, after 2-3 hours a night googling this issue, for 3 weeks give or take now, trust me, I know its not like I have anywhere but here to go, the only reason I'm HERE, in THIS subforum, was because similar issues were posted about right here... more similar than anywhere else.)
Anyways, now I got a wiped device which I hope I can at least get back to where I was. Knowing NOW it had nothing to do with being stock or not, its simply unable to install update.
Click to expand...
Click to collapse
you cant update your phone if it is rooted you have to unroot for that or just temporary unroot the option is available in supersu /superuser
and some apps like root keeper and you have to be on stock recovery
AtmaDarkwolf said:
*snip*
Click to expand...
Click to collapse
Not trolling, the sub categories are there for a reason.
Good luck!
I'd like to start off by saying that I have NEVER rooted this device and have been 100% stock since day 1.
The only thing I did was enable developer options to unlock the bootloader so I could sideload OTA updates in the event they take too long to hit my device... No custom recoveries, no custom roms, no custom kernels, no exposed framework... NOTHING.. pure stock.
I started getting the 5.0.2 upgrade notification yesterday. Everytime I download and install, about 30% of the way through the installation I get the android icon showing ERROR. When I open the last recovery log it mentions not being able to open /cache/update.zip with a status 7 error. .. All I can do it reboot and return back to 5.0.1
I did some reading and it was recommended to wipe / format the CACHE partition. So I went into the stock recovery and tried this but to no avail.
I REALLY don't want to factory reset (or flash a factor image) and lose all the progress on the various games I have been playing.
Is there anything else I can try ??
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Thanks for the feedback... I can try this but IMO it's more of a workaround than a solution.
What I'm trying to get at is..... How in the heck would Google or HTC expect the average consumer to resolve such an issue.
Needing to have a PC, have special drivers installed, etc.., is understandable for those who want to step away from STOCK but what about the average consumer who just purchased the tablet to use as is, continues to receive a notification that an update is available, but fails every time it is applied ? Surely there is something that can be done so allow the update to take without having to factory reset or RMA the device...
y2whisper said:
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Click to expand...
Click to collapse
From the sounds of it there is an issue with the OTA file. But I agree you shouldn't be having to do this. I worry about the non xda'ers of the world when this stuff happens
Mine is doing the same crap. Also unmodified Nexus 9. This is nonsense.
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
kurtis.austin2 said:
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Click to expand...
Click to collapse
the.teejster said:
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
Click to expand...
Click to collapse
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
adstro said:
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
Click to expand...
Click to collapse
the.teejster said:
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
Click to expand...
Click to collapse
Have you seen any evidence of this unicorn? Just curious...
Reported on the official Google+ page :
https://plus.google.com/+Nexus/posts/2hB9k5r2Z7T
But I can't find any reports of anyone actually receiving it yet. IF 5.0.2 needs to act as a stepping stone then maybe they delayed to get the 5.0.2 issue resolved 1st.. It seems to be getting more and more attention out there now.
cam30era said:
Have you seen any evidence of this unicorn? Just curious...
Click to expand...
Click to collapse
FWIW.
I went into recovery, wiped cache and tried to side load the 5.0.2 OTA update manually and got the same error. The error displayed approx. 40% into the upload process from the PC.
I'm getting frustrated I can't get 5.0.2 to install. This is ridiculous
When I get the error, Power/Vol+ switches to the recovery log - there is a warning about (from memory) a partition having been mounted R/W, and a suggestion to re-flash the device first.
All I can remember changing from stock is permitting bootloader-unlock from dev options (never got round to unlocking, so far as I remember).
Not too worried, will hang on for the next major update (or 6.x if there is a preview, maybe) - however, it seems 5.0.2 is a fix to allow 5.1.1 to download (from comments on the G+ thread)
My error is an SHA mismatch on /dev/block/platform/sdhci-tegra.3/by-name/APP. I have
47e96f7e7daa360947b456eca9dc5a8e45573b30
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
How do I do this? Need adb from a computer?
kurtis.austin2 said:
How do I do this? Need adb from a computer?
Click to expand...
Click to collapse
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
cam30era said:
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Click to expand...
Click to collapse
Thank you ? very kind of you
kurtis.austin2 said:
Thank you ? very kind of you
Click to expand...
Click to collapse
Welcome
Please read the OP.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
Trying to root Nougat (Android 7)? Then read the comments at the bottom please...
I will first state I do NOT own a Moto G4, I own the G3 and the X Pure which are both 3rd Gen devices, but I was requested to write this tutorial by a few users here due to lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3/4, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread. Remember, I do not own this device although the methods used are the same as similar devices.
Prerequisites:
0) Be running Marshmallow (Android 6.x) stock ROM, at this time Nougat (Android 7.x) is not working via any method.
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: As of 7/18/2016, Amazon ad-subsidised Moto G 4th Gen devices cannot be bootloader unlocked, therefore they cannot be rooted. Sorry, Lollipop and newer Android security changes pretty much put an end to that.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP's Moto G 2016 page
3) You need a copy of the latest stable SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. SR1-SuperSU-v2.78-SR1-20160915123031.zip is the lastest version verified to work with this method.
Note: Do NOT use any 2.77 version, it was a beta intended specifically for the SG Note 7 and will not work, it does not harm but fails to root.
4) Reboot and start TWRP recovery, and PERFORM A COMPLETE BACKUP IN TWRP (Nandroid)!!!
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Notes on Nougat/Android 7... At this time this method of rooting does not work properly on the official Nougat ROM for this device, it causes WiFi issues and interface problems (settings crashes, etc) and with no complete factory image there is no work fix other than to restore your Nandroid backup to pre-root status. If you wish to play with this method and try it, your on your own, I will try to assist but as I stated earlier I do not own this device. To my knowledge as of this posting, there is no working root on stock Android 7 on this device.
I can confirm this worked on my formerly-amazon XT1625 16GB G4. You will get an error about not being able to mount /data, but it proceeds and works anyway.
This is exactly what was missing! I rooted as normal with the latest SuperSU expecting it to just work like on other phones/tablets, but yeah. Before specifying systemless, it hung on boot. After following your instructions it booted right up. Thanks!
Also if you setup adaptable storage with your SDcard, so it works like internal storage, TWRP can't find any files on the SDcard. You will need to revert to non-adaptable storage for TWRP to find the supersu ZIP file.
And make sure you're using the latest SuperSU-- I accidentally tried a very old version which did not work!
Scared Noobie
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Appreciate this. I miss the old days where it was all simple. Everything was flashable. Never had to flash back to something or re flash.
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
Very rare...all you need is read, read, read and follow the instructions. Good luck
Very nice and just what I needed. Worked perfectly on my Amazon Moto G4 with ads. I got no errors or messages but booted fine-got caught in a boot loop once as the SuperSU file explains after it installs. Boots in less then a minute first time.
Marty
acejavelin said:
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Tomsgt said:
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Click to expand...
Click to collapse
cheers mate
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
zipjay said:
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
Click to expand...
Click to collapse
Your welcome... Just give click thanks on the first post, but if you feel absolutely compelled to buy me dinner, there is the Donate button.
Sent from my MotoG3 using Tapatalk
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
mikeruss said:
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
Click to expand...
Click to collapse
Can't you just use MTP mode of TWRP to copy the latest SuperSU to internal storage then flash after creating the config file?
Sent from my MotoG3 using Tapatalk
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
mikeruss said:
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
Click to expand...
Click to collapse
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
acejavelin said:
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
Click to expand...
Click to collapse
32 bit
Sent from my Moto G (4) using Tapatalk
thanks, xposed works fine
Well, I was planning on joining all of you with your Moto G4's soon, or possibly the G4 Plus... but since the Amazon version can't be unlocked anymore I got cold feet, and today Best Buy was running a special on the Moto X Pure 32GB edition for $249 (My Best Buy Elite members only), I pulled the trigger on that one instead. No change in helping though, I didn't have the device to begin with so I will continue to assist with this thread as I can.
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
Hello, just bought the One Plus Nord N20 unlocked version with the intent of rooting it and installing a ROM. I haven't turned it on because I don't want it to upload the latest security patch and make itself unrootable, so I have nothing to backup. Ideally I would want to install e/OS, but have not rooted nor unlocked the bootloader of a device since 2012, so I essentially know nothing. Can someone please explain if:
- Is this is possible?
- If it is, is it a bad idea?
- Is the GSI for e/OS absent for this phone, and is this an issue?
- Is using a GSI a placeholder until a true custom ROM is made?
- Should I wait until the process is more mature?
- I am told to wait until I know what I am doing. Where should I learn / practice since there is still little documentation for this specific phone?
Thank you for your time!
Oromis995
you have nothing to worry about with the updates if u have a gn2200 atleast as far as i know you should be abe to follow any of the root guides posted here
PsYk0n4uT said:
you have nothing to worry about with the updates if u have a gn2200 atleast as far as i know you should be abe to follow any of the root guides posted here
Click to expand...
Click to collapse
Thank you, that's helpful
PsYk0n4uT said:
you have nothing to worry about with the updates if u have a gn2200 atleast as far as i know you should be abe to follow any of the root guides posted here
Click to expand...
Click to collapse
Is this still the case? I read another thread that says this may be the reason it no longer works.
oromis995 said:
Hello, just bought the One Plus Nord N20 unlocked version with the intent of rooting it and installing a ROM. I haven't turned it on because I don't want it to upload the latest security patch and make itself unrootable, so I have nothing to backup. Ideally I would want to install e/OS, but have not rooted nor unlocked the bootloader of a device since 2012, so I essentially know nothing. Can someone please explain if:
- Is this is possible?
- If it is, is it a bad idea?
- Is the GSI for e/OS absent for this phone, and is this an issue?
- Is using a GSI a placeholder until a true custom ROM is made?
- Should I wait until the process is more mature?
- I am told to wait until I know what I am doing. Where should I learn / practice since there is still little documentation for this specific phone?
Thank you for your time!
Oromis995
Click to expand...
Click to collapse
If you think you don't need a backup because "you've not turned your phone on yet", you should probably think twice about trying to flash custom software. Especially GSI...
Just trying to save you some heart ache down the road. Cheers
mobile_sensei said:
If you think you don't need a backup because "you've not turned your phone on yet", you should probably think twice about trying to flash custom software. Especially GSI...
Just trying to save you some heart ache down the road. Cheers
Click to expand...
Click to collapse
I meant data. I know that I need the partitions
oromis995 said:
Is this still the case? I read another thread that says this may be the reason it no longer works.
Click to expand...
Click to collapse
if you decide to use the security patch it came with stock then be sure not to connect tp the internet at all because once its unlocked and rooted and downloads an update dsu sideloader will not work until that update is dealt with and system updates wont work while bootloader unlocked and definitely not going to work if any partitions are modified(not stock such as magisk patched boot image). im not sure about the september update but some did have issues with the august patch although others were successful so it may have just been user error. my suggestion is to just put dsu sideloader and a prerooted gsi on an sdcard or transfer via pc/usb cord to internal storage but don't connect to the internet and use that to gain root long enough to pull your full stock partitions backups. this would be playing it safe. then ifnyou want you can relock your bootloader and update to september/newest and pull another full backup so you have it in the case that ypur successful and if not then your bases are covered to downgrade and downgrading will be as easy as simply reflashing all the stock images you pulled the first time though you shouldnt have to reflash ALL of them but in case you want to / need to then u have them. I cant stress backups enough. I use Partitions Backup & Restore by Wanam from playstore or wherever u want to download it unless u prefer to dd everything but i like the gui its just easier. read my post on how to root any n20 as there are somegood tips there and a great response detailing the procedure and dmtec also posted a much more detailed guide. i still havr a device on May patch and the other on July