TWRP and FFF Installed; Cannot Boot Fully - Kindle Fire Q&A, Help & Troubleshooting

Thanks in advance for the help. Like many others I have searched for something similar to what I am experiencing but have not had luck finding it. So here goes my "special" situation:
Background:
-I use a PC with Windows 7 installed
-I downloaded KFU (v. 0.9.6) and ran install_drivers
-Connected KF and ran "run"
-Selected Option 2 for a Permanent Root with Superuser
-I am not sure if this step fully worked because during the root it seemed like my PC and KF disconnected from each other and my PC flashed a message about "smartphone no attached" that I didn't catch the exact verbiage of
-I restarted my KF and found myself in the TWRP (v. 2.2.0) interface
-Followed directions from another post and selected "reboot" and then "system"
-This worked and it loaded the familiar KF home screen
-From here I again ran the "run" file from KFU
-This time I selected Option 6 for extras, then Option 1 for Google Apps / Go Launcher Ex
-The ADB Status was Online and away the install went
-Here I am not totally sure what happened, but I believe a similar problem happened as before with m PC and KF losing connection during install
-Either way, I landed on the KF boot screen (blue Fire, which implies I have FFF installed v. 1.4);
-It was stuck here so I tried the Unbrick Utility and several other suggestions from posts and was once again able to get back to the TWRP interface
-Here, I thought I had everything figured out and again navigated to "reboot" and then "system"
-This time however, I did not go back to the KF home screen and instead got right back to the TWRP interface
-It almost seemed like it tried to load the home screen (yellow word "fire"); but quickly restarted again and went back to the blue fire and then the TWRP interface
-From here, I have tried several different approached to no avail, but here is the state I am in to the best of my knowledge:
1. It appears I have FFF and TWRP installed
2. I may or may not have the Google Aps installed
3. My drivers are all still installed, but the only time my computer recognizes it is the split second when the yellow word "fire" comes up on a system reboot.
I think I am close, but maybe not. Any help is greatly appreciated and let me know if I need to provide more information. Tried to be thorough but this is my first crack at this.

hold the power button down for 20 seconds then power on when you see the white kindle blue fire press your power button to get boot menu
then select recovery from the boot menu with the power button
Download this rom http://forum.xda-developers.com/showthread.php?t=1439916
select mount in twrp transfer this rom zip to your sd card but dont place it in a folder
then select unmount
go to install make sure you can find it
then hit the home button select wipe
wipe factory reset
wipe cache
wipe dalvik
wipe system
then go home again
select install again tap on rom zip flash it let it finish
then select reboot
enjoy your lovely rooted kindle fire
this is just rooted stock with playstore if you wish to try other roms use the same method with the exception of making a backup first

Thepooch said:
select mount in twrp transfer this rom zip to your sd card but dont place it in a folder
then select unmount
go to install make sure you can find it
Click to expand...
Click to collapse
Thanks for the help! I have the ROM downloaded but am still cannot get my KF to be recognized on my PC to transfer files. Any suggestions on how to get the two to communicate?

Linux LiveUSB plus this:
http://forum.xda-developers.com/showpost.php?p=30629067
---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------
...or you could just pay attention to the directions Thepooch gave you. Just a thought.

soupmagnet said:
Linux LiveUSB plus this:
http://forum.xda-developers.com/showpost.php?p=30629067
...or you could just pay attention to the directions Thepooch gave you. Just a thought.
Click to expand...
Click to collapse
Thanks for getting back to me once more. I did try the directions Thepooch gave me exactly and no connection. Mounting did not allow my KF to connect. I also went into Linux and tried your code to get my KF to connect to my PC. I am no pro, but it seemed your first script just displayed a string and was rather frustrating. Inside one of the folders appeared to be a more complete script (with options 1 and 2) that your "READ ME" instructions hinted at (install_it file). I must be missing something. Would you be willing to provide more guidance on the Linux connection?
I appreciate all the help.

Yeah double click on runit then run in terminal.... Hit selection number 1 hit enter when it prompts for password... let it finish. ...Then hit selection number 2.... Then enter a y hit enter it will reboot.. Then try adb devices in a terminal..

SOLVED!
Thepooch said:
Yeah double click on runit then run in terminal.... Hit selection number 1 hit enter when it prompts for password... let it finish. ...Then hit selection number 2.... Then enter a y hit enter it will reboot.. Then try adb devices in a terminal..
Click to expand...
Click to collapse
Thanks to both of you for all the help! These little added details helped me through the home stretch. I still did not use the ""run_it.sh" script in terminal. I went straight to the "install_it.sh" file. I then followed your directions and had no troubles. The only change I had to do was manually toggle by booting selection after it kept rebooting to TWRP.

noobathon said:
Thanks to both of you for all the help! These little added details helped me through the home stretch. I still did not use the ""run_it.sh" script in terminal. I went straight to the "install_it.sh" file. I then followed your directions and had no troubles. The only change I had to do was manually toggle by booting selection after it kept rebooting to TWRP.
Click to expand...
Click to collapse
I think I'm going to have to change the title of that thread. I really did have faith in people.
There are instructions in that thread and in the README, and nowhere does it say to run any script other than "run_it.sh". There are separate sets of scripts for good reason.
If you had paid attention to the OP, you would have found what to do in your particular situation.

Related

TWRP loop and KFU problems

