Hi fellows,
My kindle fire HD 6 - 4th Gen recently updated itself to 5.1.1. It worked well for a few days and one fine morning, it was stuck with a future date - Feb 10, 2036, yes the year 2036.
I've tried all sorts of things to fix it - factory reset, changed my wifi router (cos it says it gets the time from there), hooked onto my friends wifi, talked to Amazon support (useless anyway) but there hasn't been a resolution. Its day 10 today and the date has moved to Feb 19, 2036.
Because of this year mismatch, the kindle considers all the SSL certificates from present year to be obsolete and doesn't connect to anything which is over SSL - HTTPS, Sync, Apps, nothing works. HTTP sites work as expected, no issues at all.
I was wondering if reinstalling the 5.1.1 update manually would help and that is pretty much my last option, any ideas what else I could try apart from trying to root it ?
How wonderfully bizarre! Are you sure you can't adapt to it . There must be some advantage to a device existing 20 years in the future!
I read some posts a while back in Amazon discussions about fixing time problems with the wifi advanced options (long press network name>modify network>advanced options>ip=static), but you'll need to search for required changes unless you, or someone else here, knows exactly what settings to use.
Systemwise, you can download 5.1.1 from here, put it in /sdcard (not in a folder) and see if it will reinstall by pressing Update Now in Device Options. I don't think that works when you're up-to-date, but worth a try. If no luck, you'll need to root to reinstall 5.1.1 in TWRP. @bibikalka reveals it all here.
EDIT: @crankdoofus, just assumed you'd messed around with manually changing time zone in settings, then changing back to auto. You did, right?
Thanks for reply DoLooper. For now, I think its a sign from my future self to connect to time travel portal, only that I don't know the URL
regarding the trials ..
1. I downloaded the update offline and forced update, but it refused saying its already running equal or higher
2. I tried to use the advanced options in wireless connections .. it doesn't seem to have many only a proxy address and option to provide static IP/DHCP
3. Turning of WiFi, Automatic timezone, rebooting and factory reset and all kind of combinations of these four haven't yielded any positive results
Strangely enough, I have a nexus 7 tablet with the same "use network settings" and it seems to having the correct time all this while.
Any other suggestions before I root it ?
crankdoofus said:
Thanks for reply DoLooper. For now, I think its a sign from my future self to connect to time travel portal, only that I don't know the URL
regarding the trials ..
1. I downloaded the update offline and forced update, but it refused saying its already running equal or higher
2. I tried to use the advanced options in wireless connections .. it doesn't seem to have many only a proxy address and option to provide static IP/DHCP
3. Turning of WiFi, Automatic timezone, rebooting and factory reset and all kind of combinations of these four haven't yielded any positive results
Strangely enough, I have a nexus 7 tablet with the same "use network settings" and it seems to having the correct time all this while.
Any other suggestions before I root it ?
Click to expand...
Click to collapse
Probably a factory reset will fix this.
Another option is to update everything to nice rooted Lollipop, and do factory reset during the process. Root first, install TWRP. Then before installing Lollipop format /data first as fat, then back to ext4 . This should clear everything real good, including /sdcard. Without reboot, from TWRP follow the guide to install Lollipop. This should have the cleanest system you can have, with the exception of some small partitions (which could become a problem for you). See what this gets you.
bibikalka said:
Probably a factory reset will fix this.
Another option is to update everything to nice rooted Lollipop, and do factory reset during the process. Root first, install TWRP. Then before installing Lollipop format /data first as fat, then back to ext4 . This should clear everything real good, including /sdcard. Without reboot, from TWRP follow the guide to install Lollipop. This should have the cleanest system you can have, with the exception of some small partitions (which could become a problem for you). See what this gets you.
Click to expand...
Click to collapse
Thanks for the suggestions bibikalka and here is the update.
A factory reset doesn't help. Its still the same.
I tried these steps .. root using kingroot, used gscript (and 453_key_images.zip and flash453.zip) to get into recovery - TWRP. There I formatted /data as fat, then back as ext4. Everything seemed to work OK, no error messages. Then I put back 5.4.1_1133_stock_recovery_uboot to get the recovery back to stock so I could get back in.
After reboot, it spent about 10 minutes optimizing apps, but the problem still remains.
Recovery logs indicate quite a few of these messages, if its of any help...
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
What else can I try :
1. Another ROM perhaps ? - CM11 by ggow ?
2. Downgrade from 5.1.1 to 4.5.3 ?
Any suggestions are welcome, currently this is not a brick but pretty much useless.
crankdoofus said:
Thanks for the suggestions bibikalka and here is the update.
A factory reset doesn't help. Its still the same.
I tried these steps .. root using kingroot, used gscript (and 453_key_images.zip and flash453.zip) to get into recovery - TWRP. There I formatted /data as fat, then back as ext4. Everything seemed to work OK, no error messages. Then I put back 5.4.1_1133_stock_recovery_uboot to get the recovery back to stock so I could get back in.
After reboot, it spent about 10 minutes optimizing apps, but the problem still remains.
Recovery logs indicate quite a few of these messages, if its of any help...
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
What else can I try :
1. Another ROM perhaps ? - CM11 by ggow ?
2. Downgrade from 5.1.1 to 4.5.3 ?
Any suggestions are welcome, currently this is not a brick but pretty much useless.
Click to expand...
Click to collapse
It's all a mystery, but anyway ... A good bet is to downgrade to 4.5.3, and see if FireOS 4 also has the time screwed up. If it becomes OK, try updating to 5.1.1 . If not, I guess you could try CM11, no harm.
bibikalka said:
It's all a mystery, but anyway ... A good bet is to downgrade to 4.5.3, and see if FireOS 4 also has the time screwed up. If it becomes OK, try updating to 5.1.1 . If not, I guess you could try CM11, no harm.
Click to expand...
Click to collapse
So here is the update
Quick update - got it fixed by running an app to sync the time, it just needed root access to do it.
Long update - I saw that 5.1.2 was out, so I thought it might help. Downloaded and updated offline, didn't help. Worse, now I had lost root and Kingroot said it didn't know how to root it - tried about 7 times.
Booted into recovery, lollipop recovery has sideload options. So I setup adb and drivers (thanks to detailed posts by @DoLooper), and side loaded 4.5.3. Rebooted, date still wasn't fixed. But now kingroot was helpful and I chanced upon this app called ClockSync, which needed root access to sync system time with one of the NTP servers worldwide. And now I am upgrading to 5.1.1 to get back where I was but in the present tense. I intend to keep it rooted and keep the ClockSync app handy.
All this nonsense with Amazon yielded a 30$ store credit which should come in handy now
and thanks a lot for your help guys, @DoLooper and @bibikalka, your replies were just enough for me to prod on.
crankdoofus said:
So here is the update
Quick update - got it fixed by running an app to sync the time, it just needed root access to do it.
Long update - I saw that 5.1.2 was out, so I thought it might help. Downloaded and updated offline, didn't help. Worse, now I had lost root and Kingroot said it didn't know how to root it - tried about 7 times.
Booted into recovery, lollipop recovery has sideload options. So I setup adb and drivers (thanks to detailed posts by @DoLooper), and side loaded 4.5.3. Rebooted, date still wasn't fixed. But now kingroot was helpful and I chanced upon this app called ClockSync, which needed root access to sync system time with one of the NTP servers worldwide. And now I am upgrading to 5.1.1 to get back where I was but in the present tense. I intend to keep it rooted and keep the ClockSync app handy.
All this nonsense with Amazon yielded a 30$ store credit which should come in handy now
and thanks a lot for your help guys, @DoLooper and @bibikalka, your replies were just enough for me to prod on.
Click to expand...
Click to collapse
This is interesting! Did you run 5.1.2 rootless, downgraded to 4.5.3, and then upgraded to 5.1.1 from 4.5.3 using my guide ? So your bootloaders now are 5.1.1 (meaning you did not do anything special regarding bootloaders when you went from 5.1.2 to 4.5.3 to 5.1.1 ) ? And everything is working now ?
bibikalka said:
This is interesting! Did you run 5.1.2 rootless, downgraded to 4.5.3, and then upgraded to 5.1.1 from 4.5.3 using my guide ? So your bootloaders now are 5.1.1 (meaning you did not do anything special regarding bootloaders when you went from 5.1.2 to 4.5.3 to 5.1.1 ) ? And everything is working now ?
Click to expand...
Click to collapse
Yes, once I had 5.1.2, I lost root. Kingroot could not root it even after multiple attempts. The only option was to try out sideload. A sideload with 4.5.3 binaries worked. Then I moved on to 5.1.1 using your guide.
After sideloading 4.5.3, the boot loader was also over written with older one (verified by booting into recovery). After upgrade to 5.1.1, now my boot loader is at 5.1.1 stage.
Everything with regards to kindle is working, tried multiple reboots to be sure. I had a glitch with su though.
Supersu, for some reason complains that it needs to be upgraded, but it stays on the screen indefinitely while upgrade (i tried sideload as well, no luck). An adb shell su -v or adb shell su -V returns kingsroot user. So I'm guessing there are some remains of kingsroot still there although I did a wipe at the end as per your procedure. There seems to be partial root as esexplorer can access /sys, etc very well. Adb shell su fails.
I can help with more diagnostics if you need any. Really thankful for the good job that you're doing here !
Further to my investigations with messed up supersu, I realized that kingroot installs root in a strange manner and supersu doesn't seem to like it. In my opinion, supersu will never work till kingroot is incharge (I may be wrong, this is based on my experience). It keeps saying that it needs to be updated, but never gets done.
So while looking for ways to get rid of kingroot (sorry I don't trust that app other than for rooting my device) and installing supersu, I landed at this thread..http://forum.xda-developers.com/general/general/lenovo-k4-note-replace-kingroot-supersu-t3314955.
If you follow the instructions, it works. So now I'm kingroot free, but still rooted with my favorite su binary.
I'm just putting it here for the benefit of others who might want to do the same. @bibikalka, my suggestion is to include this step in your guide instead of flashing the supersu.zip to end up with a neat and clean kingroot free system. Thanks again for supporting us.
crankdoofus said:
Further to my investigations with messed up supersu, I realized that kingroot installs root in a strange manner and supersu doesn't seem to like it. In my opinion, supersu will never work till kingroot is incharge (I may be wrong, this is based on my experience). It keeps saying that it needs to be updated, but never gets done.
So while looking for ways to get rid of kingroot (sorry I don't trust that app other than for rooting my device) and installing supersu, I landed at this thread..http://forum.xda-developers.com/general/general/lenovo-k4-note-replace-kingroot-supersu-t3314955.
If you follow the instructions, it works. So now I'm kingroot free, but still rooted with my favorite su binary.
I'm just putting it here for the benefit of others who might want to do the same. @bibikalka, my suggestion is to include this step in your guide instead of flashing the supersu.zip to end up with a neat and clean kingroot free system. Thanks again for supporting us.
Click to expand...
Click to collapse
This is a fair point, but of somewhat narrow interest. The TWRP install wipes out Kingroot, so it's not really an issue. People like Kingroot to get them root, but then they all of a sudden become super suspicious And for that reason if you get TWRP, you can install fresh copy of FireOS, which has no Kingroot traces.
This worked for me !!
crankdoofus said:
Hi fellows,
My kindle fire HD 6 - 4th Gen recently updated itself to 5.1.1. It worked well for a few days and one fine morning, it was stuck with a future date - Feb 10, 2036, yes the year 2036.
I've tried all sorts of things to fix it - factory reset, changed my wifi router (cos it says it gets the time from there), hooked onto my friends wifi, talked to Amazon support (useless anyway) but there hasn't been a resolution. Its day 10 today and the date has moved to Feb 19, 2036.
Because of this year mismatch, the kindle considers all the SSL certificates from present year to be obsolete and doesn't connect to anything which is over SSL - HTTPS, Sync, Apps, nothing works. HTTP sites work as expected, no issues at all.
I was wondering if reinstalling the 5.1.1 update manually would help and that is pretty much my last option, any ideas what else I could try apart from trying to root it ?
Click to expand...
Click to collapse
Hi, I had the same issue. I didn't want to root my kindle fire so contacted the Amazon support for help. Since my tablet was out of warranty all they could offer was a discount on a new one. This is after collecting all log reports and updating to OS 5.3.2.0 So I did the following which fixed my date and time issue.
Step 1. Enable developer options and turn on ADB. Search and install ADB drivers for your PC/MAC
Step 2. Download the amazon fire 5th generation super tool by root junkie. http://www.rootjunky.com/amazon-fire-5th-gen-supertool/
Step 3. Connect the tablet and run the super tool. Choose option 2. install google play store.
Once this is done, midway through the process it will correct the date and time. once this is done, you can choose to continue to install play store or stop the process.
Don't try to root, there are several warnings all over the forums that it'll brick the device.
Related
a stock android ROM (recommendations?)?
I've searched, but not found anything that can handily take me from having a rooted 14.3.2.6 HDx 8.9 (Apollo, right?) to a ROM. There's so much confusion about downgrading to an earlier version (for what?), having/not having safestrap, having TWRP, etc.
Anyone got a place where I can simply follow a 1-2-3 guide to go from root to ROM? Thanks!
BRPW said:
a stock android ROM (recommendations?)?
I've searched, but not found anything that can handily take me from having a rooted 14.3.2.6 HDx 8.9 (Apollo, right?) to a ROM. There's so much confusion about downgrading to an earlier version (for what?), having/not having safestrap, having TWRP, etc.
Anyone got a place where I can simply follow a 1-2-3 guide to go from root to ROM? Thanks!
Click to expand...
Click to collapse
There are no 1-2-3 guides. However, the steps required are not complicated but do require carefully reading and attention to detail. As you are probably aware Kindles in general and HDX models in particular are easy to 'brick' with limited/no recovery options. Many folks have killed their device with a simple mistake. Stakes are high with an Apollo given the device's value. Think hard before moving forward; even if you do everything right you can end up with an expensive paperweight. If you're an 'android expert' be aware many recovery techniques used on other devices simply will not work on an HDX. Fastboot cables are useless.
Preliminary questions:
- have you blocked OTA (if so via which method) or otherwise taken steps to isolate your device from automatic updates?
- do you have safestrap or Xposed Framework installed?
- have you enabled adb?
Davey126 said:
There are no 1-2-3 guides. However, the steps required are not complicated but do require carefully reading and attention to detail. As you are probably aware Kindles in general and HDX models in particular are easy to 'brick' with limited/no recovery options. Many folks have killed their device with a simple mistake. Stakes are high with an Apollo given the device's value. Think hard before moving forward; even if you do everything right you can end up with an expensive paperweight. If you're an 'android expert' be aware many recovery techniques used on other devices simply will not work on an HDX. Fastboot cables are useless.
Preliminary questions:
- have you blocked OTA (if so via which method) or otherwise taken steps to isolate your device from automatic updates?
- do you have safestrap or Xposed Framework installed?
- have you enabled adb?
Click to expand...
Click to collapse
Hi,
thanks for the response; I understand 100%.
I have blocked OTA (but weirdly keep getting "kindle is upgrading" messages every time I restart my Kindle)
I have Xposed Framework installed
ADB is enabled.
On another note, I've installed the four Gapps APKs, but my google play store won't work. Any idea why? When I install them, the play store opens and displays apps just fine, but won't download them. I reboot, and when I do I get "Google play store has stopped" and "Google play services has stopped working" messages, and Google Play crashes instantly.
I can't figure out why. Any idea? Apologies for bombarding you with queries.
Your play store issue is probably Google play services. Download version .99 from the internet or the general thread.
As for your next steps.
It depends on how involved you want to go.
You can use safestrap and run the nexus Rom. Some people feel that is less risky because you are not modifying the system as much or recovery at all. However, if something goes wrong, you have almost no way to fix it (it is possible to brick with safestrap).
Or,
Downgrade to 2.3.2 (you have to do this because the 2.6 bootloader will not load any other recoveries or roms. Then put twrp on and use cm11 or similar. This gives you a working recovery to fix some issues which could go wrong.
Finally, you could rollback and unlock your bootloader. If you do that, it is the most involved, and a little risky. However, if you succeed. You will be able to put more rooms on it and this gives you the most options to recover from an error.
Many people are playing with cm12 after this.
It all depends on how you are willing to take your risks. It will all require a lot of reading on the forums.
Good luck.
Sent from my KFTHWI using Tapatalk
BRPW said:
Hi,thanks for the response; I understand 100%.
I have blocked OTA (but weirdly keep getting "kindle is upgrading" messages every time I restart my Kindle)
I have Xposed Framework installed
ADB is enabled.
On another note, I've installed the four Gapps APKs, but my google play store won't work. Any idea why? When I install them, the play store opens and displays apps just fine, but won't download them. I reboot, and when I do I get "Google play store has stopped" and "Google play services has stopped working" messages, and Google Play crashes instantly.
I can't figure out why. Any idea? Apologies for bombarding you with queries.
Click to expand...
Click to collapse
You need to clean up your device before going further. Yes, some folks have successfully rolled back with baggage in tow. With limited data points my observation is previously unsurfaced add-ons and tweaks (usually revealed only after someone fubars their device) are contributors to unfavorable outcomes. Take that for what it's worth.
Recommendations:
- Identify and discard the update file that is triggering the "Kindle is upgrading" message. Best guess is a 14.x upgrade that can't progress due to OTA block. You are looking for a large (500 MB+ file) .bin file with a name similar to "update-kindle-14.4.5.3_user_453011120.bin". Reboot to make sure the upgrade message goes away.
- Tether your device. Download HDX Toolkit to a Windows box and make sure it can see your Kindle. Don't take any actions other than confirming root.
- Disable wifi and delete all existing wireless profiles. Then remove the existing OTA blocker reversing whatever technique was previously used.
- Use HDX toolkit to block OTA (this is the only method I trust for Fire OS 3.0.x-3.2.x)
- Uninstall Xposed framework and all associated modules (module portion isn't technically necessary as they won't run with framework disabled)
- Remove play store, services, framework (via services) and all Google apks. Reboot to make sure your device is 'clean'. You should still have root, of course.
- Come clean on any other tweaks previously made including modifications to build.prop, failed root attempts, safestrap, etc. Anything that deviates from stock.
Post back when complete. I'll then help you through the roll back process and installation of twrp. From there you can install Nexus (excellent, stable rom but Jellybean based) or CM11 (KitKat). Save bootloader unlocking for another day.
Davey126 said:
You need to clean up your device before going further. Yes, some folks have successfully rolled back with baggage in tow. With limited data points my observation is previously unsurfaced add-ons and tweaks (usually revealed only after someone fubars their device) are contributors to unfavorable outcomes. Take that for what it's worth.
Recommendations:
- Identify and discard the update file that is triggering the "Kindle is upgrading" message. Best guess is a 14.x upgrade that can't progress due to OTA block. You are looking for a large (500 MB+ file) .bin file with a name similar to "update-kindle-14.4.5.3_user_453011120.bin". Reboot to make sure the upgrade message goes away.
- Tether your device. Download HDX Toolkit to a Windows box and make sure it can see your Kindle. Don't take any actions other than confirming root.
- Disable wifi and delete all existing wireless profiles. Then remove the existing OTA blocker reversing whatever technique was previously used.
- Use HDX toolkit to block OTA (this is the only method I trust for Fire OS 3.0.x-3.2.x)
- Uninstall Xposed framework and all associated modules (module portion isn't technically necessary as they won't run with framework disabled)
- Remove play store, services, framework (via services) and all Google apks. Reboot to make sure your device is 'clean'. You should still have root, of course.
- Come clean on any other tweaks previously made including modifications to build.prop, failed root attempts, safestrap, etc. Anything that deviates from stock.
Post back when complete. I'll then help you through the roll back process and installation of twrp. From there you can install Nexus (excellent, stable rom but Jellybean based) or CM11 (KitKat). Save bootloader unlocking for another day.
Click to expand...
Click to collapse
I can't find anything resembling that type of file name, after doing a ES file explorer search. I also tried ordering by size and going through folders and files, but still couldn't find anything.
BRPW said:
I can't find anything resembling that type of file name, after doing a ES file explorer search. I also tried ordering by size and going through folders and files, but still couldn't find anything.
Click to expand...
Click to collapse
Don't have an immediate explanation but suggests something is amiss that could muck-up roll back efforts. It could be OTA is only partially blocked so your Kindle sees there is an update but can't download or process it. Do you know what method was used to block updates?
Davey126 said:
Don't have an immediate explanation but suggests something is amiss that could muck-up roll back efforts. It could be OTA is only partially blocked so your Kindle sees there is an update but can't download or process it. Do you know what method was used to block updates?
Click to expand...
Click to collapse
Yeah, I used the KFHDX Toolkit 0.95, and once I'd installed Xposed Framework, I installed the HDXposed module, which also blocks OTA updates.
BRPW said:
Yeah, I used the KFHDX Toolkit 0.95, and once I'd installed Xposed Framework, I installed the HDXposed module, which also blocks OTA updates.
Click to expand...
Click to collapse
HDXposed is likely part of the problem. Uninstall that (make sure wifi is off), reboot then reapply the OTA blocker integrated into KFHDX Toolkit 0.95. Reboot again and see if update message goes away. Might not if a bit got set somewhere indicating that an update is available. That in itself shouldn't be an issue unless information about the update version is also stored (don't believe it is).
Disclaimer: Anytime you muck with OTA blocking there is a chance it won't get set properly resulting in an unwanted update when wifi is restored. Recently this has been the case with renaming the otacerts file...at least on some versions of Fire OS. That said, I have yet to have the OTA blocker in KFHDX Toolkit fail. Once you ditch Fire OS this worry goes away.
Davey126 said:
HDXposed is likely part of the problem. Uninstall that (make sure wifi is off), reboot then reapply the OTA blocker integrated into KFHDX Toolkit 0.95. Reboot again and see if update message goes away. Might not if a bit got set somewhere indicating that an update is available. That in itself shouldn't be an issue unless information about the update version is also stored (don't believe it is).
Disclaimer: Anytime you muck with OTA blocking there is a chance it won't get set properly resulting in an unwanted update when wifi is restored. Recently this has been the case with renaming the otacerts file...at least on some versions of Fire OS. That said, I have yet to have the OTA blocker in KFHDX Toolkit fail. Once you ditch Fire OS this worry goes away.
Click to expand...
Click to collapse
Tried that; deactivated HDXposed, reboot. Enabled OTA, then re-disabled it, and rebooted again. Message still pops up briefly.
Should I continue with the steps you've listed above?
BRPW said:
Tried that; deactivated HDXposed, reboot. Enabled OTA, then re-disabled it, and rebooted again. Message still pops up briefly.
Should I continue with the steps you've listed above?
Click to expand...
Click to collapse
Yes - still need to prep the device. I'll be out-of-pocket for the next 8-10 hours; will look for an update then.
Davey126 said:
Yes - still need to prep the device. I'll be out-of-pocket for the next 8-10 hours; will look for an update then.
Click to expand...
Click to collapse
Okay, I'll complete the list of things you've recommended; again, thanks for your help so far. Really appreciate it.
Edit: All Google apps/APKs removed, Xposed Framework's gone also. Rebooted and clean as stock (apart from root, of course), and zero custom apps apart from SuperSU and towelroot; interestingly, after reboot, there's no 'upgrading' message. So seems that's also disappeared.
BRPW said:
Okay, I'll complete the list of things you've recommended; again, thanks for your help so far. Really appreciate it.
Edit: All Google apps/APKs removed, Xposed Framework's gone also. Rebooted and clean as stock (apart from root, of course), and zero custom apps apart from SuperSU and towelroot; interestingly, after reboot, there's no 'upgrading' message. So seems that's also disappeared.
Click to expand...
Click to collapse
Have a look here for next steps. You are following instructions for 3.2.5-3.2.6 which is at the bottom of the post shaded in grey. To be clear you do not need to modify build.prop (if anything suggests that and/or installing Safestrap you're in the wrong section). You can get everything ready following the post and move forward if you feel comfortable. Remember you will need to reroot and block OTA once the rollback completes; use HDX toolkit for both. An outline of further actions can be found here.
Ok - now i really do have to go ...
Davey126 said:
Have a look here for next steps. You are following instructions for 3.2.5-3.2.6 which is at the bottom of the post shaded in grey. To be clear you do not need to modify build.prop (if anything suggests that and/or installing Safestrap you're in the wrong section). You can get everything ready following the post and move forward if you feel comfortable. Remember you will need to reroot and block OTA once the rollback completes; use HDX toolkit for both. An outline of further actions can be found here.
Ok - now i really do have to go ...
Click to expand...
Click to collapse
Haha thanks; I have the update file downloaded, but getting suspicious about the update.prop file download link. Got phishing warnings and malicious warnings all over the place. May wait and see what you say once you're back.
Edit: Did some research; was clicking the wrong damn button. For anyone who comes across this, click the BLUE 'download now' button. I was clicking the green (read: advert) button. I've rolled my update back all fine; one question.
The update file says: 14.3.1.0, yet my Kindle firmward says 14.3.0.0. Is that supposed to be like that? Anyhow, I'm rerooted, OTA updates blocked. I think I'm going to wait to proceed with the next part. Thanks again (so far)!
BRPW said:
Haha thanks; I have the update file downloaded, but getting suspicious about the update.prop file download link. Got phishing warnings and malicious warnings all over the place. May wait and see what you say once you're back.
Edit: Did some research; was clicking the wrong damn button. For anyone who comes across this, click the BLUE 'download now' button. I was clicking the green (read: advert) button. I've rolled my update back all fine; one question.
The update file says: 14.3.1.0, yet my Kindle firmward says 14.3.0.0. Is that supposed to be like that? Anyhow, I'm rerooted, OTA updates blocked. I think I'm going to wait to proceed with the next part. Thanks again (so far)!
Click to expand...
Click to collapse
Not sure the rollback completed successfully. It is normal for your Kindle to report 14.3.0.0 just after executing the batch file. Fire OS normally won't downgrade so the script 'tricks' the system into thinking it's at 14.3.0.0. Your device then sees the 14.3.1.0 file as an update and processes it. You are essentially leveraging Amazon's update process to execute a rollback.
I'm guessing your forgot to transfer the bin file to your device after executing the upgrade script. If accurate your Kindle is in a someone dangerous state. You'll want to disable OTA blocking, copy the bin file to 'internal storage' and then check for updates via Fire OS settings. It may take a few minutes for your Kindle to recognize the update file. Also note the original bin file needed to reside in the same windows directory as the batch file when it was executed.
Side note: We are experiencing a rare power outage in my area. I'm penning this from a secondary system. Won't be staying on long to conserve battery. Will check for updates once power is restored.
Davey126 said:
Not sure the rollback completed successfully. It is normal for your Kindle to report 14.3.0.0 just after executing the batch file. Fire OS normally won't downgrade so the script 'tricks' the system into thinking it's at 14.3.0.0. Your device then sees the 14.3.1.0 file as an update and processes it. You are essentially leveraging Amazon's update process to execute a rollback.
I'm guessing your forgot to transfer the bin file to your device after executing the upgrade script. If accurate your Kindle is in a someone dangerous state. You'll want to disable OTA blocking, copy the bin file to 'internal storage' and then check for updates via Fire OS settings. It may take a few minutes for your Kindle to recognize the update file. Also note the original bin file needed to reside in the same windows directory as the batch file when it was executed.
Side note: We are experiencing a rare power outage in my area. I'm penning this from a secondary system. Won't be staying on long to conserve battery. Will check for updates once power is restored.
Click to expand...
Click to collapse
Hey Davey,
hope your power problems get sorted soon. As for the update, I did in fact pull the file both into the "rollback89v2" folder (containing the install.bat) and into the 'internal storage' area of the kindle, so should be no problem there. Got up this morning, headed to the 'Device' section to find my Kindle says 'update available'.
Bear in mind that OTA is disabled, and I've not enabled my WiFi since I began the process yesterday, so there should be ZERO chance of that being a normal OTA; I'm guessing it's the 'update' to 14.3.1.0?
BRPW said:
Hey Davey,
hope your power problems get sorted soon. As for the update, I did in fact pull the file both into the "rollback89v2" folder (containing the install.bat) and into the 'internal storage' area of the kindle, so should be no problem there. Got up this morning, headed to the 'Device' section to find my Kindle says 'update available'.
Bear in mind that OTA is disabled, and I've not enabled my WiFi since I began the process yesterday, so there should be ZERO chance of that being a normal OTA; I'm guessing it's the 'update' to 14.3.1.0?
Click to expand...
Click to collapse
Sorry for the delay. Yes, accept the update if you have not done so already. You will probably need to re-enable OTA (keep wifi off) for processing to complete. After reboot the device should report it's on 14.3.1. You can then reroot and block OTA via HDX toolkit.
Next step is to install twrp. If you are comfortable issuing adb commands you can use the method outlined here which is also where you grap the custom apk. Alternatively, sideload flashify (here or elsewhere; copy apk via tether). I recommend the latter as flashify simplifies future efforts and contains some nice backup/recovery features.
Test twrp by powering down your device then restarting by pressing power + vol-up. Release the power button when the grey Kindle logo appears. Release the volume button a few seconds later. You should eventually enter the twrp environment. Familiarize yourself with the options but don't take any actions. When complete hit the reboot button from the main screen (lower right corner).
Then update your bootloader to 3.2.3.2. This is listed as a prerequisite for twrp but the order is not important provided both get done. Personally I prefer to get twrp installed early in the sequence as it offers vastly improved recovery options should something go wrong. You can flash the updated bootloader from twrp or flashify.
Once this is done you are ready for a custom rom! Post when complete and I will briefly outline your options.
As always, think through each step before proceeding. Make sure you have the right files. Verify MD5s once copied to your device (I use Hash Droid). Installing twrp and the bootloader update involve flashing code directly to your device. A mistake can be non-recoverable.
Davey126 said:
Sorry for the delay. Yes, accept the update if you have not done so already. You will probably need to re-enable OTA (keep wifi off) for processing to complete. After reboot the device should report it's on 14.3.1. You can then reroot and block OTA via HDX toolkit.
Next step is to install twrp. If you are comfortable issuing adb commands you can use the method outlined here which is also where you grap the custom apk. Alternatively, sideload flashify (here or elsewhere; copy apk via tether). I recommend the latter as flashify simplifies future efforts and contains some nice backup/recovery features.
Test twrp by powering down your device then restarting by pressing power + vol-up. Release the power button when the grey Kindle logo appears. Release the volume button a few seconds later. You should eventually enter the twrp environment. Familiarize yourself with the options but don't take any actions. When complete hit the reboot button from the main screen (lower right corner).
Then update your bootloader to 3.2.3.2. This is listed as a prerequisite for twrp but the order is not important provided both get done. Personally I prefer to get twrp installed early in the sequence as it offers vastly improved recovery options should something go wrong. You can flash the updated bootloader from twrp or flashify.
Once this is done you are ready for a custom rom! Post when complete and I will briefly outline your options.
As always, think through each step before proceeding. Make sure you have the right files. Verify MD5s once copied to your device (I use Hash Droid). Installing twrp and the bootloader update involve flashing code directly to your device. A mistake can be non-recoverable.
Click to expand...
Click to collapse
Having issues with the first part. I have 'update failed'. I keep trying wifi on/OTA disabled, OTA enabled/Wifi disabled. Sometimes I get 'update now', but having trouble. It wants OTA and Wifi enabled. Any workaround?
BRPW said:
Having issues with the first part. I have 'update failed'. I keep trying wifi on/OTA disabled, OTA enabled/Wifi disabled. Sometimes I get 'update now', but having trouble. It wants OTA and Wifi enabled. Any workaround?
Click to expand...
Click to collapse
Suggestions (in priority order):
- remove all existing wifi profiles (so your device can't connect), move away from open hotspots, enable wifi and retry. Some report this solves the problem.
- if above fails shut down device and boot into recovery via power + vol-up. From there perform a factory reset. Then see if the update takes.
There is a small risk of crashing your device with the second method. I used to recommend against it but others report it is a necessary step. Suspect it depends on how OTA has been disabled in the past. Factory resets only cause problems if your device has unusual mods that prevent the reset from fully completing.
Davey126 said:
Suggestions (in priority order):
- remove all existing wifi profiles (so your device can't connect), move away from open hotspots, enable wifi and retry. Some report this solves the problem.
- if above fails shut down device and boot into recovery via power + vol-up. From there perform a factory reset. Then see if the update takes.
There is a small risk of crashing your device with the second method. I used to recommend against it but others report it is a necessary step. Suspect it depends on how OTA has been disabled in the past. Factory resets only cause problems if your device has unusual mods that prevent the reset from fully completing.
Click to expand...
Click to collapse
First option worked. Right, I side-loaded flashify. I'm guessing Im choosing the recovery image option, which then asks me to choose a recovery option; I choose TWRP, which then takes me to a device option. I don't see HDX 8.9 anywhere there. Which device am I choosing?
Edit: Scratch that; figured out what I had to do. Right, everything is done. TWRP's installed and working fine; bootloader is installed (though I don't know how to check it installed correctly). I think I'm ready for ROMs unless there are more checks to do?
Second edit: After some research, I think I've decided on CM11 (That's KitKat, right?). It seems that everything works on that; wifi works nicely, the Kindle app works nicely (had a HD7 that had issues after I flashed an Android ROM), even the camera works nicely. Just need a clear guide on how to flash it, so will wait for you to come back. It's things like "do I wipe dalvik cache, etc" that I'm confused about also. I'd rather not mess it up on the last hurdle trying to rush into it.
To specify, I'm looking at this one: http://forum.xda-developers.com/kin...rom-cm-11-20150228-unofficial-apollo-t3042776
Does it come pre-installed with gapps or no? Can't quite figure that out, since some ROMs specifically mention that they have gapps already loaded in.
Thanks.
Hi all,
Putting it briefly....
Factory reset of hdx 7" on 4.5.2
Stuck at Kindle Fire logo
Shows in PC as Internal Storage but just empty folders Music, DCIM etc...
Can get ADB connection (good news?)
That's it....now here's the interesting bit.....
If I use Kindle Fire Utility and try to root using Towelroot the device goes straight go lock screen. I slide to open and am confronted with Towelroot app. Click on Make It Rain but nothing happens.
If I try other things like installing SU it returns with permission errors.
I can also get to the devices settings too. No other apps installed just HDXPOSED and TOWELROOT.
Got me baffled... Any ideas how to fix?
You can NOT use Towelroot for 4.5.2! You must use Kingroot. Read about this, I've no experience with it. From what I've read it's possible it requires internet connection, I also read this could be for optional download of some browser or whatever, so try to disable such options, if available. You should avoid internet connection, or have it as short as possible, to avoid OTA upate from Amazon to 4.5.4.
Yep I get that I can't use TOWELROOT. I'm just pointing out that installing it gets me past the stuck Kindle Logo into the devices settings. Just no other apps or home scree though. Can't lock screen and if I restart the device it sticks at logo again....
myotai said:
Yep I get that I can't use TOWELROOT. I'm just pointing out that installing it gets me past the stuck Kindle Logo into the devices settings. Just no other apps or home scree though. Can't lock screen and if I restart the device it sticks at logo again....
Click to expand...
Click to collapse
Nothing comes to mind. Generally being stuck at the grey Kindle logo is terminal on a device with stock recovery and a locked bootloader. For future reference HDXPOSED is obsolete and may have contributed to your woes. It was never designed for FireOS v4 and doesn't work well on later versions of FireOS v3.
Thanks,
Yet I can get as far as 'Settings'. Isn't there a way I can push an update via ADB and flash....I guess I'd need to install root first? Is either possible?
P.s its not the grey logo its the coloured orange animated one.
myotai said:
Thanks,
Yet I can get as far as 'Settings'. Isn't there a way I can push an update via ADB and flash....I guess I'd need to install root first? Is either possible?
P.s its not the grey logo its the coloured orange animated one.
Click to expand...
Click to collapse
Assume you tried another factory reset. Being stuck at the orange logo offers some hope but there is no Rx that I know of.
Obtaining root is obviously desirable. You can try installing Kingroot via adb install and hope it executes (like towelroot apparently does) and continues to completion. If successfully you could try to repair the damage that is preventing FireOS from fully booting.
I recall someone saying installing a different launcher (eg: Nova) allowed their Kindle to boot.
Another path is to place the 3.2.8 rollback file into the root of sdcard and hope it takes.
Thanks - I have had a look but can't see a specific guide to installing Kingroot via adb. There are generic tips and pointers but I want to salvage what I have and not completely brick it - does anyone know where the thread is?
Thanks...
myotai said:
Thanks - I have had a look but can't see a specific guide to installing Kingroot via adb. There are generic tips and pointers but I want to salvage what I have and not completely brick it - does anyone know where the thread is?
Thanks...
Click to expand...
Click to collapse
You probably won't find that (not aware of any forum postings). Here's the deal. You are operating in uncharted waters trying to revive an unlocked/unrooted device that got borked for unknown reasons. You are going to have to a bunch of research and take some chances. FireOS can be a bxxch to repair. If the device is under warranty your best course of action is to engage Amazon for an exchange.
Kingroot is a longshot idea which I would not have mentioned if not for your experience with Towelroot. I have no idea if it will work.
Google (or another search engine) is your friend. A couple representative links below that popped up on the first attempt. I have no experience with either site an can not vouch for the content. Just a starting point ...
- Kingroot
- ADB Info
Thanks for your feedback!
I guess nothing ventured n all that!
Its a paper-weight at the moment so can't get much worse.....I'll wander around those un-charted lands and see what I come up with!
Ok, so I've managed to root using Kingroot. Installed Su too. But that's as far as I've got - I'm hoping that there is some way of salvaging this machine now I have root enabled and can get as far as the settings menu?
Thanks...
myotai said:
Ok, so I've managed to root using Kingroot. Installed Su too. But that's as far as I've got - I'm hoping that there is some way of salvaging this machine now I have root enabled and can get as far as the settings menu?
Thanks...
Click to expand...
Click to collapse
So you're on 4.5.2 rooted & OTA disabled now? Then try to install Safestrap v4. If it works, backup your stock slot (even if it doesn't work, who knows what it'll be good for), and move it to your PC. As the secondary slots won't work with WLAN atm anyway, you can install one of the Safestrap v4 compatible ROMs, e.g. Nexus, or CM11 in the stock slot, don't create any secondary Slots (yet).
myotai said:
Ok, so I've managed to root using Kingroot. Installed Su too. But that's as far as I've got - I'm hoping that there is some way of salvaging this machine now I have root enabled and can get as far as the settings menu?
Thanks...
Click to expand...
Click to collapse
To confirm you are now on rooted 4.5.2 but can get beyond the FireOS settings menu. If you install an apk via adb can you retain enough control to launch the app UI? You can do this via an adb shell command; unfortunately, the specifics are beyond my knowledge. Hopefully someone else can jump in or you can research on your own (if needed).
There is no safe way to repair FireOS directly with a locked bootloader. On many Android devices you would simply reflash/reinstall the ROM. Unfortunately, Amazon neutered the stock recovery environment as you discovered. If something goes wrong you are in a world of hurt. I think there is a very good chance your device can be revived. Just need to proceed carefully and not bork things to the point were you don't get past the grey logo. That generally means you own a door stop.
Thoughts (sorry if these are obvious):
- Keep in mind OTA is probably enabled on your device. Stay off wifi if you get that far; best to use a tether for file transfer, etc. until the problem is fixed. You can also rename the OTA apk via adb ... but your focus should be elsewhere at this point.
- It appears the FireOS launcher is hanging during initial setup (as you did a factory reset). You may find joy by installing another launcher (eg: Nova via adb) which often set themselves as the default when installed. Once you regain some control you can then install Safestrap v4 which is the pathway to other roms or repairing 4.5.2. Be aware FireOS will try to reset the default launcher on reboot. If this method works don't mess around trying to fix stuff. Install Safestrap v4 immediately (you also need to open the app and install Safestrap recovery) so you retain some control over your device during further troubleshooting.
- If a different launcher does not work try going for Safestrap v4. You will probably need to get smart around adb shell commands as you have to launch the UI to install the Safestrap recovery environment.
Thanks all taken in - my knowledge of ADB and its various commands are being added to as the hours go by - never really used it before.
Determind though........!
So, its looking better. Managed to get Safestrap installed and using a VERY convoluted method got into Recovery. After four attempts installed CM11 and have a working tablet now.
What I want to do now is somehow get a stock Kindle ROM running....any ideas?
Thanks again for your help everyone!
myotai said:
So, its looking better. Managed to get Safestrap installed and using a VERY convoluted method got into Recovery. After four attempts installed CM11 and have a working tablet now.
What I want to do now is somehow get a stock Kindle ROM running....any ideas?
Thanks again for your help everyone!
Click to expand...
Click to collapse
Yep - just flash 4.5.2 rom from here (don't use any other - you'll be rewarded with a brick). I strongly suggest you backup your existing stock slot (containing CM11) and reflash that to a secondary slot that you'll need to create. You won't be able to use wifi on the secondary slot but it will give you a rom to boot into in the event something goes wrong with the FireOS flash. Once you get FireOS working in the stock slot you should be able uninstall Safestrap. The operative word is 'should' as the system and recovery partitions need to be consistent for FireOS to boot properly. From what you have shared there is no reason to believe this is not the case - but the risk can not be dismissed. The other option is to leave Safestrap installed which only adds an annoying splash screen on boot but otherwise does not impact performance. What it does do is give you a pseudo-recovery environment which can be quite handy as you have discovered! It's also the vehicle for installing other roms such as CM11, Nexus v4, etc.
Take note of the cautions in the linked OP, in particular OTA. After flashing 4.5.2 you'll need to root and rename the OTA apk before enabling wifi. Amazon is aggressively pushing 4.5.4 which can not be rooted. Don't ruin your day - block OTA (yea - that was stupid).
Thanks so much. Its worth listing the procedures that got me this far...
I think installing TOWELROOT via ADB despite the fact I knew it wouldn't work was oddly the only thing that got me as far as 'settings' from a stuck Kindle logo. Then I had to resgiter the device in order to go to 'new offers' in the books setting to access the browser.....emails......Kingroot......finally Safestrap....boom!
Does anyone know of a custom recovery that has been compiled for the LG L15G (AKA Sunrise)? I've been looking all weekend for one and haven't had any luck. I know there's no official build of either CWM or TWRP available for it, but I'm hoping to find an unofficial build that will work. I have it rooted already, but I've not been able to find a recovery for it and I don't want to do any more hacking till I have that.
Also if anyone can point me towards a decent custom ROM for this thing I'd appreciate it. I haven't had any luck finding that either.
siskulous said:
Does anyone know of a custom recovery that has been compiled for the LG L15G (AKA Sunrise)? I've been looking all weekend for one and haven't had any luck. I know there's no official build of either CWM or TWRP available for it, but I'm hoping to find an unofficial build that will work. I have it rooted already, but I've not been able to find a recovery for it and I don't want to do any more hacking till I have that.
Also if anyone can point me towards a decent custom ROM for this thing I'd appreciate it. I haven't had any luck finding that either.
Click to expand...
Click to collapse
i have this model but i updated it before I knew it would prevent me from rooting it... any way you could upload a backup of your firmware that I can use to downgrade to?
How can you beat a $9 phone
siskulous said:
Does anyone know of a custom recovery that has been compiled for the LG L15G (AKA Sunrise)? I've been looking all weekend for one and haven't had any luck. I know there's no official build of either CWM or TWRP available for it, but I'm hoping to find an unofficial build that will work. I have it rooted already, but I've not been able to find a recovery for it and I don't want to do any more hacking till I have that.
Also if anyone can point me towards a decent custom ROM for this thing I'd appreciate it. I haven't had any luck finding that either.
Click to expand...
Click to collapse
Just picked this phone up too, any luck on getting a ROM for it?
I picked one up....couldn't resist for just $9.82. I didn't let it update, so I was able to root it with Kingroot 4.6. Quite snappy after all the bloatware was removed. Have about 1.5gb of internal memory left, but added an 8gb microSD. I haven't been able to findy any recovery, doubt one exists. Nice little emergency phone to have in the car or backpack.
Just picked this phone up as well, and KingoRoot doesn't work. I wasn't prompted for a firmware update when I first cranked it up so I guess I'm on some version that isn't supported? Can anybody clarify what the status of this device is currently? I've got the Tracfone version.
I just rooted my LG L15G tracphone with KingRoot and it worked immediately. Great!
Next step is to get this 10 dollar phone unlocked.
By the way, my firmware version is: Android 4.4.2
I picked one up last night. Kingroot said my device wasn't supported but clicking "try it" successfully rooted the device!
I replaced Kingroot with SuperSU by following these directions: http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html?m=1
I've removed McAfee, but are the Tracfone bloat apps safe to remove?
Tracfone refused to give me the unlock code because their policy is that the phone must be active and have minutes on it for 12 consecutive months (wtf?)
One unlock website did have our device listed (http://www.imei-unlocker.com) but both their methods said that unlock wasn't available yet. They refunded me for both attempts.
If anyone has a Linux setup, we can compile our own TWRP. I found the kernel source earlier today: http://opensource.lge.com/osSch/list?types=NAME&search=Lgl15g
anuraj1 said:
I picked one up last night. Kingroot said my device wasn't supported but clicking "try it" successfully rooted the device!
I replaced Kingroot with SuperSU by following these directions: **Link removed**
I've removed McAfee, but are the Tracfone bloat apps safe to remove?
Tracfone refused to give me the unlock code because their policy is that the phone must be active and have minutes on it for 12 consecutive months (wtf?)
One unlock website did have our device listed (**Linked Removed***) but both their methods said that unlock wasn't available yet. They refunded me for both attempts.
If anyone has a Linux setup, we can compile our own TWRP. I found the kernel source earlier today: **link removed **]
Click to expand...
Click to collapse
I just got this phone for Christmas. What version of Kingroot did you use? The ones I'm downloading don't work. (The one I've tried says something about no available root strategy and adds me to some stupid que line or something. There is no "try it" button after it does this.) You happen to have the specific APK you used and what version was your phone on when you rooted it?
Currently mine is Android version 4.4.2 with kernel version 3.4.0. I haven't attempted to update it yet as I am to assume that would be a bad idea. Unless you have a version newer then mine, then I guess updating would actually help me in this situation.
Looks like there STILL isn't any custom rom or custom recovery for this phone yet. It's been out since July and thanks to the $10 phone promo, there are tons of these out in the wild so I'm surprised nothing has been done with it yet.
I really want to root it as I want to remove some bloatware like McAfee and Polaris office. I would also like to uninstall Chrome so that I can install it to SD card. (unless Chrome can't be moved to SD card, in which case this would be a waste of time I suppose.) Aside from a few extra Google apps, there really isn't that much bloatware aside from what I already mentioned above. I can wait for a custom rom/recovery (though having a custom recovery would be nice as it would allow me to backup my phone incase something gets messed up). I just want to free up some internal storage by removing the bloatware.
(also, the no outside links thing with new users is annoying. I agree new users shouldn't be allowed to. But please at least code the forum to be smarter. I had to manually remove all the links to a post I quoted before it would let me post. That's kinda stupid. If I quote a post in the same thread I'm responding too that has links, it should be assumed to be safe since the links were posted by a verified member. I would hope the forum could fix that or at least have the common ***king courtesy of removing the links from the quotes for me. )
EDIT:
Ok some interesting news to report. It almost wants to work now. For what ever reason, it randomly decided to finally show me the "Try it" button. (I should have clarified earlier it never displayed that button. It would just say root strategy unavailable and that was the end of it. Now it says there is one and lets me use the Try It button. However it will get to about 60% (though it will randomly stop earlier on other attempts. Sometimes my phone will reboot after it reaches 20% or so) it will just say root failed.
I don't understand why this is seeing that my LG Sunrise is pretty much the same as someone else who managed to root it with Kingroot. It's never been updated. (I even checked for updates and there aren't any).
The only thing I can think of that might be a problem is that the phone isn't yet activated as I have not gotten air time for it yet. Does this root process require the phone to be on an active SIM first?
Root with Root Genius
I have root my LG L15G (Android 4.4.2, kernel 3.4.0+, software version LGL15G10f) with Root Genius for PC v3.0.85.
Of cource, before rooting "Developer options" must be unlocked (5-8 taps on Settings>About Phone>Software information>Build number) and turned on; in "Developer options" must be selected "USB debugging".
After this connect phone to PC. All phone drivers must be installed.
Run Root Genius. When program will ready and say about connect with LG L15G - press one button. After 2-3 minutes root is enabled.
Titanium Backup works. But I have no ideas for unlock the phone to make a possibility work in other GSM-networks, except TracFone's.
Hmm, I had tried Root Genius and that didn't work for me (and yeah I did enable USB debugging. I apparently was using an older build of Root Genius. But I found and used the build you used and still get the unsupported model error. ). My software version is as follows:
Android Version: 4.4.2
Baseband version: M8610B-AAAANAZM-1.0.6060
Kernel version: 3.4.0+
Build number: KOT49I.LGL15G11a
Software version: LGL15G11a
There does appear to be some differences in the software version of mine vs the post above me. I'm guessing they changed something. But that's odd as my phone was brand new just like yours assuming you got it around the same time as me.
EDIT. Ok some bad news. Looks like there was a newer software update (that my phone apparently came with) that blocks root and even prevents download mode from working. (I had attempted to boot into download mode but none of the button combinations work and even the root scripts I've tried can't get it to reboot into download mode)
Seems I'm stuck with a phone I probably can't ever root.
It seems it can still be forced into download mode by using a "56k/130k/910k cable" cable (special cable with resistor on one of the data lines). But they are running for $18 on ebay and way to damn expensive for a simple cable with a resistor installed. Resistors are probably only worth pennies each, so they are way too expensive to be charging that much for it.
If I had a such a cable, the root script I had tried awhile back might have worked as it needs to get the phone into download mode to finish the process.
There seems that there's little hope for your phone but I may have a solution. My LG Sunrise got updated as well and got root access with the update. You can use King Root but not Kingo.
Look it up on Google. So far I've had no success on getting to the recovery mode.
I've tried rooting with KingRoot. It will just say it failed after 20% (sometimes it goes higher, but always end with it saying this).
Note that unlike your phone, mine already had the latest update out of the box.
Apache Thunder said:
I just got this phone for Christmas. What version of Kingroot did you use? The ones I'm downloading don't work. (The one I've tried says something about no available root strategy and adds me to some stupid que line or something. There is no "try it" button after it does this.) You happen to have the specific APK you used and what version was your phone on when you rooted it?
Currently mine is Android version 4.4.2 with kernel version 3.4.0. I haven't attempted to update it yet as I am to assume that would be a bad idea. Unless you have a version newer then mine, then I guess updating would actually help me in this situation.
Looks like there STILL isn't any custom rom or custom recovery for this phone yet. It's been out since July and thanks to the $10 phone promo, there are tons of these out in the wild so I'm surprised nothing has been done with it yet.
I really want to root it as I want to remove some bloatware like McAfee and Polaris office. I would also like to uninstall Chrome so that I can install it to SD card. (unless Chrome can't be moved to SD card, in which case this would be a waste of time I suppose.) Aside from a few extra Google apps, there really isn't that much bloatware aside from what I already mentioned above. I can wait for a custom rom/recovery (though having a custom recovery would be nice as it would allow me to backup my phone incase something gets messed up). I just want to free up some internal storage by removing the bloatware.
(also, the no outside links thing with new users is annoying. I agree new users shouldn't be allowed to. But please at least code the forum to be smarter. I had to manually remove all the links to a post I quoted before it would let me post. That's kinda stupid. If I quote a post in the same thread I'm responding too that has links, it should be assumed to be safe since the links were posted by a verified member. I would hope the forum could fix that or at least have the common ***king courtesy of removing the links from the quotes for me. )
EDIT:
Ok some interesting news to report. It almost wants to work now. For what ever reason, it randomly decided to finally show me the "Try it" button. (I should have clarified earlier it never displayed that button. It would just say root strategy unavailable and that was the end of it. Now it says there is one and lets me use the Try It button. However it will get to about 60% (though it will randomly stop earlier on other attempts. Sometimes my phone will reboot after it reaches 20% or so) it will just say root failed.
I don't understand why this is seeing that my LG Sunrise is pretty much the same as someone else who managed to root it with Kingroot. It's never been updated. (I even checked for updates and there aren't any).
The only thing I can think of that might be a problem is that the phone isn't yet activated as I have not gotten air time for it yet. Does this root process require the phone to be on an active SIM first?
Click to expand...
Click to collapse
If you still haven't got root yet,for me it was McAfee that's been blocking Kingroot every since Nov.
Even though I never set up an account,it was the culprit..I opened the McAfee app created the account and Disabled.
Went to settings,ALL apps,then opened McAfee..Scrolled down to ''manage space'' and deactivated and hit force stop.
Then I ran KingRoot version 4.8.0 from this site.My device rebooted at around 30%,went back to KingRoot and it finished rooting.
THANK YOU!
It took a few tries, but after disabling McAfee's root protection (It completely skipped my mind that this stupid app would have a feature that would interfere. ) KingRoot definitely did it's thing. (I had to re-attempt twice because once it rebooted and failed. So I had to kill the app again and try again. That time it rooted without restarting).
I've already uninstalled McAfee and a few other system apps I need to get rid of. (McAfee on a $10 phone? Yeah..... No.... I'll take my chances. )
I also replaced KingRoot with SuperSU and uninstalled Purify and the KingRoot app that installed the root. After cleaning out unneeded bloatware, this phone is pretty responsive now! It used to lag a little and not register touches some times. But after cleaning out the bloatware (McAfee was probably the main source of the lag) it runs pretty well now!
EDIT:
Ok minor issue. I can't seem to uninstall Chrome (since it's a system app on this phone). It keeps reinstalling it self. It won't stay gone. What would be causing that? I wanted to move Chrome to SD so it doesn't take up space. But this particular phone won't let me.
Seems to happen with Polaris Office as well. Not a big deal at the moment. I can just freeze this app so it won't take up any CPU time/ram. Freezing it seems to work fine. Uninstalling it just results in it mysteriously reinstalling it self....
Does yours lose root after rebooting? I tried to run 'adb reboot recovery' for giggles and SuperSU no longer had root when it failed to start the local and booted normally.
---------- Post added at 04:27 AM ---------- Previous post was at 04:19 AM ----------
anuraj1 said:
If anyone has a Linux setup, we can compile our own TWRP. I found the kernel source earlier today: http://opensource.lge.com/osSch/list?types=NAME&search=Lgl15g
Click to expand...
Click to collapse
I have the Android SDK installed on my desktop but the TWRP porting guide by Dees_Troy is a little bit too vague for a first timer. I was able to extract the stock recovery using dd this afternoon.
I haven't tried to reboot mine into recovery mode. But root sticks when doing normal reboots.
recovery/rom LG-L15G
I am currently working with this phone to provide a twrp recovery that will work properly, please hang on while i work out the bugs. its been a while since i developed anything, was taking a extended break from development
DroidHost said:
I am currently working with this phone to provide a twrp recovery that will work properly, please hang on while i work out the bugs. its been a while since i developed anything, was taking a extended break from development
Click to expand...
Click to collapse
That's really awesome! I'm looking forward to what you come up with. I'd be happy to send you some beer money for your efforts as well!
anuraj1 said:
That's really awesome! I'm looking forward to what you come up with. I'd be happy to send you some beer money for your efforts as well!
Click to expand...
Click to collapse
Hang on to that beer money for now, I am working on zeroing the /laf partition to gain access to fastboot hopefully this will work out, and we will have save and easy way to unlock the bootloader on phone to make it flashable
DroidHost said:
Hang on to that beer money for now, I am working on zeroing the /laf partition to gain access to fastboot hopefully this will work out, and we will have save and easy way to unlock the bootloader on phone to make it flashable
Click to expand...
Click to collapse
That's fantastic. If it would help, I have one of those variable resistor cables that some LG phone requires for supporting baseband or entering the bootloader.
This is the cable I have: http://m.ebay.com/itm/131321398015
It is described here as well: http://forum.xda-developers.com/showthread.php?t=2069564
Alright XDA Community. I need some help. Desperately. So I had plans on rooting my tablet (TF201) to install a custom ROM. Being that I have version 4.1.1 installed I would looking for something a little newer and modern. That did not go as planned from the beginning. Since the first step was rooting it, I looked for a ROM. So I searched the web, including XDA and found KingRoot to root my device. Either KingRoot was a terrible choice or something did not go right with the process. Now when I turn on my device I get random pop ups for for stupid garbage that I don't want installed like What's App and UC News. Everything functions as it should but I get random messages that Settings stopped working. I get random apps being installed on a regular basis. I could be in an app and I get a blank / black box on top of something trying to open or install. This very frustrating and I am completely over my head now. So here is what I would love help with;
1. I would like to UNROOT my device to ALL stock settings and firmware. Completed
2. I would like to ROOT my device PROPERLY. Completed
3. I would like to install a custom ROM with Android 6.x or 7.x (Something plain and vanilla)
4. I would LOVE this help if at all possible in plain English Step by Step with pictures if possible. I would like it dummy proof.
Thank you very much for any and all help. It will be very much appreciated.
PS. I do not need to back anything up. It was a fresh reset recently and I do not have anything to backup.
Step 1 is complete. I used Kingo Root to UNROOT my device.
Step 2 is complete. I used Kingo Root to ROOT my device.
Have you unlocked the bootloader using the Asus supplied software?
NP
No. I downloaded it and installed it but when I go to run the APP it asks for my Google Credentials but it does not accept them. I use the credentials every day so I know my username and password but it does not work.
Delete you google account then run the bootloader unlocker again.
NP
Nektopoli said:
Delete you google account then run the bootloader unlocker again.
NP
Click to expand...
Click to collapse
Thank you very much. That did the trick. Here is the problem though. I think I am way over my head on this. I did a Davlik Wipe and a Factory Reset but there is something still not right. I did both a Dalvik wipe and Factory reset last night before bed. I did not touch it once complete but on a regular basis I get pop ups about Android System stopped working or UC News. I cannot get rid of either of these on my tablet.
Any idea what I can do?
Now that you have the BOOTLOADER unlocked next step is to ROOT the TF201, I used MOTOCHOPPER. Check out this thread;
https://forum.xda-developers.com/showthread.php?t=2230763
NP
That worked. I was able to Root my device without issue. Actually that was a great tool. Nice and easy to work with.
So here is my next stop. What ROM do I pick? I was looking at 6.x or 7. It looks like KatKiss is pretty good but I am not sure.
https://forum.xda-developers.com/transformer-prime/development/rom-katkiss-nougat-t3459313
No reason not to go straight to 7.1.2 just make sure you flash the correct TWRP.
NP
And this is the part I don't understand. I have downloaded TWRP and ROM Manager from ClockWork. I have copied the ZIP folder to my SD card and placed it in my TF201. From here I don't know what to do.
I follow the instruction from 5.1 here: https://forum.xda-developers.com/transformer-prime/development/rom-katkiss-5-1-tf201-22-t3080892
using the 7.1 files from here: https://forum.xda-developers.com/transformer-prime/development/rom-katkiss-nougat-t3459313
NP
Yeah. So now the tablet is stuck at the Asus Splash Screen. Been for the last 48 hours or so. I completely drained the battery but when I filled it back up, no difference.
Can you get into the TWRP recovery console?
NP
Nope. I can't do anything with it. I have power cycled it many times over holding different buttons but no difference.
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