Database Develop

[Q] Device not found on ADB | TWRP Sideload and CWM mount problems

My friend has HTC One. He wiped all the data on SD including the ROM files and One is not booting right now. It's rooted and has Trickdroid's 4.2.2 based ROM.
We tried lots of things so far;
- Pushing files via ADB
Trying ADB, it says device not found, no matter we did we couldn't manage the pc to recognize the phone.
- Mounting SD via CWM
I have HOX, when I enter CWM I can see the option to mount the SD but on One there's no line like this.
- Activating Sideload on TWRP
We also flashed TWRP and tried to use Sideload feature but when we tried to activate it, it says something like "unable to mount .."
- Flashing the RUU
And lastly we tried to flash the RUU, we checked the CID and it says o2___001 and there's no RUU for it.
I just saw that One could be S-OFF and got Super-CID, but to do that again, I have to pull and push some files via ADB so we stuck here.
Could you plese help me on this?

Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again

NiMH_999 said:
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
Click to expand...
Click to collapse
We tried a different computer and solved the ADB problem, then I did just like you told and it's OK now.
Thank you.

You're welcome. glad it's all all OK for you

Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.

Same problem as you --> fixed
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.

If you found that adb worked from a different machine, you might check whether you had any tethering drivers installed (eg EasyTether) on the machine that was not able to see the phone via adb. I found that they interfered with adb's operation on my Macbook previously; it was maddening.

woraz said:
My friend has HTC One. He wiped all the data on SD including the ROM files and One is not booting right now. It's rooted and has Trickdroid's 4.2.2 based ROM.
We tried lots of things so far;
- Pushing files via ADB
Trying ADB, it says device not found, no matter we did we couldn't manage the pc to recognize the phone.
- Mounting SD via CWM
I have HOX, when I enter CWM I can see the option to mount the SD but on One there's no line like this.
- Activating Sideload on TWRP
We also flashed TWRP and tried to use Sideload feature but when we tried to activate it, it says something like "unable to mount .."
- Flashing the RUU
And lastly we tried to flash the RUU, we checked the CID and it says o2___001 and there's no RUU for it.
I just saw that One could be S-OFF and got Super-CID, but to do that again, I have to pull and push some files via ADB so we stuck here.
Could you plese help me on this?
Click to expand...
Click to collapse
if you have problems always use Hasoon All-In-One_Kit for HTC

Am having the same issues, have tried everything I can think off and everything google has suggested. I'm beyond stuck any and all help would be greatly appreciated

my bad exp
I don't know if that help anyone but I had the problem "device not found" when I was trying to side load with HTC AIO KIT.
I removed all my drivers for htc from the control panel and installed only the htc driver (binary100100.googlecode.[com]/files/HTCDriver3.0.0.007.exe). Then the adb started to work. (after the htc drivers install you need to restart your OS)
When I installed new ROM and reboot the device it showed me the screen with the developer's rom. I thought that I failed and flashed new rom then suddenly the new ROM after one minute started to work. So looks like that I should wait long enough for the first and may be it would also starts to work.

Was he by chance having issues charging his phone before he wiped it?
Myself and my brother both a had issues with the USB port going. Couldn't charge while phone was on. PC wouldn't pick it up so no adb. However was able to pickup fastboot and charge while in fastboot mode.
If that's the case you could try running a zip in oemRUU mode just to get an os on there.
Is he soff?
Sent from my HTC One using xda premium

makkasi said:
I don't know if that help anyone but I had the problem "device not found" when I was trying to side load with HTC AIO KIT.
I removed all my drivers for htc from the control panel and installed only the htc driver (binary100100.googlecode.[com]/files/HTCDriver3.0.0.007.exe). Then the adb started to work. (after the htc drivers install you need to restart your OS)
When I installed new ROM and reboot the device it showed me the screen with the developer's rom. I thought that I failed and flashed new rom then suddenly the new ROM after one minute started to work. So looks like that I should wait long enough for the first and may be it would also starts to work.
Click to expand...
Click to collapse
This worked for me. Thanks!!
Once I removed all the extra crap from control panel and used the latest I was able to do adb devices successfully from bootloader / recovery.

