New Verizon HTC one S-off but can not access recovery - Verizon HTC One (M7)

I just got an HTC one from Best Buy Mobile (Verizon) yesterday. Turned S-Off using runrunner. Verified root but can not access recovery. I had the same issue with a S4 but it was a known issue for all that has updated to the 4.3.
I have tried all the suggestions in flashing TWRP. I am wondering if this is a Verizon related issue? Maybe they are putting something on their phones to prevent recovery?
HELP!!!!

Something is really jacked up with my phone. It kept saying Unfortunately Amazon has stopped. Over and over again. So I gave up and went to do a factory restore and data wipe. I first went to Super user and removed permanent root. I then tried to do a factory wipe through settings/backup & reset reset phone. It still gave me issues trying to enter recovery mode. It would get hung up and then reboot to a sort of safe mode version of the OS. (with a red disclaimer at the bottom). Then I tried to do factory reset by holding the volume down and power. Its doing the same thing. At this point I don't are about root I just want a working phone.
Any suggestions?

Flash twrp from the xda thread here and then flash arom. What exactly are you doing to flash it?
Sent from my One using xda app-developers app

I have tried flashing a recovery. Now I dont have root and cant do anything. It will not let me even upgrade firmware. I tried to get it back to stock. My recovery is jacked up.

adodson927 said:
I have tried flashing a recovery. Now I dont have root and cant do anything. It will not let me even upgrade firmware. I tried to get it back to stock. My recovery is jacked up.
Click to expand...
Click to collapse
OK, so you are s-ff, is your bootloader unlocked?
IF you are not on stock recovery YOU CANNOT run an update

I'm s-off bootloader unlocked. I have no recovery. Not even stock.
Sent from my HTC6500LVW using XDA Premium 4 mobile app

adodson927 said:
I'm s-off bootloader unlocked. I have no recovery. Not even stock.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
.. you have to have a recovery..
I think?
can you successfully fastboot flash a custom recovery? If not can you fastboot the stock recovery..?
To be completely honest, I would just run the RUU. should fix you right up

You could boot into RUU and flash the decrypted stock rom zip to get back to straight stock. The zip reflashes stock recovery. I don't see why that wouldn't work.
Edit: Oops. Didn't even notice andy just recommended the same thing lol. My fault.

adodson927 said:
I'm s-off bootloader unlocked. I have no recovery. Not even stock.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thats odd, i thought you had to have a recovery of some kind.
Here is what I would do:
Lets try Flashing CWM instead of TWRP in fastboot I will post it, and I will also post the stock recovery there to as well.
https://www.dropbox.com/s/kk2esdrx1g1b50p/recovery-clockwork-touch-6.0.4.5-m7vzw.img
the image is easily installed via an unlocked bootloader with the following command:
fastboot flash recovery imagename.img
in this case: fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7vzw.img
See if it actually takes, and report back any errors.
If for some reason it does not, try booting into bootloader/fastboot then push the stock recovery:
https://www.dropbox.com/s/hgzgq84svzahvnv/htconerecovery_signed.img
Hopefully that will at least take and try to push CWM again , reboot bootloader and reboot into recovery . I am hoping that does it for you.
Go here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip and dump SU on the root of your SD card and flash the SU.
I have seen people have all kind of weird issues with rum runner and I am just glad i had the official java card method used on mine. I also tend to just use a stock ROM which is just de-bloated.
Anyways I have used Santod040 roms in case i need to go back to pure stock ROM only: http://forum.xda-developers.com/showthread.php?t=2485319
You will need the odex one to run any OTA
The firmware is a different thing to flash.
here are the checksums:
htconerecovery_signed.img
MD5: E3F5208454689BE7F09835D4A60953A8
SHA-1: 1B0734D97732039528159AD1409AFEE858B5E9F1
SHA3-256: E0741EB77E5DEBEA932EE74F374FAC9E1037776178944279E8B12832C30E2546
recovery-clockwork-touch-6.0.4.5-m7vzw.img
MD5: 21A386CB920C485844E3BE0727351838
SHA-1: 312350D7383850915A648E2060AA2FC72B5EA08F
SHA3-256: 78B0C42CD62D3EB2B18BF62B544FC86878A56199DB96D13F26EA65663A822932

