So I recently came back to my rezound to mess with roms and stuff and upon trying to boot I realized it wouldn't boot. When plugged in the battery would not charge so I went to Verizon and had them test it and the guy told me it wouldn't take a charge when he plugged it in. So i got a new battery and now the phone boots....but its stuck in a loop on the HTC screen. When I boot to hboot and try to get into recovery it just goes black. Next I tried fastboot and adb commands and all it says is device not found. I tried re-flashing recovery and new roms by naming it ph98img on the SD card and it says the charge on the battery is to low. I plug the phone in and try and charge it it just won't charge the led light will come on for a brief second then turn off and then proceeds to go the white htc screen for a few second then it turns off then the charging light comes on again rinse and repeat. Now i think the battery is drained because I can't get it to boot to hboot but it will still do the boot loop if left plugged.
What i remember from the hboot screen was
Locked
s-off (it said vigor shipped)
hboot 2.25.00
I could have swore I had the boot loader unlocked and juniper bear hboot installed and I know I had do the wire trick to s-off so it shouldn't say shipped right? I don't remember which radio it was running but that shouldn't affect it booting right? I'm all out of ideas at this point and was hoping some one could either give me more things to try or something. I've already tried everything in brick threads as well. I wanna try charging the battery and and flashing a new recovery but I don't have a way of doing that.
Any help would be much appreciated.
try getting another device to charge your rezound battery I have a thunderbolt and i charge the extra battery like that.
ive only tried this with other htc devices
Once I get the battery charged then what? Flash recovery in hboot then go from there or is there a reason in adb it says device not found?
Well you can try flashing a new rom but i had a similar problem before when i turned my rezound on it would boot loop and i flashed the newest RUU and that fixed it although i had to root again
I remember Feralicious told me that s off is more of a risk since you can brick your device easier.
feralicious said:
Yes. Since you are s-on you must flash the kernel that goes with the ROM after you flash the ROM.
If you s-off you won't have to but it makes it easier to brick the phone. I've also read where some people have lost the use of their usb ports trying to s-off. I'm s-on and it doesn't bother me to flash the kernel separately. The ROM I'm using puts it on the sd card and puts the phone in hboot so all I have to do is accept the update. Easy peasy.
Click to expand...
Click to collapse
you can try this, this got me out of a predicament
Flyhalf205 said:
Flash the stock recovery. Then try a factory reset inside of HBOOT.
Link to stock recovery: http://goo.im/devs/Flyhalf205/Rezound/Recovery/stock_recovery_signed.img
Click to expand...
Click to collapse
Ok thanks I appreciate all your guys help. Do you think if I ask nicely at Verizon they'll charge it for me? The battery that is of course.
That all depends on the rep that you talk to some are nice and some are jerks. You can try a phone repair shop im sure they will charge it for you.
xkjonathanxk said:
That all depends on the rep that you talk to some are nice and some are jerks. You can try a phone repair shop im sure they will charge it for you.
Click to expand...
Click to collapse
Phone repair shop might be my best bet the reps I talked to at Verizon said they couldn't do it even though the guy did it the other day. Thanks for the tip.
xkjonathanxk said:
Well you can try flashing a new rom but i had a similar problem before when i turned my rezound on it would boot loop and i flashed the newest RUU and that fixed it although i had to root again
I remember Feralicious told me that s off is more of a risk since you can brick your device easier.
Click to expand...
Click to collapse
Meh, I've been s-off since the day the exploit was released and I've installed multiple roms and my phone is fine. Only case I've seen of people getting bitten by s-off was during getting CM9 to work.
Truemeaningoffear said:
Once I get the battery charged then what? Flash recovery in hboot then go from there or is there a reason in adb it says device not found?
Click to expand...
Click to collapse
If you hava an extra charger (Especially one from an old phone that you need anymore) you can cut the wires open and charge the battery that way. I will walk you through it if you think this is something you want to do.
After it is charged factory reset (as in wipe, I dont think that you need to actually go back to stock) and try flashing a new rom that uses the same or similar boot.img (stick with sense if thats what you have now, or if you are de-sensed try Neo's rage rom http://forum.xda-developers.com/showthread.php?t=1899085 I have found it to be very very stable)
Make sure that after the factory wipe you also wipe dalvik cache and cache. They sometimes fail to wipe I have noticed (it is very rare but happens)
----------------------------------------------
I forgot to mention that you should stick with he android version that you are currently on.
Also forgot to say my OG droid had the exact same charge problem. But I fixed it just by using a facory charger plugged into the wall (not a usb port that didn't work for some reason). My dads HTC Incredible was charged by the wire method that I mentioned
coltstrgj said:
If you hava an extra charger (Especially one from an old phone that you need anymore) you can cut the wires open and charge the battery that way. I will walk you through it if you think this is something you want to do.
After it is charged factory reset (as in wipe, I dont think that you need to actually go back to stock) and try flashing a new rom that uses the same or similar boot.img (stick with sense if thats what you have now, or if you are de-sensed try Neo's rage rom http://forum.xda-developers.com/showthread.php?t=1899085 I have found it to be very very stable)
Make sure that after the factory wipe you also wipe dalvik cache and cache. They sometimes fail to wipe I have noticed (it is very rare but happens)
----------------------------------------------
I forgot to mention that you should stick with he android version that you are currently on.
Also forgot to say my OG droid had the exact same charge problem. But I fixed it just by using a facory charger plugged into the wall (not a usb port that didn't work for some reason). My dads HTC Incredible was charged by the wire method that I mentioned
Click to expand...
Click to collapse
So I got the battery charged and tried flashing new recovery and it still doesn't do anything just sends me back to htc boot screen and loops. I've tried flashing a stock RUU and still right back to the loop. I've tried factory reset and clear storage it sends right back to the boot loop. I have no idea if their is anything I can do at this point. Still get device not found and wait for device from adb and fastboot commands. I noticed that the water indicator is tripped could something have got wet and be dis-functioning inside?
Truemeaningoffear said:
So I got the battery charged and tried flashing new recovery and it still doesn't do anything just sends me back to htc boot screen and loops. I've tried flashing a stock RUU and still right back to the loop. I've tried factory reset and clear storage it sends right back to the boot loop. I have no idea if their is anything I can do at this point. Still get device not found and wait for device from adb and fastboot commands. I noticed that the water indicator is tripped could something have got wet and be dis-functioning inside?
Click to expand...
Click to collapse
Sorry for taking so long on replying. If the water tag has been tripped then maybe that is the problem, but I would doubt it. I would think from what I have seen that when it is triggered if the phone is going to fail it fails hard. It might light up, but no boot loop. The kernel is trying to load if you have made it all the way to the boot animation. Its like on a computer the bios flashes while the cpu, memory, and storage are checked. Only if they all appear to be working will it move on to the next step.
From my computer (not phone) experience I think you could have some bad ram. It it comes loose or maybe is damaged it could still (possibly but unlikely) pass the mem check. If you have dropped it this could be more likely but I'm not really sure.
If you have insurance on the phone you could get it replaced. Just tell them that you lost it. Do not mention the water or they will charge you more.
You might also want to check this out. I have not downloaded it or looked at it, so It may be out of date(probably is) but hey its worth a try
http://forum.xda-developers.com/showthread.php?t=1833530
coltstrgj said:
You might also want to check this out. I have not downloaded it or looked at it, so It may be out of date(probably is) but hey its worth a try
http://forum.xda-developers.com/showthread.php?t=1833530
Click to expand...
Click to collapse
There isn't really any instructions in the thread on how to use it but it looks like you need fastboot to be working and a linux box. My fast boot doesn't work so idk if that would even help and all of the download links are dead anyway.
Thanks for the help though.
Related
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...
So this happend yesterday, I plugged it in my computer and my phone just shuts down all a sudden (because of the USB port). Now it keeps saying it is charging, even when it is not, the red light stays on, even when the phone is powered down. Only when my phones battery is out it stops, but as soon as I plug the battery back in the light pops up....
After an entire night of charging the phone is not even fully charged it was stuck around 85%. Never reached green.... I flashed it twice, once with a different rom once with the exciting rom...
Any ideas on how to fix this?
The phone is S-off rooted unlocked if that is to any help.
Please help.
Toasit said:
So this happend yesterday, I plugged it in my computer and my phone just shuts down all a sudden (because of the USB port). Now it keeps saying it is charging, even when it is not, the red light stays on, even when the phone is powered down. Only when my phones battery is out it stops, but as soon as I plug the battery back in the light pops up....
After an entire night of charging the phone is not even fully charged it was stuck around 85%. Never reached green.... I flashed it twice, once with a different rom once with the exciting rom...
Any ideas on how to fix this?
The phone is S-off rooted unlocked if that is to any help.
Please help.
Click to expand...
Click to collapse
Have you tried wiping battery stats from recovery?
DjDom said:
Have you tried wiping battery stats from recovery?
Click to expand...
Click to collapse
How does that go in its work? Sorry for the late reply, have not been in country.
It sounds like to me there could be a few things that are the problem. First, it could be the recovery you are using. If you are using cwm then I suggest getting rid of that and flashing twrp or 4ext. If you already have one of those recoveries then it could the kernel you are using. Depending on the rom you are on flash a different one to see if that stops the constant red light. You also said that your phone shuts down instantly when you plug it into a usb port. That could either be a rom or a kernel issue. Try flashing a different rom and kernel to see if that helps. Lastly, if none of these haved worked then rule out battery by using a another one and another charger cord. If those didn't help then you are probably looking at a hardware issue. In that case you would have to return your phone to complete stock before you send it in for repairs. Also if you do go this route make sure you tell the techs not to replace your motherboard unless it's absolutely necessary. Doing so will render your phone unable to be unlocked and rooted. I hope that any of these solutions will help.
Jsparta26 said:
It sounds like to me there could be a few things that are the problem. First, it could be the recovery you are using. If you are using cwm then I suggest getting rid of that and flashing twrp or 4ext. If you already have one of those recoveries then it could the kernel you are using. Depending on the rom you are on flash a different one to see if that stops the constant red light. You also said that your phone shuts down instantly when you plug it into a usb port. That could either be a rom or a kernel issue. Try flashing a different rom and kernel to see if that helps. Lastly, if none of these haved worked then rule out battery by using a another one and another charger cord. If those didn't help then you are probably looking at a hardware issue. In that case you would have to return your phone to complete stock before you send it in for repairs. Also if you do go this route make sure you tell the techs not to replace your motherboard unless it's absolutely necessary. Doing so will render your phone unable to be unlocked and rooted. I hope that any of these solutions will help.
Click to expand...
Click to collapse
Thanks, going to flash a new rom. Maybe that helps Fingers crossed.
By the way, is there a way to return it in a state of S-on and full stock? I have managed to install ICS rom, the HTC release.
Tried a battery, seems even a NEW battery does not fill to a 100% rate, stops around 83-86%
Toasit said:
Thanks, going to flash a new rom. Maybe that helps Fingers crossed.
By the way, is there a way to return it in a state of S-on and full stock? I have managed to install ICS rom, the HTC release.
Tried a battery, seems even a NEW battery does not fill to a 100% rate, stops around 83-86%
Click to expand...
Click to collapse
Are you CDMA or Gsm? Also are s-on or s-off?
Toasit said:
Thanks, going to flash a new rom. Maybe that helps Fingers crossed.
By the way, is there a way to return it in a state of S-on and full stock? I have managed to install ICS rom, the HTC release.
Tried a battery, seems even a NEW battery does not fill to a 100% rate, stops around 83-86%
Click to expand...
Click to collapse
Hopefully the ROM worked for you, because it does sound software related if you tried a new battery.
I was saying wipe the battery stats because it'll clear all battery info and it'll re calibrate itself.
However, yes, you can go back to full S-ON.
If the new ROM didn't help, I'll show you how to get back to stock.
My phone is GSM.
Rom didnt do much for me... tried 2 different ROM's excluding the official one.
So, I made it S-off, I have it ''relocked'' anything else I need to do before I can send it RMA?
I did clean out my USB port btw. Could it be a hardware related problem?
http://forum.xda-developers.com/showthread.php?t=1535987
I found this guide, now my issue is. I S-off'ed my phone with Hboot 1.5xxxx not with 1.4xxxx Is that any problem if I am about to revert it?
Since your s-off you can revert back to whatever hboot you want. Just keep in mind it has to be a stock boot loader. No custom ones or you could brick your phone when you write the security flag command in fast boot.
Jsparta26 said:
Since your s-off you can revert back to whatever hboot you want. Just keep in mind it has to be a stock boot loader. No custom ones or you could brick your phone when you write the security flag command in fast boot.
Click to expand...
Click to collapse
So, that means I can choose whatever RUU as long as it is for my region and phone? After that I can lock it once again?
DjDom said:
Hopefully the ROM worked for you, because it does sound software related if you tried a new battery.
I was saying wipe the battery stats because it'll clear all battery info and it'll re calibrate itself.
However, yes, you can go back to full S-ON.
If the new ROM didn't help, I'll show you how to get back to stock.
Click to expand...
Click to collapse
If you can show me please. I did use the wire trick to get it S-off if that is relevant.
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?
So today, i went to load up a book in kindle and it crashed a couple times in a row. I figured no biggy, and rebooted the phone (which I can't remember the last time I did, weeks ago).
Upon reboot, for some reason, I'm stuck in a boot loop. I get the white screen with the HTC logo for about 15-30 seconds, it shuts down, repeat. I figured no biggy, everything is stock, I don't care about anything on it, I'll just use the RUU to fix it.
That is where my problem begins. Unforunately, I am updated to 2.95, and the last release RUU is 2.89, so it won't let me install. I can get into hboot, I can use fastboot, so I used fastboot to erase the cache. Anything I select (factory reset, recovery, etc) in hboot just sends me back into the reboot loop. Manually flashing errors out because of the mainver discrepancy. I can't use the low version fix because I'm not rooted, so sure, let's try that... I started the process and unlocked successfully. Now the problem is, any recovery I've installed (4ext from the root thread, CWM5.8 from the boot loop thread) installs fine, but whenever I reboot recovery, again, boot loop. It doesn't matter whether the reboot comes from a fastboot command or selecting recovery reboot from inside hboot.
So, desperate (and somewhat ignorant), I booted up into Linux and tried the unbrick post, and of course, the device never shows up with the battery out, cause it ain't bricked. I was hoping somehow that I could use it to replace hboot, figuring that might be corrupt or something crazy like that (grasping at straws really).
What I really need is a 2.95 RUU, but that hasn't been released, and I figured if that didn't work, something is probably fried hardware wise.
I restored a stock signed recovery, so more or less, right now I'm back exactly where I'm started (other then the fact that my phone is now unlocked) and just not sure where to go from here. Any advice would be helpful. Thanks!
EDIT: I'm a moron, and I forgot to specify, but the phone is sprint. I also don't have any service on it (mainly used as an mp3 player) so I don't have any recourse through them.
I'm almost considering bricking the thing to change the hboot (I haven't done my homework on it yet) any thoughts there? Or is it not something I can do because of my problem?
Sounds like you didn't flash a ROM after getting into recovery.
You need to make sure you're unlocked, and flash a recovery...4ext recovery is highly recommended as it has a setting just to help s on users.
To start and get you up and going, i suggest downloading butterz sense ROM and placing it on your SD card.
Then you need to wipe everything except your SD card
Now flash a new rom, like butterz sense.
Reboot and you should be good
If not you may need to flash boot.IMG in fast boot.
to run an old ruu, you will need to get s off and for that you need a booting ROM.
Good luck!
Sent from my Evo 3D CDMA using xda app-developers app
hossman said:
Sounds like you didn't flash a ROM after getting into recovery.
You need to make sure you're unlocked, and flash a recovery...4ext recovery is highly recommended as it has a setting just to help s on users.
To start and get you up and going, i suggest downloading butterz sense ROM and placing it on your SD card.
Then you need to wipe everything except your SD card
Now flash a new rom, like butterz sense.
Reboot and you should be good
If not you may need to flash boot.IMG in fast boot.
to run an old ruu, you will need to get s off and for that you need a booting ROM.
Good luck!
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
Well, the problem is that I can't get into a recovery after I install it, I'm still caught in the boot loop... but I will try flashing the boot img. Thanks!
If you would like a quicker response/fix check your pm....i can try to help
Sent from my Evo 3D CDMA using xda app-developers app
Well, I did reflash boot.img with no success. I went to relock the phone and was just gonna throw it on the shelf for a couple weeks (as I do have another one), and when I did that using fastboot, it sent the command over and the phone received it, but it gave me a failure message. So now, it doesn't turn on, when I hook it up to the charger, I get the red charging light for about 10 seconds, and very occasionally when I remove the battery and put it back in the HTC logo appears for about 3-5 seconds before the phone cuts off again.
I'm starting to think there was some hardware issue. Since it had a screwy digitizer anyways (and I chose to get another evo for 65 rather then paying 30-35 for the ldc/dig combo), I'm just going to keep it around for parts and maybe play with it another time.
Your offer of help is greatly appreciated however, thank you.
EDIT: It doesn't seem to be truly bricked, or it isn't a recoverable brick... not really seeing the dim red light and the unbrick script doesn't detect it... the phone isn't in emmc mode... but I'm not hugely concerned with it now like I said.
LOL I'm a moron... my battery went dead during the whole recovery thing. Slapped another battery in and I am back to the original problem. Ignore my last post, basically.
At this point, I think that I might be possible that I can't get into recovery because, to the best of my knowledge, the "fast boot" option is ticked in the settings. Unfortunately, I can't get into the phone to change it, so even more chicken/egg stuff. Bleh. I'm still chugging along, any input appreciated. Maybe I can call HTC or Sprint and beg for an RUU?
thatdumbguy said:
LOL I'm a moron... my battery went dead during the whole recovery thing. Slapped another battery in and I am back to the original problem. Ignore my last post, basically.
At this point, I think that I might be possible that I can't get into recovery because, to the best of my knowledge, the "fast boot" option is ticked in the settings. Unfortunately, I can't get into the phone to change it, so even more chicken/egg stuff. Bleh. I'm still chugging along, any input appreciated. Maybe I can call HTC or Sprint and beg for an RUU?
Click to expand...
Click to collapse
Good luck!
So pull the battery, and put it back in.
Hold volume up and then press power.
Does that bring you to boot loader?
Does it say unlocked?
Sent from my Evo 3D CDMA using xda app-developers app