Database Users

ADB shell not reconizing it.

I rooted it and installed CM7 on it, CM7 was getting a boot loop so I did a factory reset, I read online that I should reinstall CM7 to help get rid o the boot loop, i turned off the kindle, putting it into recovery mod (like a t**t). Stuck in FFF boot loop, windows reconizses its an ADB device but nether the KF utility, nor ADB thinks its plugged in. I can mount it as a mass storage device. Any help is appreciated.
Edit: This picture better explains what is going on, but as i am a new user, i cannot post a link so I'm sorry but you will have to copy and paste this : i.imgur.com/3Lcsh.png

Did you try this?
adb shell
idme bootmode 4000
reboot

Droidanian said:
Did you try this?
adb shell
idme bootmode 4000
reboot
Click to expand...
Click to collapse
As i was trying to explain adb shell keeps telling me the device isn't found
And before you ask, yes i have installed the drivers and yes i have reinstalled them and yes i have rebooted the device and my computer

Did you try using the command prompt instead of the KFU? I had success doing it manually.

yup, no luck

Remove the KF, uninstall the drivers, restart Windows, and install them manually.
That should work.

no luck, still stuck

Did you edit the "adb_usb" and "android_winusb" files?

HOLY **** after ~ 4 hours of tinkering i got it!!!
Within the KFU i installed the TWRP recovery and while it said waiting for device, I restarted it. I had done this before but it didn't take.
I LOVE THE KFU, IF I HAD ANY MONEY I WOULD GIVE IT TO THEM.
If anyone in the future has this problem and has any questions, PM me and I will try to help you as best as I can.

[Q] Yet another bricked KF

Hello all,
I've got a bricked droid, and haven't been able to find a fix that worked in other threads here.
I rooted my droid successfully, and installed GO Launcher EX, along with the android market, and a number of apps from there.
Among those, busybox, metamorph (which i then used to change the wallpaper), titanium backup, etc. I had successfully rebooted after all these installations and after changing the wallpaper.
I was getting on a plane the other day and turned off the KF, and havent been able to get it to boot since.
Originally it was in a boot loop, getting to the kindle fire icon and rebooting every 3 seconds.
I tried using the KFU, but it was unsuccessful at changing the boot mode (drivers were successfully installed).
Failing at that, i tried following the instructions in http://forum.xda-developers.com/showthread.php?t=1414832
After the reboot, it is now just stuck in the kindle fire screen, and i cant run any adb commands, device not found.
Am I straight up screwed now? or anything I might be able to do at this point.
Much appreciated, thanks for any advice.

Do you have fastboot access? Try running the following...
fastboot -i 0x1949 oem idme bootmode 4000

Try this: http://forum.xda-developers.com/showthread.php?t=1422832

Thanks guys, ill try those and post back w the results.

so i tried fastboot -i 0x1949 oem idme bootmode 4000
and it seems to have been successful, in that it is now back to its original boot loop state. however, it is still not booting fully.
it seems that adb commands are now working, i can do adb shell, and navigate root folders (system etc).
zombie, i havent had much luck with that route, i had tried that earlier.

I've seen people mentioning that the cause for their brick had something to do with permissions, so i did ls -l in the adb shell, here are the permissions for some of the relevant folders. if there are any others that might be helpful, let me know.
root -> drwx------
system -> drwxr-xr-x
sdcard -> lrwxrwxrwx
oh and framework-res.apk -> -rw-r--r-- (same as all other files in that directory)
i did modify the framework-res to change the background image. it successfully booted at least once after the modification - i used metamorph, i loaded the file, then rebooted for it to take effect. this was successful, but i believe it was the next reboot which did my kindle in, so possibly related.
i rambled a bit, but maybe if i replaced the current framework-res.apk with the stock framework-res.apk, that might be worth trying? are all stock framework-res.apk files the same at stock? because i don't have a copy of the original that came with my kindle.

i would go back into fastboot and then flash over TWRP... and then reinstall your os from scratch. it would probably be easier than trying to root around fixing it from the inside.

Thanks xrishox, I might do that. Is there a thread detailing how to do that?
When I tried doing fastboot I lost the ability to use adb commands so I'm not sure how to go about flashing twrp.

