[Q] Lost Dashboard - Fire HD 6 and 7 Q&A, Help & Troubleshooting

I tried tried to upgrade my Fire HD 7 to 4.5.4 from 4.5.3 and keep root, but for some reason I lost it. So I though I would try to upgrade to 5.0 again, but under system updates it says "Last update failed". Then tried to do a reset to Factory Defaults and that's when my dashboard disappeared. When I boot up, I open up into settings and can't get anywhere else. Adb still connects.
I have TWRP installed and tried to flash stock 4.5.4 but that update failed because the binary could not execute because the device name did not match.
I would like to reset to factory defaults, or be able to upgrade to 5.0. Any tips?

My issue with reflashing the OS in TWRP has been fixed. In the updater-script I had to change the name of the device from ariel_full to ariel_omni.

tocohl said:
My issue with reflashing the OS in TWRP has been fixed. In the updater-script I had to change the name of the device from ariel_full to ariel_omni.
Click to expand...
Click to collapse
im having the same issue but im not sure where to update the script. mind pointing me in the right direction?

Related

[Q] Un-root after Towel root

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.

OTA update won't install - status 7

My Nexus 9 is stock, un-rooted with an unlocked bootloader.
I have received the OTA update but when it reboots it gets part way through then shows "error" with and android on his back. I have downloaded the OTA file from AndroidPolice and tried flashing via adb sideload.
It attempts to verify the current system but then errors with the following message:
Package expects build fingerprint of google/volantis/flounder:5:/LRX21L/1546449:user/release-keys or google/volantis/flounder:5:/LRX21Q/1573789:user/release-keys; this device has google/volantis/flounder:L:/LFW73W/1491895:user/release-keys
Click to expand...
Click to collapse
Why have I got a different build?! Is there a different OTA that i need?
I have the same issue, any one any idea?
same here. tried factory reset just to eliminate didn't help
https://plus.google.com/110305043896789356373/posts/bHyo4UazRpH
As I have an unlocked bootloader i've just flashed the recovery from the factory image and then applied the OTA update (mostly to see if it would work, otherwise i'd have continued with factory image). It's booting up now. I guess Google will need to push a new OTA that updates from this version... a bit of a screw up though!

Panasonic DMC-CM1 Stagefright update fails

