Update: I have the stock.img and need the stock zip file... please help that is all i need. i tried the stock RUU but for some reason my computer will not run the application and i don't know any other way to fix my phone other than adding the stock zip file to my phones sd card and installing it thru recovery.
Update: I fix my computer problem with the RUU not starting, it starts now and runs all the way thru then says it's the wrong one. I got the at&t ruu off the htc site.
UPDATE: I got my phone off of ebay, heres what the item was listed under.
SR HTC Desire 610 8GB Black AT&T Unlocked Any GSM 4G LTE Android Smartphone
Model: Desire 610
Bundled Items: 4G LTE May not be compatible with T-Mobile, Doesn't work with Verizon or Sprint
Contract: Without Contract
Lock Status: Network Unlocked
Operating System: Android
Unlock Status: Carrier Unlocked
Color: Black
SO... it's a AT&T Unlocked GSM phone? so what RUU do i need to use?
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I don't know exactly what all you need but here goes nothing.
I unlocked and rooted my phone a few nights ago using, http://forum.xda-developers.com/desire-610/general/info-htcdev-unlock-root-t2844323
also had TWRP recovery installed.
Yesterday i was playing around in recovery mode trying to clean up my phone and restore it to factory settings. I accidentally deleted my system.. and when i try go to reboot it says No OS Installed! Are you sure you wish to reboot?
So i rebooted to fastboot and clicked power down.. and when i try to reboot it, it gets stuck on the HTC start up screen untill my phone dies or i go thru all the trouble to take the battery out.
So i deleted the OS System, and can't boot my phone up. I can get to recovery and fastboot just fine tho.
Bigger problem is, before this happened i had to Factory Restore my computer, so i no longer have any of the files i had to download to unlock and root my phone.
Anyone know what i need to do to be able to use my phone again? I'd really rather not have to go back stock ROM but if it's the only choice i will.
Please help me fix this, I can't go without my phone and I really can't afford a new one right now.
Thank you...
Dawniebear
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
A3_UL PVT SHIP S_ON
HBOOT-3.19.0.0000
RADIO-1.101.1372.19.1121
OpenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1024MB
Aug 28 2015,16:24:59.0
Try to reboot recovery
Install CM11 or stock ATT ROM from xda.
Move it to device.
Flash in recovery!
If your computer won't detect the 610, put it on USB OTG and connect to phone and flash.
Good luck
magicstick5 said:
Try to reboot recovery
Install CM11 or stock ATT ROM from xda.
Move it to device.
Flash in recovery!
If your computer won't detect the 610, put it on USB OTG and connect to phone and flash.
Good luck
Click to expand...
Click to collapse
That's one of the first things i did.. and i don't know of any other option..
dawniebear said:
That's one of the first things i did.. and i don't know of any other option..
Click to expand...
Click to collapse
Well, then put one of the zip files on an SD card and put it in your phone, and then flash it in twrp, that's what I did when I did the exact same thing lol
dawniebear said:
That's one of the first things i did.. and i don't know of any other option..
Click to expand...
Click to collapse
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
A3_UL PVT SHIP S_ON
HBOOT-3.19.0.0000
RADIO-1.101.1372.19.1121
OpenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1024MB
Aug 28 2015,16:24:59.0
Well, looking at your 1st post(see exert pasted in above) you have somehow re-locked your bootloader. So the first thing you will have to do is go back through your emails and find the unlock_code.bin file that htcdev emailed you when you first unlocked it and use wndroid or fastboot to to unlock your bootloader again with that code. Recovery won't let you flash back anything while the bootloader is locked.
MiniBlu said:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
A3_UL PVT SHIP S_ON
HBOOT-3.19.0.0000
RADIO-1.101.1372.19.1121
OpenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1024MB
Aug 28 2015,16:24:59.0
Well, looking at your 1st post(see exert pasted in above) you have somehow re-locked your bootloader. So the first thing you will have to do is go back through your emails and find the unlock_code.bin file that htcdev emailed you when you first unlocked it and use wndroid or fastboot to to unlock your bootloader again with that code. Recovery won't let you flash back anything while the bootloader is locked.
Click to expand...
Click to collapse
Oh that's why, didn't even see that it said relived, looked real quick, thought it said unlocked, whoops lol
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
MGfusion said:
Oh that's why, didn't even see that it said relived, looked real quick, thought it said unlocked, whoops lol
Click to expand...
Click to collapse
Relocked, not relived
Every tutorial i have tried has said to relock bootloader before using the ruu. oh btw i have fixed the ruu not opening problem but it ran all the way thru then said it was the wrong one. I don't understand, my desire is at&t and i got the at&t ruu from the htc page.
Do i need to go s-off?
Kay
Unlock bootloader again and flash it
Easy
magicstick5 said:
Kay
Unlock bootloader again and flash it
Easy
Click to expand...
Click to collapse
unlock and flash what?
Made a mistake guys, its a AT&T Unlocked GSM phone, so what RUU would i use?
dawniebear said:
unlock and flash what?
Click to expand...
Click to collapse
Since you somehow relocked bootloader, unlock it using windroid.
Then transfer cm11 or stock ATT ROM and flash in recovery
magicstick5 said:
Since you somehow relocked bootloader, unlock it using windroid.
Then transfer cm11 or stock ATT ROM and flash in recovery
Click to expand...
Click to collapse
I know how to unlock my bootloader thru fastboot, but my phone is a at&t unlocked gsm phone what rom do i use? and where to find it.
dawniebear said:
unlock and flash what?
Click to expand...
Click to collapse
follow this step by step
1 - Use windroid tool found here and your unlock_code.bin file to unlock your bootloader.
2 - If you don't still have TWRP installed use the above mentioned windroid tool to install TWRP.
3 - reboot to recovery (TWRP).
4 - Select the "WIPE" button in TWRP and swipe to do a factory reset.
5 - Return to main menu in TWRP and use the "INSTALL" button to install CM11 from here. or the "RESTORE" button to install the stock at&t backup from here.
6 - When instaling 1 of the above follow all instuction from the thread you get the rom from and the then once flashed hit the "WIPE DALVIC AND CACHE" button then reboot.
7 - You will now have a fresh intalation of the rom you chose so just set it up and enjoy.
MiniBlu said:
follow this step by step
1 - Use windroid tool found here and your unlock_code.bin file to unlock your bootloader.
2 - If you don't still have TWRP installed use the above mentioned windroid tool to install TWRP.
3 - reboot to recovery (TWRP).
4 - Select the "WIPE" button in TWRP and swipe to do a factory reset.
5 - Return to main menu in TWRP and use the "INSTALL" button to install CM11 from here. or the "RESTORE" button to install the stock at&t backup from here.
6 - When instaling 1 of the above follow all instuction from the thread you get the rom from and the then once flashed hit the "WIPE DALVIC AND CACHE" button then reboot.
7 - You will now have a fresh intalation of the rom you chose so just set it up and enjoy.
Click to expand...
Click to collapse
Sorry for the late reply i was having some driver issues on my computer, had to wait to borrow a friends. This worked PERFECTLY!! I can't thank you enough!
i have the exact problem my bootloader is unlocked and installed twrp but everytime i try to install something it says failed to mount system, data, cache PLEASE i need some help
sif5812 said:
i have the exact problem my bootloader is unlocked and installed twrp but everytime i try to install something it says failed to mount system, data, cache PLEASE i need some help
Click to expand...
Click to collapse
install older version of twrp. The latest ones don't work. I have attached an older version I had floating around, just unzip it then falsh the image with fastboot.
could you please tell how can i do it,, if its not too much trouble, i installed twrp via windroid, im completely new in this, and i could use some help
sif5812 said:
could you please tell how can i do it,, if its not too much trouble, i installed twrp via windroid, im completely new in this, and i could use some help
Click to expand...
Click to collapse
Just use windroid. First unzip the file I attached. Connect phone to PC. Start windroid. At top of windroid select COMMANDS. FLASH. FLASH RECOVERY. It will open an explorer window, just navigate to where you unzipped the file I sent you and select it. It will then flash the recovery. Once finished reboot to recovery.
Good day sorry to bother you again i tried to do that but now i cant enter recovery mode twrp, i click there but only goes to htc logo for a sec then goes back to fast boot
http://imgur.com/NMe0m0I
http://imgur.com/R8KmRBS
here are some pictures of my screen
Related
so i went to switch out my battery and when i turned the phone back on it vibrated and displayed the white htc screen, then went black for a second and then stays on the white htc screen forever! Im a total noob when it comes to all the technical stuff about RUU's Kernels Roms and whatnot. I can get to bootloader, but i tried to do factory reset and it showed a green circle with a loading bar but then it changed into a red triangle with an exclamation. I tried flashing amon ra recovery but it doesnt work, although TWRP works. While in TWRP though, whenever i try to flash a zip file, it fails and says something like E:failed to mount /cache E:failed to mount /system E:failed to mount /data. Please help me i need this phone working to help me at my job. If someone can walk me through what i need to do i would REALLLYYYY appreciate it. Like i said though, i am a noob so i need realy stupified instructions lol. Thanks
just wanted to note that right now when i go to bootloader it says
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
Vigor PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
kverduin said:
just wanted to note that right now when i go to bootloader it says
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
Vigor PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Click to expand...
Click to collapse
First you should go to shipped-roms.com and download the vigor ics ruu.exe, the rezound downloads there are under vigor . Plug your phone into your computer and from hboot highlight fastboot press power and run the .exe file from your computer and follow the on screen instructions, this will return your phone to full stock ics. Make sure you download the vigor ics ruu.exe as the GB ruu will not work with s-on.
You can also download this: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ it's the latest ruu it'll update your hboot, stock recovery, rom, and radios, to latest stock. Just download, rename the zip file to PH98IMG (don't include .zip it is a zip file it'll add it on its own in hboot) put it on your sd card, not in a folder just on. Put it back in your phone and boot to bootloader and runn the update, when it powers off. Run it again. (As it has to update the hboot to 2.27 first)Then you'll be on the stock latest. Then root and Rom from there. Of you need help pm me for my gtalk and I could walk you thru it..
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
Sounds like no boot.img
GrayTheWolf said:
Sounds like no boot.img
Click to expand...
Click to collapse
Its because of the security warning. The phone wont boot if it says that he has to run an RUU
Sent from my HTC Droid Incredible
Same exact problem. Installing zip now, god i hope this works!!
So my screen is the exact same, i tried to flash a kernal for not only wrong phone but wrong carrier too. Anyways no OS, when i try to flash either of the ways you have explained they both dont work. When i put it on the sd card as PH98IMG it looks like it loads it in the upper right then thats it. regular bootload screen after that nothing happens. try to load it by opening the application after im plugged in as fasboot usb and the program says Install script setup launcher has stopped working. I have been able to flash liquids rom and looks as if it is booting but waited 24 min and nothing happpend just stayed on boot screen. So im just trying to get back to RUU then work from there.
mrcorson said:
So my screen is the exact same, i tried to flash a kernal for not only wrong phone but wrong carrier too. Anyways no OS, when i try to flash either of the ways you have explained they both dont work. When i put it on the sd card as PH98IMG it looks like it loads it in the upper right then thats it. regular bootload screen after that nothing happens. try to load it by opening the application after im plugged in as fasboot usb and the program says Install script setup launcher has stopped working. I have been able to flash liquids rom and looks as if it is booting but waited 24 min and nothing happpend just stayed on boot screen. So im just trying to get back to RUU then work from there.
Click to expand...
Click to collapse
You need to extract the boot.IMG from liquid Rom and rename it ph98img and put that on your sd card or in the folder with adb and fastboot flash it using fastboot flash boot boot.img
Sent from my ADR6425LVW using xda app-developers app
Also wipe cache and dalvik cache in recovery immediately after doing this
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
I ended up flashing liquidsmooth rom in recovery then had to wipe factory data reset, then i could wipe dalvick cache then when i rebooted it actually booted the rom and I LOVE IT. Still having some issues tho.
Still cant get my computer to talk to my phone when in fastboot usb i cant get any devices when i do "adb devices" cmd.
It says devices listed below but no devices.
Also im still stuck on TWRP 2.2 and I cant my 2.6 to flash in recovery. - Still troubleshooting this and might get it in a bit.
Thanks for the suggestions!!!
mrcorson said:
I ended up flashing liquidsmooth rom in recovery then had to wipe factory data reset, then i could wipe dalvick cache then when i rebooted it actually booted the rom and I LOVE IT. Still having some issues tho.
Still cant get my computer to talk to my phone when in fastboot usb i cant get any devices when i do "adb devices" cmd.
It says devices listed below but no devices.
Also im still stuck on TWRP 2.2 and I cant my 2.6 to flash in recovery. - Still troubleshooting this and might get it in a bit.
Thanks for the suggestions!!!
Click to expand...
Click to collapse
ooooh older stuff ick lol...do you have your htc sync drivers installed....what os are you on? are you s-on? what hboot you on? you need to be wiping before rom install and not after....are your issues pertaining to random reboots?
REV3NT3CH said:
ooooh older stuff ick lol...do you have your htc sync drivers installed....what os are you on? are you s-on? what hboot you on? you need to be wiping before rom install and not after....are your issues pertaining to random reboots?
Click to expand...
Click to collapse
Yes i did reinstall my HTC Sync drivers, I have been wipining factory reset, cache, system, dalvick cache before i flash a new rom. I am S-On. Havent really determined a reason to go s-off yet, i am messing up my phone good enough with this let alone a paperclip. no problem with random reboots. I finally decided to go to a custom rom bc i was sick of my phone rebooting for OTA updates then being late for work. So the 3 roms i have now tried are Liquid smooth which i liked but i couldnt get mms messages to show up on phone. Also it wouldnt change from silent to a beep for text message notifications. i could select it but it would stay as silent. So.... I flashed ViperRezROm which i just didnt like the look and theme. So i finally flashed Cyanogen ROM and come to find out its the same kernal as Liquid smooth so it looks the same and I like that but I still cant change the notification from silent to a beep for text messages. So i never know when i get a text.
Still working on trying to flash a newer version of TWRP.
Then this time flashing I tried to titanium backup and went to load my backup and it cant find it.... WTF
UGH... Learning so much with this stuff. just taking alot of patience.
Thanks again for yalls support, I love this forum.
Mike
BTW just to note...if your bootloader is locked fastboot flash methods will not work 90 percent of the time...if you flashed liquid 3.0 that's more than likely your problem with mms as that is a beta...but on more recent 4.3 builds mms is fixed...and no its not the same kernel...just similar source code...liquid 2.9 does not have this mms issue...any random reboots on 4.2 are caused by min frequency not set right at 384 mhz and using amon ra to flash or not doing a proper clean flash....I do recommend s-off as it will make life much easier for you for modding things or flashing custom zips and for future flashing back to full stock if needed as its not possible while s-on...you can always pm me for help as I've yet to run into an error I can't fix unless posted in op caused by source
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
There is a few good reasons to S-Off.
1.No need to fastboot flash kernels
2.can RUU if needed
3.can flash recovery updates (cwm, twrp) as ph98img zips
4. Can keep bootloader ***locked***
5. No more ***tampered*** tag after you RUU
Scenario: you are out and about (or a computer isn't handy) somehow you are in an infinite bootloop. You nandroid restore. But it is something on boot partition. Only way to fix this while S-On is fastboot flashing a boot.img, but if you were S-Off, you would have restored the boot image from the nandroid.
Edit: added 5th reason
Sent from my ADR6425LVW using xda app-developers app
Uzephi said:
There is a few good reasons to S-Off.
1.No need to fastboot flash kernels
2.can RUU if needed
3.can flash recovery updates (cwm, twrp) as ph98img zips
4. Can keep bootloader ***locked***
5. No more ***tampered*** tag after you RUU
Click to expand...
Click to collapse
I finally went S-OFF to help another user get step by step to restore to fully locked and stock ruu. I decided to leave it S-OFF. It's so nice to be able to just load a rom and not have to do anything else (other than wiping). It makes changing/upgrading rom's a breeze.
I highly recommend it. It seems scary, but once you have done it once, you will not go back.
But be warned, never go back to S-ON on a non-HTC hboot... you will hard brick your device. That is the only real threat I've heard about... if you never go back to S-ON, then you have absolutely nothing to worry about. Just about any error can be fixed except for going s-on on a non-ruu hboot.
Thanks
molson8045 said:
You need to extract the boot.IMG from liquid Rom and rename it ph98img and put that on your sd card or in the folder with adb and fastboot flash it using fastboot flash boot boot.img
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
You saved me! That worked like a charm.
please help
Hi guys
Im have that problem in my htc rezound i seen the above comments but i couldnt able to understand so please tell the procedure one by one please pleasr..........
parthis said:
Hi guys
Im have that problem in my htc rezound i seen the above comments but i couldnt able to understand so please tell the procedure one by one please pleasr..........
Click to expand...
Click to collapse
If English is not your first language I apologise.
Otherwise, you need to be more specific and use full sentences.
GrayBoltWolf said:
Sounds like no boot.img
Click to expand...
Click to collapse
you were dead on accurate regarding my problem. Your post helped me revive an all but dead rezound!! Thanks man!!
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
silenthatred said:
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
Click to expand...
Click to collapse
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
silenthatred said:
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
Click to expand...
Click to collapse
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
silenthatred said:
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
Click to expand...
Click to collapse
This happens sometimes if you have a custom bootloader installed when you flash the RUU. Just cancel the Windows task and restart it and you should be fine.
ramjet73
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
silenthatred said:
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
Click to expand...
Click to collapse
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
Click to expand...
Click to collapse
Why is this? Is there not a full RUU for the latest version?
ramjet73 said:
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
silenthatred said:
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
Click to expand...
Click to collapse
Does it still say ** LOCKED ** Or does it say ** UNLOCKED ** now?
Unknownforce said:
Why is this? Is there not a full RUU for the latest version?
Click to expand...
Click to collapse
No. Virgin Mobile released an OTA update in November but there's no RUU that corresponds to it available yet. Fortunately, the bootloader version didn't change so the original RUU can be flashed with S-ON if the mainver is set low, but you need to be unlocked and rooted already to flash the zip file that does that.
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
Click to expand...
Click to collapse
That would be a problem for him then. I don't know of anyway to flash the RUU with S-ON after the OTA has been installed if the bootloader is actually locked and he can't unlock it.
ramjet73
Yeah, not looking good. Thanks for the help though!
Hello.
I have an Internation HTC One X+ on the Vodafone UK Network.
Few months ago I unlocked bootloader, rooted the phone and installed Lloir's CM mod for it with no problems... Until I tried to update to the newest version of the rom.
Google play store kept consistently crashing despite me reflashing google apps, clearing caches etc basically everything you guys had previously told others to do on here.
So I tried to go back to a previous backup but ran into similar difficulties.
This is when I thought **** it I'll go back to stock....
Long story short my phone is now stuck in a version of CM where certain apps = playstore included no longer function.
I tried to install a RUU to no avail, it errors 170 half way through installation.
I cannot follow the previous steps around rooting and installing roms as for some reason my phone shows as totally empty on my PC, no folders no nothing.
Errrm what else.
So yeah I'm totally stuck to be fair all I wanna do is go back stock now and get OTA updates and be a normal user but I can't even do that. Pleeeeeeeeeeeease help. I know people like me are a massive annoyance but I just want my phone back
Thanks
run into bootloader > use hasoon toolkit to re-lock bootloader > restart > boot in bootloader again and check its re-locked > now u can flash the RUU with no errors
tell me what u get so i can help u more
Mr.Boombastic said:
run into bootloader > use hasoon toolkit to re-lock bootloader > restart > boot in bootloader again and check its re-locked > now u can flash the RUU with no errors
tell me what u get so i can help u more
Click to expand...
Click to collapse
It errors, I'll have to try it again later and replicate the error so I can give you the exact problem..
However I've been tinkering further and now I'm completely romless.
Thanks for your offer of help, I'll post info about the RUU error as soon as I get chance to get back at my computer.
Long and short of it is it says that I'm not using the right RUU for my phone but I am...>_<
astephens1 said:
Long and short of it is it says that I'm not using the right RUU for my phone but I am...>_<
Click to expand...
Click to collapse
what version of hboot have you got? if it is 1.40 then there is no RUU for you device at this time.
you could try installing twrp recovery and "sideloading" a ROM on there, then install the boot.img and hopefully you should be sorted
cheers
Start in bootloader and give us information you get
Sent from my HTC One X+ using Tapatalk 4
*** UNLOCKED ***
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-3.1204.168.32
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
I've managed to get back into a half-working phone running CM10, play store still won't work so im still kinda stuck and unable to do anything else really! doh.
And it says no external storage available when I go to gallery/camera etc anything that might need to use my phone's storage...
astephens1 said:
*** UNLOCKED ***
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-3.1204.168.32
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
Click to expand...
Click to collapse
this should do the job of going back to stock
you will have to relock your boot loader, you can use hansoon toolkit if you are not sure
then you can click this link here:
http://www.feartech.co.uk/rom/RUU_E...Radio_3.1204.167.31_release_289473_signed.exe
i have uploaded it on my website, this will wipe everything of your phone and will take it back to stock then you can do the OTA's
thanks
Lee
leefear said:
this should do the job of going back to stock
you will have to relock your boot loader, you can use hansoon toolkit if you are not sure
then you can click this link here:
http://www.feartech.co.uk/rom/RUU_E...Radio_3.1204.167.31_release_289473_signed.exe
i have uploaded it on my website, this will wipe everything of your phone and will take it back to stock then you can do the OTA's
thanks
Lee
Click to expand...
Click to collapse
Thats the one that I ran but it errors half way through
astephens1 said:
Thats the one that I ran but it errors half way through
Click to expand...
Click to collapse
i have used the same ruu and it has worked for me
are you sure you have relocked your bootloader before installing this?
I'll give it one more go and post the results/error.
I know this is what I need to work it just won't!
astephens1 said:
I'll give it one more go and post the results/error.
I know this is what I need to work it just won't!
Click to expand...
Click to collapse
try another usb port, like the ones at the back of the pc, don't use extensions
make sure your drivers are up to date as well, that may help
leefear said:
try another usb port, like the ones at the back of the pc, don't use extensions
make sure your drivers are up to date as well, that may help
Click to expand...
Click to collapse
RUU never gone solve his problem , he got ( HBOOT-1.72.0000 )
RUU only work with ( hboot-1.35.0000)
ERROR [158]: IMAGE ERROR
The ROM Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Click 'Exit' to quit.
Do you think there is any way I'll ever have a working phone again?
Or is it borked forever and I should just get a new phone :/
download this toolkit (Hasoon2000 toolkit ) from this link [ http://d-h.st/Lbx ]
since u already unlocked your bootloader just flash the recovery
next
download ROM in this thread (Installation guide in post #3) http://forum.xda-developers.com/showthread.php?t=2067325
Easy but Kill 2 hours downloading and flashing
You never flashed the updated boot.img for CM did you?
Sent from my enrc2b using Tapatalk 4
astephens1 said:
Do you think there is any way I'll ever have a working phone again?
Or is it borked forever and I should just get a new phone :/
Click to expand...
Click to collapse
just been looking around mate, i am using insertcoin with sense 5
install twrp, wipe everything, fastboot flash boot boot.img provided from download
sideload or push rom, install and all hopefully should be good
or copy rom to sdcard go to bootloader and flash the boot.img, then go to recovery install rom and wipe all when prompted in installation
let us know what happens
sorry i can't be more help
astephens1 said:
Do you think there is any way I'll ever have a working phone again?
Or is it borked forever and I should just get a new phone :/
Click to expand...
Click to collapse
u can run bootloader So you HOX+ didn't [ borked ] yet
Hi everyone, here is my last attempt to save my desire x.
First : i’m not completely a newbee, i’m use to the devlopment with android i’m owing a TF700 and xperia mini pro, both rooted and running under custom rom.
My problem : This summer my phone used to switched off and on again, once per day. One day, it switched off and i couldn’t start it again (stuck on HTC logo). I did the first operation which came in my mind « factory reset by the bootlader » , same problem !
My second problem, i bought the phone in India were i was studying, HTC France explained me that i should return to the shop where i bought the phone to fix it up…..hahahahaa !
I gave up, now i want fix it by myself
How my phone is actually
HBOOT : 1.24
Access to the bootloader possible
Fastboot command works
Rooted with WIndroid
Why not flashing ?
I tried…First, i rooted sucessfully my phone, installed a ICS recovery but no a single one is working, can’t wipe any cache, ect…and the zip installation failed with CWM, TWRP, Philz….
I get these messages for all recoveries :
- Can’t mount eMMC
- Can’t mount cache
Any attempt to mount the eMMC and the cache is a fail, though the Ext-sd card can be mounted.
I tried the RUU (asia) , I relocked the bootloader with windroid, the RUU failed, it sent the files, and failed at the « signature update », the code error is 155.
Everything which is cited is what i did today, I did many other operations this summer but i couldn’t precisely describe it, i just know that i did a lot, and i’m today without any other solution….thus here is my post !
Thanks for your answers !
hugiz said:
Hi everyone, here is my last attempt to save my desire x.
First : i’m not completely a newbee, i’m use to the devlopment with android i’m owing a TF700 and xperia mini pro, both rooted and running under custom rom.
My problem : This summer my phone used to switched off and on again, once per day. One day, it switched off and i couldn’t start it again (stuck on HTC logo). I did the first operation which came in my mind « factory reset by the bootlader » , same problem !
My second problem, i bought the phone in India were i was studying, HTC France explained me that i should return to the shop where i bought the phone to fix it up…..hahahahaa !
I gave up, now i want fix it by myself
How my phone is actually
HBOOT : 1.24
Access to the bootloader possible
Fastboot command works
Rooted with WIndroid
Why not flashing ?
I tried…First, i rooted sucessfully my phone, installed a ICS recovery but no a single one is working, can’t wipe any cache, ect…and the zip installation failed with CWM, TWRP, Philz….
I get these messages for all recoveries :
- Can’t mount eMMC
- Can’t mount cache
Any attempt to mount the eMMC and the cache is a fail, though the Ext-sd card can be mounted.
I tried the RUU (asia) , I relocked the bootloader with windroid, the RUU failed, it sent the files, and failed at the « signature update », the code error is 155.
Everything which is cited is what i did today, I did many other operations this summer but i couldn’t precisely describe it, i just know that i did a lot, and i’m today without any other solution….thus here is my post !
Thanks for your answers !
Click to expand...
Click to collapse
Have you tried to wipe cache in fastboot? Use the command: ''fastboot erase cache''
Try to flash a Hboot 1.24 recovery after that and factory reset the phone. Then flash the rom of your choice (for 1.24 hboot of course)
So, I used the clear cache tool of the WinDroid, i flashed the TWRP 2.5.0.0 recovery for ICS, reset the phone, the same, can't clear any cache !
hugiz said:
So, I used the clear cache tool of the WinDroid, i flashed the TWRP 2.5.0.0 recovery for ICS, reset the phone, the same, can't clear any cache !
Click to expand...
Click to collapse
Don't use any tool, just do the command yourself
You sure you have hboot 1.24? For me, this looks like the typical hboot mismatch...
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
You sure you have hboot 1.24? For me, this looks like the typical hboot mismatch...
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wait you got a point, can you show us your bootloader screen @hugiz
ok I did the command directly in cmd, it works, i flashed the recovery...same
hugiz said:
ok I did the command directly in cmd, it works, i flashed the recovery...same
Click to expand...
Click to collapse
Show me a pic of your bootloader/fastboot screen
Here is the screen of the BL !
Here is the Fastboot one...same
hugiz said:
Here is the screen of the BL !
Click to expand...
Click to collapse
Now that's interesting... i didn't know that there were different partition layouts in hboot 1.21 as well. But then at least the RUU should work...
Which CID do you have? You are sure your CID is compatible with the RUU?
cid: HTC__038
i took the RUU asia of this link http://www.androidruu.com/?developer=Proto
I guess it's the right one, because when i called htc the guy noticed immediatly that i bought it there !
Ya, indeed this phone is interesting, if we can't fixe it up, i give to xda for science purpose ! :laugh::laugh::laugh:
By the way, the RUU detect the phone and its version,1.18.XXXX but can't restore it !
hugiz said:
cid: HTC__038
i took the RUU asia of this link http://www.androidruu.com/?developer=Proto
I guess it's the right one, because when i called htc the guy noticed immediatly that i bought it there !
Ya, indeed this phone is interesting, if we can't fixe it up, i give to xda for science purpose ! :laugh::laugh::laugh:
By the way, the RUU detect the phone and its version,1.18.XXXX but can't restore it !
Click to expand...
Click to collapse
Relock your bootloader and run the ruu in the bootloader mode (not the fastboot mode)
GtrCraft said:
Relock your bootloader and run the ruu in the bootloader mode (not the fastboot mode)
Click to expand...
Click to collapse
I need an explication here, I did relock the BL ( how can i check if it's really relock ?), so, I should launch the program of the RUU while i'm in the HBOOT USB window and no the FASTBOOT USB one, right ?
hugiz said:
I need an explication here, I did relock the BL ( how can i check if it's really relock ?), so, I should launch the program of the RUU while i'm in the HBOOT USB window and no the FASTBOOT USB one, right ?
Click to expand...
Click to collapse
At the top of the bootloader screen the purple text is showing if it's locked, unlocked or relocked.
I see at the pics you send the bootloader is unlocked so do this:
1. Go to fastboot mode and do this command: ''fastboot oem lock''
2. It will restart after that but as you said it will be stuck at the htc logo so go back to the bootloader.
3. If it says RELOCKED at the top of the screen you are good to go
4. Go into bootloader/hboot mode
5. Connect the phone to the PC and run the RUU again
GtrCraft said:
At the top of the bootloader screen the purple text is showing if it's locked, unlocked or relocked.
I see at the pics you send the bootloader is unlocked so do this:
1. Go to fastboot mode and do this command: ''fastboot oem lock''
2. It will restart after that but as you said it will be stuck at the htc logo so go back to the bootloader.
3. If it says RELOCKED at the top of the screen you are good to go
4. Go into bootloader/hboot mode
5. Connect the phone to the PC and run the RUU again
Click to expand...
Click to collapse
so, i tried 3 times, i get :
(bootloader) lock sucessfully...
FAILED ( status read failes (no such file or directory))
finished. total time 1.027s
reboot, stuck logo....
hugiz said:
so, i tried 3 times, i get :
(bootloader) lock sucessfully...
FAILED ( status read failes (no such file or directory))
finished. total time 1.027s
reboot, stuck logo....
Click to expand...
Click to collapse
Then send it to a htc repaire center or use it as a paperweight
hugiz said:
cid: HTC__038
i took the RUU asia of this link http://www.androidruu.com/?developer=Proto
I guess it's the right one, because when i called htc the guy noticed immediatly that i bought it there !
Ya, indeed this phone is interesting, if we can't fixe it up, i give to xda for science purpose ! :laugh::laugh::laugh:
By the way, the RUU detect the phone and its version,1.18.XXXX but can't restore it !
Click to expand...
Click to collapse
I know the problem why the RUU is not working. Your software version is 1.18.XXXX but RUU software version is 1.14.XXXX. As you can't downgrade your phone with RUU, that won't work.
Take a look at that: http://forum.xda-developers.com/showthread.php?t=2210619&highlight=nandroid
You'll find a restorable nand backup there, which first part is incomplete, so you need to flash the second file as well like explained in the thread. Good luck!
Ok that's look interesting, i followed the step perfectly ,i put on my SD card the files of this folder
- https://drive.google.com/folderview?id=0Bytqvf8J9vnabkhxVWJJMk45dFU&usp=sharing from this link http://forum.xda-developers.com/showpost.php?p=40541546&postcount=102 which match with my CID.
I put the file as indicated in theses folders TWRP/BACKUPS/SERIALNO/2013-03-28--11-51-07
Once in twrp i can mount the sd card put nothing appear in the available backups but i can see the files in the integrated file explorer of TWRP....
You need to replace SERIALNO with the actual Serial number of your phone. If you don't know how to do that, you can do a little trick: Just do a nand backup of your current configuration, the folder with your Serial Number should then be created. After that, paste the files from the link to that folder. Also, do not forget do flash the additional file needed for CID HTC_038 to be completely stock.
Hey, just to let people know, be wary of flashing the firmware from the M7 Sense 6 update from T-Mobile, I pulled it from the OTA and it flashed successfully in RUU mode, but now im stuck in the dreaded QHSUSB_DLOAD mode, trying to figure a way to get a replacement, but just letting people know to be careful...
Whoareyou said:
Hey, just to let people know, be wary of flashing the firmware from the M7 Sense 6 update from T-Mobile, I pulled it from the OTA and it flashed successfully in RUU mode, but now im stuck in the dreaded QHSUSB_DLOAD mode, trying to figure a way to get a replacement, but just letting people know to be careful...
Click to expand...
Click to collapse
Please provide more details;
Do you have a T-Mobile device? --Did you change your CID?
What ROM?
What recovery?
Bootloader unlocked? S-Off?
What hboot did you have before flashing (stock? custom?)
How exactly did you pull the firmware?
These details would be very helpful.
Sent from my HTC One_M8 using Tapatalk
krook6023 said:
Please provide more details;
Do you have a T-Mobile device? --Did you change your CID?
What ROM?
What recovery?
Bootloader unlocked? S-Off?
What hboot did you have before flashing (stock? custom?)
How exactly did you pull the firmware?
These details would be very helpful.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes I have a T-Mobile Device, yes its S-OFF, CID is SUPERCID (1111111), had Firewater HBOOT previously.
ViperONE 6.2.1
TWRP
i used WinRAR and pulled the firmware.zip from the OTA file, then booted into rebootRUU mode and "fastboot flash zip firmware.zip" the it told me to flush again as per usual, i did it again, then when i went to reboot, i was in QHSUSB_DLOAD
Whoareyou said:
Yes I have a T-Mobile Device, yes its S-OFF, CID is SUPERCID (1111111)...
Click to expand...
Click to collapse
Maybe an issue with SuperCID...
You should read this thread: http://forum.xda-developers.com/showthread.php?t=2753631
People had a similar problem and a few were able to get back into hboot by plugging the phone to computer and persistently pressing power and volume down and/or volume up in different combinations. If you can get back to the boot loader flash a know working firmware. It's worth a shot... Here are some relevant comments from that thread...
streather said:
Same problem here, bricked the phone.
I have managed to get it to turn back on and got to the silver HTC logo but I sent the wrong command over fastboot and it turned off again
Click to expand...
Click to collapse
BanBoo said:
How do you managed it?!
Click to expand...
Click to collapse
simaka said:
OK, I got back to the bootloader.
Guys, be persistent in pressing power+vol buttons while usb connected to PC, it took me about 10-15 minutes but now I am back to fastboot!
Any ideas what would be the best course of action now?
Click to expand...
Click to collapse
simaka said:
Not sure if it was power + vol down or + vol up... But I definitely waited each time about 20 secs before switching to the other possibility. And the phone was usb connected to my pc.
Click to expand...
Click to collapse
simaka said:
Yes, each time. I also tried pressing both + and - at the same time, but that was not the winning combination.
Click to expand...
Click to collapse
yoshi8 said:
how did you recognized that you are in fastboot again? did your screen turn on again?
Click to expand...
Click to collapse
simaka said:
Yes, it has booted and screen is lit and I am in fastboot. Now wondering what is the best next step... Which firmware should I upgrade with...
Click to expand...
Click to collapse
simaka said:
Here is what I did the last time:
1. winclock showing seconds in front of me.
2. hold power + vol down.
3. Count 3 seconds
4. release.
5. Go to 1 and add 1 second on step 3 . In about 20 minutes (when I surpassed 20 secs I started from 3 seconds on step 3 again) I woke it up.
good luck!
Click to expand...
Click to collapse
Sent from my HTC One_M8 using Tapatalk
All CID's must have eight characters. SuperCID would have to be 11111111 not 1111111
Sent from my HTC One using XDA Free mobile app
NxNW said:
All CID's must have eight characters. SuperCID would have to be 11111111 not 1111111
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
you know what i mean, it was all 1s also holding the buttons didnt work
Whoareyou said:
you know what i mean, it was all 1s also holding the buttons didnt work
Click to expand...
Click to collapse
Just checking- someone said it could be an issue with the CID, and that would definitely be "an issue" ; )
Whoareyou said:
Yes I have a T-Mobile Device, yes its S-OFF, CID is SUPERCID (1111111), had Firewater HBOOT previously.
ViperONE 6.2.1
TWRP
i used WinRAR and pulled the firmware.zip from the OTA file, then booted into rebootRUU mode and "fastboot flash zip firmware.zip" the it told me to flush again as per usual, i did it again, then when i went to reboot, i was in QHSUSB_DLOAD
Click to expand...
Click to collapse
That right there is what bricked your phone. I honestly don't know why people care so much about the red message on boot to flash a modded Hboot. Most devs on the One international forum are starting to pull of their modded Hboots as people usually don't know flashing a modded one can brick phones on future updates or so.
I haven't manually flashed just firmware. I am s-off with supercid. To get most current I loaded the last tmous ruu then let it go through all updates until it was at the latest sense 6, then reloaded twrp and my latest nandroid.
Sent from my HTC One using XDA Free mobile app
Jorakal said:
I haven't manually flashed just firmware. I am s-off with supercid. To get most current I loaded the last tmous ruu then let it go through all updates until it was at the latest sense 6, then reloaded twrp and my latest nandroid.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
That is a good way however we should point if one has a moded hboot and applies the official RUU will brick the phone. Just pointing that out.
Sent from my HTC One using Tapatalk
Firmware Update
I have been looking to update to the latest firmware on my tmobile htc one, but i also have a custom hboot that i got from here " http://forum.xda-developers.com/showthread.php?t=2497712 " so im holding off on flashing the newest firmware, because it will probably brick my phone. But what i am wondering is does anyone know where i can just fine the 1.44 tmobile hboot that i was currently on?? so that i dont have to flash the stock RUU and start all back over from scratch ?? I could just flash back to the 1.44 stock hboot and then upgrade to the newest firmware without bricking my phone ??
Tewessarino said:
I have been looking to update to the latest firmware on my tmobile htc one, but i also have a custom hboot that i got from here " http://forum.xda-developers.com/showthread.php?t=2497712 " so im holding off on flashing the newest firmware, because it will probably brick my phone. But what i am wondering is does anyone know where i can just fine the 1.44 tmobile hboot that i was currently on?? so that i dont have to flash the stock RUU and start all back over from scratch ?? I could just flash back to the 1.44 stock hboot and then upgrade to the newest firmware without bricking my phone ??
Click to expand...
Click to collapse
Take a look @Behold_this thread TMOUS Firmware Packages - Release Builds for the correct firmware to return you to stock hboot.
factory reset
i tried almost everything i cant do ruu.exe cause i get and error 155 which is unknown error and yes i was relocked before running the ruu. i tried doing s-off with no luck im on t-mobile us network htc one m7
i have viper rom 6.2.0 running right now on it
bootloader menu i have
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.21.3263.03
OpenDSP-v32.120.274.0909
OS-*** this is what im not sure why theres nothing when there used to be***
eMMC-boot 2048m
its tampered and unlocked at the moment plz help thanx i need to factory reset
matador1510 said:
i tried almost everything i cant do ruu.exe cause i get and error 155 which is unknown error and yes i was relocked before running the ruu. i tried doing s-off with no luck im on t-mobile us network htc one m7
i have viper rom 6.2.0 running right now on it
bootloader menu i have
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.21.3263.03
OpenDSP-v32.120.274.0909
OS-*** this is what im not sure why theres nothing when there used to be***
eMMC-boot 2048m
its tampered and unlocked at the moment plz help thanx i need to factory reset
Click to expand...
Click to collapse
Which RUU.exe are you attempting to run? If it is this one: T-Mobile HTC One 4.3 3.24.531.3 RUU then your hboot is too high. I would suggest trying this one: T-Mobile USA | 4.4.2 | Sense 6 | 5.14.531.11. Also, since you are S-ON the bootloader needs to be locked/relocked for you to run a RUU. You can lock it in bootloader/FASTBOOT USB with this command: fastboot oem lock
If Viper is running on your One without an issue then you have an operating ROM and the missing OS is due to the custom recovery you used. If you are using TWRP, I would recommend TWRP 2.6.3.3 or TWRP 2.6.3.4 or TWRP 2.7.1.2! The last one has some changes built in that help eliminate the issue of a blank OS.
factory reset
majmoz said:
Which RUU.exe are you attempting to run? If it is this one: T-Mobile HTC One 4.3 3.24.531.3 RUU then your hboot is too high. I would suggest trying this one: T-Mobile USA | 4.4.2 | Sense 6 | 5.14.531.11. Also, since you are S-ON the bootloader needs to be locked/relocked for you to run a RUU. You can lock it in bootloader/FASTBOOT USB with this command: fastboot oem lock
If Viper is running on your One without an issue then you have an operating ROM and the missing OS is due to the custom recovery you used. If you are using TWRP, I would recommend TWRP 2.6.3.3 or TWRP 2.6.3.4 or TWRP 2.7.1.2! The last one has some changes built in that help eliminate the issue of a blank OS.
Click to expand...
Click to collapse
thanx i will try this will let you what happens
htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0
lordtopher said:
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0
Click to expand...
Click to collapse
Check out this post for the TWRP nandroid, firmware and stock recovery for your phone. You will need to unlock your bootloader to flash the recovery or TWRP. If you decide to flash the firmware your bootloader should remain locked. In fact, I would flash the firmware first, then install TWRP to install the nandroid.
majmoz said:
Check out this post for the TWRP nandroid, firmware and stock recovery for your phone. You will need to unlock your bootloader to flash the recovery or TWRP. If you decide to flash the firmware your bootloader should remain locked. In fact, I would flash the firmware first, then install TWRP to install the nandroid.
Click to expand...
Click to collapse
the problem is the phone... when i got the fastboot menu...i can scroll down and up but when i press on power button to enter the bootloader the phone freezer and i must turn it off. have you heard this issue??? must i buy another phone??:crying:
lordtopher said:
the problem is the phone... when i got the fastboot menu...i can scroll down and up but when i press on power button to enter the bootloader the phone freezer and i must turn it off. have you heard this issue??? must i buy another phone??:crying:
Click to expand...
Click to collapse
Can you connect the phone to a computer and is it recognized?
If yes, then I would recommend flashing the firmware. It contains hboot and you may have an issue with hboot.
Here is the procedure for flashing the firmware. If your phone is already in bootloader/FASTBOOT USB you can skip the first line.
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse