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
Related
Very noobish issue. Rooted, unlocked bootloader on Atrix HD. Set up SafeStrap as recovery. Everything checked and working. After letting SafeStrap install Cyan 10.3 and rebooting, phone entered CyanogenMod boot screen and become stuck for an hour. Realized that I forgot to reset and wipe all stock settings and cache (yes, I know that should have been obvious step). Figured I could just go into SafeStrap and make the quick fix.
Seems that I'm unable to enter my custom recovery, instead I'm lead to the familiar bricked android stock recovery. No options to access stock rom (assuming it was deleted during install or lost, etc). Tried installing a different recovery, but fastboot on PC is unable to find device. Help at this point is very much appreciated, either to do any of the following:
1. Somehow access SafeStrap again (assuming that it wasn't wiped aswell) so I can clear stock settings and cache, get Cyan 10.3 going properly.
2. Instructions/links to another method to otherwise forcibly delete stock settings and cache (please keep in mind, fastboot is currently unable to find device).
3. Otherwise completely clear phone of EVERYTHING, then reinstal stock recovery and or/stock ROM so I can give up on flashing custom and stick with stock.
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Update Motorola drivers on your computer and check threads for fastboot files from skeevydude.
Sent from my MB886 using XDA Premium 4 mobile app
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
http://forum.xda-developers.com/showthread.php?t=2226527
Sent from my MB886 using XDA Premium 4 mobile app
SkunkID said:
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Click to expand...
Click to collapse
The error is from using the wrong fastboot executable. Look at post 5. If you get a stickybit error, search our general forums for "stickybit" and you'll find that fix.
deeje00 said:
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
With a bit of creativitity one could use SSR to dual boot Holo Blur and Batakang....or two custom 4.3's that use the same kernel....PAC + Carbon both with arrrghhh's kernel.....Only problem is ya can't be a noob at all if ya do it.
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
When you're at the "dead Android" screen pressing Vol Down + Power pushes it into recovery, iirc - might seem random but there's a purpose behind it.
SkunkID said:
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
Click to expand...
Click to collapse
Hi, I am having the same issue you had... how the heck were you able to get back into stock recovery? Every time I try my phone just reboots and gets stuck again. I cant even turn off my phone with out it rebooting. I have read your posts and followed that other forum you mentioned but if I cannot boot into recovery and if my computer cant see my phone it wont work. Please help when you get a chance.
I factory reset my Glass today because it wouldn't connect to my phone (I switched roms so I needed to pair Glass again). After I did the reset it went into a boot loop. When it's on the "Glass is Updating" screen it can't be accessed via ADB, but I managed to figure out how to get it into the bootloader via the buttons.
From the bootloader I've tried erasing and flashing 16.2, 16.11, and 16.0 but it just returns to the same "Glass is Updating" screen when I reboot.
When I erase, I erase boot, recovery, system, userdata, and cache. When I flash, I flash boot, recovery, and system. I've tried with and without flashing userdata.
Does anyone have any ideas as to what could be wrong?
EDIT: Something really weird is going on. I ran the erase without flashing anything back on and did a reboot. I expected it to stop at the bootloader since there should be nothing to load, but instead it continues to go into the "Glass is Updating" boot loop.
EDIT 2: I've been doing a lot of reading and it sounds like there are more partitions than just the bootloader and the 5 that I have been erasing. My guess right now is that my device downloaded the 16.2 update into some other partition before I did the factory reset and now every time it boots it's running that update. I can't get much info from the device because I can't use adb.
I had the same issue when I tried flashing 16.2. I went back to XE12 and it resolved the issue. The whole point was to get away from the train wreck that is XE16.x anyway, so I'm just going to stay on 12 until the XE17 images are available - then we'll see if that release is any more stable.
davezack said:
I had the same issue when I tried flashing 16.2. I went back to XE12 and it resolved the issue. The whole point was to get away from the train wreck that is XE16.x anyway, so I'm just going to stay on 12 until the XE17 images are available - then we'll see if that release is any more stable.
Click to expand...
Click to collapse
That did it! I didn't try a version back that far because as far as I know mine had XE16 on it when I first got it.
Thanks!
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.
I just got the phone today.
I was trying to follow this guide to install lineageOS https://wiki.lineageos.org/devices/s2/install
Flashed twrp and got up to the 3rd part. I was about to start flashing the rom but the recovery mode was asking me for a password I didn't have. I never set a password on it.
So I tried doing a factory reset and now when I try to reboot it, it gets stuck on the boot screen with the LeEco logo and powered by android etc.
I can still boot into recovery. I tried wiping the cache and dalvik cache and factory reset it again but it didn't help. I didn't try wiping anything else yet since I'm afraid to break it.
I did get twrp on but I did not install any roms yet.
All I did was the factory wipe and now I'm stuck.
I have no important data on it, so I don't care if I have to reset everything.
If I can just get it back to factory default so I can start over, I'd be fine.
What's the recommended course of action?
Sorry I'm kind of a noob at this so detailed instructions would be appreciated.
I figured it out.
In recovery mode, mounted the phone to computer
Computer didn't recognize it at first so had to go to device manager and change the driver to read it as composite usb
Moved over the rom I wanted to flash and just installed it like I was planning to
Another possibility would have been an OTG adapter. You don't have any problem with windows drivers that way
motaku96 said:
I figured it out.
In recovery mode, mounted the phone to computer
Computer didn't recognize it at first so had to go to device manager and change the driver to read it as composite usb
Moved over the rom I wanted to flash and just installed it like I was planning to
Click to expand...
Click to collapse
So you flashed it with ADB?, cuz i have the same problem aswell.
somzkiller said:
So you flashed it with ADB?, cuz i have the same problem aswell.
Click to expand...
Click to collapse
Yes, I found it easier to flash through ADB.
This is my backup phone so I don't care for the data that is on it and just want it working again. It was rooted before and I needed it unrooted in order to download an app that was blocked by root detection. I tried uninstalling the root using Super SU in its settings, when I restarted my phone it just freezes at the AT&T white screen.
I'm still able to go into the boot recovery menu, I tried putting on the I537UCUCOC7 (5.0.1) firmware found here (https://forum.xda-developers.com/showthread.php?t=2629093). I downloaded it, extracted the zip, and renamed the file "update.zip" and put the file on a microSD then in the recovery boot menu I went to install from external and selected the update.zip. It sorta kinda looked like it accepted it but I get a red error message about the sideloader and I'm still stuck at the white screen when it boots.
What else can I do from here?
P.S. I already tried wiping the cache and data/factory restore options and that didnt work.
Is there anything else that can be done?
I restored my phone to 4.4.2. How can I install 5.0.1? When I search for software updates it says theres nothing available even though I know it can go to 5.0.1 cause thats what I had before it bricked.
Please share how did you restore when I only able to boot into recovery and clearing cache and factory reset does not help. Phone just stack on boot loop
RemixDeluxe said:
I restored my phone to 4.4.2. How can I install 5.0.1? When I search for software updates it says theres nothing available even though I know it can go to 5.0.1 cause thats what I had before it bricked.
Click to expand...
Click to collapse
alex4cta said:
Please share how did you restore when I only able to boot into recovery and clearing cache and factory reset does not help. Phone just stack on boot loop
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s4-active/general/guide-update-to-i537-att-firmware-t2835481