Thanks guys!
I was able to install TWRP and also Superuser.
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.
Download the latest version of TWRP for your phone and carrier. Rename file to twrp.img.
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.

adodson927 said:
Thanks guys!
I was able to install TWRP and also Superuser.
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.
Download the latest version of TWRP for your phone and carrier. Rename file to twrp.img.
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.
Click to expand...
Click to collapse
how else were you trying to flash a recovery ?!?

Goo.im app as well as ROM Manager, ROM Toolbox can flash recoveries. I've notice there isn't much compatibility with the m7vzw though. You can also use terminal command's from the device. All of these require root access though.
Sent from my One using XDA Premium 4 mobile app

Hey everyone, so my problem is that i did run rumrummer the way it said on the directions and i double checked my rom version type countless times. It says that i am unlocked and s-off, but i cant access recovery. I tried flashing recovery with fastboot command prompt, and still no luck. It gives me a "error: cannot open 'open.img', I navigated to the folder that it is located in and executed the command properly every time. I also dont know how to flash superuser using flashboot, so any help will be very much appreciated. Also I'm kinda new to rooted, I have some experience from a few years back, but dont remember everything.

Jo5ton1018 said:
Hey everyone, so my problem is that i did run rumrummer the way it said on the directions and i double checked my rom version type countless times. It says that i am unlocked and s-off, but i cant access recovery. I tried flashing recovery with fastboot command prompt, and still no luck. It gives me a "error: cannot open 'open.img', I navigated to the folder that it is located in and executed the command properly every time. I also dont know how to flash superuser using flashboot, so any help will be very much appreciated. Also I'm kinda new to rooted, I have some experience from a few years back, but dont remember everything.
Click to expand...
Click to collapse
place the name.img file in the same folder as the adb and fastboot executables, open command prompt as administrator for that directory, then type "fastboot flash recovery name.img" substitute name.img for the actual name of the file including extension and make sure there are no quotes around it. also, use "fastboot devices" or "adb devices" to make sure your phone is being recognized.

I got it to work, finally. Thanks for the reply pointedge. I beat u to it earlier in the day and forgot to post up again that I got it. It was like u said, I just had the file in the wrong folder.
Sent from my HTC6500LVW using XDA Premium 4 mobile app

nrfitchett4 said:
how else were you trying to flash a recovery ?!?
Click to expand...
Click to collapse
I'm willing to bet he flashed the wrong recovery. It's happened to a lot of people.

Related

[RECOVERY] PRE/Post OTA Stock Recovery Images

