Develop Bugs

[Q] How do I push a stock recovery to my HTCone using ADB?

So I admit I screwed up and started the whole root process without reading and studying about adb. What happened was I enabled developer mode and disabled fast boot on my HTCone. I then tried to use the rumrunner root method. It was successful and gave me S-off, unlock and SUser. Where I failed at was just coming over from an iPhone and having a HTC Evo in the past I was not familiar with adb or have I done any development. So I didn't even have adb set up and it left me with my custom recovery. I let a friend look at it that had some linux experience and he deleted my stock recovery and tried to push the TeamWin Recovery Project recovery to my phone. This failed and left me with no recovery at all. I then still not knowing what was going on got frustrated and tried to remove root and just run everything stock till I studied up more. Well I removed root access but I still have s-off, fastboot and unlocked. Since I had no recovery I can not do anything but run what I have on my phone now. I did however do a backup of everything before this using titanium backup. But my understanding you have to have root to use it.
Since my screw up I have studied up on adb and installed everything needed. I have played around with it just without making changes just to get familiar and test if it was working. I tried to use rumrunner again but it fails at the end but does connect to adb now.
What I need to know is can I push my stock recovery back to my phone via adb then try to use rumrunner again for root? Or what can I do since S-off and unlocked?
I admit I pulled an idiot move and will study and learn the whole process before doing anything new.
Thanks in advance for all help.

I have the 1.10.605.8 software version and I'm on Android 4.2.2

You didnt really do anything to your device honestly.. Its pretty much untouched, for root, simply download superuser from playstore, rumrunner is manily for the s off , bootloader. Also head over to original android development section and install twrp recovery.
Use flashify from playstore to flash recovery if you like aswell instead of adb.
Sent from my M7 using xda app-developers app

First, take a deep breath! Everything will be OK. As digitalbot mentioned, you phone should be fine.
Some clarification first. You do not use adb to flash a recovery, kernel, or anything else. That's fastboot and you'll be doing that from the bootloader, not while booted in the OS. Fastboot does not work while in the OS, adb does not work while in the bootloader. Since you were able to use rumrunner, adb and fastboot should already be installed on your computer and working. Now, understand that the fast boot that you disabled to use rumrunner is not the same as the fastboot that you use to to communicate between your computer and phone. Similar term, but completely and unrelated things.
Sounds like you are still s-off so no need to use rumrunner again. You mention having a custom recovery. Did you install it? Rumrunner does not install a custom recovery so unless you did, you still have stock recovery. To verify, plug in your phone to your computer and open a command prompt and type "adb reboot recovery." Phone your reboot to recovery. What recovery does it boot? If it's not TWRP or CWM, find a custom recovery in the forum (I use TWRP) and follow the instructions there to flash it to your phone from the bootloader. You'll do that with fastboot not adb.
Now for root, verify that you do not have root. Install a root checker from the playstore and check. If you don't have root, you'll have to flash SuperSU from recovery so go to http://download.chainfire.eu/supersu and download SuperSU to your phone. Reboot your phone to recovery and install the zip. You should now be rooted, double check with root checker. Now go to the playstore and install SuperSU to stay up to date.
Not sure if I covered all your questions, so post back if you still need clarification. Good luck!

Thanks guys!
I was able to install TWRP and also Superuser the same way.
Here are the instructions I used. Maybe they will help someone else like me.
Power off your device, then press and hold Power and Volume Down until you're in the bootloader menu. Highlight FASTBOOT and press Power. You should see Fastboot USB highlighted in red.
Open a command prompt on your computer and navigate to your SDK directory. Type "fastboot flash recovery twrp.img" and hit Enter.
Then I backed up my stock rom using TWRP
In TWRP's main menu, tap Reboot. It will tell you that you're not rooted and ask you to install SuperSU, so swipe to confirm. When you reboot your phone, you should see a notification that you need to install the SuperSU app. Open the notification and select TWRP, since the app from Google Play only works with S-OFF.
Worked flawlessly.
I installed NuSenseONE max and I love it so far. :good:

Oh of course I downloaded the latest TWRP build and renamed it before I copied it over.

Good work, yeah not really that tough, now accidently wipe your internal storage and flash a RUU, fun all over again haha :beer:
Sent from my M7 using xda app-developers app

HTC One Stuck in Bootloader

