Database Develop

How to wipe w/o recovery or adb?

I was following the steps to update to Cyanogen's newest ROM and going through the steps on Cyanogenmod. I wiped, had both ROM's on my SD card and fell asleep while it was flashing the HTC recovery image. Well I must not have slept long and for some reason I thought it was done, but apparently I rebooted before the entire flash had finished. Right as I was rebooting I realized it said it was "formatting CACHE" but it was to late..I already started the reboot. So now my phone will get to the second loading screen that says "android" and then goes to a black screen. I have no recovery but can get into fastboot. I have the 1.6 SDK on my laptop, but have never used it, so the drivers aren't in place and plugging my phone in via USB does nothing.
I have read MANY posts about similar situations, but almost all of them involves using fastboot and ADB to push and install files, but how is that possible if I can't get ADB to work?? What else can be done via fastboot?? I know my phone isn't bricked, but not sure how to proceed from here.

I got a little further with my phone. I have ADB running on my laptop and I even got my computer to recognize the G1 as Android 1.0, but when I run ADB in a CD, it's not listing the phone. I am guessing because before this I wiped and never went and turned on USB de-bugging.

I ended up following the steps to downgrade, root, and ended up with a working phone.

[Q] Soft brick(?)/usb drivers issue

Hey all! I'm having some big problems getting my phone working. I was running Venom One rom for a while but then decided to try out something else and installed the CM 11S. Again phone worked perfectly but I got used to using Venom so I wanted to go back to it. And that's where I fu**ed it I think... I've installed the rom (I'm using T.W.R.P 2.7.1.1, standard cache and data format) like previously and again everything went smoothly with no errors. However, when I restarted the phone it got stuck on HTC logo. But it wasn't stuck like you couldn't do anything, I could lock the screen and when I unlocked it it would present me with the usual lock screen, time, taskbar etc. but when you unlocked it it went back to the HTC logo after a while an error popped up saying that the htc dialler was not responding. I haven't came across something like that ever before... So I went back to recovery and flashed the system again and again I had the exact same issue. So then I went and formatted everything including my internal storage, and that's where I made the biggest mistake. I forgot that I had the rom zip on internal storage and I'd lose it if I format the partition. No problem you'd say BUT I can't copy anything onto the phone.
When I connect the phone to my PC in recovery mode it just refuses to mount!! No matter which partition I want to mount, nothing comes up in my computer. I went on to the device manager and surely enough the HTC One is an unknown device... I tried side-loading the rom but the adb can't connect to the phone. I tried re-installing the HTC sync just to make sure I definitely have the usb drivers but still no luck. ADB devices command shows no devices connected. I've run out of ideas and I'm regretting my decision to try different roms...
I really don't want to buy a new phone so if anyone has ANY ideas please right it down. Thanks in advance!

