Database Info

[Q] Stuck on Moto Logo

Hey there,
Was on Dexter's Froyo 1.2b. Phone froze up, had to pull battery.
After pulling the battery, it won't reboot. Just stays on the Moto logo forever.
Will not go into recovery mode, but will go into bootloader.
Tried flashing a few different ROMs onto it with RSD, no luck.
Any thoughts?
Thanks!

Charles Angus said:
Hey there,
Was on Dexter's Froyo 1.2b. Phone froze up, had to pull battery.
After pulling the battery, it won't reboot. Just stays on the Moto logo forever.
Will not go into recovery mode, but will go into bootloader.
Tried flashing a few different ROMs onto it with RSD, no luck.
Any thoughts?
Thanks!
Click to expand...
Click to collapse
try this
remove your sdcard and just leave sim card in our phone and boot..wait for it ..if after 10 minutes moto logo still there..pull out your battery and put it back into phone
press power button , press the Vol + button for 30 seconds as soon as the Moto Logo shows up
if you see the recovery option select the wipe data/ factory reset option and then reboot..

I had exactly the same problem (and a few people too)
sorry...but you can't do anything!
I tried to flash my phone numerous time, and can't get into recovery!
only solution is to send phone to motorola service
PS. this is 100% connected with dexter's froyo...so it would be nice that we collect some info why is this happening on some phones......

pajo985 said:
I had exactly the same problem (and a few people too)
sorry...but you can't do anything!
I tried to flash my phone numerous time, and can't get into recovery!
only solution is to send phone to motorola service
PS. this is 100% connected with dexter's froyo...so it would be nice that we collect some info why is this happening on some phones......
Click to expand...
Click to collapse
Did you end up sending yours out to motorola service? Were they able to fix your phone? I think resar also had a similar problem. http://forum.xda-developers.com/showthread.php?t=821210 (before Dexter's ROM)

It is wrong that there is no way to deal with that problem. I also had it a few weeks ago.
Method 1: http://forum.xda-developers.com/showthread.php?t=892026
Method 2: Get a second battery that is charged up ( at least 40 % or so..) and then get into the bootloader and reflash your custom ROM.
Method 3: Charge up your phone ( do not connect it to PC ) with the wall charger. When the phone wants to boot automatically, pull out the battery and set it in again. When the phone tries again to boot, pull the battery out and set it in again. My XT720 wanted to boot after 5-10 minutes or so when it was charging up. You should do that until your phone has enough battery to get into the bootloader.
In my opinion the problem is that the battery does not charge up anyway?
It worked for me with a second battery that was charged up for 50 % and then I reflashed custom ROM with RSD Lite.
Just ask if you don't understand anything
Did you get into RSD Lite & bootloader mode?

Knoedelkopf said:
It is wrong that there is no way to deal with that problem. I also had it a few weeks ago.
Method 1: http://forum.xda-developers.com/showthread.php?t=892026
Method 2: Get a second battery that is charged ( at least 40 % or so..) and then get into the bootloader and reflash your custom ROM.
Method 3: Charge your phone ( do not connect it to PC ) with the wall charger. When the phone wants to boot automatically, pull out the battery and set it in again. When the phone tries again to boot, pull the battery out and set it in again. My XT720 wanted to boot after 5-10 minutes or so when it was charged up. You should do that until your phone has enough battery to get into the bootloader.
In my opinion the problem is that the phone does not charge anyway?
It worked for me with a second battery that was charged up for 50 % and then I reflashed custom ROM with RSD Lite.
Just keep asking questions if you don't understand anything
Did you get into RSD Lite & bootloader mode?
Click to expand...
Click to collapse
Interesting! So, the idea is that when battery power is too low the flash is either ineffective or perhaps disabled by some low-level hardware check? It does seem plausible. I hope I don't ever have to try this.

battery is not a problem (at least in my case)
I have original milestone which have the same battery as xt, so I always charged battery at 100%...
motorola did repair my phone, but now I am afraid of flashing 2.2 back, because it will surely stuck at M logo again (I tried it two times already )
PS. tried flashing ALL available flashes (even original korean 2.2), and nothing happened..
I just couldn't boot into recovery

