Related
Hello guys, you'll have to excuse me for the wall of text, but it is necessary to fully describe my ordeal.
I bought an used atrix about 4 months ago from ebay (and i'm now deeply regretting it, too many issues). When I first received the phone I was unable to hear callers, even though they could hear me (badly, but could). I resolved that the easiest way possible: I bought a headset. Even with that issue and since it was impractical for me to return the phone because I'm in a different country (customs alone were over $100) I continued to use it. I flashed CM7 and ATT N_.37, flashed TWRP 2.1 and I enjoyed my phone for a couple months (even with the audio issue). Then one day, I went to bed with my phone on a full charge and in the morning I found it turned off. I tried to turn it back on and nothing happened. I thought maybe the battery had been drained by something, because I had left 3G data enabled. I tried to charge it and nothing happened, except the phone started to get really really hot in the lower part so I decided to disconnect it. I tried again a couple hours later and same thing happened. Next day I hit the power button and was able to enter android recovery. I wiped and factory reset, reinstalled cm7, gapps and radio and phone turned on and showed around 60% charge and it seemed fine and then all of a sudden the led started glowing light blue. Then the phone shut down and started to boot loop. I took off the battery, let it rest a while and then when I turned it back on everything worked fine (still, minus audio). That was two weeks ago. Today, it started to do the something similar but worse. Blue led flashing and boot loop are there but if I enter recovery I can't find anything in the sdcard, and if I place a microsd in the slot it isnt recognized. Also, led is flashing blue even while in recovery so I doubt it is a CM7 issue.
tl;dr My phone is dead. Can it be fixed or do I now own a $250 paperweight?
Try to flash your phone with your stock firmware using rsd lite
here a list of firmwares ... http://forum.xda-developers.com/showthread.php?t=1125944
WARNING! : flash it with YOUR stock sbf !!!
isn't that dangerous? from what i understand with this post it seems as if it isn't advisable to use an sbf on an unlocked bootloader.
not.a.troll said:
isn't that dangerous? from what i understand with this post it seems as if it isn't advisable to use an sbf on an unlocked bootloader.
Click to expand...
Click to collapse
Only if you're downgrading. It can work if you do it properly, but it's not recommended. Fruitcakes are the more foolproof way to go.
well i chickened out of the .sbf flash and just tried the moto-fastboot stock restore available elsewhere. while everything seemed to flash correctly i am still bootlooping/shut down. also, light blue led still there and sometimes i get stuck on bootscreen and can't even enter recovery. guess ill have to take it to a shop and see if something can be done. else S>atrix 4g for parts.
D:
hello to all
my atrix 4g originally was in firmware 4.5.141.MB860 ATT, i unlocked the bootloader succesfully and flash CM7... but for reasons of life (silly excuse jejeje) i want to take it back to the original fw... with this files: Blur_Version.4.5.141.MB860.ATT.en.US and 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf.gz can i go back to stock fw? with this stock files i lose the boot unlock? is this a safe method? and what is the safest?
thanks for your help and greetings from Colombia (and sorry for my bad english)
Flash the latest sbf for your phone. I've done several with no problems. Yes, you do lose the unlocked bootloader though.
This will return you to stock. I used the same files.
not.a.troll said:
well i chickened out of the .sbf flash and just tried the moto-fastboot stock restore available elsewhere. while everything seemed to flash correctly i am still bootlooping/shut down. also, light blue led still there and sometimes i get stuck on bootscreen and can't even enter recovery. guess ill have to take it to a shop and see if something can be done. else S>atrix 4g for parts.
D:
Click to expand...
Click to collapse
I also have been through several phones with this issue. Although you can flash the sbf with no troubles, that is really only good for sending it into warranty. From my experience, this is a hardware issue, and flashing the stock sbf doesn't solve the problem. If you do not have warranty, a repair shop is your best bet.
Good luck.
Repy
x-geo said:
hello to all
my atrix 4g originally was in firmware 4.5.141.MB860 ATT, i unlocked the bootloader succesfully and flash CM7... but for reasons of life (silly excuse jejeje) i want to take it back to the original fw... with this files: Blur_Version.4.5.141.MB860.ATT.en.US and 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf.gz can i go back to stock fw? with this stock files i lose the boot unlock? is this a safe method? and what is the safest?
thanks for your help and greetings from Colombia (and sorry for my bad english)
Click to expand...
Click to collapse
Hi,
Yes you can go back to your stock rom. Another yes, you will lose all your files and your bl unlock too. You have to start everithing from the begining. this is a safe method if you flash your own rom.
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.
So I know there is a TWRP recovery (currently using it, very nice job and am very thankful for the work put into it).
My question is, is there an updated recovery that fixes powered off charging? Additionally I notice the battery percentage indicator says 66% regardless of actual battery percentage, put of curiosity (not necessity) is this fixed. And lastly can we charge while in recovery mode?
While I do not see either issue as a major problem right now my concern is if I ever accidentally let my battery die, as a fix is not as simple as pulling the battery out and charging it in another phone/dock charger.
There hasn't been an updated version of TWRP yet, so no offmode charging or fixed battery % in Recovery. I just flashed back to the stock recovery so I can charge. It's not a big deal or long process to flash TWRP back when I'm ready to install a ROM or something else.
As for charging in Recovery, I would tend to think that it won't work. Although you could try charging while on the bootloader screen. No idea if that will work or not. Probably worth testing both if you plan to keep TWRP on your device.
911jason said:
There hasn't been an updated version of TWRP yet, so no offmode charging or fixed battery % in Recovery. I just flashed back to the stock recovery so I can charge. It's not a big deal or long process to flash TWRP back when I'm ready to install a ROM or something else.
As for charging in Recovery, I would tend to think that it won't work. Although you could try charging while on the bootloader screen. No idea if that will work or not. Probably worth testing both if you plan to keep TWRP on your device.
Click to expand...
Click to collapse
Thanks for the heads up. Any chance you have a link to the stock recovery?
Check your PM.
911jason said:
Check your PM.
Click to expand...
Click to collapse
could you help me out as well with this file?
WARNING! I got this from another user, not sure where it came from. It works on my AT&T One X+, I can't speak for any other device versions.
http://dl.dropbox.com/u/17351188/StockRecovery.img
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.