Hello all!
This morning my wife tried to turn on her phone (Stock GS7 Edge on Tmobile) after charging overnight- It kept cycling the Galaxy S7 Edge screen. It would then show the Samsung shutdown screen, and then re-load the Galaxy S7 Edge starting screen. It did this probably 10 times or before I went to boot into recovery mode. However, when I tried this it showed the "Recovery Mode..." screen, but then immediately went to the blue "Installing system update" screen. It says here for a second then goes back to the black "Recovery booting...". It does this back and forth at least 5 times, and then if I plug it into something eventually it changes from the system update screen to a blue screen that says "No Command".
Now, if I let it sit on this screen for a minute or so it will actually boot to Recovery mode successfully. I wiped the cache but that did nothing. I checked the logs and nothing immediately weird jumped out at me but I am not 100% sure what I would be looking for as I don't know what caused this issue. The only messages I see worth noting/present some kind of error are:
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata_path: ANDROID_DATA not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
And: error: open_script: could not open /res/recovery.customize.do No Such File or Directory
[failed start]
sales_code=[TMB]
Carrier ID=[EMPTY]
Don't Delete lib .so files
Not sure if these are normal or helpful to anyone reading. I have not yet tried anything with Odin or recovering the stock ROM or factory resetting. I was hoping there was some way to get this thing back on without losing the data but I think we are past that point. However, if anyone has anything I can try before factory resetting that may fix this it would be greatly appreciated!!!
Well. After trying repeatedly it finally decided to break out of the loop and boot normally. Totally bizarre....but I am backing up everything while I still can!
Krieger0311 said:
Well. After trying repeatedly it finally decided to break out of the loop and boot normally. Totally bizarre....but I am backing up everything while I still can!
Click to expand...
Click to collapse
what exactly did you do to "try repeatedly"??
I am stuck in a recovery loop and nothing is working.
Related
I am not exactly sure what happened, but I am stuck in the "Android system recovery <3e>" menu. I had unlocked the phone before and was trying to relock it and get it back to stock because the new update wouldn't install.
While the HTC update utility was installing the stock firmware, I think the cable came loose at some point because it stopped part way. Now it boots, shows the HTC logo, goes black and then eventually shows a phone lying down with a red triangle and an exclamation point. I can push vol+/power to get "Android system recovery" to show up, but that seems to be all. It says "Mount SDCARD failed".It will only boot to this menu. I cannot load the bootloader or anything else so I can't seem to use fastboot or adb and can't seem to copy any files onto the phone. Does anyone have any ideas? Is it totally bricked?
Edit: doing a factory reset from recovery does nothing.
Edit2: Sorry!!! False alarm. After spending about an hour going back and forth with this and finally breaking down and posting about it on XDA, suddenly the bootloader DID appear. I have absolutely no idea what I did differently. I guess the 500th try was the charm. Reflashing stock now!
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
somesortofthing said:
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
Click to expand...
Click to collapse
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
ShapesBlue said:
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
Well, can I somehow get my phone into working order? Because it's as good as bricked right now.
Hello,
I bought a new device and therefore wanted to factory-resent my Nexus 5 to give it to my wife.
I did it from within Android and then it restarted and stayed in the "Erasing..." screen for quite a while, then showed the dead robot with the "!" triangle sign, then rebooted and started "Erasing..." again, with apparently no way out.
I had unlocked bootloader and TWRP, but also booting the recovery went back into "Erasing..." mode.
I then tried to boot from an external TWRP iso image with fastboot from the PC. TWRP seemed to load, then started doing a bunch of things like formatting "something" (was too quick to read) and suddenly in a matter of second it was back to the robot but now without the "Erasing..." label anymore and now it's stuck there.
No idea what happened and how to fix and now I'm somewhat scared of trying something else.
Any idea?
Never mind... Flashed ALL stock images from fastboot (just userdata and cache didn't work) and it rebooted.
No idea what the problem was.
Hi guys, so recently I bought a Galaxy S6 Verizon off of eBay. I got it for fairly cheap because it was stuck in a boot loop. I usually have no problem fixing stuff like this, but this time is different. So the first thing I tried when I got the phone was to do a reset and cache wipe from recovery. I rebooted the phone and it showed a screen that said "Android is starting, optimizing app 9 out of 31." when it got to 21 the phone rebooted and went back to 9. It did this several times before I attempted to wipe/reset again. I then downloaded the tar file G920VVRU4CPH1 and flashed it in Odin. I did a manual reset before the phone booted, and it is doing the same thing again. reboots to a green screen where it tries to optimize apps, stays there for about 20 seconds, and reboots over and over again in the same cycle. I have tried all other stock marshmallow roms that i can find, Odin won't flash older ones, (assuming its not letting me downgrade). Also another weird thing, every time I flash, the blue update screen goes to 32%, stops, erases, and reboots. Phone is on 6.0.1 version MMB29K.G920VVRU4CPH1 as seen in recovery. Any help would be gladly appreciated. Thank you!
I am having a similar problem with loading new rom. The farthest it gets is 32%. Sometimes it doesn't get even that far.
I ended up just buying a trashed s6 and swapping the motherboards. Only way I could fix it
My father-in-law's S6 was rebooting right after the menu screen came up. After trying numerous things which wouldn't work (still had varying boot loops) like getting into the recovery mode and doing a factory wipe, I decided to use Odin and flash the base stock Android nougat on this (it had the one verizon security patch after that, so should be no issue doing this).
That went okay and it rebooted and got all the way to "Android is starting" which you see after a firmware upgrade. But I didn't realize the battery had run down through all this so it died at this stage. So it was taking a charge now, so let it charge overnight and give it another run.
Got up today, tried to start it...back to the boot loop. So I figured I'd flash stock again with Odin (can always get back to that mode).
It completes successfully and then after the reboot at about 32% jumps to "erasing" and then the boot loop again.
Got into recovery mode once and wiped cache (pointless at this point, but whatever) and did factory reset there, then boot to bootloader. Got all the way to the verizon screen...and then boot loop again.
Is this phone just done? The only thing I can consistently get to is Odin mode. I tried the stock reflash a couple more times and keep ending up in a boot loop and it doesn't even get past the "custom" screen now. And I can't even actually get it to shutdown for that matter. I can get to the battery pull mode but if I try to power off from there, I just get the black screen with the blue light.
And, to make matters even worse, now on restart, it brings up the blue system update screen for a second, then jumps over to the no command screen, sits there for a second, then reboots again. I think I've somehow managed to even blow the recovery menu but this has all been stock and never had any custom firmware or root.
Any help/suggestions would be greatly appreciated!