Database Develop

Solved - Locked Boot Screen, Unable To Access Custom Recovery Image.

Very noobish issue. Rooted, unlocked bootloader on Atrix HD. Set up SafeStrap as recovery. Everything checked and working. After letting SafeStrap install Cyan 10.3 and rebooting, phone entered CyanogenMod boot screen and become stuck for an hour. Realized that I forgot to reset and wipe all stock settings and cache (yes, I know that should have been obvious step). Figured I could just go into SafeStrap and make the quick fix.
Seems that I'm unable to enter my custom recovery, instead I'm lead to the familiar bricked android stock recovery. No options to access stock rom (assuming it was deleted during install or lost, etc). Tried installing a different recovery, but fastboot on PC is unable to find device. Help at this point is very much appreciated, either to do any of the following:
1. Somehow access SafeStrap again (assuming that it wasn't wiped aswell) so I can clear stock settings and cache, get Cyan 10.3 going properly.
2. Instructions/links to another method to otherwise forcibly delete stock settings and cache (please keep in mind, fastboot is currently unable to find device).
3. Otherwise completely clear phone of EVERYTHING, then reinstal stock recovery and or/stock ROM so I can give up on flashing custom and stick with stock.

*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.

Update Motorola drivers on your computer and check threads for fastboot files from skeevydude.
Sent from my MB886 using XDA Premium 4 mobile app

Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX

http://forum.xda-developers.com/showthread.php?t=2226527
Sent from my MB886 using XDA Premium 4 mobile app

SkunkID said:
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Click to expand...
Click to collapse
The error is from using the wrong fastboot executable. Look at post 5. If you get a stickybit error, search our general forums for "stickybit" and you'll find that fix.
deeje00 said:
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
With a bit of creativitity one could use SSR to dual boot Holo Blur and Batakang....or two custom 4.3's that use the same kernel....PAC + Carbon both with arrrghhh's kernel.....Only problem is ya can't be a noob at all if ya do it.

Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.

When you're at the "dead Android" screen pressing Vol Down + Power pushes it into recovery, iirc - might seem random but there's a purpose behind it.

SkunkID said:
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
Click to expand...
Click to collapse
Hi, I am having the same issue you had... how the heck were you able to get back into stock recovery? Every time I try my phone just reboots and gets stuck again. I cant even turn off my phone with out it rebooting. I have read your posts and followed that other forum you mentioned but if I cannot boot into recovery and if my computer cant see my phone it wont work. Please help when you get a chance.

I messed up trying to install CM12.1...

I currently am trying to install CM12.1 onto my Amazon Fire 7, but unfortunately, it looks like I may have messed up in the process (I am stuck with the Amazon logo re-looping every ~15-20 seconds). I am able to go into the safe recovery mode, so I assume I haven't bricked the device completely, but I was wondering, what exactly is the best way to flash CM12.1 onto this device?
There seems to be an excessive amount of information, but very little organization, so would love to hear what the "best" steps would be to get CM12.1 on this bad boy.

I don't have the device yet but from what i read you need to tell us more info like what was your amazon v. 5.0.1 or 5.1.1 and how you install cm by TWRP or flash fire
Sent from my iPhone using Tapatalk

it will all depend on the version you have, but here you will find most info.
http://forum.xda-developers.com/amazon-fire/general/videos-tutorials-how-to-root-flash-roms-t3254268

shabuboy said:
it will all depend on the version you have, but here you will find most info.
http://forum.xda-developers.com/amazon-fire/general/videos-tutorials-how-to-root-flash-roms-t3254268
Click to expand...
Click to collapse
So I went ahead and installed the original firmware (5.1.1), but now am wondering where do I go from here. I have the device rooted and installed Flashify, but I am not sure how to install TWRP for 5.1.1, as I was using Rootjunky's .bat file.

darkgiant said:
So I went ahead and installed the original firmware (5.1.1), but now am wondering where do I go from here. I have the device rooted and installed Flashify, but I am not sure how to install TWRP for 5.1.1, as I was using Rootjunky's .bat file.
Click to expand...
Click to collapse
You can't install TWRP on 5.11, if you want to flash roms you have to use FlashFire now.
This is due to the 5.11 ota update including a bootloader update which removes the ability to fastboot boot.
Just follow the instructions to install CM 12.1 and wait for it to boot.

Ownster said:
You can't install TWRP on 5.11, if you want to flash roms you have to use FlashFire now.
This is due to the 5.11 ota update including a bootloader update which removes the ability to fastboot boot.
Click to expand...
Click to collapse
Yeah, so I just found that out few seconds ago. I tried to flash and install CM, but after the reboot, it just goes back to the FireOS "Optimizing system storage and applications..." screen, no idea what I am doing wrong...
I am also wiping everything too before I flash the CM and GAPPS zip files

darkgiant said:
I am also wiping everything too before I flash the CM and GAPPS zip files
Click to expand...
Click to collapse
I would be very careful using flashfire if your coming from fire os 5.1.1, we cannot use TWRP and a few people(myself included) have lost access to Amazon recovery, if you get stuck in a boot loop you have no way to recover your device, your best bet is to wait to see if a more secure way appears of flashing a device that has been using fire os 5.1.1.

abacabie said:
I would be very careful using flashfire if your coming from fire os 5.1.1, we cannot use TWRP and a few people(myself included) have lost access to Amazon recovery, if you get stuck in a boot loop you have no way to recover your device, your best bet is to wait to see if a more secure way appears of flashing a device that has been using fire os 5.1.1.
Click to expand...
Click to collapse
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.

darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
Click to expand...
Click to collapse
Glad it worked well for you. Not everyone has been so fortunate. One persons favorable experience does not equate to everyone. Some of those impacted are veteran users who 'lost' devices testing out code and techniques that you are now benefiting from.

darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
Click to expand...
Click to collapse
If you read my post properly i said " lost access to Amazon recovery" , there is no way to transfer the file from ADB as ADB is not there, due to the fact that there is no Amazon recovery, holding volume down + power does nothing, if you look around the forum you will see this has happened to a few people myself included .

darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
Click to expand...
Click to collapse
He's talking about how his device got buggered from a dirty Rom load. In his case and for a few others, they've lost the option to sideload back to stock.
Anyway here's the bare minimum process, since it sounds like you've gone through the details parts of Rom loading before.
#1 restore to stock rom 5.1.1
#2 install SuperSU/Root
#3 install flashfire
#4 install CM/SlimLP and Gapps (pico, micro, mini) of your choice, and your done.
When I put CM on my 5.1.1 Fire device, I installed flashfire.apk manually, used open Gapps pico, and the CM 12-30-2015 image.

abacabie said:
If you read my post properly i said " lost access to Amazon recovery" , there is no way to transfer the file from ADB as ADB is not there, due to the fact that there is no Amazon recovery, holding volume down + power does nothing, if you look around the forum you will see this has happened to a few people myself included .
Click to expand...
Click to collapse
Gotcha, didn't know there was level of increments the relooping represented. Well either way, hopefully something gets developed to all the "hard-bricked" users.

Bricked my Amazon fire 5th gen

Hey guys, after successfully changing my OS to cyanogenmod I wanted to do the same on a second amazon fire 5th gen I had laying around. So I rooted it, installed the google apps, downloaded Flashfire from the google play store, but when I used flashfire to flash the most recent CM12.1 from the XDA thread it kept saying that the data was incompatible or something. So I tried doing a factory reset and tried again, but the same thing kept occurring. After that I thought I would try installing the SlimLP mod instead, and it worked. Once I got SlimLP up and running I downloaded Flashfire again, and went to go install CM12.1 once again, but this time it got stuck at the very beginning. It didn't even look like it was writing any data or anything. The whole process only took about a minute on my other amazon fire, so I knew something was wrong. I waited 15-30 mins and no change. Eventually I turned it off, and rebooted, hoping for the best. Unfortunately, it loads the CM boot logo, and just gets stuck their permanently. I tried going into boot recovery by holding down volume down, and the power button, but when I do that it gets stuck at the amazon boot logo. I can still get it to boot into fastboot by holding down the volume up and power button, but when I try to flash a recovery image using fastboot it says that Flashing images is locked, or something.
Can someone tell me if there is still anyway to save it?

This will work
Hi
So i have the same tablet as you do and i faced the same problem as well and i found a way to fix it and this is what i did-
1) I went to recovery mode ( Power button and volume up button at same time) and factory reset and cleared data.
2) Wipe cache patition
3) Then I used this tutorial so i can go back to original state
4) Once there, I rooted my tablet again and download google play store and blahh balhh
5) Then I downloaded flashfire apk
6) This time i didn't download latest CM 12.1 for the tablet but this one ( cm-12.1-20151230-R01-UNOFFICIAL-ford.zip )
7) And gapps
8) I flashed and it worked beautifully.
9) Once done then I flashed the latest version CM 12.1 for the tablet and it worked amazingly . Sorry for not providing the links because i am new and i still have to wait a bit longer Thanks for reading this and i can guarantee 99.9% this work. Don't forget to tell me what happened.

