hey guys and gals, hope yall can help me out a bit. im kinda at my wits end. my girls phone (box stock) decided to reboot a few times today at random then stuck itself at lg logo with a blue and green blinking led. (ive recovered a few of my older moto droids) i have read on here quite a bit but am only finding info on rooted devices. i have tried to boot into stock recovery with no luck. i can however get into the firmware update. i have the software tool, vzw drivers, and a copy of the 27a_05.zdk. i read that to clear device you have to use the cme flash method, during the "write to device" icon the device acts like it rejects and sticks a 4% (was stuck there around 1.5 hrs). any and all help will be greatly appreciated.
Related
Alright, 2nd time soft bricking, this time a different way. I think I'm done messing around - if anyone could help me get back to stock I would appreciate that.
I ended up rooting with odin, then got a status 7 error when installing this rom. After (attemping) to reboot, Samsung logo pops up, then t-mobile android logo, the blue bar loads, then nothing. Stuck.
I can still get back into CWM, I have no backups. Where can I download the stock rom? If I could get this working I would be thrilled.
solved:
http://forum.xda-developers.com/showthread.php?t=2135332
I could only find three references to boot loop in the Moto G troubleshooting area...so here I type.
phone is XT1064
Was trying to side load Lollipop. Got to the boot menu no problem...when I selected Recovery the phone rebooted and got stuck on the Moto logo screen "powered by android."
I'm able via external reset get back to the boot menu, but whatever option I choose I end up looping...
Just spent a couple of hours with Moto tech support...painful, avoid if possible. The script pages were turning so fast I thought there were wind gusts in the tech office!
Any ideas would be greatly appreciated.
Littlalex
littlalex said:
I could only find three references to boot loop in the Moto G troubleshooting area...so here I type.
phone is XT1064
Was trying to side load Lollipop. Got to the boot menu no problem...when I selected Recovery the phone rebooted and got stuck on the Moto logo screen "powered by android."
I'm able via external reset get back to the boot menu, but whatever option I choose I end up looping...
Just spent a couple of hours with Moto tech support...painful, avoid if possible. The script pages were turning so fast I thought there were wind gusts in the tech office!
Any ideas would be greatly appreciated.
Littlalex
Click to expand...
Click to collapse
did you have your xt1064 rooted? i have mine rooted in lollipop, i also have the boot loop when starting sometimes, so far you can uninstall root via super user app and solve the problem or have patience untill some good developer fix this problem, to get out of the boot loop i find that connecting to charger the phone does the trick for me, it take like 3 minutes to start, if i uninstall root it starts very fast, im waiting for a solution.
Hi all,
I use CM12 from MacLaw in combination with TWRP 2.8.1.0 recovery for about 3 weeks now.
Yesterday the phone didn't respond properly, was very very slow and I basically couldn't use the phone. It felt like the CPU was at 100% all the time, so unlocking the phone, calling and so was nearly impossible. A reboot (battery removal) didn't solve it, also the pin code for the sim card came after a few minutes while usually this will come right after starting.
So eventually I did a factory reset from the menu as I did on other occasions just to get rid of this kind of problems.
Well, right after the Samsung s3 mini logo I get the TWRP logo and it will be stuck in there, I see it blinking every few seconds and that's it. When I connect the phone to USB I hear it connecting-disconnecting every few seconds (bing-bong, bong-bing sound).
After a while I flashed TWRP using Odin again, this didn't give any problem but it will still hang in this TWRP loop.
I found some references to this problem but no real solutions. Someone suggested to use ADB but I don't know how to do that, nor could I find a suitable guide on this.
Can anyone help me? Or is it bricked somehow?? I suspect not, download mode is still working.
Thanks for any help!
Greetings, I requires assistance with my phone since its bricked and even after many tries, my computer does not read my phone. I can not get into recovery or boot into android, if i try the screen becomes pink and shuts off with a triangle and a red exclamation mark. I have rooted my phone in the past and installed many roms and even went back to a stock rom via RUU's. The problem that I have now is that my computer will not read my phone...whatever I try will not work. I have searched up other posts on different forums but all of them have the option to boot into android.
This all happened 2 days ago when the new update for android started downloading onto my phone and me pressing "Install now" and not "install later" and since then my phone has been bricked .
I would much appreciate your assistance.
Thank you.
McTwist36
Yeah, I softbricked my Moto G... and flashing stock isn't fixing it.
Today my Moto G battery was at 0%, so I started charging it again, after a few minutes the phone booted up, but, after it booted, the phone started shutting down (the same way the phone shuts down when the battery is empty) and the screen turned into black (but the LCD was still on), so I just Power + Vol Down and rebooted to the system...
...however, it didn't work, it starts booting up but never boots...
"Okay then, let's flash another ROM..."
When trying to wipe, TWRP returns "I/O error"...
"Uh... ok, let's try reflashing the stock Marshmallow ROM..."
No errors, but NOTHING CHANGES, after I boot up the ROM isn't even wiped.
So now I'm stuck with a phone that does nothing...
I already tried searching but I didn't find a solution, so... can anyone help me?
Hello MrPowerGamerBR, big fan of your work (Undertale Android port).
Just replying here to say that I've faced the same problem. I plugged in my G2 to charge, still at 0%, and it booted to system but shortly powered off. Now it doesn't boot at all. Error 43 on Device Manager (Windows 10). I've searched it up and it's stupid that this eMMC "problem" was something I could have avoided, should I had known in advance that this resulted in hard bricks.
Three years. Now I'm stuck with no phone. I should have known better to wait to charge it..