Woke up yesterday morning and my phone was acting all weird. Couldn't unlock the phone from Moto Display (swiping to unlock from the black screen with the clock on it). So I decided to hard reboot it (held down the power and volume down button for about 10 seconds). At that point, the phone got to the Motorola boot logo, did the initial vibrate and then.... nothing. It just stayed there. I know that it didn't actually start booting because the Moto logo didn't animate, so seems like it was stuck on the boot loader.
Restarted into TWRP and tried to wipe cache, but I got an error saying that the cache partition couldn't be mounted. Strange stuff, so I said what the hell, let's factory reset this guy. And nope, that didn't work either. TWRP failed to mount /data, /system and /cache. It's like the partitions don't even exist anymore. I checked the sizes in TWRP and they're all showing 0MB.
So I went back to Fastboot, and tried to flash the original 5.1 system files (the .img ones, not the .zip ones), but I kept failing with a "Could not write to device" error. Also tried doing "fastboot erase userdata", but that also returned an error. Basically, it sounds like I can't access the storage (write to it or even read it) on the device for some weird reason.
I left the phone alone for about half a day and decided to try again except this time, I couldn't even get into fastboot! The power button does absolutely nothing. I know the battery is full because I left it in the charger. At first, the little battery low indicator in the earpiece would turn on, but now it doesn't even do that. Basically I'm left with a dead phone at this point. Does anyone know of a way for me to fix this? Sounds like a hardware fault maybe? I'd like to get a second opinion before I ship it off to get fixed by Motorola.
AggieMan0419 said:
Woke up yesterday morning and my phone was acting all weird. Couldn't unlock the phone from Moto Display (swiping to unlock from the black screen with the clock on it). So I decided to hard reboot it (held down the power and volume down button for about 10 seconds). At that point, the phone got to the Motorola boot logo, did the initial vibrate and then.... nothing. It just stayed there. I know that it didn't actually start booting because the Moto logo didn't animate, so seems like it was stuck on the boot loader.
Restarted into TWRP and tried to wipe cache, but I got an error saying that the cache partition couldn't be mounted. Strange stuff, so I said what the hell, let's factory reset this guy. And nope, that didn't work either. TWRP failed to mount /data, /system and /cache. It's like the partitions don't even exist anymore. I checked the sizes in TWRP and they're all showing 0MB.
So I went back to Fastboot, and tried to flash the original 5.1 system files (the .img ones, not the .zip ones), but I kept failing with a "Could not write to device" error. Also tried doing "fastboot erase userdata", but that also returned an error. Basically, it sounds like I can't access the storage (write to it or even read it) on the device for some weird reason.
I left the phone alone for about half a day and decided to try again except this time, I couldn't even get into fastboot! The power button does absolutely nothing. I know the battery is full because I left it in the charger. At first, the little battery low indicator in the earpiece would turn on, but now it doesn't even do that. Basically I'm left with a dead phone at this point. Does anyone know of a way for me to fix this? Sounds like a hardware fault maybe? I'd like to get a second opinion before I ship it off to get fixed by Motorola.
Click to expand...
Click to collapse
It sounds like hardware fault to me. It sounds almost like the internal memory died.
Sent from my XT1095 using Tapatalk
If you're getting an error that it was unable to write through fastboot, it sounds like your memory is FUBAR. If it's under warranty I would definitely contact Moto.
Sent from my XT1095 using Tapatalk
Hi all, something new out for hardbrickeds XT1092/1095 ? As i read on other threads Motorola would not release the files we neeg to repair it with blankflash
Related
...Brick an *UNROOTED* G1...?!
I attempted a soft factory reset (which I have done on many occasions previously successfully) but on this occasion I've run into the bootloop. Hitting Camera+Power button results in bootloop also.
One thing to mention is I removed my SD card before running the factory reset?
I've tried leaving the battery out over night and trying again in the morning.
I've tried placing the SD card back in and booting up the phone.
I've tried holding Home+Power to get into recovery but results in bootloop
I've tried holding Camera+Power to get into Bootloader but results in bootloop.
Any suggestions please?
Thanks!
No, this should not happen. With Bootloop do you mean there is just the G1 logo and nothing else, or does it get past the logo and reboots then?
Another thought, has this phone ever been rooted and unrooted again?
If you are still under warranty and the phone is completely stock, I'd return it.
Nope. Phone has never been rooted then unrooted.
By bootloop, I mean, G1 T-Mobile logo shows followed by a picture of a open box with the phone just outside animation and then seconds later the phone reboots itself running into this loop again and again.
Warranty is only for a single year, right? So then that's not an option.
Thanks for suggestions.
Jignesh Sutar said:
Warranty is only for a single year, right? So then that's not an option.
Click to expand...
Click to collapse
Depends on where you are: http://www.htc.com/www/support/warranty.html
It looks like you phone either fails to boot, thus tries to boot recovery (box picture is the background of the recovery) and then reboots (best case, i guess) or the boot to recovery flag is set, recovery fails, reboot (you might seriously be screwed).
You are sure that you can't enter the bootloader? Also try Back+PowerOn. That would make things alot more easy.
How long does it stay with the box picture? Long enough to get adb connected? If yes you could try "adb shell reboot bootloader".
Tried all combinations of buttons to try get into bootloader or recovery, nothing!
Definitely no chance of being able to ADB, the phone switches off very quickly...
Also, have ensured the battery is fully charged, in case that has an impact?
I really looks like you are the first all stock bricked guy I ever heard of.
The boot recovery flag seems to be set for some reason (is this set during a normal hardreset?) as all boottime commands are ignored.
The recovery fails improperly (sounds strange, but if it failed properly, you would end up in bootloader or your system).
-> That really looks like a brick...
Options:
- Warrenty
- JTAG
- perhaps someone else has another idea / sees something I missed...
Good luck with it.
Jignesh Sutar said:
By bootloop, I mean, G1 T-Mobile logo shows followed by a picture of a open box with the phone just outside animation and then seconds later the phone reboots itself running into this loop again and again.
Click to expand...
Click to collapse
What where you flashing? It probably had a radio and something got copied incorrectly into the staging area of ram.. if the radio passes recovery's validation but not the current radios validation you can get stuck.. this shouldn't be possible but I've seen it before.. my bet is a bit error at the wrong point in time.
I have G1 sitting around that I never messed with until last night, so if it's bricked, it's not a big deal. The phone will turn on, and loop through the splash screen. The only way it will boot is in safe mode. When trying to do ANYTHING in safe mode (aside from power down), everything will FC. If i go into the recovery menu with the Home plus End key sequence, I get the "can't open cache recovery command". I've tried to install RC33 in that screen, and get "installation interrupted".
The phone was given to me, so I really don't know if it was rooted or what was on it before. I do remember it worked, and just one day stopped working. When it was working I never saw a superuser icon or any other apps you usually see with a root. Thanks in advance for any help.
No one? Is there just a full update I can throw on the SD card and get it running?
Try formatting the sd card fat32, putting dreaimg.nbh(search) on it. Then, put it in the phone and boot with camera+power. Follow the onscreen instructions, and hopefully it'll work.
If it doesn't, not my fault. Good luck!
Thanks Michael, but I did that already and it really didnt change anything. I noticed the recovery menu looks a bit different, and when I go to safemode, the "android" looks different, but thats it. Still cant boot, and still shows there is no recovery in the recovery menu.
I've been using Hazou's ROM for months, worked fine, haven't changed anything. Today I was browsing in Firfox with quite a lot of tabs open. I kept getting odd warnings of apps having low memory. I could do nothing with these popping up every second so I restarted my phone. It was taking forever shutting down so I did power + volume down.
Now it's stuck at the very first screen, the 'warning bootloader unlocked' screen. It just stays like this and occasionally resets and makes the reset buzz and that's it. I can get into fastboot by holding volume down and power and releasing but whenever I try and select an option in fastboot it just resets to the first screen or fastboot again.
I'm mystified because usually people have issues performing the rooting etc but it was a while ago that I successfully rooted the phone and unlocked the bootloader and put on a rom and had been using it. Could my hardware (memory?) have broken rather than software?
Any help would be great, thanks.
Ps. fastboot says:
"Fastboot Reason:
max download size: 100mb."
Possible it's always said that and it means nothing.
Ps. Possibly this thread is of use to me? I'm not sure if it's the same problem. http://forum.xda-developers.com/showthread.php?t=1945176
quixoticduck said:
Ps. Possibly this thread is of use to me? I'm not sure if it's the same problem. http://forum.xda-developers.com/showthread.php?t=1945176
Click to expand...
Click to collapse
What does it say when u try to flash a recovery? a stock system image? wipe data? wipe cache?
If any of those mention an i/o error the phone is beyond repair from the knowledge here or someone can come up with any kind of solution. More phones have this error and it can happen to anyone, it is just rare.
Moto X 2014: unrooted with bootloader unlocked. It's running Stock 5.1 and I haven't messed with anything on it. I gave it to my Dad after a few months of using it, so I factory reset it and gave it to him, 2 weeks later he tells me it has stopped working. It boots up normally, but from then on it is black, I can access minor parts of the OS such as the power off menu, the camera (by shaking) and Moto Display, but everything else doesn't work. I have never seen anything like this before, and I am well accustomed to flashing custom ROMs and rooting Android. If it comes down to it I will factory reset it or flash stock, but I can't even plug it into my PC and retrieve any files. Anyone have any idea whats gone wrong?
I have attached a video demonstrating what's happened to help diagnose the problem.
thomaswilloughby said:
Moto X 2014: unrooted with bootloader unlocked. It's running Stock 5.1 and I haven't messed with anything on it. I gave it to my Dad after a few months of using it, so I factory reset it and gave it to him, 2 weeks later he tells me it has stopped working. It boots up normally, but from then on it is black, I can access minor parts of the OS such as the power off menu, the camera (by shaking) and Moto Display, but everything else doesn't work. I have never seen anything like this before, and I am well accustomed to flashing custom ROMs and rooting Android. If it comes down to it I will factory reset it or flash stock, but I can't even plug it into my PC and retrieve any files. Anyone have any idea whats gone wrong?
I have attached a video demonstrating what's happened to help diagnose the problem.
Click to expand...
Click to collapse
If you search the forum here for "black screen" it has happened to other people as well on stock 5.1. Supposedly the fix is a factory reset.
Sent from my XT1095 using Tapatalk
AGISCI said:
If you search the forum here for "black screen" it has happened to other people as well on stock 5.1. Supposedly the fix is a factory reset.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ok, It was just really surprising thats all. I will factory reset then. Thanks
I am having the exact same issue. Have you had a luck resolving it short of a factory reset?
My phone battery died last night. I plugged my phone in, let it get about 15% charge, then tried to turn it back on. The phone boots like normal, but after the boot animation goes away, the screen is black. Active notifications still seem to work, and I can hold the power button to get the Power Down option. I can boot into the bootloader & access recovery just fine. However, my phone is fully stock (no root, no bootloader unlock, no anything). I can't seem to access ADB when the phone is powered normally (ie, when I'm at this mysterious black screen), but it's possible that USB debugging isn't even enabled.
So far, I've found a few people who've said a full factory reset will fix the problem, but I'm looking for another solution, or at least a way to grab my data before I reset. Since my bootloader's still locked, I can't seem to use fastboot boot to boot into TWRP, and I can't find any other way to access my data to copy it off the phone. I've tried wiping the cache using the stock recovery to no avail. Any suggestions?
bjg222 said:
I am having the exact same issue. Have you had a luck resolving it short of a factory reset?
My phone battery died last night. I plugged my phone in, let it get about 15% charge, then tried to turn it back on. The phone boots like normal, but after the boot animation goes away, the screen is black. Active notifications still seem to work, and I can hold the power button to get the Power Down option. I can boot into the bootloader & access recovery just fine. However, my phone is fully stock (no root, no bootloader unlock, no anything). I can't seem to access ADB when the phone is powered normally (ie, when I'm at this mysterious black screen), but it's possible that USB debugging isn't even enabled.
So far, I've found a few people who've said a full factory reset will fix the problem, but I'm looking for another solution, or at least a way to grab my data before I reset. Since my bootloader's still locked, I can't seem to use fastboot boot to boot into TWRP, and I can't find any other way to access my data to copy it off the phone. I've tried wiping the cache using the stock recovery to no avail. Any suggestions?
Click to expand...
Click to collapse
Unfortunately I couldn't retreive any data from the phone, I can confirm however that a factory reset does fix the issue. The Android automatic backup does work in the broken state so I did manage to restore my settings and apps. But the internal sd card was wiped upon factory reseting. Just an idea of the top of my head: Try running adb backup and see if that works, and then unlocking the bootloader, flashing twrp, restoring the backup, and finally transfering the internal sd card data to a mounted drive using twrp. Thats just a stab in the dark and i dont have the phone on me to test it. Give it a try and lets hope Motorola will fix this bug soon.
Ok, thanks. I did try adb backup, but adb won't recognize the device when it's "booted" & sitting at the blank screen, and the stock recovery doesn't give full adb access. I'm currently looking into the various data recovery options to maybe pull some stuff off after reseting. It's really only a few files that I need, so maybe that will work?
bjg222 said:
Ok, thanks. I did try adb backup, but adb won't recognize the device when it's "booted" & sitting at the blank screen, and the stock recovery doesn't give full adb access. I'm currently looking into the various data recovery options to maybe pull some stuff off after reseting. It's really only a few files that I need, so maybe that will work?
Click to expand...
Click to collapse
Unfortunately the internal SD card mounts using MTP and not like a flash drive, so using the usual methods through Windows to recover wont work. However you could try and restore your internal sd card using this solution: http://goo.gl/OKdV14
As for accessing adb through recovery, you could try this method: http://goo.gl/5T7bhq
Hopefully one of these methods should work, so you can at least recover some of your files.
I had the same problem today. I tried to backup a twrp backup I have made few weeks ago but I still had the black screen. The only solution is to factory reset...
Happily I could have saved my data when I was on TWRP. Anyone knows how to restore sms from the data I have saved ?
I have a Blu R1 HD that I have been on again off again fiddling with for a few months that is soft bricked. It will turn on but it will hang on the second "Bold like us" splash screen after the animation ends. It had no recovery installed to it prior to the bricking, I have attempted flashing a stock rom to it with SPFT but It gets interrupted less then 3 seconds in. From my reading It seems like I have the 6.6 preloader that stopped spft from working.
Is there anything that could be done with this to get it working once again?
kamikazisolly said:
I have a Blu R1 HD that I have been on again off again fiddling with for a few months that is soft bricked. It will turn on but it will hang on the second "Bold like us" splash screen after the animation ends. It had no recovery installed to it prior to the bricking, I have attempted flashing a stock rom to it with SPFT but It gets interrupted less then 3 seconds in. From my reading It seems like I have the 6.6 preloader that stopped spft from working.
Is there anything that could be done with this to get it working once again?
Click to expand...
Click to collapse
Depends on few things.
Do you know what was last thing done before this brick?
Have you tried holding volume up when powering on, to enter recovery(stock, i know you mentioned no custom recovery installed)?
It goes to and past the animation , so i don't think it is a secure boot type of failure. But maybe a bad data problem. See above statement about recovery.
mrmazak said:
Depends on few things.
Do you know what was last thing done before this brick?
Have you tried holding volume up when powering on, to enter recovery(stock, i know you mentioned no custom recovery installed)?
It goes to and past the animation , so i don't think it is a secure boot type of failure. But maybe a bad data problem. See above statement about recovery.
Click to expand...
Click to collapse
I have gone into the stock recovery menu, And i have attempted factory data reset, clearing the cache, and a root integrity check. The integrity check says one item fails the check and that is "/system/lib/libLLVM.so"
The last thing that I recall happening is that I had a pop up saying that an app had stopped working, But it reappeared immediately after closing it again several times. I thought rebooting it would stop whatever was happening, but it never came back to the OS.
The device has a small crack on the bottom right hand side of the screen that happened when it fell from my pocket on top of a ladder. A family member who also works with electronics as a hobby thinks that may have something to do with it but the phone worked for weeks after the break happened.
kamikazisolly said:
I have gone into the stock recovery menu, And i have attempted factory data reset, clearing the cache, and a root integrity check. The integrity check says one item fails the check and that is "/system/lib/libLLVM.so"
The last thing that I recall happening is that I had a pop up saying that an app had stopped working, But it reappeared immediately after closing it again several times. I thought rebooting it would stop whatever was happening, but it never came back to the OS.
The device has a small crack on the bottom right hand side of the screen that happened when it fell from my pocket on top of a ladder. A family member who also works with electronics as a hobby thinks that may have something to do with it but the phone worked for weeks after the break happened.
Click to expand...
Click to collapse
I do not know if there will be any way forward with this.
As you are not bootloader unlocked, sp flash refuses to connect, and only thing that can be done on stock is "factory reset" did not help, you might be done , other that see if can send to Blu.
mrmazak said:
I do not know if there will be any way forward with this.
As you are not bootloader unlocked, sp flash refuses to connect, and only thing that can be done on stock is "factory reset" did not help, you might be done , other that see if can send to Blu.
Click to expand...
Click to collapse
Sending to blu isnt an option. Out of waranty period, And I also opened it to make sure there was nothing obviously physically wrong.
I also tried using the dirty cow tool, But i cant seem to see the device in ADB. Fast boot however, can see it.
Update over ADB/SD in the stock recovery wouldn't lead me anywhere would they?