Yeah, but like I said, the device freezes before it can get into recovery mode. I can only get into fastboot, but I don't think there is anything I can do with that.

speaker1264 said:
Yeah, but like I said, the device freezes before it can get into recovery mode. I can only get into fastboot, but I don't think there is anything I can do with that.
Click to expand...
Click to collapse
Return it to Amazon. I rang them and basically claimed ignorance that the device had stopped working, they sent me another one (and I returned the 'bricked' one). Luckily the replacement one came with 5.0.1 so I carefully made sure I did not upgrade before replacing the ROM instance with CM12.1.

jeromeof said:
Return it to Amazon. I rang them and basically claimed ignorance that the device had stopped working, they sent me another one (and I returned the 'bricked' one). Luckily the replacement one came with 5.0.1 so I carefully made sure I did not upgrade before replacing the ROM instance with CM12.1.
Click to expand...
Click to collapse
exactly the same thing happened to me as in the op. there is absolutely no way to fix it with the bootloader being locked down. i filed a replacement, telling them that after i installed a program it no longer goes past the boot screen. (i call that a grey area as far as lies go). go through their little trouble shooting performance where they ask if the device is charged.... then they will replace the device as long as it is in the warranty period. drop the old one off at ups, and 2 days later you will get the new one in the mail.

Help with recovery

