currently: boot loader unlocked
RUBY PVT SHIP S-ON RL
HBOOT-1.93.003
eMMC-boot
Aug 14 2012, 17:22:50
I am also using 4ext as a recovery installed from hasoons toolkit, ive tried multiple roms and always the same outcome. wifi may or may not work on first install, if it does its only periodic sometimes hours sometimes days sometimes never turns on at all. Anyone know how to fix this problem ? is it a problem with my s-on or hboot ?
hrsa_13 said:
currently: boot loader unlocked
RUBY PVT SHIP S-ON RL
HBOOT-1.93.003
eMMC-boot
Aug 14 2012, 17:22:50
I am also using 4ext as a recovery installed from hasoons toolkit, ive tried multiple roms and always the same outcome. wifi may or may not work on first install, if it does its only periodic sometimes hours sometimes days sometimes never turns on at all. Anyone know how to fix this problem ? is it a problem with my s-on or hboot ?
Click to expand...
Click to collapse
Is your wifi not picking up access points, or is it that the wifi activation box won't tick to "ON"? I'm running the same HBOOT and am also S-On. With the newer roms (CM10.2 for example) I've noticed a similar behavior that it seems to take a while to find the access point, however never taking longer than 5-10 minutes. Have you tried going back to an older series rom and seeing if it works better?
voodoodude said:
Is your wifi not picking up access points, or is it that the wifi activation box won't tick to "ON"? I'm running the same HBOOT and am also S-On. With the newer roms (CM10.2 for example) I've noticed a similar behavior that it seems to take a while to find the access point, however never taking longer than 5-10 minutes. Have you tried going back to an older series rom and seeing if it works better?
Click to expand...
Click to collapse
that's exactly what happens it just says turning wifi on but never ticks to on. I ended up relocking bootloader and flashing the r2 ruu but its still having the same problem :/
Seems like there are 2 reasons for the problem
1. You have faulty hardware (which likely isnt the case, since it still works...kinda, and you also wouldnt want to accept it)
2. It is a kernel issue
I am not sure of your method of flashing a new rom, or restoring with RUU, but the only explantion for the WiFi module not functioning properly after a RUU is done, is the radio, since the kernel is being replaced constantly with the rom flashing...
Do some googleing about bootloaders, especially radios, etc. and you will understand how flashing the incorrect bootloader/radio combination coudl damage and fatally brick your device
Hope this helps
since your S-ON my guess is your kernel isn't flashing properly...make sure to flash the rom with correct modules then flash the kernel through adb or flash the whole zip (modules+boot.img) while enabling smart flash
Related
I have my LTE rooted with s-on and Hboot 1.12 I dont know if Dumlock is installed but I've seen before somewhere in the phonew. My problem is bluetooth. The ding dong I sent the phone to who rooted with s-on had flashed the htc viper rom- theres a warning under 'quietly brilliant' that says "not for use outside of htc without certain permission, doing so may result in legal action" or something to that effect. Anywhay, this was way back when the LTE came out and the bluetooth worked fine until 3 or so weeks ago. Thats about the time that the 2.13.651.1 or whatever it is came out. The bluetooth dropped and would not re-connect. Then unpairing, soft resets, safe mode reboots, factory resets, I have 3 bluetooth units and they all pair up to ther devices no problem. I flashed 2 other roms - mean rom which based on the 2.13.651.1 update as well as the Team win Venom Viper rom which is by far the best rom I've had. This rom is also based on the update. So I imagine I have it. The bluetooth none the less does not work. I found out yesterday that since the update there are a couple oither people with the bluetooth issue. Htc is aware oif the issue and is working on a fix which could take weeksI am perplexed as to wether this is the issue or the fact that I have s-on. I saw there was a download of that update for rooted users posted so I downloaded it and flashed it and my phone went into a bootloop-I almost didnt get it out but I did and dl'd the viper rom again and the phones working nice again- no BT and a couple custom features within the rom arent working but not a big deal. My guess is I need s-off - I dont think anyhting else will work until this is done. Are you aware of this bluetooth issue and would you be able to give me the proper steps in getting s-off on the phone?
Thanks very much for your time,
TJ
Son with unlocked does not affect anything in the os, soff gives you the advantage of direct access to the partitions on your phone. Unlocking the bootloader gives partial access, soff and hboot unlock only deals with the hboot, partitions, and access full read/write access through the fastboot command line
Don't see any way that s-off is going to help the bluetooth issue. Also the only way to get s-off requires the 1.13 software. I've heard that downgrading is not recommended and can cause issues. Better to stay s-on.
FrankthaTank said:
Don't see any way that s-off is going to help the bluetooth issue. Also the only way to get s-off requires the 1.13 software. I've heard that downgrading is not recommended and can cause issues. Better to stay s-on.
Click to expand...
Click to collapse
Toolkit for downgrade is being worked on now. Exciting stuff!
S-on or S-off, bluetooth the real issue
om4 said:
Toolkit for downgrade is being worked on now. Exciting stuff!
Click to expand...
Click to collapse
Hello I see you're a senior member and I'm wondering if you would read this and possibly shed any light on my problem, I’d be very grateful. First a little info on my phone and root:
In the bootloader it says ***TAMPERED*** ***UNLOCKED*** JEWEL PVT SHIP S-ON RL, HBOOT- 1.12.0000, RADIO-1.02.12.0427, Open-DSP-v25.o1.32.0405, eMMC boot. The rom that was loaded on the phone was an HTC build called Viper Rom. When the HTC 'quietly brilliant' screen comes up, underneath in red text it says "This build is for developement purposes only Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action." There were no issues with the bluetooth for months. My Bluetooth started disconnecting roughly 3 or 4 weeks ago and I have tried almost everything I can think of to try and fix it. First checking the three Bluetooth headset devices I use on other devices and they show up no problem. The perplexing thing that I recently found is when connectin via USB and opening all the files on the phone, there is no 'root' file that I can find anywhere. What I have tried:
1. Soft resets
2. safe mode restarts
3. factory resets
4. Bluetooth fix/ repair app
5. Change wifi frequency band from 'auto' to '2.4'
Now all of the 5 things above that I have tried worked one time and all stopped working within about 2 hours. Some almost right away the bt was disconnecting- even though it would re-connect, soon that stopped. From that point forward I have done the following:
1. Downloaded and flashed the 'Team Venom's version of Viper Rom 2.0.0.
The rom worked fine. but no BT. Another member on XDA suggested flashing the latest Mean Rom based on the HTC update 2.13.651.1. Did so, no BT. Then I flashed the latest Viper Rom 2.0.2 also based on the update and no BT. My next step was flashing a rooted version of that update that Max (Mikroms) posted on here. I did a factory rest, wipe cashe, wipe Dalvik cashe- six times before doing so. I Thought bricked my phone, it was bootlooping. I held down the power button for two full minutes then let go and then held down the power and vol down buttons and luckily the bootloader came up. I again did a factory reset, cashe and Dalvik wipe and reflashed the Viper Rom 2.0.2 again. which is the best rom I have ever used. This time some of the viper Tweak aren't working of available but everything else works fine except the BT.
I found out a couple of days ago there are a couple other people having a similar problem. I called HTC and they are aware theres a BT problem and are working on a fix which could take weeks. I dont know how I would get this fix since my phone is S-on. Another senior member has told me I can get S-off on the phone since I have 1.12 Hboot. I will be reading up on how to properly do that but was also told that that wouldn't have anything to do with the BT. I see it as being able to get updates, fixes and other stuff I have read about 'S-off'
After reading online, I found something about fixing bluetooth with logcat but didn't quite understand it. I do have an app on my phone now called aLogcat but do not know how to use it. I also went through the Play store and came across an app called 'rSAP- Bluetooth SIM Access Profile'. I then read the reviews and it sounded like the fix. Instead of spendingt the $12.49, I downloaded the trial version. An error came up "System file library not found. Is the an HTC/Samsung phone?" with no means to reply. The first clue about the problem is that the BT system files are not there, empty or blocked somehow. The only other things I can think of are:
Finding a stock rom, downloading/ flashing latest stock RUU.
Finding and copying the bluetooth system files from a friends evo 4G LTE phone that is a couple months newer.
I will be contacting my BT headset manufacturer and see if I can find out what should be on the phone for files since HTC wont or dosen't know what they are. Do you know how to access and copy the BT software on the phone or have any answers or suggestions moving forward???
Thanks in advance for any info,
TJ
Hi guys, I've searched the forums for days now and tried many recovery methods, all which end in failure.
Basically my Evo which is on cyanogenmod is stuck on the wrong kernel, and I now have zero reception.
I even tried going into sprint, but their tech told me the first step towards recovery is going to be installing the right kernel.before I can do anything or get service again. He even let me take a picture of the Kernel info on an EVO LTE in the store.
The method of HOW to install the right kernel is where I am completely at a loss and would appreciate help.
I believe I'm looking for Odin
Stock Kernel
Stock Rom
and the steps it takes to do it
I am rooted.
I have TWRP v.2.2.2.0
Here is what my Hboot looks like.
***TAMPERED ***
***UNLOCKED***
JEWEL PVT SHIP S-0N RL
HBOOT 1.12.0000
RADIO. 1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMMC-boot apr 26 2012, 19:54:01
I have tried multiple RUU's which end in Failure and errors.
I've tried placing a stock recovery image and flashing it through Hboot.
UPDATE: someone told me I need to re-lock before I can flash a RUU.
so I re locked. and then ran an RUU and it finally completed successfully...
and now my phone has nothing but H boot.
no more TWRP
no more Rom
still have adb and electricity so if there is any way of saving my phone I'd appreciate any pointers.
UPDATE 2: after being stuck in fastboot only for the last 7 hours and trying all the recommended RUU's, I decided I'd try anything, so I re-did htc dev unlock.
I was then taken to my boot animation of cyanogen mod and nothing else.
I just rebooted into recovery and ::huzzah:: TWRP is still intact with 2 old backups of cyanogen mod.
I am going to be very careful of where I step next because all I've managed to do is dig myself deeper.
this is the one step forward in an otherwise downhill **** eating of grand magnitude.
I just read a google voicemail transcript for a video gig that I just lost because I never got the call.
I am thinking of installing the most stock rom I can, taking it into sprint, and claiming ignorance in hopes that they will just swap it out.
I'm now going to check if flashing the RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16
got my reception back...
Here's to hoping!
Which ruu did you run? If an old ruu and you still have hboot 1.12, any time you flash a ROM the correct kernel will also be flashed in the process.
I've never used ruu before, but it seems weird to me that after RUU, there is no ROM on your phone.
Do you have an SD card and card reader and PC?
Also, your twrp version is very outdated.
Using fastboot, you should be able to fastboot flash recovery to update TWRP. If you're unsure how, om4 has a great guide in either the general or general sticky section.
Sent from my EVO using xda premium
t3chn0v1k1ng said:
Hi guys, I've searched the forums for days now and tried many recovery methods, all which end in failure.
Basically my Evo which is on cyanogenmod is stuck on the wrong kernel, and I now have zero reception.
I even tried going into sprint, but their tech told me the first step towards recovery is going to be installing the right kernel.before I can do anything or get service again. He even let me take a picture of the Kernel info on an EVO LTE in the store.
The method of HOW to install the right kernel is where I am completely at a loss and would appreciate help.
I believe I'm looking for Odin
Stock Kernel
Stock Rom
and the steps it takes to do it
I am rooted.
I have TWRP v.2.2.2.0
Here is what my Hboot looks like.
***TAMPERED ***
***UNLOCKED***
JEWEL PVT SHIP S-0N RL
HBOOT 1.12.0000
RADIO. 1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMMC-boot apr 26 2012, 19:54:01
I have tried multiple RUU's which end in Failure and errors.
I've tried placing a stock recovery image and flashing it through Hboot.
UPDATE: someone told me I need to re-lock before I can flash a RUU.
so I re locked. and then ran an RUU and it finally completed successfully...
and now my phone has nothing but H boot.
no more TWRP
no more Rom
still have adb and electricity so if there is any way of saving my phone I'd appreciate any pointers.
Click to expand...
Click to collapse
Odin is the upgrade utility for Samsung, our equivalent is basically the HTC RUU packages. I would suggest re-running the ruu or running either 1.15 or 1.19 to restore the phone. If you want to continue using custom roms you should go to unlimited.io and follow the directions for soff
scottspa74 said:
Which ruu did you run? If an old ruu and you still have hboot 1.12, any time you flash a ROM the correct kernel will also be flashed in the process.
I've never used ruu before, but it seems weird to me that after RUU, there is no ROM on your phone.
Do you have an SD card and card reader and PC?
Also, your twrp version is very outdated.
Using fastboot, you should be able to fastboot flash recovery to update TWRP. If you're unsure how, om4 has a great guide in either the general or general sticky section.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
the RUU I flashed was "RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe"
Also I just noticed I am upgraded to Hboot 2.09.0000
t3chn0v1k1ng said:
the RUU I flashed was "RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe"
Also I just noticed I am upgraded to Hboot 2.09.0000
Click to expand...
Click to collapse
:what: Well... you can disregard that post about gaining s-off, that is a thing of the past now that you fully updated to the new baseband and hboot. If I might as (you don't have to answer as it doesn't really matter now) Why were you still s-on with hboot 1.12 in the first place??
mrrogers1 said:
:what: Well... you can disregard that post about gaining s-off, that is a thing of the past now that you fully updated to the new baseband and hboot. If I might as (you don't have to answer as it doesn't really matter now) Why were you still s-on with hboot 1.12 in the first place??
Click to expand...
Click to collapse
Honestly I have no idea.
I rooted my phone like the 2nd day I had it.
I also had on OG evo that I had rooted the entire time I owned it.
I never learned about s-off. I just wanted CM10, tethering, and adfree.
This is the reason for all of this to begin with:
on CM10, I had working 3G, but also 4G here and there.
my connection would drop out all the time to zero, or 1x.
Still had bars though, just no mobile data.
oh yea I have an air rave, does that make this story more fun?
anyway.
After getting a different answer, literally every time I went into sprint and asked about 4G.
It's on! it's coming next month! we have a repeater just in this area! it's coming on next month!
I decided it was my phones fault and that I need it back to factory.
I even have backups named "dec 2012 LTE works" and "DONT **** THIS UP"
And now I am here. twrp and fastboot are the only things I can access now.
I'm thinking of taking it into sprint with a stock image flashed
and letting it bootloop no matter what they try.
It'll still say "relocked" "tampered though"
I guess unrooting is my best next option?
I'm so clueless it's probably pretty funny to some of you.
the latest RUU I flashed is RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed (1).exe
does this mean my kernel and radio are updated now?
Yes should be. But now you may have more problems now with the new hboot then you had to begin with. Hboot 2.09 has more security features.
Hello all, I need some help if there are any ideas what could be going on with this phone. I can usually fix my own phone problems, but this one has stumped me...
I bought a rezound dirt cheap that was stuck on the white HTC screen and would not boot into the stock rom. At the time I bought it, it was s-on and I could get in the HBOOT and run fastboot commands.
Since buying it, I have tried many things to get this thing working. I've tried to RUU (with PH98IMG and .exe) and apparently after it completes it is once again in a boot loop on the white HTC screen. I have been able to unlock and flash a custom recovery onto it (amon-ra) and install any cm/aokp rom onto it and boot into that. The only issue with that is when in the rom, my wifi and bluetooth will not connect at all. It wont even toggle on in settings and it is not greyed out. 4G and everything else seems to work ok.
At this time, I'm thinking there is some kind of hardware failure but I'm open to suggestions.
In summary...
I have been able to s-off
I have tried different firmware combos of HBOOTs/radios
I have flashed custom recoveries and roms and can boot into them without wifi or bluetooth
I have been unsuccessful to RUU to anything stock, it'll just boot loop the white HTC screen
Right now, I have installed Tron 2.1 onto it. I did notice post:http://forum.xda-developers.com/showthread.php?t=2272781&highlight=no+wifi
When I go into system/lib, there was no /modules folder. I went ahead and created it and put in bcmdhd.ko and rebooted, but still no go. I'm not sure why the /modules folder was missing, but this reaches the extent of my knowledge on what is supposed to be there.
I believe I have tried everything and done fairly thorough searches to get this phone working properly and am at a loss what to do next. If anybody has a thought of something to try, I'm all for it. Fortunately if this phone doesnt work out, its not a big deal to me.
I don't want this to sound like another "stuck on HTC screen" thread. I have been through all those and this doesn't seem like the same problem.
Your help is greatly appreciated!
tacoman said:
Hello all, I need some help if there are any ideas what could be going on with this phone. I can usually fix my own phone problems, but this one has stumped me...
I bought a rezound dirt cheap that was stuck on the white HTC screen and would not boot into the stock rom. At the time I bought it, it was s-on and I could get in the HBOOT and run fastboot commands.
Since buying it, I have tried many things to get this thing working. I've tried to RUU (with PH98IMG and .exe) and apparently after it completes it is once again in a boot loop on the white HTC screen. I have been able to unlock and flash a custom recovery onto it (amon-ra) and install any cm/aokp rom onto it and boot into that. The only issue with that is when in the rom, my wifi and bluetooth will not connect at all. It wont even toggle on in settings and it is not greyed out. 4G and everything else seems to work ok.
At this time, I'm thinking there is some kind of hardware failure but I'm open to suggestions.
In summary...
I have been able to s-off
I have tried different firmware combos of HBOOTs/radios
I have flashed custom recoveries and roms and can boot into them without wifi or bluetooth
I have been unsuccessful to RUU to anything stock, it'll just boot loop the white HTC screen
Right now, I have installed Tron 2.1 onto it. I did notice post:http://forum.xda-developers.com/showthread.php?t=2272781&highlight=no+wifi
When I go into system/lib, there was no /modules folder. I went ahead and created it and put in bcmdhd.ko and rebooted, but still no go. I'm not sure why the /modules folder was missing, but this reaches the extent of my knowledge on what is supposed to be there.
I believe I have tried everything and done fairly thorough searches to get this phone working properly and am at a loss what to do next. If anybody has a thought of something to try, I'm all for it. Fortunately if this phone doesnt work out, its not a big deal to me.
I don't want this to sound like another "stuck on HTC screen" thread. I have been through all those and this doesn't seem like the same problem.
Your help is greatly appreciated!
Click to expand...
Click to collapse
i would like you to do the following.
flash this http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
2 times. it will make sure we have a solid base to work on.
after that has ran 2 times. boot into the stock rom one time.
after that flash this https://dl.dropboxusercontent.com/u/12405441/new.global.firm.PH98IMG.zip
once this is done let it boot into the rom.
from here you should be good to flash any rom that is out there to date. (note please dont restore any system data, only app data)
ALSO MAKE SURE YOU HAVE 100% battery. doing an ruu can brick the phone if its interrupted.
report back when done
Thanks for replying. I have flashed that RUU several times in a row in the past, but I'm redownloading it now to make sure my copy isnt corrupt. Earlier experience when I double flashed this it still remained a white HTC screen loop.
Currently estimated at 6hrs to download, so I wont be able to reply for a bit with my findings...
tacoman said:
Thanks for replying. I have flashed that RUU several times in a row in the past, but I'm redownloading it now to make sure my copy isnt corrupt. Earlier experience when I double flashed this it still remained a white HTC screen loop.
Currently estimated at 6hrs to download, so I wont be able to reply for a bit with my findings...
Click to expand...
Click to collapse
When the Rezound first came out a bunch of people had boot loop problems because the phone was set to wcdma or some such thing instead of cdma. I'm just a noob hack but that's my memory of it. The cure was to boot without the back cover on which contains the antenna and then change the setting.
Ok, I have re downloaded the AndroidPolice RUU and flashed twice, but was not able to boot into it no matter how long I waited (20 min+). It would just loop the HTC white screen. I then went ahead and flashed your global update firmware and have the same result after waiting (20 min+), it just loops the HTC white screen.
I have tried this process several times last night, but still no progress.
As the phone sits now:
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF 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
tacoman said:
Ok, I have re downloaded the AndroidPolice RUU and flashed twice, but was not able to boot into it no matter how long I waited (20 min+). It would just loop the HTC white screen. I then went ahead and flashed your global update firmware and have the same result after waiting (20 min+), it just loops the HTC white screen.
I have tried this process several times last night, but still no progress.
As the phone sits now:
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF 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
Click to expand...
Click to collapse
You need stock recovery and a locked bootloader
- "Is it dark in there?"
drynyks said:
You need stock recovery and a locked bootloader
- "Is it dark in there?"
Click to expand...
Click to collapse
S/he ran the RUU so they are stock.
Sounds like the symptoms of a kernel issue. Try pulling the boot.img from this stock OTA ROM and flashing it.
http://forum.xda-developers.com/showthread.php?t=2260154
fastboot flash boot boot.img
I have the exact same you. Been this way for months. Maybe once a month BT/Wifi will turn on but only for a few hours maybe. Phone will reboot itself and come back up with the 2 broken again.
feralicious said:
S/he ran the RUU so they are stock.
Sounds like the symptoms of a kernel issue. Try pulling the boot.img from this stock OTA ROM and flashing it.
http://forum.xda-developers.com/showthread.php?t=2260154
fastboot flash boot boot.img
Click to expand...
Click to collapse
Well I finally booted into stock sense after flashing that boot.img which is a big step from before. For a brief moment, it saw wifi networks in my office but when I went to connect to one, wifi died and it no longer sees any wifi network. Bluetooth appears to still be an issue as well, i.e. will not turn on.
Flyhalf205 said:
I have the exact same you. Been this way for months. Maybe once a month BT/Wifi will turn on but only for a few hours maybe. Phone will reboot itself and come back up with the 2 broken again.
Click to expand...
Click to collapse
Unfortunatly that doesnt sound very good for me if you've been battling this wifi/BT problem for months.
synisterwolf said:
i would like you to do the following.
flash this http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
2 times. it will make sure we have a solid base to work on.
after that has ran 2 times. boot into the stock rom one time.
after that flash this https://dl.dropboxusercontent.com/u/12405441/new.global.firm.PH98IMG.zip
once this is done let it boot into the rom.
from here you should be good to flash any rom that is out there to date. (note please dont restore any system data, only app data)
ALSO MAKE SURE YOU HAVE 100% battery. doing an ruu can brick the phone if its interrupted.
report back when done
Click to expand...
Click to collapse
can you explain what you mean by flash the ruu twice once I have saved it to the root of my sd card? Does that just mean get to the bootloader, watch as it reads the the ph98img file and let it do that twice, or do I need to reboot in between, or do I need to put in a command?
fivedezs said:
can you explain what you mean by flash the ruu twice once I have saved it to the root of my sd card? Does that just mean get to the bootloader, watch as it reads the the ph98img file and let it do that twice, or do I need to reboot in between, or do I need to put in a command?
Click to expand...
Click to collapse
when you let hboot flash the zip, the first time is super short. it updates hboot, stock recovery, and splash i think. then it will reboot back to bootloader and ask to be flashed again. this time it will take some time to update because it does the whole system.
---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------
tacoman said:
Well I finally booted into stock sense after flashing that boot.img which is a big step from before. For a brief moment, it saw wifi networks in my office but when I went to connect to one, wifi died and it no longer sees any wifi network. Bluetooth appears to still be an issue as well, i.e. will not turn on.
Click to expand...
Click to collapse
something doesnt seem right. the RUU would have flashed the boot.img for you. can you link me to the downloaded ruu that you have? also before you run the ruu did you do fastboot oem lock the bootloader?
Edit:
i remember an old trick from the inc days. after the RUU boot back into hboot and do a "factory reset" then boot into the phone. it use to fix the radio errors somewhere getting after a RUU. no clue why we did it. it just worked. try that when you are on stock recovery locked bootloader
Here is the RUU I have re downloaded. It was also the original I used in the past on my other Rezound
https://www.dropbox.com/s/1570h8l0ba1u7qp/rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
I have also tried the RUU 3.14.605.12.exe and a couple other different RUU versions, but have the same issue with that as well. Even on MicroMod777's OTA-Global-Stock-4.05.605.14 710RD-Rooted 5/1/13 flashed through amon-ra, I get the bootloop. I have done these as locked and unlocked bootloader with no difference. I have also tried the factory reset with locked bootloader.... no go with that either.
I was only able to finally boot in to stock by fastboot flashing the boot.img, and that is where this phone sits now. My major issue at this point is I dont have wifi or bluetooth and have dug through numerous posts and tried different things, and nothing is working on it. What was strange as I said in my previous post, the very first time I was able to boot into stock sense by flashing the boot.img, it briefly saw wifi networks but disappeared and disabled as soon as I tried to connect to one. I have not been able to replicate that since then.
On a sidenote and possibly related, since this phone has been sitting at my desk I decided to try and flash Newt's NOS JB v1.0.0 ROM and it bootloops also at the droid eye screen. I never was able to get it going on this phone. My other rezound boots this just fine.
I think I have reached the limits of my android knowledge of what to try on this thing. I am satisfied with it not having wifi/bluetooth since my wife wont be using those features. I would like to understand what the heck is going on though.
The back story...
I had to ditch Verizon. I didn't want to fork over $300 for a Republic Wireless phone only to be stuck with their crappy ROM, and the only 4G LTE android phone supported by Ting is the Evo 4G LTE; picked one up for $50 on ebay. I installed Cyanogenmod on a half dozen devices, newer and older than this phone, and thought this HTC Evo 4G LTE would be as easy as they were to unlock, root, S-OFF and flash. I've been more wrong before, but not without resulting in bodily harm. A hearty 'get stuffed' to HTC for this, and a plea for future rooters to have a concise guide on how to repair their phone under these circumstances.
The flawed process...
I went through HTC's unlock method to unlock the phone. Then I installed the latest TWRP via fastboot command line (2.7.1.0b as I found in a thread somewhere). No problems so far... I then went to install the latest CM build for Jewel (10.2.0 ) through TWRP 2.7.1.0b and it failed. This marked the first time I'd ever seen a fail message in TWRP. I thought no big deal, I'll restore the backup... The backup was gone. Now we have problems; phone is stuck in a bootloop. After reading many threads stating that S-OFF is required to flash their ROM, I tried to achieve that in Windows 7 to no avail through all available means. I then tried the closest RUU for my phone, and it failed. I then tried every RUU I could find, all failed. I tried a full firmware update to 4.13 via PJ75IMG.zip on the SD card, which failed.
The repair process that worked for my situation...
Once I focused on the HBOOT as a potential issue, I found this thread: http://forum.xda-developers.com/showthread.php?p=40848479#post40848479
Quite simply, MeanBean 3.09 worked as advertised, and my phone has booted into a ROM for the first time in days! A HUGE thanks to both Magnum_Enforcer and mikeyxda.
Specific phone information
TAMPERED
UNLOCKED
JEWEL PVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.13.11.0830
OpenDSP-v31.1.0.45.0815
eMMC-boot
Oct 18 2012, 15:46:20
IMAGE CRC
rpm: 0xBC1CB8D
sbl1: 0x507A9B32
sbl2: 0xEAF345D0
sbl3: 0xD5BB18AD
tz: 0xFB084399
radio: 0xC78A66EB
boot: 0xB683E2D
recovery: 0xB47A92E4
system: 0x376A0C9B
Software Version Reported by RUU: 3.17.651.5
Glad to help:thumbup:
Sent from my HTC device
I'm going to keep this log going, since I think quite a few people will follow a similar path as I'm following.
Just tried to achieve S-OFF with the new MeanBean ROM I'm running.
First attempt: Firewater
All of the steps went exactly as expected. The command line dialog was amusing, and ended in "nasty, needs a chaser" or something and rebooted to the ROM. Once rebooted into recovery to verify s-off status, S-ON is reported.
Second attempt: Rumrunner
More interesting dialog in the process, and it, too, went smoothly. Rebooted into bootloader and voila...S-OFF achieved.
Installed Dirty Unicorns 4.4.4
So, after the first day's use I've come to realize that my PRL needs updating and the Dirty Unicorn 4.4.4 ("du_jewel_4.4.4_20140621-0657") ROM doesn't have a 'Update PRL' function as far as I can tell. I backed up DU 4.4.4 and restored MeanBean, updated the PRL, and restored back into DU 4.4.4 with ease.
After using DU for a week, I've come to realize it's fairly unstable. I'll be looking for a different rom soon.
OMG!!!! FINALLY!!!
I've been reading and reading and pulling my hair out for 3 days after attempting to load a custom Rom on my Evo 4G LTE.
I have almost exactly the same situation/experience as you did. I was able to get the CyanogenMod to load but for the life of I can't get any gapps installed. I've tried loading from TWRP and the SDcard to no avail. It looks like it flashes fine but when I reboot the phone no apps are installed. I like CM 10.2.0 but I need the Google apps. Right now I'm missing so many things like contacts, etc. I've tried to install Google Play and just download each app individually but it crashes on start. I'm really feeling lost here and helpless. I never had problems like this with my original EVO or EVO 3D. Tried to go back to stock using Sprint RUU's but nothing works...
I've highlighted my differences in RED.
Is there anyway you could explain your method to get your EVO S-off in more detail? Is this the problem?
SethW said:
The flawed process...
I went through HTC's unlock method to unlock the phone. Then I installed the latest TWRP via fastboot command line (2.7.1.0b as I found in a thread somewhere) (I loaded TWRP 2.7.1.0 which seemed to work) . No problems so far... I then went to install the latest CM build for Jewel (10.2.0 ) through TWRP 2.7.1.0b and it failed (I was able to load CM 10.2.0 through Fast Boot boot.img command) . This marked the first time I'd ever seen a fail message in TWRP. I thought no big deal, I'll restore the backup... The backup was gone (Same here, Backup gone). Now we have problems; phone is stuck in a bootloop (I watched the CyanogenMod screen spin for 2 hours). After reading many threads stating that S-OFF is required to flash their ROM, I tried to achieve that in Windows 7 to no avail through all available means (same here, tried several ways but nothing worked for Windows 7). I then tried the closest RUU for my phone, and it failed (same here). I then tried every RUU I could find, all failed. ( I tried a full firmware update to 4.13 via PJ75IMG.zip on the SD card, which failed.
Specific phone information My Info is exactly the same
TAMPERED
UNLOCKED
JEWEL PVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.13.11.0830
OpenDSP-v31.1.0.45.0815
eMMC-boot
Oct 18 2012, 15:46:20
Software Version Reported by RUU: 3.17.651.5
Click to expand...
Click to collapse
airdog99 said:
Is there anyway you could explain your method to get your EVO S-off in more detail? Is this the problem?
Click to expand...
Click to collapse
I just ran the program as it specified. Make sure your drivers are installed correctly... that step usually caught me up because some Android device drivers conflicted with some of my other Android device drivers.
Hi everyone. New to the forum and new to flashing etc. I have been playing with my phone for a couple of nights now but finally gave in and think I need to ask for help.
Here is a bit of background info so far. The last few weeks my One X+ has been suffering from getting stuck coming out of airplane mode. I am currently using an old Desire HD so thought I have nothing to lose by trying to fix the +.
I have managed so far to unlock the bootloader and root the phone. I have flashed TWRP and created a backup.
I have tried to load Android Revolution 8 which complete successfully along with the boot image but when the phone starts I get the HTC splash screen (quietly Brilliant & One X Beats Audio) but it then goes to just HTC then the phone turns itself off.
Have tried a couple of time but end up having to flash my recovery to revert back to how it was.
I feel I may be missing something and would appreciate it if someone could help me out.
Many Thanks :good:
Battery empty?
Sent from my Find 5 using Tapatalk
Lloir said:
Battery empty?
Sent from my Find 5 using Tapatalk
Click to expand...
Click to collapse
No I don't think so. Like I say I have had a few goes at it now and from reading some of the guides on here which say it is important to make sure it has plenty of charge, I have made sure it is well charged before starting.
If it helps, here is some info phone the phone:
HTC One X+
CID-HTC__001
ENRC2B
HBOOT-1.72.0000
Model ID-PM3511000
Have you tried doing a full wipe before or during flashing ARHD? Can you still get into the bootloader or recovery? I had similar problem, changed the cable then flashed the boot image again.
qasimrb said:
Have you tried doing a full wipe before or during flashing ARHD? Can you still get into the bootloader or recovery? I had similar problem, changed the cable then flashed the boot image again.
Click to expand...
Click to collapse
I have done a wipe yes. I have been picking my way through these guides which all have small differences.
http://forum.xda-developers.com/showthread.php?t=2066390
http://forum.xda-developers.com/showthread.php?t=1987885
http://forum.xda-developers.com/showthread.php?t=1995685
Yes I can still access the bootloader and TWRP recovery. The phone is currently restored back to how it was originally.
Are you flashing the boot image before or after you install the rom? With the ARHD he recommends flashing his firmware.zip before flashing the rom.
But from what I remember when my phone was stuck on the splash screen I went back into the bootloader, used another cable and flashed the firmware.zip again, restarted it and it was fine.
Info when I'm in bootloader is:
***UNLOCKED***
ENRC2B_U S-ON
HBOOT-1.30
CPLD- None
MICROP- None
RADIO- None
(Don't know why it says "none" next to radio, network etc is fine, Vodafone UK)
qasimrb said:
Are you flashing the boot image before or after you install the rom? With the ARHD he recommends flashing his firmware.zip before flashing the rom.
But from what I remember when my phone was stuck on the splash screen I went back into the bootloader, used another cable and flashed the firmware.zip again, restarted it and it was fine.
Info when I'm in bootloader is:
***UNLOCKED***
ENRC2B_U S-ON
HBOOT-1.30
CPLD- None
MICROP- None
RADIO- None
(Don't know why it says "none" next to radio, network etc is fine, Vodafone UK)
Click to expand...
Click to collapse
I have tried both ways. Flashing the boot image before and after the installing the ROM and both ways reproduce the same effect.
I have read the page where it mentions loading the firmware but as I have just set out about learning the in's and out's of loading ROMS I wasn't sure what this was. I now understand what the boot image is and what the ROM is but take it the firmware is something different. Should loading the firmware be the first step before falshing the boot image and ROM?
I have been over to his download page with the two 401 firmwares which I believe are the ones I require. The only issue I have is, it seems these are earlier versions so wasn't sure they would be correct to use. I cannot check currently as I'm at work but I think I am running firmware version 2.18.401.3.
So which one should I load?
Also here is the info from my bootloader screen:
HTC One X+
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-3.1204.171.33
eMMC-bootmode: disabled
CPU-boomode: disabled
HW Secure Path: enabled
MODEM PATH: OFF
Model ID-PM3511000
Software Number - 2.18.401.3
CID-HTC__001