Hi there,
My S9+ (SM-G9650) is softbricked right now, due to a attempt on flashing the Pixel Experience ROM in it. After a few tries, using the "High on Android" tutorial for this kind of procedure, I gave up, seeing that my phone did not correctly flash it, and every time I booted it up, the Samsung logo appeared, with the opened lock with the "CUSTOM" warning below it, and the warning "Set warranty bit: kernel" on the top of the screen (or sometimes with the "Set warranty bit: Recovery" message instead, when I boot into recovery mode). I also can't seen to rid myself of TWRP, since every time I boot into recovery mode, TWRP is there.
So I wanted to undo all that I have done by flashing the stock firmware for the device through Odin 3.13.1. But I keep getting the same error message, a few seconds or a minute later the flashing process is started. It says "Complete(write) operation failed".
I am familiar with adb and fastboot, as well as flashing images to phones like Essential Phone, but I am at a loss with this one. I have tried following some tutorials, but they all say the same thing, and it is not working for my case. Btw, the name of the zip file I downloaded and tried to flash is SM-G9650_1_20180418174053_asu7y86t8u_fac.zip (oreo 8.0.0), if this information is of any help.
Any thoughts? Or advices?
Edit: fixed it already. Guess I had the wrong file
Related
I recently tried a factory reset on my phone after finding that one of my apps was sending out spam texts to random people and racking up my text plan. Upon the first boot, it showed a green android man with a blue orb thing spinning in its stomach and kept going for hours.
My phone was previously running an unofficial build of CM12 and was unlocked and rooted.
Now, I just figured that I could just flash a new recovery to the phone and flash a new ROM to get it back up and running, but I also keep having troubles getting it to flash. Using 'flashboot devices', I see my phone's serial, but when I try to use 'flashboot erase recovery' or 'flashboot flash recovery recovery.img' seems to hang up. I finally got it to write clockwork recovery to the phone somehow, but the device still boots to the green android man w/ blue instead of clockwork. I thought it was an issue, so I have been trying to flash TWRP, and it just hangs, and doesn't even give the <waiting for device> text, so I know it sees it.
Can anyone help me figure out a way to get my recovery flashed correctly? From that point, I should be good to go, as long as it loads into recovery.
Tampered
I have tried everything I can think of, and it still stalls while it is supposed to flash the new recovery, then fails with the error "too many links".
Also, now the **TAMPERED** flag pops up at the top of the bootloader. It still lets me into the FASTBOOT portion, so I don't believe that it is effecting anything, so I will probably just have to worry about that later, if I really feel like going through the whole rumrunner/revone process.
TWRP
Not sure if it is a good sign or not, but I replaced the USB cable and was able to get TWRP to install and actually load once. There were errors after it booted, and I choose to do a full factory wipe to hopefully start over fresh, and the phone rebooted itself. Now TWRP seems to endlessly load while it the splash screen flashes on and off, almost as if it is in a bootloop. I tried reflashing with a slightly older TWRP for my phone, and no luck.
Also, another strange thing is that when I flash a new recovery file, it shows that it only takes a total time of 2.607s. If feel like this is quite short and I remember it taking a bit longer in the past. I just feel like it is not writing the entire recovery, hense the blinking teamwin logo that seems to be stuck in a bootloop.
OK I screwed up. I would appreciate any help here. Rogers S6 Edge, G925W8. It was stock 5.0.2.
Wanted to try a ROM so flashed TWRP, then flashed Kingfisher ROM v1.1 (it seemed the safest / W8-friendly). ROM was fantastic (much better battery), but GPS would never lock.
Tried to start over by flashing stock Rogers 5.0.2 via Odin but it wouldn't flash. I read (a little too late) that downgrading isn't something Samsung enjoys. Argh!
Then out of desperation, I flashed the BL (BL_G925W8VLU2BOH8_5.1.1.tar) from http://forum.xda-developers.com/galaxy-s6-edge/general/canadian-odin-5-1-1-bootloader-twrp-t3196595 , which was a very bad move, I assume because I wasn't on 5.1.1 to begin with. Crap!!
So now the phone gets to the Galaxy S6 edge splash screen, with "KERNEL IS NOT SEANDROID ENFORCING", and it stays there. The phone also gets very warm, and I can't shut it off. Using VolDown+Power+Home reboots it (showing the same message) but doesn't shut it off. Using VolUp+Power+Home reboots it but only says the same thing about Recovery.
Please tell me that I didn't just brick this phone!!
UPDATE:
Am able to get the phone into Download/Odin mode by holding the 3 buttons (voldown+power+home) while plugging the phone into USB. The stock Rogers image refuses to flash (Odin says fail immediately), but I am a step closer thanks to @brar.arsh's thread ( http://forum.xda-developers.com/galaxy-s6-edge/general/canada-galaxy-s6-edge-canadian-users-t3069314 )
From there I grabbed the "S6 Edge Stock Firmware OG2" which comes in 4 parts (BL, AP, CP, and CSC). I added all 4 pieces to Odin and started flash. Boot.img and recovery flashed, but then during the system.img flash, it failed about half-way through. Right after that failure, something changed because the device now became "Unknown Device" to windows, and it complained that "a USB device has malfunctioned, and Windows no longer recognizes it".
This gave me hope that I could get into Recovery (since that flash was successful), but the phone likes to boot directly to the "The update failed so please launch Smart Switch" message - regardless of starting with VOLUP+PWR+HOME button combination. So no recovery access... but making progress.
I belive I initiated a flash that contained JUST the BL, CP, and CSC portions, and it passed quickly. This, of course, isn't enough to get the system going. I just wanted to see if it would fail in other areas.
Trying the emergency flash via Smart Switch: Smart Switch said it required the phone to be in Recovery mode, but it still attempted the fix even though I was in Odin/Download mode. Good news, but unfortunately it gave the same result - a failure at around 50% of the entire flash operation.
I have tried re-flashing the AP portion several times and it fails at different progressions (50%, 75%, 90%)... so close.
I was thinking that it was maybe a power issue (since the battery was completely dead during the "kernel is not seandroid enforcing" period, with no way to turn the phone off or pull battery), I wondered if the battery just needed a little juice before starting the operation. I let it stay plugged in for a few minutes after one of the many failed flash attempts (screen was illuminated with the progress bar frozen at the point of failure). I noticed that when I unplugged it, it didn't die immediately, so I plugged it back in (getting the "USB device has malfunctioned" message again), and forced it to restart by holding the VOLDOWN+PWR+HOME buttons). It got back into Odin mode and the PC recognized it again. Loaded up just the AP portion in Odin, hit Start, left the room, and when I came back it said PASS! I cannot prove that it had any battery power from this method... or if it even helped. This could have just been a fluke.
The phone automatically rebooted into Recovery mode (which scared me) so I hit Power Down.
Rebooted the phone - I hear the lame Samsung startup song, and it is booting. Hallelujah.
I was recently given an S6 from a friend who won it but already had one. I was excited to try and root it, foolish of me to think about maybe getting more information, and I attempted a CF-Autoroot. The root claimed, in Odin 10, to have succeeded. However, it fails to boot entirely. The grey android screen that flashes the word "erasing" as the loading bar progresses during firmware reboot makes it half way before restarting. Now I can boot into Odin mode, and I can boot into recovery. USB debugging was off at the time the phone started to act up so that's a no go. I have tried multiple times in restoring it to no avail. The phone recovery says "failed to mount /efs."
Odin mode said custom and then, after using kies to attempt a restore, would fail to complete and once again get stuck on SAMSUNG screen. If I Return to Odin mode I would notice that the system went back from custom to Samsung again, though the knox counter was still at 1.
I am able to load TWRP and occasionally manage to format and tweat partitions to mount the phone in recovery but can't transfer any files.
I have access to a USB OTG device that loads via mini usb port in the device. This phone has caused me a lot of grief and I Can't think of any way to recover it. Essentially I am left with a brand new device that is worthless. Is there anyone out there with experience recovering this error.
Also I am unable to obtain the lost emergency firmware recovery number.
Thank you in advance for all the time and efforts that I hope will be provided. I have spent many days on this device trying to simply make it work.
Regards, Desmond
Hi All
I have samsung A5 2017. When i start my phone it shows no command and it continues to restart after 1 minute.
When i try to open recovery mode i get error "fail to open recovery_cause(No such file or directory)". I have also tried combination of key power and volume up but not getting recovery mode. I think it has been deleted or something else. I am also unable to load firmware.
I also tried to install twrp with odin 3.13 but get error unable to install frp locked.
Please tell me solution how can i get back recovery mode so that i can install firmware.
Please help me for this.
Hey there,
I have a similar issue and I can see your post dates back to 2020. Have you ever found a way?
I'm very curious about solving the issue on mine (I can't reboot at all, can't even access the reboot after getting the "no command" message. If you have any clue on how you accessed reboot mode and can be kind enough to share, this would be really appreciated )
I know this is an old thread, but did you find a solution?
On an unlocked J6, after flashing the stock rom, although I can open recovery, I get the same message. The options I tried (both reboot options, both wipe options, power off) work. I went ahead and installed twrp through odin, which passed, but when I boot into recovery, it boots into samsung recovery (with the same message) and not twrp.
I'm guessing the twrp problem is related to the error message.
Hello!
This is about an old model of phone, so chances are I am in trouble.. but will describe the problem specifically.
Was a normal S4 mini without modifications - turned on USB debugging, installed Samsung Kies, and Odin, and got started on this guide: (https://forum.xda-developers.com/t/root-samsung-galaxy-s4-mini.2387341/)
Went into "download mode", ran Odin, it detected my device, installed "GT-I9195_MF5_870901_kernel.tar.md5" as PDA within Odin (all files are on the forum post linked above)
After this, device rebooted, as per the guide.. then I had trouble getting into the "download"/"recovery" environment again for some reason, and in frustration, unplugged/plugged cable, and after this didn't work, closed and reopened Odin. Now the problem is the guide explicitly says "Do not close Odin", and this is where the issue came up.
Holding volume up + power + home, takes me to "android system recovery <3e>", which I'm guessing is where I should be, but however Odin does not recognise the device now, and in fact, in this recovery environment, I don't think it's recognised by my PC even, so I guess that's why both install steps had to be done in one go... Now, my phone has options such as "reboot system now", "apply update from ADB", etc, and other stuff, but I am not able to figure out what to do next, and so as a result, the phone is just not useable for me. (blurry picture attached)
Some notable details from the blurry picture are:
"KOT49H.I9195XXUCOE4" (at the top of the screen)
"# MANUAL MODE "
--- Appling Multi-CSC...
Applied the CSC-code : KOR
Successfully applied multi-CSC." (at the bottom of the screen)
Notably if I let the phone try to boot normally, it does get detected by my PC and by odin, but if I try to install something to the device with Odin, it falls over, something to do with being unable to establish connection probably because the phone is in the wrong mode. It would not be the end of the world if the phone was bricked forever but man would I feel like ****
Update: turns out there are two different things you can boot to, via the volume up + down buttons, my stupid ass didn't clock this, so got very confused. Now was able to follow the steps in their entirety, however phone is still not booting into OS, despite now having custom recovery.
After doing some research, seems that the issue stems from this:
BOOT LOADER AP SWREV:2
Apparently REV:2 can't be flashed with anything custom, and bricks the phone, and rev:2 is what I have. Whilst this will certainly put an end to my days of referencing old forum posts for stuff like this, at the very least I have a broken S4 mini with a perfect 16 Gb motherboard I can swap out, my bro's old one, he's not too happy but understands.