For anyone who wants it, here's the STOCK PRE & Post-OTA recovery images. (I just added PRE-OTA if for some reason it's needed down the road.)
If you plan on flashing it back over the ClockWork recovery image, make sure S=OFF otherwise the flash won't complete successfully.
You can turn S=ON back after the flash.
THIS IS NOT A FLASHABLE ZIP - I only zipped it to get it to upload as an attachment! You will need to do a Fastboot Flash to install (there may be other methods but Fastboot is what I used).
Below are instructions I am borrowing from the Amen-Ra recovery installation from the N1 - they will apply the same here!
via fastboot
Code:
Copy recovery.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding volume down, then select fastboot)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery.img
via terminal app
Code:
Copy recovery.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery.img(press enter)
reboot recovery(press enter)
I hope this proves to be useful to at least 1 person!
Thanks a lot!
MYT4G (Glacier)
sounds like a good way to restore...now all we need are some roms
The reason I dug this up was that I am very curious as to whether after having rooted, if you have stock recovery and S=ON whether or not further OTAs will come to you.
Back in my N1 days if the stock recovery was not present an OTA couldn't install.
Sweet! Was looking for the stock recovery before exchanging my mytouch. Where/how did you get this?
Great contribution
c_licious said:
Sweet! Was looking for the stock recovery before exchanging my mytouch. Where/how did you get this?
Click to expand...
Click to collapse
Actually I merely extracted them from the stock Rom here on xda and from the ota update file someone posted but nobody has figured out how to apply. Both have been tested on my phone.
I figured I would make it easier on everyone who simply wants to download the recovery as opposed to the entire rom or update.
Does this then solve the problem people have of not being able to root because they downgraded? If so, we may not need that OTA update link anymore.
kitsunisan said:
Does this then solve the problem people have of not being able to root because they downgraded? If so, we may not need that OTA update link anymore.
Click to expand...
Click to collapse
Check this thread out - I was just reading it, should help out!
http://forum.xda-developers.com/showthread.php?t=843428
Nevermind, wasn't paying attention when I posted, thought it was something else. Still, will come in very handy for me, I just got my replacement today, and replacing clockwork recovery was the last thing I needed to do.
JWhipple said:
The reason I dug this up was that I am very curious as to whether after having rooted, if you have stock recovery and S=ON whether or not further OTAs will come to you.
Back in my N1 days if the stock recovery was not present an OTA couldn't install.
Click to expand...
Click to collapse
Thanks for making these available. I also wanted to get the recovery to hopefully let me get OTA's again (got the first one).
I was hoping I could do so with everything stock (unroot with visionary) but also being able to leave s=off - does that absolutely have to be set back =on?
You got the first one after reverting back from being rooted?
gaww said:
Thanks for making these available. I also wanted to get the recovery to hopefully let me get OTA's again (got the first one).
I was hoping I could do so with everything stock (unroot with visionary) but also being able to leave s=off - does that absolutely have to be set back =on?
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
gaww said:
Thanks for making these available. I also wanted to get the recovery to hopefully let me get OTA's again (got the first one).
I was hoping I could do so with everything stock (unroot with visionary) but also being able to leave s=off - does that absolutely have to be set back =on?
Click to expand...
Click to collapse
Not sure - but if you want to "appear" to be 100% stock w/ OTA update, probably best to set it to S=ON.
The thing is though, my understanding is that if even if you use the unroot, you still will have persistent root unless HTC or Google somehow patches the exploit that was used to get root in the first place. So, you'll have root but won't be able to change anything on the ROM unless you turn S=OFF again. I ran the unroot and S=ON and still have the ability to do everything (other than mess with the ROM) that your standard Rooted phone would be able to.
jjlean said:
You got the first one after reverting back from being rooted?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
You can force install the first OTA, but without forcing it I don't believe it's going to happen.
http://forum.xda-developers.com/showthread.php?t=843428 shows how to do it.
JWhipple said:
You can force install the first OTA, but without forcing it I don't believe it's going to happen.
http://forum.xda-developers.com/showthread.php?t=843428 shows how to do it.
Click to expand...
Click to collapse
I got the first OTA before doing s=off (needed the OTA to make it work at the time - did it first day).
I am trying to find out about the second OTA, about which there is practically no information available. I would I assume I have to have the first one installed to get the second (but what is it?).
Again - thanks for posting the original stock recoveries - have a feeling I may need one down the road (like when 2.3 finally comes out and I have a reason to go back to stock).
I've yet to see anyone say that they have actually received a 2nd OTA... Go figure?
Would I be able to use this recovery image to get my phone back up an running again?
I was messing around trying to apply the custom animations and somehow ended up getting my phone stuck in a constant reboot mode.
I have done some research and think that I am on the right track, but can someone verify this for me?
I have permroot with S-OFF, factory reset from the bootloader menu does not get me anywhere, but the phone is recognized through the "fastboot" prompt.
Would I just place the recovery image in the root of the sd card and run these commands?:
fastboot erase recovery
fastboot flash recovery.img
Thanks in advance for any help
From terminal im getting image not found? Do I have to mount or something?
Also... From pc ....Put .img in a place where fast boot can see it, where is thay
Sent from my HTC Glacier using XDA App
Ok guys, the absolute easiest way to do this... This is dependent upon you having S=OFF.
1) Install the android SDK....
2) In my case, fastboot is in C:\sdk\tools as I installed the SDK to C:\SDK. For fastboot to see the image file, I placed the image file (after extracted from the .ZIP) into the C:\sdk\tools folder.
3) Shut down the phone. Turn it back on while holding down the VOL-DOWN button.
4) On the bottom of the screen you'll see:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
5) FASTBOOT should already be highlighted. Press the POWER button.
6) If your USB isn't already plugged in, do it now.
7) Give the PC max of 30 seconds to recognize the bootloader mode.
8) From a DOS prompt, navagate into the C:\SDK\TOOLS folder.
9) Type "FASTBOOT DEVICES" (less the quotes) and press ENTER. If your phone is recognized it should show the serial info of your phone.
10) Type "FASTBOOT FLASH RECOVERY RECOVERY.IMG" (again, less the quotes) and press ENTER .
11) You should see the send and receive. If you do, SUCCESS.
I was able to do all of the steps listed, but I keep getting stuck at a boot loop.
Fastboot recognized my phone, flash recovery from fastboot says that it is successful, but still no luck.
Sent from my HTC HD2 using XDA App