I just got a Kindle Fire from a relative that wanted root access, and have performed several in the past without incident. When I was trying to use KFU to root with Superuser ("#2 option"), I accidentally bumped my booby-trapped keyboard's sleep mode button which shut off the monitor. When I turned it back on, I didn't realize my wifi disconnected and I entered option #2 to root (I'm not even sure internet access is relevant to the process). I immediately got errors which caused my Kindle Fire to get stuck at the splash screen. Using KFU, I changed the boot back to normal with option #1. Upon resuming root w/ superuser (that is, after selecting #2), it started rebooting and whatnot but got hung up at a point. KFU says "Attempt to remove root checker. / mv: can't rename 'system/bin/check_rooted': No such file or directory. / Please wait..." and never finishes. Meanwhile, my Kindle is stuck on the TWRP screen with Install, backup, etc. and won't move past. I have never experienced this screen before with the other roots that I have done; it just moves right into normal display after KFU does it's thing. Being the self-proclaimed techy that I erroneously think I am, I rolled up my sleeves and immediately googled a bootloop fix that seemed to be common with TWRP (command prompt > "adb shell" > changing boot to 4000), but I couldn't get the results the original poster got (I switched my environmental variables to allow for it, but still nothing). Against my better judgement, I will include that I got TWRP to let me into normal Kindle Fire operations and I factory reset it (which is fine, because it was factory to begin with) but TWRP is still showing up. I would have just played it safe and handed it back to my relative without root, but I'm not sure they could get past TWRP boot, and I wouldn't even want to do that to them if it was unavoidable. I have included everything I think was relevant to my troubles, and would be greatly appreciative if someone can glean from what I've done my level of understanding and guide me through this BS. A routine magic trick that I share with my less-tech-savvy family and friends has turned into a headache. To be clear, my question is how do I either A) get rid of TWRP (which seems like taboo from what I've read so far), or B) get back to a condition where I can start the whole rooting process over without interruptions, as I feel that is why I am in this mess. The goal is to get the Kindle Fire to a point where all my relative has to do is turn it on and go (no TWRP screens, bootloops, etc.) I can handle what follows after KFU rooting (namely, installing google market.....nothing like CM7 and the like.) Thank you.:good:
Whewww that a lot k well your best bet is to flash fff in twrp from this link only http://forum.xda-developers.com/showthread.php?t=1632375 by simply mounting the sdcard and transferring fff to it and flashing then power off get back into recovery by pressing the button a few times when you see the white kindle blue fire logo select recovery then mount SD again and transfer this rom in zip form of course http://forum.xda-developers.com/showthread.php?t=1439916 not the alt version that's for dual boot then wipe factory reset , wipe cache , wipe dalvik , wipe system then return to home screen of twrp select install flash rom when done reboot then system if prompted that's it.. wait for boot pass off the beautifully rooted kindle fire to your family member..
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
Google android market will be located in apps no more tampering needed modaco is nothing but rooted stock with Google play
Yeah, sorry. I just wanted to be complete, and I wasn't sure how much information would end up being useful. I'll let you know how it goes, and thanks for the reply!
Try this...
Acquire FireFireFire 1.4.zip and transfer it to your sdcard. Boot into twrp and install FireFireFire1.4.zip. Search the FFF thread for information on how to use it. I think that will either fix most of your problems or set it up to fix them easily
Sent from my Galaxy Nexus using Tapatalk 2
Thepooch said:
Whewww that a lot k well your best bet is to flash fff in twrp from this link only http://forum.xda-developers.com/showthread.php?t=1632375 by simply mounting the sdcard and transferring fff to it and flashing then power off get back into recovery by pressing the button a few times when you see the white kindle blue fire logo select recovery then mount SD again and transfer this rom in zip form of course http://forum.xda-developers.com/showthread.php?t=1439916 not the alt version that's for dual boot then wipe factory reset , wipe cache , wipe dalvik , wipe system then return to home screen of twrp select install flash rom when done reboot then system if prompted that's it.. wait for boot pass off the beautifully rooted kindle fire to your family member..
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
Google android market will be located in apps no more tampering needed modaco is nothing but rooted stock with Google play
Click to expand...
Click to collapse
At the risk of coming off ignorant, I am going to clarify what I need to do so I don't dig my hole even deeper. Please excuse me
I used the first link to download FFF. It came with the folders "cache" and "META-INF" and the single file "padfile". I assume mounting the SD card needs to be done through the TWRP screen, or do you mean on the Kindle Fire itself? Which part of the FFF download needs to be transferred to the SD card; the contents of "cache" or "META-INF", the padfile, or all of it? Do I just drop it onto the SD card, or does it have to be put somewhere special?
I understand how to get into Recovery mode on TWRP, and I will again assume that I need to mount the sd card in TWRP. What contents from the second link (Modaco) do I need to put on sd card, and where (if somewhere special)? It downloaded as a .zip, so should I just leave it that way and drop it onto the sd card?
I saw on TWRP where to wipe everything you mentioned, so I think I got it covered there. Also how to install flash rom.
You mentioned that Modaco already has google play, so I am going to also assume that this will conclude the fix, unless something unexpected pops up. I will try to work through your suggestion, but if you can let me know if any of my understanding is incorrect, I would be very much obliged!
I see that the SD mounting will probably come from within TWRP itself, since I will need to use "Install" for the rom flash, but I am still confused as to how to transfer it over and where it needs to go inside of SD card if there are any special rules for it.
Do not unzip the file! Place the .zip file on your sdcard as is and install it with twrp as you would a rom...no wipes
Sent from my Galaxy Nexus using Tapatalk 2
soupmagnet said:
Do not unzip the file! Place the .zip file on your sdcard as is and install it with twrp as you would a rom...no wipes
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Are you referring to your own suggestion soupmagnet, or my question about what to do with the FFF or Modaco .zip? If it's a reply to my question, should I just leave both of them zipped, or just the Modaco one, or what? How do I place them on my SD card for that matter? Through TWRP (which I don't think I know how to do) or onto the Kindle Fire directory on My Computer? I've never installed anything with TWRP; in the past, I've never had to use the screen that I'm seeing now ;p Should I not use any wipes as the first reply suggested? I am confusing myself at this point.
fff you flash in zip form you don't unzip it no wipes needed a rom you wipe prior and then flash in zip form as well
I am seeing on the Modaco website that wipe is not required.
Not for you ... you must wipe...
Thepooch said:
Whewww that a lot k well your best bet is to flash fff in twrp from this link only http://forum.xda-developers.com/showthread.php?t=1632375 by simply mounting the sdcard and transferring fff to it and flashing then power off get back into recovery by pressing the button a few times when you see the white kindle blue fire logo select recovery then mount SD again and transfer this rom in zip form of course http://forum.xda-developers.com/showthread.php?t=1439916 not the alt version that's for dual boot then wipe factory reset , wipe cache , wipe dalvik , wipe system then return to home screen of twrp select install flash rom when done reboot then system if prompted that's it.. wait for boot pass off the beautifully rooted kindle fire to your family member..
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
Google android market will be located in apps no more tampering needed modaco is nothing but rooted stock with Google play
Click to expand...
Click to collapse
This is what I'm about to do as succinct as I can be (as per Thepooch's instructions):
1. Download FFF from the first link. Keep it .zip
2. Transfer FFF by mounting SD within TWRP menu.
3. Flash fff
4. Power off.
5. Enter Recovery TWRP.
6. Mount SD again, then transfer .zip Modaco (not the alt version)
7. Wipe factory reset, wipe cache, wipe dalvik, wipe system.
8. Install Modaco rom
9. Reboot
10. Give to family member and refuse all other requests
Flash fff before powering off.. flash fff before powering off or rebooting guess that better
Crap we made it to thread page 2. I really didn't mean to make this harder than it had to be, I just wanted to be sure of what needed to be done. Thanks again gents for all the input
Mmm, incredible Everything appears to be in order. No TWRP screen and Google Play is included. Thank you so much for the fix. Not completely sure what went wrong, but glad you knew how to get around it. Omne ignotum pro magnifico!
Solved.:highfive:
OK now try to access recovery again to make sure the bootloader works as it should
---------- Post added at 11:02 PM ---------- Previous post was at 10:58 PM ----------
Also now create a backup something you could not do before because I believe the system was broken
Entered recovery without any problems. Created a backup, as well. Every boot since has gone straight to Kindle Fire; no TWRP menu Excellent, because it would have been a pain to explain that whole process to my relative. Great stuff!
Glad it worked everyone's happy no harm done
Help!
Hi, I am hoping someone can help me. I came across this thread because I was having and identical problem, but unfortunately, I am not having the same result. If anyone can help me I would greatly appreciate it. These are the steps I carried out based on what I got from this thread.
1. Downloaded fff-u-boot_v1.4a and Gr9.2-update-modacocustomrom-kindlefire-unsigned-MD5 zip, placed it on the root of the SD card
2. In TWRP, I entered install and selected the zip.
3. From that screen I hit reboot.
4. I went to Reboot->Recovery
5. Wiped factory reset, cache, dalvik, system.
6. Installed Gr9.2-update-modacocustomrom-kindlefire-unsigned-MD5-569fe6550cfcfba68dabc3d088324a46.zip file
8. Rebooted...
But after all this it went right back into TWRP. I am sure I am just missing something obvious, please help.
WasabiPeanut said:
Hi, I am hoping someone can help me. I came across this thread because I was having and identical problem, but unfortunately, I am not having the same result. If anyone can help me I would greatly appreciate it. These are the steps I carried out based on what I got from this thread.
1. Downloaded fff-u-boot_v1.4a and Gr9.2-update-modacocustomrom-kindlefire-unsigned-MD5 zip, placed it on the root of the SD card
2. In TWRP, I entered install and selected the zip.
3. From that screen I hit reboot.
4. I went to Reboot->Recovery
5. Wiped factory reset, cache, dalvik, system.
6. Installed Gr9.2-update-modacocustomrom-kindlefire-unsigned-MD5-569fe6550cfcfba68dabc3d088324a46.zip file
8. Rebooted...
But after all this it went right back into TWRP. I am sure I am just missing something obvious, please help.
Click to expand...
Click to collapse
You almost got it. When you install a ROM and want to boot to it from recovery, select "reboot system". You can still change your bootmode on the fly with FFF1.4 by holding the power button when you see the Kindle Fire logo until you see the boot options appear at the bottom.

