What steps should be taken to Un-root the hdx 7 and reset to stock after rooting with the latest Towel root toolbox and firmware?
rootnooby said:
What steps should be taken to Un-root the hdx 7 and reset to stock after rooting with the latest Towel root toolbox and firmware?
Click to expand...
Click to collapse
To do that, you must uninstall the Towelroot app (shouldn't be too hard) then, to finish it off, try running these commands in an adb shell:
Code:
su
mount -o rw,remount /system
rm /system/bin/su
rm /system/xbin/su
mount -o ro,remount /system
exit
You are now unrooted!
Sent from my Nexus 7 using Tapatalk
rootnooby said:
What steps should be taken to Un-root the hdx 7 and reset to stock after rooting with the latest Towel root toolbox and firmware?
Click to expand...
Click to collapse
in SuperSu > settings > fullunroot
and it will unroot your Kindle
and then settings > device > restore factory settings
blade22 said:
in SuperSu > settings > fullunroot
and it will unroot your Kindle
and then settings > device > restore factory settings
Click to expand...
Click to collapse
He never said he was using SuperSU. And I wouldn't recommend the factory reset as those have caused many people issues around here.
Sent from my iPod touch using Tapatalk
r3pwn said:
He never said he was using SuperSU. And I wouldn't recommend the factory reset as those have caused many people issues around here.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
i have done the same steps and factory reset..faced no Issues.
and may be people facing issues might not have uninstalled xposed module and xposed framework
r3pwn said:
He never said he was using SuperSU. And I wouldn't recommend the factory reset as those have caused many people issues around here.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I factory reset my 8.9 after rooting 2 days ago. No issues at all except YOU MUST ALLOW OTA UPDATES BEFORE YOU RESET OR IT WILL NOT ALLOW YOU TO REGISTER AND YOU WILL KEEP POPPING BACK TO THE LAGUAGE SETTING AT RANDOM TIMES, I had a hassle re enabling ota after the reset, very annoying. As to Xposed .. I would MAKE SURE you uninstall xposed modules and xposed framework before resetting. I would also recommend putting back to rights ANY changes you make in build prop as well as custom disables of the nav bar. I have ran into problems with other tablets when resetting after nav bar changes.
conan1600 said:
I factory reset my 8.9 after rooting 2 days ago. No issues at all except YOU MUST ALLOW OTA UPDATES BEFORE YOU RESET OR IT WILL NOT ALLOW YOU TO REGISTER AND YOU WILL KEEP POPPING BACK TO THE LAGUAGE SETTING AT RANDOM TIMES, I had a hassle re enabling ota after the reset, very annoying. As to Xposed .. I would MAKE SURE you uninstall xposed modules and xposed framework before resetting. I would also recommend putting back to rights ANY changes you make in build prop as well as custom disables of the nav bar. I have ran into problems with other tablets when resetting after nav bar changes.
Click to expand...
Click to collapse
Thanks for all the great feedback. I should have provided more detail to start. I have a follow up question/clarification. This is what did:
1. Run Towel root - success
2. Followed directions to block ota updates and install supersu. - success
3. With root confirmed, Installed exposed frame work and module from here: http://forum.xda-developers.com/showthread.php?t=2618158 (to get play store and other google apps). - success
4. Activate exposed module and update. - success
5. Installed hdxposed.Apk, enabled it, Rebooted, and play store worked. - success
6. In any order, installed the files from the link. - success
Install play services
Install framework
Install Google account manager
7. Overall, all worked well.
Question:
What is the best way to undo everything I did?
Enable OTA updates?
Update to the latest firmware (basically to get prime music and fix wifi issues I'm having)?
Re-root?
conan1600 said:
I factory reset my 8.9 after rooting 2 days ago. No issues at all except YOU MUST ALLOW OTA UPDATES BEFORE YOU RESET OR IT WILL NOT ALLOW YOU TO REGISTER AND YOU WILL KEEP POPPING BACK TO THE LAGUAGE SETTING AT RANDOM TIMES, I had a hassle re enabling ota after the reset, very annoying. As to Xposed .. I would MAKE SURE you uninstall xposed modules and xposed framework before resetting. I would also recommend putting back to rights ANY changes you make in build prop as well as custom disables of the nav bar. I have ran into problems with other tablets when resetting after nav bar changes.
Click to expand...
Click to collapse
I ran into the problem with the language repeatedly popping back upbecaus I didn't first re-enabe the OTAs. How did you fix thisissue please? Thanks or you help in advance.
brooklynstar220 said:
I ran into the problem with the language repeatedly popping back upbecaus I didn't first re-enabe the OTAs. How did you fix thisissue please? Thanks or you help in advance.
Click to expand...
Click to collapse
You need to reverse the method originally used to block OTAs of which there are several. What version of FireOS are you on?
Davey126 said:
You need to reverse the method originally used to block OTAs of which there are several. What version of FireOS are you on?
Click to expand...
Click to collapse
I am version 13.3.2.4. The problem I am running into at this point is that USB debugging is not working. I have even dowloaded seperate debugging apps and they fail to work giving me errors that it has stopped. I am assuming there is something wrong in that script at this point. Is there any way to fix it? I disabled the OTA updates with KFHDX Toolkit v0.95.
Also I can root and unroot with no problem but can't flash anything because even though it says safe strap is installed it won't boot into recovery.
brooklynstar220 said:
I am version 13.3.2.4. The problem I am running into at this point is that USB debugging is not working. I have even dowloaded seperate debugging apps and they fail to work giving me errors that it has stopped. I am assuming there is something wrong in that script at this point. Is there any way to fix it? I disabled the OTA updates with KFHDX Toolkit v0.95.
Also I can root and unroot with no problem but can't flash anything because even though it says safe strap is installed it won't boot into recovery.
Click to expand...
Click to collapse
Sounds like you have some deeper problems with the ROM on your device. In your shoes I would install Safestrap v3 (not v4) followed by the SS compatible version of Nexus. This will also address the Google Play/Services issues. Others may suggest unlocking your bootloader. I wouldn't go there given current issues ... even if you could somehow reenable OTA. High risk imo.
Davey126 said:
Sounds like you have some deeper problems with the ROM on your device. In your shoes I would install Safestrap v3 (not v4) followed by the SS compatible version of Nexus. This will also address the Google Play/Services issues. Others may suggest unlocking your bootloader. I wouldn't go there given current issues ... even if you could somehow reenable OTA. High risk imo.
Click to expand...
Click to collapse
I was able to get that version of Safestrap installed and was able to flash roms again but ADB is still not connecting when attached to the computer. Do you think a nanroid restore from my original setup could help fix this?
Davey126 said:
Sounds like you have some deeper problems with the ROM on your device. In your shoes I would install Safestrap v3 (not v4) followed by the SS compatible version of Nexus. This will also address the Google Play/Services issues. Others may suggest unlocking your bootloader. I wouldn't go there given current issues ... even if you could somehow reenable OTA. High risk imo.
Click to expand...
Click to collapse
Thank you for your help with this. What is crazy but was probably a driver issue the whole time, I udated my laptop to Windows 10 and somehing told me to try it again and it worked immediately with the Toolkit and re-enabled the OTA updates. Thanks again.
Related
Hi Guys,
i just got my HDX (7" - Thor) this week and was trying to get the Thor GAPPS ROM by Cpasjuste to work. Having found nothing specific for FireOS version 13.3.2.1 i went ahead and tried my luck with the "old" version of the ROM (thor-gapps-13.3.0.0-v2.zip).
Unfortunately i couldn't get it to work and am back to factory defaults. Which is good, since it's not a brick. So now i'm trying to play it safe and wait for the developer's magic to happen
i'm eager to play around with the device, but don't want to risk losing my chances of running a custom ROM in the future. i already own the first Kindle Fire and wouldn't want to miss the near stock Android on that.
So, finally, my question:
If i use the HDX Toolkit to root and disable OTA updates, i assume it will be safe to use the device until the bootloader gets unlocked or some other magic happens. Am i correct with this assumption?
Edit1 [2014-07-09 - 21:21]: sorry for the soonish edit, but i just prepared the device in case someone confirms, that it is more or less safe to use it with OTA disabled.
Upon disabling OTA, i get a few rows of "killed" messages in the HDX toolkit. When i first disabled OTA i saw that some services were being disabled or uninstalled. Is "killed" a confirmation that the components are already killed? i have already factory resetted, as i cannot find a way to do a full wipe. The result is the same.
Thanks in advance.
umm
kobayashimaru said:
Hi Guys,
i just got my HDX (7" - Thor) this week and was trying to get the Thor GAPPS ROM by Cpasjuste to work. Having found nothing specific for FireOS version 13.3.2.1 i went ahead and tried my luck with the "old" version of the ROM (thor-gapps-13.3.0.0-v2.zip).
Unfortunately i couldn't get it to work and am back to factory defaults. Which is good, since it's not a brick. So now i'm trying to play it safe and wait for the developer's magic to happen
i'm eager to play around with the device, but don't want to risk losing my chances of running a custom ROM in the future. i already own the first Kindle Fire and wouldn't want to miss the near stock Android on that.
So, finally, my question:
If i use the HDX Toolkit to root and disable OTA updates, i assume it will be safe to use the device until the bootloader gets unlocked or some other magic happens. Am i correct with this assumption?
Edit1 [2014-07-09 - 21:21]: sorry for the soonish edit, but i just prepared the device in case someone confirms, that it is more or less safe to use it with OTA disabled.
Upon disabling OTA, i get a few rows of "killed" messages in the HDX toolkit. When i first disabled OTA i saw that some services were being disabled or uninstalled. Is "killed" a confirmation that the components are already killed? i have already factory resetted, as i cannot find a way to do a full wipe. The result is the same.
Thanks in advance.
Click to expand...
Click to collapse
Never factory reset stock slot if you have run the OTA blocker the utility also has a eNAble option for the OTA blocker always uninstall xposed framework and modules before factory reset also .. Always returning the unit to as close to factory as you can before doing a factory reset in factory recovery. Otherwise you risk breaking your device.. If you look around you will find ways to do a manual update to a slightly newer firmware just not the newest and your ROMs will work.
jimyv said:
Never factory reset stock slot if you have run the OTA blocker the utility also has a eNAble option for the OTA blocker always uninstall xposed framework and modules before factory reset also .. Always returning the unit to as close to factory as you can before doing a factory reset in factory recovery. Otherwise you risk breaking your device.. If you look around you will find ways to do a manual update to a slightly newer firmware just not the newest and your ROMs will work.
Click to expand...
Click to collapse
Thanks. i will look for the update method you mentioned. i might have already read it on Friday, but didn't think it would apply to my version.
i have removed everything related to modding before factory resetting from the FireOS settings. At that point, there was only safestrap left, which i uninstalled.
If i decided to stay on FireOS after all, until a better method comes up, is there a way for me to check, if the OTA blocker is actually working?
lol
kobayashimaru said:
Thanks. i will look for the update method you mentioned. i might have already read it on Friday, but didn't think it would apply to my version.
i have removed everything related to modding before factory resetting from the FireOS settings. At that point, there was only safestrap left, which i uninstalled.
If i decided to stay on FireOS after all, until a better method comes up, is there a way for me to check, if the OTA blocker is actually working?
Click to expand...
Click to collapse
It works. Just open settings go device,system updates ,check for updates, should fail immediately..if it stars to dl. kill wifi
jimyv said:
It works. Just open settings go device,system updates ,check for updates, should fail immediately..if it stars to dl. kill wifi
Click to expand...
Click to collapse
Thanks, i'm always scared with such new devices.
"Update failed". Perfect.
i got the Thor GAPPS working by now, so i'll try using that for now.
http://www.droid-life.com/2014/12/05/lg-g3-on-verizon-gets-advanced-calling-1-0-volte-in-update/
The update mainly brings Advanced Calling 1.0 and updates to some LG apps.
It looks like Advanced Calling also needs to be enabled on your account.
http://www.verizonwireless.com/supp...Turning Advanced Calling On/Off on Your Phone
Personally, I'd like to know if someone who is stock/rooted with no system files changed can accept the update and keep root. If anyone gets it and tests that, please report back. Also, include whether or not SuperSU is in survival mode.
With the previous update, I was stock/rooted with 1 system file that dealt with headphone volume changed. I had to restore the original version of that file, then the update completed and root was kept (without SuperSU survival mode being required).
I've done the check for updates on my phone, but nothing yet.
I've actually just accepted the update and I still have root. However it may appear to run slowly at the beginning, but eventually everything came back. So if you're worried a root app won't work, then wait around 3 to 5 minutes and everything should be working again and back to normal as well. I was rooted from 10C and now I'm on the latest update.
david_hume said:
I've actually just accepted the update and I still have root. However it may appear to run slowly at the beginning, but eventually everything came back. So if you're worried a root app won't work, then wait around 3 to 5 minutes and everything should be working again and back to normal as well. I was rooted from 10C and now I'm on the latest update.
Click to expand...
Click to collapse
I see the update available to be pulled now.
SuperSU in survival mode or not? I'm on 11C, but I wouldn't think going from 10C/rooted to 12B or 11C/rooted to 12B would make a difference. I guess I'll give it a go here as soon as I can restore that system file.
lexluthor said:
I see the update available to be pulled now.
SuperSU in survival mode or not? I'm on 11C, but I wouldn't think going from 10C/rooted to 12B or 11C/rooted to 12B would make a difference. I guess I'll give it a go here as soon as I can restore that system file.
Click to expand...
Click to collapse
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
david_hume said:
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
Click to expand...
Click to collapse
I don't think survival mode is required. It wasn't went I went from 10C to 11C.
I'm holding off on this one. I bounce between 4g and 3g a lot and I heard that if you start a call on 4g and it drops to 3g, you will drop the call. Not sure if this is true, hope someone can chime in
hawkswind1 said:
I'm holding off on this one. I bounce between 4g and 3g a lot and I heard that if you start a call on 4g and it drops to 3g, you will drop the call. Not sure if this is true, hope someone can chime in
Click to expand...
Click to collapse
From what I read somewhere, I think you can turn it off if you don't like it. My update completed, it's optimizing apps now. Will post once I confirm I've kept root (or not).
I just updated mine. I upgraded from 11C and still have root. I put my SU in survival mode just in case, but I'm not sure if that was necessary or not.
Also, for those that are worried about being stuck on VoLTE. There's a new entry in the Settings menu that lets you turn the "Advanced Calling" on/off at will.
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
If someone could pm me with a link to a system partition dump (or kdz) it would be appreciated, thanks.
EDIT: nvm, got it.
j0hnnyn said:
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
Click to expand...
Click to collapse
I'm back up. I had to restore the sound system file, do the update, then put my custom file back. My frozen apps stayed frozen. I had to re-install xposed framework (didn't have to uninstall it first) and I still have root (I did not have SuperSU in survival mode). All in all pretty easy. Yes, I know the update could have included a shut out of root, but it didn't (for me).
You'll probably have to restore those system apps if you did any type of "hack" uninstall (as opposed through some sort of regular OS menu).
Other than that, you should be good. Just re-install xposed framework through the xposed installer that's still there after the update.
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
xdabbeb said:
If someone could pm me with a link to a system partition dump (or kdz) it would be appreciated, thanks.
Click to expand...
Click to collapse
I 2nd this!
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
taihard said:
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Same thing here. I hope there is something else other than using LG Flashtool to download the stock firmware
taihard said:
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Here's another thing i'm noticing... before, I downloaded a couple UI themes to change the nav buttons at the bottom through g3 tweaksbox and after removing g3 tweaksbox, the buttons changed to stock on the home screen but if I go in to settings or any other app it still shows the "LG" logo as my "home" button... maybe some left behind changes that are preventing update?
lexluthor said:
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
Click to expand...
Click to collapse
I did this earlier, it shouldn't be difficult for you, assuming your admin isn't a jerk of course. It's a feature that needs to be checked on your account, but it's also a free feature, so I'm not sure what excuse they'd have for denying your request.
taihard said:
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Can't help you with your error code, but I can say that my rooted phone also reported as "modified" status before applying the OTA and it still does afterwards as well.
Please help
Phone is rooted and has oem rom ... and xposed framework for tweakbox philz recovery mode just keeps loading after i treid the update what can i do i cant get back into my phone at all please help
Also tried resotring a backup i made yesterday before any of this and its still doing the same thing please please please helpl
j0hnnyn said:
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
Click to expand...
Click to collapse
No. Xposed will block all OTA and removing system Apps will also.
david_hume said:
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
Click to expand...
Click to collapse
lexluthor said:
I'm back up. I had to restore the sound system file, do the update, then put my custom file back. My frozen apps stayed frozen. I had to re-install xposed framework (didn't have to uninstall it first) and I still have root (I did not have SuperSU in survival mode). All in all pretty easy. Yes, I know the update could have included a shut out of root, but it didn't (for me).
You'll probably have to restore those system apps if you did any type of "hack" uninstall (as opposed through some sort of regular OS menu).
Other than that, you should be good. Just re-install xposed framework through the xposed installer that's still there after the update.
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
Click to expand...
Click to collapse
can one of you guys (or anyone else who took the update) use this code to pull the modem for us please?
(use terminal emulator)
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem-12B.img
Thanks!!
tech_head said:
No. Xposed will block all OTA and removing system Apps will also.
Click to expand...
Click to collapse
I had Xposed installed and it updated no problem. But I would think the system apps would make it fail though.
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
jeraldjunkmail said:
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
Click to expand...
Click to collapse
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Visa Declined said:
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Click to expand...
Click to collapse
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
well at the moment that doesn't effect the GPe, and may never. There will have to be a system image flashed to put the block device in a known state before the new way could ever be used, and if there is a system.img we can always flash that to get the OTA to work... no big deal I don't think.
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
What is Xposed? How would I check to see if it has affected my device? Only thing I did was Towelroot and running SuperSU. I may have done something to allow writing to the external SD card, but forget how I did that. I was intentionally trying to keep this phone basically stock so that it would easily update to Lolipop. I did a Titanium backup to the externalSD card and reset it to factory and the OTA update still fails though. I assume this was due to the fact that I rooted it. The bootloader is still unmodified, secureboot is still green - yes, lock state is locked. Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
jeraldjunkmail said:
I may have done something to allow writing to the external SD card, but forget how I did that.
Click to expand...
Click to collapse
jeraldjunkmail said:
Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
Click to expand...
Click to collapse
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Visa Declined said:
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Click to expand...
Click to collapse
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
jeraldjunkmail said:
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
Click to expand...
Click to collapse
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
blueether said:
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
Click to expand...
Click to collapse
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
jeraldjunkmail said:
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
Click to expand...
Click to collapse
That's fine and I take no offence at you not wanting to unlock the BL.
I haven't tried the full unroot option in supersu so I'm not sure what the outcome is. One of the other GPe users care to comment?
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
jeraldjunkmail said:
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
Click to expand...
Click to collapse
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
blueether said:
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
Click to expand...
Click to collapse
Can you point me inthe right direction for instructions on this process? Thanks!
Visa Declined said:
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
Click to expand...
Click to collapse
Your post is two years ago but i think you can help me,there is a new update for my phone and i am rooted i also have xposed installed so this mean i cannot update my sytem? Do i need to uninstall xposed? Im on stock rom and with TWRP recovery it would be a big help if you reply thanks.
Hi,
I bought a Nexus 5 on amazon, and when it came in, it went through the setup process as if it were a brand new phone. However, as soon as it got to the home page, i noticed that SuperSU was installed, and it was in the app drawer. I did not want a rooted phone, so i installed root checker to see if the phone was rooted. Root checker said it was not rooted, so i thought i was safe to uninstall superSU. But when I launch superSU, it gives me a popup that says that there is no supersu binary installed or something, and i can't access the app further than that. Is there any way to uninstall it otherwise? I also went to the play store to uninstall it but it just says that it will uninstall all updates. Also, if i install marshmallow, will that fix the problem? i heard that the OTA update for M will remove root, supersu, etc.
thanks
EvilLemon said:
Hi,
I bought a Nexus 5 on amazon, and when it came in, it went through the setup process as if it were a brand new phone. However, as soon as it got to the home page, i noticed that SuperSU was installed, and it was in the app drawer. I did not want a rooted phone, so i installed root checker to see if the phone was rooted. Root checker said it was not rooted, so i thought i was safe to uninstall superSU. But when I launch superSU, it gives me a popup that says that there is no supersu binary installed or something, and i can't access the app further than that. Is there any way to uninstall it otherwise? I also went to the play store to uninstall it but it just says that it will uninstall all updates. Also, if i install marshmallow, will that fix the problem? i heard that the OTA update for M will remove root, supersu, etc.
thanks
Click to expand...
Click to collapse
did you try settings>apps>
is superSu listed in under downloaded tab?
sd_shadow said:
did you try settings>apps>
is superSu listed in under downloaded tab?
Click to expand...
Click to collapse
yes, it is listed there, and when i click on it, it gives me options to force stop it, uninstall updates, or disable it. But i heard that if i try to install OTA updates on the phone, it will stop halfway cause the updates now check for stuff like supersu
EvilLemon said:
yes, it is listed there, and when i click on it, it gives me options to force stop it, uninstall updates, or disable it.
Click to expand...
Click to collapse
If there is no option to uninstall, it is on the system partition, you will need to root to remove it, or better reinstall stock firmware.
the devices was rooted at some time and it was not unrooted correctly, I would not allow the device to update ota, because you just do not know if stock rom is complete.
But i heard that if i try to install OTA updates on the phone, it will stop halfway cause the updates now check for stuff like supersu
Click to expand...
Click to collapse
yes, that is possible.
see the nexus 5 forum http://forum.xda-developers.com/google-nexus-5
at look for how to restore stock rom
sd_shadow said:
If there is no option to uninstall, it is on the system partition, you will need to root to remove it, or better reinstall stock firmware.
the devices was rooted at some time and it was not unrooted correctly, I would not allow the device to update ota, because you just do not know if stock rom is complete.
yes, that is possible.
see the nexus 5 forum http://forum.xda-developers.com/google-nexus-5
at look for how to restore stock rom
Click to expand...
Click to collapse
I have decided to give back the phone, I really don't want that kinda risky device on me for the next 2 years... however, will i be able to factory reset it before i send it back? or will the phone mess up? (when i initially got the phone, i THINK it was factory reset because i had to go through the default android setup process) i just don't want the next owner to gain any of my information or anything even if i delete everything i have on it so far and disconnect my google account
EvilLemon said:
I have decided to give back the phone, I really don't want that kinda risky device on me for the next 2 years...
Click to expand...
Click to collapse
Yes, that is probably safest option
however, will i be able to factory reset it before i send it back? or will the phone mess up? (when i initially got the phone, i THINK it was factory reset because i had to go through the default android setup process) i just don't want the next owner to gain any of my information or anything even if i delete everything i have on it so far and disconnect my google account
Click to expand...
Click to collapse
factory reset should be safe.
flashing firmware, is what the seller should have done, before shipping
I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
DroidDogg said:
I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
Click to expand...
Click to collapse
Be happy 4.5.5.1 didn't take when SafeStrap recovery was installed; device would have bricked. Assume you used the Safestrap compatible variant of 4.5.2 (here). After flashing that (stock slot only; never use secondary slots in SS v4) reboot device and remove Safestrap recovery via SS app. Power down and boot into stock recovery via <power>+<vol-up> and perform a factory reset (you'll loose all apps/data). Reboot again and initialize FireOS. It should then accept OTA updates.
Be 100% sure Safestrap recovery is uninstalled prior to doing a factory reset.
Curious - why to you want 4.5.5.1? Offers no advantage over 4.5.2 if running custom ROMs. Nor will it automatically update to FireOS v5 as Amazon has no plans to release a v5 update for 3rd gen devices.
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
DroidDogg said:
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
Click to expand...
Click to collapse
DroidDogg said:
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
Click to expand...
Click to collapse
IDK - should work. You can try downloading the latest version of FireOS here; installation instructions here. Also verify OTA apk is installed and properly named (here).
It's likely 4.5.x is the terminal release of FireOS for 3rd gen devices; potential buyers will not be severely disadvantaged on 4.5.2.
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
As previously posted - IDK and I do not think anyone else does either. What I do know is every flash (some which appear questionable) presents another failure opportunity that could yield an unrecoverable device. Keep experimenting and posting results; others will learn from your efforts. Just recognize the risk and know when to say 'good enough'. Pushing from 4.5.2 to 4.5.5.1 buys you no additional capability/functionality/stability at this time.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
Do you checked if the DeviceSoftwareOTA.apk is there? (which @Davey126 mentioned above).
I was in the same situation and had to rename it back, which I'd renamed before as described in the OTA blocking tutorial. http://forum.xda-developers.com/showpost.php?p=59160158&postcount=1
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
mzk1 said:
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
Click to expand...
Click to collapse
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Davey126 said:
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Click to expand...
Click to collapse
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
mzk1 said:
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
Click to expand...
Click to collapse
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Davey126 said:
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Click to expand...
Click to collapse
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
mzk1 said:
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
Click to expand...
Click to collapse
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Davey126 said:
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Click to expand...
Click to collapse
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
mzk1 said:
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
Click to expand...
Click to collapse
Yep - that would be my choice too. Take note there are two Nexus builds, one for devices that have a 4.5.5.1 kernel, the other for older kernels. Try the former first as it as actively maintained and has a broader feature set. Links below:
old: http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-v4-0-1-t3125808
new: http://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931