Download the fbmode binary and TWRP image. Then run the following.
Code:
adb push fbmode /data/local/temp
adb shell /data/local/tmp/fbmode
arbiter reboot
Your device should reboot and be stuck on the Kindle bootscreen. You are currently in fastboot mode. Now run the following...
Code:
fastboot -i 0x1949 poem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.image
Your device will reboot after that last command. It will boot into the TWRP installer. When it completes, tap "Reboot". Then boot into TWRP recovery and install the factory update, or a custom image that won't replace FireFireFire and TWRP.

jackofaiitrades said:
Hello all,
I've got a bricked droid, and haven't been able to find a fix that worked in other threads here.
I rooted my droid successfully, and installed GO Launcher EX, along with the android market, and a number of apps from there.
Among those, busybox, metamorph (which i then used to change the wallpaper), titanium backup, etc. I had successfully rebooted after all these installations and after changing the wallpaper.
I was getting on a plane the other day and turned off the KF, and havent been able to get it to boot since.
Originally it was in a boot loop, getting to the kindle fire icon and rebooting every 3 seconds.
I tried using the KFU, but it was unsuccessful at changing the boot mode (drivers were successfully installed).
Failing at that, i tried following the instructions in http://forum.xda-developers.com/showthread.php?t=1414832
After the reboot, it is now just stuck in the kindle fire screen, and i cant run any adb commands, device not found.
Am I straight up screwed now? or anything I might be able to do at this point.
Much appreciated, thanks for any advice.
Click to expand...
Click to collapse
Howdy!
I recently just dealt with this same issue. My KF was stuck in boot loop and wouldn't be recognized by my computer. I left it in bootloop until it ran out of battery. Once it was completely drained, I connected it to my computer and my computer recognized it, I then reinstalled the drivers. Right after that I used KFU to change bootmode to normal boot and let it fully charge! Good to go! Hope this helps someone.

from the op of kfu:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and here is a note from vashypooh - the op of kfu
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
maybe it helps someone ...

Thanks guys, I won't be near a computer until tonight but will try these out as soon as I get back

lmntone said:
Download the fbmode binary and TWRP image. Then run the following.
Code:
adb push fbmode /data/local/temp
adb shell /data/local/tmp/fbmode
arbiter reboot
Your device should reboot and be stuck on the Kindle bootscreen. You are currently in fastboot mode. Now run the following...
Code:
fastboot -i 0x1949 poem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.image
Your device will reboot after that last command. It will boot into the TWRP installer. When it completes, tap "Reboot". Then boot into TWRP recovery and install the factory update, or a custom image that won't replace FireFireFire and TWRP.
Click to expand...
Click to collapse
Tone you're a life saver, thanks. I'm up and good to go.

good that it's working again !
have you seen this one in the dev section - could save a lot of handwork:
http://forum.xda-developers.com/showthread.php?t=1428428