Friend Gave Me Bricked Kindle Fire (NEED HELP)

Hello everyone I am new to these forums and I was hoping that some one here would be able to help me with my issue. Ok so here is the story, my friend some how bricked his Kindle Fire and was so frustrated with trying to fix it that he ended up giving it to me. This situation is what brought me to these forums. I have no experience with the Kindle Fire but from digging around on the internet I have managed to figure out that my friend tried to mod it or something like that but let me get to the main issue.
The Kindle Fire powers on and shows a little triangle with a flame inside of it and below that there is a prompt that says something like press the power button for recovery. Upon pressing the power button the screen flashes revealing a background that says TEAMWIN which quickly disappears and reveals a new screen with several touch button options. On the top left hand corner TWRP and the android icon are displayed and following that it says, "Team Win Recovery Project (twrp) v2.0.0". The first thing I noticed was the restore button but upon clicking that it asks me to select a package to restore but there are no options to select.
This is all the information I have so far but if anyone here is willing to help me I will gladly do my best to provide more.
TeamWin
Well you're less screwed than you think. In TWRP - are you able to manually navigate the folders to download(s) and in there is there a .zip file that is about 115MB that is named something like this: jb-4.2-kfire-hashcode-2013-01-22.zip
If so, flash that, if not, you'll need to install Kindle Fire Toolkit on your PC (not Mac ) and push this file: goo.im/devs/Hashcode/otter/aosp/jb-4.2-kfire-hashcode-2013-01-22.zip
to the Kindle while it is in ADB mode
Oh man not to be harsh but wipe before flashing. Wipe factory reset, wipe cache, wipe dalvik, wipe system, flash rom.zip, flash gapps.zip select reboot then system if prompted.
goodluck and godspeed
Sent from my Amaze 4G using Xparent ICS Tapatalk 2
SergioRSchubert said:
Well you're less screwed than you think. In TWRP - are you able to manually navigate the folders to download(s) and in there is there a .zip file that is about 115MB that is named something like this: jb-4.2-kfire-hashcode-2013-01-22.zip
If so, flash that, if not, you'll need to install Kindle Fire Toolkit on your PC (not Mac ) and push this file: goo.im/devs/Hashcode/otter/aosp/jb-4.2-kfire-hashcode-2013-01-22.zip
to the Kindle while it is in ADB mode
Click to expand...
Click to collapse
Don't see any mention of having a rom on the device as a side note not even a restore point.
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
Connect to pc select mount in twrp then transfer the needed rom.zip and gapp.zip to the sdcard. Wipe as directed and flash the files you added after unmount and disconnect.
Thepooch said:
Don't see any mention of having a rom on the device as a side note not even a restore point.
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
Connect to pc select mount in twrp then transfer the needed rom.zip and gapp.zip to the sdcard. Wipe as directed and flash the files you added after unmount and disconnect.
Click to expand...
Click to collapse
Thank you everyone for your input, I greatly appreciate it. Like I said I really have no experiance with modded out kindles or any kindles at all for that matter but I messed around with it and figured out how to wipe and how to mount the kindle as a USB storage device so I am going to do that now. When I go to install, no matter where I browse to, all the folders are blank. I can not find a Kindle Fire Toolkit anywhere and I downloaded the goo.im/devs/Hashcode/otter/aosp/jb-4.2-kfire-hashcode-2013-01-22.zip but I have no idea what to do with it . I really appreciate you guys trying to help me and I apologize for the lack of knowledge on my part. I am going to try and find rom.zip and gapp.zip online, download those, wipe everything, and flash rom.zip and gapp.zip. I'll post my results when I am done.
ssj9dude said:
Thank you everyone for your input, I greatly appreciate it. Like I said I really have no experiance with modded out kindles or any kindles at all for that matter but I messed around with it and figured out how to wipe and how to mount the kindle as a USB storage device so I am going to do that now. When I go to install, no matter where I browse to, all the folders are blank. I can not find a Kindle Fire Toolkit anywhere and I downloaded the goo.im/devs/Hashcode/otter/aosp/jb-4.2-kfire-hashcode-2013-01-22.zip but I have no idea what to do with it . I really appreciate you guys trying to help me and I apologize for the lack of knowledge on my part. I am going to try and find rom.zip and gapp.zip online, download those, wipe everything, and flash rom.zip and gapp.zip. I'll post my results when I am done.
Click to expand...
Click to collapse
The jb-4.2-kfire hashcode-2013-01-22.zip is your rom.zip. what you have to do is transfer that over to the kindle fire from mounting the USB storage and then install it.
Sparx639
Sparx639 said:
The jb-4.2-kfire hashcode-2013-01-22.zip is your rom.zip. what you have to do is transfer that over to the kindle fire from mounting the USB storage and then install it.
Sparx639
Click to expand...
Click to collapse
Lol yea I figured it out AND...it looks like you guys helped me fix this thing. I followed the instructions of wiping everything and then flashing those two .zips and when I rebooted it the screen got passed the flame in a triangle logo and booted up. I am very grateful and there is no way I would have figured this out without you guys helping me . Thank you so much!
ssj9dude said:
Lol yea I figured it out AND...it looks like you guys helped me fix this thing. I followed the instructions of wiping everything and then flashing those two .zips and when I rebooted it the screen got passed the flame in a triangle logo and booted up. I am very grateful and there is no way I would have figured this out without you guys helping me . Thank you so much!
Click to expand...
Click to collapse
Sweet, enjoy the kindle!
Sparx639

