Related
So I have a rooted Atrix HD that I tried to restore to stock using the original fastboot files from this thread:
http://forum.xda-developers.com/showthread.php?t=1853522&page=2
I ended up getting error messages with the 1st xml file so I used the modified one in Post #14 of the same thread.
Phone appears to flash properly but gets stuck at AT&T logo and RDS makes me power cycle the phone after an eternity.
When I do and get back into fastboot it says pass and thinks everything is good.
Bad news for me is I'm stuck at the AT&T logo and can't move forward.
I can still get into boot mode selection menu so that appears to be good but I'm at a loss on how to recover this thing into a working phone again.
Anyone have any insight?
Battery life was right around 50% when I started.
Maybe RDS puked since it wasn't at 75%?
Any help would be greatly appreciated.
Make you are using the latest version of RDS 6.1.4 and make sure that your cable is perfect and that your phone is detecting properly.
I think I figured out part of my problem.
Used the modified xml file for 144 with the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file.
RDS lets it flash but never gets past the AT&T logo.
Now if I try to go back and flash with the right file for the modified XML I get 1/24 flash partition "gpt_main0.bin" -> Phone returned FAIL.
I think I might have borked this phone......
windago said:
I think I figured out part of my problem.
Used the modified xml file for 144 with the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file.
RDS lets it flash but never gets past the AT&T logo.
Now if I try to go back and flash with the right file for the modified XML I get 1/24 flash partition "gpt_main0.bin" -> Phone returned FAIL.
I think I might have borked this phone......
Click to expand...
Click to collapse
That fastboot is not for Retail AT&T devices.
Well after booting phone into BP tools to let it charge all night I attempted to reflash this morning with a full battery and a new USB cable using the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file and we're back in and now on 4.1.1.
Time will tell if we're back to normal for good.
What is the BP tools you mentioned? Because I've known that it's imposible to charge the phone while it is stcuked into bootloop or even being in the Bootloader screen.
jics91 said:
What is the BP tools you mentioned? Because I've known that it's imposible to charge the phone while it is stcuked into bootloop or even being in the Bootloader screen.
Click to expand...
Click to collapse
BP Tools is the fifth option available when I boot into the boot mode selection menu by pressing Vol Up/Vol Down + Power.
Boot Mode Selection Menu (10.9B)
Available Boot Modes:
Normal
Recovery
AP Fastboot
Factory
BP Tools
I ended up plugging the phone into my Galaxy S3 wall charger last night and then selecting BP Tools when I entered the Boot Mode Selection Menu.
A simple battery icon appeared telling me I had 9% battery left.
This morning after keeping it plugged in all night I had 100% battery.
As I stated earlier after a full charge I was able to flash using RSD lite and now have a working phone again.
windago said:
BP Tools is the fifth option available when I boot into the boot mode selection menu by pressing Vol Up/Vol Down + Power.
Boot Mode Selection Menu (10.9B)
Available Boot Modes:
Normal
Recovery
AP Fastboot
Factory
BP Tools
I ended up plugging the phone into my Galaxy S3 wall charger last night and then selecting BP Tools when I entered the Boot Mode Selection Menu.
A simple battery icon appeared telling me I had 9% battery left.
This morning after keeping it plugged in all night I had 100% battery.
As I stated earlier after a full charge I was able to flash using RSD lite and now have a working phone again.
Click to expand...
Click to collapse
Congrats. I know exactly how that feels. I was in a similar situation not too many days earlier! It is a little sad that there is very little help online when you get stuck when trying something on this phone. You end up having to figure things out by yourself.
windago said:
Well after booting phone into BP tools to let it charge all night I attempted to reflash this morning with a full battery and a new USB cable using the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file and we're back in and now on 4.1.1.
Time will tell if we're back to normal for good.
Click to expand...
Click to collapse
So flashing this worked for you? I think someone tried this a week or so ago and it bricked their phone.
Sent from my MB886
ReverseZero said:
So flashing this worked for you? I think someone tried this a week or so ago and it bricked their phone.
Sent from my MB886
Click to expand...
Click to collapse
Please no one try that file... it will only work on bootloader-unlocked Atrix HD devices since it is not a build meant for retail AT&T devices.
Makes sense. Don't think I'll be trying that.
Sent from my MB886
As mattlgroff stated:
Please do not flash the file I linked to/reference to in my OP.
He's a developer and has much more insight into the workings of these files then I do.
I'm not sure why mine worked but I defer to his statement about not flashing that particular file.
I was on stock JB. Rooted with new exploit. Installed bootstrap and custom ROM. Wanted to get back to stock, so I uninstalled bootstrap, and flashed MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip.
RSD failed with 'getvar' and 'oem'. I then edited the xml, removed 'getvar' and 'oem', and retried the flash. RSD failed at system.img.
I then booted the phone into fastboot and did the whole thing manually thru fastboot and terminal. This time everything went through okay. I rebooted the phone into stock recovery and erased cache. But now the phone is stuck in bootloop on the red m logo.
What am I missing?
I am having trouble to flash back to stock ICS with RSD lite everytime i use it and connect my phone it says USB connected but that is it. I cannot find the associated file anywhere to flash back to stock any ideas?
Hello guys.
So my cousin's AHD started to reboot all times and can't cross over the "M" logo.
I tried everything, opened stock recovery, wiped data/cache, downloaded stock firmware and flashed with RSD, then flashed manually, step-by-step, but still no luck.
Phone starts, moto logo appears, then it restarts and so on.
Might it be a hardware issue?
For the sake of god, help me guys
Demsee said:
Hello guys.
So my cousin's AHD started to reboot all times and can't cross over the "M" logo.
I tried everything, opened stock recovery, wiped data/cache, downloaded stock firmware and flashed with RSD, then flashed manually, step-by-step, but still no luck.
Phone starts, moto logo appears, then it restarts and so on.
Might it be a hardware issue?
For the sake of god, help me guys
Click to expand...
Click to collapse
When you flash with RSD Lite, does it gives you an error? Have you tried doing it manually with fastboot?
mauchito said:
When you flash with RSD Lite, does it gives you an error? Have you tried doing it manually with fastboot?
Click to expand...
Click to collapse
not a single error dude, everything goes OK. i tried with manual method as well, but still no go.
any1?
I cant tjink of anything other then asking what rom version you are using
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
Well, you could try "fastboot -w" (a factory reset via fastboot) to see if the problem is related to the internal SD or userdata. That's a common issue we were having when CM10.2 sucked and users were swapping between stock roms and custom 4.2+ roms (the sd card is stored differently from 4.1 to 4.2+). It was a cause of some of my bootloops.
I noticed you metioned using stock recovery....is your bootloader locked? If yes then only use the fastboot zip of your last stock rom and nothing else. Even with an unlocked bootloader we can't downgrade gpt_main0.bin (the first thing fastboot flashes) so stick with your stock rom just in case this is a hardware issue....cause it would seriously suck to be voided for warranty because they detected the wrong partition table, and they will detect that because an RSD flash is the first thing they'll do.
If you could, post some screenshots of you flashing crap with RSD and from the terminal. Most of the time those screenshots help us more than what's actually posted in text. If you're unlocked with CWM and ADB up and running, then after a loop access CWM and do "adb shell cat /proc/last_kmsg > C:\last_kmsg.txt" and post the last_kmsg.txt here. That'll tell us if this is a kernel error or not.
skeevydude said:
Well, you could try "fastboot -w" (a factory reset via fastboot) to see if the problem is related to the internal SD or userdata. That's a common issue we were having when CM10.2 sucked and users were swapping between stock roms and custom 4.2+ roms (the sd card is stored differently from 4.1 to 4.2+). It was a cause of some of my bootloops.
I noticed you metioned using stock recovery....is your bootloader locked? If yes then only use the fastboot zip of your last stock rom and nothing else. Even with an unlocked bootloader we can't downgrade gpt_main0.bin (the first thing fastboot flashes) so stick with your stock rom just in case this is a hardware issue....cause it would seriously suck to be voided for warranty because they detected the wrong partition table, and they will detect that because an RSD flash is the first thing they'll do.
If you could, post some screenshots of you flashing crap with RSD and from the terminal. Most of the time those screenshots help us more than what's actually posted in text. If you're unlocked with CWM and ADB up and running, then after a loop access CWM and do "adb shell cat /proc/last_kmsg > C:\last_kmsg.txt" and post the last_kmsg.txt here. That'll tell us if this is a kernel error or not.
Click to expand...
Click to collapse
thanks mate for respond.
first of all, BL is locked and i know about RSD and all that crap things. There is latest stock JB installed on this phone, i also tried fastboot -w command, but it makes nothing, still boot loop.
I haven't CWM, because of locked BL.
I saw video on youtube, how to fix boot loop. Guy in that video, removed battery, gave it on external direct charge and fixed phone. If necessary, i'll post the link. I just wanna know, if it's hardware or software issue. Thanks in advance
Demsee said:
thanks mate for respond.
first of all, BL is locked and i know about RSD and all that crap things. There is latest stock JB installed on this phone, i also tried fastboot -w command, but it makes nothing, still boot loop.
I haven't CWM, because of locked BL.
I saw video on youtube, how to fix boot loop. Guy in that video, removed battery, gave it on external direct charge and fixed phone. If necessary, i'll post the link. I just wanna know, if it's hardware or software issue. Thanks in advance
Click to expand...
Click to collapse
Probably a software issue. For some reason these phones can be very finicky.
In that video I'd assume that guy used a Moto Factory cable...that's the only think I can think of that will allow us to do that. The Factory cable is able to power the board directly from USB and is a good tool to keep around (I actually need to get one myself).
When you say "latest stock JB" do you mean "latest stock AT&T JB or Bell JB or Mex Retail JB". It matters. If your last stock was AT&T and you flash Mex Retail system, dev_tree, & boot.img then it won't work (gpt_main0.bin will detect the different partition md5 and halt the boot). If you can manually flash gpt_main0.bin from AT&T JB then your last stock was AT&T JB, if not then use the Bell JB fxz, if still not then use Mex Retail fxz. (snap-fastboot flash partition gpt_main0.bin....snap-fastboot is what I renamed our custom fastboot executable to).
skeevydude said:
Probably a software issue. For some reason these phones can be very finicky.
In that video I'd assume that guy used a Moto Factory cable...that's the only think I can think of that will allow us to do that. The Factory cable is able to power the board directly from USB and is a good tool to keep around (I actually need to get one myself).
When you say "latest stock JB" do you mean "latest stock AT&T JB or Bell JB or Mex Retail JB". It matters. If your last stock was AT&T and you flash Mex Retail system, dev_tree, & boot.img then it won't work (gpt_main0.bin will detect the different partition md5 and halt the boot). If you can manually flash gpt_main0.bin from AT&T JB then your last stock was AT&T JB, if not then use the Bell JB fxz, if still not then use Mex Retail fxz. (snap-fastboot flash partition gpt_main0.bin....snap-fastboot is what I renamed our custom fastboot executable to).
Click to expand...
Click to collapse
Of course i mean AT&T stock JB. I didn't flash anything, except at&t stock firmware.
this is link, to that fix http://www.youtube.com/watch?v=5QgavcY0OAg
One more thing guys.
When i try to flash with RSD, it can't be finished, because of loop.
there is 23 step for flashing.
It writes system, writes boot, writes everything, than it erases cache and reboots, but stucks in boot loop.
Result is "In Progress", if i look on RSD.
Suddenly phone came back to life, idk why.
but now i'm afraid to unlock bootloader, coz i'm not sure, if it comes back to life after reboot.
what should i do?
Demsee said:
Suddenly phone came back to life, idk why.
but now i'm afraid to unlock bootloader, coz i'm not sure, if it comes back to life after reboot.
what should i do?
Click to expand...
Click to collapse
Maybe use it as is for a while to make sure it is functioning properly. It could be a hardware problem, no?
audit13 said:
Maybe use it as is for a while to make sure it is functioning properly. It could be a hardware problem, no?
Click to expand...
Click to collapse
i really don't know, but suddenly it came back to life, than i rooted, installed CWM, unlocked bootloader and phone works like a charm. i have no words to say, it fixed itself, but maybe some day it will loop again. just dont know
Demsee said:
i really don't know, but suddenly it came back to life, than i rooted, installed CWM, unlocked bootloader and phone works like a charm. i have no words to say, it fixed itself, but maybe some day it will loop again. just dont know
Click to expand...
Click to collapse
The fact that you were able to do all of that is awesome. Let's hope the phone lasts for a while and enjoy:fingers-crossed:
audit13 said:
The fact that you were able to do all of that is awesome. Let's hope the phone lasts for a while and enjoy:fingers-crossed:
Click to expand...
Click to collapse
thanks mate ^_^
seems like it's fixed, i restarted about 20-25times and loop has gone
installed holoblur and enjoying this phone.
thank you all for respond
Very noobish issue. Rooted, unlocked bootloader on Atrix HD. Set up SafeStrap as recovery. Everything checked and working. After letting SafeStrap install Cyan 10.3 and rebooting, phone entered CyanogenMod boot screen and become stuck for an hour. Realized that I forgot to reset and wipe all stock settings and cache (yes, I know that should have been obvious step). Figured I could just go into SafeStrap and make the quick fix.
Seems that I'm unable to enter my custom recovery, instead I'm lead to the familiar bricked android stock recovery. No options to access stock rom (assuming it was deleted during install or lost, etc). Tried installing a different recovery, but fastboot on PC is unable to find device. Help at this point is very much appreciated, either to do any of the following:
1. Somehow access SafeStrap again (assuming that it wasn't wiped aswell) so I can clear stock settings and cache, get Cyan 10.3 going properly.
2. Instructions/links to another method to otherwise forcibly delete stock settings and cache (please keep in mind, fastboot is currently unable to find device).
3. Otherwise completely clear phone of EVERYTHING, then reinstal stock recovery and or/stock ROM so I can give up on flashing custom and stick with stock.
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Update Motorola drivers on your computer and check threads for fastboot files from skeevydude.
Sent from my MB886 using XDA Premium 4 mobile app
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
http://forum.xda-developers.com/showthread.php?t=2226527
Sent from my MB886 using XDA Premium 4 mobile app
SkunkID said:
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Click to expand...
Click to collapse
The error is from using the wrong fastboot executable. Look at post 5. If you get a stickybit error, search our general forums for "stickybit" and you'll find that fix.
deeje00 said:
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
With a bit of creativitity one could use SSR to dual boot Holo Blur and Batakang....or two custom 4.3's that use the same kernel....PAC + Carbon both with arrrghhh's kernel.....Only problem is ya can't be a noob at all if ya do it.
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
When you're at the "dead Android" screen pressing Vol Down + Power pushes it into recovery, iirc - might seem random but there's a purpose behind it.
SkunkID said:
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
Click to expand...
Click to collapse
Hi, I am having the same issue you had... how the heck were you able to get back into stock recovery? Every time I try my phone just reboots and gets stuck again. I cant even turn off my phone with out it rebooting. I have read your posts and followed that other forum you mentioned but if I cannot boot into recovery and if my computer cant see my phone it wont work. Please help when you get a chance.
C6603 Stuck in bootloop! [Last update: 24/1/14]
UPDATE 24/01/14
This issue has been SOLVED.
I replaced the battery with one from eBay and the phone is working flawlessly, all the ROM flashing I went through was not the problem at all. Remember that if you are going to try to replace the battery you may as well buy a new rear glass piece as it is almost guaranteed that the glass will break in the removal process. You will also require new a adhesive piece. The entire procedure cost me $51AUD (battery, glass, adhesive).
All the content below is irrelevant, if your phone randomly shuts off (instantaneously) on boot or soon after, try to replace your battery!
Thanks for your help.
I've got quite a story to tell and if you have the patience to read it, I will greatly appreciate your assistance. TL;DR BELOW
In the beginning I was running 4.2.2, on a stock Australian 10.3.A.0.423 Unbranded ftf. It had been working flawlessly for a month or so until quite recently. It had developed a problem where it would only remain switched on whilst being plugged into the wall socket. As soon as (or thereafter) I removed the plug out of the phone, with one touch, one action, BAM! The display was off and I had to restart the phone again. I spent a few hours browsing for solutions to this problem, most of them said to hold the power and vol+ buttons until the handset vibrated 3 times. That turned it off alright, but I'm looking to go in the other direction.
After a stressful while scrounging old forum posts, I came to the conclusion that the fault is in my ROM, after all, I had flashed from 4.1.2 (I think) to 4.2.2 just a month prior (I flashed a ROM instead of waiting until the snail-like carriers here in Australia decided to dribble out the release). So now being convinced that I ROM is at fault I browse XDA for a newer stock one. Hey! Look! 4.3 it being rolled out in Aust, I check whether it's available to me yet, and obviously, no, it is not. I stumble upon this thread in my travels. I spend a while working to meet it's requirements. Get flashtool, get unlocked bootloader, get root, install cwm, and attempt to install XzDualRecovery 2.6. I've placed the XDR.zip on the sdcard in the XZ, I run the zip using CWM, it seems successful, I then go to reboot and check whether my 4.3 works, after I select reboot I'm asked whether I wish to root the phone. Why yes! that seems easy enough, and just as I select 'ok' the screen goes blank. The bloody phone has switched off in the middle of my work! I try to boot and it hangs on the Sony logo then reboots, creating a cycle. I decide to plug it back in to the wall socket (as this is the only way to get it to boot and remain on), huzzah, it runs. But the root had failed. The rest of my rant is insignificant until now (around 7 hours of failed attempts later)
So in an attempt to keep this wall of text down, I try my best to summarize, If I am not clear enough, just say.
I tried reflashing my old 4.2.2 ROM back, this makes the whole thing worse, now the phone won't even get past the Sony logo (even when plugged to a socket), I flash a different 4.3 ftf, nothing, I restore with PCC, I restore with SUS, I create a ftf from the SUS files and attempt to flash that. Nothing, nothing works. So where am I at now?
The phone still has battery, although, I'm not sure how much, I can no longer get it to charge as it hangs on the Sony logo. The phone should be flashed with 10.3.A.0.423, but when I check the baseband version in Fastboot cmd prompt, it still says 10.4.B.0.569, I feel as though flashtool isn't flashing properly, but I've read that this is usually a non-issue. I can boot into flashmode and fastboot mode. I can unlock and lock the bootloader. I can use ADB and Fastboot CMD (Minimal version) to read values and run commands. Actually, I managed to use the phone in fastboot mode, in conjunction with ADB and Fastboot CMD, I ran the command "fastboot continue" and the phone went on to charge off the usb power, It didn't seem to charge very fast, or at all, and I haven't been able to get it to do it again. So a TL;DR:
-C6603 stuck in bootloop.
-Possibly has a 4.2.2 ROM installed (10.3.A.0.423 Unbranded AU)
-Cannot Charge
-Can run flashmode and fastboot mode
-Can use ADB and Fastboot
-Can use SUS, PCC, and Flashtool to flash stock roms
-Can't figure this out for the life of me!
UPDATE 01/01/14
Currently I have a kernel installed that allows me to use cwm twrp (doomkernel v19, maybe), I have flashed a 'flashable' stock 4.3 rom using cwm and the phone didn't manage to get past the kernel logo. HOWEVER, using fastboot mode, I run the command "fastboot continue", and if I allow the phone to go past the kernel logo it vibrates, the LED turns green as opposed to showing a purple one, and it will begin charging (The LED isn't green as a result of the battery level). EDIT [1/1/14 3:01AM]: I tried to launch the phone whilst it was charging, the charging symbol went away and the phone remained on a black screen (lcd is on, but nothing is displayed) for a few seconds before shutting off automatically.
I must mention, I cannot get into recovery unless I boot the phone into fastboot mode, run the command in fastboot: "fastboot continue". If I don't do this, it simply crashes (shuts off) when showing the kernel logo.
If you need to know more I will provide as much information as I can, as succinct as I can, as fast as I can. I am in this for the long run. Thank you for your time,
UPDATE 08/01/14
I've come to the conclusion that my issue is battery related. After repeated from flashes and fastboot attempts, I managed to get the phone charging a few times, I witnessed the level was sporadic upon infrequent viewings. I have come across a few other very similar threads and feel that it is necessary to try replacing the battery, I try and post a youtube clip that details what happens currently.
Keringkien
keringkien said:
C6603 Stuck in bootloop!
I've got quite a story to tell and if you have the patience to read it, I will greatly appreciate your assistance. TL;DR BELOW
In the beginning I was running 4.2.2, on a stock Australian 10.3.A.0.423 Unbranded ftf. It had been working flawlessly for a month or so until quite recently. It had developed a problem where it would only remain switched on whilst being plugged into the wall socket. As soon as (or thereafter) I removed the plug out of the phone, with one touch, one action, BAM! The display was off and I had to restart the phone again. I spent a few hours browsing for solutions to this problem, most of them said to hold the power and vol+ buttons until the handset vibrated 3 times. That turned it off alright, but I'm looking to go in the other direction.
After a stressful while scrounging old forum posts, I came to the conclusion that the fault is in my ROM, after all, I had flashed from 4.1.2 (I think) to 4.2.2 just a month prior (I flashed a ROM instead of waiting until the snail-like carriers here in Australia decided to dribble out the release). So now being convinced that I ROM is at fault I browse XDA for a newer stock one. Hey! Look! 4.3 it being rolled out in Aust, I check whether it's available to me yet, and obviously, no, it is not. I stumble upon this thread in my travels. I spend a while working to meet it's requirements. Get flashtool, get unlocked bootloader, get root, install cwm, and attempt to install XzDualRecovery 2.6. I've placed the XDR.zip on the sdcard in the XZ, I run the zip using CWM, it seems successful, I then go to reboot and check whether my 4.3 works, after I select reboot I'm asked whether I wish to root the phone. Why yes! that seems easy enough, and just as I select 'ok' the screen goes blank. The bloody phone has switched off in the middle of my work! I try to boot and it hangs on the Sony logo then reboots, creating a cycle. I decide to plug it back in to the wall socket (as this is the only way to get it to boot and remain on), huzzah, it runs. But the root had failed. The rest of my rant is insignificant until now (around 7 hours of failed attempts later)
So in an attempt to keep this wall of text down, I try my best to summarize, If I am not clear enough, just say.
I tried reflashing my old 4.2.2 ROM back, this makes the whole thing worse, now the phone won't even get past the Sony logo (even when plugged to a socket), I flash a different 4.3 ftf, nothing, I restore with PCC, I restore with SUS, I create a ftf from the SUS files and attempt to flash that. Nothing, nothing works. So where am I at now?
The phone still has battery, although, I'm not sure how much, I can no longer get it to charge as it hangs on the Sony logo. The phone should be flashed with 10.3.A.0.423, but when I check the baseband version in Fastboot cmd prompt, it still says 10.4.B.0.569, I feel as though flashtool isn't flashing properly, but I've read that this is usually a non-issue. I can boot into flashmode and fastboot mode. I can unlock and lock the bootloader. I can use ADB and Fastboot CMD (Minimal version) to read values and run commands. Actually, I managed to use the phone in fastboot mode, in conjunction with ADB and Fastboot CMD, I ran the command "fastboot continue" and the phone went on to charge off the usb power, It didn't seem to charge very fast, or at all, and I haven't been able to get it to do it again. So a TL;DR:
-C6603 stuck in bootloop.
-Possibly has a 4.2.2 ROM installed (10.3.A.0.423 Unbranded AU)
-Cannot Charge
-Can run flashmode and fastboot mode
-Can use ADB and Fastboot
-Can use SUS, PCC, and Flashtool to flash stock roms
-Can't figure this out for the life of me!
If you need to know more I will provide as much information as I can, as succinct as I can, as fast as I can. I am in this for the long run. Thank you for your time,
Keringkien
Click to expand...
Click to collapse
download any FTF , 4.2.2 or 4.3 , connect your device to flash tool as flashmode , and select to flash the ftf , when you are selecting the ftf in the flash tool , at the right side check all at the wipe section , and uncheck all at the exclude section
but your internal storage might get also wiped , but i assume it already happened when you unlocked your boot loader
elias234 said:
download any FTF , 4.2.2 or 4.3 , connect your device to flash tool as flashmode , and select to flash the ftf , when you are selecting the ftf in the flash tool , at the right side check all at the wipe section , and uncheck all at the exclude section
but your internal storage might get also wiped , but i assume it already happened when you unlocked your boot loader
Click to expand...
Click to collapse
Alrighty then, I'll give that a go later. I have just found a 4.3 for Australia, perhaps it will be different. Thanks for the quick reply.
keringkien said:
Alrighty then, I'll give that a go later. I have just found a 4.3 for Australia, perhaps it will be different. Thanks for the quick reply.
Click to expand...
Click to collapse
this thread could be helpful : http://forum.xda-developers.com/showthread.php?t=2229250
i'm not sure if that problem could be solve, but it was, like you said, different. never saw anything like that either.
Anyway:
Can it boot into custom recovery in its state now?( for mounting storage for something else in case you have cwm or twrp installed)
Jambu95 said:
this thread could be helpful : http://forum.xda-developers.com/showthread.php?t=2229250
i'm not sure if that problem could be solve, but it was, like you said, different. never saw anything like that either.
Anyway:
Can it boot into custom recovery in its state now?( for mounting storage for something else in case you have cwm or twrp installed)
Click to expand...
Click to collapse
Thanks so much for the reply. The thread has something I can try, if this new rom fails (I expect it will). What is custom recovery? I cannot access the storage, only fastboot and flashmode. no cwm and xdr was never completed.
ROM just failed, trying SUS now.
keringkien said:
Thanks so much for the reply. The thread has something I can try, if this new rom fails (I expect it will). What is custom recovery? I cannot access the storage, only fastboot and flashmode. no cwm and xdr was never completed.
ROM just failed, trying SUS now.
Click to expand...
Click to collapse
oh dear, custom recovery is cwm (clockworkmod recovery) or twrp (team win recovery project), it means, it allows you to do something important just before it boot into system, which is bootstall or bootloop as you call it. you cannot boot into system, then try to boot into recovery ( which is before it boot the system), that might help.
both recoveries will allow you to mount storage to copy things to sd cards from pc.
you can try unlock bootloader and flash custom kernel with recoveries, maybe you "could" boot into one of those recoveries.
I also got the same problem, but mine is a C6602. I was trying to setup a mail exchange, then it asked for some permission. I push enter, then after an hour, it start the bootloop.
The phone boot till the main screen, i could swipe and play around for 10 second, then it reboot.
I have tried everything from hard reset, to FlashTool to SUS, relock, unlock, flash stock, from old stock to new stock, it just won't work :|
Jambu95 said:
oh dear, custom recovery is cwm (clockworkmod recovery) or twrp (team win recovery project), it means, it allows you to do something important just before it boot into system, which is bootstall or bootloop as you call it. you cannot boot into system, then try to boot into recovery ( which is before it boot the system), that might help.
both recoveries will allow you to mount storage to copy things to sd cards from pc.
you can try unlock bootloader and flash custom kernel with recoveries, maybe you "could" boot into one of those recoveries.
Click to expand...
Click to collapse
I'm well aware what cwm is, I just assumed that because you said 'custom' that it might possibly be different, as recovery is always custom anyway, sorry for the misunderstanding.
I am able to flash a 'boot.img' that enables me to use cwm and twrp, HOWEVER, the only way I can access it (as in cause the phone to remain on long enough for it to parse the boot.img) is to connect the phone to my computer in fastboot mode, then using the Fastboot command: "fastboot continue", it will run the 'img' and allow me to enter twrp or cwm. It still won't begin charging or even show the Xperia logo if I allow it to continue without accessing the recovery options.
Thanks for your help.
keringkien said:
I'm well aware what cwm is, I just assumed that because you said 'custom' that it might possibly be different, as recovery is always custom anyway, sorry for the misunderstanding.
I am able to flash a 'boot.img' that enables me to use cwm and twrp, HOWEVER, the only way I can access it (as in cause the phone to remain on long enough for it to parse the boot.img) is to connect the phone to my computer in fastboot mode, then using the Fastboot command: "fastboot continue", it will run the 'img' and allow me to enter twrp or cwm. It still won't begin charging or even show the Xperia logo if I allow it to continue without accessing the recovery options.
Thanks for your help.
Click to expand...
Click to collapse
if you can mount the storage, you could copy the flashable stock rom (4.3) and copy it into your sd card, and maybe you can flash through there by following instructions from that thread.
---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------
billhainh said:
I also got the same problem, but mine is a C6602. I was trying to setup a mail exchange, then it asked for some permission. I push enter, then after an hour, it start the bootloop.
The phone boot till the main screen, i could swipe and play around for 10 second, then it reboot.
I have tried everything from hard reset, to FlashTool to SUS, relock, unlock, flash stock, from old stock to new stock, it just won't work :|
Click to expand...
Click to collapse
look for the disaster recovery thread i posted above
Jambu95 said:
if you can mount the storage, you could copy the flashable stock rom (4.3) and copy it into your sd card, and maybe you can flash through there by following instructions from that thread.
---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------
Click to expand...
Click to collapse
I tried to mount the storage, my pc wouldn't detect the phones storage, I managed to push the stock rom zip to the sd card using ADB. I still had cwm recovery and could flash the zip using it. Still, however, the phone shuts down before it gets past the kernel logo. Again, I used the phone in Fastboot mode and forced it to continue using "fastboot continue", I left it go past the kernel logo and it is charging at the moment. I may try to start the phone now, yet expect it to crash again.
EDIT: I tried to launch the phone whilst it was charging, the charging symbol went away and the phone remained on a black screen (lcd is on, but nothing is displayed) for a few seconds before shutting off automatically.
EDIT: Happy New Year!
Thank you.
keringkien said:
I tried to mount the storage, my pc wouldn't detect the phones storage, I managed to push the stock rom zip to the sd card using ADB. I still had cwm recovery and could flash the zip using it. Still, however, the phone shuts down before it gets past the kernel logo. Again, I used the phone in Fastboot mode and forced it to continue using "fastboot continue", I left it go past the kernel logo and it is charging at the moment. I may try to start the phone now, yet expect it to crash again.
EDIT: I tried to launch the phone whilst it was charging, the charging symbol went away and the phone remained on a black screen (lcd is on, but nothing is displayed) for a few seconds before shutting off automatically.
EDIT: Happy New Year!
Thank you.
Click to expand...
Click to collapse
this problem occurs with every kernel you've used (including stock and custom kernels)?
Jambu95 said:
this problem occurs with every kernel you've used (including stock and custom kernels)?
Click to expand...
Click to collapse
Yes that is correct, it's current issue (turning off sponanteously) occurred when I was running stock 4.2.2 (no root, no bootloader unlock).
keringkien said:
Yes that is correct, it's current issue (turning off sponanteously) occurred when I was running stock 4.2.2 (no root, no bootloader unlock).
Click to expand...
Click to collapse
lol, you should unlock the bootloader before you flash a custom boot.img. the primary solution now is to flash any rom to see if it boots up normally , then you can still find a way to revert back to stock.
Jambu95 said:
lol, you should unlock the bootloader before you flash a custom boot.img. the primary solution now is to flash any rom to see if it boots up normally , then you can still find a way to revert back to stock.
Click to expand...
Click to collapse
I never said that I flashed a custom boot.img whilst on a locked bootloader. The reason I tried all the things that I have is because the phone was spontaneously shutting down (on stock, unedited). Perhaps once I made the mistake of flashing a boot.img before unlocking, but I have since unlocked and flashed many roms and kernels. Thanks for your reply.
keringkien said:
I never said that I flashed a custom boot.img whilst on a locked bootloader. The reason I tried all the things that I have is because the phone was spontaneously shutting down (on stock, unedited). Perhaps once I made the mistake of flashing a boot.img before unlocking, but I have since unlocked and flashed many roms and kernels. Thanks for your reply.
Click to expand...
Click to collapse
the device can't get pass the sony logo?
edNHour consum
Jambu95 said:
the device can't get pass the sony logo?
Click to expand...
Click to collapse
That is correct, it doesn't hang but suddenly turns off, the only way I can use recovery tools in the kernel is if I plug the phone into my pc in Fastboot mode, then issue the command "fastboot continue" from cmd.
keringkien said:
That is correct, it doesn't hang but suddenly turns off, the only way I can use recovery tools in the kernel is if I plug the phone into my pc in Fastboot mode, then issue the command "fastboot continue" from cmd.
Click to expand...
Click to collapse
i think there is something wrong with your motherboard or the battery connection, i'm not sure, because my pc got that problem before, it just boot up to starting windows... and then reboot, in the end i found out the capacitor got swelled in the power supply.
Jambu95 said:
i think there is something wrong with your motherboard or the battery connection, i'm not sure, because my pc got that problem before, it just boot up to starting windows... and then reboot, in the end i found out the capacitor got swelled in the power supply.
Click to expand...
Click to collapse
That is certainly possible, I have had to replace the back glass and during that operation it is possible that the battery got too hot and is now lower in voltage or something. Thanks for the suggestion, I would appreciate a second opinion with this...
Thank you.
keringkien said:
That is certainly possible, I have had to replace the back glass and during that operation it is possible that the battery got too hot and is now lower in voltage or something. Thanks for the suggestion, I would appreciate a second opinion with this...
Thank you.
Click to expand...
Click to collapse
if you still have your warranty, you can go to the center and request for a replacement, the best solution now is to revert to as stock as possible, if can get the bootloader locked again then it's good,
Jambu95 said:
if you still have your warranty, you can go to the center and request for a replacement, the best solution now is to revert to as stock as possible, if can get the bootloader locked again then it's good,
Click to expand...
Click to collapse
I imagine it is still under warranty, however I have read that unlocking the bootloader permanently voids warranty. And I have replaced the back of my white phone with a black glass, perhaps if I get a new white rear glass it will be ok, but then I might as well just replace the battery $40AUD isn't too expensive IMO.
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
mediaman123 said:
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
Click to expand...
Click to collapse
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
jeromechrome1 said:
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
Click to expand...
Click to collapse
Please! Anyone!
by manually do you mean flashing all the separate parts of the stock image separately, system, boot, recovery, cache and so on..........
I don't know what else to do after going through with that process.....
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
I'm a total newb here so take what I tell you with a grain of salt. I had your exact same problem on my Nexus 5. Every single thing you just described is what happened to my N5. And just like your N6...I was able to boot up into recovery (stock and TWRP), I was able to flash all the things manually and even used Wug's NRT. But then whenever I tried to actually boot up the device it could never pass the Google logo....basically EVERYTHING THAT IS HAPPENING TO YOU.
What I did to fix everything? Changed my battery. Sounds stupid and totally irrelevant but that did the trick. When I opened up my phone I noticed my battery had a nasty bulge and realized it was defective. Bought a new one for $25 and have never had any issues ever since. I suggest you look at your battery and see if that is the root of your problem. I have heard of the N6 having some batteries expanding and causing the back covers to pop off...this could be related to your problem.
Like I said I am a newb and thought I'd share my experience in the hopes it solves your problem.
Good luck buddy! :good:
my N6 is actually away getting repaired for the exact issue you described, expanding battery [assumed], and cover coming away from the bezel.....
I believe though that if you keep the device plugged into the wall when trying to boot up with this battery defect it will get through the boot, at least in the beginning anyway....
I believe also that if it was a battery issue the device would power off first, as opposed to just sticking on the Google logo.........
ldkud50 said:
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
Click to expand...
Click to collapse
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
jeromechrome1 said:
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
Click to expand...
Click to collapse
Thats too bad. Maybe the device is hosed. RMA for a new one.
Same thing happened to me. As soon as I updated to the newest version of fastboot on my computer, everything worked...
jeromechrome1 said:
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
Click to expand...
Click to collapse
I know, it's been a long time, but coud you tell me what happened to the phone?