[Q] Stuck in boot cycle...not a wcdma problem - HTC Rezound

I Have restorted to being the noob that signs up to ask a question...The other day I was driving (pre-root) and I look down to notice my phone had power cycled on its own. I thought it would come back one, boy I was wrong....
It spiralled into endless boot cycle. It would at first reboot get to the 4g screen and then back to the htc...over and over. I was able to get into Hboot, and atempt to do a factory reset that didnt help because it became a endless reboot that way as well.
Now before any of you say "why dont you warranty replace the phone" Im a VZW agent, alas we dont have a warranty on our phones when it comes to our concessions lines...
Now, at that point I said enough is enough and I delved into the world of rooting. I self taught everything within a few hours. I had my phone unlocked and ready to go. I picked Ineffabile (http://forum.xda-developers.com/showthread.php?t=1420513) to use as a rom, I followed the procedure to a T it installed correctly, but then when it came back on everything seemed to work fine...for about 5 minutes and then it happened agian a power cycle all over again. and again...and again. It now comes on works for about 5mins and then reboots.
Im at a complete loss at this point I have gone back into the SD card and deleted the ph98 file etc.... I just dont know what to do. I need this phone to work.
Any help is appreciated Thank you so much!

I know you said it's not the wcdma problem but will your phone stay booted with the back cover off?
Else I'd ruu back to stock. Could try the different radios and see if it helps.
If you want to try the older radios and are on the OTA you'll have to hexedit you mainver. There's a guide if you look.

older radios? Im still new to this so I applogize...

A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
Here's a couple guides to help you get familiar with rooting stuff:
http://androidforums.com/evo-3d-all-things-root/389787-beginners-guide-rooting-android-devices.html
http://androidforums.com/evo-4g-all-things-root/129648-quick-intro-rooting-those-new-rooting.html
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?

feralicious said:
A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?
Click to expand...
Click to collapse
I dont have insurance =/ and cant get it either. Im trying to find the radios, and what kernal should I be flashing? because I cannot find the one that should match the rom im using.
What I dont understand is why the phone powers on, works for a few moments like nothing is wrong what so ever. Then freezes and reboots.

Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
http://themikmik.com/showthread.php...-Beats-Tweaks-2-01-605-11&p=164906#post164906
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.

feralicious said:
Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.
Click to expand...
Click to collapse
This is a clean SD card, and I didnt create a backup because I couldnt get the phone past Hboot when it was doing boot cycles previous to the root. I re-ruu'd right now. And im starting from scratch. I used clockwork before, Im trying amon ra now.

Related

HELP I think i Bricked

I have a t-bolt rooted with easy root and 'Was" running "the Perfect storm" I was trying to flash the new radio and I think I successfully learned how NOT to flash.
I used opened clockwork chose the option to load from sd card checked the options to wipe the data and chose ok it rebooted wrote the data "or at least looked like it" then rebooted but now it wont go past the splash screen of the clouds. i pulled the batt a couple times but it stops at same place everytime. there is a backup done by cw on it but I dont know what or how to fix it (hopefully it can be fixed)
I am running a duel boot windows vista/ubuntu system if that helps I also have access to work on the files on the card from puter.
Please give me some good news =)
Sorry to hear that. Radio flashes on the Thunderbolt have to be done through "hboot" for future reference.
Anyway, are you still able to access the hboot? (power + volume down) If so, you have hope and you should be able to load a stock or other RUU that way.
im with you man, but my phone won't even start up. I remember i got into hboot once, but i didnt choose restart and chose some other option on accident. Now when i hold power with volume down or just power and power with volume up nothing happens.
Tnx for quick reply,yes I was able to boot to hboot and did a restore so now I'mback to where. I was before I effed. So back to flashing the new radio
Yes this is why flashing radios is not the best thing to do unless you know what you are doing. This is like an RUU and needs to be done in the hboot not CWM. Im not sure if the original post stated this, i hope they did so no one else makes this mistake because this is the easiest way to brick your phone.
CWM can't flash the PG05 files. So you can't brick it.
ITT you find people who flash before reading...
Any idea when I can find the original radio, seems this one is causing random reboots for me.... dont want to loose my Perfect Storm or root, just want to go back to the old radio until the bugs are ironed out a little better?
DarwynZ said:
Any idea when I can find the original radio, seems this one is causing random reboots for me.... dont want to loose my Perfect Storm or root, just want to go back to the old radio until the bugs are ironed out a little better?
Click to expand...
Click to collapse
In this thread
http://forum.xda-developers.com/showthread.php?t=1045081
pmazz850 said:
In this thread
http://forum.xda-developers.com/showthread.php?t=1045081
Click to expand...
Click to collapse
Exactly what I was looking for... THANKS

