Can someone help me with changing my build.prop so the update picks it up as an upgrade and not an older version. I have tried over and over again and I can't get it. I can't get it to go to the stock bootloader because I had my bootloader unlocked and it was rooted then I went from 4.5.3 to 4.5.4 with the new google play services working. I then upgraded to the 5.2.0 preview and now I can't get to the recovery at all. Please help
junglistknot said:
Can someone help me with changing my build.prop so the update picks it up as an upgrade and not an older version. I have tried over and over again and I can't get it. I can't get it to go to the stock bootloader because I had my bootloader unlocked and it was rooted then I went from 4.5.3 to 4.5.4 with the new google play services working. I then upgraded to the 5.2.0 preview and now I can't get to the recovery at all. Please help
Click to expand...
Click to collapse
Am I missing something, or did you get root under 5.2.0 ? Only with root you could edit your build.prop file.
The boot sequence is tee1->UBOOT->{recovery,kernel}. Right now you have TWRP sitting in recovery, and 5.2.0 UBOOT will not boot it. On the other hand, I think sideloading works via booting into kernel. So you should be fine then. Just follow the sideloading instructions precisely from the original downgrade thread.
bibikalka said:
Am I missing something, or did you get root under 5.2.0 ? Only with root you could edit your build.prop file.
The boot sequence is tee1->UBOOT->{recovery,kernel}. Right now you have TWRP sitting in recovery, and 5.2.0 UBOOT will not boot it. On the other hand, I think sideloading works via booting into kernel. So you should be fine then. Just follow the sideloading instructions precisely from the original downgrade thread.
Click to expand...
Click to collapse
I do not have root in 5.2.0 I wish I did. If you can help me sideload I can get it back to 4.5.3 that is my problem right now.
junglistknot said:
I do not have root in 5.2.0 I wish I did. If you can help me sideload I can get it back to 4.5.3 that is my problem right now.
Click to expand...
Click to collapse
My thought was to change the build.prop of the update zip and rezip it and then try to downgrade with that zip
junglistknot said:
My thought was to change the build.prop of the update zip and rezip it and then try to downgrade with that zip
Click to expand...
Click to collapse
The update file has to be signed by Amazon, so you repackaging it won't work. Why cannot you follow these instructions to downgrade :
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
?
bibikalka said:
The update file has to be signed by Amazon, so you repackaging it won't work. Why cannot you follow these instructions to downgrade :
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
?
Click to expand...
Click to collapse
It does not boot into the stock recovery or any recovery for that matter.
I would like to try to flash the stock recovery.img from the 5.2.0 update via fastboot but I can't seem to find it anywhere. Does anyone have a copy of this img?
Edit: Well I was able to get in touch with Amazon and they made me give them my DSN of my device and they will send an update to revert the device back to Fire OS 4. It says I need to wait at least 48 hours for the update so I will report back after it is sent and let everyone know how it goes.
Related
Help.
So, my boss asks me to root his thunderbolt, so I do. Then, he goes and tries to install an OTA update on the thunderbolt and wonders why it won't work. I get into work this morning and he says, "I need you to unroot my phone so I can install OTA updates"???
I'm very confused, but hey, he wants it unrooted. Problem is, I can pull the battery, startup like normal, boot into the rooted OS and immediately the thing shuts down and tries to install the OTA update he installed.
This results in the android guy and the triangle with an exclamation point in it showing and I can't go any further.
ADB DOES see the device when I do adb devices.
How do I push the stock ROM back on to the phone and have it update that back to stock?
Help.
WHY he wants the phone unrooted or even decided to update it with an OTA ROM is beyond me.
Please and thank you in advance.
Wrong section but if the bootloader still has s-off, I would install custom recovery again and flash the rooted ota rom.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1009423
You should be able to flash the latest ota by booting into bootloader. If adb is working then I believe you can...
adb reboot bootloader
here is a link to the file you will need with instructions...
how to flash the latest ota
1. I realized too late it was the wrong section, apologies.
2. I don't need to flash a ROOTED ROM, he wants this device back to being stock UNROOTED.
Can I, using recovery, flash PG05IMG_MR1_no_hboot.zip over what is there now and go back to unroot and stock?
I use an Evo and can do almost anything on that, but the thunderbolt is a little new to me. Not my device, shouldn't have offered to root it for my boss without knowing he was going to try to install an OTA update.
Any help with unrooting and reflashing the Stock OTA would be very helpful.
It's one of the big issues with running stock rooted. Nothing stopping it from trying to update itself and screw the pooch
Honestly, if he wants OTAs just for the latest goodies/stability and battery improvements he'd be better off with something cooked... Just my opinion though
Sent from my ADR6400L using XDA App
sanjsrik said:
2. I don't need to flash a ROOTED ROM, he wants this device back to being stock UNROOTED.
Any help with unrooting and reflashing the Stock OTA would be very helpful.
Click to expand...
Click to collapse
Hmmm - not sure why you didn't just use the link that I provided? I will quote from there...
Code:
Using this RUU will wipe all data on your device!
Please make a backup of all sensitive data before
proceeding. Similarly, you will [B]LOOSE ROOT IF
YOU FLASH THIS[/B]. It is unclear right now
whether or not this version is easily rootable.
[B]PROCEED WITH CAUTION[/B]
This is not a link to a rooted rom.
thepolishguy said:
Hmmm - not sure why you didn't just use the link that I provided? I will quote from there...
Code:
Using this RUU will wipe all data on your device!
Please make a backup of all sensitive data before
proceeding. Similarly, you will [B]LOOSE ROOT IF
YOU FLASH THIS[/B]. It is unclear right now
whether or not this version is easily rootable.
[B]PROCEED WITH CAUTION[/B]
This is not a link to a rooted rom. It is a link to the full unrooted ota ruu that has been put in a flashable (from hboot) PG05IMG.zip.
Click to expand...
Click to collapse
Update: Worked like a charm.
Thanks, polishguy, that wasn't clear originally, will follow your link. Much appreciated.
sanjsrik said:
Thanks, polishguy, that wasn't clear originally, will follow your link. Much appreciated.
Click to expand...
Click to collapse
No problem. It wasn't clear originally bc I am not sure how XDA views links to "this sort of file". As in a "Romeo Uniform Uniform"
thepolishguy said:
No problem. It wasn't clear originally bc I am not sure how XDA views links to "this sort of file". As in a "Romeo Uniform Uniform"
Click to expand...
Click to collapse
I would guess it's fine considering there are an abundance of RUU links in the dev section.
Hello. I want to root my nexus 9 without installing any custom recovery. I want this because i want to receive google updates...
And sont suggest me about "install custom recovery and when you need flash the stock etc.)
Thanks in advance
Wrong forum. This is a dev forum, not Q&A. Rooting w/out custom recovery is possible with chainfire's autoroot flashable zips. But still you won't receive OTA updates b/c since Lollipop the validation process has changed and you need to be pure stock. This also includes the recovery iirc.
Moved to correct forum
Just root it. You don't need custom. Use the nexus tool kit
Sent from my Nexus 9 using XDA Free mobile app
giannisgt said:
Hello. I want to root my nexus 9 without installing any custom recovery. I want this because i want to receive google updates...
And sont suggest me about "install custom recovery and when you need flash the stock etc.)
Thanks in advance
Click to expand...
Click to collapse
brownog1 said:
Just root it. You don't need custom. Use the nexus tool kit
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
You will not receive OTA updates if you are rooted.
cam30era said:
You will not receive OTA updates if you are rooted.
Click to expand...
Click to collapse
Since when does rooting prevent OTA updates? Thats the first time I hear that.
On my N10 I always booted only into TWRP (fastboot boot twrp.img) and flashed from there the supersu.zip and still got OTAs without any issues.
I sold my N10 and my N9 is currently on the way to me so Im preparing everything to unlock and root it as soon as it arrives, thats why I am checking all those threads right now regarding root.
Well, I read only about this root injecting methode which doesnt sound very good to me and the nexus toolkit methode. Isnt it possible to boot into TWRP like I did before? Why shouldnt this work on the N9?
HansiHusten said:
Since when does rooting prevent OTA updates? Thats the first time I hear that.
On my N10 I always booted only into TWRP (fastboot boot twrp.img) and flashed from there the supersu.zip and still got OTAs without any issues.
I sold my N10 and my N9 is currently on the way to me so Im preparing everything to unlock and root it as soon as it arrives, thats why I am checking all those threads right now regarding root.
Well, I read only about this root injecting methode which doesnt sound very good to me and the nexus toolkit methode. Isnt it possible to boot into TWRP like I did before? Why shouldnt this work on the N9?
Click to expand...
Click to collapse
My bad. I should have said you will not be able to install OTA if you are rooted. The install script checks system files and if anything has been modified, it aborts installation. Your better option is to fastboot flash the Google factory image.
So what is the current working root methode for 5.1.1 without losing OTA or flashing any recovery?
This injecting thing, nexus toolkit or another way?
--edit--
seems like CF-Auto-Root (special version for the N9) works also? Im right now having 40 windows open in chrome, trying to find the best way...
Question is, does it still work for 5.1.1?
Again: Why should not boot into TWRP and then flash the supersu zip not work? Any issues with that?
Please share your experience. Thanks
HansiHusten said:
So what is the current working root methode for 5.1.1 without losing OTA or flashing any recovery?
This injecting thing, nexus toolkit or another way?
--edit--
seems like CF-Auto-Root (special version for the N9) works also? Im right now having 40 windows open in chrome, trying to find the best way...
Question is, does it still work for 5.1.1?
Again: Why should not boot into TWRP and then flash the supersu zip not work? Any issues with that?
Please share your experience. Thanks
Click to expand...
Click to collapse
It's a Nexus device. The easiest root method is to fastboot flash TWRP, the download SuperSU and flash it in recovery. Link here > http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
cam30era said:
It's a Nexus device. The easiest root method is to fastboot flash TWRP, the download SuperSU and flash it in recovery. Link here > http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
Click to expand...
Click to collapse
Alright, so the 'usual' way works as always, thanks for clearing this up. Was wondering if there were still some issues with rooting the N9.
So you suggest the beta version of supersu, will give a try first to the stable one, if this doesnt work ill try the beta.
Thanks m8
HansiHusten said:
Alright, so the 'usual' way works as always, thanks for clearing this up. Was wondering if there were still some issues with rooting the N9.
So you suggest the beta version of supersu, will give a try first to the stable one, if this doesnt work ill try the beta.
Thanks m8
Click to expand...
Click to collapse
Stable should work for Lollipop. Beta necessary for M. And beta works fine on Lollipop, too, FWIW.
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
If you have this exact problem, unbrick instructions here:
Try using Phone Flash Tool from the Dell site, and this zip:
https://mega.co.nz/#!Vgw1CTYT!y1_tSTCMmzrhJSQy0lxwY59iyRhdJovC-IDMF25PB4k
It's the new boot firmware binaries packed in the developer edition firmware zip with the xml changed to point to the new files.
For the flashing process of this zip, start with the tablet completely off and disconnected, then in Phone Flash Tool, load the zip file, click "Start to flash" (the button near the bottom should be blue/clickable), then once it's counting attempts (attempt #0, attempt #1, etc.) then connect USB. It should proceed to flash.
Click to expand...
Click to collapse
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
xBIGREDDx said:
I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
What is the process to unroot on our device?
Install es file explorer or root explorer.
Grant root access to the app.
in es you need to enable root explorer in the settings menu.
Go to
Code:
/system/bin
delete su (mine was not locate in here)
/system/xbin
delete su (mine was here)
/system/app/Superuser.apk delete this
SuperSu has a selection of uninstall options in the app's menus.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
I've applied plenty of OTAs in the past to other devices on top of rooted systems, and never had a problem as bad as bootlooping.
(Not saying it's not my fault, as I knew there was a risk, I guess I was just running on a series of good luck, or maybe other companies write better OTA pre-checking features.)
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
kage69 said:
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
Click to expand...
Click to collapse
It's hard to say, as lollipop was just released, only you guys with lollipop can test and see.
Neither SDC nor myself have lollipop so we can't test.
sent from my kingSing T1 via taptalk
On mine, I forgot to un-root with no issues, but it defaults to encrypting the tablet and now I can't re-root.
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
old root method dont work :crying:
kage69 said:
old root method dont work :crying:
Click to expand...
Click to collapse
Well you tried, did you get an error? Can you give more details?
sent from my kingSing T1 via taptalk
xBIGREDDx said:
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
ely105 said:
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
Click to expand...
Click to collapse
@kage69 says no, only you guys with lollipop can confirm or deny if root works or not.
sent from my kingSing T1 via taptalk
the tool flashes temp cwm but the tab dont boot to recovery
stays in bootloader where you can choose boot normal, power down and recovery
choosing recovery boots to stock recovery
there were errors while flashing, ill post them tomorrow
reading a book in bed on my lollipopped tab now
hope we can root it again, need that for customizations and airaudio
see u tomorrow
So how were you able to flash after bootlooping the first time when you tried to update with root? I cannot get into the bootloader or anything :silly:
Does any one have the ota so I can patch the stock firmware to investigate rooting it?
might be stored in cache i think
cant get to that without root
kage69 said:
might be stored in cache i think
cant get to that without root
Click to expand...
Click to collapse
Yeah I we hoping someone captured it before updating
xBIGREDDx said:
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
Click to expand...
Click to collapse
Exactly which binaries did you flash back? In the zip I see:
dnx_fwr_ann_a0-mofd_v1.bin
dnx_fwr_ann_a0-mofd_v1-DBG.bin
dnx_fwr_blackburn_preqs_preqs.bin
dnx_fwr_blackburn_qs_qs.bin
dnx_fwr_preqs.bin
dnx_fwr_qs.bin
ifwi_ann_a0-mofd_v1.bin
ifwi_ann_a0-mofd_v1-DBG.bin
ifwi_preqs.bin
ifwi_qs.bin
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
Hi guys,
first of all I want to salut everybody here as I am completely new to the Android world and that's indeed the best resource online. Thanks for that.
Now my big problem. As from the title, I downgrade my Fire HD 6 (4th gen) to 4.5.3 with adb sideload to root it with kingroot and everything went fine. I have then installed TWRP and everything went fine. I have then used TWRP to go back to 5.3.1 and I lost root and recovery. I managed to gain my root privileges back but as for the recovery not a chance. I tried to install TWRP again with dd from adb shell (as I can su) but once again nothing. Checking with fastback getval all, I do have a locked bootload:
Is this the reason why TWRP doesn't run anymore?
If yes, how can I unlock it back?
Is this what's meant with boot loader loop?
Thank you all in advance!
Edit 1:
maybe cuber.py may help but I can't find this file.
Edit 2:
ok found the tools here https://forum.xda-developers.com/kindle-fire-hdx/development/tools-create-unlock-img-fix-boot-img-t3050689
Edit 3:
I tried with cuber.py but the tool can't sign the img because it's not ANDROID. That's what it says. Now I am really stuck. Help please!
LM
I was in the exact same situation, so maybe I can offer some insight. I also have an HD 6 running 5.3.1 that I have downgraded to get root then upgraded a few times. Let me say that I am still learning too, and am by no means an expert but I can try to help.
As far as losing root, i'm not sure as that never happened to me. Did you flash the most up-to date SuperSu with TWRP or did you just answer yes when TWRP prompted you if you wanted root privileges? Flashing a SuperSu through TWRP will give you the SuperSu icon on your home screen once you upgrade back to 5.3.1, whereas just letting TWRP grant root access won't. You will still have root, but without the icon there's no direct control over it (at least not that I could find) so it's still there, just hidden.
My TWRP also replaced by the stock recovery upon updating back to 5.3.1. As far as I know, this is unavoidable. I believe it's as you suspect and is due to the 5.3.1 bootloader being locked. This would also explain why the process for rooting 5.3.1 is so involved as opposed to just using something like Kingroot. I also don't think there's anyone still doing active development on the HD 6 / HD 7.
If you really want to have both root and TWRP, you could try downgrading to an older OS that still has the feel of 5.3.1. I'm not sure about any other versions, but 5.1.1 is rootable via Kingroot (which should mean that it has an unlocked bootloader) and has the same exact UI as 5.3.1. So if you're feeling adventurous try downgrading to 4.5.3, installing TWRP, and upgrading to 5.1.1 instead of 5.3.1 (just be sure to block automatic updates!) and see if TWRP is still active. If so, root with Kingroot and you're good. If you still don't have TWRP, at least you're no worse off than you were.
If you do try this, please post your results here. I might try this myself. I am currently running stock. As I said, I went through the process a few times. For some reason SuperSu was causing erratic behavior in some of my apps and when I tried to switch my SU app to kingroot I lost root completely. I really didn't care about root enough to repeat the whole process again, but if I could keep TWRP it might be worth it. Anyway, good luck.
P.S. You may need to try rooting with Kingroot several times for it to work. I know for a fact that it can root 5.1.1 since I've done it on my own HD 6 when I was running 5.1.1. I'm not sure why it fails, but keep trying and eventually it will get root access. You may have to try 6 or 7 times but eventually it will work.
I went back and re-read this thread more carefully:https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 and it turns out that TWRP doesn't play well with any 5.X.X bootloaders. Oh well, I was kind of hoping my idea would work. It turns out that you can use TWRP on your current rooted 5.3.1, but only on a temporary basis. Refer to the above thread post #2 for instructions. Basically, you put the correct 5.3.1 bootloader on your device then run AutoTWRP which will flash 4.5.3 bootloaders and TWRP for you. Reboot into recovery and you have your TWRP. You can then do whatever you want. The downside is that since you are running a 4.5.3 bootloader you can't get back into your OS, only TWRP. And once you flash your 5.3.1 bootloader to get back into your OS, TWRP no longer works. I know it's a pain in the arse having to connect to a PC and run a batch file every time you need to use TWRP, but at least it's a sort of workaround.