Here are some of the problems I've run into:
No shell access unless I'm in CWR.
Can't flash an update.zip, fails to mount the sdcard.
Can't restore to stock using http://forum.xda-developers.com/showthread.php?t=1378063 just flashes update failed on the screen for a split second.
Can't flash a system.img, too large, at least the one I was sent in a PM.
If I reboot, anything I pushed is wiped by time I'm back in recovery.
If I try to run zergrush it says "/sbin/sh: ./zergRush: not found"
Cannot run idme bootmode from recovery, I can do it in fastboot though with a factory cable:
# idme bootmode 0x5001
idme bootmode 0x5001
/sbin/sh: idme: not found
ATM I have CWR and FireFireFire installed.
I originally messed up my "/system/bin" and "/system/framework" permissions by merging a folder over them. I went and changed the permissions back to what they were and root explorer force closed.
When I would try to launch apps it would just give a force close error with some random symbols text, went to shutdown and wouldn't allow me to press shutdown, it was just a grey button with no action, So I hard rebooted.
My KF did not boot back into Android the screen with "Your Kindle has detected a problem and must clear App storage..." etc came up and I figured eh I'll just have to reroot. It wiped, lost my root, lost shell access, except for the first few seconds when booting up, but it would loop back to that screen and I would have no access.
Now I have a factory cable and do not know how to fix my problem.
This guy seems to have a similar problem to me from "[HOW TO] Unbricking/Restoring your Kindle Fire" thread http://forum.xda-developers.com/showpost.php?p=20145762&postcount=308
Our problem seems to be beyond the scope of that thread where our device is essentially wiped with no way to fix our devices except with outside files.
Any help would be appreciated.
Power off completely, plug factory cable into computer then kf. Doing so will automatically start the device, but with the factory cable it will be in fastboot
Sent from my DROID Pro using XDA App
JackpotClavin said:
Power off completely, plug factory cable into computer then kf. Doing so will automatically start the device, but with the factory cable it will be in fastboot
Sent from my DROID Pro using XDA App
Click to expand...
Click to collapse
I Know how to get into fastboot, I was fully stock and rooted before my brick. I added CWR and FFF afterwards using fastboot.
I don't have a small enough system.img to flash, assuming that would fix my problem.
Whoops I had just woken up from a nap and my head wasn't screwed on right
Very strange that you can't mount the sdcard. Are you using my clockwork that I provided in the CM7 rom thread?
Try adb shell
Mount sdcard
And then see if you can install an update?
Sent from my DROID Pro using XDA App
JackpotClavin said:
Whoops I had just woken up from a nap and my head wasn't screwed on right
Very strange that you can't mount the sdcard. Are you using my clockwork that I provided in the CM7 rom thread?
Try adb shell
Mount sdcard
And then see if you can install an update?
Sent from my DROID Pro using XDA App
Click to expand...
Click to collapse
Gives this error:
~ # mount sdcard
mount sdcard
mount: mounting /dev/block/mmcblk0p12 on /sdcard failed: Invalid argument
HELP
Im stuck at TWRP and my bootmode is 0x5001. Can anybody help?
So, I've been up all night after buying this Fire trying to fix it, and I've decided to go along with my original decision to just return it. I'll rewind a bit to give you guys a play by play to show how I got to what I've determined is a FUBAR situation, and hopefully you guys can help me at least remove TWRP so I can return it without much issue.
If it's tl;dr, I bolded the main errors I got from the console and TWRP
1. I purchased my Kindle Fire from Best Buy with a 1 Year Protection plan, so in all reality, I could just break it in half and get a replacement, but I don't necessarily want a replacement.
2. I initially purchased it for my mom, but when I found out that the stock Fire OS didn't have Korean input or the option to have a Korean interface, I did a bit of research and started reading up on how to root, how to install the market, things like that. My mom's not a native English speaker, so this was an important thing for her, etc etc.
3. I read multiple guides on this forum and others, and rooted using the guide found here , since a few of the threads I was reading through seemed to point in that direction, and I had a bad experience with SOCR on my Droid X.
4. The root was successful, so I moved on and used KFU .3 to do the rest of the important bits; android market, etc etc.
5. Everything was working fine, but, after looking through it, I realized that it wouldn't work for what I needed it to, and I would have to return it, so, I attempted to unroot the tablet using TWRP's interface.
6. I cleared the cache, the devlak cache, and system wiped, then restored using the system restore point in the TWRP folder, figuring after that, the Kindle would boot up with stock OS and then I would just system restore the default way. This method got me stuck in a recovery-loop, and no matter what I did, the Fire always booted to recovery mode.
7. I figured I had bricked it, so I followed the steps in this guide, but always seemed to have problems at the step where I have to chmod 755 of the zergRush. I get "Not a directory" error, which after doing some research, I believe is on account of me no longer having rw privilege?
8. I looked around some more, ignoring that guide, and found a method to force-push the amazon update, but TWRP would no longer run the update, saying it could not Mount the SD Card due to an Invalid Argument, and I have yet to determine what that means.
9. After manually changing it to fastboot in an attempt to at least get it out of recovery mode, I have the Fire recognizable as a device in my ADB, but it is now stuck in a fastboot loop, and when I attempt to re-root it in order to give myself rw privileges again, it stalls on "waiting for device" and never gets past that point.
Update
I tried to reroot while the Fire was stuck in the Kindle Fire splash screen using the KFU tool, and used zergRush, but the error message I got was - exec '/system/bin/sh' failed: No such file or directory (2) - 4 times over.
What I think the problem is, is that when I wiped the cache/devlak cache/ and system reformatted, it wiped my SU privileges, and as a result, no longer allowed me to write the backup to the Fire, therefore leaving me in a perpetual state of limbo?
What I'm asking for from you is;
What can I do to fix this?
Is there any more information you need/want from me?
And finally,
Is there an easy way for me to remove TWRP from the system?
Thank you.
Hi!
There are a lot of great tips regarding TWRP and fastboot over at RootzWiki.
Some users are reporting the same fastboot loop that you currently experience. I suggest you read the thread and follow the suggestions. One suggestion which you may want to try first is the one in this post.
Thank you for the reply. I did as you suggested and followed the links and the post on the guide, and although that did change the nature of my fastboot loop, I'm still stuck in a fastboot loop.
I was initially stuck in a fastboot loop on the Kindle Fire logo, which I determined by running fastboot devices, while it was stuck on that logo, and it showed the device as being fastboot. After following that guide, and using the hard reset, then using the "How to Unbrick" in order to change back to a normal boot, I'm stuck in a fastboot loop on the TWRP splash screen of a triangle with a fire in it. I'll continue looking through the guides to see if I can solve the problem, but thank you once again, and sorry for not clarifying which type of fastboot loop I was in.
Sorry it didn't work out! However...
isjonamon said:
I'm stuck in a fastboot loop on the TWRP splash screen of a triangle with a fire in it.
Click to expand...
Click to collapse
I really though the solution posted over at RootzWizi would solve this problem. Getting stuck at the yellow triangle is 'common'. I really though adding
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
Click to expand...
Click to collapse
to android_winusb.inf would solve it. But if you are able to recognize your Fire in fastboot mode via your PC, I guess that's not where your problem is.
Is this tip to any help?
And lastly... the great Kindle Fire Utility thread is worth checking out, in case you haven't already
I hope you'll find a solution to this problem!
I've tried the tip you linked me to, and sadly it didn't do anything for me.
Moving on, though, I'm reading through the KFU thread again to see if there was anything I missed, and decided I might as well try re-flashing to CM7 to see if I can at least get it working up to a rooted/rom standpoint. I figure from there, I can at least have a working platform to factory reset from. If I can't do that... well...
Does anyone know a way to just return everything to factory settings? To just wipe everything and make it so it turns on like it's out of the box? Either through adb commands, or TWRP or anything?
Sorry for the double post, but I managed to get CM7 back up on my Fire, and managed to regain SU access. Can anyone point me to a guide to restoring it back to its former "glory" so I can return it?
Fixed it!!
For anyone interested, this is what worked for me;
From where I ended up with the problem, I followed hachiueno's advice and read through the KFU's thread as well as the TWRP thread on Rootzwiki, that led me to adding those lines to the device firmware, which I think was the first step in the solution, so...
Step 1. Add
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
to android_winusb.inf , then restart your computer with your Fire unplugged.
After that, I was inspired, through reading the KFU thread, to attempt to manually install CM7 since I wasn't having much luck zergRushing on my own, so, I went to the CM7 thread and pushed the Update.zip there, and used my TWRP to install that, effectively rebuilding my filestructure, since it seems the Kindle Fire doesn't have so much as a SH folder in it.
Step 2. MANUALLY (maybe) install CM7 if you can.
Once I got CM7 up and working, using the USB mounting option, I replaced the update.zip in the sdcard folder with the Amazon 6.2 firmware downloaded from their website, renamed to update.zip, and then unmounted my fire from my laptop.
Step 3. Download the Amazon 6.2 Firmware from amazon's website (I can't post...), rename it to update.zip, and replace the CM7 mod update.zip in your /sdcard directory with it.
Then, I figured if I ran TWRP like it was supposed to run, and just ran the update.zip like any other ROM, it should fill in the blanks in the filesstructure, bypassing Amazon's own lack of certain folders, and various other things, filling in the gaps as they were. The next step might be entirely redundant, since I'm a bit clueless, and it might have been entirely luck on my part, but I initially forgot to wipe my cache, devlak cache, and system restore, so I did all that and did it again, and my wishful thinking leads me to believe that doing that saved my ass from having a crapton of errors....
Step 4. Using the install function on TWRP, install the renamed Amazon update.zip, reboot, clear your cache, devlak cache, system reformat, then reinstall the update.zip. Reboot one more time, and you should come up to the Kindle Fire splash screen. Leave it for a few minutes, and it'll be like it just came out of the box.
Thanks for all your help. I love you. Seriously. No homo. Maybe a little. I love you.
Good to hear that you managed to boot it again!
isjonamon said:
Sorry for the double post, but I managed to get CM7 back up on my Fire, and managed to regain SU access. Can anyone point me to a guide to restoring it back to its former "glory" so I can return it?
Click to expand...
Click to collapse
This guide seems to be an easy solution to this. However, no one has replied any success or failure, so not sure if it's 100% bulletproof for everyone... if I were you, I would follow JackpotClavin's guide here. He's a known developer here and knows what he's doing, and many successful replies from users having used this method... so yeah, just to be 'sure' (can you ever be...?) that you won't experience any further problems, I recommend the last one.
I actually used the first guide in order to get the Amazon update, but couldn't post a reply since I'm still a noob. I had to do a few things differently, and ultimately got a few different results, but posted up my own version of the steps.
Once again, thanks for all your help!
It seems to me that the majority of problems people are having are driver related. When I was using KFU to install TWRP it stalled half way through and just said waiting for device. Just had to install drivers again and it happily completed the install.
Sent from my Kindle Fire using xda premium
all u needed do initially was change bootmode it seemed. thrn u went and did all kinds of stuff that wasnt necessary.
sent from my kindle fire
smirkis said:
all u needed do initially was change bootmode it seemed. thrn u went and did all kinds of stuff that wasnt necessary.
sent from my kindle fire
Click to expand...
Click to collapse
I actually changed bootmodes quite frequently, following multiple threads and guides, changing from recovery, to normal, to fastboot, and back and forth when called for. Changing to fastboot stuck me in an eternal fastboot loop, changing to normal reverted me to a recovery loop, and recovery was the only bootmode I could access adb from.
Sheolrock said:
It seems to me that the majority of problems people are having are driver related. When I was using KFU to install TWRP it stalled half way through and just said waiting for device. Just had to install drivers again and it happily completed the install.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Driver issues seemed to be part of the problem for me, but just updating the drivers didn't fix the issue entirely. I'm jealous that you got it to work with just a driver update...
Hey i believe im in the same problem but i keep reading the posts and im still stuck and i have no idea what to do im worried that i cant fix it.... Some please help me ASAP
Thanks in advance
wrong boot mode ?
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
bad drivers ?
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
I have had the looping problem and none of these would fix it. I got it to work by adding those lines to android_winusb and running the run.bat, trying to make it switch to normal mode as the kindle was turning on. Somewhere along the yellow triangle when it was loading it accepted the command from KFU. Hope this helps, only thing that worked for me.
the drivers i included contain all the necessary entries in adb_usb.ini and android_winusb.inf
Please can someone help me!?
I did idme bootmode 4002 and now my fire won't boot up or show up in android adb. Any solution?
awidawad said:
I did idme bootmode 4002 and now my fire won't boot up or show up in android adb. Any solution?
Click to expand...
Click to collapse
you switched it to fastboot (4002) - adb commands are not working in fastboot mode !
little guide:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse
Not sure if this is totally helpful to anyone but originally I thought the thread was started with a posting of being stuck bootlooping into twrp in recovery mode with a complete loss of file structure. I had this same issue my Kindle would not start in anything but straight to twrp and if I tried to flash my CM9 ICS rom it was not there and only the twrp folder empty was. So I went to mount and mounted usb storage and moved the stock update zip file from amazon to the twrp folder and flashed that. Worked like a charm now I appear to be straight stock. I am no developer of this stuff I just am a bit of a tinkerer so don't understand all the code stuff but it starts like a normal kindle and appears totally stock. So hopefuly that helps you return your deice to stock for return or to continue wahtever modifications you intend.
2992
Hi, i had my Fire bricked (changed system folder permissions) but I made it came to life thanks to pokey9000´s new fastboot method. First thing i´ve done is install recovery. Once in recovery i wanted to make a clean install of the Fire original rom so i downloaded the update.zip, wiped all and flashed the update.
Then something has gone wrong, because the Fire boots as if recovery is not there and hangs on the logo. And worst of all, i can´t use pokey9000´s utility again as adb shell says:
- exec '/system/bin/sh' failed: No such file or directory (2)
Of course Kindle Utility fails at every option I select because of the same error.
Is my Fire dead for good or anyone knows how to solve this??
Thank you in advance!
You shouldn't have flashed the stock update, it got rid of the root I believe, thus your recovery would be useless. Don't hold me to that though, I could be wrong.
cccodyyyy said:
You shouldn't have flashed the stock update, it got rid of the root I believe, thus your recovery would be useless. Don't hold me to that though, I could be wrong.
Click to expand...
Click to collapse
The thing is, flashing an update.zip erases recovery? Cause in my Nexus One it does not!
Hi. Given that the error I have is that it can´t find the '/system/bin/sh' executable I´ve tried to copy it with this command:
adb push system/bin/sh /system/bin
The result is
failed to copy 'system/bin/sh' to '/system/bin': Read-only file system
So the folder must exist. Is there a way to see the content of the rom, given that adb shell isn´t working?
Thanks!
Apparently I made the same mistake. Any help on this one would be greatly appreciated. I have been all over this forum and the amount of conflicting information is astounding. At this point I am just confused, and highly agitated with myself.
Is there a way to either re-flash the entire thing (I assume using the "magic cable"), or perhaps manually reinstall the folder structure?
I think the only way is booting to Fastboot with the factory cable. I don´t think we can execute anything without adb shell working
maybe this helps:
http://forum.xda-developers.com/showthread.php?p=20714780#post20714780
Sorry to be WAY off topic, but what exactly is this "magic cable"?
it's the "factory cable" - such a cable is used in the factory to "load" the devices with software
if you want to know more search in the forum for "factory cable"
Solved
thanks to all for the great info
i have a fire that is stuck on the static kindle logo. was rooted and had fff and twrp. while messing with flashing different roms i used a custom rom that had several apks removed. after booting i still had fff and twrp but my wifi stopped working. i flash the 6.2.1 stock rom that removes fff and twrp, but did a stupid and wiped some stuff before i booted the stock rom. now im stuck with kfu showing online but under status says unknown. i can use adb to reboot but that seems all i can get it to do. im at work now and cannot quote the messages i get. something like /systme/whatever is not there. seems like i wiped the sd card and all. now with that information can i still use a factory cable to fix this? im working on one now to try and see. just wanted to hear from someone who has maybe done the same.
thank you very much for any info
I was in the same exact situation and with the factory cable i managed to fix my brick. Don't worry, your Fire is fine.
The same thing happened on mine 20 minutes ago. I worked it out with the method used in this thread.
lmntone said:
The same thing happened on mine 20 minutes ago. I worked it out with the method used in this thread.
Click to expand...
Click to collapse
That won't work without a working adb shell (http://forum.xda-developers.com/showthread.php?t=1418080), whik i think is the case.
man i hate being a noob fire owner i have my cable done 5v on 1 and 4 but not getting what i was looking for. kfu still shows
adb: online
adb rooted: no
boot status: unknown
im on windows 7 and can reboot the fire with cmd window adb reboot. but i have no idea where to go from here.
i thought the factory cable would put it in fastboot, but not sure how to check or what to do.
adb shell gets this:
-exec '/system/bin/sh' failed: no such file or directory (2) -
It won't show up in kfu, just select flash twrp anyway.
Sent from my myTouch_4G_Slide using XDA App
Use fastboot.exe located in the tools directory and run "fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.image". But you have to download the TWRP image and place it in the same folder as fastboot.exe.
Iguanadon said:
man i hate being a noob fire owner i have my cable done 5v on 1 and 4 but not getting what i was looking for. kfu still shows
adb: online
adb rooted: no
boot status: unknown
im on windows 7 and can reboot the fire with cmd window adb reboot. but i have no idea where to go from here.
i thought the factory cable would put it in fastboot, but not sure how to check or what to do.
adb shell gets this:
-exec '/system/bin/sh' failed: no such file or directory (2) -
Click to expand...
Click to collapse
you know you're in fastboot mode when your kindle fire logo is static instead of glimmering
maybe you want to take a look here:
http://forum.xda-developers.com/showpost.php?p=21391952&postcount=38
Everything I've seen so far has resulted in someone bricking their phones, including somehow deleting their IMEI numbers or somehow resulting in their BT/WiFi not working. There were so many threads that it's hard to remember which one is which.
I've decided it's time to unlock/root my phone but I don't want to make the same mistakes and somehow brick my phone. Why was it that the partition with the IMEI was written over? What about the other bricks? What is the best method to unlock/root right now?
Often times mixing firmware from other regions will cause issues. For example flashing the US version with the G or international versions. By firmware, I'm referring to other system components besides /system and kernel. Radio/baseband, BT firmware, etc.
The other issue has to do with the axon7backup program. For greatest safety, this really should only be used to backup and flash recovery while the bootloader is still locked only.
I see, thanks.
I followed these guides:
- https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
- https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
Now my phone is unlocked and rooted... but after each reboot the annoying system apps I uninstalled return. I'm guessing this is because I have a systemless root?
So I guess my questions are now:
- Most importantly if a system root is required to keep changes such uninstalling system apps, how can I switch to that and is there anything I should be wary of? Is a system root guaranteed to be seen even with SUhide/whatever?
- How can I even know if the SafetyNet program is even working if according to that guide I can't even use it's check app to test it?
- What about SUhide? Like SafetyNet I don't seem to have a way to see anything regarding it.
There is no way to fully brick a device with the Qualcomm 820 SoC. It is more or less complicated, but even deleting the bootloader it is possible to recover the device with the appropriate Qualcomm flashing tools.
Regarding "easy" bricks, you will be able to recover any brick by using tenfar's Axon7tools, and DrakenFX guides. Also Just keep on had a backup of your boot.bin, recovery.bin (both using Axon7Tool), and the full ZIP for your device model in a FAT formatted SDcard.
The recovery process is just to flash back the boot.bin, then recovery.bin (using the same tool Axon7tool) and then from the stock recovery reinstall the full zip and optionals OTA.
Cyrus D. said:
I see, thanks.
I followed these guides:
- https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
- https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
Now my phone is unlocked and rooted... but after each reboot the annoying system apps I uninstalled return. I'm guessing this is because I have a systemless root?
So I guess my questions are now:
- Most importantly if a system root is required to keep changes such uninstalling system apps, how can I switch to that and is there anything I should be wary of? Is a system root guaranteed to be seen even with SUhide/whatever?
- How can I even know if the SafetyNet program is even working if according to that guide I can't even use it's check app to test it?
- What about SUhide? Like SafetyNet I don't seem to have a way to see anything regarding it.
Click to expand...
Click to collapse
You missed a step. Use Terminal or Terminal Emulator , type SU, then reboot disemmcwp
or
Go to adb shell while in TWRP and enter adb reboot disemmcwp
This will reset settings to allow system changes so they will "stick".
Good luck!
amphi66 said:
You missed a step. Use Terminal or Terminal Emulator , type SU, then reboot disemmcwp
or
Go to adb shell while in TWRP and enter adb reboot disemmcwp
This will reset settings to allow system changes so they will "stick".
Good luck!
Click to expand...
Click to collapse
Sorry I'm new to all this, I'm doing something wrong here.
So just to be clear it's:
- Type in "SU", enter it, then type "reboot disemmcwp", in TWRP's terminal?
That results in "SU not found" for me.
or
- Type in "adb reboot disemmcwp" in a command window opened in the adb folder on my PC while TWRP is running adb sideload?
That resulted in "* daemon not running. starting it now on port 5037 * * daemon started successfully * error: closed"
Edit: Just "reboot disemmcwp" in the terminal without SU first worked. So... what was I doing wrong?
Cyrus D. said:
Edit: Just "reboot disemmcwp" in the terminal without SU first worked. So... what was I doing wrong?
Click to expand...
Click to collapse
The su binary only exists if you open a terminal in an android app because apps do not have root permission. TWRP and adb shell automatically have root privileges.