So when you got into the bootloader mode, was there shown something like "battery low cannot program"?
Or what do you mean exactly with "I just couldn't boot into recovery "?

Knoedelkopf said:
So when you got into the bootloader mode, was there shown something like "battery low cannot program"?
Or what do you mean exactly with "I just couldn't boot into recovery "?
Click to expand...
Click to collapse
We tried everything we could to save pajo's phone but nothing worked. resar is also extremely knowledgeable and had to send the phone to Motorola for repair. Pajo's thread has been merged into this mega thread, unfortunately:
http://forum.xda-developers.com/showthread.php?t=962744&page=1

Mine bricked today also using Dexter 1.3. This was my replacement phone (other one had audio jack issue, hardware not software). My battery died and couldn't get it to reboot, would just cycle the moto logo then sometime the dex froyo logo. I'm flashing back to stock right now,then reverting ti 1.2b was a more stable build.

[Q] Xperia M2 blocked on boot even after flash

My sony xperia M2 suddenly start blocking on boot. It comes to blue waves animation and it is stuck there.
I used flashtool software to flash new firmware hoping that it will solve the problem, but even after flashing device the problem still occurs.
Please help

TeslaNikola said:
My sony xperia M2 suddenly start blocking on boot. It comes to blue waves animation and it is stuck there.
I used flashtool software to flash new firmware hoping that it will solve the problem, but even after flashing device the problem still occurs.
Please help
Click to expand...
Click to collapse
Best to ask in the Xperia M2 Q&A, Help & Troubleshooting forum.
There you will get quick and proper help.
Good luck !

If it boots to the blue waves that means the Linux kernel is running, but something gets stuck at Java level. As fast attempts you may try to boot the phone without SIM card, or reboot in safe mode (not sure about the key combination, though. I'm a bit new to this phone). The other option is to do an hard reset to factory mode (again, I don't know the boot key combination): Otherwise repair the FW from the PC companion/ Bridge for Mac, I wouldn't use flashtool.

Miche1asso said:
If it boots to the blue waves that means the Linux kernel is running, but something gets stuck at Java level. As fast attempts you may try to boot the phone without SIM card, or reboot in safe mode (not sure about the key combination, though. I'm a bit new to this phone). The other option is to do an hard reset to factory mode (again, I don't know the boot key combination): Otherwise repair the FW from the PC companion/ Bridge for Mac, I wouldn't use flashtool.
Click to expand...
Click to collapse
I've done all of that...I updated software with PC Companion.. I can't get into safe mode, and I did hard reset several time...
But still, same thing is happening, It's still blocked on blue waves animation on boot.

TeslaNikola said:
I've done all of that...I updated software with PC Companion.. I can't get into safe mode, and I did hard reset several time...
But still, same thing is happening, It's still blocked on blue waves animation on boot.
Click to expand...
Click to collapse
Same here i have tried everything you have tried but no luck i hope someome can help !!!! cause i am at a lost....

Unless there is some malfunctioning piece of HW breaking up the boot process I am running out of ideas. After repairing the FW the ROM is like brand new. It should boot. To get more info one would need to run
Code:
adb logcat
From the PC/Mac with the phone connected via USB. But the USB debugging must be enabled. You may give it a try, but I doubt adb would connect.
PS: Wait, unless you guys unlocked the bootloader and restored the wrong TA partition. That would mess up things quite heavily.

Hello, after flashing the ftf it takes a very long term for it too boot up. For me it too about 20mins first time and about 1 hour for one time that I messed up really bad. I just left it on charge. (best charge on pc with adb running) and it should be fine. Also try sticking a pin/paperclip/pen into the hole next to the sim and sd slots. This will force the phone to shut down. Try rebooting. Also while flashing the ftf you need to UNTICK the data and cache (this WILL wipe all your data) AND TICK all the others. This will flash everything else. Also after flashing don't just unplug your phone. Eject it first (no one does that but do it) My current best guess is that. You've installed an app that runs at boot and is poorly written and cause error that stops the phone booting.
Additional to that. The is a chance very slight that one of your files is currupted try doing a md5hash and matching it. Secondly and most likely is that you packaged the ftf wrong if you just downloaded it and popped it inside the flash tools installations folder then it probably won't be this. But if you downloaded with the app, you get to choose what aspect of the ftf to include. So at this stage you might be miss out the kernal or whatever else as you spam next. Try reading my guide if you already haven't. Sorry for the very long post. I hope I helped
Sent from my D2305 using XDA Free mobile app