Rebooting Das BAMF

Have had my T-Bolt for about a month now and just rooted it yesterday! Loving it even more now! I decided to root because I was one of the lucky people that got the update a couple weeks ago and have been having random reboots ever since. I was hoping a different ROM might help with that.
I came from a D1 that I had rooted about a month after it first came out, so I know the basics of using Clockwork.
I put Das BAMF 1.6.3 on yesterday and it seems to be working good. Problem I am having is that I am still getting some random reboots. Not sure if it has to do with the radio installed on the phone or something with the kernal?
It isn't happening all the time. I noticed one last night and one this morning. Suggestions?
Which kernel & radio are you using?
I had the same problem had to switch to a different kernal. It was getting a little to warm causing the phone to reboot. Most noticeably when I used the navigation.
Sorry it took a while for me to respond. Been pretty busy.
After the reboot yesterday, I put a new kernel on there cause I say someone tried that when they got reboots and it fixed the problem.
Here is what I put on, the lean kernel, extremely undervolted - http://forum.xda-developers.com/showthread.php?t=1021404
It seems to be running good. No reboots since I put it on. But then this afternoon I got one. I wasn't doing anything crazy on my phone but it just rebooted out of nowhere. I was on 3G if that matters...???
BUMP
Had one random reboot today. Can't figure out what is doing it. This time I was in the middle of typing a text while on WiFi.
If you are using extremely undervolted try switching to normal. The extremely undervolted setting is also overclocked and may not get enough juice to run properly. see if running normal for a while also has you rebooting.
schmaltzy said:
BUMP
Had one random reboot today. Can't figure out what is doing it. This time I was in the middle of typing a text while on WiFi.
Click to expand...
Click to collapse
I like the BAMF Tom's, but the CM7 alpha for the Tbolt is stable and awesome... no wireless tether yet, but I'm sure it is on the way!
Sent from my ThunderBolt using XDA Premium App
I had random reboot problems after I flashed to the new radio. I switched back to the original radio and have not had a problem at all with bamf 1.6.3 or 1.7.
Sent from my ADR6400L using XDA App
I put the .7cdma and .6lte on and it solved my reboots. Before that I got random reboots and even a couple times where it just shut off. There is a radio thread in the dev section with all the combinations. Been on this radio for weeks and no reboots.
1.6.3 and 1.7bamf not o/c
OK.....need a little help with flashing a new radio....
See, I came form the origional Droid, which was super easy when switching ROMS. Download the ROM you want, throw the zip on the SD, boot into recovery, flash your ROM, good to go!
Seems a little more complicated with the Thunderbolt, so I'm still getting a little use to it.
I went to the post that has all the different radios, but I'm still not exactly sure on how to flash one. Can anyone explain???
schmaltzy said:
OK.....need a little help with flashing a new radio....
See, I came form the origional Droid, which was super easy when switching ROMS. Download the ROM you want, throw the zip on the SD, boot into recovery, flash your ROM, good to go!
Seems a little more complicated with the Thunderbolt, so I'm still getting a little use to it.
I went to the post that has all the different radios, but I'm still not exactly sure on how to flash one. Can anyone explain???
Click to expand...
Click to collapse
Pretty easy actually. Just download the image that you want to use. Make sure it is at the root of your sd card. Boot your phone into Hboot and it will try and load the file automatically at that point.
Tell the phone it's ok to install. Once you have it installed, don't forget to delete the image file from your root or at least rename it. Otherwise if you go back into hboot, it's going to try and install the image again.
Hope that helps.
Dnakaman said:
Pretty easy actually. Just download the image that you want to use. Make sure it is at the root of your sd card. Boot your phone into Hboot and it will try and load the file automatically at that point.
Tell the phone it's ok to install. Once you have it installed, don't forget to delete the image file from your root or at least rename it. Otherwise if you go back into hboot, it's going to try and install the image again.
Hope that helps.
Click to expand...
Click to collapse
How do you get into Hboot?
I'm running Das BAMF 1.7 Remix and I get a "bootloader" option under the restart. Is that the same thing??
Couple of ways.
If your rom supports it. You can hold the power button down and pick restart and then pick bootloader.
or if your phone is powered down, just hold the volume down key while holding down the power key and that should get you to the bootloader.
Edit: Make sure that your image is named PG05IMG at the root of your sd card.
It's the LTE radio causing reboots, so from http://forum.xda-developers.com/showthread.php?t=1045081 select either the second or fourth option. Any combo that has the 1.12.605.6 LTE radio. Also don't forget to rename it PG05img.zip and put it on the root of your sd card.
If your in hboot and it doesn't recognize the file, make sure it's not named PG05img.zip.zip, changing the name in windows will cause that to happen.
DixonToofar said:
It's the LTE radio causing reboots, so from http://forum.xda-developers.com/showthread.php?t=1045081 select either the second or fourth option. Any combo that has the 1.12.605.6 LTE radio. Also don't forget to rename it PG05img.zip and put it on the root of your sd card.
If your in hboot and it doesn't recognize the file, make sure it's not named PG05img.zip.zip, changing the name in windows will cause that to happen.
Click to expand...
Click to collapse
Thanks Dixon.
I was one of the lucky few that was getting quite a few reboots before I was rooted when Verizon sent out the update. Is it the LTE radio the cause for sure? I know there was a lot of speculation on what was the actual cause, but then I rooted so I stopped following the problem.
Does it matter that I have my LTE turned off all the time? I don't live in an LTE area so I never have it on, yet I still get 1 or 2 random reboots a day. Still better than the 6-8 I was getting when I wasn't rooted!
schmaltzy said:
Thanks Dixon.
I was one of the lucky few that was getting quite a few reboots before I was rooted when Verizon sent out the update. Is it the LTE radio the cause for sure? I know there was a lot of speculation on what was the actual cause, but then I rooted so I stopped following the problem.
Does it matter that I have my LTE turned off all the time? I don't live in an LTE area so I never have it on, yet I still get 1 or 2 random reboots a day. Still better than the 6-8 I was getting when I wasn't rooted!
Click to expand...
Click to collapse
I don't know if anyone can say for certain, but many people(Myself included) experienced reboots after switching to the updated .7 radios. After switching back to the .6 LTE radio, I haven't had a single reboot in weeks, and many others have had the same results. Whether it is the cause or not, switching seems to solve the problem. If it doesn't, then chances are something else is causing them on your phone, but you won't know until you try.
I usually have LTE turned off as well, and I know at least a couple of my reboots happened while it was turned off. Whatever the cause, it doesn't seem to be related to the use of the radio. Just having the .7 version loaded seems to be enough.
Should I make a Nandroid backup before I flash a new radio? Or would that not back anything up as far as the radio goes?
schmaltzy said:
Should I make a Nandroid backup before I flash a new radio? Or would that not back anything up as far as the radio goes?
Click to expand...
Click to collapse
I would always make sure you have a recent Nandroid backup before flashing anything. It won't back up the radio itself, but you never know what else could go wrong.
OK, last question....hopefully!!
There was just a new radio that was released. Looks like it is a new Gingerbread radio. Now I'm thinking about just throwing a gingerbread ROM and do everything once.
Question is....if I switch from a Froyo ROM to a GB ROM, in what order do I flash the ROM/Radio??
1) Backup, Wipe data/cache, flash ROM, boot into HBOOT, then flash the new radio?
or
2) Backup, boot into HBOOT, flash new radio, boot into recovery, wipe, flash ROM?
Doesn't matter. Some will tell you one way, others will tell you the other way.
From what I can tell, either way works. I've done both with the new radio and have had no issues either way.
Happy Flashing!

[Q] rezound boot loop/ *#*# not working

So i would like to apologize first off by saying i am a complete and total noob in every sense of the word. This is the first time trying to root any phone. ok so heres the deal, the phone powers up... FINALLY... and will load to the homescreen but reboots the device. I used the BAMF ICS rom and put in a PGIMGnewfirmwarepeople.zip... ive tried to do the *#*# but as soon as i bring it up i can only get maybe the * or at best the *# but then it reboots itself. I mess with cars on a daily basis but unlike a car part i cant bang or heat up the phone to get the desired result. i attempted to do this since i saw the video on the rezound redifined 4.0.3 ICS with nova launcher.. it was a video by driodzero?
i have no idea where to go from here... i would greatly appreciate any help anyone can provide
If it is indeed a network bootloop, try booting with the backpate removed. As long as the network signal isn't overly strong it should be able to get you in.
i think that was one of the things i did... i tried to let it boot with the back off, then with the back off and SIM card out... but to no avail. is there a way to somehow cmd prompt the *#*# in order to switch the problem... i dont know if this helps but it is S-ON
No SIM means no signal, which means no network bootloop. Must be another cause. Looking at the Bamf ICS thread, did you upgrade your firmware to ICS properly first. Hmm.
i will go back and look.. the problem is it will not let be go back and down grade img file...
twd420 said:
i will go back and look.. the problem is it will not let be go back and down grade img file...
Click to expand...
Click to collapse
Yeah, S-off is suggested eventually since it allows you to downgrade from the leaks. Risk of perma-brick in certain situations, like flashing a bad download of radios. But it helps more than hurts to have that freedom.
On S-on you also need to make sure the boot.img gets flashed seperate in the bootloader for a given ROM.
thanx i will try the wire trick to get it to S-OFF but right now i cant even get the phone to power up to the home screen
You can check the hboot/radio version in the bootloader to confirm firmware version. See what it says there.
Would attempt a clean reinstall of the ROM if it is indeed on ICS (hboot 2.21 or 2.25) firmware proper.
Then make sure to wipe system, davik-cache and cache, flash ROM twice, the patch Joelz has, and flash the boot.img as a PH98IMG.zip in bootloader. Then boot the ROM up.
i would definitely try that except i can not get it to power on, nor can i get it to charge... i think its bricked, since ive even gone to the standard battery as well as using different chargers. i greatly appreciate your insight
twd420 said:
i would definitely try that except i can not get it to power on, nor can i get it to charge... i think its bricked, since ive even gone to the standard battery as well as using different chargers. i greatly appreciate your insight
Click to expand...
Click to collapse
Did you use ClockworkMod by any chance? My first Rezzy charging capability fried on its own eventually, but aside from hardware failure: that recovery has been reported to have issues when battery drains down...

