Hello, I have an htc desire 510 cricket that became unusable. so, I attempted to factory reset it, but that did not work. So, in my quest to find an answer, I have tried many different things. I think in the process I have accidentally wiped the system and cache. Then I began to get the system and cache cannot be mounted errors. So, I followed the directions of reformatting those sections using twrp. Still they have remained unmountable. I have tried all the instructions online that I can find. However, now, I cannot load twrp. I can't even boot into twrp from fastboot. When i try recovery or factory reset in the bootloader the phone merely vibrates, blanks and then goes back to the bootloader.
anyone have any ideas how I can bring this back to life, if at all possible?
Thanks in advance for any help you may be able to give.
Dave
Another thing I just noticed
bramwell40 said:
Hello, I have an htc desire 510 cricket that became unusable. so, I attempted to factory reset it, but that did not work. So, in my quest to find an answer, I have tried many different things. I think in the process I have accidentally wiped the system and cache. Then I began to get the system and cache cannot be mounted errors. So, I followed the directions of reformatting those sections using twrp. Still they have remained unmountable. I have tried all the instructions online that I can find. However, now, I cannot load twrp. I can't even boot into twrp from fastboot. When i try recovery or factory reset in the bootloader the phone merely vibrates, blanks and then goes back to the bootloader.
anyone have any ideas how I can bring this back to life, if at all possible?
Thanks in advance for any help you may be able to give.
Dave
Click to expand...
Click to collapse
Now when I just try to start my phone normally, it automatically goes to the fastboot screen. It won't even try to boot up.
Related
Okay, so I am having a lot of trouble with a bootloop for seemingly no reason. I got two nexus 6'es, and i unlocked, rooted, and flashed TWRP on mine, no problem at all.
So onto my gf's, I did fastboot oem unlock, and then i went to reboot-bootloader, but i accidentally bumped the power button, which was on "Start". It launched a weird loading style screen - the green android standing up with a blue ball spinning around (NOT the stock recovery, android laying down with chest open) , and i couldn't do anything. eventually, when i hit the volume up button, it said "Formatting /data..." but it never completed.
The only thing I could do was unplug it from my computer (mac) and put it in fastboot mode again. I tried flashing all the shamu factory images, and then rebooted again. Same thing. Now, i re-locked and then unlocked the phone again. Now it's just looping at the red, blue, green and yellow circles for over ten minutes now. What the heck can i do to fix this? I can in no way get it to boot to the lock screen, but fastboot is working fine and it recognizes the device
Edit: Got into TWRP by writing it over stock recovery. Tried to factory reset in TWRP and got the following errors:
E: Unable to mount /data
Unable to mount /cache
Unable to mount /storage
Wiping the cache should fix it.
joshua.justice said:
Wiping the cache should fix it.
Click to expand...
Click to collapse
Okay, i wiped cache, userdata, system and everything just to be safe, am currently finishing flashing the rest of the factory images, waiting on system. I'll let you know
joshua.justice said:
Wiping the cache should fix it.
Click to expand...
Click to collapse
./fastboot erase cache did not work still looping the four colored circles
joshua.justice said:
Wiping the cache should fix it.
Click to expand...
Click to collapse
Got this when trying to Factory reset in TWRP Got into TWRP by writing it over stock recovery.
E: Unable to mount /data
Unable to mount /cache
Unable to mount /storage
I was trying to take picture but suddenly my phone restarted. Then after few sec it was not booting up. It was giving me blank screen, no boot animation was coming up. So now what should I do? I try to wipe/factory reset the phone but still phone was not booting up. It was still stuck on blank screen. Please help?
Device: nexus 4
I got stuck in a boot loop also. I had to reflash the factory image. See this link here. It's the best way to do it just follow the instructions you should be fine. http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
Try to flash the unencrypted boot image, mine did the same thing when in first flashed TWRP to it and it. Then reflash the stock image and wipe the phone.
So let me explain my situation. I decided to factory reset because I needed to clean up my tablet quite a bit. I did this and it decided to freeze on reboot. I waited 30ish minutes and it was still stuck, so I shut it off. It would not boot after that, it would get stuck at the second asus screen with load wheel. I went into recovery and did data/cache wipe. That allows me to boot once after everytime I wipe otherwise it will be a bootloop. I tried sideloading the firmwares on asus's support page NONE of them worked. I tried fastboot and adb and none of them were successful. I have a bunch of errors in the bootloader. I also have pictures of what it boots to. Aswell as the bootloader errors. What should I do, asus said I should rma but I dont have the money and I also rooted this thing which can be seen whenever I do su in adb it still asks for root. I have very few options anybody's word would probably be a help. Thanks
How I recovered
applerulez1 said:
So let me explain my situation. I decided to factory reset because I needed to clean up my tablet quite a bit. I did this and it decided to freeze on reboot. I waited 30ish minutes and it was still stuck, so I shut it off. It would not boot after that, it would get stuck at the second asus screen with load wheel. I went into recovery and did data/cache wipe. That allows me to boot once after everytime I wipe otherwise it will be a bootloop. I tried sideloading the firmwares on asus's support page NONE of them worked. I tried fastboot and adb and none of them were successful. I have a bunch of errors in the bootloader. I also have pictures of what it boots to. Aswell as the bootloader errors. What should I do, asus said I should rma but I dont have the money and I also rooted this thing which can be seen whenever I do su in adb it still asks for root. I have very few options anybody's word would probably be a help. Thanks
Click to expand...
Click to collapse
Please see what worked for me, when i got it a similar situation.
http://forum.xda-developers.com/memo-pad-7/help/unbrick-memo-pad-me176cx-t2987068#post58231184
ardluc said:
Please see what worked for me, when i got it a similar situation.
http://forum.xda-developers.com/memo-pad-7/help/unbrick-memo-pad-me176cx-t2987068#post58231184
Click to expand...
Click to collapse
I have given you the nickname android jesus in my household, my tablet is fixed now! I love you, thanks so much! This thread can be closed.
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 ?
So after trying to install the cyanogenmod nightly, my device started displaying repeated errors about different processes stopping. This would not stop, so I tried to reboot the device. Now the device is attempting to load into the recovery section, but it has just reached the teamwin screen and just keeps going black then flashing back to the screen. Any way I can recover it, or should I finally retire it?
I'm having the same exact issue. Mine started after doing a factory reset from the system settings to try to alleviate some Play Store issues.
I'm just replying in the hope that someone will see this and help us out.
I got the same issue, I tried to factory reset the system and now mine keep flash at the teamwin screen. I cannot connect to the PC neither. Please help.
nicarasu said:
So after trying to install the cyanogenmod nightly, my device started displaying repeated errors about different processes stopping. This would not stop, so I tried to reboot the device. Now the device is attempting to load into the recovery section, but it has just reached the teamwin screen and just keeps going black then flashing back to the screen. Any way I can recover it, or should I finally retire it?
Click to expand...
Click to collapse
You probably didn't factory reset, wipe cache and wipe dalvik cache when you flashed the ROM.
usn.mustanger said:
I'm having the same exact issue. Mine started after doing a factory reset from the system settings to try to alleviate some Play Store issues.
I'm just replying in the hope that someone will see this and help us out.
Click to expand...
Click to collapse
Both of you, you can't factory reset a rooted device from the system settings, this usually wipes out the whole OS because with root the device has access to system partition, when you reset it wipes everything it has permission to remove(with root it has permission to everything).
Factory reset from settings on a nonrooted device doesn't wipe the OS because it doesn't have permission to alter system. That's why it doesn't harm the device and only wipes the data you've put on the phone.
Try flashing TWRP and see if your devices will boot to recovery then. If not, you may have to use fastboot to flash the stock firmware.
boy201 said:
I got the same issue, I tried to factory reset the system and now mine keep flash at the teamwin screen. I cannot connect to the PC neither. Please help.
Click to expand...
Click to collapse
nicarasu said:
So after trying to install the cyanogenmod nightly, my device started displaying repeated errors about different processes stopping. This would not stop, so I tried to reboot the device. Now the device is attempting to load into the recovery section, but it has just reached the teamwin screen and just keeps going black then flashing back to the screen. Any way I can recover it, or should I finally retire it?
Click to expand...
Click to collapse
Strange... is your tablet at least recognized by a computer?
Make sure you connect it to a USB 2.0 port
Trying to give the mother in law my old N6. It was rooted / bootloader unlocked. First attempt was to factory reset from within the OS. That worked fine, until I rebooted... it wouldn't boot.
I then downloaded the Shamu factory images from Google's website (shamu-n6f27m-factory-bf5cce08) and ran the flash-all.bat script. Multiple errors showed up during the script... but I chalked it up to ADB looking for boot slots etc, whereas this one has none.
Phone booted fine. Installed apps, set up the phone, power cycled it and promptly entered a bootloop.
Ran flash.all again, phone booted fine. Flashed TWRP, booted into recovery, checked things out in there (didn't do anything but flash the TWRP) tried to reboot, phone bootloops.
Flashed TWRP, booted into Recovery, tried to erase system, etc.... multiple errors again. Booted into bootloader, ran Flash-all... phone boots. Installed some apps, rebooted phone and bootloop again.
Then I did something REALLY stupid, I locked the bootloader from ADB. Now I'm on the bootloader, but can't OEM unlock because it's asking me to boot into the OS and enable the ability from Developer options.
I've no idea why this phone is doing this - booting fine into the OS once and then getting into a bootloop every time thereafter.
If anyone can shed some light on this, I'd appreciate it. Also, how in the hell do I unlock the bootloader now that I've locked it and I can't boot into the OS or run the Flash-all.bat anymore since it's locked?
Is your recovery stock? If it is, sideload the last OTA from Google and that should get you back into Android so you can toggle the OEM Unlock button.
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
usafle said:
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
Click to expand...
Click to collapse
So did you finally figure out what it could have been that you were doing wrong?
Strephon Alkhalikoi said:
So did you finally figure out what it could have been that you were doing wrong?
Click to expand...
Click to collapse
No. I could only assume I had messed something up when I was using it back in the day and really hosed something up. System wouldn't wipe, cache wouldn't wipe, userdata wouldn't wipe in "fasboot" just kept getting "unable to find XXXX".
So multiple flashes into TWRP and bootloops trying to really REALLY wipe the device finally fixed it. I just kept erasing / wiping every partition I could find in Stock Recovery, TWRP, and with fastboot commands. Finally I got them all wiped/cleared and was able to flash the stock OS back on and have it 'stick'.