Today I received a notification about System updates on my Panasonic DMC-CM1 (5.0.2, 12.0274) and allowed the update to run. Now every time I reboot I am seeing a warning "System Updates" "Software Update Stopped, Please Try again". If I go to "About Phone" "System Updates" it says "Your phone is up-to-date" but it is still at 12.0274, it should be 12.0300.
I have also tried to install the update by downloading the .DAT file from the Panasonic website and copying it to the "Download" folder of my microSD, and updating from there. I get the same result.
Any ideas?
*bump*
Does anyone on XDA have any experience with the Panansonic CM1?
Same here. Are you rooted? — I reckoned that in my case root might be the culprit.
cybriks said:
Same here. Are you rooted? — I reckoned that in my case root might be the culprit.
Click to expand...
Click to collapse
I WAS rooted, but I unrooted with SuperSU. It makes no difference.
Exactly what I tried – to no avail.
Unrooting with SuperSU does not remove all changes done to the system...
---------- Post added at 02:31 PM ---------- Previous post was at 02:22 PM ----------
What I've tried this far:
unrooting through SuperSU -> nope
re-rooting, uninstallning xposed sdk, unrooting -> nope
re-rooting, re-enabling all services, unrooting -> nope
trying to flash the ealier update -> nope
---------- Post added at 02:46 PM ---------- Previous post was at 02:31 PM ----------
FlashFire gives me "/system/bin/app_process has unexpected content"
You have tried more than me. I tried reinstalling kingroot 4.5, rerooting then unrooting. Nope. This post on DPreview suggests that Developer setting is an issue. I've checked that, no difference for me.
Have you tried factory reset? I've not tried that yet because I haven't backed up this week.
JPCoetzee said:
You have tried more than me. I tried reinstalling kingroot 4.5, rerooting then unrooting. Nope. This post on DPreview suggests that Developer setting is an issue. I've checked that, no difference for me.
Have you tried factory reset? I've not tried that yet because I haven't backed up this week.
Click to expand...
Click to collapse
The "/system/bin/app_process has unexpected content" warning seems to be caused by changes made by Xposed. Uninstalling (by flashing the uninstaller with FlashFire) doesn't seem to do the trick, however.
cybriks said:
The "/system/bin/app_process has unexpected content" warning seems to be caused by changes made by Xposed. Uninstalling (by flashing the uninstaller with FlashFire) doesn't seem to do the trick, however.
Click to expand...
Click to collapse
The .DAT update files are zips. Maybe you could replace app_process32 with the one from 0P...0761_9274.DAT?
Have you tried factory reset?
Factory reset did not work.
However, I give you... *drumroll*... SUCCESS
Make sure you are rooted and that Xposed was properly uninstalled (by flashing the uninstaller with FlashFire)
Navigate with your file browser (I am using Solid Explorer) to /system/bin. (In the settings of Solid Explorer you have to enable display of the root folder)
Locate app_process32
Check whether you have app_process32.orig in the same folder
Change the name of app_process32 to whatever you like. Rename app_process32.orig to app_process32
Unroot.
Update system
The flashing will be done in three increments, with the device rebooting between each increment. Don't freak out, it's not a bootloop. Three circles underneath the android robot are changed to filled circles/dots, one for each increment.
After completing the flash, it took ages during the "optimizing apps"-process, but I was finally greeted with the "Update successful"-notification. The "about this phone"-section in settings now properly states version 12.0300 (though still Android 5.0.2).
Trying to acquire root was more of hit-and-miss. I had to run KingRoot several times, before it worked properly. SuperSU Me gave me different results on every run.
After the first run of KingRoot, it indicated success, but I could not to anything requiring root. SuperSU Me told me that KingRoot was not installed.
I re-ran KingRoot. Now SuperSU Me told me, that KingRoot is installed. Great. Trying to remove KingRoot, SuperSU Me stalled completely. Even KingRoot and the bloatware it installs crashed (giving system warnings). The result after this try basically was no root at all.
I re-ran KingRoot a third time, SuperSU Me works through both stages and notifies me of success. Amazing.
Running SuperSU afterwards however gives me a warning: "Another su-binary seems to be installed. Should I remove it" (or something similar, didn't jot it down).
After choosing yes, and a final reboot, everything seems to be back to normal with proper su, no KingRoot and latest version from Panasonic :good:
cybriks said:
Factory reset did not work.
However, I give you... *drumroll*... SUCCESS
Click to expand...
Click to collapse
I have never installed Xposed so I've never seen this error. Is it installed by Kingroot?
Great news, all the same!
JPCoetzee said:
I have never installed Xposed so I've never seen this error. Is it installed by Kingroot?
Great news, all the same!
Click to expand...
Click to collapse
Not that I am aware of. Take a look into the /system/bin folder and check whether you have app_process32 in differently named versions (I had app_process32 (which was a symlink) and app_process32.orig)
This didn't work for me There was an acc_process32_original and a symlink, but I think it was the SuperSU symlink. Anyway, no go. Back to the drawing board. Factory reset made no difference.
Which version of Kingroot did you use?
While having root, you could try to install FlashFire (if you haven't already). One of Chainfire's amazing tools.
Download the .dat-file to your phone and start to flash it with FlashFire. This will most certainly fail, but instead of simply rebooting upon failure, FlashFire should swiftly show you an error-message. Try to remember that and hunt down the problem by that.
You have to follow what is beeing displayed however, as FlashFire will abort the flashing and reboot just a few moments after displaying the error message.
I used KingRoot 4.65
Update: you probably wouldn't have to follow the display real-time. FlashFire should log to Internal memory > FlashFire > lastlog
cybriks said:
FlashFire should swiftly show you an error-message. Try to remember that and hunt down the problem by that.
Click to expand...
Click to collapse
Flashfire has helped me fix it! What a marvellous tool.
Ages ago I removed GCoupon - Panasonic/Lumix bloatware. Flashfire showed me that the update was failing on "/system/app/Gcoupon/Gcoupon.apk/ has unexpected contents". Gcoupon.apk was actually missing, so I replaced it with the version from the previous update file (0P0000121100000600110761_9274.dat).
I unrooted and restarted the update. After the 3 reboots and "Android is upgrading" I now have 12.0300. Using Kingroot 4.8.0 and Super-SUme I rooted on first attempt.
For my phone (without Xposed) the "app_process32 has unexpected contents error" is a red herring. When SuperSU is installed on a rooted device the app_process32 executable is replaced by a symlink to daemonsu so any update attempted on a rooted phone is bound to fail during the checking stage.
Thanks for your help!
JPCoetzee said:
Flashfire has helped me fix it! What a marvellous tool.
Click to expand...
Click to collapse
Great :good:
I tried to write a sum-up on the other thread as well: http://forum.xda-developers.com/showpost.php?p=65404103&postcount=40
Does anyone know how to get the CM1 into recovery mode? My CM1 is now in a boot loop after a failed panasonic update. The phone had been kingrooted, so that may be a contributing factor.
Anyway, I need to know how to get the phone into enter recovery mode, so I can do a reset.
Thank you.
allmankind said:
boot loop ... phone had been kingrooted, so that may be a contributing factor.
Click to expand...
Click to collapse
Something similar happened with my Sony Z3 (bootloop after kingroot on tablet with locked bootloader) and I had to reinstall the firmware using a Sony PC utility. Unfortunately Panasonic don't provide anything similar (I have asked their tech support).
If it can't be fixed using some generic PC software there is a Panasonic Service Centre here in the UK http://panasonic.dkavs.co.uk/
Thanks, but I am in Thailand. I have been in contact with Panasonic Japan, and they have refered me to Singapore. With the boot loop, it never gets to the stage where ADB can interact with the phone. But hopefully they will have something to allow either a factory reset, or a complete reloading fof the firmware.
As an aside, Japan told me the CM1 is in fact produced by the camera division (DMC-CM1 designation) and not the phone division.
After update firmware to 12.300, wifi tethering not working
DMC CM 1 Lockscreen
hello my CM1 have screenlock i dont know the pin anymore
anyone was able to make a Factory Reset with the phone?
i need some help please how to do a Factory Reset with the phone
it is show me in Windows as Android ADB Interface
or USB multimedia.
but if i use ADB SDK Manager it says Error no Devices found.
#i just need to do a factory reset. i also was trying to remove the Battery but i failed.

Can't upgrade to 3.41.651.4 OTA

Hi, I am trying to upgrade my Sprint HTC One M9 to 3.41.651.4.
Current Software Version: 2.11.651.19
My phone finds and installs 2.11.651.180, everything seems to work correctly, however, after rebooting, my phone is still on software 2.11.651.19.
My phone has never been rooted, s-on/off, or anything else. The only thing that I have changed on it is adding an SDCard. Everything else has been OTAs. Last factory reset was 3 weeks ago to solve a problem I was having with Gmail not syncing properly.
I would prefer to not have to factory reset it again by manually upgrading the firmware. Is their a log somewhere that will show what is preventing the upgrade from taking?
Ok, some more details. It appears when doing the OTA, the error I am getting is a System 7 error?
Then when I try to flash following the instructions on HTC's site using the RUU .exe, I get a 155 error.
From googling it appears both of these errors are caused by modifying the system partition. Which is great, except I haven't. I haven't monkeyed with my phone. Not unlocking, s-on/off, bootloader, recovery, etc. So I'm not sure how it came to be this way or how to restore it. Previous OTAs have all installed without issue.
Software Status: Modified
Locked
S-ON
Security Warning
And now my phone is stuck with a white screen. Menu options are:
Reboot
Reboot to Bootloader
Boot to Download mode
Boot to Recovery Mode
If I select recovery mode, it is unable to launch and takes me back.
Ok, I set it to Download mode and re-ran the RUU .exe, and it seems to have flashed properly now. So I guess I'm good. But I do have questions:
A) Why did the OTA fail multiple times with the System 7 message
B) Why did the RUU .exe wipe everything and give me the 155 failure the first time
C) Is there anything I should do/install/check to prevent problems in the future?
shawndoc said:
Ok, some more details. It appears when doing the OTA, the error I am getting is a System 7 error?
Then when I try to flash following the instructions on HTC's site using the RUU .exe, I get a 155 error.
From googling it appears both of these errors are caused by modifying the system partition. Which is great, except I haven't. I haven't monkeyed with my phone. Not unlocking, s-on/off, bootloader, recovery, etc. So I'm not sure how it came to be this way or how to restore it. Previous OTAs have all installed without issue.
Software Status: Modified
Locked
S-ON
Security Warning
Click to expand...
Click to collapse
you did something to make status modified
Yes, but what? Every other OTA has installed fine. I haven't tried to root or mess with s-on/off. The only thing I can think of, is last time I reset my phone (due to gmail failing to get push notifications) I uninstalled a bunch of the bundled apps, but I did it using the normal apps management settings.
shawndoc said:
Hi, I am trying to upgrade my Sprint HTC One M9 to 3.41.651.4.
Current Software Version: 2.11.651.19
My phone finds and installs 2.11.651.180, everything seems to work correctly, however, after rebooting, my phone is still on software 2.11.651.19.
My phone has never been rooted, s-on/off, or anything else. The only thing that I have changed on it is adding an SDCard. Everything else has been OTAs. Last factory reset was 3 weeks ago to solve a problem I was having with Gmail not syncing properly.
I would prefer to not have to factory reset it again by manually upgrading the firmware. Is their a log somewhere that will show what is preventing the upgrade from taking?
Click to expand...
Click to collapse
You probably got all those errors due to the fact you manually tried to update the firmware/software. And according to what you wrote you currently had 2.11.651.19 tried to update with an older firmware 2.11.651.180. Second if you are stock, not rooted or s-off and previously did OTA's, why didn't you wait for the 3.41.651.4 OTA?
schmeggy929 said:
You probably got all those errors due to the fact you manually tried to update the firmware/software. And according to what you wrote you currently had 2.11.651.19 tried to update with an older firmware 2.11.651.180. Second if you are stock, not rooted or s-off and previously did OTA's, why didn't you wait for the 3.41.651.4 OTA?
Click to expand...
Click to collapse
Re-read my first post, it was the OTA that was failing to install with the System 7 error, which then led me to try installing manually.
The OTA is a two part OTA. First it installs 2.11.651.180 and then it installs 3.41.651.4. See here: http://www.htc.com/us/support/htc-one-m9-sprint/news/
It was 2.11.651.180 OTA that was giving me the original error message.
shawndoc said:
Re-read my first post, it was the OTA that was failing to install with the System 7 error, which then led me to try installing manually.
The OTA is a two part OTA. First it installs 2.11.651.180 and then it installs 3.41.651.4. See here: http://www.htc.com/us/support/htc-one-m9-sprint/news/
It was 2.11.651.180 OTA that was giving me the original error message.
Click to expand...
Click to collapse
Gotcha, the 2.11.651.180 was the pre-MM update then the MM full OTA. Yes it is weird you were getting those error on a OTA. Even the RUU shouldn't have lead to an error as well. You still having problem or everything ok now?
Yup, all good now. Forcing the phone into download mode and performing the upgrade took. Thanks.

[Help Needed] Flashed 4.5.2 cant update update failed

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

Categories

Resources