[Q] Unexpected Brick

About a month ago I rooted a HTC EVO 4G LTE, installed the recovery with touch screen and Cyanogenmod nighties.
It worked great, including tethering on Sprint.
Last week an update to latest Cyanogenmod was made. Phone worked normally, until today when screen stopped responding completely (physical buttons were working), including after rebooting. On a second reboot phone was stuck on a boot loop.
Went into bootloader mode and tried to go to recovery. It would boot loop again. Noted that it said UNLOCKED S-ON (I thought it was supposed to be S-OFF). I tried flashing the boot.img from latest Cyanogenmod. Nothing. Tried reseting from the menu. Tried more things. Nothing worked. So I downloaded and used the latest version of RUU after fastboot oem lock. RUU was successful (no error, phone no longer displays HTC developer message), however it's still stuck on the boot loop. I thought RUU would restore it completely.
What am I missing?
Read here
http://forum.xda-developers.com/showthread.php?t=2084633
And here
http://forum.xda-developers.com/showthread.php?t=2097150
#Root-Hack_Mod*Always=SG3
I followed the instructions.
Then I tried all RUU that I had and always got Error 140.
Finally, found in a rooting pack 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 which worked to restore.
However, the phone is still in the same state. What do I do?
How long did you give the phone to boot.? Also did you flash the firmware zip after you relocked your boot loader?
#Root-Hack_Mod*Always=SG3
Phone is RELOCKED.
What I did:
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
Then used that RUU to restore. After this I left the phone without touching it for about ten minutes, but it keeps restarting (never passes booting stage).
Try this. Remove your sd. Then back up all your data. Then format it threw your PC and return it to factory defaults. Then put it back in your phone and redo the steps. Also were did you get the ruu your using from ?? Also if that fails to work look here
http://forum.xda-developers.com/showthread.php?t=2045935
And try the firmware zip with the stock recovery. Then run the ruu. Hope this helps.
#Root-Hack_Mod*Always=SG3
Does it matter if the SD is in?
So, I took out the SD card, repeated those three steps and I should use RUU again.
The RUU is from 3.15_RUU_PLUS_ROOT.zip.
I'm going to try again now with no SD.
Same result after trying without SD card. Also I did flashboot flash zip
Code:
PJ75IMG_3.15.651.6-firmware.zip
from the link you provided without help.
PepeJones said:
Does it matter if the SD is in?
So, I took out the SD card, repeated those three steps and I should use RUU again.
The RUU is from 3.15_RUU_PLUS_ROOT.zip.
I'm going to try again now with no SD.
Click to expand...
Click to collapse
Yes the sd card should be in your phone. Also your trying to go back to stock so using the ruu that's stock with root might be the issue given your phones current state. I'll try and find you just the stock ruu with no root, unless you have one or if you know were one is download it and run it. Also when I posted about the SD card you were only supposed to remove it to "back up your data" and then "format" it. After you have formatted it then place it back into your phone. I'm not aware of any potential issues with running a ruu without the SD card being in the phone, however I would strongly suggest always running the ruu with the SD in the phone. Its what I've always done. Also make sure that your battery is over 75%. And did you flash the one with the stock recovery? There are several firmware zips on that thread but the one with the stock recovery is the one I suggested you try. And I'm not sure what the "without help" post is about. I'll help you as much as I can and I'm sure if I don't reply to you right away that there are more than enough knowledgeable members in this forum to help you as well. Take in mind that phones are so easy to screw up but it might take some time to get it back up and running. But troubleshooting is all part of the process.
#Root-Hack_Mod*Always=SG3
I'll try it again with the SD card in the phone. No, the RUU I'm using it's in a pack for rooting and updating. I don't think it's modified at all. I don't even think RUU can be altered and signed anyway. I'll search for another RUU again.
Yes, the one that I flashed is
Code:
PJ75IMG - Firmware zip with hBoot and stock recovery (signature intact)
http://d-h.st/sKO (MD5: 0d8f9d65e29c1c824654bf88b9438f15)
and I had enough battery. (It was supposed to be without luck not without help).
So, I'll flash the above mentioned PJ75IMG, then use the RUU (I'll search for one that's in no pack, but I'm confident it's not altered) - all this with the SD card inside.
Thanks for your help.
laie1472 said:
Yes the sd card should be in your phone. Also your trying to go back to stock so using the ruu that's stock with root might be the issue given your phones current state. I'll try and find you just the stock ruu with no root, unless you have one or if you know were one is download it and run it. Also when I posted about the SD card you were only supposed to remove it to "back up your data" and then "format" it. After you have formatted it then place it back into your phone. I'm not aware of any potential issues with running a ruu without the SD card being in the phone, however I would strongly suggest always running the ruu with the SD in the phone. Its what I've always done. Also make sure that your battery is over 75%. And did you flash the one with the stock recovery? There are several firmware zips on that thread but the one with the stock recovery is the one I suggested you try. And I'm not sure what the "without help" post is about. I'll help you as much as I can and I'm sure if I don't reply to you right away that there are more than enough knowledgeable members in this forum to help you as well. Take in mind that phones are so easy to screw up but it might take some time to get it back up and running. But troubleshooting is all part of the process.
#Root-Hack_Mod*Always=SG3
Click to expand...
Click to collapse
PepeJones said:
I'll try it again with the SD card in the phone. No, the RUU I'm using it's in a pack for rooting and updating. I don't think it's modified at all. I don't even think RUU can be altered and signed anyway. I'll search for another RUU again.
Yes, the one that I flashed is
Code:
PJ75IMG - Firmware zip with hBoot and stock recovery (signature intact)
http://d-h.st/sKO (MD5: 0d8f9d65e29c1c824654bf88b9438f15)
and I had enough battery. (It was supposed to be without luck not without help).
So, I'll flash the above mentioned PJ75IMG, then use the RUU (I'll search for one that's in no pack, but I'm confident it's not altered) - all this with the SD card inside.
Thanks for your help.
Click to expand...
Click to collapse
You can't flash a PJ75IMG.zip unless you are S-OFF and the file you posted above is not an RUU it's just the updated firmware
It didn't work.
So I followed the steps from this link.
After using HTCDev to unlock the phone and I try to open RabiesShot, it reboots the phone but it's not able to connect. Sometimes the phone goes in a loop, sometimes the phone boots (it did boot twice). However, even when it booted, the screen didn't work at all, which is the original problem.
Right now the phone is ON but the only thing that works is the power and volume buttons (screen and soft buttons do not work). I've also noticed the phone reboots alone.
Any ideas left?
(This is my friend's phone. Anyway, I'll convince anyone to stay away from HTC. Nexus is so much better than this...)
Its not the phone its the user. I've never heard of a phone hacking itself. So usually the fault is the owner of the device and not the device itself. And In this case I'd say its user error. Also I'm lost as in what your doing at the moment. I thought you were trying to go back to stock? Now you post says your basically trying to obtain s-off. If this is the case then you make it extremely difficult to try and pin point what's actually the issue with your firends phone because you jump methods. So at this point exactly what are you trying to do ? Are you trying to go back to stock to gain s-off ?? Also if you come here to receive help with your issue you should always try the posted methods first so the member that's helping you is aware of what steps your taking and what your going to do. If not then it becomes difficult to help you.
#Root-Hack_Mod*Always=SG3
laie1472 said:
Its not the phone its the user. I've never heard of a phone hacking itself. So usually the fault is the owner of the device and not the device itself. And In this case I'd say its user error. Also I'm lost as in what your doing at the moment. I thought you were trying to go back to stock? Now you post says your basically trying to obtain s-off. If this is the case then you make it extremely difficult to try and pin point what's actually the issue with your firends phone because you jump methods. So at this point exactly what are you trying to do ? Are you trying to go back to stock to gain s-off ?? Also if you come here to receive help with your issue you should always try the posted methods first so the member that's helping you is aware of what steps your taking and what your going to do. If not then it becomes difficult to help you.
#Root-Hack_Mod*Always=SG3
Click to expand...
Click to collapse
Not hacked itself, just not working. At least, that's what I've been told. Right now I'm trying to make it stock, but since what you proposed didn't work I tried different things such as obtaining S-OFF (no success).
The comment regarding HTC wasn't necessarily related to this case but in general. Just look how miserably is the process to just obtain root and unlock the bootloader. And in many cases is not even possible until some exploit is found. Why...? HTC used to be great.
I'm just trying to get this phone work again. Initial idea was to go stock, since it seems logical that it should be straight forward.
So I tried everything you have posted, including the last instructions you left me (backup everything off SD, deleted everything and inserted SD in the phone, then repeated the process).
Thanks for your help.
I understand your frustration about the issues with the phone in its current state. However if done correctly gaining root/s-off can be achieved in less that an hour. I do realize the fact that even if guides are followed to the exact directions that issues still occur. But that's the risk you take when you modify you phone. Your aware of this I'm sure. However that's why xda is a great website. Not only can you get the software to modify your phone, you can also get help in case the process didn't go the way it should have. You can't dispute the fact that there are more than a few members with the evo-lte who had no problems at all with gaining root or s-off. As far as the steps I suggested there was no guarantee that they would work its just the process of trouble shooting to see what will work. If you don't mind can you post the exacts steps you took before you tried to achieve s-off ? Also can you post the links to the exact ruu and firmware you last used as well.? Also if the phone is on try powering it down and attempt to boot into the boot loader. If your successful then try factory reset.
#Root-Hack_Mod*Always=SG3

[Q] New ROM, Cell not Working

Hey guys,
Just rooted my phone today, and have had a pretty bumpy time. I've made it through most of it, but am having trouble getting a new ROM installed (NilsP's Business ICS Sense 6.4). Basically, install is going fine, but when I make it to the ROM, I get no cell signal, no data, and gps won't turn on.
I'm running S-on, and the install will complete and it will automatically reboot to hboot for the kernel. However, nothing happens that indicates that the kernel installed. Upon reboot, the ROM will open, I'll skip through the setup wizard, and once out cell, data, and gps fail to turn on.
I tried placing the kernel's zip file directly onto my SD card's root drive. Once booted to hboot, the kernel will install. However, problem will persist. I updated to 6.4 OTA with no change. I tried disabling the Fast Boot option and cycled various settings, as suggested in NilsP's original thread. Prior to rooting, I had the most current update from Verizon (pushed through about a week or two ago). I even tried installing with the s-off option, which gave the same result.
I spent about five hours today searching these forums, as well as others, for a similar issue but was unable to find one. Until I figure out a way forward. I feel like I'm missing something simple, since I'm almost there! As I said, I'm a newbie, so forgive me if I misused any terms. Any and all help would be greatly appreciated!
flash stock recovery and do factory reset.
Damasterjj said:
flash stock recovery and do factory reset.
Click to expand...
Click to collapse
from the HBOOT
But first... did you put the back cover on again? The antennas are in there so you won't get any service without it on.
feralicious said:
But first... did you put the back cover on again? The antennas are in there so you won't get any service without it on.
Click to expand...
Click to collapse
Yup, tried with the lid back on, too. Figured there must have been an important circuit with all those contacts in there.
I'll try the reset from HBoot later this evening. I wiped every time I tried to reflash the OS, though only from the recovery menu. I'll let you know how it goes.
Thanks for the help guys, it ended up installing just fine after a factory reset from Hboot. Now I'm running into the same Play Services issue as everyone else using this ROM. Go figure. I'll monitor NilsP's original ROM thread for a solution. Looks like he's working on it already.

Categories

Resources