[Q] COT only or stuck at Kindle Fire logos- No TWRP, ROM

Hi,
I previously rooted my Kindle and things were just peachy until I tried to wipe it to give to my husband. I must have gotten the happy fingers because I deleted everything. After about 6 days of reading through the various threads and trying different things, it will only boot to the Kindle Fire logo screen and it will go from blue and white to the orange one, but it hangs there. The alternate boot option or reset boot mode does not have any other outcome. If I change it to "recovery mode" it will only open into the Cannibal Open Touch v2.1 Meanwhile, back on the computer the Device Manager seems to recognize the Kindle and the adb driver, but the system does not respond when I try to run any of the utilities that I've used; nor does the system respond to any of my commands I attempt. With the KFU it will reboot the Kindle to the logo and then hang at "waiting for device" or boot me back up to the COT Recovery.
I think I have tried every sequence or option with COT but I'm not real sure what the options are supposed to be doing and in what sequence. Below is an image of what I am now able to get on Recovery boot to COT. Can someone help? Is it too late? is it permanently bricked?
Thanks!!!
cpeaches said:
Hi,
I previously rooted my Kindle and things were just peachy until I tried to wipe it to give to my husband. I must have gotten the happy fingers because I deleted everything. After about 6 days of reading through the various threads and trying different things, it will only boot to the Kindle Fire logo screen and it will go from blue and white to the orange one, but it hangs there. The alternate boot option or reset boot mode does not have any other outcome. If I change it to "recovery mode" it will only open into the Cannibal Open Touch v2.1 Meanwhile, back on the computer the Device Manager seems to recognize the Kindle and the adb driver, but the system does not respond when I try to run any of the utilities that I've used; nor does the system respond to any of my commands I attempt. With the KFU it will reboot the Kindle to the logo and then hang at "waiting for device" or boot me back up to the COT Recovery.
I think I have tried every sequence or option with COT but I'm not real sure what the options are supposed to be doing and in what sequence. Below is an image of what I am now able to get on Recovery boot to COT. Can someone help? Is it too late? is it permanently bricked?
Thanks!!!
Click to expand...
Click to collapse
COTR is the best recovery out there, and as long as you even have the worst recovery that functions, your device is certainly not bricked.
It would be better if you put your enthusiasm to have the KFU fix your kindle aside.
Step 1) Download MoDaCo Rom/Any other ROM BUT NOT ANY KITKAT ROM(COTR can NOT flash KitKat)
Step 2) Transfer your ROM while in recovery
Step 3) Do a preflash wipe
Step 4) Do a factory reset
Step 5) Go to 'Install -> Install from SD Card -> Folder where you put your ROM
Step 6) Click Install without Backup
Step 7) Boot Android
LIFE and SANITY Saver!!!
Thank you sooooooo MUCH!!!!
You made me proud of myself...
Everything worked like a charm with my Samsung S4 USB chord.
For the Install step I had to use the "Zip installation" option to see the file MoDaCo file I copied over. Once I did the fat lady was tuning up and in about 5 minutes she was delivering the most beautiful solo I had heard in quite sometime!!!!
MUCH APPRECIATED!!! :good::good::good:
cpeaches said:
Thank you sooooooo MUCH!!!!
You made me proud of myself...
Everything worked like a charm with my Samsung S4 USB chord.
For the Install step I had to use the "Zip installation" option to see the file MoDaCo file I copied over. Once I did the fat lady was tuning up and in about 5 minutes she was delivering the most beautiful solo I had heard in quite sometime!!!!
MUCH APPRECIATED!!! :good::good::good:
Click to expand...
Click to collapse
Yes, by install I meant 'Zip Flashing'
I forgot the functions and didn't see the pic, its been about a month I used COT as to flash KitKat I had to switch to TWRP 2.6.3.1
Nice to see you got it working!

