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.
Related
First of all I apologize if there is a fix somewhere on this forum for this (I searched and was unable to find any) I am pretty newbish so please try to make things simple. Now let me explain what happened I booted into TWRP to install kinoligy I followed the steps very closely and did everything right. Then I rebooted and everything seemed to be going fine and then my device loaded TWRP and I wasn't pressing the up volume key I have tried rebooting many times and it still refuses to just boot into the OS. PLEASE help and thanks in advance!
Cytherea said:
First of all I apologize if there is a fix somewhere on this forum for this (I searched and was unable to find any) I am pretty newbish so please try to make things simple. Now let me explain what happened I booted into TWRP to install kinoligy I followed the steps very closely and did everything right. Then I rebooted and everything seemed to be going fine and then my device loaded TWRP and I wasn't pressing the up volume key I have tried rebooting many times and it still refuses to just boot into the OS. PLEASE help and thanks in advance!
Click to expand...
Click to collapse
That's because there is no OS to begin with. Did you leave out some files that you had to download? All the steps? You had to flash everything in order, all of those files.
seokhun said:
That's because there is no OS to begin with. Did you leave out some files that you had to download? All the steps? You had to flash everything in order, all of those files.
Click to expand...
Click to collapse
I've followed the steps, reading over them many times before hand and I am having the same problem. I booted fine after I was finished, then went to check twrp. Once booted in twrp, I rebooted and it continues to load in twrp, I don't know why.
I've got an Atrix HD and I've been trying to flash HoloBlur since a while now.
I'm presently on 4.1.1 (98.4.20.MB886.ATT.en.US).
I used the Motochopper tool to gain root access. Success.
I used the Motoapocalypse tool to unlock bootloader. Success.
I've used the Myth Tools to flash the inbuilt CWM as well as other versions of it. I've also tried installing CWM through fastboot. All of the methods which I use tell me that the recovery was flashed successfully. However I cannot enter recovery mode at all. I've used to Myth Tools to enter recovery. Failure. I've powered down and tried the Vol-Up and Power button combination. Failure. I just get the image of the dead Android.
Also, in the fastboot mode, pressing the Vol-Up or Vol-Down buttons does not do anything.
I know for sure that I'm rooted. The Super User app is fully active. I've removed AT&T bloatware to confirm this. The app is fully functional.
I also am certain that the bootloader is unlocked. I've verified this through the fastboot mode.
I don't have a clue about what am I doing wrong. I just cannot enter recovery mode at all.
Any help regarding this will be greatly appreciated!
Reinstall cwm through adb? Is the phone still working?
Sent from my MB886 using Tapatalk 4
salafra 367
The phones working perfectly fine. The only problem is that I can't enter recovery mode no matter what. I've tried flashing recoveries through fastboot, adb, toolkits, everything. The phone merely shows the dead Android when it enters recovery.
Rabie Haider said:
The phones working perfectly fine. The only problem is that I can't enter recovery mode no matter what. I've tried flashing recoveries through fastboot, adb, toolkits, everything. The phone merely shows the dead Android when it enters recovery.
Click to expand...
Click to collapse
Try starting from scratch using RSD Lite to flash yourself back to stock. Then begin the process again, minus unlocking the bootloader, since you already did that.
I really don't want to do that. Since I dont have access to any recovery at this time, I cant make a Nandroid backup. Which means in case things go bad with the flashing, Ill be stuck with a bricked phone.
did u rename the file install_recovery.sh?
devilsking said:
did u rename the file install_recovery.sh?
Click to expand...
Click to collapse
No. However I just tried doing this.
I downloaded CWM Touch 6.0.3.6 from m0ndul's thread.
I extracted the package. Copied the recovery image to moto-fastboot folder as well as recovery folder for Myth Tools.
I entered fastboot and used 'fastboot flash recovery recovery.img'. Fastboot gave me success notification.
I restarted the phone and entered recovery. The phone shows the dead Android image.
So then I renamed the file to 'install-recovery.sh' in both fastboot and Myth folders.
Both fastboot and Myth Tools give me success notification.
However on entering recovery the same dead Android image comes up. :crying:
You should definitely RSD or MythTools back to complete stock and do the process over again, as mentioned above. It is the only conceivable fix to this strange problem at the time. As long you don't unplug the chord during RSD flashing then nothing will go wrong, I've had to do it about 3 times. I may be wrong, but I'm pretty sure that if an RSD flash was unsuccessful you wouldn't be able to use that nandroid backup in the first place, fastboot would be pretty much the only place you can go.
Even if it didn't work (very highly unlikely), this is another way to do it that will definitely work: http://forum.xda-developers.com/showpost.php?p=40929335
Here's all you need: http://sbf.droid-developers.org/dinara/list.php The third ATTUS and the Mexico Retail are the only two that will work.
I have the AT&T model as well and I have used the Mexico Retail zip every time without fail.
Replace the XML file inside of the zip with this one so that it flashes properly: https://www.box.com/s/num1eshkf0c2or2h4160
It is completely safe, just don't do it during shceduled power outages, storms, don't touch the data cable, and let it do its thing until it boots back up.
Can you boot your phone? If you can, install Root Explorer and change the recovery file name by adding .bak to the end, then try to install cwm.
Neighbor808 said:
You should definitely RSD or MythTools back to complete stock and do the process over again, as mentioned above. It is the only conceivable fix to this strange problem at the time. As long you don't unplug the chord during RSD flashing then nothing will go wrong, I've had to do it about 3 times. I may be wrong, but I'm pretty sure that if an RSD flash was unsuccessful you wouldn't be able to use that nandroid backup in the first place, fastboot would be pretty much the only place you can go.
Even if it didn't work (very highly unlikely), this is another way to do it that will definitely work: http://forum.xda-developers.com/showpost.php?p=40929335
Here's all you need: http://sbf.droid-developers.org/dinara/list.php The third ATTUS and the Mexico Retail are the only two that will work.
I have the AT&T model as well and I have used the Mexico Retail zip every time without fail.
Replace the XML file inside of the zip with this one so that it flashes properly: https://www.box.com/s/num1eshkf0c2or2h4160
It is completely safe, just don't do it during shceduled power outages, storms, don't touch the data cable, and let it do its thing until it boots back up.
Click to expand...
Click to collapse
SOLVED!
I followed instructions from the CWP thread by some other members.
I've had dozens of Androids and I've flashed things hundreds of times but nothing got as messy as AHD did.
In short, bootloops, nuclear warfare and whatnot later, I'm running HoloBlur.
Thanks a million for your assistance.
Rabie Haider said:
SOLVED!
I followed instructions from the CWP thread by some other members.
I've had dozens of Androids and I've flashed things hundreds of times but nothing got as messy as AHD did.
In short, bootloops, nuclear warfare and whatnot later, I'm running HoloBlur.
Thanks a million for your assistance.
Click to expand...
Click to collapse
How did you fix it?
UPDATE:
Nevermind... JUST Remove ~/system/etc/install-recovery.sh it keeps on overwriting the recovery when you boot.
Just That?
MGA2009 said:
How did you fix it?
UPDATE:
Nevermind... JUST Remove ~/system/etc/install-recovery.sh it keeps on overwriting the recovery when you boot.
Click to expand...
Click to collapse
Just that?
you did the whole thing to replace files on the rsd thing? or this is the noobsafe method to get into the recovery?
BTW i'm noob...
clopezloud said:
Just that?
you did the whole thing to replace files on the rsd thing? or this is the noobsafe method to get into the recovery?
BTW i'm noob...
Click to expand...
Click to collapse
That's way to install custom recovery since renaming that file is the necessary step before flashing custom recovery.
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
Hello everyone.
I don't know what happened but my device entered in the infamous bootloop. I tried to erase cache, partition, reinstall a rom, install a different rom and nothing.
My true problem is that last night I made a horrible mistake: I erased everything including my SD card, which contained the data for boot to recovery. Right now I can only see the SONY logo when I power up my device and nothing else.
I tried to install recovery via fastboot flash boot boot.img but I can't keep my device in fastboot. I mean, I connect my device and hold Volume Up but after a few seconds it continuous to the SONY logo and stays there forever.
Am I missing something? What can I do to reintall a recovery if I can't access my phone data?
Thank you.
How to install recovery in a phone which can't start [Solved]
I just figured it out! I installed Sony's stock rom following this guide and my phone is alive again.
bbabel said:
I just figgured out! I installed Sony's stock rom following this tutorial and my phone is alive agaoin.
Click to expand...
Click to collapse
Good you managed to fix it and posted it back here with a solution. So few people do it. On the side note, link you provided does not work, please fix if you can
kwitu said:
Good you managed to fix it and posted it back here with a solution. So few people do it. On the side note, link you provided does not work, please fix if you can
Click to expand...
Click to collapse
Thank you. I just fixed the link and now it works.
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...