Help, soft bricked my device.

I was attempting to unlock/root and long story short, now I have TWRP installed, and I can get to FASTBOOT but if i try to boot normally I get the Nexus logo, and no further. When I unlocked, I installed TWRP then loaded it. After leaving TWRP it said 'Seems you are not rooted, want to root"? or something to that effect. I clicked YES and now I'm stuck. Since I had just unlocked it, it *should* have reset my entire device(which was all stock anyway) so I am not sure what went wrong. I have been trying everything I know but I'm now out of ideas. Would appreciate any help. I see now that the version of SuperSu that it would have pushed would have been wrong, would that be preventing the tablet from booting?
If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app
ronni.rasmussen said:
If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.
Landara said:
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.
Click to expand...
Click to collapse
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app
ronni.rasmussen said:
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app
Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
I would suggest you just restore your N7 back to stock. No need for root yet, seriously! But this should help get you going in the right direction.
Power it off completely. Hold Power + Volume down until it boots into the bootloader. Run the following commands:
fastboot devices (to confirm you are connected)
fastboot flash recovery recovery.img
If you haven't unlocked your N7 yet, run fastboot oem unlock first.
ronni.rasmussen said:
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.
Landara said:
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.
Click to expand...
Click to collapse
Start over by downloading recovery, Superuser and a clean stock rom image.
But before that you could try to reset all data in recovery (factory reset) and cache if you haven't tried.
http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!
Landara said:
http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!
Click to expand...
Click to collapse
Super

[Q] S-Off Recovery problem

