Related
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.
I rooted my Kindle Fire using KFU 0.9.5 and flashed a custom ROM. It worked fine for a few days and then just crashed -- The options bar located on the bottom disappeared and the error message was: System UI has crashed. (I have attached two pictures for better clarity)
Also, whenever I boot up, there is no yellow flame that appears, it goes to the moving colourful discs straight on.
I tried using terminal emulator and entered many codes in some hope of mounting USB Mass Storage so that I can use KFU and restore my Kindle, but in vain.
I have tried EVERYTHING. I've been at this for 6 days now and am at wits end. :crying: I have read up close to a 100 articles; this was my last resort.
I just want to get the Kindle's stock OS back - no root, nothing.
And the only was is, I suppose, if I am able to mount my Kindle as USB Mass Storage onto my computer.
ANY help is appreciated!
AndroBoss.
I don't have a kindle but did you try wiping it and reinstalling it?
Sent from my SPH-L710 using xda app-developers app
jr71x said:
I don't have a kindle but did you try wiping it and reinstalling it?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
As it now runs on ICS, there is no Gingerbread for Kindle anymore on it. I can't wipe it clean from the device or atleast I don't know how to, please help?
All the wipes you should need to perform can be done in twrp recovery. Wipe factory reset , wipe cache , wipe dalvik and wipe the system. Reflash ROM , reflash gapps , reboot then system if prompted and you should be good to go.
Edit: failing to use the correct method to return to stock will just cause more problems. Rather than trying to go back to pure stock without fff and twrp I suggest you perform the above wipes and flash this instead http://forum.xda-developers.com/showthread.php?t=1439916 its just modified stock with Google play and it will not wipe out your recovery and bootloader.
Thepooch said:
All the wipes you should need to perform can be done in twrp recovery. Wipe factory reset , wipe cache , wipe dalvik and wipe the system. Reflash ROM , reflash gapps , reboot then system if prompted and you should be good to go.
Edit: failing to use the correct method to return to stock will just cause more problems. Rather than trying to go back to pure stock without fff and twrp I suggest you perform the above wipes and flash this instead http://forum.xda-developers.com/showthread.php?t=1439916 its just modified stock with Google play and it will not wipe out your recovery and bootloader.
Click to expand...
Click to collapse
Okay, I will flash what you suggested but that's the problem. I am unable to access TWRP recovery from my Kindle. When it boots up there is no yellow flame that appears as the custom ROM is ICS 4.0.
I tried mounting a twrp.img on to the SD Card after downloading one straight onto the tab but of no avail :/
What do you suggest? Is there any way I can get the TWRP Recovery to come up so that I can get the modified stock that you suggested?
Thanks for your help, regardless
Androboss1994 said:
Okay, I will flash what you suggested but that's the problem. I am unable to access TWRP recovery from my Kindle. When it boots up there is no yellow flame that appears as the custom ROM is ICS 4.0.
I tried mounting a twrp.img on to the SD Card after downloading one straight onto the tab but of no avail :/
What do you suggest? Is there any way I can get the TWRP Recovery to come up so that I can get the modified stock that you suggested?
Thanks for your help, regardless
Click to expand...
Click to collapse
I know you said you read "close to a 100 articles" in your OP, but I suggest you do a little more reading. Get yourself acquainted with the key software components of the Kindle Fire and how they work together. Some of the things you say in your posts suggest you would benefit from the first post here...
http://forum.xda-developers.com/showthread.php?t=1552547
- The yellow flame you are looking for is an older version of the FireFireFire (FFF) bootloader, but there is a newer/better version.
- The KF cannot go to "the moving colorful discs straight on" because the first thing you will see is the bootloader's bootlogo.
- You must determine what bootloader is currently installed on the device because it is key in determining how you can get into recovery (TWRP).
- "Mounting" sdcard means to make the storage space available to either the host computer or the Kindle Fire, but it almost always means the former. Your comment about having "tried mounting a twrp.img on to the SD Card" doesn't make sense.
My guess is you do not have FFF installed and the device is booting with the stock bootloader. Odds are you will still be able to boot into your current ICS system and execute an adb command to set the bootmode to recovery (5001). Then a reboot should take you into TWRP. At that point, you should try to mount the sdcard partition onto your computer and transfer the latest FFF and whatever ROM you want to flash. Be sure to install FFF as soon as possible. This will allow you to get back into TWRP even if your system software becomes unbootable. Only when you are comfortable with FFF and TWRP should you consider flashing another ROM onto the device.
In broad strokes, the above paragraph contains the steps you will take to get your device running properly again. If any part of it doesn't make much sense to you, I suggest you read the above article again. Then, you can figure out the specifics commands from the third post of the link above and the following...
http://forum.xda-developers.com/showthread.php?t=1638452
kinfauns said:
I know you said you read "close to a 100 articles" in your OP, but I suggest you do a little more reading. Get yourself acquainted with the key software components of the Kindle Fire and how they work together. Some of the things you say in your posts suggest you would benefit from the first post here...
http://forum.xda-developers.com/showthread.php?t=1552547
- The yellow flame you are looking for is an older version of the FireFireFire (FFF) bootloader, but there is a newer/better version.
- The KF cannot go to "the moving colorful discs straight on" because the first thing you will see is the bootloader's bootlogo.
- You must determine what bootloader is currently installed on the device because it is key in determining how you can get into recovery (TWRP).
- "Mounting" sdcard means to make the storage space available to either the host computer or the Kindle Fire, but it almost always means the former. Your comment about having "tried mounting a twrp.img on to the SD Card" doesn't make sense.
My guess is you do not have FFF installed and the device is booting with the stock bootloader. Odds are you will still be able to boot into your current ICS system and execute an adb command to set the bootmode to recovery (5001). Then a reboot should take you into TWRP. At that point, you should try to mount the sdcard partition onto your computer and transfer the latest FFF and whatever ROM you want to flash. Be sure to install FFF as soon as possible. This will allow you to get back into TWRP even if your system software becomes unbootable. Only when you are comfortable with FFF and TWRP should you consider flashing another ROM onto the device.
In broad strokes, the above paragraph contains the steps you will take to get your device running properly again. If any part of it doesn't make much sense to you, I suggest you read the above article again. Then, you can figure out the specifics commands from the third post of the link above and the following...
http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
WOW! Okay, thank you so much; I'll keep you updated. I'll do all this tonight! Cheers :good:
So recently, i was trying to install a custom rom and accidentally deleted the external storage. now, when i try to boot it is stuck at the TWRP
Kindle Fire logo. i can go into TWRP boot menu, but my computer won't recognize my kindle since it can never fully boot. how do i unbrick/ reset if i cannot connect to my computer? This is probably a post redone multiple times but if anyone could link me or help me out i would appreciate it very much. i will try to answer any/all feedback asap and thank you.
I know clockwork mod gives you the option to mount storage in recovery. Idk about twrp. Boot it up and see. I'm not familiar with the kindle fire but I'd it has an SD card slot you can pur the SD in your PC, copy the ROM.zip file over to it, stick it back in the kindle and flash the ROM from twrp.
Sent from my Inspire 4G using xda premium
brndnddge said:
I know clockwork mod gives you the option to mount storage in recovery. Idk about twrp. Boot it up and see. I'm not familiar with the kindle fire but I'd it has an SD card slot you can pur the SD in your PC, copy the ROM.zip file over to it, stick it back in the kindle and flash the ROM from twrp.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Thanks for helping! Unfortunately, kindle fire has no SD slot or external storage.
i believe that i am using twrp v2.2.2.1 if that helps anyone.
I Haven't deleted my OS because it says i have 5000 mb free out of 8000, but im still not sure what the problem is
Reboot into your twrp recovery and see if you have the option to mount storage. If you do, do it. Drop the ROM onto your storage and flash via twrp.
Sent from my Inspire 4G using xda premium
brndnddge said:
Reboot into your twrp recovery and see if you have the option to mount storage. If you do, do it. Drop the ROM onto your storage and flash via twrp.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
i rebooted into recovery and then mounted, but still no luck detecting the fire on my computer.
Shorticus_Noob said:
i rebooted into recovery and then mounted, but still no luck detecting the fire on my computer.
Click to expand...
Click to collapse
Remember that I am not a Kindle Fire expert. In fact, I have never held one in my hands. However, I did find this tool that is used to unbrick a kindle fire. It might help you. It is a stickie on the main page of Android Development for Kindle Fire:
http://forum.xda-developers.com/showthread.php?t=1428428
brndnddge said:
Remember that I am not a Kindle Fire expert. In fact, I have never held one in my hands. However, I did find this tool that is used to unbrick a kindle fire. It might help you. It is a stickie on the main page of Android Development for Kindle Fire:
http://forum.xda-developers.com/showthread.php?t=1428428
Click to expand...
Click to collapse
Thanks again. Even though you are not an expert the help was much appreciated!
Shorticus_Noob said:
Thanks again. Even though you are not an expert the help was much appreciated!
Click to expand...
Click to collapse
If you were to ask me something about an HTC Inspire or a Gnex 7, I could help you a lot more. Wish you the best of luck.
brndnddge said:
If you were to ask me something about an HTC Inspire or a Gnex 7, I could help you a lot more. Wish you the best of luck.
Click to expand...
Click to collapse
this is what it looks like when i open kindle files
View attachment 1352397
Shorticus_Noob said:
this is what it looks like when i open kindle files
View attachment 1352397
Click to expand...
Click to collapse
The image isn't all that great. I can make out a TWRP folder at the top. If this is the root to your device, all you would have to do is drag and drop the downloaded ROM into this location, power your device down, reboot into TWRP recovery and choose to install ROM from SD or whatever it is, navigate to the rom and choose to install it.
Edit: I believe I see a text file for fix permissions, a recovery.img file and an update file for the kindle fire...
Before you go to far you are not bricked. Just simply select mount then hit the big button drag and drop a rom zip and gapp zip to your sdcard.Do all the wipes minus your external storage/sdcard after unmounting then flash rom and then gapps, select reboot then system if prompted.
Edit: And don't flash that bin file or you will have nothing but problems.
Any luck on un-bricking your soft bricked kindle?
Yeah, i was trying to restore it by flashing the update but i looked through my files on my kindle and it wasnt there
Thepooch said:
Before you go to far you are not bricked. Just simply select mount then hit the big button drag and drop a rom zip and gapp zip to your sdcard.Do all the wipes minus your external storage/sdcard after unmounting then flash rom and then gapps, select reboot then system if prompted.
Edit: And don't flash that bin file or you will have nothing but problems.
Click to expand...
Click to collapse
where can i get a google apps package, and also, i accidently deleted external storage a couple days back
flashed cm10, and it works. i cant thank you guys enough for spending your time on a newb like me i was wondering where a GAPPS package would be?
Shorticus_Noob said:
So recently, i was trying to install a custom rom and accidentally deleted the external storage. now, when i try to boot it is stuck at the TWRP
Kindle Fire logo. i can go into TWRP boot menu, but my computer won't recognize my kindle since it can never fully boot. how do i unbrick/ reset if i cannot connect to my computer? This is probably a post redone multiple times but if anyone could link me or help me out i would appreciate it very much. i will try to answer any/all feedback asap and thank you.
Click to expand...
Click to collapse
The blue Kindle Fire logo and boot menu you see is not TWRP, it's FireFireFire.
What happens when you select "reset boot mode"? "recovery"?
soupmagnet said:
The blue Kindle Fire logo and boot menu you see is not TWRP, it's FireFireFire.
What happens when you select "reset boot mode"? "recovery"?
Click to expand...
Click to collapse
i fixed it along with the help of this amazing community. the not connecting to pc was due to my cable being made for a phone, and my computer.
Shorticus_Noob said:
where can i get a google apps package, and also, i accidently deleted external storage a couple days back
Click to expand...
Click to collapse
Since you are on CM10, you can get GAPPS from their website.
http://wiki.cyanogenmod.com/wiki/Gapps#Google_Apps
You want the GAPPS for CM10. Good choice in ROM IMO.
Edit: You flash GAPPS from your Kindle this way:
1. Download GAPPS from the link above
2. Scroll Down on the notification bar at the top
3. Tap the GAPPS.ZIP file
4. ROM Manager Opens
5. Leave the bottom box checked and tap OK
6. TAP OK again and the device will reboot into recovery and install GAPPS
brndnddge said:
Since you are on CM10, you can get GAPPS from their website.
http://wiki.cyanogenmod.com/wiki/Gapps#Google_Apps
You want the GAPPS for CM10. Good choice in ROM IMO.
Edit: You flash GAPPS from your Kindle this way:
1. Download GAPPS from the link above
2. Scroll Down on the notification bar at the top
3. Tap the GAPPS.ZIP file
4. ROM Manager Opens
5. Leave the bottom box checked and tap OK
6. TAP OK again and the device will reboot into recovery and install GAPPS
Click to expand...
Click to collapse
thank you. got it and google play installed, and im off
Shorticus_Noob said:
thank you. got it and google play installed, and im off
Click to expand...
Click to collapse
Sweet!!! Enjoy some nice Jelly Bean!!!
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Any suggestions on how I can get access back to my device so I can repair/replace the platform.xml file and restore functionality to my phone?
Thank you very much!
Deozaan said:
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Click to expand...
Click to collapse
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
enryea123 said:
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
Click to expand...
Click to collapse
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Deozaan said:
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Click to expand...
Click to collapse
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
enryea123 said:
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
Click to expand...
Click to collapse
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Deozaan said:
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Click to expand...
Click to collapse
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
having a backup of the sdcard is always a good idea :good:, i have 2 backups of mysdcard on 2 different hard drives of my computer and the pictures i take with the camera are automatically uploaded on my dropbox .
enryea123 said:
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
Click to expand...
Click to collapse
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Deozaan said:
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Click to expand...
Click to collapse
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
enryea123 said:
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip
Click to expand...
Click to collapse
I was in CWM Recovery. I was using the zip file that I extracted from the link you gave me for Google's stock ROMs (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
enryea123 said:
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
Click to expand...
Click to collapse
Try this one
Deozaan said:
I was in CWM Recovery. I was using the zip file that I extracted from here the link you gave me (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
Click to expand...
Click to collapse
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
enryea123 said:
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
Click to expand...
Click to collapse
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
I got it working again. The ROM you gave me failed signature verification in CWM Recovery, but I told it to install anyway and it worked. Thank you.
The problem I was having with Gmail not syncing was that I used Titanium Backup to restore my data, but because all the data from my "SD card" got erased, Titanium Backup itself lots its settings, so my Device ID was different. I guess Gmail relies on the device ID for syncing.
Thank you so much for your help! I learned a lot from the experience.
Glad i helped you. well this is one of the reasons why i don't restore data with titanium (especially system data).
and by the way:
Deozaan said:
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
Click to expand...
Click to collapse
To fully reset and install a clean rom using fastboot you have to extract the bootloader-blabla.img and radio-blabla.img files from the tar.gz archive and then extract the 4 .img files inside the zip (that is inside the tar.gz) and flash this 6 .img files connetting your phone in bootloader mode to your computer and using fastboot in terminal (in fact this procedure reinstall the recovery too).
Do you have to install BOOT MENU every time before you update a Custom ROM?
http://www.aftvnews.com/roms/
Boot Menu MUST be installed BEFORE installing this ROM or you will brick your Fire TV. Boot Menu and ClockworkMod are NOT the same thing.
You MUST first have installed Pre-Rooted ROM version 51.1.4.0 at some point before installing this version. You don’t have to downgrade to 51.1.4.0 if you are running a newer pre-rooted ROM. You just can’t skip from 51.1.3.0 or older straight to this version.
md5sum: de2ab7f2d3072e10d3e592b73ca52750
Released: 4/15/2015
Click to expand...
Click to collapse
Neo3D said:
Do you have to install BOOT MENU every time before you update a Custom ROM?
http://www.aftvnews.com/roms/
Click to expand...
Click to collapse
If I remember right, you only have to install the custom boot menu when applying either of the most recent updates. However, if you downgrade back to an older update that doesn't require the menu and decide to go back to the one of the newer updates, then you have to re-install the custom boot menu. I think it's only a requirement for the last two updates that're at the top of the list in the updates thread, the ones listed below don't require the custom menu. I know from experience that after install the custom menu and then the latest update, then going back to the build I was on before that, I lost the menu. Either way, though, just make sure you install the custom menu BEFORE applying the latest update, otherwise you'll get stuck on the Amazon logo screen, and the only way to get into recovery mode is to do the Fire TV version of the three finger salute: Alt+Shift+Print Screen, I think, and keep doing it til you get to recovery. I apologize in advance if I confused you a little, sometimes I get a little informative and ramble, kind of like what I'm doing right now
will4958 said:
If I remember right, you only have to install the custom boot menu when applying either of the most recent updates. However, if you downgrade back to an older update that doesn't require the menu and decide to go back to the one of the newer updates, then you have to re-install the custom boot menu. I think it's only a requirement for the last two updates that're at the top of the list in the updates thread, the ones listed below don't require the custom menu. I know from experience that after install the custom menu and then the latest update, then going back to the build I was on before that, I lost the menu. Either way, though, just make sure you install the custom menu BEFORE applying the latest update, otherwise you'll get stuck on the Amazon logo screen, and the only way to get into recovery mode is to do the Fire TV version of the three finger salute: Alt+Shift+Print Screen, I think, and keep doing it til you get to recovery. I apologize in advance if I confused you a little, sometimes I get a little informative and ramble, kind of like what I'm doing right now
Click to expand...
Click to collapse
I had Boot Menu previously installed but didn't reinstall it again before updating to this latest Custom ROM and now my AFTV is in a boot loop. I also noticed that the Boot Menu is now gone?
Is there anything I can do to fix this?
I can go into Recovery using the three finger salute, thanks!
But what do I do next?
Neo3D said:
I had Boot Menu previously installed but didn't reinstall it again before updating to this latest Custom ROM and now my AFTV is in a boot loop. I also noticed that the Boot Menu is now gone?
Is there anything I can do to fix this?
I can go into Recovery using the three finger salute, thanks!
But what do I do next?
Click to expand...
Click to collapse
Cool. Glad you were able to get back in there. When it happened to me, my arms got a little sore from having to smash the keyboard so much, but the keyboard is a little on the stiff side, so it didn't take much. Anyway, at this point you want to restore a backup you hopefully made, install the custom boot menu, then install the new update again. On the chance you don't have a recent backup, or any backup handy, just install any the last version you were on that didn't require the menu, reboot to make sure it took, install the custom menu, flash the new update, then reboot. That should get you back up and running.
will4958 said:
Cool. Glad you were able to get back in there. When it happened to me, my arms got a little sore from having to smash the keyboard so much, but the keyboard is a little on the stiff side, so it didn't take much. Anyway, at this point you want to restore a backup you hopefully made, install the custom boot menu, then install the new update again. On the chance you don't have a recent backup, or any backup handy, just install any the last version you were on that didn't require the menu, reboot to make sure it took, install the custom menu, flash the new update, then reboot. That should get you back up and running.
Click to expand...
Click to collapse
Thanks! Unfortunately, I didn't make any backups of before when it was working.
How do I copy the Custom ROM zip file onto the AFTV?
Neo3D said:
Thanks! Unfortunately, I didn't make any backups of before when it was working.
How do I copy the Custom ROM zip file onto the AFTV?
Click to expand...
Click to collapse
Since you're only able to get into recovery mode at this point, you'd have to copy the ROM to a flash drive. If you have a USB hub, preferably a powered one, plug the flash drive into the hub, along with a usb/wireless keyboard if you have either. The Fire TV should automatically detect the flash drive as long as it's formatted with a Windows file format. At that point, installing the update is just like doing it from the Fire TV itself, but since you're using a flash drive you'll want to select the install from USB option. I forget exactly what it's called, but you'll know it when you see it. The only thing that'll pop up will be the custom ROM you copied to the drive.
will4958 said:
Since you're only able to get into recovery mode at this point, you'd have to copy the ROM to a flash drive. If you have a USB hub, preferably a powered one, plug the flash drive into the hub, along with a usb/wireless keyboard if you have either. The Fire TV should automatically detect the flash drive as long as it's formatted with a Windows file format. At that point, installing the update is just like doing it from the Fire TV itself, but since you're using a flash drive you'll want to select the install from USB option. I forget exactly what it's called, but you'll know it when you see it. The only thing that'll pop up will be the custom ROM you copied to the drive.
Click to expand...
Click to collapse
So, I copy my zip file onto a USB drive and plugged it into a hub into the AFTV. However, I can't find any option to access the USB drive from inside Clockwork?
When I go into /sda1/ it doesn't actually show the contents of the USB drive. I'm using the same USB drive that I normally have plugged into the AFTV (for downloading videos from Genesis).
Neo3D said:
So, I copy my zip file onto a USB drive and plugged it into a hub into the AFTV. However, I can't find any option to access the USB drive from inside Clockwork?
When I go into /sda1/ it doesn't actually show the contents of the USB drive. I'm using the same USB drive that I normally have plugged into the AFTV (for downloading videos from Genesis).
Click to expand...
Click to collapse
Your flash drive has to be formatted to FAT or NTFS, both of which are Windows file system formats. Once you plug the drive into the Fire TV or hub, it will automatically detect it. Give it a few seconds to do so, then select Install zip. On the next screen you'll see the usual methods for installing a ROM, but now you should also see an option that says Choose zip from USB, or something similar to that. Once you choose it, the next screen should show the zip file for the custom ROM you placed on your flash drive, but the drive has to be formatted as a FAT32 or similar Windows file system drive for the Fire TV to see the drive. And yes, I know it sounds a little silly considering the Fire TV runs on a version of Linux, but that's technology for you
will4958 said:
Your flash drive has to be formatted to FAT or NTFS, both of which are Windows file system formats. Once you plug the drive into the Fire TV or hub, it will automatically detect it. Give it a few seconds to do so, then select Install zip. On the next screen you'll see the usual methods for installing a ROM, but now you should also see an option that says Choose zip from USB, or something similar to that. Once you choose it, the next screen should show the zip file for the custom ROM you placed on your flash drive, but the drive has to be formatted as a FAT32 or similar Windows file system drive for the Fire TV to see the drive. And yes, I know it sounds a little silly considering the Fire TV runs on a version of Linux, but that's technology for you
Click to expand...
Click to collapse
Here are the options that I see?
Choose zip from /sdcard
Choose zip from last install folder
Install zip from sideload
My recovery is version: 6.0.5.1.4a
http://www.aftvnews.com/recovery/
Neo3D said:
Here are the options that I see?
Choose zip from /sdcard
Choose zip from last install folder
Install zip from sideload
My recovery is version: 6.0.5.1.4a
http://www.aftvnews.com/recovery/
Click to expand...
Click to collapse
Yeah, it looks like it's not detecting your flash drive. Did you format the drive to something like FAT, FAT32, or NTFS? If not, it won't detect the drive, and you won't be able to install the ROM from the flash drive. Also, if the drive is already plugged in, you could try pulling it out then reinserting it again. But like I said, none of that will work if the drive isn't formatted properly.
will4958 said:
Yeah, it looks like it's not detecting your flash drive. Did you format the drive to something like FAT, FAT32, or NTFS? If not, it won't detect the drive, and you won't be able to install the ROM from the flash drive. Also, if the drive is already plugged in, you could try pulling it out then reinserting it again. But like I said, none of that will work if the drive isn't formatted properly.
Click to expand...
Click to collapse
Yes, it is NTFS?
Neo3D said:
Yes, it is NTFS?
Click to expand...
Click to collapse
I'd say if it's not detecting it with that format, try formatting as FAT32. I just checked a drive I've used before for the same thing, and it's formatted as FAT32 and it still has a recent update on it I tried before.
will4958 said:
I'd say if it's not detecting it with that format, try formatting as FAT32. I just checked a drive I've used before for the same thing, and it's formatted as FAT32 and it still has a recent update on it I tried before.
Click to expand...
Click to collapse
Thank you! I will try that.
So, I guess I should have re-installed BOOT MENU before upgrading the custom ROM.
It kind of doesn't make sense to have to re-install BOOT MENU if you already have it running before upgrading?
Neo3D said:
Thank you! I will try that.
So, I guess I should have re-installed BOOT MENU before upgrading the custom ROM.
It kind of doesn't make sense to have to re-install BOOT MENU if you already have it running before upgrading?
Click to expand...
Click to collapse
I can't remember the reason the custom boot menu requirement before applying the new update, but it does give you a couple different options when booting. Can't remember what they are, but the logo looks cool. As far as having to reinstall the custom boot menu, though, it's only a requirement for the two newest updates on this forum, and the way the thing is programmed it's made to look for that custom menu when booting. It only takes a couple minutes to install the menu, and after that you're back to watching Netflix, playing Dead Trigger, or whatever.
will4958 said:
I can't remember the reason the custom boot menu requirement before applying the new update, but it does give you a couple different options when booting. Can't remember what they are, but the logo looks cool. As far as having to reinstall the custom boot menu, though, it's only a requirement for the two newest updates on this forum, and the way the thing is programmed it's made to look for that custom menu when booting. It only takes a couple minutes to install the menu, and after that you're back to watching Netflix, playing Dead Trigger, or whatever.
Click to expand...
Click to collapse
Yea, it was confusing whether or not the BOOT MENU needed to be re-installed before EVERY new update when you already have it installed and working.
i did not install the bootmenu again when i did update from 1.4.1 to 1.4.3 nor from 1.4.3 to 1.5.0.
I just installed the zip file via recovery.
Why dont you boot to recovery and adb push the update .zip file to your internal storage? IIRC adb is enabled in recovery,
(since you seem to be having problems with the usb drive)
aHcVolle said:
i did not install the bootmenu again when i did update from 1.4.1 to 1.4.3 nor from 1.4.3 to 1.5.0.
I just installed the zip file via recovery.
Why dont you boot to recovery and adb push the update .zip file to your internal storage? IIRC adb is enabled in recovery,
(since you seem to be having problems with the usb drive)
Click to expand...
Click to collapse
Yea, I didn't think I had to either since my BOOT MENU had been installed and working....but I got stuck in a boot loop after upgrading??
I ended up using SIDELOAD to push a zip to the AFTV: https://www.youtube.com/watch?v=dWXHD7PlaQc
Thanks!