Related
UPDATE 3: I've got it back to as stock as I can get it. I think I'm going to just return it and get a new one. Thank you all for your help.
UPDATE 2: As of right now, I'd like to completely remove FFF from the device, but I can only use fastboot to do it. I have absolutely no adb access. Is there a way?
UPDATE: Here is a video showing what is happening to my KF: http://www.youtube.com/watch?v=MH6oUg1NmC0
I hate to start another thread about boot loops/bricking, but I'm not sure what's going on with my fire.
I had CM7 installed successfully since the day after Christmas. This morning I woke up and my Fire was being really sluggish, so I rebooted it (I did not select reboot into recovery).
After it powered on, I was stuck at the CM7 boot screen (with the skateboarding android). I let it sit, but no luck. I went into TWRP to try and restore the backup I made of the stock rom. It looked successful, but when I rebooted I was stuck at the Kindle Fire boot screen.
Next, I tried wiping the device and re-installing CM7, but I received an error (something along the lines of E:Error unable to find /tmp/sideload/blahblah).
So I again restored my backup of the stock rom. Now when I power on my Fire I see the yellow triangle, then the kindle fire logo, yellow triangle, kindle fire logo, and it just keeps repeating. The problem is I am unable to connect to adb because the PC only seems to recognize the adb device for a few seconds after the yellow triangle, which does not give me enough time to fix the problem.
Any ideas?
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
b63 said:
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
Click to expand...
Click to collapse
Recovery shows my battery level to be at 53%. I've got it on the charger now, but I have a feeling there is something else going on.
Also, I am unable to mount my Fire's SD to my computer in recovery. It looks like it is working, but my computer never acknowledges it.
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
b63 said:
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
Click to expand...
Click to collapse
Thanks for the reply. Is adb required to get into fastboot? The problem is that I am unable to get into adb because my computer only sees the Fire for about 1 second. When I go into device manager, I don't see it at all.
EDIT: Yeah, I see the mount in TWRP, but it does not do anything when I select it.
Hi Im a beginner but Id like to try to help :
In case you become desperate ignore twrp's battery display and try wall charger.
Anorher idea id have is to shut down throughr twrp and start up then instead of rebooting.
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
skourg3 said:
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
Click to expand...
Click to collapse
So this time it looks like the installation worked in TWRP, but after reboot now I'm stuck at the CM7 boot screen. This is at least some progress, so when I get home I'll see what I can do.
Sent via my internet connected mobile cellular telephone.
Well, the battery is definitely not the issue. I've been trying to get fastboot, but the problem is the fact that I can not get adb. Has anyone else had issues with getting adb? I've already tried to install the drivers, and that doesn't work.
EDIT: I've tried issuing "adb devices" from the command prompt repeatedly as soon as I hear the ding until it disconnects a second later, but still I have had no luck.
Also, I found this thread in which someone else appears to have had a similar issue to mine.
[Q] New kind of unfixable Super Brick?
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
b63 said:
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
Click to expand...
Click to collapse
I can not seem to get fastboot to work either. Does fastboot rely on adb? Or do you just run the .exe file? I tried to run it, and nothing happened.
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
Just wanted to let you know I updated the OP with a video showing what is happening to my KF.
Haven't tried that particular rom yet, but I have wiped data and cache and attempted to re-install CM7.
great idea with the video !!!
b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
OK, so I restored my original rooted kindle rom, but I still can't get into fastboot because of the problem I showed in the video. It is doing exactly the same thing, just instead of the CM7 boot screen, it is the Kindle Fire boot screen.
Is is possible to get into fastboot without the computer? Can anyone think of a reason why I would not be able to mount my device in TWRP?
I just want to understand something about fastboot... can you upload and flash roms with it? Or can you only get TWRP / FFF with it? I ask because I already have them, and I still can't do anything (mount from inside TWRP doesn't work). Thanks!
Sent via my internet connected mobile cellular telephone.
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
b63 said:
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
Click to expand...
Click to collapse
Cool. I just ordered one of SkOrPn's cables, so once I get it I'll be sure to give an update. Thanks for all the help so far!
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
foxdog66 said:
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
Click to expand...
Click to collapse
Yep, I've used adb successfully, and it is set up as an environmental variable. I actually installed FFF and TWRP with the KFU. Problem is I think something else is botched; perhaps it is TWRP itself, since I am unable to mount from TWRP. I'll try again when I get home.
Sent via my internet connected mobile cellular telephone.
I flashed the wrong kernal and I'm stuck on a bootloop. I can't access my internal storage via TWRP or cant use ADB either. ADB isn't recognizing the device. Is there anyway I can come out of this without losing my data on the phone? I can see the g2 listed as Other Devices in my PC's Device Manager while plugged in. I suppose that has something to do with it. Is there some driver I need to use ADB in recovery?
sacredsoul said:
I flashed the wrong kernal and I'm stuck on a bootloop. I can't access my internal storage via TWRP or cant use ADB either. ADB isn't recognizing the device. Is there anyway I can come out of this without losing my data on the phone? I can see the g2 listed as Other Devices in my PC's Device Manager while plugged in. I suppose that has something to do with it. Is there some driver I need to use ADB in recovery?
Click to expand...
Click to collapse
not sure if you found out already but
all you have t do is go to mount and mount what uou need
sacredsoul said:
I flashed the wrong kernal and I'm stuck on a bootloop. I can't access my internal storage via TWRP or cant use ADB either. ADB isn't recognizing the device. Is there anyway I can come out of this without losing my data on the phone? I can see the g2 listed as Other Devices in my PC's Device Manager while plugged in. I suppose that has something to do with it. Is there some driver I need to use ADB in recovery?
Click to expand...
Click to collapse
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
device manager, right click phone, update drivers, browse computer, let me pick from a list, unclick show compatible hardware, and find LGE or LG and pick the adb driver
Yes, I solved it. Got the drivers fixed.
Fun fact : If your G2 is just getting stuck at boot, turn it off for an over and try again. I stupidly flashed a zip containing a recovery using Flashify and not the boot.img and I got stuck in Fastboot mode or it'd just stuck at the boot animation. I had given up and decided to go back to stock, wiping all my photos. But thankfully the stock flash got stuck because I am using a custom kernal. I turned it off, watched some tv and tried again. Booted right back into the rom. Flashed a proper recovery using adb, got into TWRP, reflashed my rom and didn't lose any data. @autoprime got me through the process via IRC so big kudos to him!
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Added:
If you can't find a patched version, flash cwm or philz recovery with fastboot, adb is working on both of those. You just need a rrcovery image and do
"fastboot flash recovery <recovery-file>.img"
In fastboot mode.
let's try it out!
nvan7891 said:
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Click to expand...
Click to collapse
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
alkkade said:
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
Click to expand...
Click to collapse
i dont know how to fix your problem but i know how u can change the devices not found
install on your computer pdanet driver.
p.s.
i ****ed up my phone as well today i publish a post i will be thankfull if look on my problem.thanks.
alkkade said:
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
Click to expand...
Click to collapse
See the edit to my first response. Fastboot is done in fastboot mode, not recovery, so you should be good. You just need the basic .img file of cwm or philz recovery.
If you are on win 7 try this:
http://adbdriver.com/downloads/
(Adb driver installer)
Run it when you turn adb sideload on in G2 and connect it to PC.
If it fails you still can go buy somewhere USB OTG cable (few bucks) and flash ROM from usb stick like me.
It appears that accessing fastboot pn the lg g2 is not so simple. Sorta like samsung phone deal, where a manufacturer download is used instead. From what I gather, recovery might need to be wiped to access fastboot, which you could do from terminal in twrp, but thats risky. Apparently, a lot of people have gotten stuck in fastboot mode. Best bet would be to reflash stock firmware through lg download mode. Also see this thread for a method to return to stock firmware:
http://forum.xda-developers.com/showthread.php?t=2432476
Once you are back to stock, just reroot and flash revovery, etc.
downloadmode should still work. go back to any kdz for your version
also source and versions post next time
Hi, I was switching rom cuz of many errors and I stucked on TWRP. Im able to enter download mode and adb and internal storage via PC. Whenever Im trying to flash new ROM twrp just restarts. I search whole the forum and no one of guide work for me. Additional full wipe and hard reset doesnt remove previous system. When Im connecting to lg mobile flash he says that I have still OptimusROM. Please help me
@edit:
After a few hours I find a simple solution. If u got the same situation like me just lanuch adb via cmd and write "adb reboot fastboot". After u can restore stock with LG flash tool. Just be sure that u have .kdz file in the same direction.
Xematos said:
Hi, I was switching rom cuz of many errors and I stucked on TWRP. Im able to enter download mode and adb and internal storage via PC. Whenever Im trying to flash new ROM twrp just restarts. I search whole the forum and no one of guide work for me. Additional full wipe and hard reset doesnt remove previous system. When Im connecting to lg mobile flash he says that I have still OptimusROM. Please help me
@edit:
After a few hours I find a simple solution. If u got the same situation like me just lanuch adb via cmd and write "adb reboot fastboot". After u can restore stock with LG flash tool. Just be sure that u have .kdz file in the same direction.
Click to expand...
Click to collapse
Given what you're saying, I'm guessing you're using at least 1 f2fs partition in the custom rom.
This has caused TWRP to panic and reboot for a few people (myself included) when trying to reformat f2fs partitions. The only way to fix that is like you're doing, or wiping the affected partitions back to EXT4, then going back to f2fs if you REALLY want to use it. The reason that this would cause the reboots on install, is because one of the first things most roms do is format cache.
Hi, I wanted to return my g2 to stock rom because I didn't like my custom rom, so I followed the lg flash tool guide(tot):http://forum.xda-developers.com/showthread.php?t=2432476
It worked, but it was jelly bean 4.2 instead of Kit kat 4.4, so I tried to install TWRP so that I can install again a custom rom, but when I tried to backup before flashing TWRP, it wrote "backup Failed", I tried again and it wrote it again, but then the phone just stayed on the boot animation for a few seconds and didnt turn on again. After that, again I tried to do the flash tool method just to return to stock rom but now, it just doesn't work, whenever I insert the DLL and TOT file and start the installation, it goes up to 80% extremely quick and just boots up to TWRP without actually installing the stock rom. So now I'm stuck here with TWRP but without a system to boot to and no rom on my sd card to flash.
I really need help here because I have no idea how to continue.
Thanks for any help!
PriStol said:
Hi, I wanted to return my g2 to stock rom because I didn't like my custom rom, so I followed the lg flash tool guide(tot):http://forum.xda-developers.com/showthread.php?t=2432476
It worked, but it was jelly bean 4.2 instead of Kit kat 4.4, so I tried to install TWRP so that I can install again a custom rom, but when I tried to backup before flashing TWRP, it wrote "backup Failed", I tried again and it wrote it again, but then the phone just stayed on the boot animation for a few seconds and didnt turn on again. After that, again I tried to do the flash tool method just to return to stock rom but now, it just doesn't work, whenever I insert the DLL and TOT file and start the installation, it goes up to 80% extremely quick and just boots up to TWRP without actually installing the stock rom. So now I'm stuck here with TWRP but without a system to boot to and no rom on my sd card to flash.
I really need help here because I have no idea how to continue.
Thanks for any help!
Click to expand...
Click to collapse
You could load the zip you want to flash to a USB drive, then connect it to your phone with an OTG cable. TWRP can read from OTG.
Can you get into download mode? (phone off, hold up volume, insert USB cable connected to computer)
thecadman99 said:
You could load the zip you want to flash to a USB drive, then connect it to your phone with an OTG cable. TWRP can read from OTG.
Can you get into download mode? (phone off, hold up volume, insert USB cable connected to computer)
Click to expand...
Click to collapse
I just tried to do it through an OTG cable, it said that it flashed successfuly, but when I restarted it just went back to TWRP without booting up the system. Also, when I tried to wipe dalvik and cache, it said "wipe failed.". When I rebooted it said "It seems that the device is not rooted"... I really don't know what to do now And I can get to download mode.
PriStol said:
I just tried to do it through an OTG cable, it said that it flashed successfuly, but when I restarted it just went back to TWRP without booting up the system. Also, when I tried to wipe dalvik and cache, it said "wipe failed.". When I rebooted it said "It seems that the device is not rooted"... I really don't know what to do now And I can get to download mode.
Click to expand...
Click to collapse
Can you get ADB connectivity from within TWRP if you connect your device to the PC?
If so you could do the following command from your computer.
Code:
adb push ROM.zip /sdcard/Download/
Then navigate to your /sdcard/Download folder and flash the ROM.
d00lz said:
Can you get ADB connectivity from within TWRP if you connect your device to the PC?
If so you could do the following command from your computer.
Code:
adb push ROM.zip /sdcard/Download/
Then navigate to your /sdcard/Download folder and flash the ROM.
Click to expand...
Click to collapse
When I try to do ADB sideload on TWRP, it just loads forever and doesn't do anything... So I cant get ADB connectivity.
PriStol said:
When I try to do ADB sideload on TWRP, it just loads forever and doesn't do anything... So I cant get ADB connectivity.
Click to expand...
Click to collapse
TWRP should detect your phone without the need for ADB sideload.
If I boot into TWRP, I can instantly run "adb devices" from the terminal my phone is picked up as a "device".
If I choose ADB Sideload, my TWRP hangs just like yours does, but if I run another "adb devices" command my device shows up in sideload mode, regardless of it hanging.
Conclusion, try running the adb commands without running sideload in the first place.
Edit: Upon reflection, this is most likely because I have created an RSA key between the PC and my phone.
d00lz said:
TWRP should detect your phone without the need for ADB sideload.
If I boot into TWRP, I can instantly run "adb devices" from the terminal my phone is picked up as a "device".
If I choose ADB Sideload, my TWRP hangs just like yours does, but if I run another "adb devices" command my device shows up in sideload mode, regardless of it hanging.
Conclusion, try running the adb commands without running sideload in the first place.
Click to expand...
Click to collapse
It just says error: device not found whenever I do a command.
Please help, I really dont know what to do.
PriStol said:
I just tried to do it through an OTG cable, it said that it flashed successfuly, but when I restarted it just went back to TWRP without booting up the system. Also, when I tried to wipe dalvik and cache, it said "wipe failed.". When I rebooted it said "It seems that the device is not rooted"... I really don't know what to do now And I can get to download mode.
Click to expand...
Click to collapse
Did you wiped absolutely everything before flashing? Do you have previous Nandroid backup you can just flash. Anyway if you connect your phone to PC while in TWRP what does your PC show. Anything?
yanis15 said:
Did you wiped absolutely everything before flashing? Do you have previous Nandroid backup you can just flash. Anyway if you connect your phone to PC while in TWRP what does your PC show. Anything?
Click to expand...
Click to collapse
I tried to wipe but it just wrote "wipe failed". I do have a back up on my computer but for some reason when I try to connect my phone to my computer through an OTG cable, it doesn't find the backup. And my pc doesn't show anything when I connect my phone.