So, when I waked up this morning I found my S3 turned off. Nothing to worry about, I thought, since I use SlimKat+Googy it had already happened sometimes in the past that phone auto-reboots or something.
However, when I tried to turn it on I was just stuck in the bootscreen "Galaxy S III etc", but NOT in a bootloop, just stuck, the slimkat animation never start. I can enter recovery and all.
So I tought "whatever, i'll just wipe". So I did, full wipe and reinstall of SlimKat, just to be greeted again by the same problem. I repeated some times and same thing.
Trying to adb shell it says "- exec '/system/bin/sh' failed: No such file or directory (2) -" and I can't enter shell.
At this point I was totally WTF, starting to fear the worst. Just now I'm downloading a stock rom to make a last try with it. However I would like to know if someone else had this problem and if they solved it.
Anyone?
matrixino said:
So, when I waked up this morning I found my S3 turned off. Nothing to worry about, I thought, since I use SlimKat+Googy it had already happened sometimes in the past that phone auto-reboots or something.
However, when I tried to turn it on I was just stuck in the bootscreen "Galaxy S III etc", but NOT in a bootloop, just stuck, the slimkat animation never start. I can enter recovery and all.
So I tought "whatever, i'll just wipe". So I did, full wipe and reinstall of SlimKat, just to be greeted again by the same problem. I repeated some times and same thing.
Trying to adb shell it says "- exec '/system/bin/sh' failed: No such file or directory (2) -" and I can't enter shell.
At this point I was totally WTF, starting to fear the worst. Just now I'm downloading a stock rom to make a last try with it. However I would like to know if someone else had this problem and if they solved it.
Anyone?
Click to expand...
Click to collapse
Flash stock rom with Odin... that should fix your problem.
AbhiLP said:
Flash stock rom with Odin... that should fix your problem.
Click to expand...
Click to collapse
Yup, I was waiting for the download to finish. It indeed worked, but I have some yellow debug text on screen. I did a search and seems related to efs corruption or something like that. However I'm now trying to go back to slimkat from here. Now I'm less scared anyway
Ok, now I'm scared again. I get no signal. Nor with stock or custom. Also tried to restore a nandroid and nothing.
Update: I luckily found an EFS backup in the lost+found folder. Thanks god. All working now.
Related
Im going to lose my mind! I've searched and read and found no real answer..... Is there anyway that I can get my phone out of the boot screen?
Ive downloaded and rooted before and never had a prblm! I download this certain Rom Lastnight and all of a sudden my phone is stuck on the boot screen! I've tried everything i can with it and no luck. Does anyone have some type of info on what i can do or is there no hope for my poor lil droid?
Please let me know!
Thanx in advance!
Have you tried a battery pull? Pop that out and back in, reboot into recovery and restore your nandroid back up. Should be fine from there...
What I do when this happens to me is pull the battery, wipe my phone, re-apply the rom, then reboot.
-If that does not work, then revert back to your nand backup.
Thanks for the ideas but I tried both of those actions first and got nothing in return. This sukks! I even tried to go back and load the PB00img zip tha i had and no go. I'm guessing that i Bricked this dam Phone!
Back to the Blackberry! Damn!
Do you think its possible that i can load a new Rom and try to boot the phone into recovery and flash that zip? The problem seems to be my boot screen! I've seen post with people with similar "situations" <--------lol (not From Jersey shore) and tried those methods and once again nothing.
Sucks that you are still having this issue. The next step I can think of would be if you have SDK set up then once it is stuck on the boot screen, run a logcat and post it here so someone that is smarter than I can figure out where you are running into problems at. You'll need to navigate to your SDK/tools folder (in the Command window of course...) and then once there just type in: adb logcat .
This will result in a myriad of crazy computer language stuff. Should be able to tell us something at least.
First, take a deep breath; your phone is not bricked. Far from it in fact.
Second, prove to yourself that it isn't bricked by booting it into the custom recovery:
Power it off, and then hold down Vol-Up (first) and the End (second); keep pressing both buttons until the three skating droids have appeared. The custom recovery menu should pop up about 10-12 seconds after that.
Third, download "some other certain ROM" (I get to be as vague as you are, right?) to your PC, and get it to the root folder of your SD card somehow. Look up "USB-MS toggle Amon_RA" if you don't already know what that is.
Fourth, flash that "some other certain ROM" and prove to yourself that your phone is not bricked, making sure that you perform a "Wipe data/factory reset" first before you flash the ROM.
Then, after you've shown yourself how it is possible to do these steps, go back and try to figure out why the other "certain ROM" doesn't work on it's first boot. Try popping out the SD card before you boot it to see if that is the trouble.
bftb0
@es0tericcha0s, Thanks for the response but instead of doing more harm to the phone i just took it to VZW, (Kinda) Explained what happen and they switched it out no prob.
@bftb0 lol Be as Vague as possible.... I didn't want to say any particular Rom for the simple fact that who ever did the Rom i'm sure worked hard at it, And evevn tho i'm not new at this, it could very possibly be my mistake somewhere in installing it! SO I choose to respect the XDA and The Dev But thanks for your awesome response! (no Sarcasm intended) lol
I've tried to look for this problem and haven't found anything similar. If it's already been addressed please direct me to the previous thread, if this is in the wrong place please move it.
I rooted my Galaxy S II a while ago and it's been working great. I wanted to try Cyanogen mod 7 and so I followed the instructions on their website. Trying to use ROM manager gave me a weird error message telling me that there was an invalid signature or something, despite toggling everything and wiping the cache to turn it off. So I followed the "method via recovery" instructions. I did everything exactly as it is there, including the Google apps stuff, and it all seemed to work perfectly. Then I rebooted it hoping for it to boot into CM7, and instead, when it turns on it goes to the screen saying Samsung Galaxy S II with the yellow triangle underneath, and stays there. Every time it turn it on it goes to that screen and doesn't change. It's now been like that for half an hour. I can start it up into download mode, and I've tried flashing zImage to it again, but no change.
I have a NANDroid backup (it's backed up with CWM anyway), and I've copied the backup to my computer, but I have no idea how to apply it when the bloody thing won't turn on.
I'm using Linux with Heimdall (the cross-platform Odin clone).
Please help me. Unfortunately I have no internet in my flat so I won't be able to see any advice until tomorrow unless it;s given in the next ten minutes. God I really hope the thing's ok.
Hi
Do you have jigg? ( if you don't have it buy it from ebay or ask some friend of you )
With jigg you can enter download mode and then flash the stock rom.
Pull battery, wait 10s, then boot while holding power+vol-up+home. This should get you in recovery. Then restore nandroid.
Sent from my Transformer TF101 using xda premium
TheGhost1233 said:
Pull battery, wait 10s, then boot while holding power+vol-up+home. This should get you in recovery. Then restore nandroid.
Click to expand...
Click to collapse
I can't believe it was this simple, I knew power+vol-down+home got tme to downloading but I didn't know that got me into recovery. Everything's recovered now.
Thank you Dutch people!
Ok, so I wanted Ice Cream Sandwich on my Samsung Galaxy S Vibrant SGH-T959.
I found a Youtube video and eventually installed the passion ICS rom on my phone successfully. Then, I inserted my external sd card and took it back out with out unmounting it. This made my phone want to wipe all my (internal) sdcard data. So stupidly, I did. Luckily I have a recent backup. But then I did a reboot, and it said that the encryption failed and I needed to reset my phone. I complied. Then it would only go into the mod recovery screen, since I had no rom to reinstall (my sdcard wouldn't mount for some odd reason, even after I tried repeatedly). So I decided to start over. I used odin to revert it to what it came like. I unplugged it because it got stuck at cache.rfs and soft-bricked it. Luckily I know how to fix this so I got it back into odin, and I got it to work until it would have a blue reset box in the top left corner, and it said I removed my device. My phone then tried to reboot. It showed the vibrant screen, then crashed and showed the little swirl thing that it does before it shows the green charging battery, it would show that, then show that with the battery in the background, then crash and start again, never getting to the green battery. I tried unplugging it and booting it that way... it went to the vibrant screen and crashed yet again. Also can't get it to display the pink animation. I tried the odin thing again just to get the same result. I tried to boot into recovery mode and it won't even do that. It wont show the terminal thing to save its life. Any ideas? I can get it to the download screen. Any hope? (sorry for the in-depth story, but I thought it might help someone pinpoint what was wrong) I am sporting windows xp. Losing data isn't a problem for either my internal sdcard or external sdcard seeing as I have complete backups on my computer.
Thanks!
Help Please!
UPDATED!
I just tried again and it showed the terminal thing for the first time since I used odin. It will now show the green battery screen, it went into terminal and looked like it was doing stuff and it said that the data wipe failed. Boot Pattern still the same, goes to the vibrant screen and then crashes.
UPDATED YET AGAIN!
It will now go into recovery.
AND AGAIN
Now after I wiped it etc. in recovery mode and rebooted and now it just shows the vibrant screen and crashes over and over on its own.
here's a work around fix
http://forum.xda-developers.com/showthread.php?t=1580902&highlight=encryption
Not-Working Links, noncompaitibility with windows xp it doesn't restore to 2.1
So I tried that a bit ago and the pit file link to download doesn't work. So I used the default one for the vibrant. Didn't successfully run 2.1. Still same problem. Oh, and also, the whole command prompt open in that folder doesn't work on xp, only windows 7 or vista, I found a fix, but still it doesn't recognize adb as a command that is acceptable or whatever.
Thanks, but any other help?
I try Odin and when my phone shows data formatting..... it says data wipe failed afterwards. I think this is the problem.
blu422 said:
So I tried that a bit ago and the pit file link to download doesn't work. So I used the default one for the vibrant. Didn't successfully run 2.1. Still same problem. Oh, and also, the whole command prompt open in that folder doesn't work on xp, only windows 7 or vista, I found a fix, but still it doesn't recognize adb as a command that is acceptable or whatever.
Thanks, but any other help?
I try Odin and when my phone shows data formatting..... it says data wipe failed afterwards. I think this is the problem.
Click to expand...
Click to collapse
Looking back... I didn't know what adb was and now that I have the android SDK installed I'm sure I would be able to fix. Too bad I sold it for an insanely low price. Ugh.
Galaxy S3 T999 rooted and flashed more than daily.
Hi, ever since I began the install process for the Pixel Experience ROM for I9100 my S2 is in a continuous bootloop. I started from a LineageOS that was at least 6 months old because I kept the phone turned off without the battery in it for that period because I don't use, I have another phone that I use as a daily. My problem is that no matter what ROM I install it keeps bootlooping. I think I did some steps wrong at the first install of the Pixel Experience ROM but I tried like 6 or 7 times after that and I'm pretty sure I got the steps right. I even tried installing other roms with / without emulated storage with no success. As of now I have the bone stock firmware with the stock pit file and it still does not boot. It goes past the screen that says the "Samsung Galaxy SII I9100" in a screen that has a animation with the samsung logo and that is where it ends. I've tried numerous clean installs, cache wipes and all this stuff. I think good to mention is that sometimes the stock recovery says it can't mount data and efs folder and sometimes the TWRP can't mount data. I fixed all these, except the efs file thing but it does not always come up. The only thing I have't tried with success and I don't know if it works in my state is ADB but when I tried "adb shell" it came up as an error even though the phone was recognised by "adb devices" command. I even tried as a last resort the "Nand wipe" in Odin but it *fortunately I think* didn't work (literally nothing happening). I don't know what this might mean, NAND corruption maybe?! I've been messing with this for 5 days already in all my free time and I've got nowhere. If you have any ideea, no matter how crazy, I can try it and tell you how that worked out.
I got it to connect to ADB properly but I still don't know what to do. Any sugestions?
Sent from my SM-G965F using XDA Labs
I managed to fix this problem by following THIS tutorial step by step.
Long story short, stock phone just randomly blew up and I'm trying to re-install its stock Android OS. Phone has never been rooted before, it just started to reboot on its own and now I'm in a position where I can only access download mode.
I'm in Odin, with what I believe is the correct firmware for my device (SM-N950U1) and I just keep getting a "Secure Check Fail: system" when trying to flash. it via Odin. The Odin log says "FAIL! (auth) right after trying to write system.img.ext4 for a few minutes. The "Secure Check Fail: system" is the printout on the phone screen itself.
Any clues?
Bump! Anyone?
playbacktri said:
Bump! Anyone?
Click to expand...
Click to collapse
I see that you have not received an answer. That is upsetting. I am also struggling with this exact same issue on a g955u1. Have not found a solution. Did you end up solving your problem? If so, what did you have to do?
ap7x942 said:
I see that you have not received an answer. That is upsetting. I am also struggling with this exact same issue on a g955u1. Have not found a solution. Did you end up solving your problem? If so, what did you have to do?
Click to expand...
Click to collapse
Nope, I have not solved the problem. I've scoured the internet and other people asking the problem all have not had any answers either. My assumption is that the actual internal memory of the phone is corrupted and won't let me write past a certain point, or on certain sectors, or something and its not actually fixable via software. I think everyone else just stops at this point and its never resolved because there is no resolution hah.
Good luck, let me know if you ever figure it out...
playbacktri said:
Nope, I have not solved the problem. I've scoured the internet and other people asking the problem all have not had any answers either. My assumption is that the actual internal memory of the phone is corrupted and won't let me write past a certain point, or on certain sectors, or something and its not actually fixable via software. I think everyone else just stops at this point and its never resolved because there is no resolution hah.
Good luck, let me know if you ever figure it out...
Click to expand...
Click to collapse
This phone I am working on is for a customer of mine. Thankfully, they have given me an open ended time frame. I have been working on this for about a week trying to figure out whats going on.
The memory corruption thing you were talking about resonates with me, because prior to my customer bringing this in, they had attempted a couple factory resets trying to resolve the original issue which was all the system apps crashing. The phone would reboot like someone killed all the processes. Pretty much from the moment it reached the home screen, and it was not power related. The problem persisted after their factory resets within recovery mode. And then I hit the phone with Odin and ended up with a partial flash. Soft bricking the phone.
You saying that kinda reinforces what I was already thinking, that it might be a hardware issue. Im not sure.
5 minutes ago I was able to get odin to successfully flash BL, CP, and CSC. It even brought me back to the Samsung logo for a minute but hung there. That's the most success I have had with this thing. Ive flashed numerous firmwares and every single one of them fails on system.img.ext4. After it reboots, it boots directly into this altered version of download mode with an emergency recovery error.
I have flashed dozens of phones before without issue. This is the first time I have ever experienced this one. You could be right but I refuse to accept defeat in this case lol so im gonna keep trying and ill report back if I have success.
ap7x942 said:
This phone I am working on is for a customer of mine. Thankfully, they have given me an open ended time frame. I have been working on this for about a week trying to figure out whats going on.
The memory corruption thing you were talking about resonates with me, because prior to my customer bringing this in, they had attempted a couple factory resets trying to resolve the original issue which was all the system apps crashing. The phone would reboot like someone killed all the processes. Pretty much from the moment it reached the home screen, and it was not power related. The problem persisted after their factory resets within recovery mode. And then I hit the phone with Odin and ended up with a partial flash. Soft bricking the phone.
You saying that kinda reinforces what I was already thinking, that it might be a hardware issue. Im not sure.
5 minutes ago I was able to get odin to successfully flash BL, CP, and CSC. It even brought me back to the Samsung logo for a minute but hung there. That's the most success I have had with this thing. Ive flashed numerous firmwares and every single one of them fails on system.img.ext4. After it reboots, it boots directly into this altered version of download mode with an emergency recovery error.
I have flashed dozens of phones before without issue. This is the first time I have ever experienced this one. You could be right but I refuse to accept defeat in this case lol so im gonna keep trying and ill report back if I have success.
Click to expand...
Click to collapse
Man, that sounds very very familiar to mine. I don't know if you found my other threads where I was asking for help, but I woke up with a phone that wouldn't turn on. Finally found the key button combo to get it to soft reboot, then it would turn on and just crash in the middle of using it after anywhere from 30 seconds to 5 minutes. If i started to use the phone heavily it would just shut off instantly and reboot back up on its own.
After clearing the boot cache, then doing a factory reset, it finally just stopped turning on at all (just samsung boot logo loop)
So I hit it with odin, unsuccessfully for 2-3 days, and then out of nowhere it just finally took a successful flash. However, it still just bootlooped, so I did a factory reset again and it put it back to being toast.
Since then, not a single successful complete flash from odin. I too can do the BL, CSC and CP files but I can't flash the AP file as it is writing the most data and finally fails about 3-4 minutes into to writing the system image file.
Again...good luck, ha!