Database Develop

[Q] i need help for my "bricked" phone.. i know it can be fix :-/

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

[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.

Full Panic Mode. Boot Issues + Format

Hey guys,
I done ****ed it all up.
Was in my TWRP recovery on my One, was wiping the phone to prepare for a new rom. Unfortunately, I was stupid and didn't realize that I was formatting it instead of wiping it. Now, I have a useless chunk of beautiful metal.
I can get into TWRP, but cant really do anything from there. It wont connect to my PC ( I dont see it under My Computer ) so I cant move any roms over to flash. I feel like I'm missing something very simple here.
Any ideas?

Adb sideload from recovery, advanced option.
Sent from my HTC One using Tapatalk 4

Dont panic as pablo11 have said, you can use adb sideload to sideload a rom.
Boot into twrp go to advanced, then adb sideload and swipe then on your computer open a command line where you have your folder for rooting the htc one (where fastboot is etc) and put the ROM you want to flash in that folder and type adb sideload ROM.zip and you should be good to go!

ADB Sideload
What is ADB*sideload?
ADB*sideload is a new feature that was added to AOSP*recovery in Jelly Bean.* As of version 2.3, TWRP*now supports ADB*sideload mode.* ADB*sideload is a different ADB*mode that you can use to push and install a zip using one command from your computer.* Most likely*ADB*sideload won't be very useful for your average recovery user, but ADB*sideload can be a huge time-saver for a ROM developer.
How do I*use ADB*sideload?
Have a recovery installed on your device that supports ADB*sideload like TWRP*2.3 or higher
Have newer ADB binaries installed on your computer.* If it's been a while since you installed ADB on your computer, you may need to get the latest ADB binaries in platform-tools from*the Android*SDK.* You will need version 1.0.29 or higher.* You can find your current version by typing*"adb version" at the command line.
Set the device into ADB*sideload mode. In TWRP*you do this by going to Advanced then ADB*Sideload.
From the command line, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page.* It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device.* As soon as the file is copied to your device, it will automatically be installed.* When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB*mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
Sent from my HTC One using Tapatalk 4

Instructions:
http://forum.xda-developers.com/showthread.php?t=2325853&highlight=sideload

All fixed last night. Thanks guys, got my phone running again! Now to fix that radio...
Sent from my Nexus 7 using XDA Premium 4 mobile app

yasha.sinitski said:
All fixed last night. Thanks guys, got my phone running again! Now to fix that radio...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Happy to hear it and glad to help!

[Q] Device Brick!!! HELP!

I think I bricked my phone.... :'(
I was running Android Rev 61.1 and then my screen started to flash and then it would reboot. It kept doing it and so then I decided to try to wipe my phone and install Android Rev 6.1 GE and then it would get to the "pick a language screen" and then after 2 or so seconds it would shut the screen down and if I press the lock button then it would reboot.
I went to format my storage and then (like a complete IDIOT) I formatted the whole thing causing me to lose all my ROMs on the internal storage.
Now I can't put any ROMs on it cause the only place that I can access without it rebooting is the TWRP recovery.
I'm soooo stupid....
idk the ROM was really messed up..
Any way to load a ROM onto my phone (like CM) while I'm in recovery?
I am trying the Android Revolution method.
I have the mini-sdk downloaded and put on my c:\ drive. I download the HTC Sync Manager to get the drivers and after that I run the cmd.exe in the mini-sdk folder. When I type in adb shell it puts out the line ~ # ←[6n
What do I do then?

Bump.... Please help?

Adb push or adb sideload is your friend. Plenty of guides on such things
Sent from my GT-I9305 using xda app-developers app

nateboi81 said:
Adb push or adb sideload is your friend. Plenty of guides on such things
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Happened to me two weeks ago, and like you I panicked best thing to do is go into TWRP, and in advanced settings turn ADB sideload. Now open the latest fastboot in cmd (you need the newest, else it wont work). and type "adb push rom.zip /sdcard/" (without the " ofcourse)
rom.zip is the rom name and should be in the fastboot folder.
adb will sideload a filename called sideload.zip to the root of your phone.. You can install this like any regular rom

Yes this is what you have to do

[Q] HTC One - Custom Recovery not mounting storage

Hi,
I've looked everywhere for a solution but couldn't find one that helped. I was trying to flash a mod via TWRP custom recovery (followed all the instructions, wiped dalvik cache etc) but when rebooting, |the phone got stuck on the HTC One logo. I can access the custom recovery but when trying to mount storage, computer -running Windows 8- doesn't seem to do anything. Also made the mistake of not making a nandroid backup beforehand, so just need to be able to flash a ROM. Tried to adb push the file, but it gives me the error 'device not found'.

Delete... Sorry, I did misread it.

A lot of people have issues with getting drivers to work on Windows 8. Probably easier if you know someone who has Windows 7 and install the drivers on that
Sent from my HTC One using XDA Premium 4 mobile app

Minimal ADB and Fastboot
Maybe you could try this one here, solved this problem for me.
http://forum.xda-developers.com/showthread.php?t=2317790
You can check if adb can find your phone with "adb devices". If there is none, you have to check your drivers again.
I then used adb sideload in TWRP. Start it when connected and type "adb sideload update.zip" (or whatever your zip is called). He will load the file to your root /data directory. You can install the zip from there then.

Thanks
Thanks for the answers! I'll try using another computer that's not running Windows 8 - I have a feeling its a problem with the drivers.

Same problem here, when i type fastboot devices the serial appeared but i cant push files like the stock odex rom, cant, i found out i cant access my internal memory, is there a solution for that?
Thanks!!

Fastboot and adb are different. You can only adb push from in a Rom or in recovery
Sent from my HTC One using XDA Premium 4 mobile app

nateboi81 said:
Fastboot and adb are different. You can only adb push from in a Rom or in recovery
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
even in settings in twrp or cwm recovery, i cant mount my memory, is there a way to remount my memory on my phone? so that i transfer stock rom to my phone