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!
Related
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.
After succesfully rooting my Kindle, I flashed a JB bulid. About a month later wanting to flash an update I noticed I have no recovery and no more FFF boot logo. I tried usiong KFU, but nothing worked. After searching through pages and pages, I decided to uninstall drivers as many have suggested, and delete, then reinstall kfu. I finally got it working again. I flash another rom, and two weeks later, no recovery or fff.
I repeated my steps to no avail. Trying KFU, or getting into fbmode, leave me nowhere, but with a cmd prompt screen with waiting for device.
On KFU my ADB status is online and Boot status 4000
When trying to install FFF I get: failed to copy 'files\fbmode' to data/local/fbmodeermission denied
Unable to chmod /data/local/fbmode: No such file or directory
/system/bin/sh: /data/local/fbmode:not found
Same when trying to install TWRP. When screen prompt initiates fbmode reboot, it boots into normal os.
adb devices gives me this reading 0123456789ABCDEF.
While trying Pokey 9000's fbmode, I was able to enter fbmode, but trying to install TWRP again left me with Waiting for device..
Any help/suggestions would be appreciated.
I'm not sure if /data/local/ is user writable. I've always used /data/local/tmp/ for this purpose. Here are some manual instructions to get TWRP and FFF installed manually...
http://forum.xda-developers.com/showthread.php?t=1638452
Fastboot mode uses a different interface than adb, so your Windows box may not have the drivers properly installed for it even if adb is working. You might also have to force the KF off by pressing/holding the power for 20 seconds or so and then restart it because both the host and the KF must see the other the moment the device goes into fastboot mode. Check the second post for help on getting the device drivers working properly...
http://forum.xda-developers.com/showthread.php?t=1552547
I tried pokey's fbmode which worked. Now I'm stuck in fbmode and can't get out.
When trying to flash TWRP it would not pass waiting for device
When I connect to my pc, a propmt states device is unrecognizable.
Device manager only shows USB Mass Storage with exclamation.
ADB does not recognize device
Here try this iso*http://db.tt/KDNzyCTP
*Instructions:*
1. Download this http://www.pendrivelinux.com/
2. Download iso
3. Preformat usb in windows
4. Select try unlisted Linux iso from the very bottom of dropdown in universal usb installer
5. Select iso
6. Select usb drive letter
7. Tick format
8. Create
9. Eject safely and remove
10. Shut down computer
11. Insert and power on computer
12. Select boot from usb and use..
All you need is a 2 gig usb flash drive to create this live linux adb and fastboot are preconfigured
different build but thread found here http://forum.xda-developers.com/showthread.php?t=1882565
kinfauns said:
I'm not sure if /data/local/ is user writable. I've always used /data/local/tmp/ for this purpose. Here are some manual instructions to get TWRP and FFF installed manually...
http://forum.xda-developers.com/showthread.php?t=1638452
Fastboot mode uses a different interface than adb, so your Windows box may not have the drivers properly installed for it even if adb is working. You might also have to force the KF off by pressing/holding the power for 20 seconds or so and then restart it because both the host and the KF must see the other the moment the device goes into fastboot mode. Check the second post for help on getting the device drivers working properly...
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Windows,Windows,Windows...Why must I reboot so much!
After installing/Unstalling drivers, many reboots, and unplugging/plugging in usb, I've finally got it fixed. Big thanks for those guides. Everything I needed was right there, except my pc was being a real d***head about these drivers.
I uninstalled faulty USB mass storage drivers then reinstalled, and it recognized my device immediately
Now that I have it fixed, any insight on why I lost TWRP and FFF. I would hate for this to be a recurring issue. Especially if I have to wait for my pc to play ball..
I really dont know what you did to wipe fff and twrp but I would say that your case is extremely rare in fact Im sure there is great debate about whether it is even truly possible... And if you were able to duplicate it would be quite impressive... It certainly wouldnt hurt to flash a little smirkit when you change roms if you do it frequently http://forum.xda-developers.com/showthread.php?t=1500935 as far as I know the only thing that will wipeout fff and twrp like that is update.zip your case I believe is only the 3rd that I have ever heard this happening to. I can almost say with at least 98 % certainty that one of those occasions was purely user error.......
Thepooch said:
I really dont know what you did to wipe fff and twrp but I would say that your case is extremely rare in fact Im sure there is great debate about whether it is even truly possible... And if you were able to duplicate it would be quite impressive... It certainly wouldnt hurt to flash a little smirkit when you change roms if you do it frequently http://forum.xda-developers.com/showthread.php?t=1500935 as far as I know the only thing that will wipeout fff and twrp like that is update.zip your case I believe is only the 3rd that I have ever heard this happening to. I can almost say with at least 98 % certainty that one of those occasions was purely user error.......
Click to expand...
Click to collapse
I'm not too sure if I lost TWRP, but I know I lost fff. Kfu and fastboot wasn't working. I know when things like this happen, usually a step was missed.
Sent from my HTC Sensation using xda premium
Hello everyone!
A few days ago, my Kindle Fire crashed during use and I could not get it to reboot. I reflashed the ROM I used that I kept in /sdcard (now I realize that I should have done a factory reset beforehand, but, alas, that's in the past) and could not get it to boot, so I connected the thing to my PC and tried to just get the stock ROM back on with KUU, but it failed to write it while in fastboot. In fact, fastboot seems to fail to write any update.zip, as doing it from terminal gives me the error "android-info.txt or android-product.txt not found in archive". Of course, now I decided to be an idiot and perform a wipe, including the ROM from my /sdcard folder in it. This wouldn't be as big a problem if I had access to ADB; however, I don't. When in TWRP 2.5 Recovery, the device doesn't show up at all under Device Manager, neither as "Kindle" or "Android ADB Composite Device". Therefore, I can't use adb push to have a ROM to flash. Seems peculiar to me, since I can access fastboot just fine, albeit under the name "Kindle Blue Fastboot Mode | Gen 1" instead of "Android ADB Interface" (I assume FFF 1.4a is installing some driver hidden in it's files?) I also attempted to use USB Mount to just drop the zip onto the Kindle, but it did not show up on my PC either.
This leaves me with three possibilities, unless you guys think of a fourth one.
1. Activate ADB for my Kindle in recovery, somehow (you'll need to direct me how to even touch this).
2. Use fastboot to put a ROM on (again, either someone needs to show me how to get fastboot flash update update.zip to work, or possibly there's a way to push files in here too?)
3. Use USB OTG in TWRP to install a ROM. I'm not even sure if this is a thing that's supported, but I'll try after I get a little more juice in the tablet (Edit: doesn't seem to work, sadly :crying
Thanks so much for viewing this thread, I hope one of you has some insight on how to fix my problem
Demostrs said:
Hello everyone!
A few days ago, my Kindle Fire crashed during use and I could not get it to reboot. I reflashed the ROM I used that I kept in /sdcard (now I realize that I should have done a factory reset beforehand, but, alas, that's in the past) and could not get it to boot, so I connected the thing to my PC and tried to just get the stock ROM back on with KUU, but it failed to write it while in fastboot. In fact, fastboot seems to fail to write any update.zip, as doing it from terminal gives me the error "android-info.txt or android-product.txt not found in archive". Of course, now I decided to be an idiot and perform a wipe, including the ROM from my /sdcard folder in it. This wouldn't be as big a problem if I had access to ADB; however, I don't. When in TWRP 2.5 Recovery, the device doesn't show up at all under Device Manager, neither as "Kindle" or "Android ADB Composite Device". Therefore, I can't use adb push to have a ROM to flash. Seems peculiar to me, since I can access fastboot just fine, albeit under the name "Kindle Blue Fastboot Mode | Gen 1" instead of "Android ADB Interface" (I assume FFF 1.4a is installing some driver hidden in it's files?)
This leaves me with three possibilities, unless you guys think of a fourth one.
1. Activate ADB for my Kindle in recovery, somehow (you'll need to direct me how to even touch this).
2. Use fastboot to put a ROM on (again, either someone needs to show me how to get fastboot flash update update.zip to work, or possibly there's a way to push files in here too?)
3. Use USB OTG in TWRP to install a ROM (I'm not even sure if this is a thing that's supported, but I'll try after I get a little more juice in the tablet)
Thanks so much for viewing this thread, I hope one of you has some insight on how to fix my problem
Click to expand...
Click to collapse
"fastboot flash update.zip" doesn't work on the KF btw.
I haven't had a chance to look at hardware IDs or see how KFU's drivers are configured these days, but it may serve you well to use fastboot and install an earlier version of TWRP. Maybe a 2.4.x version to start out with...
soupmagnet said:
"fastboot flash update.zip" doesn't work on the KF btw.
I haven't had a chance to look at hardware IDs or see how KFU's drivers are configured these days, but it may serve you well to use fastboot and install an earlier version of TWRP. Maybe a 2.4.x version to start out with...
Click to expand...
Click to collapse
Rolled back to 2.4.4.0 and 2.2.2.1, no dice
Edit: I did buy two new Micro-USB cables, should I wait until I get them to try and get my Kindle recognized by my computer? This person did the same (http://forum.xda-developers.com/showpost.php?p=25896517&postcount=12) and I feel like when I can get ADB to run, I can fix everything from there. It just seems odd to me that Fastboot would be recognized and the tablet can charge when in recovery on the same cable, it just can't access ADB.
Got the new cables today, still nada. Tried on my Win8 desktop, Win7 laptop, and Ubuntu Laptop, and none of them even showed that a device was plugged into it in recovery. Any other tips before I try to get Amazon to replace this thing?
Any further instruction I should try? I really want to get this thing in operation...
I everyone,
I need your help, I tried to install a new rom (AICP : this one) , and somehow forgot to do a backup.
When I boot I only get the swirling logo, never get to fully load.
The phone is not bricked, I can still access the bootloader / fastboot and my recovery, so I could simply flash another rom... but I can't figure how to get the zip file on the /sdcard.
I can't use adb sideload or push, I have HTC sync and android sdk installed, I have no problem to use fastboot commands, so I guess I don't have any driver problem, but adb devices never shows my phone (Tried while off, booted on bootloader, on fastboot, and on recovery, never shows up when I try adb devices)
On windows I get a driver error when plugging my phone while in recovery, but I don't find how to install it.
So... is there a way to mount the /sdcard/ as an external drive in windows or ubuntu ? Or do you have a workaround for adb ?
Thanks a lot !
Vincent
I hope all of you would be fine.
I was trying to install a custom ROM in my HTC one X via CWM recovery. I formatted the system partition (ROM) and tried to flash the new ROM. I ended up soft bricking my phone as the ROM file was corrupt. I tried to push another ROM.zip file into the phone memory via adb. My phone shows up in fastboot devices when it's turned on but it's not detected as adb device. When I turn it off then it shows up in the attached adb devices list. I used the adb push command to transfer the ROM file into the phone memory and cmd tells me it's done as it shows the transfer speed and the size of ROM file. Now the issue is that when I try to search for that ROM file in CMW recovery, it's not there in the memory.
It's been three days since I have been trying to make my phone alive but nothing seems to work.
Any help from you guys would really be appreciated
*My phone shows up in abd devices only when it's turned off.
*The adb pushed ROM.zip file is not present in the phone memory.
*All the drivers are correctly installed and my phone is listed as 'My HTC' in device manager.
Hey there, sorry for a late answer, but right now I have some town-wide internet problems, so...
Back to your problem then, if you cant have any result with adb push, try to use another method:
1. Complete steps at this link https://twrp.me/htc/htconexinternational.html to install twrp
2. Reboot to your twrp recovery
3. Choose "Mount" option and mount any partition you need(depending on your layout), after this step, you can access you phone storage with you pc.
4. Now you can wipe everything you want, do not reboot, and go to "install" option.
5. Just copy/paste you ROM, install it, reboot to fastboot, flash boot.img
Done.
Have a nice day.