My phone will only charge AC or USB if I do a reboot. If it is up and running it will not charge.. nor will it be recognized by the PC unless I do a reboot... Is there a file that needs to be replaced or setting somewhere? It started a few weeks ago when I flashed back to 1.26, OTA'd to 1.57(started then), then to 1.83.. I then OTA'd to 2.3.4 but it did not take because I had moddified the /System folder with a boot animation...
I am currently on Ninja 4.4 Unlocked and Rooted with Faux OC Kernel...
Any help would be greatly appreciated. Thank you all..
Also CWM will not work on my phone.. try to get into Android recovery and it just sits at "Entering Android Recovery Mode" use Root Manager or ACS Updater to flash ROMS since I cannot get into CWM(Help with that needed too Thanks!
Update... Still won't charge unless I reboot...
I am now able to boot into CWM, but only if I use the CWM installed via ROM Manager.. If I flash Tenfar's I get stuck on the "Entering Android Recovery Mode".. If I use the one in ROM Manager and am plugged in via AC.. I can get into CWM?!?!!? Any ideas on the charging and CWM? Thank you.
I have the same issue as you...only way I can get the phone to charge when its on is to recover from a nandroid backup. I believe a file or kernel is corrupted from when I did the root. I have the amoled version, which do you have?
I finally have my system charging without having to reboot!!!
I had to flash the a full SBF with Pudding from HERE after wiping all data, cache, and dalvik cache. Flashed via RSD Lite.
Still having issues with CWM not wanting to come up. I have been able to get CWM come up plugged into an AC charger using the version loaded by ROM Manager. If I flash any other CWM I get stuck at the Dual Core Screen with "Entering Android Recovery" But i am in recovery if I check via ADB when connected to a PC... I shows my device and shows "recovery" state. So it is getting into recovery. I just don't see the menu on my phone screen.. Any ideas?!?!? Thanks!
i tried to use the recovery and install it but i got stuck in a boot loop. so then i sbfed back to froyo then rooted it then installed the recovery then updated it and got stuck on the "dual core" boot loader. im not sure what im doing wrong. i would post in the thread but i cant since i dont have enough posts
Same exact thing happened to me today. What i did was pull the battery and booted it back up in recovery (power button and down volume button) and did a factory reset. booted it back up and it seemed to work right.
tried that im on my 2nd round of sbf root recovery reflash. of this doesnt work im going to bed i have a 15 hour double shift tomorrow
thanks stx that worked. if anyone can post in the thread that there is a possible bug in flashing this from the p3 preroot it would be cool. it would also be cool if anyone knew how i could sync with facebook too
gnuworldorder said:
i tried to use the recovery and install it but i got stuck in a boot loop. so then i sbfed back to froyo then rooted it then installed the recovery then updated it and got stuck on the "dual core" boot loader. im not sure what im doing wrong. i would post in the thread but i cant since i dont have enough posts
Click to expand...
Click to collapse
Did you wipe data before installing? Also could you confirm the MD5 Hash
917649e16b63d99a7ec30e3c6b6f02b3 Eclipse_v0.4.zip
installed it many times from the prerooted confirms it works fine just make sure you wipe once you get into recovery and my sure you plug your phone into the wall before getting into recovery because it will not boot into recovery and get stuck in motorola logo without being plugged in
after I factory reset it it booted fine.
Sent from my DROID X2 using XDA App
Hey i just PG41IMG-WIFI-light-B10 through the bootloader, at PG41IMG.zip and now its just bootlooping with the htc quietly brilliant logo.
i had s-off/revolutionary and rooted with stock gingerbread.
Im realy worryed guys have i just bricked my tablet? how can't turn it off :S nothig does anything
just got it into recovery through abd, does it recharge in recovery?
reading is fundemental.
You flashed the light version which requries and assumes you would be flashing a rom directly there after. So if you try to just boot after flashing it there is no system to boot into, thus boot loops.
Yes you should be able to charge in recovery and or power off through fastboot and charge
you just need to flash a rom and you will be good to go. Place the rom on your ext sd and enter recovery and let her rip
Just fixed it, have no idea what i did wrong, but just installed leedroids rom after getting into recovery, can someone delete this thread?
mcord11758 said:
reading is fundemental.
You flashed the light version which requries and assumes you would be flashing a rom directly there after. So if you try to just boot after flashing it there is no system to boot into, thus boot loops.
Yes you should be able to charge in recovery and or power off through fastboot and charge
you just need to flash a rom and you will be good to go. Place the rom on your ext sd and enter recovery and let her rip
Click to expand...
Click to collapse
Yeah i did read it all but it would just loop and i couldn't get it into recovery/fastboot wasn't detecting it.
it was stuck with no seeable way to
But adb was detecting it and managed to get it to reboot into recovery, i already had the rom ready on the sd card.
And god that noise it makes when looping could drive you nuts.
And yeah i did read it, read more than id like to admit lol
yes the part about not getting past the splash screen i do nto believe is in the instructions. for future notice if you are stuck in a boot loop you can just hold volume down and power. it will eventually boot into hboot
mcord11758 said:
yes the part about not getting past the splash screen i do nto believe is in the instructions. for future notice if you are stuck in a boot loop you can just hold volume down and power. it will eventually boot into hboot
Click to expand...
Click to collapse
yeah i tried that for ages, that was why i was so worried.
Not having a removeable battery there was no way i could see of getting out of it.
Its more luck than anything that i found the abd command to reload in recovery.
was worried it was that problem where it doesn't recharge. (yes paranoid i know)
But anyway, it all turned out fine
I'm running into a weird boot loop problem with my Atrix 4g. My phone is unlocked and I recently flashed to the Neutrino 2.5p GT update from 2.5 GT. I would usually do a clean install by doing Moto-fastboot -w, erase system/boot/preinstall and then install from the zip but this time all I did was install from the zip. After installing 2.5p GT from the zip, the phone booted up without any issues.
Now my problem started when I flashed the add ons. I re-downloaded and flashed the following add ons:
Live wallpaper add on
Sync add on
Theme Chooser add on
Deskclock/Default CM7 Alarm add on
GPS Mod (Pulled the US.zip file and flashed it, didn't flash "GPS Mod.zip")
Right Aligned Clock Mod
Lite gapps
After flashing the add ons my phone reboots itself before it can get past the Motorola dual core spash screen. The weird thing is now when ever I try to fastboot into my phone using rom racers tool, it says it's waiting to connect to the phone even though it's connected to my computer. I also tried to get into the android recovery but it keep freezing and rebooting after I select the recovery option.
Knowing this, what is the best way to go about getting my phone out of this boot loop? Would this be a job for NvFlash? (I'm unfamiliar with NvFlash, so this is just a guess)
Try to do a factory reset in recovery.
That should fix it
My problem is getting into recovery mode to do a factory reset. Right now my phone freezes and then restarts the boot loop process whenever I choose the recovery option. Are there any alternative ways of getting into recovery mode besides holding the power button + vol down and scrolling down to the recovery option?
I ran into the same problem the other day. I used http://forum.xda-developers.com/showthread.php?t=1314607 to reinstall recovery.
Sent from my MB860 using xda premium
Can you get into Fastboot?
Try:
fastboot -w
fastboot reboot
That worked for me when I was stuck in a boot loop(going to stock)
Yeah. There was a boot problem on 2.5p. The problem was quickly fixed, but now there is a new 2.6 version that blows all previous away.
Sent from my MB860 using XDA
ce12373 is right. The new 2.6 is sweet. You might also try pulling the battery, that seems to help a lot of people.
I would get into fastboot and do a full wipe then reflash from what i have read he suggest in the OP of the rom thread to do a full fastboot wipe
I rolled back from MMROM to NOTTACHTRIX Today and now my phone is stuck in CWM. (Cold Boot Android by selecting Boot Anroid NO BP option doesnt work either).
I have flashed MROM, Neutrino, NOTTACHTRIX, CM10.120120720 and all ended up into clockwork mod recovery. Kindly tell me an alternative -.- I am stuck with this from past 12 hours and no luck.
Update
I have managed to boot into android using Cold Boot without BP (i-e GSM radio will be disabled). I am recharging my phone battery and experimenting.
Before flashing NOTTACHTRIX, my phone had SKT version of 2.3.5 v167. I directly went for unlocking bootloader blabla recovery to get the NOTTACHTRIX working (thats like 4 months ago when I bought this phone)
So I tried going back to a version near 2.3.5 or higher. So going for 141 AT&T version didnt seem a problem for me except the .91 version bricks the device if u downgrade from 2.3.5 or above.
RSD Lite gave me 0x703e error and I couldn't flash the stop sbf.
Second resort I did was flashing 2.3.5 and 2.3.6 fruitcakes and still ended up in recovery.
I can only coldboot into android with Neutrino ROM other roms give me rebootloop when I choose coldboot.
I am suspecting a corrupted system or some kind of corrupt script in boot which keeps me in a loop into recovery. I did try adb script for ASUS TF101 to exit recovery bootloop but to no luck.
Also, I tried exitrecovery.zip flashable and still couldnt get into regular android OS.
This device is a headache for me now -.- and seemingly no one bothers to reply or to help me solve this issue >_>
Thanks for reading atleast
Update 3
Fixed it myself.
I downloaded fastboot, 2.3.6 fruitcake (system and boot), the older clockwork mod recovery, the one comes with Bootloader unlocking not some 5.0 version.
All I did was erased RECOVERY from fastboot, then boot and system. Frasled boot and system. Rooted with the bootloader unlocker package. Installed the old recovery and flashed NOTTACHTRIX.
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
mynonama said:
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
Click to expand...
Click to collapse
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Please help...recovery bootloop
dark_prince said:
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Click to expand...
Click to collapse
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
noobButStudying said:
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
Click to expand...
Click to collapse
did you try the updated and usually standardly used CWM, 5.0.2.6?
palmbeach05 said:
did you try the updated and usually standardly used CWM, 5.0.2.6?
Click to expand...
Click to collapse
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
noobButStudying said:
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
Click to expand...
Click to collapse
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Resolved!
palmbeach05 said:
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Click to expand...
Click to collapse
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
noobButStudying said:
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
Click to expand...
Click to collapse
The RSD issue and not being able to do anything. you are the 4rd person that i've dealt with to have that issue. we had a guy on here a few wks ago that me and andresrivas were trying to help. he wasn't getting the bootloop you were getting, but he had a very similar issue and had the RSD issue. like a wk later, i ended up having the RSD issue as well. Andresrivas also has experienced this issue. All i know is flashing that pudding is what saved us as well.
Idk what ROM you're going to put on there, but i would definitely keep that spare around. if your digitizer dies, you have a backup digitizer