Related
Hi Guys,
So only one hour after getting my phone, I decided to try and flash a new rom... Coming from a HD2 that was so easy, maybe I didn't read 'all' the information that I should.
Anyway, I flashed with HTC original unlock code, and that seemed to work... Over the past 12 hours or so, I've tried to flash several roms, but with no luck... I've then tried to do various recoveries, but no luck.... (I don't have all the details of what I've done, so that isn't probably going to help!).
I've been reading the forum and trying various things for days now, but no luck... what I am stuck with is the following.
When pressing the power and down button, or boot up, I get:
*** UNLOCKED ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.0008
RADIO-10.13.9020.08_2M
eMMC-boot
Jul 15 2001, 14:39:25
If I just reboot normally, then it just shows white background, with green HTC in the middle, then pauses for about a minute, then just reboots again (Yep, I have left it on for hours, same result).
So, I am able to talk to the device via fastboot, but not adb...
I have downloaded the HTCDriver3.0.0.007.exe and unloaded HTC software, but still no luck with adb..
Obviously looking at the boot screen, it still S-ON, so that probably isn't helping...
I'm happy to pass on any more information or try any suggestions that the experts may have At the mo, back using my HD2, but would love to use this new phone (the back's been off so many times that it's already starting to look old!)
So, what's next guys? Does this classify this as a brick ! ???
bro you need to visit this site.... revolutionary.io
Follow the instructions to the t on their. You are on h boot 1.4... DO NOT update anything. Just root and flash a 2.3.4 rom in the dev section
---------- Post added at 12:41 AM ---------- Previous post was at 12:40 AM ----------
also, what carrier are you with?
jnrdavo said:
Hi Guys,
So only one hour after getting my phone, I decided to try and flash a new rom... Coming from a HD2 that was so easy, maybe I didn't read 'all' the information that I should.
Anyway, I flashed with HTC original unlock code, and that seemed to work... Over the past 12 hours or so, I've tried to flash several roms, but with no luck... I've then tried to do various recoveries, but no luck.... (I don't have all the details of what I've done, so that isn't probably going to help!).
I've been reading the forum and trying various things for days now, but no luck... what I am stuck with is the following.
When pressing the power and down button, or boot up, I get:
*** UNLOCKED ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.0008
RADIO-10.13.9020.08_2M
eMMC-boot
Jul 15 2001, 14:39:25
If I just reboot normally, then it just shows white background, with green HTC in the middle, then pauses for about a minute, then just reboots again (Yep, I have left it on for hours, same result).
So, I am able to talk to the device via fastboot, but not adb...
I have downloaded the HTCDriver3.0.0.007.exe and unloaded HTC software, but still no luck with adb..
Obviously looking at the boot screen, it still S-ON, so that probably isn't helping...
I'm happy to pass on any more information or try any suggestions that the experts may have At the mo, back using my HD2, but would love to use this new phone (the back's been off so many times that it's already starting to look old!)
So, what's next guys? Does this classify this as a brick ! ???
Click to expand...
Click to collapse
When the device boots and hangs on the HTC screen and then reboots, this generally indicates there is an issue with the kernel. Either the kernel itself is experiencing trouble or the ramdisk portion of the kernel is experiencing trouble. Usually the kernel portion.
The best solution will be to reload a known working kernel. The best method to do this, w/o being able to boot into Android will be to go through the custom recovery.
If you're currently using the HTC unlock method, it only unlocks the kernel partition for writing in three boot modes: bootloader, normal android and fastboot. Since normal android mode is out of the question at this point, bootloader is usually best used for flashing the full system back to stock, that leaves fastboot mode.
There are two ways to flash the kernel through the fastboot:
1) fastboot boot c:\cwm-recovery.img . this will boot temporarily boot the custom recovery image and grant it write access to the kernel partition. while in the temporarily booted custom recovery, flash any ROM or custom kernel .zip file and it will have write access to properly complete.
2) fastboot flash boot c:\boot.img . this will boot just the kernel image and will not load the kernel modules which include WiFi and WiMAX. this will allow the phone to boot the kernel. once the phone is booted on the new kernel you'll need to copy over the modules from the new kernel manually in order for wifi and wimax to work.
for future reference, if you want to avoid these work around methods which can be confusing to some, my application, Flash Image GUI, will allow you to properly flash a kernel from normal android mode.
it should be considered best practice to be familiar with how to properly boot the custom recovery in order to do backups and restores of the full system.
Also, if you are able to use the revolutionary (http://revolutionary.io) method to s-off the device, this will grant the standard custom recovery access to write the boot partition/kernel and help avoid a lot of this hassle. if you're not able to use the revolutionary method then you're next best method is using the HTC unlock method and follow the steps/guidelines i posted above.
hope that helps!
Many thanks Guys... I have tied the revolutionary recovery a few times, but it the program just sits on my screen trying to connect to the phone - unsuccessfully.
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
I'll give the other go a shot..
I really appreciate all your help on this one..
I think my eagerness to get a better ROM on overtook my safety net in reading ALL the instructions!....
ok, further info...
Just to answer previous question, I am with Telstra in Australia... Phone came from web, with rogers rom on it...
I can now boot to ClockworkMOd Recovery v5.0.2.0 (I had to use fastboot to get the loader on)....
It's great, I get the menu and everything, but when I select on of the options (actually, any of the options), by pressing the power button, I just get the blank screen with the hat logo... nothing happens (ie, if I select load zip from sdcard).... I can press the power button again to get to the main menu, but nothing else...
I'm assuming that I still need to get s-off functioning prior to being able to flash the rom?
I've also loaded the flashimageGUI.apk file to the phone on the SD card... Rebooted in both hboot and recovery, but nothing seems to happen...
Actually, at the bottom of ClockworkMod, the following is displayed in white (rest of the text is in blue):
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Just to clarify, I'm on 3G...
Hi Guys, still stuck...
I've followed the instruction on:
http://forum.xda-developers.com/showthread.php?t=1193540&page=3
... but still no luck... I still have S-ON and not able to flash any ROMS...
I am also unable to get any response from ADB, and also revolutionary.exe just sits there 'waiting for device'...
Any more suggestions... getting desparate here!
have you flashed a custom rom if so that may be the problem what has happen is you lost your boot.img exract it from the zip file on your pc or laptop now go the that folder and open it up scroll down untile you come across your boot.img now copy it to the same folder that you have your adb and your fastboot in now open up cmd and typ fastboot flash boot boot.img press enter and your back up and running
My heart is about to break ;( , It's been a couple days without my rezound working properly.....
I tried to Flash BAMF's rom v1.1 and it kept on rebooting itself after a couple minutes.
After I found out that I had to install the new RUU i tried that.
And i guess i failed horribly.
I dl'd it and put it on my sd card.
I Locked my Rezound, and had it installing.
I ran it about 3 times and the blue bar went from blue to yellow and then it just went back to the android men skateboarding.
I tried to run my nandroid but I didnt get any signal what so ever (Wifi-3g-4g).
At this point I was going insane.
I'm not sure what I should do......
My phone is just a white screen having these text.
***UNLOCKED***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
RADIO-0.95.00.1118r/0.95.00.1223r
OpenDSP-v10.6.0.7611.00.0919
eMMC-boot
Oct 6 2011, 15:43:22
PLEASE HELP ME
(Yes, i tried looking up very single thing....)
(I have both a PC and Mac, If possible can you post instructions for MacOS)
First, based off those version numbers, you never successfully installed the latest RUU. Scott has a nice write up on his site on how to do the RUU install, it's needed for any of the latest ICS based roms. - http://www.scottsroms.com/showthread.php/856-HOW-TO-Prepare-for-CleanROM-4-0-Update
If you're trying to restore a backed up rom, you also need flash the kernel back into place, nandroid restore can't do it because our phones are s-on. Try using this to do the restore - http://forum.xda-developers.com/showthread.php?t=1547496
Is it possible to do something else than recover the back up?
What are you trying to do before recovering the back up?
kevinlovesrice said:
My heart is about to break ;( , It's been a couple days without my rezound working properly.....
I tried to Flash BAMF's rom v1.1 and it kept on rebooting itself after a couple minutes.
After I found out that I had to install the new RUU i tried that.
And i guess i failed horribly.
I dl'd it and put it on my sd card.
I Locked my Rezound, and had it installing.
I ran it about 3 times and the blue bar went from blue to yellow and then it just went back to the android men skateboarding.
I tried to run my nandroid but I didnt get any signal what so ever (Wifi-3g-4g).
At this point I was going insane.
I'm not sure what I should do......
My phone is just a white screen having these text.
***UNLOCKED***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
RADIO-0.95.00.1118r/0.95.00.1223r
OpenDSP-v10.6.0.7611.00.0919
eMMC-boot
Oct 6 2011, 15:43:22
PLEASE HELP ME
(Yes, i tried looking up very single thing....)
(I have both a PC and Mac, If possible can you post instructions for MacOS)
Click to expand...
Click to collapse
so when exactly did you almost brick?
I had a similiar problem. I relocked just fine, but when flashing the ruu it only partially worked even though it didn't give me any errors.
Turned out I had a bad download. Try to redownload ruu check file size and try to flash again. This worked for me.
tmar23 said:
I had a similiar problem. I relocked just fine, but when flashing the ruu it only partially worked even though it didn't give me any errors.
Turned out I had a bad download. Try to redownload ruu check file size and try to flash again. This worked for me.
Click to expand...
Click to collapse
That's weird. You have to run it twice, the first one updates hboot, and it will install in a random order. It will reboot, pull battery, get back to hboot, and install again. It will install in the correct order and be successful.
I was trying to recover a RezRom recovery but when I actually got into the back-up, it gave me no signal.
I'm going to try and re-download and hopefully revive me ReZound :,(
None of that = brick..
Sent from my ADR6425LVW using XDA Premium.
2 options at this point OP
1.) Reflash your custom recovery and a custom rom of your choice/nandroid and reflash kernel.
or
2.) Redownload/Check MD5 of the RUU, update, reflash AmonRA and reflash BAMF 1.1.
mjones73 said:
First, based off those version numbers, you never successfully installed the latest RUU. Scott has a nice write up on his site on how to do the RUU install, it's needed for any of the latest ICS based roms. - http://www.scottsroms.com/showthread.php/856-HOW-TO-Prepare-for-CleanROM-4-0-Update
If you're trying to restore a backed up rom, you also need flash the kernel back into place, nandroid restore can't do it because our phones are s-on. Try using this to do the restore - http://forum.xda-developers.com/showthread.php?t=1547496
Click to expand...
Click to collapse
Follow the scottsroms post on how to update. Whoever told you above that you have to battery pull to get to the second round of updating is wrong.
1. Lock it
2. Run the RUU PH98IMG.zip in the bootloader
3. It will go to the white HTC screen, for me, it stuck there for like 20min. Just make sure it's plugged in and be paitent.
4. It will reboot into fastboot, select bootloader and tell it to run the PH file again.
5. It will reboot into the stock ROM
if it does anything other than that, you've done it wrong.
6. Don't try to nandroid restore... just do a clean install and don't restore anything from Ti Backup. Why would you try to restore a broken install?
a-jive said:
Follow the scottsroms post on how to update. Whoever told you above that you have to battery pull to get to the second round of updating is wrong.
Click to expand...
Click to collapse
There were (not many) of some reports of hardlocking/freezing while updating hboot to where it comes up with an "OK" but doesnt give the prompt to press power to reboot.
Myself, I didn't have to.
this might help
Scott has a very detailed step by step guide in his CleanROM thread. Just a few pointers before you jump in. Following this and the steps in Scott's guide should help you to get your phone back. I truely suggest using the Amonra recovery, people have reported many times that this recovery just works right, no issues.
1) make sure you have a card reader for your computer that you can connect your removable micro-SD card to. Trust me, if you screw up somewhere in the process, having a reliable way to access the SD card is a life saver.
2) before flashing always wipe/factory reset 3 times, some think it is overkill, but if you end up with some odd glitch or bug when you just wiped once, you will most likely have to wipe and flash again to get rid of the bug...so of course you are actually saving time and hassle by just doing it 3 times in the first place.
3) make sure your battery is full or almost full before you start the process, you will avoid many problems by not having your phone battery die in the middle of a flash or update.
4) read, read and read again all the information and the instructions on what you are going to be doing, then make sure you understand and are comfortable Before you actually start. Reading through the forums and knowing beforehand what others have experienced, and the fixes, will make your life 100% better while you play with your phone.
THANKS
MY REZOUND IS ALIVE!!!!
I love scott.....
ohh my... im starting to think the definition for "bricking" a phone is changing
yojoe600 said:
ohh my... im starting to think the definition for "bricking" a phone is changing
Click to expand...
Click to collapse
+1
10 char
Yep. I was wondering when being in hboot=bricked.
Snuzzo said:
There were (not many) of some reports of hardlocking/freezing while updating hboot to where it comes up with an "OK" but doesnt give the prompt to press power to reboot.
Myself, I didn't have to.
Click to expand...
Click to collapse
My bad, didn't ever catch that issue in my research.
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'm sorry in advanced because I've seen a lot of threads similar to this one but none have solved my issue.
The story on how this happened:
I have an EVO LTE. I flashed it from Sprint to Verizon's prepaid unlimited everything plan and it worked awesomely. Unlocked bootloader. Installed TWRP. Rooted my phone. Everything was working perfect for a month. Sure enough, Verizon reps messed up my account somehow and I ended up having to get another phone number and another flip phone, therefore making me flash it again. No problem. Flashed it again but calling and SMS didnt work so I thought " Hey, I might just have to factory restore, wipe everything, and try again." Here's where I messed up...bad.
I went into TWRP and somehow managed to wipe EVERYTHING off my phone except for TWRP (including OS and important files that help it be a phone). I am assuming I do not have an OS anymore on this phone.
Whenever I thought i successfully flashed a ROM over and restarted my phone, it goes to the white HTC logo, then the dev disclaimer comes up, sits there for a while, the repeats infinitely.
I've lurked around and viewed MANY threads and websites trying to fix my problem but no luck at all. I've attempted many flashed and installs on trying to get an OS loaded on my phone but can't do it right (apparently).
Here's everything now:
- I can load into TWPR just fine (holding power + Vol down > hit recovery > loads into TWRP). Mount things. Move files. No problem there.
- I can fastboot things and control my phone without any problems. (although i haven't memorized any codes or commands) (fastboot flash blah blah).
Also here's what versions of stuff is on my phone (bootloader I think)(sorry I can take a screen shot)
-----------------------------------------
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.12.11.1210
OpenDSP-v31.1.0.45.0815
eMMC-boot
Oct 18 2012, 15:46:20
HBOOT
<VOL UP>
<VOL DOWN>
<POWER>
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
SHOW BARCODE
-----------------------------------------
My question is can anyone assist me in installing EVERYTHING fresh to my phone through fastboot ot TWRP? Sounds easy right?
Well I would be forever in your debt if you can work some magic and help me out.
If you can link to updated (and correct versions for what my phone is on) files I need to download, that would be really appreciated. Basically, if i can get the compatible files for my phonw and someohe can tell my where to place them and how to install them, I would be one happy camper.
Thank you and I'm sorry if there is a thread for my exact problem somewhere out there already.
**** EDIT ****
I just downloaded Viper4G 3.1.5 Full ROM and flashed it over vie mounting in TWRP. Went to install, chose it and in installed successfully without any hiccups. It said that the kernal will be installed upon restart and when it restarted my phone, it continued to say "for development purposes only" and continually restarted a few times before i went back into TWRP. Did I do something wrong?
Find the ruu you where originally on, ruu the device. Repeat your steps for vzw. After all thats done nandbackup, then mount your device to your pc copy the contents of sd. Place it somewhere safe, so if it happens again you can just nand restore. That is if I'm understanding you correctly. More details would help.
Sent from my EVO using xda app-developers app
Edit: sounds like you wiped system. So what you're gonna wanna do to flash a Rom is wipe system then wipe data/factory reset. Install a Rom zip, I'd go with stock rooted for now. Relax its not like you bricked.
Sent from my EVO using xda app-developers app
Hello all,
So I am having an interesting issue with my Rezound which has served me well for the past two years. Last night while I was browsing the internet I got the warning that my battery was going to go dead. Ignored it and kept browsing, eventually causing the phone to auto shutdown, fine, I have a spare battery (love removable batteries), threw that in and it started to boot but gets stuck at the white "HTC" loading screen. I am able to get into HBOOT and get the following.
*** LOCKED ***
VIGOR PVT SHIP S_ON RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-Boot
Sep 20 2012,17:40:22
When I try to do a factory reset it will act like it is going to start, showing a phone with a green circle and an arrow, and a loading bar. Then before the loading bar begins to get filled in at all (it is just gray with diagonal lines) the green circle changes to a red triangle and an exclamation point.
If I try to boot into recovery I get the same phone with a red triangle image.
This phone is 100% stock unrooted and untouched in any way save for disabling the stock bloatware (I didnt even root it to uninstall that!). AFAIK there was no OTA update done to it yesterday, and I have been using it every day up until now with no real issues.
Simply just the battery died, and now it wont boot. Any ideas?
I am having the same issue on my wife's Rezound. It died last night and went into the same bootloop. Tried a factory reset to no avail. Phone is stock with the same info as previous poster in HBOOT.
I'm familiar with some android development, but know nothing about HTC phones. If somebody could point me in the right direction it would be greatly appreciated.
So I have tried running the stock RUU, no dice, I was already at the latest version.
I then unlocked my bootloader through HTC dev and tried to flash AmonRA so I can do custom ROMs.
Now when I go into my bootloader and select "Recovery" the white HTC screen pops up with a brown progress bar in the top right which fills up quickly, then the phone turns off and that is it until I remove the battery (wont respond to power again after it turns itself off).
So it would appear flashing AmonRA did not work either. Next I will be trying CWM.
Thanks for the update. Keep us posted if anything works. I just don't have the time to learn and try everything right now.
So I got CWM Recovery flashed successfully, but when I boot into recovery and try to wipe I get format failed and mounting errors.
Could my eMMC have been corrupt? How can I fix it?
EDIT: I also get cant mount and cant open on /cache, /system, /sdcard from inside the CWM recovery
Have you attempted to s-off and ruu down to an official exe?
Sent from my DNA using my mind.
I have not done s-off yet, would that fix my mount issues? I am now running TWRP recovery, that also is unable to mount anything. I appear to be having issues with the /dev/block/mmcblk0p35 and /dev/block/mmcblk0p36 and /dev/block/mmcblk0p29 etc areas. At this point any help would be greatly appreciated.
I have put a good 12 hours into trying to get this thing to boot. I feel like I am close and if I could just get it to somehow re-format the whole /block directory then flash a new rom it would would. Pushing an RUU from fastboot did not work, nor did running it from TWRP. TWRP gave me issues in the aforementioned mmcblk areas, and fastboot just says failed, I would guess for the same reason though.
Yes, if all else fails. RUU exe is the last resort
Sent from my DNA using my mind.
I found another phone for the wife to use for now. I'll try to s-off and ruu when i have some time.
Uzephi said:
Yes, if all else fails. RUU exe is the last resort
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Where can I find the instructions and files to get S-Off without access to a ROM and running windows? The JPBear instructions state Linux only and says I need to have a stock ROM.
OK, so from my research I will need to use Linux. Do I need the HTC USB drivers or anything or can I just take a fresh install of Ubuntu and run JPBear? Also, since I have unlocked my bootloader and (tried) to flash a rooted stock rom, do I now need to re-lock and try to run the RUU again? I did try that tonight (re-locking then running the stock RUU) but it still gave me the error that HBOOT was older on the version I was trying to flash.
You won't be able to run any RUU with being s on as their isn't one available for the latest OTA. Try wiping and formatting cache data and system with the latest CWM (Touch). Then follow flash instructions of a ROM for s on.
Sent from my Rezound using Tapatalk 4
I have personally used the windows version of jpbear on a custom ROM to s-off my Rezound. It is somewhere in this forum. I was in a similar pickle and needed s-off to ruu. Albeit, my phone didn't have mount issues, so I don't know if ruu will fix your specific issue, but if anything will, ruu will fix it.
Sent from my Rezound using xda app-developers app
Uzephi said:
I have personally used the windows version of jpbear on a custom ROM to s-off my Rezound. It is somewhere in this forum. I was in a similar pickle and needed s-off to ruu. Albeit, my phone didn't have mount issues, so I don't know if ruu will fix your specific issue, but if anything will, ruu will fix it.
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
I believe an RUU would fix it if I can manage to get S-Off. I found an old version of ControlBear 0.2.2 for windows, when I run it it tells me to connect my phone and install drivers if I run from recovery. If I run from fastboot USB it trys to reboot my device into the ROM. So I dont know if JPBear will even work for me if I don't have access to my ROM.
Jensen567 said:
I believe an RUU would fix it if I can manage to get S-Off. I found an old version of ControlBear 0.2.2 for windows, when I run it it tells me to connect my phone and install drivers if I run from recovery. If I run from fastboot USB it trys to reboot my device into the ROM. So I dont know if JPBear will even work for me if I don't have access to my ROM.
Click to expand...
Click to collapse
i have a guide for obtaining s-off in linux....very well explained and thorough....
REV3NT3CH said:
i have a guide for obtaining s-off in linux....very well explained and thorough....
Click to expand...
Click to collapse
First off let me say a big THANK YOU for taking the time to respond and help me out. I did some searching, this is the guide you are referring to?
http://forum.xda-developers.com/showthread.php?t=2502814&highlight=s-off
I have no qualms with using linux and have some experience with ubuntu I just do not have an install up and running now so I wanted to avoid that if possible, but no big deal. In this thread
http://forum.xda-developers.com/showthread.php?t=1612035&page=202
you suggest I use fastboot usb to reinstall everything, is there a guide for this also? I am able to get to the white HBOOT screen to do fastboot USB, and I am also able to get into TWRP recovery. Version 2.6.3.3. However if I try to wipe anything from inside recovery I get "Unable to mount '/emmc'" or '/cache' '/data' or '/system'.
Sorry for my noobness with flashing, last time I did any of this was when I unlocked/s-off my DINC which was very easy at the time.
EDIT: I notice also in that guide you suggest to start from inside the ROM, I am unable to do this. Will it work from HBOOT, fastboot usb, or recovery?
Jensen567 said:
First off let me say a big THANK YOU for taking the time to respond and help me out. I did some searching, this is the guide you are referring to?
http://forum.xda-developers.com/showthread.php?t=2502814&highlight=s-off
I have no qualms with using linux and have some experience with ubuntu I just do not have an install up and running now so I wanted to avoid that if possible, but no big deal. In this thread
http://forum.xda-developers.com/showthread.php?t=1612035&page=202
you suggest I use fastboot usb to reinstall everything, is there a guide for this also? I am able to get to the white HBOOT screen to do fastboot USB, and I am also able to get into TWRP recovery. Version 2.6.3.3. However if I try to wipe anything from inside recovery I get "Unable to mount '/emmc'" or '/cache' '/data' or '/system'.
Sorry for my noobness with flashing, last time I did any of this was when I unlocked/s-off my DINC which was very easy at the time.
EDIT: I notice also in that guide you suggest to start from inside the ROM, I am unable to do this. Will it work from HBOOT, fastboot usb, or recovery?
Click to expand...
Click to collapse
1.) yes that is the guide im referring to...2.) AHA 2.6.3.3 HAS MOUNT ISSUES AND IS POSTED....go to an earlier version like 2.6.3.0...2.6.3.3 is only meant for FLASHING KITKAT ONLY and nothing else.....also why did you even trey to wipe internal sd anyway its not required...if you want the rezounds proper wipe method i can tell you...keep in mind the dinc is a whole different phone using a whole different motherboard....hence the differences....3.) once you have the proper version ill tell you how to get rid of mount issues
REV3NT3CH said:
1.) yes that is the guide im referring to...2.) AHA 2.6.3.3 HAS MOUNT ISSUES AND IS POSTED....go to an earlier version like 2.6.3.0...2.6.3.3 is only meant for FLASHING KITKAT ONLY and nothing else.....also why did you even trey to wipe internal sd anyway its not required...if you want the rezounds proper wipe method i can tell you...keep in mind the dinc is a whole different phone using a whole different motherboard....hence the differences....3.) once you have the proper version ill tell you how to get rid of mount issues
Click to expand...
Click to collapse
OK, I installed 2.6.3.0 and that is running. Still have mount issues but I am guessing that is normal at this point? I didn't try to wipe the internal SD per say, I was trying to wipe the cache and system to do a reinstall after the battery died and I was stuck at the white HTC boot screen.
Basically I am a noob and was just trying anything/everything to get it booting again. I found my old DINC now and am running that for now so I have some more time to work on it. On a side note, CM7.2 GB is still awesome.
Jensen567 said:
OK, I installed 2.6.3.0 and that is running. Still have mount issues but I am guessing that is normal at this point? I didn't try to wipe the internal SD per say, I was trying to wipe the cache and system to do a reinstall after the battery died and I was stuck at the white HTC boot screen.
Basically I am a noob and was just trying anything/everything to get it booting again. I found my old DINC now and am running that for now so I have some more time to work on it. On a side note, CM7.2 GB is still awesome.
Click to expand...
Click to collapse
so wait you are staying on ice cream sandwhich or lower? ok steps on 2.6.3.0 to get internal back is first go to wipe>advinced wipe and tick internal sd only...then swipe to wipe...youll get an error and thats ok....do the same method again except this time you'll notice it says emmc instead of internal sd....now go to mount option from main screen..then make sure only internal sd is checked and right below all options make sure it says Storage: Internal SDcard (size in mb) if it still says micro sd just tap on that area to change it....tap mount usb and plug into pc...reformat in windows using administrative tools in control panel or if it shows in my computer do it that way.....if you are staying on ICS or lower STAY WITH AMON RA ONLY...twrp and cwm is meant for jb and higher on the rezound....if the above method doesnt work...install amon ra and moun usb that way....you will have to fastboot install the recoveries obviously
REV3NT3CH said:
so wait you are staying on ice cream sandwhich or lower? ok steps on 2.6.3.0 to get internal back is first go to wipe>advinced wipe and tick internal sd only...then swipe to wipe...youll get an error and thats ok....do the same method again except this time you'll notice it says emmc instead of internal sd....now go to mount option from main screen..then make sure only internal sd is checked and right below all options make sure it says Storage: Internal SDcard (size in mb) if it still says micro sd just tap on that area to change it....tap mount usb and plug into pc...reformat in windows using administrative tools in control panel or if it shows in my computer do it that way.....if you are staying on ICS or lower STAY WITH AMON RA ONLY...twrp and cwm is meant for jb and higher on the rezound....if the above method doesnt work...install amon ra and moun usb that way....you will have to fastboot install the recoveries obviously
Click to expand...
Click to collapse
I have not decided what ROM I want to run, for now just getting it booting on the rooted OEM rom is fine.
I tried that method and it did not work. It does say unable to mount /emmc, but it also comes up with unable to mount just about everything else. Nothing shows as mounted under mount from the main menu (I have my SD card removed for now) and when I tap Internal SDcard to mount it I get unable to mount /emmc in the console.
I tried AmonRA first, flashing through fastboot usb, and it did not work for me. When I would select recovery from HBOOT the phone would go to the white HTC screen then the screen shuts off but recovery never comes up. The phone just got hot and would not respond to power button so I pulled the battery.