Also, when I get back to my computer again, ill update my OP to include the solution so that others might benefit. its like a 20 minute fix but took me days to resolve it (largely due to lack of comp access but that's beside the point).

Rooted 6.2.2?? TWRP help

Kindle looks and acts rooted but i can't install TWRP with KFU.
When it ask the kindle to reboot in fastboot the kindle stays idel in usb mode.
EDIt got it rooted by installing android phone drivers then i rolled them back now it reads as a usb composite device or something, doesn't say kindle with the flag like it did at first.

What commands did you use?

what commands??? i used 5 on KFU it did its thing so far then it said waiting for device after it told the kindle to reboot in fastboot.
I just got this today with stock 6.2.2 and got it rooted finally but i want recovery and other roms >.> THe kindle just doesn't reboot when its told by KFU during TWRP installation.

I think KFU isn't working for 6.2.2 at the moment.
Are you comfortable with running commands from the command prompt? If yes, do you have ADB running properly?

if i have a set of instructions I can use the command line. but not intuitivelly, i got this thing rooted even after installing the drivers gfailed so i did pretty good so far
,

Disregard this post. See my next post.

I has to be root first right, cause i was mistaken and it didn't take. when i run the command line to enable root it gets this message
adbd cannot run as root is in production build.
i even tried the instruction on this link by they are very vague for 6.2.2 and it doesn't tell you were to place files which i assume got to C;\kindleADBhttp://rootzwiki.com/topic/13027-universal-all-firmware-one-click-root-including-262/

Disregard my last post. Do the following.
Download BurritoRoot2.bin from this thread and TWRP from here. Place BurritoRoot2.bin and the TWRP image in the same folder as adb.exe and fastboot.exe (you can use the ones from KFU).
Now run the following...
Code:
adb push BurritoRoot2.bin /data/local/tmp/
adb shell chmod 777 /data/local/tmp/BurritoRoot2.bin
adb shell /data/local/tmp/BurritoRoot2.bin
adb root
adb shell idme bootmode 4002
adb reboot
You were given root access for the adb shell with BurritoRoot2 and that allowed you to change the bootmode. The last command will rebooted the KF into fastboot mode.
When you see a solid "Kindle Fire" logo, you can continue with the following commands...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
The device will reboot and install FFF and TWRP.

I.will be attempting this a lil bit later today have Tiber optics installed and they are due any min.
Thankyou for your help.
Do you guys know why when I command Adb root it tells me its in.production build? This confused me.last night and I am expecting to ru. Into it mater when I attempt to do this root and twrp fix

It's because it isn't rooted. I don't think KFU has implemented BurritoRoot2 yet.

I tried downloading the 6.2.2 update and manually update but when it reboots TWRP 2 says Can't mount /mnt/sdcard/kindleupdates/update-kindle-6.2.2_D01E_3205220.bin
then TWRP gets stuck in a loop only loading into TWRP until I do "idme bootmode 4000"
Anyway, since it seems pretty safe at this point to update to 6.2.2 I want to get it over with now, but am having trouble, is the problem TWRP 2.0?

if you use the original amazon update you will loose fff, twrp and root
take a look at this update method:
http://forum.xda-developers.com/showthread.php?t=1452082
works like a charme

[SOLVED] [Q] fastboot issue

Hi all,
I am currently playing around a bit with my KF and used in the beginning KFU to root with Burrito3. TWRP is functioning + CM9 already installed. BUT now, where I want to use Ravens Kernel with SDK and entering the commands he proposed for the beginning for fastboot, my KF reboots and stops in yellow triangel.
used command:
adb shell
su
idme bootmode 4002
reboot
How to go back to normal boot mode is o.k. and working, but I could no where find what to do/the reason might be, that my KF stops in triangle and how to sort it out. Drivers manually installed with SDK incl. adaption of ini and inf.
Any suggestion?
Thanks and regards
Etam1tlu

Etam1tlu said:
Hi all,
I am currently playing around a bit with my KF and used in the beginning KFU to root with Burrito3. TWRP is functioning + CM9 already installed. BUT now, where I want to use Ravens Kernel with SDK and entering the commands he proposed for the beginning for fastboot, my KF reboots and stops in yellow triangel.
used command:
adb shell
su
idme bootmode 4002
reboot
How to go back to normal boot mode is o.k. and working, but I could no where find what to do/the reason might be, that my KF stops in triangle and how to sort it out. Drivers manually installed with SDK incl. adaption of ini and inf.
Any suggestion?
Thanks and regards
Etam1tlu
Click to expand...
Click to collapse
It's in fast boot mode, just issue the remaining adb commands and you'll be fine.

what do you want to do ? this is the normal behavour when you switch to fastboot ...
---------- Post added at 04:48 PM ---------- Previous post was at 04:47 PM ----------
airmaxx23 said:
It's in fast boot mode, just issue the remaining adb commands and you'll be fine.
Click to expand...
Click to collapse
adb commands don't work in fastboot - only fastboot commands

that is what I tried, because I checked if the device is in fastboot and yes it is shown, but if I follow the next command:
fastboot -i 0x1949 boot bootnew.img or
fastboot -i 0x1949 boot cm9bootnew.img
which I placed on the internal sdcard, I get the feedback of the system:
cannot load 'xxxxbootnew.img'
any help with that?

Etam1tlu said:
that is what I tried, because I checked if the device is in fastboot and yes it is shown, but if I follow the next command:
fastboot -i 0x1949 boot bootnew.img or
fastboot -i 0x1949 boot cm9bootnew.img
which I placed on the internal sdcard, I get the feedback of the system:
cannot load 'xxxxbootnew.img'
any help with that?
Click to expand...
Click to collapse
They need to be in the tools folder where you launcher adb from.
---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------
b63 said:
what do you want to do ? this is the normal behavour when you switch to fastboot ...
---------- Post added at 04:48 PM ---------- Previous post was at 04:47 PM ----------
adb commands don't work in fastboot - only fastboot commands
Click to expand...
Click to collapse
I meant fast boot commands, my bad.

as far as i know these commands are to load a image from your computer
would try to do the img files in the same folder as fastboot.exe and retry

thanks very much for your help, after putting the img files into the folder where the fastboot.exe is, all went well.
very cool and now I learned a bit more regarding ADB stuff

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

LG G2 (Verizon) - Recovery (CWM), no download, bootloop stuck **FIXED**

I will preface this with stating that this is not my phone. A friend had rooted his LG G2 and installed CWM. After he accepted the OTA, the phone was essentially rendered useless. After this process, the phone will be reverted back to 100% STOCK. It took a while to compile all of this information, and I give all credit to respective owners, but this process I pieced together from multiple threads and was able to make this work.
Symptoms-
Not booting (Hanging at LG screen)
Able to access CWM recovery
Unable to Mount USB
Unable to access Download Mode
#####1#####
Uninstall all previous LG Drivers installed (Add/Remove Programs)
#####2#####
Install PDAnet to get the drivers required installed.
#####3#####
Once PDAnet is installed, ADB should recognize the device when it is in 'Recovery' mode.
(ADB Devices should give the result of: ###DEVICEID### Recovery)
#####4#####
Download aboot.img from: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
(The file will need to be renamed to aboot.img)
#####5#####
Download: http://www.androidfilehost.com/?fid=23252070760973106
#####6#####
Extract the files we need:
g2_security
loki_patch
loki_flash
recovery.img
#####7#####
Get into a command prompt and run the following:
adb push g2_security /sdcard/
adb root
adb push loki_patch /data/local/tmp
adb push loki_flash /data/local/tmp
adb push recovery.img /data/local/tmp
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img"
adb shell "chmod 644 /data/local/tmp/aboot.img"
adb shell "chmod 755 /data/local/tmp/loki_patch"
adb shell "chmod 755 /data/local/tmp/loki_flash"
adb shell "/data/local/tmp/loki_patch recovery /data/local/tmp/aboot.img /data/local/tmp/recovery.img /data/local/tmp/recovery.lok"
adb shell "/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok"
adb shell "rm /sdcard/g2_security"
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img"
adb shell "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota"
adb shell sync
adb reboot recovery
Once the above is done, the phone should boot into TWRP. I shut the phone off at this point and held "Volume Up" + "Power" and Download mode now worked!
#####8#####
Uninstalled PDAnet and then followed the instructions on the following page (including installing the drivers)
#####9#####--At this point the following thread finished reverting the phone to stock.
http://forum.xda-developers.com/showthread.php?t=2448960
My only suggestion is that you RUN THE MD5 HASH to ensure the large file downloads correctly. After this was done, the phone was successfully reverted back to stock.
If you found this help, please donate and buy me a beer!
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ZBZ8G6ZPUEN4C

Hi, your last step, a Verizon link for restoring back to stock.. I have international D802.. can I use some other rom(omni rom) instead of your last step...

Guys, this exactly worked for me.. i used D802... however, i used all verizon files only to flash and finally went to download mode and flashed stock ROM... awesome help guys.. i was about to change the PCB by spending half of mobile cost..... i am definitely getting you a case next week...

still nothing
Still stuck in fast boot mode cannot do anything in cwm
---------- Post added at 09:39 PM ---------- Previous post was at 09:35 PM ----------
Still stuck in fast boot mode cannot do anything in cwm. Please can someone help me ??????

:good:
Me too on D802 and it worked. followed exactly as instructed.
thanks bro!

Thanks so much for the guide, one problem for me.... Im on a mac... I have pdanet, and android sdk set up but i cant get the commands to work. any idea on what to use for the commands?
P.S It does find the phone just fine with ./adb devices

dtuma1980 said:
I will preface this with stating that this is not my phone. A friend had rooted his LG G2 and installed CWM. After he accepted the OTA, the phone was essentially rendered useless. After this process, the phone will be reverted back to 100% STOCK. It took a while to compile all of this information, and I give all credit to respective owners, but this process I pieced together from multiple threads and was able to make this work.
Symptoms-
Not booting (Hanging at LG screen)
Able to access CWM recovery
Unable to Mount USB
Unable to access Download Mode
#####1#####
Uninstall all previous LG Drivers installed (Add/Remove Programs)
#####2#####
Install PDAnet to get the drivers required installed.
#####3#####
Once PDAnet is installed, ADB should recognize the device when it is in 'Recovery' mode.
(ADB Devices should give the result of: ###DEVICEID### Recovery)
#####4#####
Download aboot.img from: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
(The file will need to be renamed to aboot.img)
#####5#####
Download: http://www.androidfilehost.com/?fid=23252070760973106
#####6#####
Extract the files we need:
g2_security
loki_patch
loki_flash
recovery.img
#####7#####
Get into a command prompt and run the following:
adb push g2_security /sdcard/
adb root
adb push loki_patch /data/local/tmp
adb push loki_flash /data/local/tmp
adb push recovery.img /data/local/tmp
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img"
adb shell "chmod 644 /data/local/tmp/aboot.img"
adb shell "chmod 755 /data/local/tmp/loki_patch"
adb shell "chmod 755 /data/local/tmp/loki_flash"
adb shell "/data/local/tmp/loki_patch recovery /data/local/tmp/aboot.img /data/local/tmp/recovery.img /data/local/tmp/recovery.lok"
adb shell "/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok"
adb shell "rm /sdcard/g2_security"
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img"
adb shell "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota"
adb shell sync
adb reboot recovery
Once the above is done, the phone should boot into TWRP. I shut the phone off at this point and held "Volume Up" + "Power" and Download mode now worked!
#####8#####
Uninstalled PDAnet and then followed the instructions on the following page (including installing the drivers)
#####9#####--At this point the following thread finished reverting the phone to stock.
http://forum.xda-developers.com/showthread.php?t=2448960
My only suggestion is that you RUN THE MD5 HASH to ensure the large file downloads correctly. After this was done, the phone was successfully reverted back to stock.
If you found this help, please donate and buy me a beer!
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ZBZ8G6ZPUEN4C
Click to expand...
Click to collapse
My ADB keeps saying that my phone is unauthorized ;( I can only access .zip. Anyone else have this issue? Have tried multiple drivers, Sideload is the only thing that works.

Joppykid said:
My ADB keeps saying that my phone is unauthorized ;( I can only access .zip. Anyone else have this issue? Have tried multiple drivers, Sideload is the only thing that works.
Click to expand...
Click to collapse
Are you connected via PDAnet?

dtuma1980 said:
Are you connected via PDAnet?
Click to expand...
Click to collapse
I can't because I cannot turn on USB Debugging, I am stuck in the Recovery. Details of my situation are in this thread I posted. http://forum.xda-developers.com/showthread.php?t=2726985

Joppykid said:
I can't because I cannot turn on USB Debugging, I am stuck in the Recovery. Details of my situation are in this thread I posted. http://forum.xda-developers.com/showthread.php?t=2726985
Click to expand...
Click to collapse
Oh boy i got the same issue before. I just go to a local technician to have it fixed.

Joppykid said:
I can't because I cannot turn on USB Debugging, I am stuck in the Recovery. Details of my situation are in this thread I posted. http://forum.xda-developers.com/showthread.php?t=2726985
Click to expand...
Click to collapse
Same issue here. In the command prompt, anything I do returns the unauthorized device error.
EDIT- I'm going to try and sideload a custom ROM, and then flash the stock ROM after setting USB debugging to see if that helps at all. I'll let you know

Joppykid said:
I can't because I cannot turn on USB Debugging, I am stuck in the Recovery. Details of my situation are in this thread I posted. http://forum.xda-developers.com/showthread.php?t=2726985
Click to expand...
Click to collapse
Please refer to the initial post. This will only work if you can access the recovery. If you cannot access recovery, this method isn't going to work. Sorry!

dtuma1980 said:
Please refer to the initial post. This will only work if you can access the recovery. If you cannot access recovery, this method isn't going to work. Sorry!
Click to expand...
Click to collapse
Did you not see what I wrote? Recovery was the only thing I could access. This method didn't work because the RSA Token wasn't authenticated on my computer any longer. My phone was bricked. I now have a new one. Lesson learned. Make sure you have USB debugging on with an RSA token on your computer at all times.

Did you end up wiping the internal SD with the process? I am in a similar situation except I don't have a friend like you to help me out haha.

Joppykid said:
My ADB keeps saying that my phone is unauthorized ;( I can only access .zip. Anyone else have this issue? Have tried multiple drivers, Sideload is the only thing that works.
Click to expand...
Click to collapse
I factory wiped/reset my phone is CWM which got my phone to be recognized as in recovery.
I can't get past the adb shell commands to work. it keeps saying 'dd: can't open '/data/local/tmp/aboot.img' : Not a directory
I tried with the double quotations and without to see if the command would work thinking I was messing up the syntax.

perfect just saved my a$$. ota took for the 24a update. found this and i am back where i was.awesomes