BlazingBullets said:
Hello, after flashing the ftf it takes a very long term for it too boot up. For me it too about 20mins first time and about 1 hour for one time that I messed up really bad. I just left it on charge. (best charge on pc with adb running) and it should be fine. Also try sticking a pin/paperclip/pen into the hole next to the sim and sd slots. This will force the phone to shut down. Try rebooting. Also while flashing the ftf you need to UNTICK the data and cache (this WILL wipe all your data) AND TICK all the others. This will flash everything else. Also after flashing don't just unplug your phone. Eject it first (no one does that but do it) My current best guess is that. You've installed an app that runs at boot and is poorly written and cause error that stops the phone booting.
Additional to that. The is a chance very slight that one of your files is currupted try doing a md5hash and matching it. Secondly and most likely is that you packaged the ftf wrong if you just downloaded it and popped it inside the flash tools installations folder then it probably won't be this. But if you downloaded with the app, you get to choose what aspect of the ftf to include. So at this stage you might be miss out the kernal or whatever else as you spam next. Try reading my guide if you already haven't. Sorry for the very long post. I hope I helped
Sent from my D2305 using XDA Free mobile app
Click to expand...
Click to collapse
I can see that flashing was successful because icon that shows when phone is turned off and charging has changed. But regardless of new firmware, the problem stays the same. I've left it for hours to boot but nothing.
I also don't think that installing bad application is a reason for this, because I haven't installed anything for days before this happened.

TeslaNikola said:
I can see that flashing was successful because icon that shows when phone is turned off and charging has changed. But regardless of new firmware, the problem stays the same. I've left it for hours to boot but nothing.
I also don't think that installing bad application is a reason for this, because I haven't installed anything for days before this happened.
Click to expand...
Click to collapse
Sorry for the super late reply and your problem is probably fixed by now. The FTF should flash everything. if you have them all ticked (except data and cache, they need to be UNTICKED for it to be flashed). If it doesn't solve your problem then its a bootloader problem and i personally cannot help you. You'll have to call into Sony.

Help with apparently hard-bricked phone?

Tried 3 different versions of Odin, it always fails after boot.img ("complete write operation failed")
My phone model is G920I.
I'm stuck in the exclamation mark screen. Only thing I can do pressing buttons is reach the download screen. Can't access recovery.
Can I flash TWRP through odin and try installing a firmware stored in my ssd? Or that wouldn't even work seeing as I can't get pass the ! blue (green?) screen anyway?
Worst part is, I don't even know how this all started. I got a notification that a new update was released, but my battery was low, the phone died, I left ir charging and it wouldn't turn on the other day. I probably ****ed something up in the recovery screen (it was accessible in the beginning) and now I can only access the !/download screen.
Does anyone have any idea what I can do? Thanks in advance.

rifek4 said:
Charge you battery a bit anyway, to be sure there is minimum 30%. Then flash latest 7.0 firmware correctly for your model via Odin3 with latest drivers: https://forum.xda-developers.com/ga...official-stock-firmware-t3086387/post73935393 here you found all.
Click to expand...
Click to collapse
Made a new thread because my problem seems slightly different and I explain about it. Don't see how it could be prejudicial to the forum but thanks for the hint.
My phone is only on when connected with cable, either to the computer or charger, When I still had access to recovery mode, it said 99% battery. Now I don't even think I can check the battery? All I know is when the phone is not connected, it stays off.
I've tried using a couple of supposedly stock firmware from my model but the error is always the same. Gonna try downloading one from where you linked me to, but do you really thing it could make a difference, considering everything I've said?
Thanks in advance.

Xperia Z5 stuck in bootloop and flashtool cannot recognize it.

