Just a moment ago I pushed my own custom framework-res to the phone. I had only edited some picture files inside it. After rebooting it worked correctly so I edited some more images, booted into clockworkmod recovery and tried to push in a new framework. But this time my adb just gave me an error "error: device offline".
After rebooting into revoked recovery I tried using adb again but with the same result. I also noticed that my computer suddenly installed all of the Android related drivers again, there were four different drivers it installed.
I thought it was because of my custom framework so I decided to flash my custom rom again. I didn't do a full wipe and after rebooting I got stuck in a bootloop.
So currently the only way I can access the phone is in fastboot. My computer recognizes the phone when it's in recovery but I can't use any adb commands. When I type adb devices it lists my devices but says it's offline. I tried doing the first step of the rooting process and it worked fine but after booting into recovery I tried doing the step2 but the device was still offline.
Is this because of my Windows drivers or did I screw up the Android system somehow?
You should have made a backup using nandroid. I though think you need to wipe.
Sent from something using the internet.
I foolishly let someone try to root my Kindle Fire, and now it is stuck in what seems to be the TWRP boot loop (the kindle fire is blue and white). If I leave it alone unplugged it will occasionally continue to the Kindle Fire orange and white screen but will not go any farther. From the Blue/white screen I can hit the power button to enter the boot menu where I get Normal Boot, Recovery, and Reset Boot Mode. I can enter TWRP recovery menus, but otherwise it just keeps rebooting. Once in the TWRP recovery screen I can only navigate for a short time before it locks up and I have to reboot by holding the power button in. The sd card will not mount, and they did not backup anything before they started messing with the os. Ive tried the Kindle Fire utility but it says device not found. The Kindle showed up in my device manager as Other-Kindle before I installed the android drivers mentioned in another thread, and now it is under Android Phone- Android ADB Interface. It doesnt show up in My Computer at all. I've read about the factory cable but cant find on in the US so it would take 2 weeks to get here from China. Any suggestions on how to fix this, or do I now have a $200 paperweight? Thanks in advance.
Kamakookie said:
I foolishly let someone try to root my Kindle Fire, and now it is stuck in what seems to be the TWRP boot loop (the kindle fire is blue and white). If I leave it alone unplugged it will occasionally continue to the Kindle Fire orange and white screen but will not go any farther. From the Blue/white screen I can hit the power button to enter the boot menu where I get Normal Boot, Recovery, and Reset Boot Mode. I can enter TWRP recovery menus, but otherwise it just keeps rebooting. Once in the TWRP recovery screen I can only navigate for a short time before it locks up and I have to reboot by holding the power button in. The sd card will not mount, and they did not backup anything before they started messing with the os. Ive tried the Kindle Fire utility but it says device not found. The Kindle showed up in my device manager as Other-Kindle before I installed the android drivers mentioned in another thread, and now it is under Android Phone- Android ADB Interface. It doesnt show up in My Computer at all. I've read about the factory cable but cant find on in the US so it would take 2 weeks to get here from China. Any suggestions on how to fix this, or do I now have a $200 paperweight? Thanks in advance.
Click to expand...
Click to collapse
Maybe go into twrp and do a factory reset. Can you get to that menu? Click wipe and then factory reset.
I've tried the factory reset but it seems to have no effect on it. How do I do the adb push? I've tried using the command prompt to run some of the commands on other threads but I'm not doing something right. I always get an 'adb' is not recognized as an internal or external command, operable program or batch file error.
I'll apologize now for my stupidity on this one- I have never worked with android software before this.
The kindle fire utility reads:
ADB status: Offline
Boot Status: Unknown
I can get it to boot in normal and recovery mode, but each time I try to boot in Fastboot I get an error message 'Oops... something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on.' The Kindle shows up in Device Manager under Android Phone as Android ADB Interface
When using the twrp, anything that involves writing to or wiping the sd card receives this error E:failed to mount /sdcard (invalid argument)
I'd appreciate any help I can get. I'm at a standstill on this one.
im in the same position you can open it as a USB by selecting mount in TWRP and selecting mount USB Storage
do you have drivers / ADB on your computer ?
I did manage to get my kindle go into a recovery boot loop by doing the root procedure for the original 6.3 original Amazon ROM while my kindle had the 6.2 ROM . After i realized that the root procedure (intended for ver 6.3) didn't work for me, I had to try the procedure for rooting ver. 6.2.
It worked but after a couple of resets, the tablet went into a recovery boot loop.
what i did was to use ADB comands:
enter windows - > start command prompt (start - > run -> cmd)
check if kindle is connected: adb devices
if the device is found then use:
adb shell
su
idme bootmode 4000
exit
Hi all, I'm having a problem with my Kindle Fire. It is automatically booting into TWRP no matter what I do.
I have wiped everything, and installed the stock ROM, and when I reboot it just goes back to TWRP.
There is always a message of *verifying file system and *verifying partition. I can mount it and move files via USB.
In the fire utility it reads
ADB Status: Online
Boot Status: Unknown
If I try to change the bootmode it comes back waiting for device. I then got into the command line.
Doing "adb devices" shows it as being in recovery. I can reboot it from here, but goes right back to twrp.
I tried to do the adb shell--> su--> idme bootmode 4000
but after I do the shell it comes back that "su" isn't valid. I'm assuming I am doing something wrong, but I can't
for the life of me figure it out...any suggestions? Thanks in advance!
lukebunny said:
Hi all, I'm having a problem with my Kindle Fire. It is automatically booting into TWRP no matter what I do.
I have wiped everything, and installed the stock ROM, and when I reboot it just goes back to TWRP.
There is always a message of *verifying file system and *verifying partition. I can mount it and move files via USB.
In the fire utility it reads
ADB Status: Online
Boot Status: Unknown
If I try to change the bootmode it comes back waiting for device. I then got into the command line.
Doing "adb devices" shows it as being in recovery. I can reboot it from here, but goes right back to twrp.
I tried to do the adb shell--> su--> idme bootmode 4000
but after I do the shell it comes back that "su" isn't valid. I'm assuming I am doing something wrong, but I can't
for the life of me figure it out...any suggestions? Thanks in advance!
Click to expand...
Click to collapse
At startup hold thepower button untill you see the bootmenu come up and select "normal boot"
On the Kindle itself you mean? There is no bootmenu. I get the Kindle Fire (Orange) text, then goes straight to twrp, and if I do normal reboot from there, just straight back to twrp.
lukebunny said:
On the Kindle itself you mean? There is no bootmenu. I get the Kindle Fire (Orange) text, then goes straight to twrp, and if I do normal reboot from there, just straight back to twrp.
Click to expand...
Click to collapse
What version of TWRP do you have?
2.2.0
From twrp try booting into recovery that worked once for me to get a normal boot. Then make sure you put the fire fire fire bootloader on there so it never happens again
Sent from my DROID SPYDER using Tapatalk 2
jamminjon82 said:
From twrp try booting into recovery that worked once for me to get a normal boot. Then make sure you put the fire fire fire bootloader on there so it never happens again
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Tried it, no go.
This is what I get in the command line
The "<[6n" is likely the result of pressing the up or down arrow with number lock turned off and it is causing the command to be unrecognized.
Regardless, there's no need to use the "adb shell su -c..." command to get into fastboot. Instead use Pokey9000's bootmode binary "fbmode".
http://forum.xda-developers.com/showpost.php?p=20755810
Have you tried reboot to bootloader?
Sent from my Galaxy Nexus using Tapatalk 2
hey i got your answer I think? lol anyways...
soupmagnet said:
The "<[6n" is likely the result of pressing the up or down arrow with number lock turned off and it is causing the command to be unrecognized.
Click to expand...
Click to collapse
i'm pretty sure it's bla bla bla \platform-tools in that picture anyways that my answer anyways, maybe not but goodluck anyways........... and this 5 mins between post for low posting users is for the birds
digital_cha0s said:
i'm pretty surs it's bla bla bla \platform-tools in that picture anyways that my answer anyways goodluck
Click to expand...
Click to collapse
As you can see, the "adb shell" command is successful because of the change in the prompt.
~ # <-indicates the shell is working and active, so the actual /path of adb is irrelavent.
soupmagnet said:
Regardless, there's no need to use the "adb shell su -c..." command to get into fastboot. Instead use Pokey9000's bootmode binary "fbmode".
http://forum.xda-developers.com/showpost.php?p=20755810
Click to expand...
Click to collapse
That seems promising, but this is what I got when I tried it.
Also, thanks for your help everyone, I'm learning a lot as I go here!
I was looking to do a full wipe from TWRP and wanted to wipe data as well. Knowing that that would erase everything from the internal storage and not having an SD card available to me now I decided to wipe everything and then transfer the new ROM with adb commands.
Before wiping, I wanted to make sure that adb was working first. So I downloaded the Android SDK and booted to TWRP. Went to Advanced--->ADB Sideload and started the command prompt on my PC. From the folder were adb.exe was I typed "adb usb" and got error:device not found.
I don't know why but after 30 minutes trying to fix that I pressed the "Fix permissions" option in TWRP and now my phone is stuck at the boot logo every time I try to turn it on. I also noticed in Device Manager on my PC that every time I connect the phone to the PC that there is a yellow exclamation mark next to the phone which suggests that I don't have the needed drivers. However I tried to install versions 3.10 and the newest 3.12 and the exclamation mark is still there.
So my question is how do I reach the phone with ADB and transfer the flashable ROM zipfile so I can get the phone past the boot logo?
Well I'll answer myself if anybody has the same problem in the future. It was obviously the USB driver's fault and since none of the LG's drivers worked, I used Google's USB drivers and was able to adb sideload the ROM zip and now it's booting into the OS.
So always check your drivers people! In case LG's don't work, then use Google's!
since this fone was having this issue i decided to try and restore from a working backup:
http://forum.xda-developers.com/g4/help/unable-to-make-phone-calls-dialer-t3278827
i am starting to think that this fones hardware is broken/defective somehow. the key combo to boot into recovery never works.
its supposed to be power+volume-down but it just boots normally.
power+vol-down/release power for 1 second goes into the erase all data: yes/no screen.
whether using android-5.1 or cyanogenmod, adb devices returns nothing; we tried on both windows and fedora; we enabled developer options/adb debugging/oem unlock.
so to test whether the original os could make fone calls i did a twrp wipe/restore of a previous backup. when it booted up it was very unstable/unusable; took a few minutes to respond to touches sometimes; process system has quit errors; random restarts; ...
no apps could launch so that meant i couldnt use quick boot to reboot recovery. adb and key combos dont work so there was no way to get back into recovery.
i put the fone in download mode (volume-up while plugging in usb) and we used LGUP_8994_DLL_Ver_0_0_3_23.msi/LGUP_Store_Frame_Ver_1_14_3.msi to install H81120i_00_0201.kdz which is the lg version of googles version of android-6.0. and we were able to make a fone call. we wanted to boot into twrp to backup but quick boot said that we are no longer rooted. ironically, adb devices now shows the serial-number of the fone so i did sudo adb reboot recovery but when it rebooted instead of going to twrp it showed a green android with a spinning blue cube thingy and rebooted into lg/google-android-6.0 where i had to sign/register for the first time and all our apps/settings were gone.
we origianlly installed twrp using the send_command.exe command on windows awhile back but it no longer works. we installed LGUnitedMobile_Win_Driver_Ver_3.14.1.exe; i run ports.bat and it tells me that the diag port is on COM5; i run Send_command \\.\COM5; it shows me the linux su prompt: #, but when i type in ENTER, it exits back to the windows-dos prompt (i also tried without first typing ENTER, if i try to run something like ls or whoami, it will display: fail).
do all these models have adb/recovery disabled or is this particular unit fubar in that regard ?
any alternative ways to install twrp/ cyanogenmod ?
It is my understanding according to autoprime's thread that you must reinstall twrp after you install the kdz as it wipes that partition as well.
bbenz3 said:
It is my understanding according to autoprime's thread that you must reinstall twrp after you install the kdz as it wipes that partition as well.
Click to expand...
Click to collapse
thanks, how does one install twrp without using send_command.exe.
I tried to root my huawei g8 using twrp, i even took the backup, when i installed SU and tried to reboot it showed "your device is not rooted, swipe to root"...i did what it said...Now the phone directly boots into twrp and show no os installed.... I tried to flash a custom rom but it wont happen....i even tried adb sideload but it shows no device connected on the commnd prmpt(on pc)...Is there any way to recover??? :crying: