Related
Hello all, I flashed thE Twisted Sence 1.5.1 ROM this afternoon and at about 8:30pm my phone completely froze and I could not do anything at all. Pulled the battery and all I can get is the HTC Logo on the White Background.
I can get into HBOOT and I have been trying everything I can to get the phone to work again but no dice.
Clockwork doesnt want to load for some reason but after letting my phone sit for about 15 minutes one time it did load into Clockwork. So I wiped the system partition/cache/dalvik and reloaded the ROM again.
After 12 minutes of waiting the phone finally started to load into the OS but it was so sloooooooowwwwww. It would not even recoginize any gestures on the touch screen.
So I rebooted again and it is stuck on the HTC Boot Screen again.
So I was thinking that I might be able to go back to the rooted stock so I went to http://forum.xda-developers.com/showthread.php?t=996616 and got the PG05IMG_stock.zip from there and renamed to PG05IMG.ZIP and had HBOOT load that.
Again went through a super long start up process and now the phone is at the unlock screen and again I cannot do anything at all. It has the correct time and it is only showing 1X for data nothing else and I am in a 4G LTE zone. I called myself from a landline and the phone rings but I cannot answer it since the touchscreen is un-responsive.
So is there any reason why my phone would be running super slow and doing what it is? I don't know if it is a Kernel thing or a Radio thing or what.
Maybe a stock kernel would help if anyone has it.
Any help would be much apperaicted as I have a brick that lights up basically. Phone isn't useable at all. =(
Reboot into recovery and try a different kernel. Or just restore an earlier state.
^_^_^'s tbolt
Load another ROM. Any rom you load should come with a new kernel. If that fails, try a different radio.
Sent from Phoenix, AZ running Thunderbolt rooted Das BAMF Remix 1.5
Does anyone know a way to go back to locked Stock through HBOOT or Clockwork without being able to boot the phone?
If I can get back to S-ON I will return the phone to Verizon since I am within my 30 days.
It has to be a kernel issue. The radio may be in conflict with something else, because all phones are different, but just restore a backup you've made, and try flashing the rom with a different kernel. If it was stable, something had to occur for that to change obviously.
If I had a backup to use then I would give that a shot. =( Shame on me I know.
webbyz said:
Does anyone know a way to go back to locked Stock through HBOOT or Clockwork without being able to boot the phone?
If I can get back to S-ON I will return the phone to Verizon since I am within my 30 days.
Click to expand...
Click to collapse
You can do it through ADB.
adb reboot recovery
now you know to make a nandroid backup prior to reflashing anything
/slaps OP with trout
Hello. I have a photon that was rooted and unlocked and all that. The thing is it somehow got the newest Motorola update. The question i have is can i reroot it. I would love to be able to run a different OS than just the stock one. Can someone help me here or do i have a nice paperweight
yes you can re-root it using the torpedo method. but unfortunately no unlocking at this time
foxsdaddy67 said:
yes you can re-root it using the torpedo method. but unfortunately no unlocking at this time
Click to expand...
Click to collapse
What he means is, you need to be unlocked to install a custom rom with custom kernel and you can no longer unlock. You have two rom options while still locked, but both are based off the blur you already have. You can still root, though.
from what I understand you can use boostrap recovery to install ROMs. i've yet to try it myself but others have used it
foxsdaddy67 said:
from what I understand you can use boostrap recovery to install ROMs. i've yet to try it myself but others have used it
Click to expand...
Click to collapse
Only roms without a custom kernel assuming you are still locked while using it.
Sorry.. but with "locked" you say.. bootloader, o gsm? In general at forum.. lock refers bl?
Sry, for my english :\
Thanks!
Enano08 said:
Sorry.. but with "locked" you say.. bootloader, o gsm? In general at forum.. lock refers bl?
Sry, for my english :\
Thanks!
Click to expand...
Click to collapse
Yes I'm referring to your bootloader. The gsm lock you are referring to only exists in the united states.
thanks for the info guys, well i did get the phone rooted and super user restored, see the thing is the phone was flashed and programmed for page plus, its still running on page plus service but i had 2 problems one being the nag screen to activate the phone for sprint and its constantly in roaming, i called page plus and they say yeah that will happen and no i wont be charged for it, i would be all happy if i could get the roaming off, i did however get rid of the sprint activation by deleting a apk called SprintOMADM,apk. now im not totally sure i need that apk or not but its gone now and i have no nag screen to activate it, it still makes calls just fine but im not sure im totally getting all my incoming phone calls or any notifications for voice mail, any sugestions on how i might be able to get rid of some of this stuff, like i said it was flashed rooted and unlocked before, i did use when i first had it that remote squad software but now it says it cant even read the phone, i was also told by them its probably that awsome new update 2.35. thanks alot again for your responses and ill keep popping in and out of here to see more responses
well disreguard the last post, I had some app downloaded on my phone used to flash roms... well basically what happened i restarted my phone and the app booted before the phone started and it said flash rom from zip file so i selected one that i downloaded here, and thinking it wouldnt work i selected it and hit ok, well it worked alright now the phone says Failed to boot 2, and just shows starting in RSD mode, now im screwed, I shouldnt have done that, I figured it was locked and wouldnt work now the phone is broke how can i get it back just to stock the way it was or am i totally screwed
mamba316 said:
well disreguard the last post, I had some app downloaded on my phone used to flash roms... well basically what happened i restarted my phone and the app booted before the phone started and it said flash rom from zip file so i selected one that i downloaded here, and thinking it wouldnt work i selected it and hit ok, well it worked alright now the phone says Failed to boot 2, and just shows starting in RSD mode, now im screwed, I shouldnt have done that, I figured it was locked and wouldnt work now the phone is broke how can i get it back just to stock the way it was or am i totally screwed
Click to expand...
Click to collapse
What rom did you flash and what little application did you use to flash it with? You're probably not screwed, we just need a bit of information on what steps you took.
Acvice said:
What rom did you flash and what little application did you use to flash it with? You're probably not screwed, we just need a bit of information on what steps you took.
Click to expand...
Click to collapse
well when i got that awsome update 2.35 from my son clicking yes to it, i tried just about any roms to get the phone back, first it was the electrify rom which i later find out dumb mistake on my part, anyway now and i mean right now i flashed the phone with rsd lite using the electrify rom 1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US..... from there i rooted the phone using the torpedo method, then i installed busybox and i forget which method i used but anyway it was all done in fastboot, once i got all that installed i downloaded a apk file system recovery which is MOTODX2_Bootstrap_signed.apk. plugged in the charger and booted up the system recovery or the bootstrap which ever you call it, and went into advanced and did a dalvik wipe i even hit fix permissions, i then hit go back and did a data- factory clear wipe, then went into install zip from sd card and i first used MOF.2.3.5.ish,v1.4.zip and that installed fine the problems i had was sometimes when i would do that i would get failed to boot 2 screen but i just used the unbrick zip that i downloaded here if anyone wants the name or link let me know, anyway.. once booted up with the MOF ish zip it would load fine but wouldnt save any settings or find any APNs or connect to any wireless networks in my house, but the wireless problem was clear it said error on it, so i knew the problem on that was it wasnt working derr. So this story is getting long now. anyway i then rebooted and turned on the bootstrap slash system recovery utility, and i installed first 2.3.x_libmoto_ril.so_198_7.zip and it aborted the install and failed. i then tried the next one in line which was 2.3.x_libmoto_ril.so_254_12.zip and that one installed fine so i rebooted and i got the failed to boot 2 screen and i did the unbrick sbf file on rsd lite and it booted fine, though still no saving of the settings and no wifi no cell service and no text or anything, I kept RSD lite open and i tried one more thing, 2.3.5sv2_198_7_radio.sbf and flashed it, the wifi for the house started working and i started getting bars on my cell service yay, well atleast i thought yay this is after weeks of not having a cell. well i thought all is well im done and fixed. NOPE im not fixed when i try and dial a number or even activate my phone i get nothing, no dial buzzing sounds like you get normally, no any kinds of sounds the call eventually times out and says called failed retry or cancel the call, i hit retry and i get the same thing. i even tried flashing the radio to 2.3.5sv2_254_12_radio. when i used that one it would save settings but i wouldnt get any cell signal or anything. so im back to square one. I need help. this phone is about 2 steps of getting thrown out the window. I just strated working again and i need this phone to call back customers and i cant afford a regular carrier so im on pageplus the phone was originally flashed through remote squad and worked great until i let my youngest son play a SNES emulator on it and it exited out of the program for some reason and it wanted to do the system update and he hit yes and it installed and screwed up everything. All i want now is to get the phone back to somewhat normal, I can use RSD lite, CDMA workshop, QPST, DFS 4.0.0.5 and a couple others if need be i can download anything i just need to be told what files i need and what i dont need to get the phone back to normal, cuz if i dont get this phone back to normal im just going to not get another pageplus card and throw the phone away and ill be back to not being able to work. thanks to all that has responded to the post here i really do apreciate the time you all have taken to help. sorry it took so long to get back to any of you here but i still need urgent help here badly please and thank you for your time to read this i hope i gave you all the info you needed to help me
I just write this.
Calm down, read the 2.3.5 sv2 custom sbf thread one more time and start from the beginning with unbrick steps. Everytime you do that process, you will understand it more and more and your phone will start to work again. Believe me.
peetr_ said:
I just write this.
Calm down, read the 2.3.5 sv2 custom sbf thread one more time and start from the beginning with unbrick steps. Everytime you do that process, you will understand it more and more and your phone will start to work again. Believe me.
Click to expand...
Click to collapse
im getting ready to try this now thank you
mamba316 said:
well when i got that awsome update 2.35 from my son clicking yes to it, i tried just about any roms to get the phone back, first it was the electrify rom which i later find out dumb mistake on my part, anyway now and i mean right now i flashed the phone with rsd lite using the electrify rom 1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US..... from there i rooted the phone using the torpedo method, then i installed busybox and i forget which method i used but anyway it was all done in fastboot, once i got all that installed i downloaded a apk file system recovery which is MOTODX2_Bootstrap_signed.apk. plugged in the charger and booted up the system recovery or the bootstrap which ever you call it, and went into advanced and did a dalvik wipe i even hit fix permissions, i then hit go back and did a data- factory clear wipe, then went into install zip from sd card and i first used MOF.2.3.5.ish,v1.4.zip and that installed fine the problems i had was sometimes when i would do that i would get failed to boot 2 screen but i just used the unbrick zip that i downloaded here if anyone wants the name or link let me know, anyway.. once booted up with the MOF ish zip it would load fine but wouldnt save any settings or find any APNs or connect to any wireless networks in my house, but the wireless problem was clear it said error on it, so i knew the problem on that was it wasnt working derr. So this story is getting long now. anyway i then rebooted and turned on the bootstrap slash system recovery utility, and i installed first 2.3.x_libmoto_ril.so_198_7.zip and it aborted the install and failed. i then tried the next one in line which was 2.3.x_libmoto_ril.so_254_12.zip and that one installed fine so i rebooted and i got the failed to boot 2 screen and i did the unbrick sbf file on rsd lite and it booted fine, though still no saving of the settings and no wifi no cell service and no text or anything, I kept RSD lite open and i tried one more thing, 2.3.5sv2_198_7_radio.sbf and flashed it, the wifi for the house started working and i started getting bars on my cell service yay, well atleast i thought yay this is after weeks of not having a cell. well i thought all is well im done and fixed. NOPE im not fixed when i try and dial a number or even activate my phone i get nothing, no dial buzzing sounds like you get normally, no any kinds of sounds the call eventually times out and says called failed retry or cancel the call, i hit retry and i get the same thing. i even tried flashing the radio to 2.3.5sv2_254_12_radio. when i used that one it would save settings but i wouldnt get any cell signal or anything. so im back to square one. I need help. this phone is about 2 steps of getting thrown out the window. I just strated working again and i need this phone to call back customers and i cant afford a regular carrier so im on pageplus the phone was originally flashed through remote squad and worked great until i let my youngest son play a SNES emulator on it and it exited out of the program for some reason and it wanted to do the system update and he hit yes and it installed and screwed up everything. All i want now is to get the phone back to somewhat normal, I can use RSD lite, CDMA workshop, QPST, DFS 4.0.0.5 and a couple others if need be i can download anything i just need to be told what files i need and what i dont need to get the phone back to normal, cuz if i dont get this phone back to normal im just going to not get another pageplus card and throw the phone away and ill be back to not being able to work. thanks to all that has responded to the post here i really do apreciate the time you all have taken to help. sorry it took so long to get back to any of you here but i still need urgent help here badly please and thank you for your time to read this i hope i gave you all the info you needed to help me
Click to expand...
Click to collapse
Wow - just Wow. Unreadable. You are truly fortunate that someone actually read that and offered advice.
yes it was a long post, yes it was all jumbled together, anyway i did all the stuff recccommended and it works. the only problem im having now is, its still not lockig onto the right cell tower or something here where i live.
I Have tried Remote Squads Full Flash and other ways of manually programming it and for some reason I cannot get it to lock onto verizon towers, its like it has me permenantly locked onto sprint. when i drive down the road about 8 miles or so i can go down at the sheetz in my area and I get locked onto a verizon tower there but as soon as i move from that area I lose it and it goes back to sprint towers, I talked with Pageplus and they told me some stuff about what SID and NID i should have in but im not sure if the info was correct they told me they didnt know pennsylvavnia all that good but here is some numbers to try .. im about to melt this thing
Try roam control.
Sent from my MB855 using xda premium
I have searched the forums for a few hours and have not found a problem close to mine. here's the story:
phone was charged to just about 100% when this happened.
HTC Rezound, with Amon Ra recovery, unlocked, rooted, S-ON flashed with Sensless Chaos Red 2.0 and it was working fine.
So I wanted to flash a different kernel. This is where I may have made a mistake. Flashed Rezound Cubed ICS Kernel 2.3.9 and rebooted, it worked but WIFI didnt and the governors weren't available so obviously the kernel wasnt fully installed. Rebooted to fastboot, used fastboot to flash the boot.img for the kernel. This also seemed to work. Phone restarted, went into ROM no problem. Was messing with governors and the phone just shut off. Now it will not turn on, will not charge, won't do squat. Can't get adb to recognize it, nothing. ANY HELP WOULD BE APPRICATED and all replies will be thanked!
First, take the battery out. Let it sit for about 10 minutes.
Put the battery back in and press the volume down and power button until you see the hboot screen. If you get there then go to recovery, wipe and reflash your ROM.
GrayTheWolf said:
First, take the battery out. Let it sit for about 10 minutes.
Put the battery back in and press the volume down and power button until you see the hboot screen. If you get there then go to recovery, wipe and reflash your ROM.
Click to expand...
Click to collapse
did that. let it sit forever. tried to get to hboot. nothing. tried different battery in my phone, no luck.tried different charger. nope. tried my battery in a different phone and it worked fine. took to verizon and they are swapping. new one in the mail. lets hope they don't find out about the whole unlocking, tampering, rooting, flashing business lol.
Thats very odd especially since your s-on and its nearly impossible to brick your phone. Here are some links to 2 ways to unbrick your phone, I have never bricked before and so i have never tried them however. http://forum.xda-developers.com/showthread.php?t=1833530&highlight=unbrick
and http://forum.xda-developers.com/showthread.php?t=1711408 I hope these help. From what i know about S-ON it protects the essential partitions and files that allow the phone to boot such as the bootloader, radios, etc. so that the system doesnt become corrupted and fail to boot. So the only way i can think of your phone bricking is something in the hardware could have died for some odd reason. If you cant get it unbricked your gonna have to take it to verizon to get a replacement.
jon7701 said:
Thats very odd especially since your s-on and its nearly impossible to brick your phone. Here are some links to 2 ways to unbrick your phone, I have never bricked before and so i have never tried them however. http://forum.xda-developers.com/showthread.php?t=1833530&highlight=unbrick
and http://forum.xda-developers.com/showthread.php?t=1711408 I hope these help. From what i know about S-ON it protects the essential partitions and files that allow the phone to boot such as the bootloader, radios, etc. so that the system doesnt become corrupted and fail to boot. So the only way i can think of your phone bricking is something in the hardware could have died for some odd reason. If you cant get it unbricked your gonna have to take it to verizon to get a replacement.
Click to expand...
Click to collapse
i know exactly what you're saying. i think the phone just fried as in hardware malfunction not software. already took it in to verizon and they sent it off. waiting for new one in the mail
techblitz said:
i know exactly what you're saying. i think the phone just fried as in hardware malfunction not software. already took it in to verizon and they sent it off. waiting for new one in the mail
Click to expand...
Click to collapse
Lol i just looked and i didnt see on your post above my previous one that you said you had already taken it to verizon. :silly:
jon7701 said:
Lol i just looked and i didnt see on your post above my previous one that you said you had already taken it to verizon. :silly:
Click to expand...
Click to collapse
it's all good. i already got my replacement.
Ok, I have a rezound, unlocked and rooted with Amon Ra with the superuser binaries updated, all after installing the Global ICS RUU. I've been running this way pretty much since a few days after the Global RUU came out. Never had any problems or issues. Love this phone (except battery life but whatever). This morning before taking it off the charger I had it reboot (which I normally do every few days) and it did not reboot. It got stuck on the white HTC screen. The screen would come on, and then blink for a sec only to stay stuck on the HTC screen. No beats audio boot animation. I'm S-ON by the way. I use Mac so I was never able to get a windows computer to S-off, but I haven't wanted to flash any Roms since my days on the Dinc. I didn't have time to mess with it this morning so I just pulled the battery to shut it off. Now that I have a few minutes, I tried to see if it would boot, and same thing. Pulled the battery again, and powered up into the boot loader. Tried to enter recovery from there, and it just went blank. Pulled battery again, and tried it again. Same blank screen with no response from power button or anything. Now it is completely dead. Won't even go into bootloader. Won't even light up on the charger. SOME times when plugging it in it will light up for 5 seconds, but then turn off. Tried it with the battery out and pluggin it in to get into bootloader that way and nothing.
Is it completely fried? I bought it from VZW last April so it should be still under the 1 year manufacturer warranty. I'm hoping to find a fix as I haven't backed up in a while, but if not, hopefully they will replace it.
Even though I have a mac, it is set up to run adb commands, but everytime I try reboot or anything it just says "waiting for device". Clearly as it is not powered on.
Any ideas or help????
The symptoms sound like you need to flash the kernel. Could be your phone took the recent OTA...?
Try pulling the kernel out of the RUU and flashing it in fastboot:
fastboot flash boot boot.img
I just tried to do that and I can't get into the RUU zip file. I attached the kernel from the nandroid I made right after I ran the global RUU (4.03.605.2). If that's the version you are on you can try flashing this kernel and see if that does it.
Ugh... having trouble uploading it. If you have a nandroid from your global RUU you can pull the boot.img from that and flash it.
feralicious said:
The symptoms sound like you need to flash the kernel. Could be your phone took the recent OTA...?
Try pulling the kernel out of the RUU and flashing it in fastboot:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I don't know how to do that. I am not a newbie, but there is a lot I don't know. I follow directions well (being able to do the adb stuff with a mac) but pulling the kernel out of an RUU is not something I've ever read about doing.
I've read many threads about charging issues and what not, but I have the stock battery and the extended with a Seidio external charger so I know they both have plenty of juice in them. I know VZW will replace the thing, but I have stuff I'd rather not lose if I can fix it. If you could walk me through pulling the kernel out of the RUU.
I edited my post above while you posted.
Do you have a nandroid of your stock global RUU? If so, you'll easily find the boot.img file in there. If not I'll try to upload the kernel again, or put it on dropbox if I can get back into my account (I never use it).
Once you have the kernel, pull the battery and put it back then boot into bootloader and put phone in fastboot. Attach to Mac, then use fastboot and this command:
fastboot flash boot boot.img (I named the one I'm trying to upload to ruuglobal_boot.img, you can either rename it or just flash using that name instead of boot.img)
feralicious said:
I edited my post above while you posted.
Do you have a nandroid of your stock global RUU? If so, you'll easily find the boot.img file in there. If not I'll try to upload the kernel again, or put it on dropbox if I can get back into my account (I never use it).
Click to expand...
Click to collapse
I hopefully have a nandroid backup on the SD card, but I will tell you it's been a long time since I installed the RUU. I've been out of the rom'ing rooting/ fiddling game for a long time. I haven't had the time recently and apparently it ain't like riding a bike. I've had to read a ton today to refresh myself.
My dinc was so easy, you didn't have to know a whole lot. Just download a zip, check the MD5, and flash it. Rezound was more complicated with the S-on, so I didn't even bother getting started....just the RUU to ICS before it was official, and then the RUU to Global. So yes, I am running the RUU you listed.
Anyway, I don't have a way of reading the SD card until I get home to find the nandroid.....and I've never looked at a nandroid made with Amon Ra....I only was used to CWM on the Dinc.
I got into my dropbox account. Here's a link to the global RUU kernel.
http://dl.dropbox.com/u/55641774/ruuglobal_boot.img
If it works, can you please post a screenshot of your kernel and baseband info?
I'm curious to see what it says, if there's a way to see if it was the OTA that caused this.
Settings > About > Software Info > More
feralicious said:
I got into my dropbox account. Here's a link to the global RUU kernel.
http://dl.dropbox.com/u/55641774/ruuglobal_boot.img
If it works, can you please post a screenshot of your kernel and baseband info?
I'm curious to see what it says, if there's a way to see if it was the OTA that caused this.
Settings > About > Software Info > More
Click to expand...
Click to collapse
Was there an OTA recently?
Yep. A week or two ago:
http://forum.xda-developers.com/showthread.php?t=2154288
You know, I apologize, but I somehow glossed over the end part of your first post where you are now dead. To be honest, that happened to me on my first Rez, and it happened a few days after the ICS OTA came out. I was never able to revive it and bought a used one which I'm using now. (Mine had a cracked screen so I couldn't get it replaced under warranty and had no insurance.)
I tried a new battery, had my old battery checked at Verizon to see if it would take a charge and it did but it wouldn't in my phone. Never was able to revive it. Hopefully you will be able to...
feralicious said:
Yep. A week or two ago:
http://forum.xda-developers.com/showthread.php?t=2154288
You know, I apologize, but I somehow glossed over the end part of your first post where you are now dead. To be honest, that happened to me on my first Rez, and it happened a few days after the ICS OTA came out. I was never able to revive it and bought a used one which I'm using now.
I tried a new battery, had my old battery checked at Verizon to see if it would take a charge and it did but it wouldn't in my phone. Never was able to revive it. Hopefully you will be able to...
Click to expand...
Click to collapse
DAMN. Oh well. They will replace it most likely, and it seems like the easiest route to take. My wife's bootloader fried itself on here Moto D2 last year and it was LONG passed warranty and they replaced it......It was completely stock, but they had no way of knowing, so I'm sure they will send me a replacement phone. I just hope they still have Rezounds to send. I don't want to get stuck with something they determine for me because there are no more rezounds.
My wife's rezound is completely stock, never unlocked so I'll see if she got the update.
ok, the phone has life again..... I got home, tried the other batteries and I'm back to the white HTC screen but no boot. I CAN get into recovery now so I will download the kernel and try that.
Before I do that, do you think something could have happened to recovery since when I select recovery from the bootloader it goes blank? Do you think flashing a rom like Nils could work? or can I just run the RUU again?
318sugarhill said:
ok, the phone has life again..... I got home, tried the other batteries and I'm back to the white HTC screen but no boot. I CAN get into recovery now so I will download the kernel and try that.
Before I do that, do you think something could have happened to recovery since when I select recovery from the bootloader it goes blank? Do you think flashing a rom like Nils could work? or can I just run the RUU again?
Click to expand...
Click to collapse
Ok, I loaded the boot.img and no dice. Still stuck at the white HTC screen. This is frustrating now. Now I do NOT want to go to the VZW store as my bootloader says tampered unlock. I guess I can always try to run the RUU again.
Well, don't give up just yet.
There was an unbrick thread in the dev section. It didn't help me and I'm not sure it applies to your situation, but it can't hurt to try it. I know it had [UNBRICK] in the title, so if you search for unbrick you should find it. You need to get a Linux live img and put in on a usb flash drive and boot into that and then see if it can find your device. It never found mine.
feralicious said:
Well, don't give up just yet.
There was an unbrick thread in the dev section. It didn't help me and I'm not sure it applies to your situation, but it can't hurt to try it. I know it had [UNBRICK] in the title, so if you search for unbrick you should find it. You need to get a Linux live img and put in on a usb flash drive and boot into that and then see if it can find your device. It never found mine.
Click to expand...
Click to collapse
Well, if I can get into the bootloader I can relock to run the RUU correct? I hate to have to lose everything, but I do need the phone, and if it was toasted, I would have to start over with a replacement anyway. Nothing on there can't be replaced except some pictures, but it won't kill me. Just a hastle. Should I try to relock and run the RUU? or should I try to load a Rom like Nils business sense for S-ON? I was considering trying it.
feralicious said:
Well, don't give up just yet.
There was an unbrick thread in the dev section. It didn't help me and I'm not sure it applies to your situation, but it can't hurt to try it. I know it had [UNBRICK] in the title, so if you search for unbrick you should find it. You need to get a Linux live img and put in on a usb flash drive and boot into that and then see if it can find your device. It never found mine.
Click to expand...
Click to collapse
I gave up bro. This sounds way over my head. I relocked and am running the Global RUU again. I will unlock again and load amon ra, and run the su binary zip I have again. Not worth this much time. My 3 year old is tearing up the place while I bury my face in my computer.
Yeah, I would go with that, not sure you have any other options.
If you haven't done the RUU yet you can try just doing the recovery first and see if you can get into it to save your files.
feralicious said:
Yeah, I would go with that, not sure you have any other options.
If you haven't done the RUU yet you can try just doing the recovery first and see if you can get into it to save your files.
Click to expand...
Click to collapse
I tried pushing the recovery again, I tried the boot (all three that were in the nandroid backup) and some other things on here I saw. Nothing worked. Just stayed at the white HTC screen. Relocking and running the RUU made the phone usable again. Thanks for your help, but my stuff is gone. After spending what feels like forever setting up the phone to make it usable again, it will all be gone when I unlock again. Don't have time to do that tonight, but this weekend I'll get to it.
Not everything is gone. I do have titanium but I haven't backed up in a while, so they will be old backups, but still backups. Lesson learned....schedule backups more frequently.....reset my dropbox to auto upload pics again. Turned it off Christmas day, and never turned it back on. The cloud is there for a reason right?
Hello all, and thanks in advance for your help. I don't know if all of this is relevant to what happened, but I'm including it in case there's some small clue.
My phone was an S-OFF running HBOOT 2.09. I have been running Deck's CM builds for a while now with no issues. Last week, I decided to update to the new firmware which included the new partition layout.
HTC's RUU executable did not work, so I used the two zip method in this post. I first renamed rom_01 to PJ75IMG.zip, placed it on the SD card, rebooted and installed, then did the same with rom_02. Loaded everything up, seemed great with the stock image. After verifying everything was working fine, I flashed a new recovery (2.7.0.0b, via PJ75IMG.zip as well), and installed the latest OmniROM (3/31) via recovery. I had some issues with the PA 0-Day GAPPs that were recommended (force close errors with Google Keyboard) so after reflashing Omni switched back to the 12/09 GAPPs in Deck's thread. Everything seemed great.
A few days later, after having the phone in my pocket, my screen turned into a rainbow of pixels. Here is what it looks like: http://imgur.com/9ef6F8z It still seemed to work, just the screen was always that rainbow.
Thinking it was an issue with the firmware, I tried to RUU back to a somewhat earlier stock by using ViperRUU 3.16.651.3. However, after going through the RUU process, it had gone about 30-40 minutes with no updates, so I thought it had crashed. I checked to see if that was normal, and saw that it was not and they recommended restarting the process. I restarted both the ViperRUU (couldn't find phone anymore) and the phone, and now I think my phone might be totally bricked.
When I turn it on, there is nothing on the screen. It vibrates once, like it's trying to start, but nothing happens and the phone is otherwise unresponsive. I can try to boot into the bootloader (volume down + power) and that SEEMS to work, but the screen doesn't turn on then either. Occasionally, it will display the same rainbow pixels after "selecting" an option on the bootloader menu (I'm assuming). I've also pulled the SD card to insure it's not trying to read any PJ75IMG.zip.
I can't seem to get it to go into fastboot mode (single power button click after thinking I'm in the bootloader) and adb only shows the device as OFFLINE when I can get it to detect. It's hard to know what's going on without the screen.
Has anyone heard of this before? I probably ****ed something up but other than ending the ViperRUU early, not sure what. Thanks in advance, I very much appreciate it.
matt135353 said:
Hello all, and thanks in advance for your help. I don't know if all of this is relevant to what happened, but I'm including it in case there's some small clue.
My phone was an S-OFF running HBOOT 2.09. I have been running Deck's CM builds for a while now with no issues. Last week, I decided to update to the new firmware which included the new partition layout.
HTC's RUU executable did not work, so I used the two zip method in this post. I first renamed rom_01 to PJ75IMG.zip, placed it on the SD card, rebooted and installed, then did the same with rom_02. Loaded everything up, seemed great with the stock image. After verifying everything was working fine, I flashed a new recovery (2.7.0.0b, via PJ75IMG.zip as well), and installed the latest OmniROM (3/31) via recovery. I had some issues with the PA 0-Day GAPPs that were recommended (force close errors with Google Keyboard) so after reflashing Omni switched back to the 12/09 GAPPs in Deck's thread. Everything seemed great.
A few days later, after having the phone in my pocket, my screen turned into a rainbow of pixels. Here is what it looks like: http://imgur.com/9ef6F8z It still seemed to work, just the screen was always that rainbow.
Thinking it was an issue with the firmware, I tried to RUU back to a somewhat earlier stock by using ViperRUU 3.16.651.3. However, after going through the RUU process, it had gone about 30-40 minutes with no updates, so I thought it had crashed. I checked to see if that was normal, and saw that it was not and they recommended restarting the process. I restarted both the ViperRUU (couldn't find phone anymore) and the phone, and now I think my phone might be totally bricked.
When I turn it on, there is nothing on the screen. It vibrates once, like it's trying to start, but nothing happens and the phone is otherwise unresponsive. I can try to boot into the bootloader (volume down + power) and that SEEMS to work, but the screen doesn't turn on then either. Occasionally, it will display the same rainbow pixels after "selecting" an option on the bootloader menu (I'm assuming). I've also pulled the SD card to insure it's not trying to read any PJ75IMG.zip.
I can't seem to get it to go into fastboot mode (single power button click after thinking I'm in the bootloader) and adb only shows the device as OFFLINE when I can get it to detect. It's hard to know what's going on without the screen.
Has anyone heard of this before? I probably ****ed something up but other than ending the ViperRUU early, not sure what. Thanks in advance, I very much appreciate it.
Click to expand...
Click to collapse
This is a known hardware issue. Look here:
http://forum.xda-developers.com/showthread.php?t=2470296
It happened to me as well. I called Sprint and they replaced my phone for no charge.
Sent from my EVO using XDA Premium 4 mobile app
Ah, thanks for the link. I don't have TEP and it's out of warranty but I'll give Sprint repair a shot. Thanks!
Evolution_Freak said:
This is a known hardware issue. Look here:
http://forum.xda-developers.com/showthread.php?t=2470296
It happened to me as well. I called Sprint and they replaced my phone for no charge.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmm...I bought mine secondhand and am going to be running it on Ting, you think they would do that for me if it happens? :laugh:
matt135353 said:
Ah, thanks for the link. I don't have TEP and it's out of warranty but I'll give Sprint repair a shot. Thanks!
Click to expand...
Click to collapse
I have TEP but that never even came up. I never filed a claim. They originally wanted me to go to a Sprint store to have a tech look at it but I complained that the nearest store is an hour away. So they took my word, after explaining what was happening, and sent me a new (refurbished) EVO and then I sent them the old one in the package they provided with the new one. This was back in November of 2013 and I never heard anything else about it.
Sent from my Nexus 5 using XDA Premium 4 mobile app