So I went to restart my rooted galaxy s6(pingpong root) and I ended up with a boot loop. Phone goes to black screen after the samsung logo and the blue light is solidly on. I was able to get into recovery, wipe the cache, factory restore, and it still failed to progress past boot screen followed by the black screen with blue led. It eventually started randomly one time out and I was able to set up the phone. Somehow I accidentally clicked the update to 5.1.1 and it went to restart and I think it said that the update failed presumably bc Im rooted and then went back into the same boot-loop only this time I cant no longer get to recovery. I used odin to flash my firmware (G920VVRU1AOE2) 5.0.2 as I have done successfully in the past and It went through all the steps successfully. When It went to restart the phone it continues to go to black screen with blue led. I tried 4 more times( all successful) to reflash the firmware with the same results. I can get to the screen before recovery with safe mode, pwr down, wipe data, etc. and all of the options produce the same results as above. I called verizon and acted completely oblivious and they are sending me a new phone but It still shows up as Custom with the unlocked icon on my boot screen. Does anyone have any ideas how to unbrick or relock the bootloader so I dont have to send my device in like this.
Also, when I plug in the phone my computer recognizes that a device is plugged in but it is not recognized and I cannot view the sd card, however it still connects to odin surprisingly
Sounds like you might have updated to of1 which there is not a 5.1.1 for a Verizon s6 by the way. If that was the case and it installed of1 firmware you will only be able to Odin of1 you won't be able to go back. Which leads me to believe why you are getting anywhere with the oe2 files.
Sent from my SM-G920V using Tapatalk
Also try smart switch. It has recovery programs for if a phone is bricked.
Sent from my SM-G920V using XDA Free mobile app
The boot loop is leading me to believe there is a mismatch between stock rom and firmware, as MrWicked1 stated above. If you try re-flashing OE2 tar in the AP slot and OE2 firmware in the CSC slot of ODIN, you should be able to get back to the homescreen. Unless you mistakenly flashed OF1 as I did 2 weeks ago. I bricked my new phone today, after installing a wonky app, re-flashed the phone with OE2 and rooted. Afterwards, I deleted system/app/sdm.apk, system/app/securitylogagent.apk and system/priv-app/spdclient.apk to prevent the of1 OTA .
So should I try to OE2 first and if that doesn't work try flashing OF1 in the AP slot?
And of1 modem from of1, if oe2 doesn't work.
I got both the tar files for of1 and oe2, but the oe2 firmware file I downloaded is not an md5 its just a folder. Can you point me to the md5 for that. And where can I find the of1 modem file and where/how do I flash that in odin if need be.
http://forum.xda-developers.com/verizon-galaxy-s6/general/verizon-s6-stock-restore-files-t3096000[/url]
this is the link that I used to download the aforementioned files
Hi, do u solved it? had the same issue but cellphones was running 5.1.1
Related
i have not used my phone in any wrong way. i did not install a custom rom or anything. no root. randomly in my evedy day normal usage of my phone, it started to restart. and the the problem got worse and worse. for a few minutes, i will be able to use my phone but then my phone will restart and be stuck restarting. most of the times i cant even go into recovery mode. it restarts again when i get to that. i already reseted my phone, and i wiped the partition.
i have a samsung galaxy s6 SM-G920W8 telus/koodo 32 gb. i got the battery replaced by samsung but that didnt work. i noticed that after a few hours, my phone stops restarting when it reaches to 10% battery life.
WHAT DO I DO?? YOU GUYS ARE THE PHONE EXPERTS!!
You might want to try re-flashing the firmware. If that doesn't fix it, then you probably have a faulty device.
i tried reflashing but now i got "there has been an error updating the softawre. please use smart switch to recover" or something like that. and my phone is not supported by smart switch..... and when ever i try using odin, i always get NAND write error.i have a telus locked phone, 5.0.2 or 5.1.1 firmware. it is the latest odin and i have the drivers and i tried several solutions but that didnt help with the NAND write error.
Jaadi said:
i tried reflashing but now i got "there has been an error updating the softawre. please use smart switch to recover" or something like that. and my phone is not supported by smart switch..... and when ever i try using odin, i always get NAND write error.i have a telus locked phone, 5.0.2 or 5.1.1 firmware. it is the latest odin and i have the drivers and i tried several solutions but that didnt help with the NAND write error.
Click to expand...
Click to collapse
Have you tried the original LATEST firmware from SamMobile? Using the original cable? The latest version of Odin?
Immoblize said:
Have you tried the original LATEST firmware from SamMobile? Using the original cable? The latest version of Odin?
Click to expand...
Click to collapse
latest telus/koodo version i can find for my galaxy s6 SM-G920w8 is 5.0.2. i only use my origional usb cable. i always get nand write error. my version is 3.10.7 of odin.
phone: SM-G920WZKATLS
locked to: telus/koodo
firmware: 5.0.2
i tried a 5.1.1 update too but that didnt work. i tried a rogers one but i still got nand write failure. on my s6, it says "
system rev. check fail device: 2 binary 1"
Ok...make sure you enable developer options...and enable OEM unlock....also go to security settings and make sure Reactivation lock is disabled or unchecked. ..then try flashing the firmware and it should go through just fine
Sent from my SM-N910G using Tapatalk
i managed to flash a rogers firmware using the samfirm software but my phone is still restarting multiple times
My sister had a Galaxy S4 that would randomly reboot once in a while. Over time it became more frequent until it would barely finish booting before it would restart. Eventually it stopped turning on altogether.
Before it died completely, I tried different firmware versions and three different batteries and no change. I even took out the motherboard and put it in another S4 and it still wouldn't boot. Put the other S4's motherboard into the broken phone and it worked just fine. So it was something on the motherboard that died.
Sounds like a similar issue with your S6. Fact is, if a full wipe and firmware flash doesn't fix it, it's a hardware issue and there's nothing we can do.
Okay,so i've had twrp and root, since the day twrp came out. Everything is great..
Today, i was using the phone, and it had 1% left, and the phone turned off.
I get to my charger, i plugged it in, and samsung s8+ logo turns up, then a red text in top right corner appears "Custom binary blocked by frp lock", then the phone would turn off, turn on, and same thing happens.
I've been reading around, and seems like i have to reflash stock firmware, but that would delete data :/? Any way to keep data instead of starting from scratch?
Got a 955F
Dang it, I flashed stock firmware with odin as i've read around that odin doesnt wipe everything, but it dirty flashes.
Apparently not. Everything got wiped :/
XabdullahX said:
Dang it, I flashed stock firmware with odin as i've read around that odin doesnt wipe everything, but it dirty flashes.
Apparently not. Everything got wiped :/
Click to expand...
Click to collapse
I tried to relock the bootloader after rooting mine yesterday and had the same thing happen. I flashed stock with Odin and then rerooted which was all good. I believe when you are flashing there are 2 csc files, if you flash home_csc it should not wipe your data (I chose to wipe mine and start fresh anyway).
I have almost all the threads open on this forum with getting resolving the issue.
I woke up last week only to find the phone continually rebooting.
I ordered a new battery - same issue
did factory reset - same issue
did wiped cache - same issue
downloaded sprint firmware and installed via Odin - same issue.
I bought this phone less than a month, although used. Its extremely frustrating.
Any help will be appreciated.
Hi, did u do something?
I also have this note when I do restore by Odin I see only logo Samsung (on top info "recovery boot" when I go to recovery info "no command" and boot loop.
I had the same problem with SM-N915P model, and here are a few steps that I did to pass the bootloop.
- Download this PIT file : https://mega.nz/#!RZEzQSwR
- Open software you prefer to flash ROMs (ODIN, Z3X)
- Select the pit file.
- Check Re-Partition option, Auto-reboot, F. Reset Time.
- Add stock ROM files (Try to install the last ROM that it worked for you. ).
- Flash it.
Best regards.
Do you have the decryption key? Has anyone else tried this option?
Same issue with the latest stock firmware from sammobile, I put it down, came back five minutes later, locked on Sprint's LTE screen. I tried to restore from my TWRP backup, factory reset, reflash the firmware in Odin (that fails for some reason). I managed to get it to "Welcome to your new device, preparing your phone, this may take 3 or 4 minutes" or whatever it says, then >poof!< it reboots.
Does anyone have any ideas for this? I'm stumped. It does have TWRP recovery on it, so there's that.
rush242 said:
Do you have the decryption key? Has anyone else tried this option?
Same issue with the latest stock firmware from sammobile, I put it down, came back five minutes later, locked on Sprint's LTE screen. I tried to restore from my TWRP backup, factory reset, reflash the firmware in Odin (that fails for some reason). I managed to get it to "Welcome to your new device, preparing your phone, this may take 3 or 4 minutes" or whatever it says, then >poof!< it reboots.
Does anyone have any ideas for this? I'm stumped. It does have TWRP recovery on it, so there's that.
Click to expand...
Click to collapse
Try again please.
https://mega.nz/#!lAMEXaCA
Decryption key: !I_kcR8cv4aXpdGQ0uQf8nnMUliDdVgI8bjzX2V4g9TQ
This process has been tested.
See the image.
After all those steps, I've unlock it with idoneapps.com instructions..
Best regards. View attachment 4521231
Sent from my LG-LS993 using Tapatalk
Thank you, very much!
Let's see what happens....
Has anyone got any ideas here, my S10+ was stolen last night, so I'm frantically trying to get this edge back in working order.
I've gotten it to the stage with the gears on the screen and "Android is upgrading apps" or something similar, with x out of XX apps being updated; however, it still reboots and won't get past that stage.
I've tried Odin 3.09 and 3.13, with the .pit and without and the attached picture is where I land "FAIL."
Any suggestions, threads, ideas?
Thank you in advance.
...aaaand I fixed it.
Thanks anyway!
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.
Alright, here's the situation I'm in. My friend's WiFi wasn't turning on so I first thing I did was reset the network settings to factory defaults which didn't help.
Next, I upgraded his OS OTA through settings pane, again no cigar. I then went to check if BT was working and it did turn on with no problem, or so I thought. Despite it being on, it wasn't seeing any BT devices I could see with my own phone and PC.
As a last resort I backed up his phone with Smart Switch and went for a factory reset. Boy, was that a big mistake. You see, when the phone went through the resetting motions, it got stuck in a bootloop. First the Samsung J4+, secured by Knox screen would show up followed by Samsung logo which would run for few seconds and then the phone would reboot.
What I tried next was going to recovery mode by pressing Volume up + power button. There I went to clear cache and once again rebooted the phone to no avail. Same thing happened again.
Next I tried doing factory reset through recovery mode, again same thing.
After that I went to download latest firmware from sammobile with correct CSC and flashed it with Odin with no problem. The problem was though that the bootloop persisted through fw flash.
Next, I found PIT file for the phone and loaded it up in Odin so I could check NAND Erase and Repartition options alongside loading up all the firmware files. This went smoothly, flash was erased and reformatted/repartitioned, Odin did its thing, firmware was loaded up to the phone, but again, bootloop persisted.
I drained the battery by letting it loop until it died, charged it back but that didn't help either. I also tried flashing several different CSC firmwares to no avail. Tried all 3 available firmware versions with binary counter of 6 (BTG1, BTE1 and BRB3).
Video at x7 speed: streamable com/uhyzpm
Unfortunately, I didn't have the presence of mind to enable OEM unlock before doing the factory reset so loading the phone with TWRP is not an option. I can't even load older versions of stock firmware either because the binary check fails. Am I SOL on this one?