So I followed a guide that used fireflash to flash freedom boot and TWRP. The problem is when it got to the point of backing up before I installed the system, I didn't have enough space. Not a problem right? Well in my haste I rebooted out of TWRP and now I can't get back into TWRP or obviously the system which doesn't exist.
I would have thought it would be simple to get back into TWRP and just carry on but it looks like there is no easy way to get back into it?
This is a HD7 model no: X43Z60
Does the logo ever turn blue still?
stunts513 said:
Does the logo ever turn blue still?
Click to expand...
Click to collapse
No it just loops on the orange kindle fire one. It's worth mentioning that obviously it did initially turn blue to get into TWRP but after it asked if I would like to restart, it just went into the loop.
If it didn't turn blue you will need a fastboot cable/adapter to fix, I recommend team blackhats from hashcode's twrp tut.
You will have to reflash stock and go about reinstalling twrp/2nd bootloader, I think you wiped the stack override so it won't boot.
stunts513 said:
If it didn't turn blue you will need a fastboot cable/adapter to fix, I recommend team blackhats from hashcode's twrp tut.
You will have to reflash stock and go about reinstalling twrp/2nd bootloader, I think you wiped the stack override so it won't boot.
Click to expand...
Click to collapse
Thanks for the responses.
I have ordered a fastboot cable and it's nice to hear that this is still recoverable. Would you be able to point me in the direction of the best reflash stock tutorial you know of?
The tutorial I used to get into this mess used an APK to do all of the flashing / stack override methods.
That's the same method I used for flashing, it seemed to have worked for you so the method was fine. Anyways you can look in the general section fornmkindke fire first aid, or in the dev section's FAQ post for the SRT(system restore tool), either one fixes it.
stunts513 said:
That's the same method I used for flashing, it seemed to have worked for you so the method was fine. Anyways you can look in the general section fornmkindke fire first aid, or in the dev section's FAQ post for the SRT(system restore tool), either one fixes it.
Click to expand...
Click to collapse
Cheers for the help
Related
Hi,
I followed the very comprehensive guide here: http://forum.xda-developers.com/showthread.php?t=2271909
however when I tried to reboot it seem the booting process restarts and the Kindle Fire logo will flash on and of with 10 sek intervals.
any ideas how to get out of this?
Thanks
Christiansloth said:
Hi,
I followed the very comprehensive guide here: http://forum.xda-developers.com/showthread.php?t=2271909
however when I tried to reboot it seem the booting process restarts and the Kindle Fire logo will flash on and of with 10 sek intervals.
any ideas how to get out of this?
Thanks
Click to expand...
Click to collapse
Something went wrong. Do you see the blue logo? If you do, you have the bootloader installed properly. Enter recovery and wipe everything (except system and sdcard) and reboot. If not, try to restore using fastboot in step 6.
seokhun said:
Something went wrong. Do you see the blue logo? If you do, you have the bootloader installed properly. Enter recovery and wipe everything (except system and sdcard) and reboot. If not, try to restore using fastboot in step 6.
Click to expand...
Click to collapse
I have the same problem. No blue logo, just an infinite boot loop.
I can't get into fastboot, so I purchased a factory cable last night in hopes that it will help.
bryang said:
I have the same problem. No blue logo, just an infinite boot loop.
I can't get into fastboot, so I purchased a factory cable last night in hopes that it will help.
Click to expand...
Click to collapse
Because the device boots properly, you'll have no trouble getting into fastboot with the cable. I apologize something went wrong, but apparently it's on your end, because many people reported no issues. Please make sure you followed the guide to the tee.
seokhun said:
Because the device boots properly, you'll have no trouble getting into fastboot with the cable. I apologize something went wrong, but apparently it's on your end, because many people reported no issues. Please make sure you followed the guide to the tee.
Click to expand...
Click to collapse
Thanks...yes I also have no blue logo, the logo looks normal (white and orange). I have ordered a factory cable and will try that way.... any tips on this that is NOT covered already in your thread?
Thanks alot
Christiansloth said:
Thanks...yes I also have no blue logo, the logo looks normal (white and orange). I have ordered a factory cable and will try that way.... any tips on this that is NOT covered already in your thread?
Thanks alot
Click to expand...
Click to collapse
Not that I know of. Once you get the cable, it's simple. Use the restore tool linked in my guide, and follow instructions.
seokhun said:
Not that I know of. Once you get the cable, it's simple. Use the restore tool linked in my guide, and follow instructions.
Click to expand...
Click to collapse
Hi again,
I have not gotten hold of the factory cable, and have tried to run the restore tool here: http://forum.xda-developers.com/showthread.php?t=1951254
However, even if it seems to work fine and the img. file is copied, there is no change in the device: it still runs a boot loop with the orange Kindle logo going on and off.
I can get the festboot logo on the screen by plugging in the factory cable, but not sure what to do now?
Would be grateful for any advice...
Christiansloth said:
Hi again,
I have not gotten hold of the factory cable, and have tried to run the restore tool here: http://forum.xda-developers.com/showthread.php?t=1951254
However, even if it seems to work fine and the img. file is copied, there is no change in the device: it still runs a boot loop with the orange Kindle logo going on and off.
I can get the festboot logo on the screen by plugging in the factory cable, but not sure what to do now?
Would be grateful for any advice...
Click to expand...
Click to collapse
Ask in that thread, I've never used the tool, so I wouldn't know.
seokhun said:
Ask in that thread, I've never used the tool, so I wouldn't know.
Click to expand...
Click to collapse
Hi again again,
I got it running again....
In your guide step 4, it says to copy the ROM and Gapps to the sdcard.... is it the zip file there has to be copied or the unzipped files?
Thanks again.
C
Christiansloth said:
Hi again again,
I got it running again....
In your guide step 4, it says to copy the ROM and Gapps to the sdcard.... is it the zip file there has to be copied or the unzipped files?
Thanks again.
C
Click to expand...
Click to collapse
The zip itself. Both come in as zip files, move those to the sdcard in zip form.
Ok so I have an Atrix HD that I rooted then went to install paranoid android on here. I made the mistake to try and install using Factory Recovery. So it threw an error in Fastboot. I used Myth Tools to get it back to stock. Then used Myth to install CWM Root it and unlock bootloader. Then went to install paranoid android again... Everything seemed to be going well but it just stayed on the Glowing X for 10-15 minutes. Knew something was up with it not loading into OS by then. So I tried to reinstall it again. No luck. Tried to use Myth Tools to go back to factory. Would just stay at Dual Core logo and do nothing. I went back in and installed CWM and tried to install Pacman Rom and it just stays at Pac is loading.
Fastboot still shows Bootloader as unlocked as it should, but is this the reason why Myth could not get me back to factory? I just want to get it back to factory at this point and worry about Rooting and installing Rom later. I have been searching and trying anything I can find on here, and droid razr forum. As well as various other sites and artices i find from google. I am at a lose. Have I bricked it enough to not come back from this or am I just missing something simple? I am looking for insight or help to get me in the right direction. I am on day 3 now off trying to get it running again.
I have tried in CWM formating Cache and re mounting it in Advance, Also have tried formating system, cache, davik cache... I did receive the can not mount errors but having formatting cache and remounting i did not get the error again.
Just take it a step at a time. Get it booted into stock first.
Sent from my MB886 using xda premium
darknessrise1234 said:
Just take it a step at a time. Get it booted into stock first.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
but where to begin? Trying to get it back to stock is not working even though Myth Tools. It states it finished I do not get any errors through Fastboot yet it stays on Dual Core never moves as if it is bricked.
DeVoe41 said:
but where to begin? Trying to get it back to stock is not working even though Myth Tools. It states it finished I do not get any errors through Fastboot yet it stays on Dual Core never moves as if it is bricked.
Click to expand...
Click to collapse
read this
http://forum.xda-developers.com/showthread.php?t=2226527
Make sure you have the adb drivers installed on your computer and I've noticed this phone is weird about chargers find one that works for data too. U will know cause if you have adb installed through myth tools and you reboot into fastboot mode then your computer will recognize it. Make sure the only thing in the firmware folder in myth tools is your .zip whatever stock att firmware you want. Then in myth tools install stock and make sure you type in the response 2 when it asks if you are in fastboot mode or normal. Fastboot is choice 2. I'm a flashaholic I've tried every rom in our development forum lol. I have bricked my AHD more times then anyone should this always worked for me. Try these things see if they help
Sent from my MB886 using xda app-developers app
Clean Flash
DeVoe41 said:
Ok so I have an Atrix HD that I rooted then went to install paranoid android on here. I made the mistake to try and install using Factory Recovery. So it threw an error in Fastboot. I used Myth Tools to get it back to stock. Then used Myth to install CWM Root it and unlock bootloader. Then went to install paranoid android again... Everything seemed to be going well but it just stayed on the Glowing X for 10-15 minutes. Knew something was up with it not loading into OS by then. So I tried to reinstall it again. No luck. Tried to use Myth Tools to go back to factory. Would just stay at Dual Core logo and do nothing. I went back in and installed CWM and tried to install Pacman Rom and it just stays at Pac is loading.
Fastboot still shows Bootloader as unlocked as it should, but is this the reason why Myth could not get me back to factory? I just want to get it back to factory at this point and worry about Rooting and installing Rom later. I have been searching and trying anything I can find on here, and droid razr forum. As well as various other sites and artices i find from google. I am at a lose. Have I bricked it enough to not come back from this or am I just missing something simple? I am looking for insight or help to get me in the right direction. I am on day 3 now off trying to get it running again.
I have tried in CWM formating Cache and re mounting it in Advance, Also have tried formating system, cache, davik cache... I did receive the can not mount errors but having formatting cache and remounting i did not get the error again.
Click to expand...
Click to collapse
I have a suspicion that for some odd reason, as Mythtools probably should have taken care of this, that there are some lingering files and caches that would cause any rom to fail upon install. I just posted something about this earlier today.
Read my post on this thread:
http://forum.xda-developers.com/showthread.php?t=2394238
PM me with any questions or problems and click the Thanks button if I helped.
I'm sorry I forgot to update I was able to get the phone working just had to do it through command prompt forcing you to file . The issue I had was using safestrap to install a ROM which somehow killed root access and the bootloader was not unlocked so and pretty much bricked the phone.
Sent from my MB886 using xda app-developers app
For recent custom roms, you must use a CWM with an unlocked bootloader.
Hi -
I have searched these forums multiple times, had numerous brower tabs open trying to follow instructions, and am at wits end. I am hoping that someone here can help me. I have a Kindle Fire HD 7" which had version 7.5.1 on it. I've rooted, tried using Fireflash to flash TWRP, bricked it twice, recovered it (with the fastboot cable that arrived in the mail 2 days ago), and now I am unable to switch on wifi (I did see the recent thread about this). I'm not sure what I'm doing wrong. The first two times before flashing the TWRP, I did not downgrade to 7.2.3. Could that have been why it bricked both times?
I just did another reset to factory defaults to try to get wifi back, to no avail. I am doing all of this so that I can install a ROM to escape all of the Amazon interface limitations.
Edit: I should add that I have so many files downloaded now (different versions, per each set of instructions) that I am confused.
Update: I just used SRT_v1.3.0 to restore factory recovery and now my wireless is enabled!
I am afraid to use Fireflash to flash TWRP again after two failures.
Thank you for any and all input!
PnGa
NM: Got it working.
Pickngrin said:
NM: Got it working.
Click to expand...
Click to collapse
HOW?? FOR GODS SAKE HOW???
I'm in the same boat, just bricked it now I think, red screen when turning on, thats it
Don't panic... get a factory (Fastboot) cable and use the Unbrick app to revive it. I took so many attempts to get it successfully flashed with CM12. I believe that I was using the incorrect boot image file and had not downgraded to 7.2.3 first. But I don't really understand the whole process. Good luck!
Pickngrin said:
Don't panic... get a factory (Fastboot) cable and use the Unbrick app to revive it. I took so many attempts to get it successfully flashed with CM12. I believe that I was using the incorrect boot image file and had not downgraded to 7.2.3 first. But I don't really understand the whole process. Good luck!
Click to expand...
Click to collapse
Cheers mate... I will try and find out to make one...
So i wanted to install CyanogenMod on my kindle fire 2, because the os amazon provides is horrible. Before i could install any roms, i had to root and install a custom recovery. I found a one-click way to do it here, and it must have failed, but the device was still on, so i manually restarted it. When it booted up, it briefly showed the kindle bootlogo, then switched to a solid red/orange full screen. I would really like help fixing this. Please help. (BTW, i do have root access.)
copycat114 said:
So i wanted to install CyanogenMod on my kindle fire 2, because the os amazon provides is horrible. Before i could install any roms, i had to root and install a custom recovery. I found a one-click way to do it here, and it must have failed, but the device was still on, so i manually restarted it. When it booted up, it briefly showed the kindle bootlogo, then switched to a solid red/orange full screen. I would really like help fixing this. Please help. (BTW, i do have root access.)
Click to expand...
Click to collapse
the TweezerMod forum says that it's only useful for the older bootloader. Go ahead and download and flash the bootloader file from Hash's thread here as directed. You really should get a factory cable if you don't already have one, as you'll need one to get into fastboot to flash the bootloader. After this, reboot and try to get into TWRP. If it works, TweezerMod mostly worked. If not, you'll need to do the entire flashing process manually.
Sent from my Amazon Jem using XDA Labs
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!