So earlier today I had my Verizon HTC One running smoothly; 4.3, 2.10.605.10, all that jazz. Then firewater came out, so I did S-Off. I then installed Clockworkmod, because TWRP wouldn't (turns out I installed the m7 variant instead of the m7vzw one). I also had the wrong version of clockworkmod, so it wouldn't factory reset or clear cache. I decided I would try to install Cyanogenmod anyway, and right after I started the install I found the correct version of TWRP so I hard reset out of the install with the Power and Volume Down buttons.
Now I am stuck in bootloader, and there is not much I can do. I can't install the RUU that i have because I cant "fastboot oem lock" and I also can't flash or boot directly to the TWRP or Clockworkmod .img files. Any ideas on how to fix it?
tl;dr I stopped a .zip install and now I am stuck in bootloader HELP PLEASE

Billcheese5 said:
So earlier today I had my Verizon HTC One running smoothly; 4.3, 2.10.605.10, all that jazz. Then firewater came out, so I did S-Off. I then installed Clockworkmod, because TWRP wouldn't (turns out I installed the m7 variant instead of the m7vzw one). I also had the wrong version of clockworkmod, so it wouldn't factory reset or clear cache. I decided I would try to install Cyanogenmod anyway, and right after I started the install I found the correct version of TWRP so I hard reset out of the install with the Power and Volume Down buttons.
Now I am stuck in bootloader, and there is not much I can do. I can't install the RUU that i have because I cant "fastboot oem lock" and I also can't flash or boot directly to the TWRP or Clockworkmod .img files. Any ideas on how to fix it?
tl;dr I stopped a .zip install and now I am stuck in bootloader HELP PLEASE
Click to expand...
Click to collapse
Are you able to access fastboot from the boot loader?
If so do
Fastboot reboot recovery
Since you have TWRP installed already? If you can get adb sideload to work you can flash a new ROM of your choice after you clear the dalvik cache and such. If adb won't work for you you may have to order an otg cable to get that ROM to your phone. If you can't access fastboot and/or get into recovery.... RIP M7Vzw

