Hey folks,
I'm having some issues with my ATT Atrix. The phone keeps rebooting at the "Rethink Possible" screen. I bought this phone off of somebody on CL. I actually had the phone make it past the att screen a couple times. It made it to the setup up Motoblur screen but when I clicked start it just skipped it and takes me to the "Emergency Calls Only" screen. However the phone would just restart eventually at this screen as well. When the screen timed out I could not get the screen to turn back on at this point unless I unplugged the USB cord and plugged it back in. When the phone was on the Emergency Calls screen, my computer did recognize the phone and it did launch the motorola website. While I had the phone at this screen it did say that it had to force close android.process.com. I am coming from a captivate with rooting and flashing roms so I am familiar with Android. I am just trying to figure out where the problem could be with my Atrix. I am hoping somebody can point me in the right direction. Thanks for your time!
Your best bet will be to SBF that back to stock. Have you tried that yet? If not search for RSD Lite and SBF in the forums. There are several links and guides.
Is it unlocked?
I am not sure if it is unlocked as I cannot get past the emergency call screen. However, I will search SBF and research that option of setting it back to stock. I know when I flashed roms on the Captivate I would enter into recovery mode. I see in the Atrix that I would have to use Fastboot? The only reason I am worried about flashing a rom is that the phone reboots on its own so I would not want to hard brick it if it rebooted during a flash.
If it's unlocked you should see the word "unlocked" in the upper left corner of the boot logo screen, unless it was unlocked then flashed back or fruitcake in which case it will not say unlocked.
You should not have issues flashing from recovery if you have enough juice in your battery, which you maybe don't if you have been letting it sit rebooting. The rebooting is more than likely caused by an issue with a kernel, ROM, etc. Think of recovery as being similar to the BIOS on a PC. You enter into BIOS before the OS boots, etc., and this is before all the hardware has initialized and drivers have loaded, so the problem causing the reboots should not exist at that time. I would definitely try flashing a different ROM, and also a stock kernel.
It never said unlocked when I got the phone to turn on. I am having trouble getting the phone to turn on this time. I have downloaded RSD Lite and the 4.5.91 .sbf file to flash. I am just having trouble getting the phone started. Are there any ways to force the phone on. When I press the power button the green LED stays lit but nothing comes on the screen. When I plug into the charger it shows the moto symbol then goes to the Battery charging screen. Im not sure if the battery is correct because it says BHX5 1500mAh on the battery. Thanks for your help guys!
Update: I can get the phone into Fastboot and then Android Recovery Mode when the phone is plugged into the wall charger. However when I connect the phone to the computer via USB it just shows the green led when the phone is powered on. Anyway I can get the phone to boot into Fastboot while connected to the computer via USB?
Bump. Any way to get the phone to turn on when plugged into the computer or anyone know why there would be an issue of the phone turning on when plugged into the wall charger but only showing the green led when plugged into the computer? The battery shows 100% charged. Thanks
Update: I got the phone into RSD mode and flashed the 4.5.91 sbf but the phone only goes to the Emergency Call Screen. Is there anything else that can be done?
nishith611 said:
Update: I got the phone into RSD mode and flashed the 4.5.91 sbf but the phone only goes to the Emergency Call Screen. Is there anything else that can be done?
Click to expand...
Click to collapse
Did you fastboot -w before flashing the sbf? (Guess you don't really need to when flashing a sbf)
What may also help is flashing the boot.img file from whatever ROM you are using via fastboot.
Don't know if this will help, but it solves an issue when flashing to a different ROM from CM7, so maybe will help for you.
I know this might sound dumb, but do you have a sim card installed? Also, try to boot into recovery and just do a factory reset. @CaelanT already pointed out that this should be unnecessary since you flashed an sbf but it wouldn't hurt to try.
nishith611 said:
Update: I got the phone into RSD mode and flashed the 4.5.91 sbf but the phone only goes to the Emergency Call Screen. Is there anything else that can be done?
Click to expand...
Click to collapse
EDIT: I reread the OP and realized he had already tried to bypass the start screen.
That is not the correct battery. That is actually a battery used for the Droid X/X2. It seems they have pulled a switch-a-roo on you. (Probably because the Atrix battery could be used as an "Extended" battery in the DX/DX2) Anyways, it should still work but you can find the correct battery online, it should be a BH6X and should have a capacity of 1880/1930mAH.
nishith611 said:
...Im not sure if the battery is correct because it says BHX5 1500mAh on the battery. Thanks for your help guys!
Click to expand...
Click to collapse
Thanks for the reply. I tried to get the phone into recovery mode. I get to the Exclamation Point screen but it gives me no options for a factory reset. I saw that you have to touch the lower right hand side of the screen, but this doesn't do anything for me.
As far as flashing the boot.img file for the rom that I used. I flashed the stock 4.5.91 motorola rom. How can I find boot.img and would I flash it using RSD?
Also would it help if I flashed a custom rom instead of the stock Motorola 2.3.4 rom?
Could the battery not being the BH6X rom be the issue for it not getting enough power to stay on by itself?
Thanks for the help guys, I really appreciate it!
No, the sim card was not installed during the flash. However, I did install the sim card afterwards but the phone boots up and goes to the big green battery charging screen and does not go any further. However when the sim card is not plugged in I can get the phone to go to the Emergency Call screen.
nishith611 said:
As far as flashing the boot.img file for the rom that I used. I flashed the stock 4.5.91 motorola rom. How can I find boot.img and would I flash it using RSD?
Click to expand...
Click to collapse
The following are the instructions for flashing the boot.img. this was the solution to bootloops when trying to restore to a different ROM after CM7, but as I said previously, you never know if it will help or not:
1.Open up the Zip file of your current Blur ROM (Ninja, CherryBlur, Alien, etc.)
2.extract the boot.img file and copy to the directory where your fastboot is.
3.Pull phone battery & reinsert
4.Power on phone and go straight to Fastboot mode (Power + Vol Down)
5.Type "fastboot flash boot boot.img" (exclude quotation marks)
6.Once flashed, reboot phone using "fastboot reboot"
Sorry, don't know how to extract the boot.img from a sbf. Did a quick search and couldn't find instructions. Not something I have done before. Maybe someone else can help with this. I don't even know if this will work, but anything is worth a shot when you are stuck.
<edit> Which CWM are you using?
You can flash Romracers via fastboot if you are not using it. This may help you get into recovery.
Update: I got the phone to recognize the sim card and make phone calls and get wifi active. But the phone still reboots by itself. I can use all the functions of the phone except it just reboots by itself. I got into the About phone section and it says
Android: 2.3.4
Kernel: [email protected] # 2
I can get into the Android Market as well as everything else. Could this be a hardware issue that causes the phone to reboot by itself within a minute or so?
Edit: I can get the vol up and down buttons to work while the phone is working but the power button is not responsive to let me power the phone off. Could a hardware issue with the power button be causing the constant reboot loop?
Update: I got the phone to function with the OS working just fine (phone calls, texts, emails, etc..) but it keeps restarting on its own. The power button still does not work however, could this be a hardware issue? Thanks
Related
I just tried unlocking the BL from my official AT&T gingerbread using this guide, I tried flashing the sbf file with RSD and it got stuck and now my phone stays at this with the difference that mine gives me the option to try fastboot, RSD mode, Android Recover and another pletora of options I'm not sure i want to name.
So being able to try RSD again, i tried flashing this and it was appearently working but when it tried to set the device on BP Pass through mode, the device would go back to the Infamous screen and it wouldn't move from there.
Am I screwed? Do i have option?
I'm going to try to flash the stock FW to see what happens
Kenchinito said:
I just tried unlocking the BL from my official AT&T gingerbread using this guide, I tried flashing the sbf file with RSD and it got stuck and now my phone stays at this with the difference that mine gives me the option to try fastboot, RSD mode, Android Recover and another pletora of options I'm not sure i want to name.
So being able to try RSD again, i tried flashing this and it was appearently working but when it tried to set the device on BP Pass through mode, the device would go back to the Infamous screen and it wouldn't move from there.
Am I screwed? Do i have option?
I'm going to try to flash the stock FW to see what happens
Click to expand...
Click to collapse
use the automatic unlock tool found here:http://forum.xda-developers.com/showthread.php?t=1182871&highlight=automatic
do option 1 then option 3 (only use option 3 if on gingerbread) and you're good to go
Fastboot then use fastboot oem unlock command on PC. Reboot and it should work.
Sent from my MB860 using XDA Premium App
Thanks, I'll try it out and post back
I forgot to mention that my phone seems to be low on battery. Does it charge if it's not on the OS?
Noob Killed his phone
Hello, First time Poster here, please bare with me...
I really shouldn't of touched this.....
I have an Atrix w/ the newest updates to it, and attempted to unlock the phone. Everything started well, then it failed while writing to the device. Now, when I attempt to boot, I get the similar message of
SVF:405;1:2
Failed to boot 0x1000
With a 14 available options. I can get into fastboot, though I honestly am not sure what to do from there. I have the fastboot s/w downloaded, along with the gingerbread OS.
Did I just kill my phone?
I haven't still fixed mine because of the battery, I still have to find an external charger. Though, you can try the link from above.
Ok, I did the steps and now my phone is at a screen with the motorola logo with the dual core name on it and it has the word Unlocked on top of it.
What should i do?
the boot screen with motorola logo and unlock in corner will take awhile to load usually like 10 minutes but if it doesnt load for example i let mine sit for an hour and never loaded i just took the batter o and restart it and it rebooted and worked but use that as a last resort give it some time!
Omg i just fixed it!! Thx for the help!!
Mrniceguy0921 said:
the boot screen with motorola logo and unlock in corner will take awhile to load usually like 10 minutes but if it doesnt load for example i let mine sit for an hour and never loaded i just took the batter o and restart it and it rebooted and worked but use that as a last resort give it some time!
Click to expand...
Click to collapse
i think if the phone can be detected by PC, it should be a soft brick.. it is unfortunate my phone is booting loop and can not be read by PC, you're better than me..
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Failed to boot, sounds like hardware failure
but you can try ezSBF, link in my list, might work.
sd_shadow's [Collection] of Links for Droid X2
Sent from my Clear using xda premium
vernon428 said:
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Click to expand...
Click to collapse
im not completely sure why you sbf'd after rooting the first time? no need for that. i would read up a bit more if you do get it working, watch tomsgt123 's videos on youtube so you know what youre doing. and you used the Gapps for cm10.1 not our version. that is why keyboard didnt work. read read read.
after reading abain, i guess you were on 2.3.5. and thats why you sbf'd. but rooting was not needed before sbf. hope you have better luck next time .
flash will fail if battery is too low, should be a low battery error though, but maybe not every time.
if it is low battery, you will need a charged battery or a tbh programing adapter
link to TBH adapter and dx2 external charger in my list
Sent from my XT862 using xda premium
Lorenzo VonMatterhorn said:
im not completely sure why you sbf'd after rooting the first time? no need for that. i would read up a bit more if you do get it working, watch tomsgt123 's videos on youtube so you know what youre doing. and you used the Gapps for cm10.1 not our version. that is why keyboard didnt work. read read read.
after reading abain, i guess you were on 2.3.5. and thats why you sbf'd. but rooting was not needed before sbf. hope you have better luck next time .
Click to expand...
Click to collapse
Do you have any advice on where I should go from here then? My phone is basically a useless hunk of technology until i can get it to boot back into cyanogen 10, or sbf it back to an android operating system. The RSD mode always fails when I try to normally sfd, but i have not tried EZ sbf yet..... any other suggestions?
vernon428 said:
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Click to expand...
Click to collapse
mine did the fail to boot thing back in september, i have to get a new x2. Try using a different computer, good luck
vernon428 said:
Do you have any advice on where I should go from here then? My phone is basically a useless hunk of technology until i can get it to boot back into cyanogen 10, or sbf it back to an android operating system. The RSD mode always fails when I try to normally sfd, but i have not tried EZ sbf yet..... any other suggestions?
Click to expand...
Click to collapse
With it powered off, hold power and volume up . See if you can get it into rsd mode . If so, sbf from there . Hope it works .
Lorenzo VonMatterhorn said:
With it powered off, hold power and volume up . See if you can get it into rsd mode . If so, sbf from there . Hope it works .
Click to expand...
Click to collapse
I can get into RSD mode, and the phone seems to SBF okay, until the SBF on the computer displays "failed", and the phone displays an error message. I am also using a fully charged battery during the whole process (my friend has the same phone so i swap batteries out with him to charge).
vernon428 said:
I can get into RSD mode, and the phone seems to SBF okay, until the SBF on the computer displays "failed", and the phone displays an error message. I am also using a fully charged battery during the whole process (my friend has the same phone so i swap batteries out with him to charge).
Click to expand...
Click to collapse
and you tried EZsbf?
try ezSBF
if you can't get it to work, you can go back, try using rsd lite, and look for Driver issues
Hello. I'm new to the forum, and the issue that brought me here as had me fulling my hair out of the last three days.
I'll try my best to make this short as possible. I have (obviously) AT&T Lg Optimus G (E970) that was running 4.0.4. i rooted and unlocked it and flashed a cm 10.1 using TWRP. Yesterday tried to flash a zip for a transparent status bar mod. But the flash resulted in CM getting stuck on the splash screen. So i booted in TWRP recovery mode to restore from a recent backup. In the midst of wiping my rom and going to restore, i guess my phone died (which was weird because it had a substantial charge). Then it would no longer power on, and the only was i could get ANY response was by plugging it on the charger. All i get it the red indicator light. my phone will only turn on when plugged into the computer. from there the only two thing i can do is enter download mode and boot. and when i try to boot, i will get the lg logo for a moment and the the screen cuts out and goes back the the flashing red light.
so I trien the LGNPST method.
i downloaded the auto LGNPST and installed just fine. downloaded teenybin and lg stock bin. i've tried to flash both (put phone into download mode, select the dll and select the bin file). what happens is everything starts off fine, then when it gets to 67% the phone reboots, then goes back to the flashing red indicator light, and a message on LGNPST will pop up saying the phone has been disconnected, and to reconnect to continue. so i'll unplug the phone, plug it back in, and put it in download mode, and hit continue. LGNPST will say complete but the phone will still be just sitting in download mode. and if i unplug it, it's goes back to square one (red flashing indicator light)
EDIT: i was flashing the v11c stock bin. i just flashed the v20j bin and now we're boot looping while plugged in (lg logo for about 2 seconds, shut off, repeat) progress???
SO SO SORRY FOR THE LONG READ. Just trying to give as much info as possible hoping it helps.
My question is, is this a hard or a soft brick, and do i have any options left? after researching on here i'm hoping JTAG isn't my only option (I don't have the time or funds to go that route) and i saw someone mention taking it back to at&t, butIi don't think that would help me any since rooting the phone voids the warranty, correct?
I'd be eternally grateful for ANY advice. i'm at my wits end, and i've been google researching this for so long i'm starting not to even comprehend what i'm reading. PLEASE HELP!! And thank you so much in advance.
goplatinum said:
Hello. I'm new to the forum, and the issue that brought me here as had me fulling my hair out of the last three days.
I'll try my best to make this short as possible. I have (obviously) AT&T Lg Optimus G (E970) that was running 4.0.4. i rooted and unlocked it and flashed a cm 10.1 using TWRP. Yesterday tried to flash a zip for a transparent status bar mod. But the flash resulted in CM getting stuck on the splash screen. So i booted in TWRP recovery mode to restore from a recent backup. In the midst of wiping my rom and going to restore, i guess my phone died (which was weird because it had a substantial charge). Then it would no longer power on, and the only was i could get ANY response was by plugging it on the charger. All i get it the red indicator light. my phone will only turn on when plugged into the computer. from there the only two thing i can do is enter download mode and boot. and when i try to boot, i will get the lg logo for a moment and the the screen cuts out and goes back the the flashing red light.
so I trien the LGNPST method.
i downloaded the auto LGNPST and installed just fine. downloaded teenybin and lg stock bin. i've tried to flash both (put phone into download mode, select the dll and select the bin file). what happens is everything starts off fine, then when it gets to 67% the phone reboots, then goes back to the flashing red indicator light, and a message on LGNPST will pop up saying the phone has been disconnected, and to reconnect to continue. so i'll unplug the phone, plug it back in, and put it in download mode, and hit continue. LGNPST will say complete but the phone will still be just sitting in download mode. and if i unplug it, it's goes back to square one (red flashing indicator light)
EDIT: i was flashing the v11c stock bin. i just flashed the v20j bin and now we're boot looping while plugged in (lg logo for about 2 seconds, shut off, repeat) progress???
SO SO SORRY FOR THE LONG READ. Just trying to give as much info as possible hoping it helps.
My question is, is this a hard or a soft brick, and do i have any options left? after researching on here i'm hoping JTAG isn't my only option (I don't have the time or funds to go that route) and i saw someone mention taking it back to at&t, butIi don't think that would help me any since rooting the phone voids the warranty, correct?
I'd be eternally grateful for ANY advice. i'm at my wits end, and i've been google researching this for so long i'm starting not to even comprehend what i'm reading. PLEASE HELP!! And thank you so much in advance.
Click to expand...
Click to collapse
If it is hard bricked when connected to computer it will show up in device manager as QDUSB Device or something similar. You could try to do a factory reset with button combo, be sure phone is powered off then hold power and volume down until menu shows up.
You Can Also Try TeenyBin If Factory Reset Does Not Work
Regards,
acervenky,
XPT
thanks for the reply guys. it looks like my phone is showing up in the device manager under ports as "LGE AndroidNet USB Serial Port (COM3)" is that a good sign? i'm going to try flashing teenybin again.
goplatinum said:
thanks for the reply guys. it looks like my phone is showing up in the device manager under ports as "LGE AndroidNet USB Serial Port (COM3)" is that a good sign? i'm going to try flashing teenybin again.
Click to expand...
Click to collapse
Yes, you are not dead in the water. Proceed, young grasshopper.
Sent from my Optimus G using xda app-developers app
All the custom, unofficial 4.2.2 roms I found on XDA require that you be on the latest LG 4.1.2 OTA.
There are also links to stock rom and kernel so you don't have to mess with LGPT whatever. No need to do OTA etc, if you flash this.
http://forum.xda-developers.com/showthread.php?t=2219953
I also found TWRP to be far easier to install, which is installed by default I think with FreeGee. But you can find thread for the latest TWRP 2.6. TWRP makes flashing and wiping cache/dalvik super easy.
Ok, so i'm starting to think this is a battery issue as opposed to a hardware issue. i could still be wrong. I've flashed the stcok rom after stock rom. When i plug my phone into a computer usb port it LG logo boot loops (and this is the only way i can get to download mode), but when i plug it into the usb wall charger, i just get the red flashing light and no other response. when it's not plugged in i get nothing.It's still showing up as "LGE AndroidNet USB Serial Port" in my device manager and i can still get to dpownload mode just fine, so i know all isn't "according to what i've read and been told". So i'm running out of fixes. I did come accross a thread on here suggesting i unplug the battery and plug it back up. So i'll be getting the tools and praying that works.
I did also come across an interesting thread on another forum. They were saying how id you allowed your battery to drain all the way to true zero (which i think might be possible because my phone died in recovery mode), it wouldn't have enough juice to initiate and monitor the charging process. If this is the case, can the batter be brought back to life? a jump start or something (lol)? or will i have to just replace the battery?
THANK YOU SO MUCH FOR THE HELP SO FAR GUYS.
When you used lgnpst to go to 11c it boot looped because you tried to go backwards from cm. If you did a factory reset afterwards with button combo it should boot. Also can you get into recovery after flashing teenybin to do a reset and flash a ROM?
adfurgerson said:
When you used lgnpst to go to 11c it boot looped because you tried to go backwards from cm. If you did a factory reset afterwards with button combo it should boot. Also can you get into recovery after flashing teenybin to do a reset and flash a ROM?
Click to expand...
Click to collapse
i did a factory reset a few times, but it still never booted. and whenever i LGNPST, when it hits 67% the phone reboots and just starts bootlooping (if i flash a stock rom) if i LGNPST teenybin, at 67% the phone will shut off and the flashing red light will just come up. and after each a message will say phone was unplugged or lost connection. after both instances ill plug it back up and put it in download mode again to finish and it will complete, but the phone will just be sitting there in download mode. and if i reboot.... bootloop city.
i cam across this thread that seems to detail my issue perfectly. so i'm going to attempt a teenybin flash one more time to tryt to get recovery mode (havent been able to get it at all), and if that doesn't work i'm going to do a battery pull..
http://forum.xda-developers.com/showthread.php?t=2261803&highlight=battery
BATTERY UNPLUG WORK LIKE A CHARM. again, i followed the method [r.]GimP laid out here http://forum.xda-developers.com/showthread.php?p=43732147#post43732147
i was nervous because i've never opened my (or any other) phone before.
and thanks to the tot link provided by zymphad above, i'm now running jb 4.1.2
THANK YOU GUYS :highfive:
I found LG's camera lacking, but 4.2 has an update for that, plus the camera mod, much improved I think.
Running RootBox great now with 124mhz idle, GPU downclocked to 200 and CPU undervolted to 85, stable and cool. I don't 3d game on phones.
Glad you fixed it, I just hope someone makes a high capacity internal battery for us since taking it apart isn't that difficult.
Sent from my Optimus G using Tapatalk 4 Beta
Hello, I have an HTC Amaze for over a year now. It was working fine, I rooted it CWM 5. and I installed Android revolution custom ROM. Until 2 weeks ago my battery was giving me some trouble, so i put away the phone for a bit, I bought a new battery then I notice the phone wasn't coming on. SO i charge for an entire day it still wasn't charging. I carried it to the shop. They said, that they don't know whats wrong with the phone.
I came home and decide am going to fix it my self i tried powering it into recovery mode, hard reset. screen is still blank, at lease that is what I thought. I look closely and then i notice the phone was in recovery mode but no lights were on in the screen. So normally I thought what anyone would of thought, the bulb in the screen or some kind of wiring went bad. The i tried wiping cache davlik install new new rom. Nothing worked. and this was defficult because I had to use a flash light to see on the screen. Lastly, i just click reboot and then the phone lights up perfectly and HTC logo comes up and then it blanks off again. So can anyone help? any advise
Sent from my HTC One using XDA Free mobile app
keronmat said:
Lastly, i just click reboot and then the phone lights up perfectly and HTC logo comes up and then it blanks off again. So can anyone help? any advise
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Find the way to install adb and communicate with the phone via adb and fastboot. If you can do that, you will be able to install anything necessary to get the phone working again.
First however, remove the battery, wait a few seconds, reinsert the battery and charge the phone overnight. Next day, try and start phone usual way--see what happens.
If NOTHING happens and you get a black screen, remove battery again for a few seconds, reinsert, and this time hold the power button in for AT LEAST 20 seconds.
See if that starts the phone.
If you get absolutely nothing again, find the "Unbricking Project" thread, but if you get any kind of screen, see if you can boot to recovery and restore anything. If you get a screen but can't do any kind of restore at all, find instructions for adb and fastboot I mentioned earlier, so you can install a new recovery and flash a new rom..
I did everything you said. Except I complete forget how to flash recovery and custom rom from my pc but when I type command in fastboot "adb devices" it was successful.
However, I charge the phone and I got into the recovery mode again and the wipe everything and then click backup and recovery. I rebooted the phone and it came on as if its a brand new HTC Amaze. I had the phone working i rejoice for a bit and then I realize I forget to put in my sim card. So i turn the phone off, put in the sim card. The same problem again. No led, no light in the screen, the phone atomatically boots into recovery mood.
One more thing. when booting into recovery mode. the phone doesn't go where I see the 3 android at the bottom and you see, fastboot, reset etc. It goes straight to cwm screen.
keronmat said:
One more thing. when booting into recovery mode. the phone doesn't go where I see the 3 android at the bottom and you see, fastboot, reset etc. It goes straight to cwm screen.
Click to expand...
Click to collapse
I think that is what you should see when you boot into recovery.
Do whatever you did before to get the phone lit up again, then change the display settings to maybe 3/4 brightness for instance. Reboot the phone normal reboot and see if it comes back with light.
If it does, maybe you are fixed enough to install the sim.
Do you possibly have a nandroid backup saved somewhere, you could put it back in the phone via recovery?
The phone is lit up again like you asked me to do. It was hard to see in recovery mode. But i used a flashlight to look on the screen of the AMAZE then i flash a new custom rom. After multiple tries I got it up. SO its up and the brightness is at its highest point. But I dont believe thats the problem. I just need to figure out how the light stays off when in recovery mood but comes on when booted normally. Its as though the recovery is broken. How do I fix it? if its broken
So I rooted my HTC ONE S (villec2) today, and I wanted to flash a custom rom on it. I got a recovery (turned out to be a bad one, but it worked either way.... I noticed way too late it was made for HTC One M8) I got TWRP 2.7.1.0 and I got it working on my phone. I then backed up the system, and realized I messed up the recovery. In the meantime I got a CM 12.1 img on it and wiped the thing. The wipe removed the old Android system and the CM I downloaded was a bad download. If I go to recovery in the bootloader, it will just do the HTC white screen with "Entering Recovery" and the red warning logo but it won't get anywhere. It's just stuck there. So now, I'm stuck with a device that won't boot normally - just stuck on the white HTC screen, will boot into bootloader, and I want to know if there's a way of accessing the internal storage without being in the operating system. The worst thing is, there's no external SD Card, all just internal... Please god help me. I'm really stressing out about this since it's the only phone I have and if I lose it.... well I'm practically f-ed.... :crying: I know that I messed a few things up really badly and I'm not sure what state the phone is in.
Also just to add, the phone is barely loading up right now. I'm really scared since it's my only phone and it won't even boot normally right now. It's really acting strange, it was on 90% battery but now it might just be dead... i don't know.... someone please help
I honestly think I screwed it up.... All it does now is just a white flash / flicker when I hold the power button (both only power button and vol down) and that's it. I'm really disappointed right now but oh well.... Maybe just because the battery is not charged.... Also been looking around the other threads and looks like a lot of people had the same issue but with 0 replies...
hi friend
i ve bricked a phone once and i recover it with flashing stock rom
did you try the stock rom ?
cazawiman said:
hi friend
i ve bricked a phone once and i recover it with flashing stock rom
did you try the stock rom ?
Click to expand...
Click to collapse
I have no way of trying the stock rom. I cannot access the phone itself because I deleted the OS. There's a weird thing, that if I plug the USB to the computer, it does the connect windows sound but the phone's internal storage is still not accessible.... So as it turns out I can get to the freaking bootloader but then it just turns off with a white flicker a second later.... I have no clue what to do :crying:
try to hook your device with windows and hold the Volume Down and Power
to see if it can detect it
cazawiman said:
try to hook your device with windows and hold the Volume Down and Power
to see if it can detect it
Click to expand...
Click to collapse
Alright. I slept through the night and now I'm here trying to resolve this again. Status now, is that when I try to boot it up, it just shows a white flicker and won't turn on. no matter if i try to boot in bootloader or normally. The device doesn't appear to be charging when I plug it in because it doesn't show the LED light for charging. I think it's hard bricked. I tried other threads, showing bright light to the proximity sensor, but nothing happened.
//edit// - My bootloader was unlocked, and I was on S-ON (HTC ONE S, S3 villec2) that might change on your phone and might make the process different
So I fixed it. I will leave the tutorial for anyone in the future that might be having the same issue. If you "locked yourself out" of your system, eg. no OS, and broken recovery just plug it into the computer, try somehow getting into bootloader, go into fastboot and plug the usb cable to your computer so you're in Fastboot USB. Then you can flash a recovery on the phone using a fastboot command. I believe it's fastboot flash recovery _filename_. Just google that, there'll be plenty. Then you have the recovery and you're back on track. After that you can get the rom you wanted. Just don't make my mistake, and check if your device is exactly the same as the files you're downloading for it. I messed up there . Anyway, good luck everyone!
t
yea
Happy to hear that u have fixed your phone add "solved " to the title and add a fast tutorial for help purpose
Sent from my thl T6 pro using XDA Free mobile app