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?
Hey everyone!
So i'll try to explain my problem. I have an ascend p7-l10. I had flashed lollipop, but ran into some problems so I wanted to revert to B609.
When I tried, I made a few mistakes and I'll sum up the problems I have right now.
-Phone won't connect to pc
-Phone only boots in 'failed to start' mode
-phone doesn't charge in 'failed to start mode', 'bootloader'
-Recovery is broken (only force flash works - it is the stock recovery from B609)
-Battery level is below 15%
I've allready given up hope and went back to my ohh so very slow samsung galaxy i9001, but if anyone can help me in any way. I would be soooooo freaking thankfull!!!!
My best regards to everyone
JulesMarcus1234 said:
Hey everyone!
So i'll try to explain my problem. I have an ascend p7-l10. I had flashed lollipop, but ran into some problems so I wanted to revert to B609.
When I tried, I made a few mistakes and I'll sum up the problems I have right now.
-Phone won't connect to pc
-Phone only boots in 'failed to start' mode
-phone doesn't charge in 'failed to start mode', 'bootloader'
-Recovery is broken (only force flash works - it is the stock recovery from B609)
-Battery level is below 15%
I've allready given up hope and went back to my ohh so very slow samsung galaxy i9001, but if anyone can help me in any way. I would be soooooo freaking thankfull!!!!
My best regards to everyone
Click to expand...
Click to collapse
I had something like this, when I tried to go back to stock 609 after using My-ROM.
Then I had to flash the B121 boot, system, userdata, recovery1, recovery2 (if exist) and cache. Using the VOL- & Power button when phone is connected to the computer.
Now I am stuck on B121, can't upgrade, can't flash custom recovery, can't flash B133, every update.app get a fail result, but at least, it work!
You have to think in emui Version...
Use the transition packet to rollback. Iam online with my phone please use the search.
Look @ my editet Text...
http://forum.xda-developers.com/showthread.php?p=60766165
Well THE biggent probleem is (atleast I think), that my battery is below 15% and won't flash because of that. The phone won't charge anymore either...
Flash the Boot and recovery img of the newest Version (via fastboot) that was okay on your phone (i think b609 was it).
Then charge the phone (dont Start it up, try it to charge complety powered off or try to go into fastboot or recovery mode and charge)....
After that, try my first post.
PS: i flashed @ 8% ...
....results?
I tried what you said but the phone won't connect to a pc in any way. The thing that's confusing me the most is that the phone does start whenever I plug it in to any kind of power source but after that it stays on but, doesn't charge...
Thank you for your help 'till now I really appreciate it!!
Ok, so I've got a little update. I got the phone updating the transition package (first file), atleast partly. I held down volume up+down and connected the usb to my pc. It starts updating but, when it comes to 100% it gives an error: System update failed (again). The pc gives a notification that a device has connected but it just says: usb-device.
I hope that with this information anyone can help me get my phone back to life! or atleast out of it's coma...
Thanks in advance
Edit: it doesn't directly give the error but stays at a 100% 'till I disconnect the phone from the pc and then gives the error
Soo, for the people who are by any chance willing to help me, I have some more information. I think that the force-update isn't working because there is no recovery or a faulty recovery installed. Besides that the fastboot mode is somehow broken and won't connect to my pc in that state. Every time I try force-update it went straight to software update failed, except for the p7L10_isreal_4.4.2_emui2.3_B135. With that rom it went to what I believe is the recovery, but then it said validating updating package. After that it shuts off and went to the force update screen with system update failed...
After 1,5 month of trying everything I finally did it!! Thank you 87insane for the help you have offered me! and I really want to thank tinyXperia for his reaction in the Q&A section (not even my thread) but, his method worked like a charm!!!! Phone is out of it's coma (thankgod). Really weird that I had to flash B800 transition package but it did the job.
Thankfully the thread can be closed.
Hello everyone. Well, as per the title, after I flashed a new custom ROM (Ivan's AOSP to be specific), my Mi3 refused to boot properly and get stuck in the bootloop at the Mi logo and it would bootloop again and again and again....
Now, if I tried to enter twrp recovery by holding power button + volume up, it would refuse to boot into recovery and just bootloop again. But, I was able to access fastboot mode (don't know why but I could easily boot into fastboot mode)
I downloaded stock ROM for Mi3 and tried to flash it via MiFlash and it succeeded but the device would still bootloop. I also attempted to flash twrp recovery via flashboot and it succeeded, again, but my phone would refuse to at least boot into twrp recovery mode, again. Naturally my phone still had the bootloop at the Mi logo, sigh.
I don't know what to do anymore, aside from sending my phone to repair center that might charge a fortune. Please help!
try to flash official twrp recovery via fastboot
Rahuljs said:
try to flash official twrp recovery via fastboot
Click to expand...
Click to collapse
How to flash it ?? Method pls...
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
Not going to send to phone center & currently my ROM can't not boot because of extend partition before & not stock partition... Help me PLEASE !!!
Many users confirmed the same symptoms. Is it possible that the damage caused by "software" since some people of India have visited the service center and asked to replace the motherboard of which cost $150?
Try flashing the phone via MIUI flashing tool as you were able to access fastboot mode
http://en.miui.com/a-234.html
xypherize said:
Hello everyone. Well, as per the title, after I flashed a new custom ROM (Ivan's AOSP to be specific), my Mi3 refused to boot properly and get stuck in the bootloop at the Mi logo and it would bootloop again and again and again....
Now, if I tried to enter twrp recovery by holding power button + volume up, it would refuse to boot into recovery and just bootloop again. But, I was able to access fastboot mode (don't know why but I could easily boot into fastboot mode)
I downloaded stock ROM for Mi3 and tried to flash it via MiFlash and it succeeded but the device would still bootloop. I also attempted to flash twrp recovery via flashboot and it succeeded, again, but my phone would refuse to at least boot into twrp recovery mode, again. Naturally my phone still had the bootloop at the Mi logo, sigh.
I don't know what to do anymore, aside from sending my phone to repair center that might charge a fortune. Please help!
Click to expand...
Click to collapse
Here is the link for tutorial for flashing recovery via fastboot mode. All commands are same just download the twrp recovery image from here. DON'T FORGET TO RENAME THE IMAGE FILE, BECAUSE ADB DOESN'T RECOGNISE ANY SPECIAL CHARACTER.
what did you do ? I'm stuck in the same situation word by word.
did you solve this issue ?
yohaneseko said:
Many users confirmed the same symptoms. Is it possible that the damage caused by "software" since some people of India have visited the service center and asked to replace the motherboard of which cost $150?
Click to expand...
Click to collapse
Seems like the problem is caused either because of this, or your battery's PCB simply fried because of unknown reason, maybe because faulty charger/cable or wrong charge voltage setting by the kernel? Also, seems like most of the similiar case stems from MM roms, including MIUI's own chinese developer ROM.
Some people with the exact same case stated that after replacing the battery, the device worked again, like this guy on iFixit: https://www.ifixit.com/Guide/Xiaomi+Mi+3+Battery+Replacement/50785
I haven't tested it yet on my bricked device (just ordered the battery today), but I really hope it was just the battery. I think fried mobo is kinda unthinkable, since if the mobo got fried, you probably can't even flash anything since the eMMC would probably also inaccessible.
Hi @rxl.noir, urang Bandung?
How much does it cost for battery replacement? I have sent my Mi3 to the seller because it's not even one year already.
rxl.noir said:
Seems like the problem is caused either because of this, or your battery's PCB simply fried because of unknown reason, maybe because faulty charger/cable or wrong charge voltage setting by the kernel? Also, seems like most of the similiar case stems from MM roms, including MIUI's own chinese developer ROM.
Some people with the exact same case stated that after replacing the battery, the device worked again, like this guy on iFixit: https://www.ifixit.com/Guide/Xiaomi+Mi+3+Battery+Replacement/50785
I haven't tested it yet on my bricked device (just ordered the battery today), but I really hope it was just the battery. I think fried mobo is kinda unthinkable, since if the mobo got fried, you probably can't even flash anything since the eMMC would probably also inaccessible.
Click to expand...
Click to collapse
yohaneseko said:
Hi @rxl.noir, urang Bandung?
How much does it cost for battery replacement? I have sent my Mi3 to the seller because it's not even one year already.
Click to expand...
Click to collapse
Heyaa~
For the battery, you could easily found it on Tokopedia started from 110k, although most of them are shipped from Jakarta. The replacement process is quite easy, you might only need #0 Phillips or any small plus screwdriver, a plastic card (for spudge replacement), and some guts :q. The details and steps are on my prev. post.
I haven't tried to sent it to the seller/distributor, since it might take a long time to get it done.
Just a little update;
I replaced my battery on my Mi3 that have the same exact case as yours, and it finally works. No more short bootloop, no more stuck in fastboot.