Help! N7 stucked at loading screen while attempting to root

Hi all,
I tried to root my Nexus 7 according to this youtube link
http://www.youtube.com/watch?v=X1cD-JXRGX8
During the step to install" super SU", i copied the the "unzipped" version of the file into the device, and couldn't install it as per video.
So i tried restating the device to try to copy the right file to the device, but now it just stucked at the loading screen (circle & square alternating, not the X screen) and i couldn't power it off too.
What should i do? Help please! Thanks!
gooner4life said:
Hi all,
I tried to root my Nexus 7 according to this youtube link
http://www.youtube.com/watch?v=X1cD-JXRGX8
During the step to install" super SU", i copied the the "unzipped" version of the file into the device, and couldn't install it as per video.
So i tried restating the device to try to copy the right file to the device, but now it just stucked at the loading screen (circle & square alternating, not the X screen) and i couldn't power it off too.
What should i do? Help please! Thanks!
Click to expand...
Click to collapse
Is it still recognised by the computer?
As in, if you plug it in with USB does it appear on your device manager?
Anyway, I would recommend using Wug's Toolkit (http://forum.xda-developers.com/showthread.php?t=2389107) to sort you out.
It's pretty straight forward so you should be able to fix it easly.
username4this said:
Is it still recognised by the computer?
As in, if you plug it in with USB does it appear on your device manager?
Anyway, I would recommend using Wug's Toolkit (http://forum.xda-developers.com/showthread.php?t=2389107) to sort you out.
It's pretty straight forward so you should be able to fix it easly.
Click to expand...
Click to collapse
No it's not recognized by my PC too. So the toolkit won't be useful too i presume?
Any other options? Just wait it out till the battery is dead?
gooner4life said:
No it's not recognized by my PC too. So the toolkit won't be useful too i presume?
Any other options? Just wait it out till the battery is dead?
Click to expand...
Click to collapse
Your best bet is to try them.
Also give a look here:
http://forum.xda-developers.com/showthread.php?t=2544361
gooner4life said:
Hi all,
I tried to root my Nexus 7 according to this youtube link
http://www.youtube.com/watch?v=X1cD-JXRGX8
During the step to install" super SU", i copied the the "unzipped" version of the file into the device, and couldn't install it as per video.
So i tried restating the device to try to copy the right file to the device, but now it just stucked at the loading screen (circle & square alternating, not the X screen) and i couldn't power it off too.
What should i do? Help please! Thanks!
Click to expand...
Click to collapse
Long press the power button and that will make it reboot, as soon as the screen turns OFF, hold down the volume down button and it will boot into the bootloader, use the volume button to select recovery, press the start button to go into recovery. In recovery (TWRP) click on wipe then do a factory reset. If it is off, press and hold volume down and power button together and that will get you to the bootloader screen.
wantabe said:
Long press the power button and that will make it reboot, as soon as the screen turns OFF, hold down the volume down button and it will boot into the bootloader, use the volume button to select recovery, press the start button to go into recovery. In recovery (TWRP) click on wipe then do a factory reset. If it is off, press and hold volume down and power button together and that will get you to the bootloader screen.
Click to expand...
Click to collapse
This whole rooting process confuse me. So you're saying after doing this, just start over the rooting process as per youtube link again or continue the step where i did wrong?
P/S is it easier to root using that rootkit as per post above?
gooner4life said:
This whole rooting process confuse me. So you're saying after doing this, just start over the rooting process as per youtube link again or continue the step where i did wrong?
Click to expand...
Click to collapse
You're two thirds of the way there. You supposedly have the bootloader unlocked, you can see that when it boots up at the "Google" screen the lock will be unlocked, It will also say unlocked in the bootloader screen. And you should have TWRP installed if you tried to flash supersu. So.. at this point, you need to flash the supersu "zip" in TWRP. Before you start making any changes I would recommend making a backup in TWRP.
gooner4life said:
P/S is it easier to root using that rootkit as per post above?
Click to expand...
Click to collapse
What you are using is part of the android sdk (adb/fastboot), the platform-tools folder with the usb drivers moved into it, not really a toolkit. I've never used a toolkit so I can't say a lot about them, I have the complete sdk installed, you were using part of it. Were you able to boot into recovery and do a factory reset?
You should not have followed that guide.
1st: Go to here: http://forum.xda-developers.com/showthread.php?t=1538053. Download the zip. DO NOT UNZIP.
2nd: Make sure that ADB is set up on your computer. To download, go to https://developer.android.com/sdk/index.html. Follow the instructions to install. Open the SDK (should be in C\development\adt-bundle-windows-x86_64-20131030\, or whereever you installed, it is an execultable file. It should have a little green android logo next to it, and it is called "SDK Manager". It will take a couple seconds to open. Once it has opened, install "Android SDK Platform-tools".
3rd: Move the Super SU zip into the C\development\adt-bundle-windows-x86_64-20131030\sdk\platform-tools, or wherever you installed the platform-tools. It should be inside the SDK folder. Just paste the zip there.
4th: Boot your Nexus 7 into recovery. Push and hold the power button and volume down button at the same time and boot into the bootloader.
5th: Boot into recovery. Do so by pressing the power button for a while, and eventually it will shut off, as mentioned above.
6th: Press and hold power button and volume down to boot into bootloader. Once in the bootloader, push the volume down button until recovery is selected.
7th: Boot into recovery by pressing the power button.
8th: In recovery, wipe the cache and dalvik under the advanced wipe in the wipe menu. Go back and click install. Click "apply from sideload", or something like that, I forgot the exact wording. Connect your tablet to your computer through a USB cable.
9th: Go back to your computer. Go to C\development\adt-bundle-windows-x86_64-20131030\sdk\ or wherever you installed the sdk. Press shift, and then right click on the folder that says "platform-tools". In the menu, click "open command window here".
10th: Copy the exact name of the supersu zip file in the platform-tools folder.
11th: In the command window type: adb sideload UPDATE-SuperSU-v1.86.zip
12th: Press enter. The name of the super su file may not be exactly that, but similar to it.
13: Reboot your tablet.
I don't know if you are a noob, or very experienced, so I made this as noob-friendly as posisble, sorry if I offended you in any way. Here are some pictures.
I did manage to boot into bootloader screen 7 the option to start, but same thing happen, it still stucked at the "4 colors" circle screen. Problem is guys i couldn't get the PC to recognise my tablet even in the bootloader screen. What should i do now?
wantabe said:
You're two thirds of the way there. You supposedly have the bootloader unlocked, you can see that when it boots up at the "Google" screen the lock will be unlocked, It will also say unlocked in the bootloader screen. And you should have TWRP installed if you tried to flash supersu. So.. at this point, you need to flash the supersu "zip" in TWRP. Before you start making any changes I would recommend making a backup in TWRP.
What you are using is part of the android sdk (adb/fastboot), the platform-tools folder with the usb drivers moved into it, not really a toolkit. I've never used a toolkit so I can't say a lot about them, I have the complete sdk installed, you were using part of it. Were you able to boot into recovery and do a factory reset?
Click to expand...
Click to collapse
Ok i can boot to recovery mode and get to TWRP. But as my post above the superSU is not in zipped form, what should i do then? And i couldn't copy the zipped verison into the tablet as my PC won't recognise the tablet. Do i choose wipe to start all over again from scratch? (assuming that's what wipe will do?) or browse into subfolder of superSU "i.e. app, bin, etc, xbi" and install form there manually? Dam im confused without knowing any basic of rooting...I thnk you're the closest to understanding where i am now, please help! Thanks!
ok guys i think my N7 got some serious problem!!
Now it would just stucked on the Google screen and won't even go to the recovery mode!!!
What should i do now to reset it back to original state now?!!
gooner4life said:
Ok i can boot to recovery mode and get to TWRP. But as my post above the superSU is not in zipped form, what should i do then? And i couldn't copy the zipped verison into the tablet as my PC won't recognise the tablet. Do i choose wipe to start all over again from scratch? (assuming that's what wipe will do?) or browse into subfolder of superSU "i.e. app, bin, etc, xbi" and install form there manually? Dam im confused without knowing any basic of rooting...I thnk you're the closest to understanding where i am now, please help! Thanks!
Click to expand...
Click to collapse
Try and do a factory reset. Just remember a factory reset is not a restore and it will not put your device back to the way it was before you tried to root. A factory reset will wipe the cache and data, not the system. Any changes to the system, kernel or recovery that you made will still be there after a factory reset. Go ahead and dot a reset and let's see if that will get your N7 to boot up. And we can go from there.
wantabe said:
Try and do a factory reset. Just remember a factory reset is not a restore and it will not put your device back to the way it was before you tried to root. A factory reset will wipe the cache and data, not the system. Any changes to the system, kernel or recovery that you made will still be there after a factory reset. Go ahead and dot a reset and let's see if that will get your N7 to boot up. And we can go from there.
Click to expand...
Click to collapse
I might have stuffed up here mate, you might have missed my last post. I did a factory wipe, and tried to use the toolkit as suggested, and i'm now im deeper water where i can't even get into recovery mode. Everything just stucked between the "Google" screen and the "volume down + power" screen....gosh i really feel stupid now...Any more suggestions?
gooner4life said:
I might have stuffed up here mate, you might have missed my last post. I did a factory wipe, and tried to use the toolkit as suggested, and i'm now im deeper water where i can't even get into recovery mode. Everything just stucked between the "Google" screen and the "volume down + power" screen....gosh i really feel stupid now...Any more suggestions?
Click to expand...
Click to collapse
I did miss your last post. Holy crap what are you doing? You went from knee deep to drowning.
---------- Post added at 04:17 AM ---------- Previous post was at 04:16 AM ----------
What you're saying is that you can't get to the bootloader screen now?
wantabe said:
I did miss your last post. Holy crap what are you doing? You went from knee deep to drowning.
---------- Post added at 04:17 AM ---------- Previous post was at 04:16 AM ----------
What you're saying is that you can't get to the bootloader screen now?
Click to expand...
Click to collapse
Yep I'm serious **** now! Any more experts here have any idea? Or do i have to bring it to local mobile shop to get it fixed? Is Google able to help ?
Anyway... getting supersu installed is a non-issue if you can't get it to boot up. When you were trying to download supersu what you were looking for was the installable zip at Chainfires thread."CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu."
wantabe said:
Anyway... getting supersu installed is a non-issue if you can't get it to boot up. When you were trying to download supersu what you were looking for was the installable zip at Chainfires thread."CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu."
Click to expand...
Click to collapse
Nah i was just using the SuperSU zip i downloaded as per youtube link. The problem is my PC cant detect my tablet and i can't do sh**t!
Any manual hardware reset option on N7?
If a factory reset didn't clear it up you might be able to get away with just flashing the system image. Long pressing won't make it reboot?
I'll tell you how the tablet is right now, and hopefully you have some ideas where to go from here.
Atm, when i turn on and off the tablet.
but when i turn it on, it will go straight to the google screen with lock image at the bottom, then it will just stuck there
I tried going to recovery mode, and it won't come up with TWRP , and after a black screen, it will go back to boot screen
Tried "restart bootloader", did nothing too, just gone back original boot screen .
So now what? Gosh did i just break my brand new N7?
I'll tell you how my tablet is right now, and hopefully you have some ideas where to go from here.
ATM, I can turn on and off the tablet., but my PC won't recognise it
However, when i turn it on, it will go straight to the 'Google" screen with lock image at the bottom, then it will just stuck there
I tried going to recovery mode, and it won't come up with TWRP as before, and after a black screen, it will go back to boot screen
Tried "restart bootloader", did nothing too, just gone back original boot screen .
So now what? Gosh did i just break my brand new N7? :crying:

[Q] KF issues and what I have tried so far...

Hello.
I have a KF 1st generation. I had rooted it some time back and then un-rooted it (thought I did?) and haven't had an issue. This week it started loading up and freezing on the Kindle Fire orange and white logo. I am able to boot it to Recovery which gives me Cannibal Open Touch screen and options. I did try a few of the options but still the same end result. After coming here and reading around I found a thread and I followed the directions since the original poster and I seemed to have the same issue. There are the steps I followed:
Step 1) Download MoDaCo Rom/Any other ROM BUT NOT ANY KITKAT ROM(COTR can NOT flash KitKat)
Step 2) Transfer your ROM while in recovery
Step 3) Do a preflash wipe
Step 4) Do a factory reset
Step 5) Go to 'Install -> Install from SD Card -> Folder where you put your ROM
Step 6) Click Install without Backup
Step 7) Boot Android
I downloaded [ROM] 14 Jun Gr9 (6.3.1) - MoDaCo Custom ROM for the Kindle Fire and made it to Step 5 using the 'Zip Flashing' option but I can't seem to flash or sideload or any of those options. While the Kindle is plugged into the computer I hear the noise and when I find my Kindle it has a Yellow Triangle with a !. I looked at the Kindle and it tells me I have no drivers and I am not able to drag and drop any files. Also, not sure if it matters but I am no longer using the computer used to root the Kindle.
the rebooting is the new 6.3.3 update trying to install, but because you have custom bootloader/recovery install fails.
may need to install twrp recovery. but my prerooted 6.3.3 zip sbould install fine.
Sent from my DROIDX using Tapatalk
sd_shadow said:
the rebooting is the new 6.3.3 update trying to install, but because you have custom bootloader/recovery install fails.
may need to install twrp recovery. but my prerooted 6.3.3 zip sbould install fine.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
@sd_shadow I appreciate the reply and the twrp file but can you lead me to the direction to getting them to the KF? I can plug the KF into the computer and it no longer gives me the triangle ! sign. I am unsure of the next step and don't wanna mess anything up with unnecessary stuff. Thank You again :good:
Sunnywonder said:
@sd_shadow I appreciate the reply and the twrp file but can you lead me to the direction to getting them to the KF? I can plug the KF into the computer and it no longer gives me the triangle ! sign. I am unsure of the next step and don't wanna mess anything up with unnecessary stuff. Thank You again :good:
Click to expand...
Click to collapse
select mount option in twrp, then just copy to sdcard folder on pc
sd_shadow said:
select mount option in twrp, then just copy to sdcard folder on pc
Click to expand...
Click to collapse
I have been trying to figure this out and searching but I can't seem to figure this out. I am uploading the screen I have on my KF and I don't know how to mount the file. I can't find a thread that will kind of walk me though it so if you know where I should go that would be great. I am uselessly pretty good with figuring things out so maybe I'm making this harder than it looks?
Sunnywonder said:
I have been trying to figure this out and searching but I can't seem to figure this out. I am uploading the screen I have on my KF and I don't know how to mount the file. I can't find a thread that will kind of walk me though it so if you know where I should go that would be great. I am uselessly pretty good with figuring things out so maybe I'm making this harder than it looks?
Click to expand...
Click to collapse
Can't remember if Cannibal Open Touch has mount options
may need to
Download a twrp.img from http://techerrata.com/browse/twrp2/blaze,
latest (24 June 2014) is openrecovery-twrp-2.7.1.0-otter.img
verify md5 check sum
Download ADB/Fastboot.exe Files from adb-fastboot.zip
Unzip adb-fastboot.zip
Copy adb/fastboot files (AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe), and twrp.img
to same folder like c:adb
reboot Kindle to Bootloader
Open command prompt (Start menu>all programs>Accessories>Command Prompt
Enter Commands
Code:
cd\adb
fastboot reboot-bootloader
fastboot flash recovery openrecovery-twrp-2.7.1.0-otter.img
fastboot reboot
kindle will reboot
When you see Press Power for Boot Options select recovery
In TWRP (Team Win Recovery Project) select Mount check sd card and tap mount USB Storage
On Pc open sd card folder and copy update-kindle-prerooted.6.3.3.v1.zip downloaded from post 1
once copy is complete, close folder, unmount sd card
in TWRP select Install select update-kindle-prerooted.6.3.3.v1.zip
Swipe to Confirm Flash
after flash is complete, wipe cache, select Back, select Reboot
May take a few minutes to boot first time
Victory!
First off TY for the time you took to get me to the finish line. :victory:
I will admit trying to mount was a nightmare. I couldn't figure out how to do it so after hours of playing around and trying to find anything to try I finally succeed by installing the Kindle Fire Unbrick Utility (again) and running KindleUnbrick.bat file and installing the TWRP that way. Once that worked (and believe me I didn't think it would work since I tried this a few times) and I yelled WOOT, I followed the rest of your directions from "In TWRP (Team Win Recovery Project) select Mount check sd card and tap mount USB Storage" and installed your prerooted 6.3.3 zip and finished off your directions and have myself my dear reading buddy back. I APPRECIATE deeply the time you took to get me back. :highfive:
I want to add for anyone who is looking though threads looking for help with the same issue. If you are trying to get the TWRP file on your Kindle download the Kindle Fire Unbrick Utility and then running the RUN file and follow the directions.
great, Glad I could help.
I have tried to use the Kindle Fire Unbrick Utility a few times, with little success.
I would only suggest it, if nothing else is working, but does work in some situations.

Categories

Resources