Hello! Hi, I'm kinda new to all of this, and I downloaded all of this today. I've been reading a lot and watching a lot of videos, yet I nothing really seems to fix my devices problem.
I have a HTC One on the Verizon carrier and I have just recently S-Off'd it using Rumrunner (I used the Rom checker to make sure it was unlocked and it even says it is whenever i enter bootloader). Although I was successfully able to unlock my device, I seem to have trouble with entering into recovery mode. Whenever I try to go into Recovery mode, my device reads "Entering Recovery mode" in pink at the top for about 10-20 seconds. Then all of a sudden it just goes black and it reboots as if I had never even chosen to go into recovery mode. I don't know if this holds any significance, but I've noticed that my boot up logo only has "HTC ONE" on it, the writing "simply beautiful" is now removed.
I have tried using cmd and ADB to clear the cache, I've tried using ClockManager from Rom Manager, and I've tried multiple times on regular mode. None of them really seem to work and I don't really understand why. Can anyone please offer me some suggestions? Thank you.
Seriously I only want a transparent theme for my HTC One that's all LOL
@Cinestra hey so I'm also kind of new to this but I can try to help. So what custom recovery did you flash?
Chilidog said:
@Cinestra hey so I'm also kind of new to this but I can try to help. So what custom recovery did you flash?
Click to expand...
Click to collapse
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app
cstrife999 said:
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Hello, thank you i very much appreciate your advice. I did not try flashing yet.
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S
Cinestra said:
Hello, thank you i very much appreciate your advice. I did not try flashing yet.
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S
Click to expand...
Click to collapse
Hmm... That is strange indeed...
Sent from my HTC6500LVW using xda app-developers app
I had the same problem and discovered that when i enter stock recovery, when the black screen appears, i had to press power+vol up to get it to show up. You may have to press them several times to get the timing right. Hope that helps!
cstrife999 said:
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
when I got my phone back from sonic, twrp wouldn't install for me so I had to use CWM.
OP should probably try both and make sure he's following the instructions here:
http://forum.xda-developers.com/showpost.php?p=45513789&postcount=2
I'm quite new to rooting as well. Seems we are having the same problem. I was able to get beaups' s-off exploit to work without any problems. When I load into HBoot it says the phone is unlocked and I've also used a Root Checker to determine the phone is rooted.
My next step was to try and install TWRP using fastboot. I ran a command prompt window using administrator rights during the whole process. Everything seemed to install just as it should. The problem is when I try to boot into recovery I'm having the same problem as Cinestra. I simply get the HTC logo screen with "Entering Recovery..." in pink letters at the top of the screen for around 15 seconds, then it reboots as if it would normally and restart the phone as usual. I have tried to reinstall the custom recovery step by step, using 'fastboot erase cache' before and after as well as using an older version of TWRP just in case that would help. Again, everything seems to install just fine but I still can not boot into recovery. I've also tried to see if the GooManager app would be of some help, but that is also not working for me.
I've since also tried flashing CWM but the same situation occurs. Install seems fine but no luck booting into recovery. ROM Manager was a no go as well.
I just can't figure this out. I've tried different cables, deleted and reinstalled HTC drivers/adb/fastboot, and multiple recovery images. I just gave beasleyj62's suggestion of holding down the power/volume down buttons after it goes to black when it starts to restart but that just put me into a bootloop sadly. Had to hold down the power button a few times to get it to boot correctly again. Any help on this would be greatly appreciated. Cheers.
I would also just like to add a little more info on my device in case this will help troubleshoot this. I'm using a Verizon HTC One with Software Number 1.10.605.10.
Same problem here. Tried flashing from fastboot, using goomanager, using rom manager, and from within the terminal emulator (can't find the command now but i think it was on the TWRP site).
Fastboot gives every indication it works, goomanager and rom manager give an error, and the emulator method appeared to work.
Tried to fastboot both TWRP and clockworkmod but neither worked.
At work right now but still investigating...
*edit: goomanager error states 'no recoveries found for your device.'
carassius-one said:
Same problem here. Tried flashing from fastboot, using goomanager, using rom manager, and from within the terminal emulator (can't find the command now but i think it was on the TWRP site).
Fastboot gives every indication it works, goomanager and rom manager give an error, and the emulator method appeared to work.
Tried to fastboot both TWRP and clockworkmod but neither worked.
At work right now but still investigating...
*edit: goomanager error states 'no recoveries found for your device.'
Click to expand...
Click to collapse
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
I wonder if you guys are having problems because you tried to use rom manager or goomanager and it messed something up...
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Chilidog said:
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Click to expand...
Click to collapse
Thanks. That answers that part of the question.
Chilidog said:
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
I wonder if you guys are having problems because you tried to use rom manager or goomanager and it messed something up...
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't realize they weren't supported. Sadly, I don't think they are the culprit here. I tried to flash using fastboot first. I attempted it with 'openrecovery-twrp-2.6.3.0-m7.img' first then with the older version 'openrecovery-twrp-2.6.1.0-m7.img' next. It was the same issue with both. I didn't attempt using GooManager until after I had used fastboot, though GooManager just failed to initialize the install. I mean it didn't even run or change anything as far as I can tell, and simply gave an error back saying "No recoveries were found for your advice".
Did the same thing with CWM and ROM Manager. I installed CWM from fastboot. Only after seeing the same thing happen when I tried to install TWRP did I give ROM Manager a shot. This also just gave an error message without initializing any install. Thanks for the input though.
Prizm432 said:
Didn't realize they weren't supported. Sadly, I don't think they are the culprit here. I tried to flash using fastboot first. I attempted it with 'openrecovery-twrp-2.6.3.0-m7.img' first then with the older version 'openrecovery-twrp-2.6.1.0-m7.img' next. It was the same issue with both. I didn't attempt using GooManager until after I had used fastboot, though GooManager just failed to initialize the install. I mean it didn't even run or change anything as far as I can tell, and simply gave an error back saying "No recoveries were found for your advice".
Did the same thing with CWM and ROM Manager. I installed CWM from fastboot. Only after seeing the same thing happen when I tried to install TWRP did I give ROM Manager a shot. This also just gave an error message without initializing any install. Thanks for the input though.
Click to expand...
Click to collapse
Yeah...I tried the fastboot method first too, for both TWRP and CWM. I really doubt that is the problem.
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
carassius-one said:
Yeah...I tried the fastboot method first too, for both TWRP and CWM. I really doubt that is the problem.
Click to expand...
Click to collapse
godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. I think it was 3 or 4 pours. Seemed to work flawlessly.
2. Still trying to learn which includes learning what an ruu is. Maybe that is my problem. I ran rumrunner and then have been trying to flash a recovery ever since...with no other steps.
godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. Nope, I had no issues while doing the S-Off. It took 3 pours for me.
2. I haven't used any RUU for this. So you suggest going back to S-On and locked, then using the RUU? Sorry, still new to the whole process so just want to be clear on procedure. Yeah, I've been considering going back to complete stock and starting from scratch again. I'll give that a go later tonight if I can't come up with anything else.
Thanks.
No, no. The only RUU available is a decrypted one, which can only be flashed while S-OFF. So the ideas I put down were distinct, and not steps. My thought is that either (i) you return yourself to full stock and non-root as is explained in a thread in this subforum, or alternatively, (ii) flash the RUU to get a fully untouched setup (the RUU contains the factory "rom", bootloader and recovery and will return it to being fresh from the factory) on the device and then flash the recovery.
Prizm432 said:
1. Nope, I had no issues while doing the S-Off. It took 3 pours for me.
2. I haven't used any RUU for this. So you suggest going back to S-On and locked, then using the RUU? Sorry, still new to the whole process so just want to be clear on procedure. Yeah, I've been considering going back to complete stock and starting from scratch again. I'll give that a go later tonight if I can't come up with anything else.
Thanks.
Click to expand...
Click to collapse
Cinestra said:
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S
Click to expand...
Click to collapse
I had the same problem and yesterday I posted my fix in this Forum's TWRP thread.
I had been using
openrecovery-twrp-2.6.3.0-m7.img
What I really needed was
openrecovery-twrp-2.6.3.0-m7vzw.img
Go here: http://goo.im/devs/Flyhalf205/M7VZW/openrecovery-twrp-2.6.3.0-m7vzw.img
beasleyj62 said:
I had the same problem and discovered that when i enter stock recovery, when the black screen appears, i had to press power+vol up to get it to show up. You may have to press them several times to get the timing right. Hope that helps!
Click to expand...
Click to collapse
Thanks for your solution, unfortunately though, it doesn't seem to work.
jpradley said:
I had the same problem and yesterday I posted my fix in this Forum's TWRP thread.
I had been using
openrecovery-twrp-2.6.3.0-m7.img
What I really needed was
openrecovery-twrp-2.6.3.0-m7vzw.img
Click to expand...
Click to collapse
Hmm alright so you suggest flash this other version of TWRP instead? That would make sense because the link looks like it's specialized for Verizon. I will try that out today!
godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. It took me about 3 pours. That is an interesting thought and I think it may very well be valid, but I would prefer not to reset or relock my device though.
2. I have not decrypted RUU yet because I was unfamiliar with the term. I may try this if the new TWRP code does not work
@Prizm432 it looks like you are flashing the wrong Twrp zip. It has to end in m7vzw.zip
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Help! Have I screwed up my bootloader?

So in the rush to get CyanogenMod installed on my newly-S-Offed phone, I downloaded CWM from the appstore and started looking through the various devices to flash ClockWorkMod Recovery to. I selected the vanilla HTC One, not the verizon-specific model. I have not yet rebooted my phone yet, but I am worried that doing so will brick the phone since I technically don't have the right bootloader. Looking through CWM's list on my phone, there is not a verizon-specific model bootloader. There is one on Cyanogen's site (can't post the link due to XDA restrictions), but it appears to involve rebooting the phone. How should I go about safely flashing a good bootloader onto my phone?
ab2 said:
So in the rush to get CyanogenMod installed on my newly-S-Offed phone, I downloaded CWM from the appstore and started looking through the various devices to flash ClockWorkMod Recovery to. I selected the vanilla HTC One, not the verizon-specific model. I have not yet rebooted my phone yet, but I am worried that doing so will brick the phone since I technically don't have the right bootloader. Looking through CWM's list on my phone, there is not a verizon-specific model bootloader. There is one on Cyanogen's site (can't post the link due to XDA restrictions), but it appears to involve rebooting the phone. How should I go about safely flashing a good bootloader onto my phone?
Click to expand...
Click to collapse
CWM is a custom recovery, not bootloader. Download your choice of CWM or TWRP, reboot into the bootloader and use Fastboot to flash it.
NotATreoFan said:
CWM is a custom recovery, not bootloader. Download your choice of CWM or TWRP, reboot into the bootloader and use Fastboot to flash it.
Click to expand...
Click to collapse
I am referring to ROM Manager from the android app store. When you bring it up it asks you to flash your bootloader. The bootloader I selected was the one for the Vanilla HTC One.
I don't use ROM Manager, but I just installed it on my phone. The prompts all refer to recovery, and make no mention of bootloader. See below.
Sent from my HTC6500LVW using Tapatalk
ab2 said:
I am referring to ROM Manager from the android app store. When you bring it up it asks you to flash your bootloader. The bootloader I selected was the one for the Vanilla HTC One.
Click to expand...
Click to collapse
Its most likely referring to the recovery, not the bootloader; Assuming you're root, Rom Manager is there to flash custom ROMS and custom recoveries. I don't think you'll have bricked your phone if you installed a bad recovery, but I think your best bet would be install a compatible one manually.
SO pick a thread and follow the directions under installation:
http://forum.xda-developers.com/showthread.php?t=2416273 CWM
http://forum.xda-developers.com/showthread.php?t=2416431 TWRP
i'd pick twrp
Well my phone will reboot safely, which is good.
However, rebooting into fastboot or recovery just reboots into normal mode. Recovery will say the first time that it's going into recovery, but will reboot again and go into normal.
Thoughts?
Success! I just had to keep scrolling. there was a version in Rom Manager, all the way down at the bottom under "m7vzw." Flashing that did the trick.
Thanks for the help.
Cheers.
ab2 said:
Well my phone will reboot safely, which is good.
However, rebooting into fastboot or recovery just reboots into normal mode. Recovery will say the first time that it's going into recovery, but will reboot again and go into normal.
Thoughts?
Click to expand...
Click to collapse
The S-Off exploit removes stock recovery, so it will go nowhere until you flash CWM or TWRP. Fastboot will work regardless.
Sent from my HTC6500LVW using Tapatalk
ab2 said:
Success! I just had to keep scrolling. there was a version in Rom Manager, all the way down at the bottom under "m7vzw." Flashing that did the trick.
Thanks for the help.
Cheers.
Click to expand...
Click to collapse
All that said, I can now boot into recovery no problem, but typing "adb reboot fastboot" just reboots the phone normally. Any idea why that might be?
I've never used that command personally. I have Quick Boot (Reboot) from the market and use it for getting into recovery and fastboot from Android.
Sent from my HTC6500LVW using Tapatalk
ab2 said:
All that said, I can now boot into recovery no problem, but typing "adb reboot fastboot" just reboots the phone normally. Any idea why that might be?
Click to expand...
Click to collapse
Do you have fastboot unchecked under power settings? Phone doesn't totally reboot with that checked.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
ab2 said:
All that said, I can now boot into recovery no problem, but typing "adb reboot fastboot" just reboots the phone normally. Any idea why that might be?
Click to expand...
Click to collapse
adb reboot recovery = takes you to recovery
adb reboot bootloader = takes you to fastboot/booloader
I don't believe adb reboot fastboot is a command, so it just does adb reboot

[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

Categories

Resources