Hey Devs,
I am running a HTC One M8 H/K from Sprint. I rooted it the week I got it and could not have been happier. A few days ago my 4G stopped working and I tried to install an OTA update but it wouldn't take. I tried to unroot and relock the bootloader but I think I have done some steps out of order. I do not have a recovery anymore although I still think I am rooted. I tried doing some RUU's but none of the .exe's will even start. I tried flashing firmware with a zip as well with the Hansoon's toolkit but I keep getting an error 12.
My fastboot info reads
*** Software status ***
*** Relocked ***
M8_WHL PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-1.08.20.0916
OpenDSP-v54.2.2-00564-M8974_HM.0811f
OS-3.31.654.2
eMMC-boot 2048
I had CWM PhilzTouch installed as a recovery but I when I select recovery on HBOOT I just get returned to the HBOOT screen. Any help would be greatly appreciated. I'm at wit's end here and know when it's time to ask for help. Thanks in advance.
dommiboy said:
I tried doing some RUU's but none of the .exe's will even start.
Click to expand...
Click to collapse
Do you have HTC Sync, or at least HTC drivers installed? This is required for the RUU to work.
What version of Windows?
dommiboy said:
I tried flashing firmware with a zip as well with the Hansoon's toolkit but I keep getting an error 12.
Click to expand...
Click to collapse
If its not a signed firmware package, it won't flash with s-on.
Do you NEED HTC Sync installed to run an RUU? I've never had it installed on my Windows 7 PC here at work and RUUs work fine but at home on my Windows 8.1 laptop they won't run past the T&Cs
EddyOS said:
Do you NEED HTC Sync installed to run an RUU? I've never had it installed on my Windows 7 PC here at work and RUUs work fine but at home on my Windows 8.1 laptop they won't run past the T&Cs
Click to expand...
Click to collapse
Definitely don't need HTC Sync to RUU (although not sure if you need HTC drivers, or if "generic" fastboot drivers will do). HTC Sync sometimes causes more problems than it solves. But I just mention HTC Sync, as its what most people have installed on their PC after connecting the phone and letting it do its thing automatically. And easy for folks to just Google for HTC Sync rather then finding a link for HTC drivers alone.
I have the HTC drivers on the computer. I'm able to adb commands and I originally rooted using this computer. The computer is running 8.1. When I try running RUU it never gets past the install wizard.
The firmware packages read signed in the filename. I have tried so many I can't even give you the links but I would say 90% came off this forum. I tried all of the base stock non-rooted complete firmware packs I could find.
dommiboy said:
I have the HTC drivers on the computer. I'm able to adb commands and I originally rooted using this computer. The computer is running 8.1. When I try running RUU it never gets past the install wizard.
Click to expand...
Click to collapse
If I knew that I'd tell you! When you get to the T&Cs, open a Run box and type in %temp% and in there, in one of the new folders, will be a zip file called rom. Copy this to your Desktop and flash this in RUU mode (fastboot oem rebootRUU) using htc_fastboot.exe (which I have here - htc_fastboot flash zip rom.zip) and it should work
dommiboy said:
The computer is running 8.1. When I try running RUU it never gets past the install wizard.
Click to expand...
Click to collapse
That may be your problem. RUUs don't play well with Win8.1. Try a Win7 or even an XP machine.
---------- Post added at 02:04 PM ---------- Previous post was at 02:03 PM ----------
dommiboy said:
A few days ago my 4G stopped working and I tried to install an OTA update but it wouldn't take. I tried to unroot and relock the bootloader but I think I have done some steps out of order. I do not have a recovery anymore although I still think I am rooted.
Click to expand...
Click to collapse
What happened when you tried to OTA?
You don't need to relock the bootloader to OTA, nor do you need to unroot. But all system files must be stock (nothing modified by root).
For a vast majority of instances (pretty much everything except trying to run RUU), I don't recommend to relock the bootloader. Its not required for OTA as mentioned, and it puts you in a worse position than UNLOCKED.
Did you try to fastboot flash the stock recovery and install the OTA again (believe you need to unlock bootloader again to do so)? You don't need a firmware zip to do that. Just find the stock recovery for your CID here: http://forum.xda-developers.com/showthread.php?t=2701376
---------- Post added at 02:10 PM ---------- Previous post was at 02:04 PM ----------
dommiboy said:
The firmware packages read signed in the filename. I have tried so many I can't even give you the links but I would say 90% came off this forum. I tried all of the base stock non-rooted complete firmware packs I could find.
Click to expand...
Click to collapse
Are you running firmware for your CID (its required with s-on)? If not, that is why you have error 12 signature fail with a signed file.
Hey Guys. I've been trying a few more things today. I first tried running opening the temp folder with the RUU install shield running but that's all the farther it gets. I never see a rom zip because it never makes it to the T&C's. Next I tried flashing these firmwares with Hansoon's toolkit.
4.20.6.51.10/URL]
[URL="http://forum.xda-developers.com/showthread.php?t=2729173"]3.30.654.2 Full Firmware From OTA/URL]
Both of those failed with a signature failure.
I will try flashing a recovery but I have no idea which one I should try to flash nor how to flash it.
In a final act of desperation for the night I tried to S-off with firewater which I pulled from web archive. I was able to push the file to the device, I had root permissions, I THINK I was able to chmod the file, however when I tried to run the file it just said not found. When I cd into the directory it's nowhere to be found?? I have no idea what happened there. I need to take a break for the evening to keep from physically bricking it into a wall. BTW, my reasoning for trying to S-Off was to use writecid and completely circumvent the signature errors. Maybe it was an okay idea, maybe it wasn't, but it didn't work so that's all that counts
I will try the official HTC RUU exe tomorrow when I have access to a win7 box but after that I really am out of ideas. I do seriously appreciate the help thus far and will greatly appreciate any more! Thank you!
1. Get rid of that Hansoon's toolkit, don't use it
2. Get the correct files from : http://forum.xda-developers.com/showthread.php?t=2729173
a- Sprint_HTC_One_M8_HK_4.20.654.10_RUU (exe)
or
b- 0P6BIMG_Sprint_HTC_One_M8_Harman_4.20.654.10_RUU.zip (zip)
3. Get the htc_fastboot.exe from @EddyOS thread : http://forum.xda-developers.com/showthread.php?t=2735235
You have three options here (all of this need a relocked bootloader, which you already have)
(Note : not sure whether this still valid on newer RUU, use USB 2.0 on your PC regardless Win 7, Win 8.1 or Win 10)
Option 1: Run the RUU.exe
a- relock bootloader
b- boot to bootloader/fastboot usb mode
c- Right click the RUU.exe and select run as Administrator
Option 2: Use the RUU.zip
a- rename the long RUU.zip name to RUU.zip (easier for you to follow commands)
b- relock bootloader
c- use the htc-fastboot.exe instead of the regular fastboot.exe
b- boot to bootloader/fastboot usb mode
c- run below commands
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
Option 3 : Try the above 2 options first, keep this option 3 later
dommiboy said:
In a final act of desperation for the night I tried to S-off with firewater which I pulled from web archive. I was able to push the file to the device, I had root permissions, I THINK I was able to chmod the file, however when I tried to run the file it just said not found. When I cd into the directory it's nowhere to be found?? I have no idea what happened there.
Click to expand...
Click to collapse
firewater was discontinued in December. Its an online service, and won't work now that the dev has stopped supporting it.
---------- Post added at 10:34 AM ---------- Previous post was at 10:32 AM ----------
ckpv5 said:
(Note : not sure whether this still valid on newer RUU, use USB 2.0 on your PC regardless Win 7, Win 8.1 or Win 10)
Click to expand...
Click to collapse
AFAIK, USB 3.0 still indeed plays havoc with RUUs and fastboot. But I don't think it would cause the RUU program to stop at terms and conditions, it would probably get stuck at trying to communicate with the device.
Suspect its a Win8 issue.
redpoint73 said:
Suspect its a Win8 issue.
Click to expand...
Click to collapse
I have no problem running RUU with my Win 8.1 64-bit, the only thing is my USB ports are all 2.0
and some Win 8.1 can't detect device when in fastboot mode but that easily can be fixed with a reg file (no need all those 3rd party drivers)
I have issues running RUUs, but both mine are USB 3.0 - but the issue I have is it not even running past the T&Cs. It extracts the files and then does nothing. Windows 7 Pro 64-bit at work works fine
Fastboot works fine (never had an issue with Windows 8.1 Pro), though, and I can flash RUU ZIPs without issue
ckpv5 said:
I have no problem running RUU with my Win 8.1 64-bit, the only thing is my USB ports are all 2.0
and some Win 8.1 can't detect device when in fastboot mode but that easily can be fixed with a reg file (no need all those 3rd party drivers)
Click to expand...
Click to collapse
The issue I've seen with Win8.1 is some C++ files not updated, so it might be build specific. A few users manually updated the appropriate files to get RUUs working.
Agree that checking the USB type (2.0 versus 3.0) is a good call. But I think that would not cause the RUU exe to crash at Terms & Conditions; but rather just get stuck trying to connect to the phone.
---------- Post added at 11:04 AM ---------- Previous post was at 11:02 AM ----------
EddyOS said:
I have issues running RUUs, but both mine are USB 3.0 - but the issue I have is it not even running past the T&Cs. It extracts the files and then does nothing. Windows 7 Pro 64-bit at work works fine
Click to expand...
Click to collapse
Right, that is the issue I've seen with USB 3.0.
Of course, it makes sense for the OP to look at (troubleshoot) every possibility (including USB type). Just trying another computer is probably the easiest fix, as long as they have access.
I'll say I was using USB 3.0 at work on the Win 7 machine, so I think it's just some PCs don't like the RUUs - proper annoying!
Randomly, thought I'd try again but run the RUU in Compatibility Mode as Windows 7 (as Administrator) and it worked fine
Related
Hi guys,
I am one of the 'lucky' ones with a broken USB-port. I currently have the MoDaCo custom ROM installed but I want to be able to install a generic ROM and return my phone for repairs.
Thus, I need to flash a generic ROM to my phone, and that's where my (n00b) problems start.
1: Flashing the original file simply by running the .exe file crashes. First, when describing my current FW version it says something about having 'too many images' or something. It tries to flash, but gets stuck while 'waiting for bootloader'. This runs to 100, and then gives me an error-message. Annoying!
2: As 1: doesn't work I want to flash directly from Fastboot. However, I cannot exract the two files needed to flash for some reason... I rename the RUU file from .exe to .zip, but only extract the boot.img file - the large .zip file returns an error, and nothing is extracted. I use winrar to extract, but have also tried 7zip.
3: If/when I succeed in extracting the files - where should the be put, when I execute the fastboot commands? On the SD-card or in the androidsdk/tools folder on the pc?
I really hope you can help me with the above. It's so annoying, so now I just want to return my device
Thanx for you help guys
Welcome in the club, come to here:
http://android.modaco.com/content/h...sues-with-usb-connectivity-etc-and-root-a2sd/
cause there we collect all infos about that issue
Thanks - but I'm following that constantly.
At the moment I just want to be able to flash the generic ROM, so I can send in my phone for repair. A rooted ROM is not going to be accepted.
Do you know the answer to my questions above?
There is a thread over at modaco on how to unroot your device. I used that to return mine to a generic rom before handing it back. It uses the fastboot option. I had the usb problem too.
Do you mean this thread:
http://android.modaco.com/content-page/307683/howto-unroot-your-htc-desire/page/40/
???
I can't see anywhere the talk about Fastboot option...
Just enter fastboot and run one of the stock roms from here:
http://forum.xda-developers.com/showthread.php?t=677513
unfortunately that's where my installation crashes. I go into Fastboot and just run the .exe files. That stops because it cannot find the bootloader or something.
I need a method that isn't just executing the .exe files, but pushing the boot.img and the .zip files from a terminal fastboot command!
what does fastboot say if you plugin your phone, start in fastboot, download the android sdk to your pc and run fastboot devices from commandline
JeckyllHavok said:
what does fastboot say if you plugin your phone, start in fastboot, download the android sdk to your pc and run fastboot devices from commandline
Click to expand...
Click to collapse
It can do that no problem - I can run the fastboot commands. I just don't know which to run - that's my problem
just run
fastboot devices
this shows if fastboot sees your phone. It should give you a letter number combi
BTW: if you are on vista or win7 try the exe several times, cause theese two OS'es aren't fast in detecting new devices
JeckyllHavok said:
BTW: if you are on vista or win7 try the exe several times, cause theese two OS'es aren't fast in detecting new devices
Click to expand...
Click to collapse
Run as administrator as well just in case.
abc27 said:
Run as administrator as well just in case.
Click to expand...
Click to collapse
I solved it - somehow.
I ran the unroot RUU file - again and again. And tried a few different USB-ports on my pc. I came gradually a little longer each time - and in the end - after maybe 5 attempts, it went all the way.
Yay - so now it's sent for repairs!
millen said:
I solved it - somehow.
I ran the unroot RUU file - again and again. And tried a few different USB-ports on my pc. I came gradually a little longer each time - and in the end - after maybe 5 attempts, it went all the way.
Yay - so now it's sent for repairs!
Click to expand...
Click to collapse
My just keep saying error 140 wrong bootloader version?? I have tried so many time now?? How did you do that? Do I have to get into fastboot to flash the exe file?
Hello,
To start off, I want to say that I DID search on this forum, for similar threads, and while I did find some, I couldn't find out how to do it.
My Phone:
HTC One X
S-ON
Rooted
Locked bootloader
ROM: Android Revolution HD
CID: HTC__E11
I flashed my current ROM a while ago, but I really cannot remember doing it and I deleted the backup I made before flashing (I always back up before flashing) because I thought I was running the stock ROM (without trouble) and I needed space.
What I want to do now, is get rid of EVERYTHING and just reset it to what it was when I first booted it, when that's all done, I want to root it again and unlock the bootloader.
The problem is that I can't find the appropriate RUU. I've been looking for it for a good while now, but I can't seem to find it.
I've downloaded OTA_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27-2.17.401.2_release_298985n1wwcwzs385c0bvz.zip from
htcruu.com/ index.php?dir=Endeavor (not allowed to put links here, sorry) and I put that in my SDCard directory.
When I tried to flash it (I don't know whether I am supposed to or not, but I only got a .zip and no .exe...) it did not work.
If you need the error, tell me and I'll do it again.
Regards,
Pim
If you can't find a ruu, you can use a stock nandroid backup. You can find a collection of them at general if I remember correctly.
Sent from my HTC One X
The ruu doesn't work because it's an OTA ....its just an update file ! Not the whole RUU
http://www.htcruu.com/securekey.php...Radio_5.1204.162.29_release_298897_signed.exe
this is the full RUU
Yes. Previous poster is correct. Download that file.
Do not put it on your sdcard.
Plug your phone into PC
Reboot into hboot by holding power & volume down for about 20seconds.
Press power button to go to fastboot
Open a cmd window and run fastboot oem lock to relock your bootloader
Run your ruu as administrator on your PC by right clicking and pressing open as administrator
Follow the instructions on your PC to flash the ruu
Sent from my HTC One X using xda app-developers app
Thanks a lot, but I'm still having trouble :s
I connect my phone to my pc via USB when I am looking at these options on my screen:
- HBOOT
- REBOOT
- REBOOT BOOTLOADER
- POWER DOWN
When I type "fastboot oem lock" in cmd, I get the following response:
" 'fastboot' is not recognized as internal or external command, operable program or batch file ".
And when I run the RUU (as administrator) I get "Error [170]: USB CONNECTION ERROR".
Regards,
Pim
Do you have HTC drivers installed and java SDK platform files ?
Have you ever used fastboot commands ?
Do you have a fastboot folder on the pc with fastboot/adb files in it ? When you connect the phone to the pc and put in bootloader menu you should see something like fastboot USB
Download this
http://db.tt/ldx3qOOU
And put the folder in c:\
So you have
C:\fastboot\ files in the folder
Open a dosprompt in that folder and type
Fastboot devices while the phone is still in bootloader menu If it comes up with your serial its good
Mr Hofs said:
Do you have HTC drivers installed and java SDK platform files ?
Have you ever used fastboot commands ?
Do you have a fastboot folder on the pc with fastboot/adb files in it ? When you connect the phone to the pc and put in bootloader menu you should see something like fastboot USB
Download this
db.tt/ldx3qOOU
And put the folder in c:\
So you have
C:\fastboot\ files in the folder
Open a dosprompt in that folder and type
Fastboot devices while the phone is still in bootloader menu If it comes up with your serial its good
Click to expand...
Click to collapse
Thanks.
I installed Windows to do this (Nothing worked on Mac, and things like this are usually easier on Windows than on Mac), and I forgot to install these things again.
I'll try this in a sec and I'll report here when I'm done.
Regards,
Pim
Mr Hofs said:
The ruu doesn't work because it's an OTA ....its just an update file ! Not the whole RUU
htcruu. com/securekey.phpfile=Endeavor/RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe
this is the full RUU
Click to expand...
Click to collapse
bagofcrap24 said:
Yes. Previous poster is correct. Download that file.
Do not put it on your sdcard.
Plug your phone into PC
Reboot into hboot by holding power & volume down for about 20seconds.
Press power button to go to fastboot
Open a cmd window and run fastboot oem lock to relock your bootloader
Run your ruu as administrator on your PC by right clicking and pressing open as administrator
Follow the instructions on your PC to flash the ruu
Click to expand...
Click to collapse
Hello,
First of all, I'd like to apologize for leaving so suddenly, but I had some other, more important, things on my mind.
Thanks for the link, but when I try to do that (and follow all the instructions I get on the screen), it all goes well, until just after "erasing user data", when I get the error as seen in the attachments.
When I started my phone, I had to fill in the basic questions, but I later found out that all my files were still there, while the apps themselves had been uninstalled...
I figured some general stuff out, and adb and fastboot are now *finally* working as they should.
Regards,
Pim
EDIT: Since I'm not quite sure whether or not the attachments are working, I uploaded them to imgur:
imgur. com/a/yMxph <= just remove the space before the between the "imgur." and "com/a/yMxph"
Well, I've just downloaded the correct RUU, but I'm currently getting error 155: unknown error...
I'm kinda clueless about what to do now...
Regards,
Pim
Download from the 2.17.401 ruu and try again.....otherwise flash back the stock recovery from the main version that you currently have
http://androidfiles.org/ruu/securek...Radio_2.1204.135.20_release_274900_signed.exe
So the stock recovery should be 1.29 based
Mr Hofs said:
Download from the 2.17.401 ruu and try again.....otherwise flash back the stock recovery from the main version that you currently have
http://androidfiles.org/ruu/securek...Radio_2.1204.135.20_release_274900_signed.exe
So the stock recovery should be 1.29 based
Click to expand...
Click to collapse
I used the same RUU I used before, but this time with relocked bootloader (forgot to relock that again), this time it worked!
I'm currently updating to Jelly Bean, and then I'll root it again etc. If I'm right, S-OFF is possible for the One X these days, right?
If so, would anyone know an easy and clear tutorial?
Regards,
Pim
Noone figured out the way to S-off for HOX yet, no.
BlueSingA said:
Noone figured out the way to S-off for HOX yet, no.
Click to expand...
Click to collapse
Sigh... well, thanks anyway.
Regards,
Pim
hello guys, i have a problem using RUU to revert my phone back to stock, i searched for a solution on xda forum and google for few hours now but nothing was exacly my problem. i am sorry if i missed vital information, this is my first android phone and i am still trying to learn and understand how it works.
CID 004 primou
i tried 2 different ruu versons for this CID. before using each i did the following steps
flashed boot from archive, flashed recovery from archive, relocked the bootloader.
-http://forum.xda-developers.com/showpost.php?p=30966084&postcount=114
first gave the error 155 due to the HBOOT being of a more recent version than the ruu (not sure if i understood well the error)
http://forum.xda-developers.com/showpost.php?p=30994089&postcount=121
on the second ruu *latest, i did same steps as before, unlocked bootloader, flashed boot, flashed recovery, relocked, but the ruu gives the error 170 ( device not connected) but i am 100% sure it is correctly connected into fastboot because it responds to One_V_All-In-One_Kit and it was recognized by the previous ruu.
i am using windows 8 pro and i have installed the ADB interface using the SDK google driver, this method to be exact http://forum.xda-developers.com/showthread.php?t=2088896
Can you run this script and let us know the result because CID 004 is different from 044.
See this post for the script : http://forum.xda-developers.com/showpost.php?p=36514545&postcount=15
And this post reason for error 170 : http://forum.xda-developers.com/showpost.php?p=36515756&postcount=22
hello, thanks for helping me,
i do not have any USB 3.0 ports on my PC, and the battery is at about 60%
the script you gave me told me this:
C:\Users\Draghici\Desktop\CID_checker_2>call fastboot getvar cid
cid: HTC__044
finished. total time: 0.001s
There is no need to flash boot.img and recovery.img, just a relocked bootloader is needed.
Just follow this step : http://forum.xda-developers.com/showpost.php?p=36515523&postcount=18
Most important is make sure your device is put on fastboot usb mode not hboot usb mode. (Another common error for usb connection problem when flashing RUU)
And use the latest RUU RUU_PRIMO_U_ICS_40A_hTC_Asia_WWE_2.22.707.2_Radio_ 20.76.30.0835U_3831.19.00.120_release_274703_signed.exe
ckpv5 said:
There is no need to flash boot.img and recovery.img, just a relocked bootloader is needed.
Just follow this step : http://forum.xda-developers.com/showpost.php?p=36515523&postcount=18
Most important is make sure your device is put on fastboot usb mode not hboot usb mode. (Another common error for usb connection problem when flashing RUU)
And use the latest RUU RUU_PRIMO_U_ICS_40A_hTC_Asia_WWE_2.22.707.2_Radio_ 20.76.30.0835U_3831.19.00.120_release_274703_signed.exe
Click to expand...
Click to collapse
sure i will do it right now, but i am 100% sure i relocked it correctly, the phone was in fastboot USB (red text) every time, and after each flash of boot/recovery, i relocked it, it told me in pink text in the recovery mode "RELOCKED"
but one more thing to add, when the RUU install failed on my phone screen it told me that the HBOOT version is too recent or something like that
hboot too recent if you flash 2.09 RUU (for hboot 1.17) but your hboot maybe 1.18 (2.22 RUU).
Unless there is a further update that I may missed, what hboot number is written on the bootloader ?
ckpv5 said:
hboot too recent if you flash 2.09 RUU (for hboot 1.17) but your hboot maybe 1.18 (2.22 RUU).
Unless there is a further update that I may missed, what hboot number is written on the bootloader ?
Click to expand...
Click to collapse
i have the 1.18, so i need to use
RUU_PRIMO_U_ICS_40A_hTC_Asia_WWE_2.22.707.2_Radio_20.76.30.0835U_3831.19.00.120_release_274703_signed
the one that gives me the error 170. i have 3 drivers provided by android SDK named
Android ADB Interface
Android Bootloader Interface
Android Composite Interface
each of them work with the 2.09 RUU and with all in one tool but none of them worked on 2.22 RUU.
You need HTC USB driver.
I'm using the driver from this HTC Sync Manager. It works nicely for Win 8 pro.
Install the HTC Sync Manager, it will install the necessary driver and you can remove the HTC Sync Manager later on but keep the driver.
http://www.htc.com/www/software/htc-sync-manager/
ckpv5 said:
You need HTC USB driver.
I'm using the driver from this HTC Sync Manager. It works nicely for Win 8 pro.
Install the HTC Sync Manager, it will install the necessary driver and you can remove the HTC Sync Manager later on but keep the driver.
http://www.htc.com/www/software/htc-sync-manager/
Click to expand...
Click to collapse
sorry for the late rly, I think I got some progress, I did the next steps.
went to device manager and uninstalled google android sdk driver, went to HTC Sync installation folder (I had it installed at first try but it did not pass my mind to show windows the location where it was installed, anyway...) and I installed the windows 7 driver, the windows 8 do not work for some reason, right now I can see the green progress bar on my phone so I guess it worked.
thanks a lot
I will ofc hit the "thanks" button on your posts here.
Yep...that's a good progress... it will be a successful flash
my bootloader show the following
***UNLOCKED***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.54.0000
RADIO-1.12.42.0731
OpenDSP-v31.120.274.0617
OS-1.10.605.8
eMMC-boot 2048MB
Aug 7 2013,16:38:58.0
after flashing the custom rom android revolution hd it said "flashed successfully please perform a full system reboot". when performed a reboot its stuck into a loop
into a panic situation right now cant use my phone please help guys
i am having recovery TWRP 2.7.0.0
Cant you just restore a backup or flash another rom? What is android revolution hd based on, jb, kk? Make sure your firmware matches the base of your rom. So if you flash a rom based on jb also flash jb firmware, if your on a kk rom, flash the kk firmware.
Also you say you have twrp 2.7.0.0? That is not a valid version for the verizon htc one.
cmlusco said:
Cant you just restore a backup or flash another rom? What is android revolution hd based on, jb, kk? Make sure your firmware matches the base of your rom. So if you flash a rom based on jb also flash jb firmware, if your on a kk rom, flash the kk firmware.
Also you say you have twrp 2.7.0.0? That is not a valid version for the verizon htc one.
Click to expand...
Click to collapse
sorry i just heard a lot about this ROM and made up my mind to use it permanently, but after flashing when i got the problem, I searched for it everywhere and found that it does not provide support for Verizon HTC one....feeling like a buge dumbbo right now as i didn't do a backup.
Can you please suggest me a good custom rom for verizon HTC One and/or also any way to return to the stock firmware?
what is the valid version of TWRP for Verizon HTC One?
Well there are tons of good roms in the develompent and original development threads. I my self prefer to just use rooted stock.
The latest twrp is 2.6.3.4 http://vzw1files.dyndns.org/RECOVERIES/twrp/openrecovery-twrp-2.6.3.4-m7vzw.img
If you wanted to you could do an ruu to get back to the stock firmware. http://vzw1files.dyndns.org/RUUs/
There is a 2.7.0.1. Also try ViperOne ROM.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button
Thats cool, i didnt realize a new twrp had been released.
I don't remember if it's an official build, but it's faster and smoother.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button
ruu gives error during flash
cmlusco said:
Well there are tons of good roms in the develompent and original development threads. I my self prefer to just use rooted stock.
The latest twrp is 2.6.3.4 http://vzw1files.dyndns.org/RECOVERIES/twrp/openrecovery-twrp-2.6.3.4-m7vzw.img
If you wanted to you could do an ruu to get back to the stock firmware. http://vzw1files.dyndns.org/RUUs/
Click to expand...
Click to collapse
i downloaded the 1.10.605.8/ version from the link you provided but this gives an error during flash
What was the error exactly?
cmlusco said:
What was the error exactly?
Click to expand...
Click to collapse
i used usb otg and copied the zip file to the sd card and then clicked on install and then selected the zip file and the swiped...the following comes written on the screen
Updatind partition details...
Full SELinux support is present.
E:Storage partition '//TWRP/BACKUPS/FA37KS92245
Installing '/sdcard/rom.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip '/sdcard/rom.zip'
Updating partition details...
Failed
i also wiped the cache and dalvik and tried again but same error
my mid is PN0731000
and currently cid is SuperCID but tried to flash the zip file with both VZW__001 and SuperCID and got same error
You do not flash ruus in recovery. You flash them using fastboot and a cmd prompt on your pc.
fasboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot
I'm having this same problem, but the issue I'm having is the fact that I'm running on Windows 8.1 x64 and it's not recognizing my fastboot. I'm getting the error 10 code for the device and I've tried updating the drivers and yes I do have driver verification off. Please help
cmlusco said:
You do not flash ruus in recovery. You flash them using fastboot and a cmd prompt on your pc.
fasboot oem rebootRUU
fastboot reboot
fastboot flash zip nameoffile.zip
Click to expand...
Click to collapse
after issuing the first command the reboots and a htc logo with black background is shown now after waiting for around 10 seconds i issue the second command aand here the problem arises as device enters into boot loop and restarts again and again, should i skip the second command or there's a way around?
My bad, i put those in the wrong order. It should be
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot
Sorry about that.
---------- Post added at 12:14 PM ---------- Previous post was at 12:06 PM ----------
thaunknownartist said:
I'm having this same problem, but the issue I'm having is the fact that I'm running on Windows 8.1 x64 and it's not recognizing my fastboot. I'm getting the error 10 code for the device and I've tried updating the drivers and yes I do have driver verification off. Please help
Click to expand...
Click to collapse
Try these drivers. They work for me on win 8.1 x86, but should also work for x64. http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
Also when was the last time you update the adb.exe and fastboot.exe files on your pc? http://vzw1files.dyndns.org/ADB/miniadb.zip
cmlusco said:
Try these drivers. They work for me on win 8.1 x86, but should also work for x64. http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
Also when was the last time you update the adb.exe and fastboot.exe files on your pc? http://vzw1files.dyndns.org/ADB/miniadb.zip
Click to expand...
Click to collapse
This is the code I just got. "This device cannot start. (Code 10)
A request for the USB BOS descriptor failed." and I updated both adb and the drivers.
cmlusco said:
My bad, i put those in the wrong order. It should be
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot
Sorry about that.
---------- Post added at 12:14 PM ---------- Previous post was at 12:06 PM ----------
Try these drivers. They work for me on win 8.1 x86, but should also work for x64. http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
Also when was the last time you update the adb.exe and fastboot.exe files on your pc? http://vzw1files.dyndns.org/ADB/miniadb.zip
Click to expand...
Click to collapse
thanx by the way skipping the second code worked....
thaunknownartist said:
This is the code I just got. "This device cannot start. (Code 10)
A request for the USB BOS descriptor failed." and I updated both adb and the drivers.
Click to expand...
Click to collapse
Im not sure. If you google "adb fastboot win 8.1 x64" there are tons of threads and youtube vidoes on how to get it working. Also make sure your using usb2.0 ports not usb3.0 ports on your pc.
cmlusco said:
Im not sure. If you google "adb fastboot win 8.1 x64" there are tons of threads and youtube vidoes on how to get it working. Also make sure your using usb2.0 ports not usb3.0 ports on your pc.
Click to expand...
Click to collapse
I've been doing this since 8am EST lol this is why I came to my forum. And my USB 3.0 is broke so I couldn't use it if I wanted too, I'm also running AMD not Intel so most of the fixes I see are for Intel or require USB 3.0 :/
All, I have an Unlocked, S-Off, Rooted HTC One M8 w/ Verizon that I was running Cyanogenmod 12.1, their latest snapshot.
Today the screen was black w/ the notification light blinking as I had a message. I couldn't get the screen to come on. I held in power + volume up until the phone rebooted. It rebooted to the boot loader. I told it to reboot & when it did the HTC splash screen didnt have the normal warnings that I'm used to seeing; warning something about developer options maybe; I can't remember. Anyways it just keeps booting to the bootloader & when I try to boot to recovery; it just reboots back into the bootloader. I've tried to flash to the lastest version of twrp via ADB on my pc, the flash is successful; but doesn't work when i try.
I've also ran...
fastboot erase cache
as i found that suggestion online.
Nothing is working for me. Any suggestions?
Thanks
AndroidJason said:
All, I have an Unlocked, S-Off, Rooted HTC One M8 w/ Verizon that I was running Cyanogenmod 12.1, their latest snapshot.
Today the screen was black w/ the notification light blinking as I had a message. I couldn't get the screen to come on. I held in power + volume up until the phone rebooted. It rebooted to the boot loader. I told it to reboot & when it did the HTC splash screen didnt have the normal warnings that I'm used to seeing; warning something about developer options maybe; I can't remember. Anyways it just keeps booting to the bootloader & when I try to boot to recovery; it just reboots back into the bootloader. I've tried to flash to the lastest version of twrp via ADB on my pc, the flash is successful; but doesn't work when i try.
I've also ran...
fastboot erase cache
as i found that suggestion online.
Nothing is working for me. Any suggestions?
Thanks
Click to expand...
Click to collapse
Download this RUU & install on cp, then power on & volume down to fastboot & run RUU
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Then reinstall twrp & rom of choice.
crackerjack1957 said:
Download this RUU & install on cp, then power on & volume down to fastboot & run RUU
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Then reinstall twrp & rom of choice.
Click to expand...
Click to collapse
Thanks, I will give this a try. Since it will take me back to stock, will I have to root again before installing TWRP & custom ROM?
crackerjack1957 said:
Download this RUU & install on cp, then power on & volume down to fastboot & run RUU
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Then reinstall twrp & rom of choice.
Click to expand...
Click to collapse
No luck. Even though I can run fastboot commands, the RUU exe package reboots the phone, then eventually fails at waiting for bootloader, even though the bootloader is ready. I get error 171 USB Connection Error, from the RUU exe on my pc.
Thoughts?
AndroidJason said:
No luck. Even though I can run fastboot commands, the RUU exe package reboots the phone, then eventually fails at waiting for bootloader, even though the bootloader is ready. I get error 171 USB Connection Error, from the RUU exe on my pc.
Thoughts?
Click to expand...
Click to collapse
Found an SD card that would fit & am now trying option 1 of the RUU.
Fingers crossed, updating just completed successful. Two steps were bypassed. Step 8, SBL1 (8) & Step 13 TP.
No change... Dang
Still same loop, boots to bootloader, selecting recovery reboots to bootloader.
Am I missing something?
AndroidJason said:
Found an SD card that would fit & am now trying option 1 of the RUU.
Fingers crossed, updating just completed successful. Two steps were bypassed. Step 8, SBL1 (8) & Step 13 TP.
No change... Dang
Still same loop, boots to bootloader, selecting recovery reboots to bootloader.
Am I missing something?
Click to expand...
Click to collapse
I guessing you have used this cp before for commands or flashing on m8.
What OS on cp?
Using USB2 port, not USB3?
HTC drivers installed?
ADB commands recognize m8?
---------- Post added 29th December 2015 at 12:01 AM ---------- Previous post was 28th December 2015 at 11:49 PM ----------
crackerjack1957 said:
I guessing you have used this cp before for commands or flashing on m8.
What OS on cp?
Using USB2 port, not USB3?
HTC drivers installed?
ADB commands recognize m8?
Click to expand...
Click to collapse
Also remember I had a problem with one, had to download and flash the L hboot from sdcard 1st then run RUU from pc.
Run L hboot the same way as option2.
Option2 did not work for me.
Good Luck!!!
crackerjack1957 said:
I guessing you have used this cp before for commands or flashing on m8.
What OS on cp?
Using USB2 port, not USB3?
HTC drivers installed?
ADB commands recognize m8?
---------- Post added 29th December 2015 at 12:01 AM ---------- Previous post was 28th December 2015 at 11:49 PM ----------
Also remember I had a problem with one, had to download and flash the L hboot from sdcard 1st then run RUU from pc.
Run L hboot the same way as option2.
Option2 did not work for me.
Good Luck!!!
Click to expand...
Click to collapse
This is the first time for me using a computer to flash my m8 or any other phone. I've always rooted, unlocked bootloader & then used TWRP.
OS on pc is Windows 7.
USB 2
HTC Drivers are installed
Im not sure is ADB commands work. I can get the Fastboot commands to work.
Nothing is listed after I run ADB Devices
I do get a device when I run fastboot devices.
The L hboot is an image, did you mean to say run it the same way as option 1?
AndroidJason said:
This is the first time for me using a computer to flash my m8 or any other phone. I've always rooted, unlocked bootloader & then used TWRP.
OS on pc is Windows 7.
USB 2
HTC Drivers are installed
Im not sure is ADB commands work. I can get the Fastboot commands to work.
Nothing is listed after I run ADB Devices
I do get a device when I run fastboot devices.
The L hboot is an image, did you mean to say run it the same way as option 1?
Click to expand...
Click to collapse
Yes, my bad, got option 1 & 2 mixed from memory
crackerjack1957 said:
Yes, my bad, got option 1 & 2 mixed from memory
Click to expand...
Click to collapse
Ok, so i ran the L hboot by renaming it & putting on an SD card, option 1. That worked fine.
Powered off.
Ran the RUU by renaming it & putting on an SD card, option 1. That worked and had the same two bypasses as before.
Rebooted & pulled out the SD card, but sadly; same results.
I think Im going to bed, its late here on the East Coast.
I'll check back in the morning. Thank you for your continuing help.
AndroidJason said:
Ok, so i ran the L hboot by renaming it & putting on an SD card, option 1. That worked fine.
Powered off.
Ran the RUU by renaming it & putting on an SD card, option 1. That worked and had the same two bypasses as before.
Rebooted & pulled out the SD card, but sadly; same results.
I think Im going to bed, its late here on the East Coast.
I'll check back in the morning. Thank you for your continuing help.
Click to expand...
Click to collapse
Sorry it did not work for you, maybe try the L hboot again & run RUU from pc.
If that does not work I'm out of ideas, maybe someone else could give some suggestions.
crackerjack1957 said:
Sorry it did not work for you, maybe try the L hboot again & run RUU from pc.
If that does not work I'm out of ideas, maybe someone else could give some suggestions.
Click to expand...
Click to collapse
Still up, wanted to give you time to respond.
I can't get the RUU update to run from pc, so it looks like this could be a dead end for me. Thank you again for trying.
I hate to get a new phone, none of the new Verizon phones can be rooted or an unlocked bootloader.
Can't get the new Nexus phones as we purchase directly through Verizon & not Google. (this is my company phone & HAS to be purchased through Verizon)
I'll retrace some steps in the morning.
AndroidJason said:
No luck. Even though I can run fastboot commands, the RUU exe package reboots the phone, then eventually fails at waiting for bootloader, even though the bootloader is ready. I get error 171 USB Connection Error, from the RUU exe on my pc.
Thoughts?
Click to expand...
Click to collapse
Looked back at the error you were getting trying to flash ruu with pc.
I'm not going to try to tell you to do the sdcard method because that did not work for me.
Here is a link that worked for some, even though this is not for the htc m8.
Think you may need to uninstall htc manager & clean with cc cleaner & reinstall.
Also try re downloading ruu incase it got corrupt.
http://androidforums.com/threads/ruu-error-170-171-solution-for-windows-7.161463/
---------- Post added at 10:14 AM ---------- Previous post was at 10:04 AM ----------
Remove Htc drivers in win7 program uninstaller also along with HTC sync then run cc cleaner.
Reinstall HTC sync then uninstall leaving drivers only, this is how my pc is setup & working.
http://www.htc.com/us/software/htc-sync-manager/
https://www.piriform.com/ccleaner
crackerjack1957 said:
Looked back at the error you were getting trying to flash ruu with pc.
I'm not going to try to tell you to do the sdcard method because that did not work for me.
Here is a link that worked for some, even though this is not for the htc m8.
Think you may need to uninstall htc manager & clean with cc cleaner & reinstall.
Also try re downloading ruu incase it got corrupt.
http://androidforums.com/threads/ruu-error-170-171-solution-for-windows-7.161463/
---------- Post added at 10:14 AM ---------- Previous post was at 10:04 AM ----------
Remove Htc drivers in win7 program uninstaller also along with HTC sync then run cc cleaner.
Reinstall HTC sync then uninstall leaving drivers only, this is how my pc is setup & working.
http://www.htc.com/us/software/htc-sync-manager/
https://www.piriform.com/ccleaner
Click to expand...
Click to collapse
Thanks will do, I'm actually trying to use a complete different computer as we speak. Will update the results.
AndroidJason said:
Thanks will do, I'm actually trying to use a complete different computer as we speak. Will update the results.
Click to expand...
Click to collapse
Same results from another pc (which had previously installed HTC drivers) I am now trying the suggestions from the last link you provided w/ uninstalling HTC software/drivers & running cc cleaner program.
AndroidJason said:
Same results from another pc (which had previously installed HTC drivers) I am now trying the suggestions from the last link you provided w/ uninstalling HTC software/drivers & running cc cleaner program.
Click to expand...
Click to collapse
Don't forget to uninstall htc sync before doing anything with ruu, it may interfere, the drivers remain behind.
What about the usb cable you are using, is it a data cable that came with m8 or spare that mainly used for charging.
AndroidJason said:
Same results from another pc (which had previously installed HTC drivers) I am now trying the suggestions from the last link you provided w/ uninstalling HTC software/drivers & running cc cleaner program.
Click to expand...
Click to collapse
Still not working.
Followed all the instructions, re-downloaded the RUU. I've uninstalled the HTC sync & drivers; ran cc cleaner, rebooted, reinstalled HTC snyc & drivers.
I've even tried this on two different Windows 7 pc's. One I left the HTC Sync on, the other I uninstalled & just left the HTC drivers behind. (as one person suggested)
Should the RUU installer app say updated to version & then it instead of a version it list odd characters that I dont even know how to type on a keyboard?
I think I've got my first true brick.
crackerjack1957 said:
Don't forget to uninstall htc sync before doing anything with ruu, it may interfere, the drivers remain behind.
What about the usb cable you are using, is it a data cable that came with m8 or spare that mainly used for charging.
Click to expand...
Click to collapse
I will try another cable, I have a ton of these & just grabbed one; & thats the one I've been using.
AndroidJason said:
I will try another cable, I have a ton of these & just grabbed one; & thats the one I've been using.
Click to expand...
Click to collapse
Using a different cable, I get the same problem.
I dont think its the cable, because the RUU can read the current version of firmware thats on the phone, then issues the phone to reboot. Then the RUU app just sits & says waiting for bootloader.
AndroidJason said:
Using a different cable, I get the same problem.
I dont think its the cable, because the RUU can read the current version of firmware thats on the phone, then issues the phone to reboot. Then the RUU app just sits & says waiting for bootloader.
Click to expand...
Click to collapse
Grab this:http://forum.xda-developers.com/showthread.php?t=2588979
---------- Post added at 12:52 PM ---------- Previous post was at 12:40 PM ----------
Grab stagefright zip:http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUUish file and place in your working fastboot/adb directory. Boot your phone to fastboot mode and connect to PC. Issue the following commands.
fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
fastboot flash zip 0P6BIMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "fastboot reboot-bootloader" command and restart option 1 again.
example
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
---------- Post added at 01:03 PM ---------- Previous post was at 12:52 PM ----------
If that fails go here to reinstall firmware 1st (4.17.605.5):
---------- Post added at 01:06 PM ---------- Previous post was at 01:03 PM ----------
Instructions
Download firmware zip
reboot your phone to bootloader
Place your firmware zip in your fastboot folder
Open CMD terminal on pc in your file you fastboot from.
Plug phone into pc
In terminal first cmd you need is
Fastboot oem rebootRUU
fastboot flash zip nameofyourfile.zip
It should ask you to reflush immediately in your cmd terminal,when it does proceed to next cmd
fastboot flash zip nameofyourfile.zip
Once all is good on your end an your ready to reboot phone use this final cmd
Fastboot reboot-bootloader
crackerjack1957 said:
Grab this:http://forum.xda-developers.com/showthread.php?t=2588979
---------- Post added at 12:52 PM ---------- Previous post was at 12:40 PM ----------
Grab stagefright zip:http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUUish file and place in your working fastboot/adb directory. Boot your phone to fastboot mode and connect to PC. Issue the following commands.
fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
fastboot flash zip 0P6BIMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "fastboot reboot-bootloader" command and restart option 1 again.
example
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
---------- Post added at 01:03 PM ---------- Previous post was at 12:52 PM ----------
If that fails go here to reinstall firmware 1st (4.17.605.5):
---------- Post added at 01:06 PM ---------- Previous post was at 01:03 PM ----------
Instructions
Download firmware zip
reboot your phone to bootloader
Place your firmware zip in your fastboot folder
Open CMD terminal on pc in your file you fastboot from.
Plug phone into pc
In terminal first cmd you need is
Fastboot oem rebootRUU
fastboot flash zip nameofyourfile.zip
It should ask you to reflush immediately in your cmd terminal,when it does proceed to next cmd
fastboot flash zip nameofyourfile.zip
Once all is good on your end an your ready to reboot phone use this final cmd
Fastboot reboot-bootloader
Click to expand...
Click to collapse
I get the following when I attempt to flash using this method...
C:\adb>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1826414592 bytes
sending 'zip' (1683272 KB)...
OKAY [ 63.976s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 63.991s
My phone also doesnt do what is described by staying at an HTC splash screen; it just boots right to the bootloader like it always does.
I've seen that remote: not allowed trying some of my own method during this whole process; not sure what that means.