I was just having the same problem on the new LG G2 (D803). It was perplexing because the computer *bleeped* every time it attached so I knew that it saw something. Based on the tips here I went to the Device Manager and sure enough there it was... I reinstalled the drivers inside device manager and then I got an easy adb hit on the phone... hmmm :fingers-crossed:

EazyVG said:
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Click to expand...
Click to collapse
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
This worked for my Nexus 4 and TWRP installed. Running the ADB sideload commad from TWRP did not, and just trying to push or sideload from command prompt on PC (Win 8) did not. I had drivers for Nexus 4 recognition installed previously from Nexus Root Toolkit which worked when the Nexus 4 was booted into system, but did not recognize it when wiped and/or in recovery mode. Loading these drivers the Nexus 4 was recognized in recovery mode, and I was able to push the ROM and install using TWRP.
Thanks much!
:good:

timekills said:
This worked for my Nexus 4 and TWRP installed. Running the ADB sideload commad from TWRP did not, and just trying to push or sideload from command prompt on PC (Win 8) did not. I had drivers for Nexus 4 recognition installed previously from Nexus Root Toolkit which worked when the Nexus 4 was booted into system, but did not recognize it when wiped and/or in recovery mode. Loading these drivers the Nexus 4 was recognized in recovery mode, and I was able to push the ROM and install using TWRP.
Thanks much!
:good:
Click to expand...
Click to collapse
Man, I just wanted to say thank you. I've been stuck on this for hours and this did the trick!

Worked
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
the drivers mentioned here worked for me.
Device : HTC One M7
Recovery : TWRP
Thanks

Thank you so much! This universal driver worked for me! (HTC One Mini with TWRP, soft-bricked)

NiMH_999 said:
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
Click to expand...
Click to collapse
Years later, thank you sir, for helping a noob with "adb kill-server"
I was so freaked as to why TWRP wasn't sideloading but PhilZ was.

flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
ADB didn't recognize my Xperia SP in Clockworkmod. That driver worked like a charm Thank you!

This worked for me...
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
Thank you so much for this. This really helped me out.

[Q] HELP! Wiped out all data, how to install a new ROM if:

Hey guys,
First of all I'd like to apoligize for my english skills and a thread if I've posted in a wrong one category.
However, I have REALLY serious problem right now and I'll try to explain. Today I decided to reset my phone (settings - back up & reset). This didin't help me as I was expected therefore I wiped out all the data by using TWRP(yes, I'm a noob). Thought that it will erase everything but the ROM. I tried to do a reboot and the phone did the htc quietly brilliant logo but got caught at the beats audio logo screen and never advanced.
Went into recovery and tried to do a factory reset, and a whole bunch of other things (tried to reboot system, but is says that no os installed). The phone still gets stuck at the same screen. Also, I am unable to get it to be accessible on my computer again. it says that installing new device but nothing happens, so I have no way how to get into sdcard and mount a new ROM or something. Is there any way how to fix it?? How to install a new ROM when USB not working and there's no way to take off SD card.....?

Nelayme said:
How to install a new ROM when USB not working and there's no way to take off SD card.....?
Click to expand...
Click to collapse
TWRP has an option to enable adb sideload. Then you can adb push rom.zip

BenPope said:
TWRP has an option to enable adb sideload. Then you can adb push rom.zip
Click to expand...
Click to collapse
Nothing happens, actually. All I can see is " Usage: adb sideload filename.zip, Updating partition details... Starting ADB sideload feature" and that's it. Waited for 5 min and still nothing..

Nelayme said:
Nothing happens, actually. All I can see is " Usage: adb sideload filename.zip, Updating partition details... Starting ADB sideload feature" and that's it. Waited for 5 min and still nothing..
Click to expand...
Click to collapse
You go into TWRP and enable sideload mode, it will do nothing but say sideload is being started. Then copy whatever ROM you want into the same folder as fastboot and adb. Open up a new command window and type "adb sideload rom.zip", obviously name your ROM "rom.zip" and click enter ... In the command window you should see a percentage figure start to increase as it pushes it to your phone. When it's completed just flash the ROM like normal in TWRP.

AllAboutTheCore said:
You go into TWRP and enable sideload mode, it will do nothing but say sideload is being started. Then copy whatever ROM you want into the same folder as fastboot and adb. Open up a new command window and type "adb sideload rom.zip", obviously name your ROM "rom.zip" and click enter ... In the command window you should see a percentage figure start to increase as it pushes it to your phone. When it's completed just flash the ROM like normal in TWRP.
Click to expand...
Click to collapse
I tried doing that myself but never got a percentage showing me anything I freaked out at first ten I just like it do it's thing until it said it transferred
Sent from inside the T.A.R.D.I.S

joselv456 said:
I tried doing that myself but never got a percentage showing me anything I freaked out at first ten I just like it do it's thing until it said it transferred
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
Another option is to just use an OTG cable and flash a ROM from a flash drive.

AllAboutTheCore said:
You go into TWRP and enable sideload mode, it will do nothing but say sideload is being started. Then copy whatever ROM you want into the same folder as fastboot and adb. Open up a new command window and type "adb sideload rom.zip", obviously name your ROM "rom.zip" and click enter ... In the command window you should see a percentage figure start to increase as it pushes it to your phone. When it's completed just flash the ROM like normal in TWRP.
Click to expand...
Click to collapse
Just tried what you said and still nothing. There're somekinda problems with USB, I'm even unable to connect my phone.. When I typed "adb sideload rom.zip" it was saying "error: device not found" only. Will try to reinstall htc sync drivers, but I think it won't help.. Any other ideas how to back my htc to life (didin't try with OTG cable yet)?

