Hi all,
I have a standard s6 with stock EE (UK) firmware 6.0.1 installed (non rooted) . The other day I put it in UPSM mode. But soon after, the phone just restarted and now just gets stuck on the Samsung logo screen. If left long enough, the phone vibrates once.
I can get in to both recovery and 'download' mode. Tried wipe cache and flashing the same firmware using odin. Odin goes through successfully but the device still gets stuck at the same place.
The main thing is that I need to get the data off the phone. Any ideas how I can do this,( I don't think USB debugging or developer mode were/are enabled) ? Or indeed remedy the boot loop?
Thanks
Any advice on this folks?
If anyone knows of a way I can recover the data at least, whilst the phone is in this state, would be appreciated. The only thing I have not tried yet is a factory reset from recovery (because of data loss). If I am able to recover the data and then a factory reset fails, I am still under warranty so that should not be an issue.
Thanks in advanced.
Hi, I recently tried to root my Samsung S7 Active G891A. I download something that was supposed to "root" my phone and installed it via Odin. After the install it said complete and I tried to boot up my Phone and it wouldn't boot up. It was go to the screen where its says "Samsung S7 Active" then the screen would go dark and it would replay again. I've tried reseting my cache and Factory Reseting everything but that doesn't work via recovery mode. Im guessing my original firmware is corrupted but I dont know how to go about fixing that. Can some please help me?
LuckyWolf16 said:
Hi, I recently tried to root my Samsung S7 Active G891A. I download something that was supposed to "root" my phone and installed it via Odin. After the install it said complete and I tried to boot up my Phone and it wouldn't boot up. It was go to the screen where its says "Samsung S7 Active" then the screen would go dark and it would replay again. I've tried reseting my cache and Factory Reseting everything but that doesn't work via recovery mode. Im guessing my original firmware is corrupted but I dont know how to go about fixing that. Can some please help me?
Click to expand...
Click to collapse
Greetings and welcome to assist. Is this the guide you used to root your phone ? If you hsve flashed the wrong files with odin that is probably the issue. The easiest way to make your phone boot is with smartswitch emergency firmware recovery
Good Luck
Sawdoctor
So i've had a rough couple of days with my S7. It all started when I used fdisk on /dev/block/sda thinking it was my usb. The phone froze and so it rebooted it, i would bring me directly to the download screen where i was able to install twrp.
Then I had problems with the /efs/ folder mounting, and like a noodle, i wiped it without a backup. So once i booted the phone. I had no service provider. I spent all day trying to figure that out.
Next I tried to install my stock firmware which always worked in the past. At this point i kept getting "dm-verifty" errors. TWRP bypassed it so i tried to flash it again, only to notice FRP lock was turned on on it's own. So let me sum it up.
I can't boot with stock firmware, i tried multiple all leading to "dm-verity error" "No DRK"
I can't install TWRP because FRP is ON.
Even if i figure this out, i have to deal with my imei and efs problems after. I read about Combination but Odin seems to refuse it.
I haven't even had the phone for a month so I may be able to return it but i doubt it because my void is 1 (0x500), which looks bad so.. :laugh:
If anyone can help me i would greatly appreciate it, thanks in advance.
I'm really hoping you guys can help me out here. This is an S7 I bought from a Best Buy when I visited the US in 2017, and I got the Unlocked version so I would be able to use it back in my home country. Unfortunately, this is the second time I've had trouble with it in a span of 4 months and the first time it was a hardware problem and ended up quite expensive to get fixed.
Today I was using my phone normally when I decided to use the Google instant translation to translate something on my computer screen. That caused my phone to freeze, restart, and then tell me I was using an unauthorized flash and it was going to be locked, or something like that. Even after restarting a few more times, the phone would never get past that screen. I proceeded to factory reset/cache reset and from then on the phone just got stuck in a boot loop.
I learned that the fix would be to flash the phone. After a lot of work I found the G930UUESACSI1-20190930144640 firmware (the XAA version, for Unlocked) and successfully used Odin 3.13 at the Download Mode screen to flash my phone. It then restarted, went back to the blue screen, started installing some updates, when it was 100% it restarted again. Unfortunately, the loop remained. Galaxy S7 logo first, then the Samsung logo, then it just repeats.
I have also tried turning the phone off with the Recovery screen shut down option (since I can't seem to be able to turn it off with the power button right now), wait a few minutes, then turn it back on. Nothing changed.
Please, does anyone have any insight into this? What else could I possibly try, or what could I be doing wrong? I really don't want to send it to repair yet again in such a short time.
Many thanks in advance.
gabeblack said:
I'm really hoping you guys can help me out here. This is an S7 I bought from a Best Buy when I visited the US in 2017, and I got the Unlocked version so I would be able to use it back in my home country. Unfortunately, this is the second time I've had trouble with it in a span of 4 months and the first time it was a hardware problem and ended up quite expensive to get fixed.
Today I was using my phone normally when I decided to use the Google instant translation to translate something on my computer screen. That caused my phone to freeze, restart, and then tell me I was using an unauthorized flash and it was going to be locked, or something like that. Even after restarting a few more times, the phone would never get past that screen. I proceeded to factory reset/cache reset and from then on the phone just got stuck in a boot loop.
I learned that the fix would be to flash the phone. After a lot of work I found the G930UUESACSI1-20190930144640 firmware (the XAA version, for Unlocked) and successfully used Odin 3.13 at the Download Mode screen to flash my phone. It then restarted, went back to the blue screen, started installing some updates, when it was 100% it restarted again. Unfortunately, the loop remained. Galaxy S7 logo first, then the Samsung logo, then it just repeats.
I have also tried turning the phone off with the Recovery screen shut down option (since I can't seem to be able to turn it off with the power button right now), wait a few minutes, then turn it back on. Nothing changed.
Please, does anyone have any insight into this? What else could I possibly try, or what could I be doing wrong? I really don't want to send it to repair yet again in such a short time.
Many thanks in advance.
Click to expand...
Click to collapse
You need to clear the cache after flashing to get out of the boot loop.
Use the download key combo to restart. As soon as the screen goes black move to Volume up+home+power.
In the recovery menu choose clear/ Wipe cache, then choose reboot.
I apologize for not updating this thread before when it was still recent. The fact is that I didn't manage to fix my phone; clearing the cache after flashing did nothing to stop the loop.
I ended up taking the phone to the people who have fixed it in the past and after more than one month, they gave up. So I got my phone back and I want to try to give it another go before I just sell it for parts.
Unfortunately, my phone has come back even worse. Now it has no Recovery Menu to speak of, at least none that I can access; after a few seconds of the blue text on the top saying that it's entering recovery mode, it then proceeds to a blue screen saying: "Security Error: This phone has been flashed with unauthorized software and is locked.". I can still access Download Mode.
I have attempted flashing a few firmwares that I believe should have worked with my SM-G930U. Odin listed the attempts as "pass" and, after restarting and going back to the Download screen, it says the binary is Official. However, after trying to restart the phone normally, it starts displaying the blue screen again, and then, after going to Download mode, the binary is reverted to "Custom".
I believe right now the order of the day is to get the recovery menu to work again so I can do all the cache cleaning that seems to be required after flashing firmware. Any ideas at all on how I should proceed? Is there something specific I should download to fix the recovery menu?
How many files are you flashing in Odin, is it just 1 file in the AP slot, or 4 files: AP, BL, etc.? Also, is your phone rooted?
Drunkpilot said:
How many files are you flashing in Odin, is it just 1 file in the AP slot, or 4 files: AP, BL, etc.? Also, is your phone rooted?
Click to expand...
Click to collapse
Never rooted, was using the phone legit before it froze and entered boot loop. I flashed all 4 files, multiple times.
Someone tried fixing my phone a few days after I replied to this thread and some progress seems to have been made, but now the phone cannot get past a black screen with a "SBL Error! rdx_init!" in red text, and "upload mode" in yellow text. Still cannot access Recovery Mode, but Download Mode still works.
I did a little Googling on rdx_init errors and it seems I need a firmware dump from another G930U or something like that...any ideas on how I can proceed?
Flash it with Eng Boot in all slots using patched Odin. Reboot to recovery and wipe it. Reboot system. Then root it with advanced adb root. Links for all of this are here in xda. Enjoy
STA1NL3SS said:
Flash it with Eng Boot in all slots using patched Odin. Reboot to recovery and wipe it. Reboot system. Then root it with advanced adb root. Links for all of this are here in xda. Enjoy
Click to expand...
Click to collapse
Sorry, I'm not an expert at this by any means, I'm not sure what files to get. So far I've found and downloaded the following:
S7_Oreo_Nougat_Adb_Advanced_Root_V10
S7_Oreo_Nougat_Adb_Advanced_Root_V12
S7_Oreo_Su_Binary_Only_ADB_Root
But I had no luck flashing any of these cause my binary is 10. Is there any more help you can provide me? I really don't know how to proceed
gabeblack said:
Sorry, I'm not an expert at this by any means, I'm not sure what files to get. So far I've found and downloaded the following:
S7_Oreo_Nougat_Adb_Advanced_Root_V10
S7_Oreo_Nougat_Adb_Advanced_Root_V12
S7_Oreo_Su_Binary_Only_ADB_Root
But I had no luck flashing any of these cause my binary is 10. Is there any more help you can provide me? I really don't know how to proceed
Click to expand...
Click to collapse
I thought I had one in my phone, but I don't. If you look at the thread where you downloaded the Root_V12, you will see it. It's near the end of the thread somewhere.
Okay. I was messing around with my firmware which I've done in the past. I've had a few problems then due to my phone model being obscure (Samsung Galaxy S6: SM-S906L). I've always had a copy of the firmware saved to my computer in the event of a bootloop or a similar issue, I figured I could just flash it with Odin to fix it. I have also done this in the past. After accidently wiping my phone, I went to re-install Magisk, but noticed my phone trying to push an update. I let it go through without much though and after it finished saw it didn't change much. I carried on with re-installing Magisk when I figured I might as well fix some problems I had with booting the phone (I would have to boot it into download mode then recovery to get it out of a bootloop each time I turned it off). I carried on with flashing my saved firmware to fix the problem. Everything flashed fine except the bootloader. It's come to my understanding now that because I let the update carry through with my phone, my saved firmware is no longer compatiable dispite the fact that it didn't change my android version. So now I have a bootloader installed that is meant for a higher update without my known ability to downgrade. Due to the obscurity of my phone model, I can't find anything to bring my firmware up to what my bootloader is at. So now my phone is stuck in a bootloop with the ability to access download mode, but recovery mode simply gives me a "recovery is not seandroid enforcing" error. I would greatly appreciate it if someone has any advise they could give me.