eXperianceHD said:
Are you able to access fastboot from the boot loader?
If so do
Fastboot reboot recovery
Since you have TWRP installed already? If you can get adb sideload to work you can flash a new ROM of your choice after you clear the dalvik cache and such. If adb won't work for you you may have to order an otg cable to get that ROM to your phone. If you can't access fastboot and/or get into recovery.... RIP M7Vzw
Click to expand...
Click to collapse
So I tried the fastboot rebbot recovery and I don't think that is a correct command, because when I do it a list of all the fastboot commands comes back and my phone doesn't do anything. Also it was working before but now my device isn't visible under adb devices, so I don't think sideloading a different rom will work. Plus I can't get to the recovery, or even the stock factory reset or anything. They all just bounce me back to the bootloader menu.
Do you think it would be worth it to order and wait for an otg cable or just order a new phone? I'm not due for an upgrade and I don't think I'm willing to shell out $500 for a new One, or even $400 for a new Moto X, so I think I'll be getting the Moto G (I'm on a student budget here).

Are you running your commands fro the platform tools folder?

Oh well
Thanks for the help guys, I wasn't able to run any adb commands like I could before, so I guess that's that. Again, I am at college, and my parents happened to be visiting so I gave it to them. I have accident insurance on my phone, so they are going to send it back and have the replacement sent to me... so I can try again, hopefully more successfully the second time :laugh:

[Q] Can't enter recovery Verizon m8

Hello guys, I've had a problem with my phone since flashing 5.0 firmware months ago but I'm just now getting to fixing it.
I have twrp recovery and some 5.0.1 rom that was in beta awhile ago. Everytime I boot into twrp in boots right into fastboot, whatever it's called, after about 5 seconds, so I can't flash any roms, which I think is the problem since it's pretty buggy.
Another thing is that Whenever I charge the phone while it's off, it boots into bootloader and therefore stops charging. Anyway I can fix my recovery without recovery?
This is Verizon htc one m8.
Thanks guys.
Edit: tried using twrp app to reinstall recovery but it boots into bootloader instead.

Fire n mage said:
Hello guys, I've had a problem with my phone since flashing 5.0 firmware months ago but I'm just now getting to fixing it.
I have twrp recovery and some 5.0.1 rom that was in beta awhile ago. Everytime I boot into twrp in boots right into fastboot, whatever it's called, after about 5 seconds, so I can't flash any roms, which I think is the problem since it's pretty buggy.
Another thing is that Whenever I charge the phone while it's off, it boots into bootloader and therefore stops charging. Anyway I can fix my recovery without recovery?
This is Verizon htc one m8.
Thanks guys.
Edit: tried using twrp app to reinstall recovery but it boots into bootloader instead.
Click to expand...
Click to collapse
Of course there's a way. Just like the way you first installed a custom recovery. I will give you instructions in case you've forgotten, or if the phone was pre-rooted when you got it.
Download the latest TWRP from here onto your PC.
When the download is finished, rename it to recovery.img and place it into your fastboot folder.
Hook up your phone to your PC, get into ADB/fastboot, and issue the command fastboot flash recovery recovery.img
Then when it's done fastboot reboot
You should now have a working TWRP recovery.

xunholyx said:
Of course there's a way. Just like the way you first installed a custom recovery. I will give you instructions in case you've forgotten, or if the phone was pre-rooted when you got it.
Download the latest TWRP from here onto your PC.
When the download is finished, rename it to recovery.img and place it into your fastboot folder.
Hook up your phone to your PC, get into ADB/fastboot, and issue the command fastboot flash recovery recovery.img
Then when it's done fastboot reboot
You should now have a working TWRP recovery.
Click to expand...
Click to collapse
Had to use my brother computer and set it up since I got a mac. Thanks for your reply, and sorry for the double post, I installed via fastboot, and I can confirm the most updated version was pushed to the device, but it still goes right into fastboot after booting into recovery.img
Edit: Did that fastboot erase cache thing in the command prompt and now it works. Thanks for telling me the commands for cmd again!

Fire n mage said:
Had to use my brother computer and set it up since I got a mac. Thanks for your reply, and sorry for the double post, I installed via fastboot, and I can confirm the most updated version was pushed to the device, but it still goes right into fastboot after booting into recovery.img
Edit: Did that fastboot erase cache thing in the command prompt and now it works. Thanks for telling me the commands for cmd again!
Click to expand...
Click to collapse
Oh Crap! I forgot to add that one. :silly:Erase cache is obviously needed. Sorry.

[Brick phone] help needed

I have flashed many phones before my G4 and this is the first time I'm having to ask for help.
The firmware installed was AICP CM13, then the screen went green with a DemiGod message. I held the vol down button to reboot and it came back up. After a few restarts and green screens i figured I needed to reflash the firmware. I booted into Recovery and while wiping the device to flash a new firmware, TWRP crashed. After leaving it for half hour or so, I took the battery out to enter into TWRP so I can flash the new firmware. TWRP is no there to be seen. I hold down the vol down and power button, releasing power for second or two and choose to go into recovery. Every time the phone just gets stuck on the LG screen displaying "Bootloader state :Bootlader unlocked!".
In short, I have no firmware, the device has been wiped and TWRP doesn't seem to be working.
I have tried to flash a KDZ file (H81520A_00.kdz) using the flash guide here. This comes back as unsuccessful saying "connection to server failed". As shown below.
View attachment 3605673
The method to flash an .img file using cmd on the pc includes moving the 4gb .img file to the parent folder of the phone storage. I can't get to move any files whatsoever to my device so figured this method would not work.
Seems if I can somehow flash TWRP, then I should be able to install a new firmware.
Any help much appreciated.

Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!

rav101 said:
Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!
Click to expand...
Click to collapse
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?

AndHD2 said:
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?
Click to expand...
Click to collapse
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi

It is late here and with me being tired I said recovery instead of download. I can boot into download mode but when I try to boot into recovery then it just goes straight to the LG splash screen and it will either remain in that screen or the green Demigod screen would come up.
I'm off to sleep and away from my laptop as I have to be up in 5 hours. Luckily I still have my Note 4 so at least I'm not without a phone in the morning. I will try the steps what you have suggested just as soon as I get back from work.
Many thanks

rav101 said:
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi
Click to expand...
Click to collapse
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.

AndHD2 said:
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.
Click to expand...
Click to collapse
Hi @AndHD2, I'm sorry but I can't think of anything else

rav101 said:
Hi @AndHD2, I'm sorry but I can't think of anything else
Click to expand...
Click to collapse
I had another demigod type screen but this was grey and not green with less detail. However it did say it were a kernel error.
Is the handset still under warrenty with the bootloader unlocked. I have a feeling its not

Tried to go back to stock and got adb error cannot read file

So I was tring to go back to stock completely, after I locked my bootloader and installed stock recovery, I proceed to sideload oss, like I've done before I put the phone in sideload mode, the device is recognized by adb although I got a cannot read file error, I downloaded the stock rom again (even though the zips were not corrupted as I could browse them easily) and the same thing happend.
Now I'm at a loss as what to do as it has stock recovery and no os installed, I can get into the bootloader and the stock recovery but I've never had this happen and I can't find anything that will help.
I tried with cmd prompt and adb in administration mode no change, I also made sure the file was in the adb folder.
I'm not sure of what else to say except to ask for help, I'm way bummed out, I've gone back to stock on this device before the only difference was I was running marshmallow other than that idk any other changes since the last time.
I would be very grateful for any help at all. Right now I just need a working phone,
Thank you for reading my post and thank you in advance for possible help with my issue.

Simple reboot of PC should do the trick, at least that did it for me

Didn't work for me, after the first fail I went to a l coffee shop and downloaded the rom again after shutting the pc off in the mean time.
It had no problem flashing the stock recovery it was only after I locked the bootloader and then tried to flash the stock rom

Check the specification of pc should be 4GB ram, drivers, and disable anti virus.

lebeatnik said:
Didn't work for me, after the first fail I went to a l coffee shop and downloaded the rom again after shutting the pc off in the mean time.
It had no problem flashing the stock recovery it was only after I locked the bootloader and then tried to flash the stock rom
Click to expand...
Click to collapse
Keep your bootloader unlocked, I assume you try to ADB sideload? Try adb push file /sdcard/ then manually flash it through TWRP
madsponge26 said:
Check the specification of pc should be 4GB ram, drivers, and disable anti virus.
Click to expand...
Click to collapse
This doesn't make sense... Even a 1GB RAM laptop can do this.

The specs. Of the pc is not the issue
So your advice would be to unlock the bootloader and use twrp?
Currently as I s

lebeatnik said:
The specs. Of the pc is not the issue
So your advice would be to unlock the bootloader and use twrp?
Currently as I s
Click to expand...
Click to collapse
No the specs are not an issue lol.. Basically it cannot read the file you are trying to sideload, this is because of either wrong adb drivers, or wrong Fastboot drivers... A easy work around is to manually push the file with "adb push filename directory" then you manually flash it but since stock recovery can't do this it won't work.

So what steps do I need to do to fix this,
Do I first lock the bootloader, then flash twrp? Also to push the file with adb what mode should I put the phone in?
Sorry For these terrible replies, I'm on a very old backup device.
It's odd to me as adb detects the device just fine, I was even able to flash the stock recovery, as I was trying to go back to complete stock.
In all I need to get the device work again.
I have the latest stock rom and twrp, I just don't want to make it totally bricked as right now I can at least get the phone into the bootloader and in side load mode (although it doesn't work)
So basically I'm asking how in what order should i go about, locking the bootloader, flashing twrp, and push the rom, I've never done this before.
I can't thank you enough for trying to help me out.
I'm thinking I would unlock the bootloader then flash twrp recovery, then idk what mode I should be in to try and push the rom via adb (I've never done this) as once I get twrp on the device and have the rom on the device I hope to have no problem flashing the rom through twrp.
Thank you for replying I hope to resolve this ASAP.

Sorry for not editing my previous post im struggling with the device I'm currently using, I don't understand why my drivers or adb version isn't working as i had no problems locking the bootloader and flashing stock recovery, the only problem I ran into was the last step, flashing the rom.
So yeah I don't know but after I locked the bootloader.... problems

lebeatnik said:
Sorry for not editing my previous post im struggling with the device I'm currently using, I don't understand why my drivers or adb version isn't working as i had no problems locking the bootloader and flashing stock recovery, the only problem I ran into was the last step, flashing the rom.
So yeah I don't know but after I locked the bootloader.... problems
Click to expand...
Click to collapse
Unlock your bootloader, install twrp. Then wipe all partitions. Adb push your rom to a directory you can remember I usually do /sdcard/ (just stay in twrp.) then you click on install and your rom should be there.
Keep the bootloader unlocked... Just in case, no need to relock it again since you will lose data if you run into an issue.

THANK YOU! All I did was unlock the bootloader and the phone started up I am assuming it did not wipe the system partition and it ended up restarting as if I did a factory reset