Nelayme said:
Just tried what you said and still nothing. There're somekinda problems with USB, I'm even unable to connect my phone.. When I typed "adb sideload rom.zip" it was saying "error: device not found" only. Will try to reinstall htc sync drivers, but I think it won't help.. Any other ideas how to back my htc to life (didin't try with OTG cable yet)?
Click to expand...
Click to collapse
OTG cable should work and is the easiest way to do it but if not you might want to check this thread .. http://forum.xda-developers.com/showthread.php?t=2363516

See this post, might help
http://forum.xda-developers.com/showpost.php?p=44730345&postcount=13

AllAboutTheCore said:
OTG cable should work and is the easiest way to do it but if not you might want to check this thread .. http://forum.xda-developers.com/showthread.php?t=2363516
Click to expand...
Click to collapse
Hey mate,
I just got OTG cable, moved a new Rom into USB stick and tried to mount on TWRP. All I got was "E: Unable to mount '/usb-otg'. Maybe I've missed couple of steps before?
FIXED: All I had to do is to format an USB stick in FAT32. Everything went well and now I can use my phone once again. Thanks a lot for your help, hope it will help to others as well.
Cheers!

Help! Infinite bootloop, can't enter Recovery, and Fastboot usb doesnt work

Super noob here. I was trying to update my android revolution hd rom and somehow I screwed everything.
Do I have a chance to fix my phone or should I purchase a new one?
My unit is a HTC One m7 (sprint).
I understand that in order to fix this I need to install a new recovery (I have a CWM old version). The phone reboots in regular mode but as ROM is not working it reboots to recovery, but this doesn't work either I just see a 0,5s splash screen and the loop goes on.
I have read the "disaster recovery" thread but they assume Fastboot USB works. My problem is I dont even know how to connect my phone to my computer in order to work from there.
My bootloader is still unlocked (fortunately).
I have Hboot 1.44 should I update it?
A step-by-step dumb proof will be appreciated!

