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
I clicked every button in the twrp wipe menu then flashed the kindle fire 6.2.1 stock rom but it sems to have failed so i don't have any files in system. I am stuck at the bootlogo and I can't get twrp. How can i boot into twrp or restore my kindle. Please help thanks
Cobohobo said:
I clicked every button in the twrp wipe menu then flashed the kindle fire 6.2.1 stock rom but it sems to have failed so i don't have any files in system. I am stuck at the bootlogo and I can't get twrp. How can i boot into twrp or restore my kindle. Please help thanks
Click to expand...
Click to collapse
You might want to check the unbricking thread at the top of the kindle fire general discussions.
if you get fastboot commands available you can try to follow this post starting at point 3:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
Amazon is sending me a free replacement
I chatted with amazon customer service and they're sending me a free replacement, but i still want to know how to fix this just in case it happens again. Does anyone know how I can get fastboot or a link to a factory cable that is for sale thanks. I can't do anything that would -exec /system/bin/sh though and I'm not rooted
here it the guy who builds and sells them: http://forum.xda-developers.com/member.php?u=500006
and a thread about it:
http://forum.xda-developers.com/showthread.php?t=1392693
This is one I haven't seen in the forums -
Last night I used KFU 093 to permanently root my phone, flash firefirefire bootloader and the twrp recovery module, followed by a flash of CM7 with a twrp backup and the KF as a second backup. All did not go smoothly but i knuckled down and with the help of the forums - i got there. i was hoping to use twrp to switch between backups of CM7 and the KF OS as needed but as of this morning i'm not seeing the firefirefire bootloader screen anymore and so i can't boot into recovery using the power button.
i tried to use kfu again today to re-flash firefirefire but now am getting an "access denied - the bootloader was not flashed" message on my kindle even though the kfu says the flash was successful. rebooting the kf demonstrates firefirefire was not flashed.
Any ideas what might be causing the "access denied" message? I checked and su access is allowed... any help would be greatly appreciated! Thank you.
PS i'm running Win 7 and KF 6.2.2.
I used KFU 093 to permanently root my phone
Click to expand...
Click to collapse
i assume you mean the kf ?
never seen such failure - sounds like messed partitions
if you get it to fastboot somehow you could try to hotboot the bootloader
by "fastboot -i 0x1949 boot bootloader u-boot.bin" and
try to restore factory partitioning with "fastboot oem format"
if you have to format it maybe this thread can help you further:
http://forum.xda-developers.com/showthread.php?t=1403337
maybe you'll need a factory cable to get to fastboot:
http://forum.xda-developers.com/showthread.php?t=1392693
Minor detail - yes the kindle fire.
I had not thought about partitions - perhaps that's the issue. I haven't had the best of luck getting it into fastboot - with the utility or by command prompt. The driver issues with the KF are absurd. Any experience with Firekit? http://forum.xda-developers.com/showthread.php?t=1430038
Perhaps I will need to get a factory cable (which by the way appear to finally be in stock: http://forum.xda-developers.com/showthread.php?t=1430038).
Is there any way for me to confirm it is a partition issue before reformatting?
Thanks again!
Btw I have been ripping off sound advice from you on these forums for a few days now - since I got myself addicted to this whole mess. I owe you already!
the thing with the drivers sounds more complicated than it is - i have written a quite long post about this: http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
i have no experience with firekit but as linux needs no drivers and the firekit is prepared exactly for the kf it should work fine - it had done for many others
if you don't have adb commands available i don't know a way to check the partitions
and to have a factory cable is allways a good idea - i have one from scorpn allthough i never needed it - just good to have
Hi all,
I made a series of mistakes that got me to where I am now. All I intended on doing was repairing my dad's tablet which was running atrociously slowly. I tried to follow some steps, but improvised as I was getting errors and ended up making things a lot worse...
Now tuning on the tablet will directly go to a command line interface with a long series of errors and these are the last 2 lines:
Rich (BB code):
blkD :HardDisk - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0) /HD(14,GPT,80868086-8086-8086-8086-000000000008,0x646828,0x16D47D8)
blkE :BlockDevice - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell> _
In this state it cannot be interacted with and won't be detected by my PC over USB.
This happens for normal, recovery and bootloader modes. The only mode that I can access is DNX mode but attempting to boot droidboot will result in the same command line UI described above, including when trying to restore the BIOS using the PC executable (which I assume needs to enter fastboot mode, which it can't do...).
What can I do now? Any way to get anything working in the above screen or through DNX?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp.img when all I have access to on the tablet is DNX mode?
Detailed history below...:
HISTORY
1)
The tablet is a Lenovo Yoga Tab 2 1050F. It was running very slowly to the point where my dad just didn't bother to use it. I thought it would be wise to factory reset it as a first step. There is no option to do so within the Lenovo skin of Android so I started by going into recovery mode and performed a factory reset from there.
After it rebooted, the Android UI would loop back to the language selection after connecting to a WiFi network and I would get "Unfortunately Google Play Services has stopped." error message. It would just loop through the Language Selection > Connect to WiFi network pages over and over.
2)
Having installed CM on my old S3 back in the day, I thought I could go about the same process and flash a gapps ZIP file in recovery mode. That didn't work, I got an error because the zip was unsigned.
I thought I could install TWRP to flash unsigned zips, reinstall Gapps and get the tablet passed the Android UI loop.
3)
I followed this guide on XDA to install an unofficial TWRP (which involved unlocking the bootloader). It didn't work because I couldn't flash over ADB (because the tablet couldn't allow Developer Mode since it was stuck in the Android UI loop). So I flashed as many files as I could in fastboot.
I eventually flashed the TWRP recovery.img but that didn't work : when turning on to Recovery mode it would just go back to the bootloader screen.
4)
I thought I must have screwed up something up so I tried to restore the BIOS using an executable I found but I realized the tablet was already upgraded to Lollipop and the only BIOS restoration exe was for Kitkat. Sure enough it got even worse and I could no longer boot Android.
5)
I still had bootloader and fastboot though so I followed a guide to restore the tablet to the original OS (which ironically I already downloaded before trying to get TWRP but forgot about and didn't unpack). I set up Intel Platform Tools but the flash process didn't work because it went to droidboot and then lost USB connection. On the Intel program it would just stay stuck at 20% Wiping ESP. It would time out twice and then give me a final error message.
6)
So I thought to explore the flash.xml file provided to see if I could do the steps manually. I knew it was stuck at wipe ESP because in droidboot it couldn't get commands from PC. So I went into fastboot and wiped ESP manually myself! Little did I know how foolish this was to do because I was simply unable to flash the provided ESP.img again. Following this I lost access to the bootloader.
7)
I found a guide to restore a bricked 1050F here on XDA but it needs droidboot which now goes to the command line UI described at the top of this post. When attempting to restore the kitkat BIOS again, droidboot is also needed which results in the same cmd UI.
8)
Which leads me to where I am now which is that the tablet doesn't boot to: normal, recovery, bootloader/fastboot or droidboot. Which is why I am now asking for help. What can I do?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp when all I can get access to is DNX mode?
Thanks for reading this far and if you have any more ideas, please let me know, thanks in advance.
Any help please?
Hi, any help please?
Hi all, would anyone like to chime in?
It would seem an update (I think from 2020)has been floating around the net for a while.
I recently decided to revisit my 1050f after I found a replacement screen to change my original one as it was cracked.
At first everything worked Okay but then the tablet decided to do this update,which has totally messed my pad up.
As I have all the old files on my computer from years back,I thought go the the re-install of everything,no matter what I do from Command lines to using "bios restore tool " and intel lite tool with both the original "kitkat" roms and modified roms,nothing will make my pad work again.
I think Lenovo have deliberately released software to break our pads.
I know all my files are good as I have reloaded them before when I was not happy with some things I did.