Ok I did my first root and install for my rezound. I messed with rooting more back when I had my TB and Eris but nothing more than doing some walk-throughs getting some new roms and such. I got Nils business sense 3.6 working great and what a great ROM! However I ran into a (in my head) major problem. With the knowledge of some people here I'm sure 30 minutes with my phone would get it going, but alas I am a noob, but good at following instructions. I'm good with all things tech until we start talking cmd and coding . Build a comp, fix a computer, OCing that kind of thing.
Anyhow, this morning I woke up to a dead phone forgot to charge, no biggy, I put in a new battery and booted...then got stuck at HTC white screen. So I boot into bootloader and all i get is the IMG updating thing and only an option to reboot. Now I'm in a loop. So I take the PHIMG out of root folder and try to boot into recovery and it goes to the white HTC screen with the small loading bar to a black screen that never changes. Cant get into recovery. Next step, using the Hasoon all in one toolkit (though I know I could use cmd myself, this makes my life easier as it accomplishes the same goal) I try to reflash recovery as recommended by someone here. No change. Alas I know my battery is probably getting low and it does NOT charge while turned off!! Lame...So any help would be greatly appreciated!
volcaicstrad37 said:
Ok I did my first root and install for my rezound. I messed with rooting more back when I had my TB and Eris but nothing more than doing some walk-throughs getting some new roms and such. I got Nils business sense 3.6 working great and what a great ROM! However I ran into a (in my head) major problem. With the knowledge of some people here I'm sure 30 minutes with my phone would get it going, but alas I am a noob, but good at following instructions. I'm good with all things tech until we start talking cmd and coding . Build a comp, fix a computer, OCing that kind of thing.
Anyhow, this morning I woke up to a dead phone forgot to charge, no biggy, I put in a new battery and booted...then got stuck at HTC white screen. So I boot into bootloader and all i get is the IMG updating thing and only an option to reboot. Now I'm in a loop. So I take the PHIMG out of root folder and try to boot into recovery and it goes to the white HTC screen with the small loading bar to a black screen that never changes. Cant get into recovery. Next step, using the Hasoon all in one toolkit (though I know I could use cmd myself, this makes my life easier as it accomplishes the same goal) I try to reflash recovery as recommended by someone here. No change. Alas I know my battery is probably getting low and it does NOT charge while turned off!! Lame...So any help would be greatly appreciated!
Click to expand...
Click to collapse
You could download and install the latest global RUU. Rename it to PH98IMG.zip and place it on root of SD. Make sure if your S-On to re lock your bootloader. Also stay away from CWM recovery, Amon Ra or TWRP is your best recoveries of choice.
Samsung Galaxy S3
Trying to do what is suggested but it seems my phone is too dead to boot into hboot, I cannot hold volume down and power to get there when plugged into the computer either.
volcaicstrad37 said:
Trying to do what is suggested but it seems my phone is too dead to boot into hboot, I cannot hold volume down and power to get there when plugged into the computer either.
Click to expand...
Click to collapse
Your going to have to pop in a new battery or find a way to charge your battery externally.
Samsung Galaxy S3
luis86dr said:
Your going to have to pop in a new battery or find a way to charge your battery externally.
Samsung Galaxy S3
Click to expand...
Click to collapse
I was afraid of that...As I look at my desk with 2 OEM batteries and an extended...all dead... :silly:
volcaicstrad37 said:
I was afraid of that...As I look at my desk with 2 OEM batteries and an extended...all dead... :silly:
Click to expand...
Click to collapse
It happens lol. Just stay away from CWM recovery in the future. It doesn't allow you to charge your device when powered off.
Also, I think there is a thread someone made on how to charge your battery externally. Might have to dig it up in the general section.
Samsung Galaxy S3
luis86dr said:
It happens lol. Just stay away from CWM recovery in the future. It doesn't allow you to charge your device when powered off.
Click to expand...
Click to collapse
I am not sure if you ever go into the Development thread but http://forum.xda-developers.com/showthread.php?t=1914215
A great tool to keep around http://www.amazon.com/eForCity-Batt...50853249&sr=8-14&keywords=htc+rezound+charger
Flyhalf205 said:
I am not sure if you ever go into the Development thread but http://forum.xda-developers.com/showthread.php?t=1914215
Click to expand...
Click to collapse
Yeah, I was going to post this:
http://forum.xda-developers.com/showthread.php?t=1711408
Just dug that up, you can use CWM Touch as well. Either or should set you straight.
Samsung Galaxy S3
I actually used the Amon recovery I did hear issues with CWM as I was doing research. So am I to assume amon has similar issues to CMW then?
Flyhalf205 said:
I am not sure if you ever go into the Development thread but http://forum.xda-developers.com/showthread.php?t=1914215
A great tool to keep around http://www.amazon.com/eForCity-Batt...50853249&sr=8-14&keywords=htc+rezound+charger
Click to expand...
Click to collapse
Just placed an order. Thanks, I was hoping to find one in a store around here to get up and running this week, but I guess I'll be out of commission for a couple days.
volcaicstrad37 said:
Just placed an order. Thanks, I was hoping to find one in a store around here to get up and running this week, but I guess I'll be out of commission for a couple days.
Click to expand...
Click to collapse
Amon recovery does not have the battery charging issue. I don't know if you ordered the battery already. But have you tried charging all the batteries?
jdm2008315 said:
Amon recovery does not have the battery charging issue. I don't know if you ordered the battery already. But have you tried charging all the batteries?
Click to expand...
Click to collapse
Yeah I've tried all three with 2 different chargers.
Related
So, yesterday morning this all went down. My Rezound has been nothing but an expensive paperweight. I am not new to the rooting game so save the nonconstructive comments.
Early Monday morning I felt the need to change things up a bit so I wanted to flash the latest CleanRom 3.7 to check it out (coming from BAMF v.09). I backed up all my apps & data and continued to make a nandroid backup (with Amon_Ra 3.14). After that, I completed the necessary wipes (including boot because Scott packages his roms with the kernel) in recovery and then flashed CleanRom 3.7 (MD5 sum matched) then booted into bootloader to flash the kernel. Everything went perfect with that.
After the phone booted I realized how low on battery I was on but connected to Wi-Fi during the initial start-up on the new rom. I got all my accounts and data synced/restored and was getting ready to knock out. I set my alarm, placed the phone on the wall charger and confirmed it was charging by the orange light around 3am.
I woke up yesterday morning around 7:30am and realize I'm running late. I pick up my phone to see if the time is correct and I get nothing but a black screen. Pulled the battery...nothing...plugged in the phone without the battery..then plugged in the battery...nothing. On my 45 minute commute to work I removed the battery and let the phone sit (hoping some magic would happen lol) and nothing changed.
When I made it to my office, I plugged the phone in to see if it would accept a charge and 2 hours later nothing. I have the 3.7v battery and have had no indications of a bad battery (short life, warm, etc.). Due to the circumstances, I was left with no choice but to go to the local VZW and order a replacement.
The guy at the Verizon store plugged my phone in the wall charger and saw it was not accepting a charge. Swapped the battery with his own personal Rezound and mine worked in his, however, his fully-charged battery would not work in mine. Narrowed it down to the phone itself which blows. I thought at worst it would be the battery.
I am really curious how/why this all went down of all times when I wasn't doing anything to my phone. You guys/gals have any idea?
Marcismo55 said:
and continued to make a nandroid backup.
Click to expand...
Click to collapse
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
mike.s said:
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
Click to expand...
Click to collapse
My bad..I forgot to mention I have been running Amon_Ra from the start. I've never ran CWM on my Rezound and I did run across some threads regarding the charging issues associated with CWM.
Thanks though!
Did you check the pins on the inside of the phone for the battery? Any scratches or rust?
This is exactly why I stay on GB and GB Kernels.
I experienced non-charging on two different ICS ROMs at seemigly random times. Sometimes just on the 3.8v. Once on the 3.7v. Going back to GB, then back to ICS temporarily resolved the issue.
One of the 10 reasons I tell people not to go ICS with this phone yet.
Get back on GB and your phone may well be just fine.
That's where my money is.
Ineffabilis with the 2.011.xxx kernel and radio is winning still.
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
mpalatsi said:
Did you check the pins on the inside of the phone for the battery? Any scratches or rust?
Click to expand...
Click to collapse
Yes. All the contacts were intact and free of dirt/debris.
pkopalek said:
This is exactly why I stay on GB and GB Kernels.
I experienced non-charging on two different ICS ROMs at seemigly random times. Sometimes just on the 3.8v. Once on the 3.7v. Going back to GB, then back to ICS temporarily resolved the issue.
One of the 10 reasons I tell people not to go ICS with this phone yet.
Get back on GB and your phone may well be just fine.
That's where my money is.
Ineffabilis with the 2.011.xxx kernel and radio is winning still.
Click to expand...
Click to collapse
I would give GB a try, however, the phone does not do anything at all.
I also don't quite follow your reasoning behind not running ICS roms as this appears to be more of a hardware related issue itself. However, that is fine if it works for you.
Dstu03 said:
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
More than half of all the roms out there are from ports/leaks. Please explain.
You put the sim card in backwards? I fried one rezound doing this already.
Sent from my ADR6425LVW using XDA
Did you try to connect via USB to your computer and type in adb reboot? I have heard some success with that. But it was for the CWM problem. It might be worth a shot.
nosympathy said:
You put the sim card in backwards? I fried one rezound doing this already.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Actually I didn't even take the SIM out. Maybe I should have given that a try.
EmerikL said:
Did you try to connect via USB to your computer and type in adb reboot? I have heard some success with that. But it was for the CWM problem. It might be worth a shot.
Click to expand...
Click to collapse
Thanks man...I tried that too and ADB was unable to see the device.
VZW told me my replacement won't be here until tomorrow...weak.
dude i started a topic on this months ago..i had a guy come in who had the SAME problem..except his somewhat powered on with another battery.
i put one in, went into bootloader, tried to boot to recovery, but it just came up as a black screen...so i reboot it, wiped it, but it wouldn't even wipe, it just went to that same black screen. his battery had died overnihgt, and he didn't charge it, and then this happened..it just wouldn't turn on, the orange light wouldn't come on showing it was charigng...
i couldn't fix it, so we had to get him a replacement that really sucks that i'm still hearing it out there...
sorry if i didn't read, but what rom/kernel were you running? this guy swears it was stock and he never heard of rooting, so who knows if he was lying or not
mike.s said:
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
Click to expand...
Click to collapse
That's only for charging when you're booted into recovery if I'm not mistaken...
---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------
Dstu03 said:
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
If flashing killed it, it would have never booted back up...
Marcismo55 said:
Actually I didn't even take the SIM out. Maybe I should have given that a try.
Thanks man...I tried that too and ADB was unable to see the device.
VZW told me my replacement won't be here until tomorrow...weak.
Click to expand...
Click to collapse
In my case when the Verizon rep gave me the phone he put the sim in and put it in backwards. To be fair, it does go in "backwards" to every other android phone I have owned haha.
Sent from my ADR6425LVW using XDA
mjones73 said:
That's only for charging when you're booted into recovery if I'm not mistaken...
Click to expand...
Click to collapse
It may depend on how you're charging. The charging process requires some intelligent oversight - if you power off the phone, and connect a charger, the process is controlled by code loaded from somewhere. I think that code is in, or loaded by, the recovery. That would tend to explain things like this, this, this, and this.
jayochs said:
dude i started a topic on this months ago..i had a guy come in who had the SAME problem..except his somewhat powered on with another battery.
i put one in, went into bootloader, tried to boot to recovery, but it just came up as a black screen...so i reboot it, wiped it, but it wouldn't even wipe, it just went to that same black screen. his battery had died overnihgt, and he didn't charge it, and then this happened..it just wouldn't turn on, the orange light wouldn't come on showing it was charigng...
i couldn't fix it, so we had to get him a replacement that really sucks that i'm still hearing it out there...
sorry if i didn't read, but what rom/kernel were you running? this guy swears it was stock and he never heard of rooting, so who knows if he was lying or not
Click to expand...
Click to collapse
Yeah dude I had just flashed CleanRom 3.7 and the stock kernel that came with it.
It was completely unresponsive to anything but I didn't think of booting into recovery. My battery had a 30% charge on it when the VZW rep put it in his Rezound and powered it on. It was just really weird.
Marcismo55 said:
Yeah dude I had just flashed CleanRom 3.7 and the stock kernel that came with it.
It was completely unresponsive to anything but I didn't think of booting into recovery. My battery had a 30% charge on it when the VZW rep put it in his Rezound and powered it on. It was just really weird.
Click to expand...
Click to collapse
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
scrosler said:
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
Click to expand...
Click to collapse
^This. Even if it is new hardware there can be defects. **** happens!
Marcismo55 said:
I would give GB a try, however, the phone does not do anything at all.
I also don't quite follow your reasoning behind not running ICS roms as this appears to be more of a hardware related issue itself. However, that is fine if it works for you.
Click to expand...
Click to collapse
I assessed your OP as related to a phone not charging.
I see what you mean, now. My points were in the case of non-charing, or failure to charge (and a phone going dead on the charger) which aren't things I've seen on any stock-based ROM, but very much so on ICS ROM's (and Kernels, as such).
I bid you good luck on your replacement hardware. Stuff happens!
scrosler said:
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
Click to expand...
Click to collapse
I understand Scott. I am in now way shape or form saying flashing your ROM was the reasoning behind all this as I have flashed numerous times before this and had no issues. Also, considering I am one of the very few this has happened to, i think its pretty obvious this was a hardware failure. I
I'll be running your roms soon enough
Thanks to everyone providing insight on this situation. I'll be back at it again very soon!
Hey,
I didn't feel like going through the trouble of buying the Motorola factory charger or whatever you need to charge the phone when it said *battery low* *cannot program* when trying to use the RSD program (might have spelled it wrong) to restore to factory settings. My battery must have been low and in the middle of the restore, it stopped and now Im unable to get to either recovery or charge it.
I had insurance luckily so I just got my galaxy nexus back and should be to me tomorrow. Do yall think someone will buy this phone like that? i have 2 nandroid backups on there so it's probably not safe to sale with that stuff accessible.. smh.. that's why i liked the samsung galaxy s and galaxy s 2 devices because you can use Odin which makes the phones virtually unbrickable. The phone's in PERFECT condition. Would be nice if there was a way around that man
how much? just curiosity...
That's why its always recommened to have full charge when rooting or installing custom rom. I hope someone here in the forum can help you solve this issue.
you can make one looks like here:
http://forum.xda-developers.com/showthread.php?t=1403100
if you want to give it a go, will cost you a $3 cable if you mess it up, and will gain you a $300 phone if you do it right.
joel_sinbad said:
how much? just curiosity...
Click to expand...
Click to collapse
I realized i can't sale it because I have nandroid backups within the phone and they'll still be there i think...
romdroid. said:
That's why its always recommened to have full charge when rooting or installing custom rom. I hope someone here in the forum can help you solve this issue.
Click to expand...
Click to collapse
Yeah but you know when you're a frequent flasher and are sure it only takes about 10 percent batter at the most, you don't charge it to the max but I just made a boo boo by not reading the part that said *You must be running a the rom already before flashing the update portion*.. that caused the bootloop..
Thanks a lot though. You're right
Shinare said:
you can make one looks like here:
http://forum.xda-developers.com/showthread.php?t=1403100
if you want to give it a go, will cost you a $3 cable if you mess it up, and will gain you a $300 phone if you do it right.
Click to expand...
Click to collapse
imma try to get these tools.. i definitely have some spare USB cables in my room.. just getting the phone open and stuff is the issue. Not that tech savy lol
You don't need to open your phone
Sent from my Nexus S using XDA
Get phone in to ap fastboot and go down to bp tools and then press vol+.
Phone should reboot in to a sort of recovered state (last firmware that was on phone) and allow you to charge up.
Once 100% retry flashing.
I screwed my phone several times already and thought I wouldnt recover. Through some chat help have always recovered. Same for my Charge after a few times you figure out all the tricks.
You can recover it. I've done it twice
If you check out my post it shows you a alternative and easier way charge your phone again and make it back to stock rom and no root. Then you can sell your phone for a better price or just keep it!
Ill give you $150 for it...
Ill trade you a Samsung Charge for it. Seriously though you should be able to recover.
passion8059 said:
Get phone in to ap fastboot and go down to bp tools and then press vol+.
Phone should reboot in to a sort of recovered state (last firmware that was on phone) and allow you to charge up.
Once 100% retry flashing.
Click to expand...
Click to collapse
It takes me to this message every time. anyone else got this before? see attached
Yup I had that before. Happened to me when rsding to an earlier version and the battery went low before it finished. Gonna have to use a factory cable or replace it.
Sent from my XT912
orcsbane13 said:
Yup I had that before. Happened to me when rsding to an earlier version and the battery went low before it finished. Gonna have to use a factory cable or replace it.
Sent from my XT912
Click to expand...
Click to collapse
what if the whit light is showing after plugging it up to a computer with a different USB?
hmmm i wonder if it's charging???? see attached
stepinmyworld said:
what if the whit light is showing after plugging it up to a computer with a different USB?
hmmm i wonder if it's charging???? see attached
Click to expand...
Click to collapse
nope, left mine like that for 12 hrs and it never charged any. Won't charge unless you can get into recovery and can't get into recovery because webtop is messed up.
Sent from my XT912
I get that on mine when I let it die completely (after cocking up flashing!) ... what I do is connect it to pc...get solid white light..... press up/down/power.....boots to the other screen (cant remember what its called).....gives the option for normal boot......press up to get into normal moto boot logo..... VERY QUICKLY replug to a desktop charger.... Seems to work for me! I really must try reflashing with a clean rom!
There are several ways to recover from bricked because of dead low battery. Im sure there are easier but Im just gonna post a few.
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
More expensive way for a cable but may want to have for future.
http://shop.teamblackhat.info/
More info
http://forum.xda-developers.com/showthread.php?t=1077414
http://forum.xda-developers.com/showpost.php?p=14832871&postcount=45
Thats all Im going to post for now but I have faith that it can be recovered. Dont sell unless desperate and dont want to deal with it. Send it to me and Ill try to recover and if not I can give you one of my Droid charges while I get it back up.
So, long story short, took the Phone into Sprint so they could look at my headphone jack (was cracked and left ear bud would constantly cut in and out) because its acting up.
Gave the Tech the phone without the battery in it (since he didn’t need to power up the device to clearly see the headphone jack has a huge crack in it) but I left my SD card installed. As he was walking away, I asked him if I could remove my SD card and he let me, then seen that I gave him the phone without a battery. So, I ended up giving it to him (praying he didn’t turn it on and see ViperBoys sick ass ROM booting up) and he accidently pressed the power button turning the phone on. Promptly short after, he removed the battery when the phone was on the HTC screen, didn’t even get the boot animation. I was like OHH $h!t, that gonna mess up my phone & sure as $h!t, it did… Just loops in and out of that screen resetting each time with a little vibrate then looping.
I can get into Fastboot and use ADB, I’ve flashed RUU’s, put Stock image on root of SD and let recovery restore (losing my CWM & my HBOOT 1.400), unlocked, relocked, wiped, thrown, and screamed at it with no luck.
I did do a CWM backup before even setting foot in the Store, so I do have a backup. The 1st thing I tried was restoring it through CWM recovery and that didn’t stop the looping. I can still get into fastboot via power + vol down and adb functionality is still there.
HBOOT is 1.50 and s-on is enabled..
Been reading through threads since lunch and tried many different solutions without success. It seems once a phone is this far gone, people stop responding.
Anyone have any ideas?
New phone will be here tomorrow (free of coarse courtesy of Sprint insurance) but I’ve been without a phone all day and most of yesterday. I’d like to get this one back to stock and booting before I trade it in for the replacement tomorrow
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
yousefak said:
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
Click to expand...
Click to collapse
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
lessegr said:
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
Click to expand...
Click to collapse
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
yousefak said:
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
Click to expand...
Click to collapse
BUMMER! In case the question comes up I ran "RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed" and it ran just fine.
Hmm, hardware issue. Dont see how I can check for that if it doesnt boot.
Guess I'll just have to wait for the new Phone
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
jdeoxys said:
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Click to expand...
Click to collapse
The HTC unlock went as expected. Followed the directions to the "T", then relocked, checked in fastboot (not that I could check anywhere else, LOL) and the phone says "*** RELOCKED***". Ran 2.17.651.5 RUU successfully to the finish. Still looping
WEIRD!
DarkManX4lf said:
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
Click to expand...
Click to collapse
Because I just want to know WTF happened!!! Had this Phone since release, abused\used the hell out of it by flashing ROMs constantly, restoring backups, tethering like crazy, emailing, texting, FBing...
No reason for it to crap out on me from a simple mistake, not even of my responsibility, lol!
The only issue I've had with this Phone is that damn headphone jack 1/2 way failing..
Got new phone, terrified to even think about trying to flash new ROM though
lessegr said:
Got new phone, terrified to even think about trying to flash new ROM though
Click to expand...
Click to collapse
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Threevo said:
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
DONT TEMPT ME DAMMIT! lol! Just been without a phone for almost 3 days. I'm also seeing a lot of new threads about people experiencing what I've gone through.
Woops, sprint\HTC! once again rooted, and running viperROM.... SWWWWWET!
HBOOT 1.5 and s-on is a *****!
Not to mention... But in Linux, I never got revo recovery to flash... You can do it in windows just do it via fastboot.
Took my Orig cwm bsckup "recovery" & "boot" .img and threw them @ the phone via command prompt.
After cwm was restored, I restored my 4\29\2012 backup that I made before I entered the Sprint store, now my phone is back to the exact same way
It was. Pretty Damn sweet!
So much info here!! I'm truly thankful!!!
Sent from my PG86100 using xda premium
So after my battery ran out today I realized that Clockworkmod does not allow charging while the phone is off... This left me in a tricky situation where I could not charge my phone at all. I had seen others mention using another battery but I did not have one on hand. Here's how I replaced Clockworkmod with Amon-Ra to fix it (this also works for all recovery images that I know):
REQUIREMENTS:
-Computer with ADB
-Rezound with Clockworkmod or other faulty recovery
-Amon-Ra's recovery image (attached)
1) Unplug USB and remove battery
2) Put battery in
3) Plug USB into computer (with ADB installed)
4) Enter "adb devices" until you see your Rezound show up as recovery. During this time, the orange LED may either blink shortly first or be solid for a few seconds and then turn off. Once it turns off, it should be accessible over ADB.
5) Grab your amonra recovery img and use adb to copy to phone.
Example: adb push amon-ra-3.15.img /tmp/amon-ra-3.15.img
6) Flash the image to recovery.
Example: adb shell flash_image recovery /tmp/amon-ra-3.15.img
7) Reboot your phone (adb reboot) and repeat steps 1-3 (but this time using wall outlet)
8) Sit back and let Amon-Ra save your Rezound. Once your orange LED has been solid for over a minute, you should be good
Nice guide
Koush really needs to fix that problem or discontinue it for our phone
Sent from my Galaxy Nexus using Tapatalk 2
superchilpil said:
Nice guide
Koush really needs to fix that problem or discontinue it for our phone
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It is discontinued. I don't even really know where to get it anymore lol.
Granted, I don't use CWM, but nice job.
con247 said:
It is discontinued. I don't even really know where to get it anymore lol.
Click to expand...
Click to collapse
Rom manager. Also he offers touch for pay (which is what I mistakenly purchased thinking it could mount the internal sd. Either way though I agree, it is not safe for the average root user even to have a recovery that doesn't allow charging even through a wall outlet. It should only list Amon-Ra's under alternate recovery.
Chyrux said:
Granted, I don't use CWM, but nice job.
Click to expand...
Click to collapse
Thanks, I know the average user is using Amon-Ra or TWRP but figured I'd put this here so we have a clear guide for getting out of this situation where some users may end up returning their phone to HTC (possibly getting charged after the fact)
con247 said:
It is discontinued. I don't even really know where to get it anymore lol.
Click to expand...
Click to collapse
Its odd, those same people who can't search to find out how to fix the problem, can find CWM
Sent from my Galaxy Nexus using Tapatalk 2
I'm fairly new to the Rezound. Came from the Nexus side because I wanted a more multimedia-friendly device (better external speaker/camera/same res). I bought mine pre-rooted and flashed to Clean, which was pretty nice - until I ran into this issue. I bought another battery from Verizon and hooked the other one up to an external charger. I figure it won't hurt to have two batteries anyway.
I know a ton of people have bad things to say about CWM but is this really the only issue? It flashes just fine, right? I ran a nandroid on what I have now and tried to install the latest leak, but I got a ton of reboots. Eventually reverted back to Clean. Either way, thanks for the writeup. Would have saved me a ton of stress over the weekend, hahaha.
Nice work djh816. this was the thing i have always feared lol. matter of fact, this is a HUGE weight lifted out of my mind. Thanks so much for this. keep up the good work
nice guide but i dont think anyone uses cwm anymore. still, thanks
I do. Haven't had issues. I just, if you can believe it, charge my battery before I do anything.
Sent from my ADR6425LVW using Tapatalk 2
Btw, I would change, just to be safe, but haven't seen instructions for doing so, and don't really want the drama that USUALLY comes from asking a question (can't always find what you are searching for).
Sent from my ADR6425LVW using Tapatalk 2
RED ZMAN said:
Btw, I would change, just to be safe, but haven't seen instructions for doing so, and don't really want the drama that USUALLY comes from asking a question (can't always find what you are searching for).
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
The OP of this thread are the instructions... Just do Steps 2-6.
Edit: or use hasoon2000's first AIO toolkit, which has AmonRa as a flash option (also another lingering source of CWM):
http://forum.xda-developers.com/showthread.php?p=22696442
RED ZMAN said:
Btw, I would change, just to be safe, but haven't seen instructions for doing so, and don't really want the drama that USUALLY comes from asking a question (can't always find what you are searching for).
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Haha I was fine as well with Clockworkmod Touch and had no clue it even had that problem until my battery finally drained all the way. Then I was SOL. But yea as he said, following those instructions simply replaces the recovery image. All your data will still be in tact (aside from your clockworkmod backups if you have them but Amon-Ra can read those too I think)
Yeah, I figured those instructions would work. You should advertise this as a how to swap between them also. There are others using CWM, and just not talking about it.
Thanks.
Sent from my ADR6425LVW using Tapatalk 2
I have an easier solution, while phone has been dead for 5-10 minutes, hold power button and as soon as screen flashes plug in the device. Works every time. I also have 3 batteries, 1 original, 2nd from my replacement from warranty, 3rd is extended. I don't ever even change batteries though.
Funny that people are still having/talking about this issue.
I remember when the issue first popped up on the Rezound and people were clueless. All kinds of theories as to the cause and solution.
I knew of the cause from a few phones back... CWM has a history of issues with charging while powered off. I learned of it from an initial release of CWM for a different phone would that when trying to charge with it powered off, would turn on the screen.
Easiest way is to run the command
adb reboot download
boom phone restarts...
I have had this modded version of CWM touch by someone else (I will let him say who he is just in case he does not want to take credit).
It is a modded version of CWM 5.8.1.4-Touch that solves the charging when off problem.
I can not support it but can assure you it works since I have been using it since the beginning of April. I do switch between this and AmonRa for testing my ROM but all my backups are with this.
Still need to copy the .hidenandroidprogress file from internal to external clockworkmod folder to solve the freeze problem when backing up or restoring.
Just install it just like any other recovery.
NOTE: If anyone want to take this and start another thread with it that is fine by me. I just don't have time which is why I never posted it before.
I ended up doing it through fastboot, as I'm a bit more familiar with that, but thanks for the notes and link. I'm now on Amon Ra.
Anything I need to know as a CWM user since, oh, the G1?
And do I need to worry about moving that file so backups work, like you did in CWM?
Thanks again.
Thanks man, this this is totally pimp, sent you a donation - get yourself some good beer!
A friend of mine has an EVo V4G. He recently did the wire trick and while trying to flash the eng hboot to his device it just turned off. his hboot is 1.57.5757 he had TWRP installed and though roms would flash fine each time he would boot loop. It doesn't respond to any button combo nor does a charge light come on while plugged in. Any help would be greatly appreciated as he lives a Looong way from me and I can't exactly drive there. Troubleshooting via Google talk sucks plus I'm running out of answers
ian577416 said:
A friend of mine has an EVo V4G. He recently did the wire trick and while trying to flash the eng hboot to his device it just turned off. his hboot is 1.57.5757 he had TWRP installed and though roms would flash fine each time he would boot loop. It doesn't respond to any button combo nor does a charge light come on while plugged in. Any help would be greatly appreciated as he lives a Looong way from me and I can't exactly drive there. Troubleshooting via Google talk sucks plus I'm running out of answers
Click to expand...
Click to collapse
It's really hard to tell with that much information, especially since he can't turn the phone on to get more data, but if his bootloader flash got interrupted somehow he might have bricked the phone. This thread is specifically about how to "unbrick" after that happens and he should probably read at least the OP to see if that fits his situation.
One thing he can try that has worked for some is to charge it on the A/C adapter overnight and see if he can start the bootloader in the morning after removing/replacing the battery.
ramjet73
ramjet73 said:
It's really hard to tell with that much information, especially since he can't turn the phone on to get more data, but if his bootloader flash got interrupted somehow he might have bricked the phone. This thread is specifically about how to "unbrick" after that happens and he should probably read at least the OP to see if that fits his situation.
One thing he can try that has worked for some is to charge it on the A/C adapter overnight and see if he can start the bootloader in the morning after removing/replacing the battery.
ramjet73
Click to expand...
Click to collapse
That's essentially what I told him to do. The only issue is that the op states it is only for s-on devices. He had successfully flashed juniperbear s-off. That's what worries me. However thanks man! Mind if I follow up with you tomorrow?
Sent from my Nexus 4 using Tapatalk 2
ian577416 said:
That's essentially what I told him to do. Thanks man! Mind if I follow up with you tomorrow?
Click to expand...
Click to collapse
Just post here. Other people might have ideas as well depending on what he finds after he's charged it for a while.
ramjet73