First download a toolkit for the HTC one m7. You can find it in the android development section. With that you can install a new recovery. I recommend twrp. After that push a ROM via adb to the device and flash that Rom. There are hundreds of sprint ROMs and even more threads "how to adb push"
http://forum.xda-developers.com/showthread.php?t=2265618
[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013

Philipp_94 said:
First download a toolkit for the HTC one m7. You can find it in the android development section. With that you can install a new recovery. I recommend twrp. After that push a ROM via adb to the device and flash that Rom. There are hundreds of sprint ROMs and even more threads "how to adb push"
http://forum.xda-developers.com/showthread.php?t=2265618
[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013
Click to expand...
Click to collapse
Thanks, downloaded this tool seems great, but my phone is not getting recognized by the system. Im using Windows 8.1
http://forum.xda-developers.com/showthread.php?t=2727913
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My drivers are installed, I have "HTC Sync Manager" installed. This is desperating.

Blocked ONE said:
Thanks, downloaded this tool seems great, but my phone is not getting recognized by the system. Im using Windows 8.1
http://forum.xda-developers.com/showthread.php?t=2727913
My drivers are installed, I have "HTC Sync Manager" installed. This is desperating.
Click to expand...
Click to collapse
First off if your running CWM and tried to install ARHD then your gonna have issues as ARHD is only compatible with TWRP recovery 2.6.3.3 or 2.7.1.1
If Windows 8 has stopped recognizing your phone and you can't boot to a Rom unfortunately there's little chance of you getting it working again.
So you have 2 good options. Get/make an otg cable and use it to install a Rom compatible with CWM.
Or create a Linux boot disk to use adb/fastboot. Linux doesn't need drivers for your phone so no detection problems then you can flash recovery or push a Rom whatever you want.
---------- Post added at 03:50 PM ---------- Previous post was at 03:27 PM ----------
Blocked ONE said:
I have read the "disaster recovery" thread but they assume Fastboot USB works. My problem is I dont even know how to connect my phone to my computer in order to work from there.
Click to expand...
Click to collapse
To use Fastboot :- boot the phone to the boot loader and select Fastboot from the menu. Then connect you phone via usb cable and Fastboot should change to fastbootusb.
Open the folder that contains adb and fast boot on your pc then hold Shift and right click on the empty white background space, from the menu that appears select "open command window here"
In the command window type
fastboot devices
If you get an output of your phone's serial no. Fastboot is working.

Danny201281 said:
First off if your running CWM and tried to install ARHD then your gonna have issues as ARHD is only compatible with TWRP recovery 2.6.3.3 or 2.7.1.1
If Windows 8 has stopped recognizing your phone and you can't boot to a Rom unfortunately there's little chance of you getting it working again.
So you have 2 good options. Get/make an otg cable and use it to install a Rom compatible with CWM.
Or create a Linux boot disk to use adb/fastboot. Linux doesn't need drivers for your phone so no detection problems then you can flash recovery or push a Rom whatever you want
To use Fastboot :- boot the phone to the boot loader and select Fastboot from the menu. Then connect you phone via usb cable and Fastboot should change to fastbootusb.
Open the folder that contains adb and fast boot on your pc then hold Shift and right click on the empty white background space, from the menu that appears select "open command window here"
In the command window type
fastboot devices
If you get an output of your phone's serial no. Fastboot is working.
Click to expand...
Click to collapse
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!

Blocked ONE said:
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Click to expand...
Click to collapse
Your not even close to being bricked
On Linux you will still need to install adb/fastboot but no drivers for your phone needed. As long as adb is working your on a winner
Also you will need to add sudo at the beginning of each command
E.g "adb devices" becomes " sudo adb devices" or "fastboot flash recovery" becomes " sudo fastboot flash recovery"

Blocked ONE said:
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Click to expand...
Click to collapse
Danny201281 said:
Your not even close to being bricked
On Linux you will still need to install adb/fastboot but no drivers for your phone needed. As long as adb is working your on a winner
Also you will need to add sudo at the beginning of each command
E.g "adb devices" becomes " sudo adb devices" or "fastboot flash recovery" becomes " sudo fastboot flash recovery"
Click to expand...
Click to collapse
also Sprint has a different partition structure you CANNOT use files for a GSM phone on yours ...please go to the sprint forums for the files and help you need

Sirs, ubuntu doesnt recognize it either!
While on the bootloop it says system can't mount the Android unit. This means the USB is working.
But on the bootloader/fastboot it doesn't even pop up this message, its like nothing is plugged. WTF I think it is bricked, can't connect anywhere. I feel stupid just trashed my phone for a non important ROM update.

Blocked ONE said:
Sirs, ubuntu doesnt recognize it either!
While on the bootloop it says system can't mount the Android unit. This means the USB is working.
But on the bootloader/fastboot it doesn't even pop up this message, its like nothing is plugged. WTF I think it is bricked, can't connect anywhere. I feel stupid just trashed my phone for a non important ROM update.
Click to expand...
Click to collapse
you need to calm down
first turn the phone off
hold power plus volume down
when the phone goes off keep holding volume down and let go of power
now your in the bootloader
use the volume key to select bootloader then power off
now wait
now hook the phone to the usb and hit power plus volume down
let go of both when you see the bootloader again
now your in fastboot USB
now you can flash the correct recovery to your phone.
next you need this >> http://forum.xda-developers.com/showthread.php?t=2658910

clsA said:
you need to calm down
first turn the phone off
hold power plus volume down
when the phone goes off keep holding volume down and let go of power
now your in the bootloader
use the volume key to select bootloader then power off
now wait
now hook the phone to the usb and hit power plus volume down
let go of both when you see the bootloader again
now your in fastboot USB
now you can flash the correct recovery to your phone.
next you need this >> http://forum.xda-developers.com/showthread.php?t=2658910
Click to expand...
Click to collapse
I followed your instructions but the device doesn't show up in Ubuntu.
But if I try to boot in regular mode, it shows! "Android Phone". The problem is I can't access this, since it just appears for some seconds because this is during the bootloop. Anyway during these seconds, if I click on "Android Phone" it says it cant access it... This is confusing.
I tried both USB 3.0 and 2.0 since I have read 3.0 has problems sometimes.
Should I install any kind of drivers on Ubuntu?

Blocked ONE said:
I followed your instructions but the device doesn't show up in Ubuntu.
But if I try to boot in regular mode, it shows! "Android Phone". The problem is I can't access this, since it just appears for some seconds because this is during the bootloop. Anyway during these seconds, if I click on "Android Phone" it says it cant access it... This is confusing.
I tried both USB 3.0 and 2.0 since I have read 3.0 has problems sometimes.
Should I install any kind of drivers on Ubuntu?
Click to expand...
Click to collapse
From @nkk71 Superguide
5) Q: How do I create a Linux Live USB
Windows users: http://click.xda-developers.com/api...ww.ubuntu.com/download/deskt...ick-on-windows
Mac users: http://www.ubuntu.com/download/deskt...ick-on-mac-osx
Ubuntu 12.04 LTS 32bit ISO from here: http://www.ubuntu.com/download/desktop
Once the Ubuntu Live USB is ready, shutdown your computer and restart from the USB
No need to install, just use the "Try Ubuntu" option
open a terminal
and install adb & fastboot using (copy/paste 1 line at a time into terminal):
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
you can then check version, by typing "adb version"
and check connection using "adb devices" in custom recovery or booted phone
and "sudo fastboot devices" in bootloader
you can also check @tobesedated guide for more info: [Guide]Suggestion For S-off On 1.55 HBoot Using Ubuntu---Step by step with pictures
Click to expand...
Click to collapse

OK i think im making some progress!!
I am running this ubuntu from USB, installed adb and fastboot, and I think its connected now. At console I type "fastboot devices" and it says: "HT359W90.... fastboot"
Then I downloaded the TWRP 2.7.1.1 and flashed it. Finally I rebooted the phone and now it enters recovery!!!!!! :good: Im now sure the one is not dead!! Thank you so much guys.
Now what? Should I make a factory reset or just go ahead and flash the ROM I intended to get? Don't want to screw it again...
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory". And from phone, the ADB Sideload feature doesnt work either, it gest stuck at "starting ADB sideload feature" even after 15 minutes...

Blocked ONE said:
OK i think im making some progress!!
I am running this ubuntu from USB, installed adb and fastboot, and I think its connected now. At console I type "fastboot devices" and it says: "HT359W90.... fastboot"
Then I downloaded the TWRP 2.7.1.1 and flashed it. Finally I rebooted the phone and now it enters recovery!!!!!! :good: Im now sure the one is not dead!! Thank you so much guys.
Now what? Should I make a factory reset or just go ahead and flash the ROM I intended to get? Don't want to screw it again...
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory". And from phone, the ADB Sideload feature doesnt work either, it gest stuck at "starting ADB sideload feature" even after 15 minutes...
Click to expand...
Click to collapse
Ok so you have usb Linux working that's great.
What method did you use to install adb/fastboot? Hopefully it was the Webupd8 repository install as this makes life easy.

Danny201281 said:
Ok so you have usb Linux working that's great.
What method did you use to install adb/fastboot? Hopefully it was the Webupd8 repository install as this makes life easy.
Click to expand...
Click to collapse
Yes I followed the method quoted by clsA

Make sure your Rom is compatible with Sprint then to push it to the phone do this.
Boot your Linux usb stick and select the try ubuntu option. Wait for the desktop to load. Open the Home folder. In the top left you should see other drives connected to your pc. Go into your hdd and copy the Rom to the Home folder of the Linux usb and rename it rom.zip.
Now reboot computer, and Wait for it to return to the try/install ubuntu screen. And press
Control + alt + F1 (this will take you to main Linux terminal)
Boot your phone into recovery and connect with usb and type
adb devices (to check phone is detected if phone is not detected see below)
Then
adb push rom.zip /sdcard
If phone is not detected type the following 3 commands waiting for each to complete there out put. Be patient it may seem stuck at some points and you may see some errors but just wait for the terminal to return to normal after each command I.E ready to accept another command. Once all 3 commands have completed try adb devices again.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot

Danny201281 said:
Make sure your Rom is compatible with Sprint then to push it to the phone do this.
Boot your Linux usb stick and select the try ubuntu option. Wait for the desktop to load. Open the Home folder. In the top left you should see other drives connected to your pc. Go into your hdd and copy the Rom to the Home folder of the Linux usb and rename it rom.zip.
Now reboot computer, and Wait for it to return to the try/install ubuntu screen. And press
Control + alt + F1 (this will take you to main Linux terminal)
Boot your phone into recovery and connect with usb and type
adb devices (to check phone is detected if phone is not detected see below)
Then
adb push rom.zip /sdcard
If phone is not detected type the following 3 commands waiting for each to complete there out put. Be patient it may seem stuck at some points and you may see some errors but just wait for the terminal to return to normal after each command I.E ready to accept another command. Once all 3 commands have completed try adb devices again.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
Ubuntu crashes whenever I press Ctrl+Alt+F1, tried twice and had to reboot.
I was using Ctrl+Alt+T for opening a console. Already did all those 3 commands but not working. This seems challenging! I have read something about 32-bits instructions needed for this? Im running under a 64bit computer and 64 bit linux distribution.
By the way a friend has got an OTG cable, would this work to get a ROM inside the SD-Card?

Blocked ONE said:
Ubuntu crashes whenever I press Ctrl+Alt+F1, tried twice and had to reboot.
I was using Ctrl+Alt+T for opening a console. Already did all those 3 commands but not working. This seems challenging! I have read something about 32-bits instructions needed for this? Im running under a 64bit computer and 64 bit linux distribution.
By the way a friend has got an OTG cable, would this work to get a ROM inside the SD-Card?
Click to expand...
Click to collapse
You should be using 32bit Linux it will run ok on a 64bit machine. But with 64bit Linux you will need to install 32bit libs I think.
Yes an otg cable can be used to copy the Rom to the phone
It's weird that you had Fastboot working but adb won't though. Try using adb without the sudo prefix. It should be working if Fastboot is. But remember you must be in recovery to use adb. Not the bootloader.
Fastboot = bootloader
Adb = recovery

Blocked ONE said:
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory".
Click to expand...
Click to collapse
Ok slight brain fart on my part lol. The error you got implies that adb is working but your Rom is not in the right place.
You can put the Rom in the home folder and use the adb push command from the terminal as it is when opened.
Or if the Rom is for instance in the downloads folder you must first use
cd Downloads (to take the terminal to the downloads folder)
Then adb push

More problems lol
Apparently I can't flash any ROM because it says I cant mount cache, data nor internal storage.
Im on TWRP 2.7.1.1

Blocked ONE said:
More problems lol
Apparently I can't flash any ROM because it says I cant mount cache, data nor internal storage.
Im on TWRP 2.7.1.1
Click to expand...
Click to collapse
So you've got the Rom on the phone but when go To recovery you can't see the rom because of this error?
It's normal to see these type of errors after using fastboot erase cache. But not normally with internal storage.
If you can see the Rom just flash it it should work.

[Q] BRICKED Lg Flex D950

I have accidently bricked my device, I rooted the phone and installed the Freedom Flex TWRP. I then thought to take the OTA for KitKat which ended up bricking my Flex. Whenever the phone turns on it boots past the LG logo and straight into TWRP. I tried sideloading the DFUSE stock att rom but I get an error saying "cannot read sideload". I have no other options, any help is appreciated.
Solved thanks to jacktackle!
His steps:
from the TWRP terminal command type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter (it should copy some file. if nothing happens then twrp backup is only option.) if there is some activity then type the next command.
where you have to change only the last word
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot

Good news. U can get to recovery you are not bricked. Even better news it is a easy fix. I was in the same boat.
To fix it:
Download the stock JB zip room. It is large, about 1.7 Gig. Make sure it downloads correctly.
Copy the file in your adb directory.
Boot into recovery and connect your phone to the computer.
Adb devices should give you the device info. Afterwords enter:
adb push <name of the zip> /sdcard/
It will take about 10 minutes for it to complete. In the meantime you will see no activity. Wait.
After it completes, do a factory reset and install the zip as normal.
Done.
Reboot, do a factory reset from the settings, accept the ota and root with stump root.

johny101010 said:
Good news. U can get to recovery you are not bricked. Even better news it is a easy fix. I was in the same boat.
To fix it:
Download the stock JB zip room. It is large, about 1.7 Gig. Make sure it downloads correctly.
Copy the file in your adb directory.
Boot into recovery and connect your phone to the computer.
Adb devices should give you the device info. Afterwords enter:
adb push <name of the zip> /sdcard/
It will take about 10 minutes for it to complete. In the meantime you will see no activity. Wait.
After it completes, do a factory reset and install the zip as normal.
Done.
Reboot, do a factory reset from the settings, accept the ota and root with stump root.
Click to expand...
Click to collapse
Its not showing up, re installed drivers about 3 or 4 times now, im going to try to update adb drivers.
Im running Windows 7 Ultimate x64bit
Edit: Didn't work doesn't even show up in device manager.
Going to try it on my WIndows 8 laptop

Mine was on Win8 laptop but if all fails just connect it to a Linux box and it should work fine.

johny101010 said:
Mine was on Win8 laptop but if all fails just connect it to a Linux box and it should work fine.
Click to expand...
Click to collapse
Same problems, tried to sideload but i get "cannot read sideload" and adb push shows device not found. I don't have a linux box, but is there any other to fix this? I hear the pop up sound whenever I plug the phone into my WIn8 Laptop but nothing comes Up (i.e. USB/adb/etc.)

What happenes if you enter <adb devices> ?

52me52 said:
Same problems, tried to sideload but i get "cannot read sideload" and adb push shows device not found. I don't have a linux box, but is there any other to fix this? I hear the pop up sound whenever I plug the phone into my WIn8 Laptop but nothing comes Up (i.e. USB/adb/etc.)
Click to expand...
Click to collapse
This LG fLEX is full of problems thanks for XDA Developers site for retriving so many devices and next is you in the list brother.
Ok it's very easy.
do you have a backup of twrp? saved somewhere? if not ask any one on the forum with d950 varient who have a backup can help you to upload it.
after you get a twrp backup, come back to me. it's a piece of cake then.
in the mean time, try this from TWRP recovery
from the TWRP terminal command type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter (it should copy some file. if nothing happens then twrp backup is only option.) if there is some activity then type the next command.
where you have to change only the last word
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot

jacktackle said:
This LG fLEX is full of problems thanks for XDA Developers site for retriving so many devices and next is you in the list brother.
Ok it's very easy.
do you have a backup of twrp? saved somewhere? if not ask any one on the forum with d950 varient who have a backup can help you to upload it.
after you get a twrp backup, come back to me. it's a piece of cake then.
in the mean time, try this from TWRP recovery
from the TWRP terminal command type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter (it should copy some file. if nothing happens then twrp backup is only option.) if there is some activity then type the next command.
where you have to change only the last word
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot
Click to expand...
Click to collapse
edit: Tried the terminal emulator thing and it worked! Thank you SO much!

52me52 said:
edit: Tried the terminal emulator thing and it worked! Thank you SO much!
Click to expand...
Click to collapse
wellcome anytime. glad that we can help the needies

same boat as op but cwm
Hi I have tripped and stumbled down the exact same path as the op, but with cwm. Will this fix work for me?
I could really use someone's help with this, there is no terminal emulator in cm and my computer reads my D950 in device manager as a D959.. I don't know what to do to fix it..

System partition deleted, need help.

Evening all. I've done a very dumb thing. While wiping my device for a clean install in TWRP, I foolishly checked the "system" partition and wiped everything out.
Currently I have ADB set up correctly on my Mac, TWRP running on my phone but I'm stumped because I haven't used ADB in quite some time.
Can anyone help me with instructions (or a link to them) on how to restore my phone to it's former glory?

I should also tell you that I've tried following the instructions found with the Google Factory Images, but I'm unable to flash anything. I get "permission denied" messages. I'm thinking this is because I have no ROM and therefore no settings to allow me access to developer settings.
The bootloader is unlocked... but I'm stuck.

If you have TWRP, enter it. Connect your N6 to your Mac. Copy a custom ROM or one of the stock ROM flashable zips to internal storage, then install it using TWRP.
ADB isn't necessary.

What I'm doing and seeing...
I start the phone in the bootloader and plug it in. The phone sees that it's plugged in.
If I "adb devices" now, I get no results.
If I start TWRP and enter "adb devices", I see a serial and the word "recovery"
I can reboot the bootloader via adb, but that's it.
If I enter any action after that, like: "fastboot flashing unlock", or "flash-all", it returns < waiting for any device >, or permission denied.

Strephon Alkhalikoi said:
If you have TWRP, enter it. Connect your N6 to your Mac.
Click to expand...
Click to collapse
Thought about that earlier, of course. My phone isn't connecting to my Mac. I'm not seeing it as a drive in Finder.

nathanotis said:
My phone isn't connecting to my Mac.
Click to expand...
Click to collapse
I uninstalled and reinstalled android file manager. I'm pulling down a new rom, now. Fingers crossed.

That was easy...

nathanotis said:
What I'm doing and seeing...
I start the phone in the bootloader and plug it in. The phone sees that it's plugged in.
If I "adb devices" now, I get no results.
If I start TWRP and enter "adb devices", I see a serial and the word "recovery"
I can reboot the bootloader via adb, but that's it.
If I enter any action after that, like: "fastboot flashing unlock", or "flash-all", it returns < waiting for any device >, or permission denied.
Click to expand...
Click to collapse
In twrp Fastboot commands not work. And in bootloader adb commands not wotk

@nathanotis: It's for situations like this that I always store a copy of the ROM I use in internal storage. Perhaps you should do the same.

Strephon Alkhalikoi said:
Perhaps you should do the same.
Click to expand...
Click to collapse
Solid advice. Thank you.

If that ever happens again, you can always use NRT. I did that one time and used WUG's to flash a factory image and start over