So here's what happened: I had TWRP and HDX Nexus ROM successfully installed for a while, but I decided I wanted to go back to Fire OS and update to the newest version. I used TWRP to flash the stock backup I had saved, and then I used the KFHDX Tool to re-enable OTA updates. I got the OTA update to .3.2.5, and when the system rebooted it booted into TWRP automatically to flash the update. That kinda surprised me, since I thought doing an OTA update would wipe out any custom recovery, but I guess not. The Kindle booted and completed the .3.2.5 installation, then downloaded the .4.1.1 file. At this point it tried to reboot but hung on the grey Kindle Fire logo. I held the power button to restart it and it booted normally, but the update was unsuccessful. I tried it a couple more times for good measure, with the same result each time. I tried following the instructions here to downgrade to .3.1.0, but it said it couldn't validate the update file. I tried doing a factory reset, but it hung on the grey Kindle logo and was unsuccessful.
Basically, I think my recovery got messed up. I tried the adb reboot recovery command from my computer and it caused the Kindle to hang on the grey logo, so I'm guessing that's what's causing my issues. Not sure where to go from here.
iNTRCPT4lyfe said:
So here's what happened: I had TWRP and HDX Nexus ROM successfully installed for a while, but I decided I wanted to go back to Fire OS and update to the newest version. I used TWRP to flash the stock backup I had saved, and then I used the KFHDX Tool to re-enable OTA updates. I got the OTA update to .3.2.5, and when the system rebooted it booted into TWRP automatically to flash the update. That kinda surprised me, since I thought doing an OTA update would wipe out any custom recovery, but I guess not. The Kindle booted and completed the .3.2.5 installation, then downloaded the .4.1.1 file. At this point it tried to reboot but hung on the grey Kindle Fire logo. I held the power button to restart it and it booted normally, but the update was unsuccessful. I tried it a couple more times for good measure, with the same result each time. I tried following the instructions here to downgrade to .3.1.0, but it said it couldn't validate the update file. I tried doing a factory reset, but it hung on the grey Kindle logo and was unsuccessful.
Basically, I think my recovery got messed up. I tried the adb reboot recovery command from my computer and it caused the Kindle to hang on the grey logo, so I'm guessing that's what's causing my issues. Not sure where to go from here.
Click to expand...
Click to collapse
If you have a thor (7" HDX) try flashing this recovery. It's from stock 3.2.6 but proven to be compatible with 3.2.5. You can use Flashify to install the recovery image. Note there's always some risk messing with recovery. Also assuming you can boot into 3.2.5 and are not stuck at the grey Kindle logo.
Thanks, that worked great. Now that the bootloader is unlocked, I got cold feet about going down the OTA path anyway. I was able to successfully roll back to .3.1.1 after I flashed the .3.2.6 recovery.
iNTRCPT4lyfe said:
Thanks, that worked great. Now that the bootloader is unlocked, I got cold feet about going down the OTA path anyway. I was able to successfully roll back to .3.1.1 after I flashed the .3.2.6 recovery.
Click to expand...
Click to collapse
Thanks for the update! Glad it worked out.
Related
My Rezound and I are stuck.
Let me start at the beginning. My Rezound was running “RUU_Vigor_VERIZON_WWE_1.02.605.6” and it was unlocked and rooted. So recently Verizon started forcing this firmware update with no way to stop it that I could find. So I decided to update on my own. I did a Nanoid backup of everything and a Titanium back up of everything. I relocked my phone and I found “RUU-build-4-03-605-2” at Android Police [Exclusive Download] Full RUU Build 4.03.605.2 For The HTC Rezound. So I downloaded it and renamed it PH98IMG.zip. Placed it on my SD card and booted into HBOOT were it loaded the new version. It worked so I unlocked my phone and loaded “recovery-ra-vigor-3.15-gnm.img”. I loaded SU from the recovery had it updated at Google Play. Reloaded Titanium rooted and this is where things started to go wrong. No permissions were being given to Titanium. I tried “recovery-ra-vigor-3.14-gnm.img” and I even tried SUSuper but nothing worked. I went into recovery and did a complete Nanoid recovery. Since then I have not been able to get anything to work. I cannot load any older versions. I try to reload “RUU-build-4-03-605-2” but it makes it to #4 system were it gets stuck in a loop of unzipping and updating.
My very last attempt was to unlock the phone load “recovery-ra-vigor-3.13-gnm.img” go into recovery and do a wipe of everything. Then from XDA-Developers [ROM][ICS Global Phone Update][4.03.605.1] Stock, Root, Deodex, Busybox, Global Phone - xda-developers I downloaded the ICS Global Phone Update Firmware and the ICS Global Phone Update. In recovery I used “flash a zip” to update the firmware. I locked the phone and renamed the Phone Update to PH98IMG.zip. Booted into HBOOT and allowed it to update the software. I instantly powered down and renamed “RUU-build-4-03-605-2” to PH98IMG.zip rebooted to HBOOT and it made it to #4 system where it got stuck in the loop.
When I try just to start the phone it stays on the white HTC screen.
What can I do to get my phone working again? Please be specific with the steps to take because I am still at the bottom of the learning curve.
One other question: Can my Nanoid backup recover the data for the internal card so Titanium will be able to recover my programs.
Thank You SOOOOOOO very much for your help.
dnvm said:
My Rezound and I are stuck.
Let me start at the beginning. My Rezound was running “RUU_Vigor_VERIZON_WWE_1.02.605.6” and it was unlocked and rooted. So recently Verizon started forcing this firmware update with no way to stop it that I could find. So I decided to update on my own. I did a Nanoid backup of everything and a Titanium back up of everything. I relocked my phone and I found “RUU-build-4-03-605-2” at Android Police [Exclusive Download] Full RUU Build 4.03.605.2 For The HTC Rezound. So I downloaded it and renamed it PH98IMG.zip. Placed it on my SD card and booted into HBOOT were it loaded the new version. It worked so I unlocked my phone and loaded “recovery-ra-vigor-3.15-gnm.img”. I loaded SU from the recovery had it updated at Google Play. Reloaded Titanium rooted and this is where things started to go wrong. No permissions were being given to Titanium. I tried “recovery-ra-vigor-3.14-gnm.img” and I even tried SUSuper but nothing worked. I went into recovery and did a complete Nanoid recovery. Since then I have not been able to get anything to work. I cannot load any older versions. I try to reload “RUU-build-4-03-605-2” but it makes it to #4 system were it gets stuck in a loop of unzipping and updating.
My very last attempt was to unlock the phone load “recovery-ra-vigor-3.13-gnm.img” go into recovery and do a wipe of everything. Then from XDA-Developers [ROM][ICS Global Phone Update][4.03.605.1] Stock, Root, Deodex, Busybox, Global Phone - xda-developers I downloaded the ICS Global Phone Update Firmware and the ICS Global Phone Update. In recovery I used “flash a zip” to update the firmware. I locked the phone and renamed the Phone Update to PH98IMG.zip. Booted into HBOOT and allowed it to update the software. I instantly powered down and renamed “RUU-build-4-03-605-2” to PH98IMG.zip rebooted to HBOOT and it made it to #4 system where it got stuck in the loop.
When I try just to start the phone it stays on the white HTC screen.
What can I do to get my phone working again? Please be specific with the steps to take because I am still at the bottom of the learning curve.
One other question: Can my Nanoid backup recover the data for the internal card so Titanium will be able to recover my programs.
Thank You SOOOOOOO very much for your help.
Click to expand...
Click to collapse
You tried in recovery turning on Full Format and formatting "system"?
Also try loading a custom rom and flashing it via recovery and see if everything works properly
Don't use the Su option in recovery always flash SU using one of the flash zips either SuperSU or Superuser
Tachi91 said:
You tried in recovery turning on Full Format and formatting "system"?
Also try loading a custom rom and flashing it via recovery and see if everything works properly
Don't use the Su option in recovery always flash SU using one of the flash zips either SuperSU or Superuser
Click to expand...
Click to collapse
Thank you for your response. I went into “Recovery – Wipe” and selected “Toggle Ext Full Wipe”. Then I went to “Format “ and selected “Format all to ext3”. It showed me the warnings and I pressed power to continue.
I tried to recover using my Nandroid backup but it did not work. So I formatted a second time. This time I flashed the firmware zip file and it worked 100% this time. Rebooted to HBOOT/Fastboot and locked the phone. The phone rebooted and made it all the way through setup and to home screen. Software version 4.0.3-605.1 so why stop there. I booted into HBOOT and let version 4.0.3-605.2 load and it made it to “System” and got stuck in the loop.
So to make a long story short I started all over again and flashed the ICS Global Phone Update Firmware. I verified that everything was up and running. Then I tried one last thing. I went into recovery and did a Nandroid recovery. I only selected “Data” and “Ext-card” and let it go. I am now fully operational with all of my programs including my wallpaper. The only thing I can tell I lost was Titanium Backup’s backup. Everything shows no backup and no files are frozen.
Thank you again for your help. :good:
Hey guys,
I got a TF201 tablet.
I was trying to install the crombi-KK rom on it.
After several hours of trying and failing I found out that I had to install TWRP 2.8, but to do so, I needed to run the hairy bean boot loader.
When I figured that out, I shut down the device, and then nvflashed it back to the stock FW.
When the flash finished, the tabled was no longer booting (weird because I have never seen it failing after nvflashing the stock firmware).
After nvflashing it, the bootloader when back to ICS. I installed flashed TWRP using fastboot, when I started the recovery image I got a message asking for the password for data. After doing some research on that I figured that I needed to format the data partition for it to boot again.
Once that was done, the device boot OK to the stock ROM. I tried upgrading back to JB using the asus upgrade procedure and the tablet rebooted back to ICS.
I tried to install the stock JB firmware using twrp, it says it completes OK but when I reboot the tablet it goes back to ICS.
I then flashed several other recovery images, every time I start the tablet in recovery I get a message saying that it cannot mount the /cache partition and others.
If I try to flash any ROM using any recovery sometimes it says it worked but the tablet boots back to ICS, some other times and says it failed and goes back to ICS.
I used to have a BAT that helped me formatting the partitions and then to flash blobs one by one, but I deleted it because I thought I was never going to need it anymore.
I was wondering if what partitions does this tablet has (EX: recovery, boot, app, etc).
Is there any toolkit that formats the partitions and flashes then using stock JB images extracted from the blob files?
Jcascantez said:
Hey guys,
I got a TF201 tablet.
I was trying to install the crombi-KK rom on it.
After several hours of trying and failing I found out that I had to install TWRP 2.8, but to do so, I needed to run the hairy bean boot loader.
When I figured that out, I shut down the device, and then nvflashed it back to the stock FW.
When the flash finished, the tabled was no longer booting (weird because I have never seen it failing after nvflashing the stock firmware).
After nvflashing it, the bootloader when back to ICS. I installed flashed TWRP using fastboot, when I started the recovery image I got a message asking for the password for data. After doing some research on that I figured that I needed to format the data partition for it to boot again.
Once that was done, the device boot OK to the stock ROM. I tried upgrading back to JB using the asus upgrade procedure and the tablet rebooted back to ICS.
I tried to install the stock JB firmware using twrp, it says it completes OK but when I reboot the tablet it goes back to ICS.
I then flashed several other recovery images, every time I start the tablet in recovery I get a message saying that it cannot mount the /cache partition and others.
If I try to flash any ROM using any recovery sometimes it says it worked but the tablet boots back to ICS, some other times and says it failed and goes back to ICS.
I used to have a BAT that helped me formatting the partitions and then to flash blobs one by one, but I deleted it because I thought I was never going to need it anymore.
I was wondering if what partitions does this tablet has (EX: recovery, boot, app, etc).
Is there any toolkit that formats the partitions and flashes then using stock JB images extracted from the blob files?
Click to expand...
Click to collapse
Join our irc sometime, we can give much better support there ..
Channel ##crombi-kk
Network Freenode
Thx Josh
I think I finally bricked my device. I'm guilty. Just want to keep track of everything I did and share how it's bricked.
1. Everything starts because the 4g LTE stopped working. The device starts to give me "Invalid SIM" message no matter how I try. Same message with either T-mobile sim card or the stock AT&T sim card. At this time, the device is on TWRP 2.8.1.0 with Thor Gapps Rom ( 13.3.2.4 ).
2. Thinking it might be a ROM issue, I restored 13.3.2.3.2. Same error message: Invalid SIM.
3. Thinking to restore everything stock before returning it to amazon, I flash stock recovery.img to overwrite TWRP and restored 13.3.2.6 backed-up with safestrap. System starts up but has some issue: it always goes back to selecting language page.
4. Flashed update-kindle-13.4.5.2_user_452004120-twrp.zip to stock slot with safestrap in hope of fixing everything. Now system stalls at the white "Kindle fire" screen.
I know that zip is for twrp, but I thought twrp can take backup made with safestrap, why not the other way around?! Well, I'm unlucky this time. One shall never touch stock slot with safestrap. I think I should have used the official update-kindle-13.4.5.2_user_452004220.bin and update through Device-update menu. Oh well.
Any way I can still play with this device before it set off for amazon?
In
shadowcliffs said:
I think I finally bricked my device. I'm guilty. Just want to keep track of everything I did and share how it's bricked.
1. Everything starts because the 4g LTE stopped working. The device starts to give me "Invalid SIM" message no matter how I try. Same message with either T-mobile sim card or the stock AT&T sim card. At this time, the device is on TWRP 2.8.1.0 with Thor Gapps Rom ( 13.3.2.4 ).
2. Thinking it might be a ROM issue, I restored 13.3.2.3.2. Same error message: Invalid SIM.
3. Thinking to restore everything stock before returning it to amazon, I flash stock recovery.img to overwrite TWRP and restored 13.3.2.6 backed-up with safestrap. System starts up but has some issue: it always goes back to selecting language page.
4. Flashed update-kindle-13.4.5.2_user_452004120-twrp.zip to stock slot with safestrap in hope of fixing everything. Now system stalls at the white "Kindle fire" screen.
I know that zip is for twrp, but I thought twrp can take backup made with safestrap, why not the other way around?! Well, I'm unlucky this time. One shall never touch stock slot with safestrap. I think I should have used the official update-kindle-13.4.5.2_user_452004220.bin and update through Device-update menu. Oh well.
Any way I can still play with this device before it set off for amazon?
Click to expand...
Click to collapse
Did you already try just holding onto the power button for over 20sec , to force a hard reset and get back into RECOVERY
the rest I'm not sure about you say you are on Thor gapps? with our new 2. 8. 1. 0?
did he make that compatible? I didn't realize Thor gapps was compatible
and what are you even doing with the update .5.2 ?that is the KitKat update and is completely incompatible with safestrap or older kernels so I am really confused on what you have stated in above post
or do you have that TRW P recovery flashed and somehow using safestrap also?
looks like to me you have flashed everything but the right thing but then again it's really hard to tell what you have going on here.
Holding the power button for over 20 sec does me nothing. I can enter "Kindle Fire System Recovery" the same way I entry twrp though by holding power and volume up during booting. There are two options there:
Reboot your Kindle
Reset to Facotry Defaults
I tried both and none helped me to boot into system.
I hate it that HDX is not like Samsung Galaxy phones which have a true recovery mode that can flash file, or a download mode that allows access via adb.
I think the reason that my hdx is bricked are:
1. First, I overwrote twrp with stock recovery 13.3.4 (because I want to restore to stock mode for return). Otherwise if I can still enter twrp, I will be saved.
2. Second, the file I flashed to stock slot with safestrap, update-kindle-13.4.5.2_user_452004120-twrp.zip, is made to boot with twrp. I guess it doesn't go well with the stock recovery 13.3.4.
jimyv said:
InDid you already try just holding onto the power button for over 20sec , to force a hard reset and get back into RECOVERY
the rest I'm not sure about you say you are on Thor gapps? with our new 2. 8. 1. 0?
did he make that compatible? I didn't realize Thor gapps was compatible
and what are you even doing with the update .5.2 ?that is the KitKat update and is completely incompatible with safestrap or older kernels so I am really confused on what you have stated in above post
or do you have that TRW P recovery flashed and somehow using safestrap also?
looks like to me you have flashed everything but the right thing but then again it's really hard to tell what you have going on here.
Click to expand...
Click to collapse
Hi, my G3 (vs985) was running 24b, rooted, and I installed TWRP Manager and installed a custom recovery. all went fine until I got a secure boot error whenever I booted to recovery. After tinkering and thinking I found a possible solution, I used autorec which gave a Success in installing twrp, and booted back in to recovery where I got a into an LG Security Error and would continue switching between the logo and the security error screen. I was still able to get into twrp through the factory recovery menu and going to factory reset which sends me to twrp. I tried restoring a backup I had previously made, and that went successfully but now my issue is that I'm stuck in a boot certification error with the light blinking blue and red and I am unable to get into download mode, but am still able to get into twrp and get into my phone's files. I don't trust myself anymore, and would absolutely love some guidance on this. If I do try to go to download mode, and I connect it to my pc, my pc makes the noise as if it were connecting, and the phone vibrates, but the screen turns black and nothing "seems" to pop up. I can try to answer any questions, I am somewhat new to this. Thank you in advance!
EDIT: The error I'm currently getting is:
"Secure Boot Error
Cause: Boot Certification Verify".
I'm guessing that you used the 23C autorec which put the wrong bootloader on the phone for 24B. From TWRP. I'd create a backup in TWRP, dirty flash JasmineROM 8.0 (in other words, no wiping), then you should be good.
I had this yesterday. Did the same thing.
I finally resolved it by getting back into TWRP from the OEM recovery, Full System Wipe menu item. TWRP allowed me to mount the storage on my computer and flash SkyDragon 5.0. I still can't get back into recovery, but at least the phone works better than stock Lollipop.
BoulderGeek said:
I had this yesterday. Did the same thing.
I finally resolved it by getting back into TWRP from the OEM recovery, Full System Wipe menu item. TWRP allowed me to mount the storage on my computer and flash SkyDragon 5.0. I still can't get back into recovery, but at least the phone works better than stock Lollipop.
Click to expand...
Click to collapse
Boulder, I'm not sure I understand what you wrote, twrp is recovery, so if you can flash using twrp are you just unable to access it ...it must me installed on your phone? I haven't flashed using the computer in a long time, so it's not really fresh in my mind what you did. If you power down your phone, then hold the power and vol down button simultaneously, it will reboot, release buttons, then as soon as you see the lg logo, press the power/volu down simult. again, and it will take you to a screen that gives you options you can choose using the volume up/down keys to navigate and power to choose a button. Wipe cache would take you into twrp if it is indeed installed on your phone. If you can access twrp however you did previously,you can flash a zip file of twrp (I use 2.8.7.0, I think it is the newest, it is newer than what was in autorec that I tried last night). Wipe davalcik/cache after you flash the twrp zip and reboot your phone and you should be fine....although I think you may actually have twrp already (hence 'recovery"} based on what you posted. Good luck.
I did flash the 23C version of Autorec into my 24b phone. This gave me the Security Error bootloop.
Eventually I was able to get into LG stock recovery with the volume down button. Magically, hitting Factory Wipe brings me to the hidden TWRP. From there I flashed base SD5.0. In Android, I installed the Autorec 24b apk and reinstalled TWRP. This again security looped.
Now, I can't even access LG bootloader or TWRP. Even the QuickBoot app fails to boot to revovery. But, the phone works, so I don't want to break it further. Might just wait for a development upgrade to SkyDragon.
Hello, I need a little advice on getting my phone working again. I got a new Ramos MOS1 Max today and rooted it via Kingo PC software. I checked to make sure it was rooted using RootChecker and it said it was rooted. I was reading up on what to do next and some sites said the next thing you must do is to make a backup of your phone via TWRP. I installed the software and then attempted to use the "reboot and create backup" functionality. The phone rebooted and I was in the Android system recovery menu. I didn't see anything like what TWRP was supposed to show, so I just rebooted via the standard recovery screen method. Now when I try to start the phone, it gives me a logo, then ARMPHONE and it hangs on that.
I've tried wiping my cache partition via recovery menu and rebooting, but no dice. Next they suggested to do a wipe data/factory reset, and since I just received the phone today, I decided to try that. After doing that via system recovery menu it still wouldn't boot past the ARMPHONE screen. I don't have a lot of experience with rooting and modifying Android devices, is there something I can do to fix this? I've installed the android SDK tools for my version of android (5.1 I believe), but I don't know how to proceed. Is there a stock image I can use for this phone, or can I just use a vanilla android image?
Thanks in advance.
sphericon said:
Hello, I need a little advice on getting my phone working again. I got a new Ramos MOS1 Max today and rooted it via Kingo PC software. I checked to make sure it was rooted using RootChecker and it said it was rooted. I was reading up on what to do next and some sites said the next thing you must do is to make a backup of your phone via TWRP. I installed the software and then attempted to use the "reboot and create backup" functionality. The phone rebooted and I was in the Android system recovery menu. I didn't see anything like what TWRP was supposed to show, so I just rebooted via the standard recovery screen method. Now when I try to start the phone, it gives me a logo, then ARMPHONE and it hangs on that.
I've tried wiping my cache partition via recovery menu and rebooting, but no dice. Next they suggested to do a wipe data/factory reset, and since I just received the phone today, I decided to try that. After doing that via system recovery menu it still wouldn't boot past the ARMPHONE screen. I don't have a lot of experience with rooting and modifying Android devices, is there something I can do to fix this? I've installed the android SDK tools for my version of android (5.1 I believe), but I don't know how to proceed. Is there a stock image I can use for this phone, or can I just use a vanilla android image?
Thanks in advance.
Click to expand...
Click to collapse
You can find the firmware here http://4pda.ru/forum/index.php?showtopic=783029