Here's my situation, maybe someone will find it interesting or know what's going on. I was running the EOS Jelly Bean (EOS-tf201-20120728-31.zip). Everything was running pretty well for a few days, then yesterday the device simply powered off. When I rebooted it got to the splash screen then shut off before it could get any farther. I figured it was a power issue, so I plugged it in and charged it for a while but get the same response. Around this point I started to get suspicious and tried to boot into recovery. It got to "Booting Recovery Kernel Image" then powers off the same way.
So then I proceed to go into fastboot and fastboot works great no power offs. Through that I am able to flash openrecovery-twrp-2.2.1-tf201.blob and the virtuous packaged boot as per this thread http://forum.xda-developers.com/showthread.php?t=1773280 as well as factory reset. I also tried a few other boot/recovery combinations and was able to make it into recovery. In twrp recovery I was able to install the latest Virtuous rom which got me back to stock and I thought good case closed. I even made it all the way into the OS and was able to install apps, wifi worked great, run the apps etc. Eventually the screen went blank though and I was stuck back in the same shutdown on boot scenario as described above. Now I'm able to fairly consistently flash openrecovery-twrp-2.2.1-tf201.blob, reboot, get into teamwin recovery, but now even that appears to be randomly powering off.
So now I'm guessing that it may just be bricked and is probably a hardware issue since the reboots appear so random, the unit was refurbished. At the same time I'm still holding out some hope that it's simply some boot code somewhere that was corrupted and I can flash something and get things back to normal again since I can still access fastboot and occasionally ADB and recovery. I've flashed from fastboot system/recovery/boot, any other thoughts or potential combinations I could try? Also anything I can do with those tools to debug it further and get more data on what may be the root cause?
My device details: SGS3 T999, rooted, running Jellybean 4.3 on a liquid smooth ROM. Its a year old and has been a solid performer up until now.
My device is stuck in a cycle where it gives a quick vibrate, then SGS3 splash screen with white letters, then black screen, then tiny blue "Recovery booting..." words in upper left of screen, then black screen with couple vibrations, and around and around it goes in the same repeating cycle.
Just before it started I had taken the following actions: Dumped the following 2 files onto my EXTSD card (cm-11-20131217-NIGHTLY-d2tmo.zip, gapps-kk-20131119.zip) from my PC, booted phone into recovery mode using TWRP, did a factory reset wipe (success), cache wipe (success), dalvik cache wipe (success), flashed the NIGHTLY file (failed), flashed the gapps file (failed). At this point I should have sought some support. Fool! I next did a reboot step still in recovery mode. Without the reboot happening a message came up stating Superuser permission had been broken (the best I can remember) and the option to have TWRP repair the permission. I opted "yes" to repair. Then the loop started that I can't escape.
I have pulled the battery multiple times, tried a regular boot up, tried a recovery boot up (up volume+power+home) dropping the home button after a few seconds. Nothing is working. Prior to the above steps I backed up everything on the device. So I have backups to use if it can be done. My best guess is that I failed to update my CyanogenMod or TWRP to the very latest versions and it caused this hang up. Otherwise, I don't know what to do and need any help I can get.
Has anyone had this issue or heard of anyone who has and have any helpful suggestions, tips, ideas, etc..?
Thank you in advance. This is my first XDA post. Please forgive and offer tips if this thread needs any scrubbing.
I've had a few similar events for a few different reasons.
I would suggest booting into recovery but it seems you have tried that already.
If the device is plugged into a wall or pc, unplugg it, that has seemed to cause and fix boot issues for me before.
Other than that, I dunno, if you can't get to recovery or fastboot, I dunno...
My wife was using her phone (completely stock, no mods whatsoever) and it started shutting down processes (contacts, calendar, etc). She held the power button down to manually shutdown and then rebooted shortly after. The next day, it started to do it again, so she did the same thing only this time it stuck on the "M" logo screen. When she brought it home, I held the power & vol down buttons in for 2 minutes and the phone began to reboot but still stuck on the "M" logo screen.
I began searching vigorously online for a solution and have tried everything. **NOTE** - I am completely unsure what version of software the phone was running before this happened. The first thing I tried was RSD Lite with the JB Stock file from Team US Cellular. The flashing fails during certain lines of the .XML file. I took suggestions from other users to delete the lines it fails on and let the file continue the flash. Once it reboots, it is still stuck on the "M" logo screen. I then tried all the other stock firmware files I could and the same result each time.
Next, I tried using ADB and Fastboot tools. My PC recognizes the phone when plugged in and running command "adb devices" shows the phone listed, but whenever I try to run a pull or other command, I get error:closed. I've tried all the solutions of making sure ADB files are updated, running the list of commands to get the daemon connection reset, etc. I can't push/pull anything using adb. I tried using mFastboot with no luck either.
I tried the above steps over and over for 3 days straight, hoping I missed something simple. My final option was to boot into Recovery Mode and run Wipe Data/Factory Reset. When I select that option, about 3 lines of command begin to run and the phone reboots and goes back to being stuck on the "M" logo screen. The command lines and reboot literally happen within 2 seconds. That tells me Factory Reset is corrupted, but I'm not 100% at this point.
Does anyone have any insight on if there is anything I can do at this point? It wouldn't be such a big deal to lose the phone, but we have pics/videos of our 2 year old that we never got backed up at home or in the cloud and they're very important to us. Unfortunately, the phone did not have and SD card. I'm honestly out of ideas at this point and have never felt so defeated.
I got brave and decided to just unlock the phone and attempt to install TWRP on it and that doesn't even work. It says it flashed it, but whenever I choose Recovery, it never boots to TWRP. It continues to use the stock recovery screen. I'm assuming this thing is just completely done for?
Hi Im new to the forum but I am finding it to be a massive resource for all things technical android. I am also new to rooting android but am technically savvy, (10 years in IT will do that). Initially it went just fine, even if a speed bump here or there. I got my Sony Z2 (starting BL unlocked w most recent Sony stock .291 firmware) rooted and flashed with TWRP and SuperSU (UPDATE-SuperSU-v2.76-20160630161323.zip) using rocker00's guide. I was then able to successfully flash ParanoidAndroid's latest (pa_sirius-6.0.3-20160809-signed.zip) and Gapps (A-GAPPS+6.0.1_14.05.2016_v5.2.zip) using TWRP recovery. I got a minor bootloop trying to get PA running, but re-flashing seemed to clear it up. It seemed to work fine although I couldn't figure out how to get the pie controls or the halo notifications to work. Without those things i couldn't see the point, so I decided to try Cyanogen (cm-12.1-20161016-NIGHTLY-sirius.zip). Apparently this uses a different recovery (CWM), I was a little worried but went for it anyway. It seemed to be fine after the first reboot. I rooted fine (same SuperSU as before) and started installing apps via Google restore. But after the next reboot, it started bootlooping. First it would cycle between the Sony screen and a blank screen, But after trying a bunch of things (I'll detail below), it just hangs at the Sony screen indefinitely.
So, what I've tried till now to fix it is:
1) First I tried to reinstall TWRP using the tool from rocker00's post with the phone in fastboot mode. The flash went without error, but did not fix the problem. I have not been able to get into recovery since the bootloop. In the process I also did a fastboot -w, which also seemed to have relatively no effect, although I would get the android robot with the blue progress once before it reboot into the bootloop.
2) With the phone in flashmode I tried flashtooling the kernel again with the same from rocker00's post (D6503_23.5.A.0.575_kernel.ftf). No effect. I also tried flashing recovery a few more times using the script from his post to no effect (i think the phone needs to be booted for this tool to work).
3) I've tried all the relevant commands from this page and this page, hoping to eradicate whatever errant code is screwing with my phone. Since fastboot seems to be the only way to interact with my phone. I tried:
Code:
fastboot flash recovery /path/to/twrp-3.0.2-0-sirius.img
fastboot -w
fastboot update /path/to/pa_sirius-6.0.3-20160809-signed.zip
the attempt to flash PA through fastboot errored with a message about not having "android-info.txt".
I also desperately tried:
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
the one about data errored. the others seemed fine, but didn't change the situation.
This guide was informative yet quite useless to me, since I definitely don't want to start scripting my phone 2 days after starting this stuff. I've also scoured this forum and others for similar situations, which I've found but they all seemed to get resolved by either doing stuff I've already tried or from having a completely irrelevant problem to my own..
I'm really scratching my head here because it is all stock TWRP and Android or should be by now. adb commands aren't connecting due to stock android not having USB debugging enabled, and without being able to boot into the settings I can do nothing to change that. So all I have is fastboot. I also have a TWRP backup image I made before installing PA but till now Ive seen no way to restore it without booting into recovery.
Any help please!!!! This can't be bricked!!
epeace said:
Hi Im new to the forum but I am finding it to be a massive resource for all things technical android. I am also new to rooting android but am technically savvy, (10 years in IT will do that). Initially it went just fine, even if a speed bump here or there. I got my Sony Z2 rooted and flashed with TWRP (twrp-3.0.2-0-sirius.img) and SuperSU (UPDATE-SuperSU-v2.76-20160630161323.zip) using this guide. I was then able to successfully flash ParanoidAndroid's latest (pa_sirius-6.0.3-20160809-signed.zip) using TWRP recovery. I got a minor bootloop trying to get PA running, but re-flashing seemed to clear it up. It seemed to work fine although I couldn't figure out how to get the pie controls or the halo notifications to work. Without those things i couldn't see the point, so I decided to try Cyanogen. Apparently this uses a different recovery (CWM), I was a little worried but went for it anyway. It seemed to be fine after the first reboot. I started installing apps, rooted fine. But after the next reboot, it started bootlooping. First it would cycle between the Sony screen and a blank screen, But after trying a bunch of things (I'll detail below), it just hangs at the Sony screen indefinitely.
So, what I've tried till now to fix it is:
1) First I tried to reinstall TWRP. The flash went without error, but did not fix the problem. I have not been able to get into recovery since the bootloop. In the process I also did a fastboot -w, which also seemed to have relatively no effect.
2) I tried flashtooling the kernel again with the same from rocker00's post (D6503_23.5.A.0.575_kernel.ftf). No effect. I also tried flashing recovery a few more times using the script from his post to no effect.
3) I've tried all the commands from this page and this page, hoping to eradicate whatever errant code is screwing with my phone. Since fastboot seems to be the only way to interact with my phone. I tried:
Code:
fastboot flash recovery /path/to/twrp-3.0.2-0-sirius.img
fastboot -w
fastboot update /path/to/pa_sirius-6.0.3-20160809-signed.zip
the attempt to flash PA through fastboot errored with a message about not having "android-info.txt".
I also desperately tried:
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
the one about data errored. the others seemed fine, but didn't change the situation.
This guide was informative yet quite useless to me, since I definitely don't want to start scripting my phone 2 days after starting this stuff. I've also scoured this forum and others for similar situations, which I've found but they all seemed to get resolved by either doing stuff I've already tried or from having a completely irrelevant problem to my own..
I'm really scratching my head here because it is all stock TWRP and Android or should be by now. adb commands aren't connecting due to stock android not having USB debugging enabled, and without being able to boot into the settings I can do nothing to change that. So all I have is fastboot. I also have a TWRP backup image I made before installing PA but till now Ive seen no way to restore it without booting into recovery.
Any help please!!!! This can't be bricked!!
Click to expand...
Click to collapse
Welcome to XDA!
May I know what fw version did you initially start with? .575 or .291 or any others?
iXaidyiu said:
Welcome to XDA!
May I know what fw version did you initially start with? .575 or .291 or any others?
Click to expand...
Click to collapse
Hi iXaidyiu,
I started with .291. i stopped going back to it after the first time as I noticed that the custom recovery stopped working in .291. I have had it at .575 since then. And of course now that I can't get into recovery .291 is not an option unless I find an ftf of it for flashtool.
Another observation I forgot to mention is that I cannot turn the thing off. I have to force quit it (vol up + power) and after a second it boots up again to get stuck at Sony screen. I have noticed that if I do the flash boot buttons (vol down + power) I get a different Sony screen (without the xperia logo). But it sticks just the same. I don't even know if the phone is charging at this point, although it was on the Sony screen all night so there must be some charging happening. How could this have gotten so screwed up? It was working fine and I was doing benign activities at the time it choked
epeace said:
Hi iXaidyiu,
I started with .291. i stopped going back to it after the first time as I noticed that the custom recovery stopped working in .291. I have had it at .575 since then. And of course now that I can't get into recovery .291 is not an option unless I find an ftf of it for flashtool.
Another observation I forgot to mention is that I cannot turn the thing off. I have to force quit it (vol up + power) and after a second it boots up again to get stuck at Sony screen. I have noticed that if I do the flash boot buttons (vol down + power) I get a different Sony screen (without the xperia logo). But it sticks just the same. I don't even know if the phone is charging at this point, although it was on the Sony screen all night so there must be some charging happening. How could this have gotten so screwed up? It was working fine and I was doing benign activities at the time it choked
Click to expand...
Click to collapse
Well if so, let's just start from scratch, because you seems to have screwed quite badly and complicated.
Firstly, flash .291 firmware with the three boxes under "Wipes:" ALL CHECKED, check also "AUTO_BOOT" on the right column. These steps will return your device into factory state.
After the flashing process has finished, if your device turned on automatically, turn it off, then unplug the device and replug it when pressing vol+ key, this will enter fastboot mode, you can have two ways to follow now:
(1) Select "Flash", "Fastboot Mode", "Select kernel to flash", navigate to the directory that contain the kernel downloaded (I personally recommand Elite Kernel and extracted), then flash the .IMG file;
(2) Open a cmd using shift+R mouse on the blank space in the directory that stores your twrp.IMG (you can download it here), and type in:
Code:
fastboot flash recovery <filename>.img
and press Enter.
In both method, after you have pressed Enter and see there are two "Okay" printed in the CLI, unplug your device and boot it.
During boot, you will see yellow or green LED light blinked, press vol+ button once and hurray, you will be booted into TWRP recovery!
Now you can load your zip onto your SD card and start flashing! Happy flashing!
P's1 When you tried to boot up your device with the vol- button pressed together, you will be booted into SAFE_MODE, in this mode all 3rd party applications will be disabled.
P's2 I personally DO NOT recommend you to flash zip or erase anything using fastboot commands, use TWRP instead
Thank you iXaidyiu. Option 1, although it fails to boot normally, was successful in getting me back into recovery! Now that I'm in recovery, I first tried to restore my back up. But this failed with errors:
Code:
Failed to mount '/system' (Invalid Argument)
Failed to mount '/data' (Invalid Argument)
Failed to mount '/cache' (Invalid Argument)
So then I tried to flash PA again (since that was the only rom I had on my sd card right now) which also failed with the same errors plus new ones:
Code:
Failed to mount '/data' (Invalid Argument)
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Download/pa_sirius-6.0.3-20160809-signed.zip'
It also said that "This package is for "sirius" devices; this is a "".". Apparently my Z2 is no longer identifying as 'sirius'. I checked the file system, and I can see that the /data, /cache, and /system folders are physically there. Why are they not mounting? Permissions? :s What to do from here?
UPDATE: This "Failed to mount /data error" seemed to be the root of all the problems till now. Others on the net with this error also see boot hanging at the mfr logo. However, I was able to solve it by formatting /data. I still couldn't flash PA due to the 'This package is for "sirius" devices' error, but I was able to restore my TWRP backup, which then solved the "sirius" ID issue, after which I could flash PA just fine! Thanks iXaidyiu for your help in getting me back into recovery! That was clutch to me finding the solution!
@epeace
If you ever face the device id issue again, unzip the ROM, navigate down /META-INF/com/Google/Android/updater-script and delete the following line:
Code:
getprop("ro.product.device") == "sirius" ||
abort("E3004: This package is for \"sirius\" devices; this is a \"" +
getprop("ro.product.device") + "\".");
(probably the first of the code till a semi-colon)
This disable the Device ID check when you flash the ROM.
P's May I know how's your phone charging status? I am curious cuz' I once tried flashing PA 6.0.3 and all working good EXCEPT the battery cannot be charged. It keeps draining itself even though it can sense the presence of the charger but it still cannot charge:crying:
Ok great tip, I'll make that edit for next time. Re: the charging, I think it's charging, but it's definitely charging very slow. But a number of things could be contributing to that, I'm constantly on it right now (setting it up), i'm charging off of my computer (usually slow to begin with), and this phone is a few years old so the battery is not what it used to be. I'll keep an eye on it the next days, and report back here and let you know what I've observed. Thanks again for your help!
iXaidyiu said:
@epeace
P's May I know how's your phone charging status? I am curious cuz' I once tried flashing PA 6.0.3 and all working good EXCEPT the battery cannot be charged. It keeps draining itself even though it can sense the presence of the charger but it still cannot charge:crying:
Click to expand...
Click to collapse
Hey @iXaidyiu,
I no longer have PA installed, but in the couple days with it I didn't notice any difference in battery performance compared to other ROMs. I think that shouldn't be a deterrent. At the moment I'm trying out GarvityBox on rcstar6696's vanilla MM/Nougat. So far it feels right, although rooting was a little tricky for some reason. We'll see how that goes!
Hello. My name is ford, i have a galaxy grand prime with no current OS on it. this is because i was attempting to install a custom ROM onto said phone and the video i had watched, had me go into twrp, (which i had installed previously) and wipe the internal storage. ( i had used odin to flash onto the phone). I then god a custom rom, lineage os i believe, and attempted to install with twrp, but a good 75 % of the way through, no matter what, the phone would reboot. this happened with multiple roms i had tried, all ending with the same result, with the phone still having no os. i then thought that it might work with cwm instead. so from there, i had installed cwm, also with odin, with twrp still installed. i figured cwm would go ahead and either become the default cstom recovery, or it would just replace twrp altogether, but then after i had rebooted and put in the key combination for the custom recovery, it would still show the text in the top left for twrp, but then the screen goes black. I had turned the phone on and off multiple times with the same result every time. i don't know this is because the phone may be confused as to which recovery to boot into, or some other alternative reason, but it will not boot into anything now, just a black screen. I still know the phone is on, because it is noticeably lit, like it is just displaying a black screen. Now to the reason for my post, (if that wasn't enough), i then just tried installing my roms with odin. and no, there is nothing wrong with the roms, as they are all tar, and are all valid, but whenever i attempt to flash any rom, the little debug will say "file analysis" and then a second later crash. (by crash i mean windows will has it has stopped working). As i have said this has happened with all roms. It doesnt matter what order i do the steps in (plug in phone, then load files; load files, then plug in phone etc...), and i have reinstalled the c++ redistributable to make sure i have all of the dll's, but absolutely nothing is working. and no it is not because of the versions of odin, because i have tried multiple. So honestly im just aggravated now. Am i just stuck with a phone with no os now, or what? Seriously will try anything. PLEASE HELP