Hello guys,
It is my first time yesterday to flash and root my Xperia Z5 since the camera app always says that it is currently in use.
I used this guide by sceryavuz . And it turned out great, I have used my phone for a day without any errors or problems encountered. But the thing is, I still cannot use the camera app and it has the same currently used by other application message so I decided to downgrade it to Marshmallow this morning. So I went to the same routine, downloaded an FTF file and loaded it into the flashtool.
After clicking Flash device in the flashtool and waited for the flashmode, I connected and pressed the volume down button of my phone but the flashtool is not reading and recognizing my phone. So I decided to open the TWRP and assumed that factory resetting my phone will do the work and it turns out that it just removed the /system folder and now I have a bigger problem with my phone.
When I'm connecting in flashmode the LED is turning to red, green, then will turn off, and then will do the same cycle if left unattended.
Could you guys please help me out with this. You'll be greatly appreciated guys. Thanks!
My phone is E6653 Xperia Z5

Well, you should reflash the system, by a custom rom of your choice or even the stock rom if you want to.
I'm using a custom rom and I highly recommend you to do so if you already lost your data, give it a try.
You don't need to downgrade to MM, it not an android version issue, I would recommend you carbon rom. Go to it's thread and figure out how to flash it, if you need help ask over there or quote me back in this thread.
Another option could be restoring your phone with xperia companion but you will need to relock the bootloader and get flashmode to work again. You can also try flashtool from your computer. Anyway I recommend you to do so ONLY and ONLY if you want your phone to run stock again as it was when you bought it.
Otherwise yep, figure out what's a customrom and how to flash it, you find tons of custom roms in xda threads. having already TWRP is an advantage, less sketchy stuff to do.
Hope it helped, as I said, quote me back if you need help
Edit: if you need the files we're running the exact same device, if you don't find em (and only if you can't find em) i could send them to you.

ofmoll said:
Well, you should reflash the system, by a custom rom of your choice or even the stock rom if you want to.
I'm using a custom rom and I highly recommend you to do so if you already lost your data, give it a try.
You don't need to downgrade to MM, it not an android version issue, I would recommend you carbon rom. Go to it's thread and figure out how to flash it, if you need help ask over there or quote me back in this thread.
Another option could be restoring your phone with xperia companion but you will need to relock the bootloader and get flashmode to work again. You can also try flashtool from your computer. Anyway I recommend you to do so ONLY and ONLY if you want your phone to run stock again as it was when you bought it.
Otherwise yep, figure out what's a customrom and how to flash it, you find tons of custom roms in xda threads. having already TWRP is an advantage, less sketchy stuff to do.
Hope it helped, as I said, quote me back if you need help
Edit: if you need the files we're running the exact same device, if you don't find em (and only if you can't find em) i could send them to you.
Click to expand...
Click to collapse
Hi ofmoll,
I'm sorry for the very late response, I had an internet connection issue this past week. I have tried your suggestion by using Carbon Rom, it works perfectly fine but I have one problem. It is not charging and the battery keeps saying that it is on 100% even if it is not. I'm trying to reflash other ROMs and I'll get back to you as soon as I finish flashing. Happy new year! Thanks!

Hi,
I tried to flash my phone a carbon rom and a crdroid rom and it was successful, my problem was it wasn't charging, and whenever I try to use flashtool, and I am entering flashmode, the phone turns red then green then after a minute it turns red again and then green after I press volume down and connect the phone to my PC. And the PC seems cannot recognize my device since no sounds are going off my computer when I connect it. I hope you can share your expertise regarding this.

Toshiiiiiiii said:
Hi,
I tried to flash my phone a carbon rom and a crdroid rom and it was successful, my problem was it wasn't charging, and whenever I try to use flashtool, and I am entering flashmode, the phone turns red then green then after a minute it turns red again and then green after I press volume down and connect the phone to my PC. And the PC seems cannot recognize my device since no sounds are going off my computer when I connect it. I hope you can share your expertise regarding this.
Click to expand...
Click to collapse
So you say it's not charging? Or did you manage to solve that? You don't really need flashtool at this point (unless you want to relock the bootloader, but I guess there are backdoors for that as well)
If it's not charging, well, the options are this: either it's a hardware problem, for example charger or charge port, or a software problem, because some files are needed for the phone to detect a charger source plugged in.
1. If the software is crashing you can try going into TWRP and wipe cache and dalvik cache, may help may not, try. If you get it yo work remember to calibrate the battery after it, it might be important because after flahsing roms and having this kind of issues the battery could not be showing the actual percentage of battery. So just calibrate, it's easy, Google it.
2. It could happen that the phone is charging but the battery status icon won't show it, I'm not too sure about this but I heard that could happen, might not be the case.
3. In none of that works, search, make a lot of research of people with your same problem and try amd try and try, If nothing works a clean reflash should solve it, usually does, if not try another rom, another kernel or go back to stock. It's your choice, but anyway I guess a clean reflash should get it working. I had the same issue with LineageOS and wiping Dalvik Cache solved it.
If you wipe dalvik expect a long reboot time, I don't suggest you to turn the phone off while it boots up. Wiping Dalvik means all cache files have to be built again the next time you reboot your phone, so yeah, expect some battery drain and a hot device while it boots up, but don't panic, it's totally normal.
Happy new year, hope you get it working again
Remember to hit thanks, cheers!

ofmoll said:
So you say it's not charging? Or did you manage to solve that? You don't really need flashtool at this point (unless you want to relock the bootloader, but I guess there are backdoors for that as well)
If it's not charging, well, the options are this: either it's a hardware problem, for example charger or charge port, or a software problem, because some files are needed for the phone to detect a charger source plugged in.
1. If the software is crashing you can try going into TWRP and wipe cache and dalvik cache, may help may not, try. If you get it yo work remember to calibrate the battery after it, it might be important because after flahsing roms and having this kind of issues the battery could not be showing the actual percentage of battery. So just calibrate, it's easy, Google it.
2. It could happen that the phone is charging but the battery status icon won't show it, I'm not too sure about this but I heard that could happen, might not be the case.
3. In none of that works, search, make a lot of research of people with your same problem and try amd try and try, If nothing works a clean reflash should solve it, usually does, if not try another rom, another kernel or go back to stock. It's your choice, but anyway I guess a clean reflash should get it working. I had the same issue with LineageOS and wiping Dalvik Cache solved it.
If you wipe dalvik expect a long reboot time, I don't suggest you to turn the phone off while it boots up. Wiping Dalvik means all cache files have to be built again the next time you reboot your phone, so yeah, expect some battery drain and a hot device while it boots up, but don't panic, it's totally normal.
Happy new year, hope you get it working again
Remember to hit thanks, cheers!
Click to expand...
Click to collapse
Hi Sir,
Happy new year! Thanks for your reply and I really appreciated it. When I connect the phone to my charger when it's off, it turns on then shows the screen of charging 0% by carbon rom then immediately dies after 2 bars being filled. I hope that it is not a hardware problem since when I connect my phone to my computer via the usb, it lights on but the computer can't recognize it. I am suspecting that this is a rom problem with my phone since the phone shows that it's charging connected to AC and 100% even if it is not connected to a charger. I am trying to get the flashmode to work again so I can flash a stock rom to it because the stock rom works perfectly fine but the camera. I will try all your suggestions tomorrow and I'll research harder to solve this. Will post an update once done. Cheers!

Toshiiiiiiii said:
Hi Sir,
Happy new year! Thanks for your reply and I really appreciated it. When I connect the phone to my charger when it's off, it turns on then shows the screen of charging 0% by carbon rom then immediately dies after 2 bars being filled. I hope that it is not a hardware problem since when I connect my phone to my computer via the usb, it lights on but the computer can't recognize it. I am suspecting that this is a rom problem with my phone since the phone shows that it's charging connected to AC and 100% even if it is not connected to a charger. I am trying to get the flashmode to work again so I can flash a stock rom to it because the stock rom works perfectly fine but the camera. I will try all your suggestions tomorrow and I'll research harder to solve this. Will post an update once done. Cheers!
Click to expand...
Click to collapse
As said, first of all try what I said. It nothing of that solves it, I suggest you 3 options
1. Either go stock, try using XPeria Companion, but I think since you flashed custom it doesn't work, at least for me. For Companion you'll need to relock bootloader. Or go stock by flashing a stock rom via TWRP. Note that after flashing a custom rom you'll never go back to the "real" stock if you don't have a backup, but you can always flash a stock rom.
2. You can also try to reflash the rom and see if that works.
3. Download a Custom kernel, then go to TWRP, wipe everything, then first of all flash the Kernel (remember to ensure that's a kernel for your device). Then reflash the ROM. This could look stupid because the ROM comes with a built-in kernel itself, but it solved an issue I had with random reboots. I didn't read this anywhere, I tried and for me it solved a problem I had which everybody was telling me that was caused by hardware, then it came out to be a Kernel issue. Try to if you want.
Try what I said before as well. This is all I know
Cheers
Edit: I forgot to tell you that PC Companion won't recognize your phone if it's running a customROM. Use Android File Transfer instead. You also need to check "use usb to transfer files" on the notifications pannel. Enable USB debugging as well, I guess you know how to do it, in case: you need to go to "about phone" in settings, hit 8 times Build Number, then the developer options should appear and check Android Debugging. That's it.

Question Bricked

Have a XQ-BC62, was working fine until it randomly died, and it won't respond to anything.
I was rebooting into fastboot, and hit the option to reboot to bootloader accidentally but then a red light started blinking when my phone was connected to my laptop.
Soft-reseting doesn't work at all, and the phone doesn't respond to any inputs at all, only a red light when charging. Unplugging turns off the red light, but nothing else happens.
My bootloader is unlocked, I have root with Magisk, and I've tried several different cables and chargers only to get the same red light.
Is there any fix to this?

Hi,
any solutions? am also facing a similar issue. mine is not responding to anything, no led lights, the screen is black, no response on any keypress, no charging indications. it's completely black.
plz do help me out if you know anything that is helpful

I haven't found a direct solution, but I am trying to discharge the battery and see if it could fix something.

Update: Still haven't found a proper fix, tried everything from the 2 minute restart to the old rubber band trick used on older Xperia's. If there is another possible fix, someone let me know, otherwise I'm just going to let the battery die in a drawer for a week and see if that works. If it doesn't, I'll just call Sony.

subiesubiesubie said:
Update: Still haven't found a proper fix, tried everything from the 2 minute restart to the old rubber band trick used on older Xperia's. If there is another possible fix, someone let me know, otherwise I'm just going to let the battery die in a drawer for a week and see if that works. If it doesn't, I'll just call Sony.
Click to expand...
Click to collapse
This exact same issue happened to me, flashing red light no matter what, no response to key presses etc. Taking apart the phone and manually disconnecting the battery did nothing, and I had to send my device in.

subiesubiesubie said:
Have a XQ-BC62, was working fine until it randomly died, and it won't respond to anything.
I was rebooting into fastboot, and hit the option to reboot to bootloader accidentally but then a red light started blinking when my phone was connected to my laptop.
Soft-reseting doesn't work at all, and the phone doesn't respond to any inputs at all, only a red light when charging. Unplugging turns off the red light, but nothing else happens.
My bootloader is unlocked, I have root with Magisk, and I've tried several different cables and chargers only to get the same red light.
Is there any fix to this?
Click to expand...
Click to collapse
Install Xperia Companion, and try the Software Repair tool. It worked for my XQ-BQ72, but my issue was wrong firmware flashed and wouldn't boot up.

Ko2nutJuz said:
Install Xperia Companion, and try the Software Repair tool. It worked for my XQ-BQ72, but my issue was wrong firmware flashed and wouldn't boot up.
Click to expand...
Click to collapse
I have the same problem. I have a XQ-BQ72, and I messed something up while installing firmware via Newflasher. (I tried to go back to Android 11)
Now I'm stuck in the "Your device is corrupted" loop and cannot solve it.
- Xperia Companion just says my device is locked, and will not do anything.
- I tried several times to flash a new firmware using Newflasher, and it runs through fine, but I'm still stuck in the boot loop.
Any ideas what else to try?
Edit:
Okay, after reading deeper in the Newflasher thread, I realized that the error is due to "rollback protection", because I wanted to install a newer version over an older version.
However, I'm still stuck, because even when flashing the newest version of the firmware (61.1.A.7.35), the problem remains.
Or could it be that it is a problem of the region customization? Does it matter which version of the XQ-BQ72 firmware I install?
Edit 2:
So it turns out I had the wrong drivers for fastboot. With that solved I could unlock the bootloader via fastboot and then use Xperia Companion to do a software repair.
And after that I was able to start over, use Newflasher to flash the old Android 11 version, lock the bootloader via fastboot and finally got what I wanted. Puh!