Related
I recently purchased an LG Phoenix by At&t, the problem I have is that I cannot leave ClockworkMod Recovery v5.0.2.0
I rooted it, restarted in recovery. and everything worked fine. I then upgraded my firmware, not sure what version though.. I backed up my phone before I upgraded into the new firmware. I then backedup my phone because it rebooted into recovery. Now everytime it boots it goes straight to Clockwork and I cant get out of it. I restored to my previous restore and it still doesn't work. What could I do? Should I install cwr 3? I read that cwr 5 has bugs and is known to brick phones..
Edit: Also the phone without the sd card still boots into clockworkmod menu
I have a ROM(Phoenix ULTIMATE) I'd like to flash but I'm not sure if I should right now considering I'm stuck at this menu.
Info- in my restores It says;
2011-10-04.21.37.48/
2011-10-04.21.56.13/
I'v tried both.
Another edit with potentially important info getting an error stating;
E: bad boot message "recovery"
Sorry If this is a n00b post.. I'm in sort of a rush because I'm moving in a few hours!
Edit; tried flashing the phoenix, didnt work.
installation was aborted
said i needed to switch to Edify scripting, and amend scripting is no longer supported.
What could I flash too to fix this, please help. I don't care if I lose data. Just need my phone back soon.
I have android SDK.
I was reading up on http://developer.android.com/guide/developing/tools/adb.html and http://forum.xda-developers.com/showthread.php?t=517874 here
Would I be-able to push somesort of boot file or firmware to my phone? Or something in that manner?
THIS:
fastboot erase boot
fastboot erase recovery
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot reboot
Seems to be perfect for what I should try, where could I get the stock imgs for my phone? (p505)
I moved this here temporarily for you to be assisted...after that it will be moved beck to the right forum
Good luck!!
M_T_M said:
I moved this here temporarily for you to be assisted...after that it will be moved beck to the right forum
Good luck!!
Click to expand...
Click to collapse
thanks
Really hope I can get this fixed soon.
Xery said:
I recently purchased an LG Phoenix by At&t, the problem I have is that I cannot leave ClockworkMod Recovery v5.0.2.0
I rooted it, restarted in recovery. and everything worked fine. I then upgraded my firmware, not sure what version though.. I backed up my phone before I upgraded into the new firmware. I then backedup my phone because it rebooted into recovery. Now everytime it boots it goes straight to Clockwork and I cant get out of it. I restored to my previous restore and it still doesn't work. What could I do? Should I install cwr 3? I read that cwr 5 has bugs and is known to brick phones..
Edit: Also the phone without the sd card still boots into clockworkmod menu
I have a ROM(Phoenix ULTIMATE) I'd like to flash but I'm not sure if I should right now considering I'm stuck at this menu.
Info- in my restores It says;
2011-10-04.21.37.48/
2011-10-04.21.56.13/
I'v tried both.
Another edit with potentially important info getting an error stating;
E: bad boot message "recovery"
Sorry If this is a n00b post.. I'm in sort of a rush because I'm moving in a few hours!
Click to expand...
Click to collapse
Are you on Ecliar , Froyo or Gingerbread ? Sorry , I don't know much but I would like to help
Forever living in my Galaxy Ace using XDA App
EmoBoiix3 said:
Are you on Ecliar , Froyo or Gingerbread ? Sorry , I don't know much but I would like to help
Forever living in my Galaxy Ace using XDA App
Click to expand...
Click to collapse
I didn't change anything, everything is stock I got it yesterday. Rooted it today and it's stuck in recovery. So I guess whatever stock is..
Xery said:
I didn't change anything, everything is stock I got it yesterday. Rooted it today and it's stuck in recovery. So I guess whatever stock is..
Click to expand...
Click to collapse
Try adb .
(If you know what it is)
Type these in:
adb shell
su
reboot bootloader
See if it works
Forever living in my Galaxy Ace using XDA App
I don't know what adb is. :c
Could you explain a bit more about it?
Xery said:
I don't know what adb is. :c
Could you explain a bit more about it?
Click to expand...
Click to collapse
Okay then .
Download and install the Android SDK Tools first
Forever living in my Galaxy Ace using XDA App
EmoBoiix3 said:
Okay then .
Download and install the Android SDK Tools first
Forever living in my Galaxy Ace using XDA App
Click to expand...
Click to collapse
OH Android SDK I have that, just updating.. another 30 minutes..
While we wait, could you explain to me what I'd do with it, and just some tips or things I could do?
Xery said:
OH Android SDK I have that, just updating.. another 30 minutes..
While we wait, could you explain to me what I'd do with it, and just some tips or things I could do?
Click to expand...
Click to collapse
If you have platform-tools , everything will be done in a flash
Forever living in my Galaxy Ace using XDA App
EmoBoiix3 said:
If you have platform-tools , everything will be done in a flash
Forever living in my Galaxy Ace using XDA App
Click to expand...
Click to collapse
"Installed Android SDK Platform-tools, revision 7"
Still installing a bunch of other things though..
"Downloading SDK Platform Android 3.2, API 13, revision 1"
Probably won't be done till tomorrow, horrible internet.
Xery said:
"Installed Android SDK Platform-tools, revision 7"
Still installing a bunch of other things though..
"Downloading SDK Platform Android 3.2, API 13, revision 1"
Probably won't be done till tomorrow, horrible internet.
Click to expand...
Click to collapse
All you need now is platform-tools . The rest can be cancelled .
Use cmd (best if used with administrative rights) to navigate to the Android SDK folder , then to platform-tools .
Once you get there , connect your phone through USB then don't touch it .
In cmd , type:
abd shell
su
reboot bootloader
Forever living in my Galaxy Ace using XDA App
EmoBoiix3 said:
All you need now is platform-tools . The rest can be cancelled .
Use cmd (best if used with administrative rights) to navigate to the Android SDK folder , then to platform-tools .
Once you get there , connect your phone through USB then don't touch it .
In cmd , type:
abd shell
su
reboot bootloader
Forever living in my Galaxy Ace using XDA App
Click to expand...
Click to collapse
How would I use the cmd to navigate to the SDK folder?
I see the cmd, I also see a window called Android SDK and AVD manager, What now?
Xery said:
How would I use the cmd to navigate to the SDK folder?
I see the cmd, I also see a window called Android SDK and AVD manager, What now?
Click to expand...
Click to collapse
Do this
Hold start button and R(on desktop)
Run will open
Type cmd in the box and press enter
A black window will open
CD to sdk dir
E.g.
If u installed sdk in C:\sdk
Then do this
cd C:\sdk\platform-tools
Then this
adb shell
reboot bootloader
cdesai said:
Do this
Hold start button and R(on desktop)
Run will open
Type cmd in the box and press enter
A black window will open
CD to sdk dir
E.g.
If u installed sdk in C:\sdk
Then do this
cd C:\sdk\tools
Then this
adb shell
reboot bootloader
Click to expand...
Click to collapse
Follow his instructions .
Forever living in my Galaxy Ace using XDA App
cdesai said:
Do this
Hold start button and R(on desktop)
Run will open
Type cmd in the box and press enter
A black window will open
CD to sdk dir
E.g.
If u installed sdk in C:\sdk
Then do this
cd C:\sdk\tools
Then this
adb shell
reboot bootloader
Click to expand...
Click to collapse
I opened the cmd, I'm not really suer where I installed SDK but I'm pretty sure it was c:\program files\android\android-sdk\tools
That seemed to work, whenever i type adb shell it says abd is not recognized as an internal or external command, program or batch.
I need more detail because I'm a noob. :/
cdesai said:
Do this
Hold start button and R(on desktop)
Run will open
Type cmd in the box and press enter
A black window will open
CD to sdk dir
E.g.
If u installed sdk in C:\sdk
Then do this
cd C:\sdk\tools
Then this
adb shell
reboot bootloader
Click to expand...
Click to collapse
I opened the cmd, I'm not really suer where I installed SDK but I'm pretty sure it was c:\program files\android\android-sdk\tools
That seemed to work, whenever i type adb shell it says abd is not recognized as an internal or external command, program or batch.
I need more detail because I'm a noob. :/
EDIT: GOTIT! got the dir, i typed adb and it says device not found should i connect my phone correct?
Edit: okay,i did that, it just rebooted my phone and it went back into the CWR.. :c wut now?
Are you able to try and boot into bootloader? Try that. Also, try and flash a new ROM in recovery, test to see if it may be the ROM. Don't be afraid to backup again, you can always access the backups based on date.
-How cruel is the golden rule, when the lives we live are all golden plated-
What's bootloader?
I tried to flash my backups before the firmware update and it didn't work, I also can't find any wp505 roms.. I found a few but they wont help in my situation. Do you know any? My rom is stock as I only rooted and got stuck in cwr.
Thanks!
EDIT: I did do that adb shell, reboot bootloader, didnt work.
Xery said:
What's bootloader?
I tried to flash my backups before the firmware update and it didn't work, I also can't find any wp505 roms.. I found a few but they wont help in my situation. Do you know any? My rom is stock as I only rooted and got stuck in cwr.
Thanks!
Click to expand...
Click to collapse
First off, not to lecture you...but you definitely should look into these kind of things before flashing a ROM.
I haven't looked at the ROMs so I'm not sure. But whatever fancies you, it's just to troubleshoot the problem. The problem itself may actually be the recovery. Do you know how to do logcats in ADB? Try and do a logcat and boot up your device while connected to ADB.
So go "adb logcat". This should show you exactly what your device is doing. When it runs and goes straight to recovery paste all that information into a .txt document and upload it onto xda so others can take a look.
I'll try and help more tomorrow but I have to get some rest. Good luck on getting this fixed.
-How cruel is the golden rule, when the lives we live are all golden plated-
I have Imilika's AOSP ICS ROM V6,
I changed the buid.prop
ro.sf.lcd_density=213
for tablet mode. after I reboot, my GNote is not booting. I cannot go to recovery mode or download mode.
Please help. I don't know what to do
Got it
OK, I was really sad about what happens to my phone, but finally I managed to fix it .
As I told you, my phone was not booting to recovery or download modes (key combinations not worked). finally I try to connect to PC via USB and luckily my PC could detect my phone . So i realized that the problem is the display not coming but phone is halfway booted.
So, I tried to change my build.prop via adb but failed due to cannot grant root permission (becoz display is off).
Finally I issue a adb commad to reboot in recovery mode.
"adb reboot recovery"
yeah, that command directly take me to the CWM recovery. then I flash AOSP v6 again.
Now, my phone is working again.
P.S. I just note this down for others if they get same problem future !
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
If you don't know what ADB is, you probably shouldn't be flashing so regularly. Anyway, ADB stands for "Android Debug Bridge" and it is a protocol for device control, development, and debugging.
Sent from my GT-N7000 using Tapatalk
priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
adb is a connection type. we can run shell commands (in the phone), file transfer via adb by using our PC. for that we should have to enable usb debug mode in our mobile.
Actually you might used adb, when you root your phone in the first place . If you have CF-Root zip file, just extract it. you will see a folder called "files", in there you can see adb.exe .
If you need test run,
connect phone via USB(make sure you've enabled USB debug), open command prompt, navigate to that "files" directory.
run "adb shell ls" (to run "ls" command in phone)
run "adb push <anyfile in the PC> /system/sdcard/" (copy files from PC to sdcard)
like that
OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..
priyanv said:
OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..
Click to expand...
Click to collapse
Its functionality is not only to copy files from pc to mobile and vice versa.You can use it to get logs due to bad flashing,zip align apps,reboot into recovery,DL mode,normal reboot etc...
well while rooting my phone, installing the recovery and custom rom.. i made a slight (big) mistake towards the ending of root kit process by hasoon. When we are about to flash the custom rom, we're supposed to wipe everything so there wouldn't be any problems later on. We all know a fresh install always gives the best results. When i was wiping everything, i forgot to put Android Revolution HD on my sd so now i have recovery but i can't install a stock rom, custom rom, and i can't restore my phone. please someone help me.. i unfortunately have to go to work in 20 mins but when i get out of work i would greatly appreciate it if i had a few answers that can help me out with my situation. I don't care if its a hard process. this isn't my first phone i root so im not that noobie (at least i don't think so) so all im asking is to be pointed in the right direction and i would greatly appreciate that. Please and thanks for the help everyone. Hope we're all enjoying this amazing phone
Use the all-in-one toolkit in the dev forum to sideload the ROM from your PC. Rename the ROM something simple like arhd.zip on your PC to make it easier.
This helped me with a similar problem.
Sent from my HTC One using xda premium
thanks for getting me on the right track.. i honestly feel really close to having a phone again but now cwm is messing me up now. whenever i try to sideload.. i keep getting "failed to open driver control: No such file or directory" then it says "restarting adbd..." and then it just repeats with the no driver control. did this happen to u? :-/
Josh112191 said:
thanks for getting me on the right track.. i honestly feel really close to having a phone again but now cwm is messing me up now. whenever i try to sideload.. i keep getting "failed to open driver control: No such file or directory" then it says "restarting adbd..." and then it just repeats with the no driver control. did this happen to u? :-/
Click to expand...
Click to collapse
I have exactly the same problem. ADB sideload isn't working for me as the device isn't showing up in adb when booted into recovery... I've been doing this for years... I don't know how I could have done something so stupid :'(
EDIT:
I managed to fix this by installing CWM touch recovery and using LINUX to sideload the ROM .zip for installation. Good look sorting it out!
No didn't get anything like that. Maybe if you can get a USB OTG cable and try load the ROM that way through CWM from a USB or micro sd adapter?
I'm not sure if this would work as I haven't tried it - just a suggestion to try.
Sent from my HTC One using xda premium
Sideload from CWM Recovery
Just went through the whole boot loop due to Aroma freezes at the beginning of the installation, but CWM Recovery is still accessible so I went the ADB Sideload method and push the file to be installed because I didn't have any backup on the internal memory.
Just a couple of guides from the guys at XDA that got me back:
make sure you have the most up to date ADB Tools
From your phone go to Recovery>install zip from sideload
From CMD prompt, check that adb can see your device by 'adb devices' command, it should show your device number with sideload next to it.
If it doesn't see it, try 'adb kill-server' and then 'adb start-server'
Then 'adb sideload custom.zip' (custom= name of ROM zip file)
You should see the percentage completion then it will start the installation on your phone.
I am also newbie at this, was panicking and looked around here having this bricked phone next to me for 24hrs, but I asked around and they got me back in.
Good luck.
boot to recovery and push rom to phone....
'adb push /path/to/ROM/on/your/computer /path/on/device' (without quotes)
xdracco said:
boot to recovery and push rom to phone....
'adb push /path/to/ROM/on/your/computer /path/on/device' (without quotes)
Click to expand...
Click to collapse
I'd be interested to see an example of the command for future reference??
For example, the ROM is saved in C:\fastboot
Thanks.
xdracco said:
boot to recovery and push rom to phone....
'adb push /path/to/ROM/on/your/computer /path/on/device' (without quotes)
Click to expand...
Click to collapse
This is what I was going to suggest.
Sent from my HTC One using xda app-developers app
redbull123 said:
I'd be interested to see an example of the command for future reference??
For example, the ROM is saved in C:\fastboot
Thanks.
Click to expand...
Click to collapse
Code:
adb push C:\fastboot\My_Rom.zip /sdcard/Download/
Try to have no spaces in the file name. linux based systems hate that.
Then when you boot into recovery, head over to:
install zip from sdcard -> choose zip from sdcard -> Download/
You'll find your ROM there.
HTH
What model do u have?
Sent from my HTC One using xda app-developers app
Hi,
I'm currently trying to use adb to push some data into my phone but i always get "error: closed". I'm using windows 7 x64 and im running it from cmd.
Almost everything i tried using adb (push, shell, remount) returns this. I've searched over the forums and tried "adb devices" as well to see if my phone is connected, but what is different from the others is i am getting
List of devices attached
XXXXXX host
instead of what most other people got
List of devices attached
XXXXXX device
Is this a problem? What am i missing? Thanks a lot for ur time in reading this
Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices
Guich said:
Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices
Click to expand...
Click to collapse
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip
Did you update the SDK Manager??? Try updating that, my ADB problem were gone after i updated them.....
xlxcrossing said:
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip
Click to expand...
Click to collapse
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?
jflora1 said:
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?
Click to expand...
Click to collapse
Try to download this, un-zip and try the tips with this
Guich said:
Try to download this, un-zip and try the tips with this
Click to expand...
Click to collapse
I downloaded the zip but haven't had any success, still getting an error:closed message
ozo012 said:
I downloaded the zip but haven't had any success, still getting an error:closed message
Click to expand...
Click to collapse
which recovery are you on? (name and version number please)
nkk71 said:
which recovery are you on? (name and version number please)
Click to expand...
Click to collapse
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
isnt "error closed" something to do with out of date adb?
ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
nkk71 said:
isnt "error closed" something to do with out of date adb?
Click to expand...
Click to collapse
Umh, no, i don' think
Guich said:
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
Umh, no, i don' think
Click to expand...
Click to collapse
I haven't tried rebooting the device seems to be the only thing I left out.
I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.
worked for me
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload
morheb said:
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload
Click to expand...
Click to collapse
Yay. That Just worked for me using Crunchbang Debian. Thanks morheb that little tweak of using 'sideload' was the key
Can anyone help me push vold.fstab file with adb?
Stock Recovery on mediatek platform. with adb i got same error as this thread. Error:closed
KoolAidBigMan said:
I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.
Click to expand...
Click to collapse
Perfect - worked for me - exact same issue - adb wasnt recognising my phone was in sideload and sideload command wouldnt work but push would - plus getting error closed message on adb usb command. Googled the above adb file, downloaded, 15 second install and now sideloading is working on my SG2 with CWM recovery 6.0.2.9 (kitkat). I was obviously using an outdated ADB driver (1.0.29).
Thanks a lot KoolAidBigMan !! Big up...
Jimbo
EDIT : Spoke too soon - now getting another error when trying to sideload.. will google it.. failed to write data 'protocol fault (no status)'
EDIT : Sorted. Ended up getting round it by pushing the files instead - found instructions on Cyanogenmod forums. Thanks once again.
http://forum.xda-developers.com/sho...wQFjAA&usg=AFQjCNGgPmMne0aYCd9RojZZhy89cQjnCw
Try this
Sent from my C6916 using XDA Free mobile app
Link not working?? Im ok now anyway.. Time to test my screen casting to my Chromecast.. :fingers-crossed:
mtk6572 have same error
I have same error.. but I know that my phone's usb debugging is not enable.. so I got this error:close..
My phone is on bootloop so I can't enable the usb debugging.. Is there any way to enable the usb debugging using adb commands? I trying to push the framework-res.apk on my phone.. because it is the cause of the bootloop.
i'm a nood
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.