bboybtek said:
Hey all! I'm having some big problems getting my phone working. I was running Venom One rom for a while but then decided to try out something else and installed the CM 11S. Again phone worked perfectly but I got used to using Venom so I wanted to go back to it. And that's where I fu**ed it I think... I've installed the rom (I'm using T.W.R.P 2.7.1.1, standard cache and data format) like previously and again everything went smoothly with no errors. However, when I restarted the phone it got stuck on HTC logo. But it wasn't stuck like you couldn't do anything, I could lock the screen and when I unlocked it it would present me with the usual lock screen, time, taskbar etc. but when you unlocked it it went back to the HTC logo after a while an error popped up saying that the htc dialler was not responding. I haven't came across something like that ever before... So I went back to recovery and flashed the system again and again I had the exact same issue. So then I went and formatted everything including my internal storage, and that's where I made the biggest mistake. I forgot that I had the rom zip on internal storage and I'd lose it if I format the partition. No problem you'd say BUT I can't copy anything onto the phone.
When I connect the phone to my PC in recovery mode it just refuses to mount!! No matter which partition I want to mount, nothing comes up in my computer. I went on to the device manager and surely enough the HTC One is an unknown device... I tried side-loading the rom but the adb can't connect to the phone. I tried re-installing the HTC sync just to make sure I definitely have the usb drivers but still no luck. ADB devices command shows no devices connected. I've run out of ideas and I'm regretting my decision to try different roms...
I really don't want to buy a new phone so if anyone has ANY ideas please right it down. Thanks in advance!
Click to expand...
Click to collapse
don't worry, you'll not have to buy another phone. Your issue is one of the most common issue we see here. First I will recommend you to use twrp 2.7.1.1 only to flash CM11 based roms and use twrp 2.6.3.3 or 2.6.3.4 for any Sense based roms.
You will first need to fix your drivers issue so you can adb push or adb sideload the rom to your phone again. there is a guide linked in my signature (nkk71's guide). In this thread, there is instruction (in the FAQ #2) about how to solve drivers issues.
When your drivers issue are solved, flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp 2.6.3.3 and adb push or sideload venom and hopefully it will be able to boot and it will be stable.

alray said:
don't worry, you'll not have to buy another phone. Your issue is one of the most common issue we see here. First I will recommend you to use twrp 2.7.1.1 only to flash CM11 based roms and use twrp 2.6.3.3 or 2.6.3.4 for any Sense based roms.
You will first need to fix your drivers issue so you can adb push or adb sideload the rom to your phone again. there is a guide linked in my signature (nkk71's guide). In this thread, there is instruction (in the FAQ #2) about how to solve drivers issues.
When your drivers issue are solved, flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp 2.6.3.3 and adb push or sideload venom and hopefully it will be able to boot and it will be stable.
Click to expand...
Click to collapse
The only weird thing is, I used the 2.7.1.1 to flash the sense rom in first place and everything worked fine :/ . Anyway, thanks for the shout! :good: I'll give it a try right now and see how it goes.

Right, I'm having problems installing the drivers for some reason. The ones downloaded from this thread don't seem to be doing anything at all. When click on them they show up for a split second in task manager and then they disappear. No install wizard no nothing. So i downloaded the ones for Windows 7 from here but this just gives me a message that "Windows could not find driver software for your device." . I mean, what the hell?
Edit: Right, after a lot of struggle I've managed to successfully bring my phone back to life! I have no idea what caused the issues with installing the drivers. I've spent ages deleting every trace of HTC drivers, then installed Windows 7 ones and somehow it worked. Then flashed t.w.r.p 2.6.3.3 and venom and it seems to be working smoothly! Hopefully no more problems . Thanks a lot for helping out man!

[help] got a soft brick after a build.prop edit

A while earlier I was trying to enable tethering on my at&t N6 by editing the build.prop and after the reboot it's stuck in a boot loop. I don't imagine that this is important but it doesn't get to the dots animation; just white Google and the unlock at the bottom. I am still able to get into fastboot and recovery (stock one). I have a backup of the correct build.prop in the /system file named build.prop.back , so I'm hoping that there's a way to revert to that without needing to wipe my device again, but I'm not sure.
I found this thread, however my computer isn't recognizing the device when it's in recovery mode. I have the fastboot drivers installed (needed to root), so that may be why but, again, I'm not sure. the adb devices command shows that there is no device, I imagine because the driver is not installed.
any help would be appreciated. thanks in advance.

Try the ADB & Fastboot installer from this thread - http://forum.xda-developers.com/showthread.php?t=2588979

jj14 said:
Try the ADB & Fastboot installer from this thread - http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Unfortunately that didn't fix the problem.
Do you know if the fastboot driver and recovery driver would be different? As far as I can tell from my research, I think they're the same, but I could be wrong. Hopefully that's the problem and you can direct me towards the correct driver.
If I select "show hidden devices" in the device manager, it shows the phone as ADB Interface, and I tried undating the driver for that but it said it was already up to date. not sure what to do from here.
Thanks for your help.

Install working drivers if you can. This is important on so many levels. If they are installed correctly you type ADB devices, you should see your device. If you do type adb reboot bootloader, it should reboot to bootloader. Type fastboot devices, you should see same device name. Pat self on back.
Once that is all good I'd install the latest TWRP img file for your whale, straight off TWRP website (do you know how to do this? fastboot flash recovery recovery/name.img) . Once you do that go to your new recovery by pushing vol-down twice then your power button, inside TWRP you mount system and go into the file manager inside TWRP and swap/rename build.prop files. At this point, please make a backup inside TWRP. This backup will be on your internal memory, also save a copy to your computer in case you accidentally reformat your internal memory like every noob that uses toolkits. Having a backup is very important when you are screwing around with your phone. Reboot and profit.

jawmail said:
Install working drivers if you can. This is important on so many levels. If they are installed correctly you type ADB devices, you should see your device. If you do type adb reboot bootloader, it should reboot to bootloader. Type fastboot devices, you should see same device name. Pat self on back.
Once that is all good I'd install the latest TWRP img file for your whale, straight off TWRP website (do you know how to do this? fastboot flash recovery recovery/name.img) . Once you do that go to your new recovery by pushing vol-down twice then your power button, inside TWRP you mount system and go into the file manager inside TWRP and swap/rename build.prop files. At this point, please make a backup inside TWRP. This backup will be on your internal memory, also save a copy to your computer in case you accidentally reformat your internal memory like every noob that uses toolkits. Having a backup is very important when you are screwing around with your phone. Reboot and profit.
Click to expand...
Click to collapse
I though I had the working drivers... Whenever I boot into fastboot/ bootloader, I can do fastboot devices and the phone shows up, but for whatever reason adb devices returns an empty list everywhere. It's empty in fastboot and recovery and while the phone is stuck in it's bootloop...
I'm fairly confident I can flash TWRP without any problems. I had an old galxy tab 2 that i flashed cyanogen onto a while ago, however i used clockwork for that recovery. I don't imagine it would be too much different though.
edit: also might be worth noting that I'm using a windows 8.1 computer for this. not sure if it matters or not, but it might be useful

momo5732 said:
I though I had the working drivers... Whenever I boot into fastboot/ bootloader, I can do fastboot devices and the phone shows up, but for whatever reason adb devices returns an empty list everywhere. It's empty in fastboot and recovery and while the phone is stuck in it's bootloop...
I'm fairly confident I can flash TWRP without any problems. I had an old galxy tab 2 that i flashed cyanogen onto a while ago, however i used clockwork for that recovery. I don't imagine it would be too much different though.
edit: also might be worth noting that I'm using a windows 8.1 computer for this. not sure if it matters or not, but it might be useful
Click to expand...
Click to collapse
You are ok w/ your problem because you can get to fastboot screen. Don'y worry about adb drivers for now. Do what I said in my earlier post in the 2nd paragraph, start w/ installing TWRP img then do the rest and it will work for you. Win 8.1 seems to have its difficulties but we'll worry about that later after you get TWRP installled.

jawmail said:
You are ok w/ your problem because you can get to fastboot screen. Don'y worry about adb drivers for now. Do what I said in my earlier post in the 2nd paragraph, start w/ installing TWRP img then do the rest and it will work for you. Win 8.1 seems to have its difficulties but we'll worry about that later after you get TWRP installled.
Click to expand...
Click to collapse
OK. twrp is making a backup as I type. is this backup the same thing as a nandroid backup? i hadnt heard of them before I decided to root.
It should boot properly now. I'll update when it's done.
Edit: IT BOOTS! thank you so much.
Edit 2: So I'm not really sure why it works now but adb recognizes it when its in twrp... odd. I tried to reinstall the drivers with the most recent version i could find, but it didn't look like it actually updated anything. maybe stock recovery was just broken? I'm not sure...

momo5732 said:
OK. twrp is making a backup as I type. is this backup the same thing as a nandroid backup? i hadnt heard of them before I decided to root.
It should boot properly now. I'll update when it's done.
Edit: IT BOOTS! thank you so much.
Edit 2: So I'm not really sure why it works now but adb recognizes it when its in twrp... odd. I tried to reinstall the drivers with the most recent version i could find, but it didn't look like it actually updated anything. maybe stock recovery was just broken? I'm not sure...
Click to expand...
Click to collapse
Cool glad it's working. Yes backup=nandroid
It's cool now I've also noticed the computer recognizes phone in TWRP. You can drag and drop files onto the phone while it's in TWRP not just booted in android, couldn't do that before unless I'm wrong which is often. This is really cool as I always forget a file or two or its location on SD card.

[Q] Bricked L70

Hi,
so I rooted my phone, unlocked the bootloader, installed TWRP, put in 3 different ROMs on my External SD card, went ahead, deleted EVERYTHING from the phone, tried flashing ROMs, not a single one worked.
I rebooted the phone because I saw no other option, TWRP said that there is no OS, I went ahead and did it.
Now the phone won't start, I tried returning it to stock firmware as per lg-phones website guide (worked before, though my phone was not this messed up, I could access download mode and now I can't), but I keep getting connection problems. I have tried doing this with the phone just "turned on", it hangs on LG logo for infinity.
When I try putting the phone in download mode, the only thing I get is fastboot. When I try to use adb devices and other similar commands, it says device not found or simply does not list it, regardless of the "mode" the phone is in. However if I try and use LAF RECOVERY MULTITOOL, it detects my phone and I can use fastboot commands. I have custom recovery, boot and laf imgs on my PC, I tried flashing them all, PC and phone tell me everything's ok, but when I restart the phone, I get nothing... what am I doing wrong, and can this be fixed? If you have any questions, I'll answer to the best of my ability.
Thanks in advance!

SOLVED!!!!
Just found a backup laf.img that enables download mode... PHEW!

Can someone PLEASE help me boot my phone into FASTBOOT mode? ( T mobile h811) on CM13

When I first purchased this phone I was able to boot to the default recovery that came with the phone ( which clearly had a *fastboot option*), it came with stock 5.1, and a bunch of bloatware.
I downloaded the one click root method for the h811 which was perhaps the easiest root i've ever done. great. i also had to flash my recovery to twrp 2.8 for some reason.
Rocked out to a newely rooted device on 5.1 until the t mobile bloatware and system update notification kept bugging me, so I said * eff it, i've been holding out for a while*
So I get to the cm 13 wiki for my device, I managed to install the cm recovery ( cant remember how i did this for some reason) and then i was able to flash cm13 to my phone. CM13 is sleek, and smooth but is presenting problems.
First of all, no google play store and the gapps zip wont install through cm recovery ( fails and tells me to use twrp instead which is a problem because i can't boot this phone into fastboot mode)
I am unrooted and can not figure out how to properly root a T mobile h811 running cm13, so the twrp manager doesn't work because it "requires root" then shuts down. ( enable root access in the cm13 developer options does nothing at all and yes, for adb and apps)
FAST BOOT MODE DOES NOT SEEM TO EXIST ANYMORE ON MY PHONE - Following the many tutorials, which goes long the lines of using adb/fastboot, adb devices can see my device, but fastboot devices can't ( figures) because its not in fastboot mode. Any fast boot reboot bootloader or any variant of that command only reboots the phone, to... swipe the screen.
I've installed the lg bridge crap ( which installed an updated usb driver) that doesn't even recognize my phone " no mobile device connected". tried uninstalling and reinstalling, but nothing. When putting the phone in download mode, to see if adb would rcognize it, windows sees this as a new device , installs drivers but says " device can not start, code 10 * in device manager. :silly:
is there anything that can be done?? google searches result in obvious solutions that SHOULD work but don't, or threads where a person coincidentally has the same exact problem as I do, but their response is usually the last response in the thread that goes unanswered
summary : I've install cm13 on my lg g4 h811, I do not have root access, I can not install twrp due to ( no fastboot mode) in effect, i cant install gapps, cant root phone etc..
any help?

did you ever unlock the phone....?

Yes, unlocking the phone is one of the first things you would need to do. In Developer Options > OEM Unlock. Then in bootloader, run the unlock command. This will delete /data and internal storage so back up your files so you can transfer them back via adb or fastboot.
Then you're probably going to need to temp boot TWRP, then flash the TWRP recovery image in TWRP. THEN you can flash properly.
Carefully read through this thread:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Good luck.
Edit: oh and this thread belongs in Q&A.

Alright. Am I only to read the first post or all 30+ pages? ( not that i have a problem, just curious)

Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.

aoaleman said:
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
Click to expand...
Click to collapse
"ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it."
didn't work, very frustrating. any clues? on windows 8.1 by the way. tried two computers. none can see this phone. I can connect the phone to the computer and see its storage, lg usb driver is installed

You probably need to reinstall the drivers. It might be the fastboot driver. That's what worked for me.

I've reinstalled the official drivers, uninstalled them... Jusst the mobile USB driver, a combo of both, plenty of times. Don't understand why this software doesn't see my phone
Lgup, lgair, lg bridge, lg USB driver (skinned down) .. Nothing works tested on my gaming rig., and work laptop both running win 8.1 64 bit

Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know

TacoTuco said:
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
Click to expand...
Click to collapse
This section does get more views though haha.
Anyway I feel that the 811 is one of the more finicky devices to get into fastboot at least in my experience. I had to enable and disable dev options while plugging and unplugging device and it finally worked. No idea if that'll work for everyone though.

I reasked the question in Q and A. Please help some one.

You start over. LG bridge.

Having the same issue. I'm on Windows 10. What developer settings did you mess with to get it working, tiskewlio?

The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?

Sunaj1 said:
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Click to expand...
Click to collapse
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing

thevirgonian said:
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
Click to expand...
Click to collapse
silly question maybe, but is there a specific tutorial in getting this to work with the files provided given my situation? (commands, etc..) will this somehow bypass the the lge mobile mtp device that wont install ? I had installed the system wide adb/fastboot drivers, and already had a folder with just the minimal install of the adb but didnt have a few files in the one you provided ( lg root, busy box, etc) so not quite sure what to do with them.
Again, if possible want to flash twrp recovery to my device but can't due to * waiting for any device* and the ( device cannot start ) error
Thanks

* waiting for device* when putting phone in download mode and pushing fastboot flash twrp-2.8.7.1-h811.img.
Any help would be appreciated as I need to get the driver to work first. see attached picture.
Cha h

the issue is largly resolved as i've been able to flash the recovery and install another rom. But i'd still like to know how to get the download mode driver properly working in the event i need a computer and can't do a self contained install.

Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.

travisd4est said:
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
Click to expand...
Click to collapse
i dont know man, i did all that a million times over, but recently i was able to just flash the stock MM rom to the device using LGup. Think i'll just stick with stock rom and root for a while as all this stuff is a little finicky at times. Thanks for your help.