I came across another thread that seemed to help me a bit. Can't find it again. So, hoping someone can point me in the right direction or better yet, give me a magic solution
History - I have a kindle fire - 5th gen. Got it with 5.1.2 which upgraded automatically to 5.1.4. I sideloaded 5.1.2 and it worked just fine. However, I missed the fact that the bootloader is locked on 5.1.2 and tried to flash TWRP. I also blocked OTA updates. (Rootjunky's tool)
Current situation - I am rooted and on 5.1.2. I want to get to Cm 12.1, but I can't get into recovery at all. It is stuck on the "Amazon" logo when I try to get to recovery. It is not the blue logo - I have never seen it, but my logo's not blue. I'm able to boot normally and use the tablet without any issues.
Question - The thread I came across earlier said that a fastboot cable is the only way out. But this person seemed to be at the "blue amazon" logo. Help? Thoughts?

smvsmv said:
I came across another thread that seemed to help me a bit. Can't find it again. So, hoping someone can point me in the right direction or better yet, give me a magic solution
History - I have a kindle fire - 5th gen. Got it with 5.1.2 which upgraded automatically to 5.1.4. I sideloaded 5.1.2 and it worked just fine. However, I missed the fact that the bootloader is locked on 5.1.2 and tried to flash TWRP. I also blocked OTA updates. (Rootjunky's tool)
Current situation - I am rooted and on 5.1.2. I want to get to Cm 12.1, but I can't get into recovery at all. It is stuck on the "Amazon" logo when I try to get to recovery. It is not the blue logo - I have never seen it, but my logo's not blue. I'm able to boot normally and use the tablet without any issues.
Question - The thread I came across earlier said that a fastboot cable is the only way out. But this person seemed to be at the "blue amazon" logo. Help? Thoughts?
Click to expand...
Click to collapse
bootloader was always locked, but 5.0.X allows booting a custom Recovery
if it will not boot to recovery nor rom/system, nothing can be done
fastboot cable doesn't work with 5th gen fires
Sent from my DROID Turbo using XDA Labs

Thanks... When you say "if it will not boot to recovery nor rom/system, nothing can be done", I see a glimmer of hope. The only thing I'm unable to do is boot to recovery. I am still rooted and able to use the tablet fully. There are no issues with that.
Does that help?

smvsmv said:
Thanks... When you say "if it will not boot to recovery nor rom/system, nothing can be done", I see a glimmer of hope. The only thing I'm unable to do is boot to recovery. I am still rooted and able to use the tablet fully. There are no issues with that.
Does that help?
Click to expand...
Click to collapse
Thoughts:
- you can still flash a custom ROM but if something goes wrong during the upgrade you're screwed without a recovery environment.
- recent versions of FlashFire have the ability to preserve and rewrite the recovery environment; not certain if the process works on this device and potential side effects (if any).
- several months ago another contributor claimed to have resurrected the stock recovery environment via adb which created quite a stir at the time. Have not seen much since so I suspect the solution was not generically applicable.
- I'm of the belief that most recovery access issues are actually a booting problem vs a damaged recovery partition. Your situation may be a little different as you attempted to rewrite the recovery partition by flashing TWRP.

oh well.. I'll just wait for you brainy guys to figure a way out. Not messing with the device anymore for now. Thank you!

Bricked Kindle

Hello All,
I have a bricked or possibly semi bricked kindle. I recently used the supertool to root the device. After using the super I tested out the novalauncher, I didn't like it so I went back to the stock launcher. When I went back to the stock launcher the screen would flash on and off not allowing me to anything. Needless to say I have to back to the nova launcher. I was able to install flashfire and I tried installing cyanogenmod. I think cyanogenmod did not finish installing flashfire just cutoff in the middle. I'm stuck in the boot animation and I waited a whole day to see if it was just optimizing apps. Things I've done so far wipe cache>factory reset, recovery via the supertool, restore via KFFirstAide but it cant pickup my kindle. I can boot into fastboot manually. I dont have TWRP recovery because it never seemed to flash.