Galaxy S7 was FRP binary locked so I flashed stock rom with ODIN, rom off of sammobile. Now phone is stuck in bootloop and when i try to open recovery mode it just reboots the device. What do I do?
EDIT:
Im able to flash all the rom files but BL one. It's just an infinite bootloop, I managed to do factory reset on recovery mode but no fix
Did you flash all parts of the latest stock ROM?
audit13 said:
Did you flash all parts of the latest stock ROM?
Click to expand...
Click to collapse
Yes, I searched up model # on sammobile and downloaded 2 different carrier versions of firmware too. Both instantly fail on odin
What is the Odin error?
Posting the Odin log will help to isolate the issue.
Odin problems can sometimes be solved by using a USB 2.0 port and using a different USB cable.
audit13 said:
What is the Odin error?
Posting the Odin log will help to isolate the issue.
Odin problems can sometimes be solved by using a USB 2.0 port and using a different USB cable.
Click to expand...
Click to collapse
It would instantly fail after Initialization. Anyway, I managed to get ODIN to succesfully flash but now bootloop is the issue.
the BL i was flashing from sammobil wouldn't work, found one for my model on the forums and flashed that + AP,CP,CSC from sammobile and .pit file with nand erase, repartition and everything all checked. Phone started and did system update then rebooted, now it's in a bootloop. I think everything is flashed correctly i just need a fix for loop now
HI
did u figured out your prob with boot loop
tdbtdb24 said:
did u figured out your prob with boot loop
Click to expand...
Click to collapse
no, still stuck in bootloop. I've flashed different versions of firmware still ending up with same issue
celk1 said:
It would instantly fail after Initialization. Anyway, I managed to get ODIN to succesfully flash but now bootloop is the issue.
the BL i was flashing from sammobil wouldn't work, found one for my model on the forums and flashed that + AP,CP,CSC from sammobile and .pit file with nand erase, repartition and everything all checked. Phone started and did system update then rebooted, now it's in a bootloop. I think everything is flashed correctly i just need a fix for loop now
Click to expand...
Click to collapse
You have a back up of the efs folder? The nand erase option is not something that I ever recommend using as this folder has a lot of critical information.
You tried doing a factory reset from the stock recovery?
audit13 said:
You have a back up of the efs folder? The nand erase option is not something that I ever recommend using as this folder has a lot of critical information.
You tried doing a factory reset from the stock recovery?
Click to expand...
Click to collapse
I used nand erase because anything else I tried didn't help, EFS isn't backed up. I did try to factory reset from recovery but it didn't work. Also did flash .pit file too, and used different firmware versions but they all ended up causing bootloop.
Were you trying to flash the bootloader from the latest nougat ROM?
You have a link to the bootloader you flashed to the g930w8?
audit13 said:
Were you trying to flash the bootloader from the latest nougat ROM?
You have a link to the bootloader you flashed to the g930w8?
Click to expand...
Click to collapse
I tried to flash these at first (BL failed but everything else PASS) https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/GLW/download/G930W8VLS2BQF1/173068/
and https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/XAC/download/G930W8VLS2BQF1/173063
BL worked when I flashed version posted here (G930W8):
https://forum.xda-developers.com/galaxy-s7/how-to/modem-samsung-galaxy-s7-sm-g930f-t3379596
So i searched filename on sammobile and flashed this
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/GLW/download/G930W8VLS3BRC2/212091/
That one ^ all passed when flashing in ODIN but still caused bootloop
BTW thanks for sticking around and helping
Looks like the BRC2 bootloader is the latest.
What was the error in Odin when flashing the bootloader?
Did you get a chance to try different USB cables and a USB 2.0 port for the bootloader?
audit13 said:
Looks like the BRC2 bootloader is the latest.
What was the error in Odin when flashing the bootloader?
Did you get a chance to try different USB cables and a USB 2.0 port for the bootloader?
Click to expand...
Click to collapse
I managed to fix the error when flashing bootloader, the firmware flashes succesfully now but the bootloop still occurs
celk1 said:
I managed to fix the error when flashing bootloader, the firmware flashes succesfully now but the bootloop still occurs
Click to expand...
Click to collapse
Try running Odin as administrator? It was my problem with the boot issue, I couldn't even turn off my phone because it would keep looping.
celk1 said:
I managed to fix the error when flashing bootloader, the firmware flashes succesfully now but the bootloop still occurs
Click to expand...
Click to collapse
I'm not 100% sure but I wonder if the bootloop is due to a missing EFS folder.
Can you not into recovery? If yes, does the phone say anything about the EFS folder?
audit13 said:
I'm not 100% sure but I wonder if the bootloop is due to a missing EFS folder.
Can you not into recovery? If yes, does the phone say anything about the EFS folder?
Click to expand...
Click to collapse
nothing about efs in recovery mode, only messages showing on recovery mode is: no support single-sku, supported api: 3, applied the csc-code glw, succesfully applied multi-msc, succesfully verify for dmverity hash tree.
MrPeebles said:
Try running Odin as administrator? It was my problem with the boot issue, I couldn't even turn off my phone because it would keep looping.
Click to expand...
Click to collapse
I ran odin as admin every time i flashed
I am really not sure what else to suggest Other than taking it to Samsung for repair or a cell phone shop that can force flash the ROM again using hardware such as an octopusbox. If this is not a feasible solution, maybe buy phone with a busted screen and working internals to perform a motherboard swap.
I'm guessing but the bootloop maybe be due to having frp enabled or wiping the band.
Edit: could also try a custom ROM.
audit13 said:
I am really not sure what else to suggest Other than taking it to Samsung for repair or a cell phone shop that can force flash the ROM again using hardware such as an octopusbox. If this is not a feasible solution, maybe buy phone with a busted screen and working internals to perform a motherboard swap.
I'm guessing but the bootloop maybe be due to having frp enabled or wiping the band.
Edit: could also try a custom ROM.
Click to expand...
Click to collapse
I'll try a custom ROM. I'm trying to flash TWRP to it but it's being blocked, 'custom binary blocked by FRP' shows on download mode and odin instant fails when flashing TWRP:
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
It makes sense that twrp world be blocked with frp enabled.
Did you flash home CSC or just CSC?
I'm out of ideas.
audit13 said:
It makes sense that twrp world be blocked with frp enabled.
Did you flash home CSC or just CSC?
I'm out of ideas.
Click to expand...
Click to collapse
I did CSC. Can I use ADB or something to force disable frp? Since I can't turn oem unlock through settings as it just bootloops
Related
Hi.
I am on my second day on bootloop and i'm getting crazy. I have tried almost everything. I will now try to load the modem, bootloader and pit file to Odin and see if my phone will boot up.
Any suggestions or where i can find the files?
SM.-G920F
Hi guys, I hope someone can give me a hint, because I am out of ideas.
I wasn't in a mood to wait for OTA update for my SM-G920F, so I dl-ed 6.0.1 from sammobile(G920FXXU3DPB8_G920FVFG3DPB8_MTL this one to be precise) and flashed it via ODIN. It failed at hidden.img and after reading some threads here I figured out that I need to export it, rename it to hidden.img.tar, export modem.bin and flash them manually. So I did. So it worked. I was able to boot the new firmware. Moments of happiness and joy. After day or two I found there is TWRP for marshmallow already(G920FXXU3ZOL6_TWRP this one (precisely)). And I flashed it via ODIN too. It passed everything was OK. But when I start the phone in Recovery mode it just stucks at Recovery is not seandroid enforcing. I have no idea what seems to be the problem Other than that and the fact that I can't use factory reset (for obvious reasons) the ROM seems to work fine.
ivanhar said:
Hi guys, I hope someone can give me a hint, because I am out of ideas.
I wasn't in a mood to wait for OTA update, so I dl-ed 6.0.1 from sammobile(G920FXXU3DPB8_G920FVFG3DPB8_MTL this one to be precise) and flashed it via ODIN. It failed at hidden.img and after reading some threads here I figured out that I need to export it, rename it to hidden.img.tar, export modem.bin and flash them manually. So I did. So it worked. Moments of happiness and joy. After day or two I found there is TWRP for marshmallow already(G920FXXU3ZOL6_TWRP this one (precisely)). And I flashed it via ODIN too. It passed everything was OK. But when I start the phone in Recovery mode it just stucks at Recovery is not seandroid enforcing. I have no idea what seems to be the problem
Click to expand...
Click to collapse
Sorry I can't help you, but could you explain exactly what you did to get it to work please? It always failed at hidden for me
emcardle660 said:
Sorry I can't help you, but could you explain exactly what you dont to get it to work please? It always failed at hidden for me
Click to expand...
Click to collapse
First of all install 7z. Extract the .tar file from the zip and open it with 7z. Extract hidden.img and modem.bin. Rename hidden.img to hidden.img.tar (don't add it to archive, just rename) and flash it via ODIN at AP. Reset odin, restart the phone to download mode and flash modem.bin at CP. Restart the phone and wait couple of mins. That's what worked for me.
Device: SM-920F
Build vers : 6.0.1
Status: stock kernel, no root
Issue: Can't flash SpacexKernel. Get error "<ID:0/005> Can't open the serial(COM) port."
http://imgur.com/a/QhkpH
I've done a search on XDA for this issue and I've found some with similar issues but no resolution. Example Here but this user was able to flash Space kernel.
So I'm trying to root my phone and than install TWRP recovery with the intention of flashing a custom rom. It is my understanding the 920F bootloader is unlocked by default so that should not be the issue. I'm following GalaxyS6Root guide. I downloaded the necessary files: SpaceXkernel, Odinv v3 3.10.6, TWRP 3.0 by Manh Ti. With my phone in download mode Odin recognizes my device cause the blue port (blue) lights up so I'm sure I have the right usb drivers. 'm stuck on the first step, trying to flash SpaceXkernel. I check AP, select the kernel, and hit start. Than I see error <ID:0/005> Can't open the serial(COM) port..
I've tried this several times but get the same error. I've read it can be a issue with a cable but I am using a OEM samsung cable. I've tried plugging it in several usb ports but same issue. Any ideas what i'm doing wrong or need to do?
Edit:
Plugged into a different usb port. Tried flashing Space kernel again and now I get error "<ID:0/006> Complete(Write) operation failed."
http://imgur.com/a/eRooU
Droid>iOS said:
Device: SM-920F
Build vers : 6.0.1
Status: stock kernel, no root
Issue: Can't flash SpacexKernel. Get error "<ID:0/005> Can't open the serial(COM) port."
http://imgur.com/a/QhkpH
I've done a search on XDA for this issue and I've found some with similar issues but no resolution. Example Here but this user was able to flash Space kernel.
So I'm trying to root my phone and than install TWRP recovery with the intention of flashing a custom rom. It is my understanding the 920F bootloader is unlocked by default so that should not be the issue. I'm following GalaxyS6Root guide. I downloaded the necessary files: SpaceXkernel, Odinv v3 3.10.6, TWRP 3.0 by Manh Ti. With my phone in download mode Odin recognizes my device cause the blue port (blue) lights up so I'm sure I have the right usb drivers. 'm stuck on the first step, trying to flash SpaceXkernel. I check AP, select the kernel, and hit start. Than I see error <ID:0/005> Can't open the serial(COM) port..
I've tried this several times but get the same error. I've read it can be a issue with a cable but I am using a OEM samsung cable. I've tried plugging it in several usb ports but same issue. Any ideas what i'm doing wrong or need to do?
Edit:
Plugged into a different usb port. Tried flashing Space kernel again and now I get error "<ID:0/006> Complete(Write) operation failed."
http://imgur.com/a/eRooU
Click to expand...
Click to collapse
bro , you can't flash kernal without rooting , try root device by cf-auto root and after that flash twrp and flash kernal by twrp not odin
shiko2007 said:
bro , you can't flash kernal without rooting , try root device by cf-auto root and after that flash twrp and flash kernal by twrp not odin
Click to expand...
Click to collapse
He can.
It's just causing by PC, or USB cable.
shiko2007 said:
bro , you can't flash kernal without rooting , try root device by cf-auto root and after that flash twrp and flash kernal by twrp not odin
Click to expand...
Click to collapse
I tried flashing CF-autoroot. I get this failure error:
http://imgur.com/a/nA0rc
forumber2 said:
He can.
It's just causing by PC, or USB cable.
Click to expand...
Click to collapse
When I try to flash space kernel I get "can't open (COM) serial port" and when I try to flash CF-auto I get "Nand Write start - > FAIL!".
I've used this PC and usb cable with other phones and it worked fine with Odin.
I am running Windows 10 this time though. I turned off Windows defender to. Not sure if that creates issues with connectivity.
Droid>iOS said:
I tried flashing CF-autoroot. I get this failure error:
http://imgur.com/a/nA0rc
When I try to flash space kernel I get "can't open (COM) serial port" and when I try to flash CF-auto I get "Nand Write start - > FAIL!".
I've used this PC and usb cable with other phones and it worked fine with Odin.
I am running Windows 10 this time though. I turned off Windows defender to. Not sure if that creates issues with connectivity.
Click to expand...
Click to collapse
bro , use the latest odin version not the old one
1 flash stock
2 factory reset /wipe cache
3 flash space x kernel
It will reboot to recovery just repeat step 2 and restart if it boots to recovery restart again
Done
shiko2007 said:
bro , use the latest odin version not the old one
Click to expand...
Click to collapse
Yup downloaded latest Odin 3.12 and still get same error.
tazaga said:
1 flash stock
2 factory reset /wipe cache
3 flash space x kernel
It will reboot to recovery just repeat step 2 and restart if it boots to recovery restart again
Done
Click to expand...
Click to collapse
When you say stock do you mean flash the official firmware? Since I've had the phone I've only updated with official firmware from Samsung.
thanks.
Droid>iOS said:
Yup downloaded latest Odin 3.12 and still get same error.
When you say stock do you mean flash the official firmware? Since I've had the phone I've only updated with official firmware from Samsung.
thanks.
Click to expand...
Click to collapse
Grab stock firmware from Sammobile use latest Odin 3.12
1 factory reset /wipe cache
2 flash stock firmware
3 factory reset /wipe cache and restart
Done!
vforvlive said:
Grab stock firmware from Sammobile use latest Odin 3.12
1 factory reset /wipe cache
2 flash stock firmware
3 factory reset /wipe cache and restart
Done!
Click to expand...
Click to collapse
Awesome I'll give it a go later today. Thanks !
Hey all,
A few days ago I did something very stupid and wiped the internal SD card which obviously bricked my phone down to download-mode, after which I initially flashed back a stock firm file which didn't help. After a lot of freaking out I remembered I had a TWRP-backup so I recovered this and my phone booted back up with IMEI in place and in/out calling+texting working.
Only things the backup couldn't fix are
1. PC - phone connectivity through USB doesn't work at all (besides when in download mode), it just charges and doesn't give me an option to choose or switch USB-mode. When connected while in TWRP there still is no connectivity, even after enabling MTP. Most importantly, Windows device manager doesn't seem to detect anything at all when I plug or unplug my phone but interestingly enough USB-OTG is working without a hitch so I have no clue as to why regular USB won't work on any pc :x
2. The initial boot screen (The one without animation saying Samsung Galaxy S6) somehow got corrupted and shows a somewhat glitched up download-mode screen before booting into system or recovery.
Anybody able to lend a hand?
if you can get to download mode and USB connectivity works, shouldn't you be able to flash stock firmware using OIDN?
Yeah I am able to flash, I already tried that and it did not help with either of the issues :/
Interestingly enough USB-OTG is working without a hitch so I have no clue as to why regular USB won't work on any pc :x
Have you tried flashing a 4-part firmware with PIT file and Re-Partition & Nand Erase All options checked in Odin ?
iDroid27210 said:
Have you tried flashing a 4-part firmware with PIT file and Re-Partition & Nand Erase All options checked in Odin ?
Click to expand...
Click to collapse
No I have not, I'd need to hunt this 4-part firmware down first + backup everything on there
Can I just restore a twrp-backup afterwards? or might that give me troubles?
screen said:
No I have not, I'd need to hunt this 4-part firmware down first + backup everything on there
Can I just restore a twrp-backup afterwards? or might that give me troubles?
Click to expand...
Click to collapse
Flash a 4-part firmware w/ PIT + Re-Partition and Nand Erase All to be back on a healthly base, then flash TWRP and restore your backup.
You can download a 4-part firmware using the SamFirm tool (Binary Nature checked in the software).
iDroid27210 said:
Flash a 4-part firmware w/ PIT + Re-Partition and Nand Erase All to be back on a healthly base, then flash TWRP and restore your backup.
You can download a 4-part firmware using the SamFirm tool (Binary Nature checked in the software).
Click to expand...
Click to collapse
This piece of advice fixed all my problems, thank you Only thing I ran in to was which PIT file to use since g920f has OPEN, OPEN_HIDDEN100M and OPEN_HIDDEN150M .PIT available and I do not know what the difference is between these (I ended up going with the non-HIDDEN one).
Hello, i have the SM-G9200ZH (Hong Kong version)
I disabled some system apps through pdp and got into a bootloop, after trying many things i did a factory reset and flashed through odin this firmware which is the latest
G9200ZHU2ERK2_G9200ZZH2ERK2_G9200ZHU2ERK2_HOME.tar the phone showed the bootanimation and then restarted to itself to bootlogo, over and over again.
So then i found a Pit file, and correct AP, BL, CSC, CP files for my device G9200ZHU2EQL1_G9200ZZH2EQL1_7.0, i flashed through odin selecting Nand Reset and Re-partition too.
At this point i still have the same issue, Phone goes into the bootanimation and then restarts itself over and over again.
The only way i have made the phone boot is by installing a custom ROM with TWRP, but i cant use any because it doesnt recognize the sim while using them.
Every time i flashed a firmware, When first booting i got a blue screen on the stock recovery that goes to 32% and then fails and says erasing.
Also im not using my Original Cable
So, can someone help me to make it work again? or to Tell me which custom rom actually works for my phone.
Did you try "wide /data" right after you've flashed the stock ROM?
forumber2 said:
Did you try "wide /data" right after you've flashed the stock ROM?
Click to expand...
Click to collapse
I did wipe data right after flashing through Odin, and also tried not wiping data after flashing through Odin. None of these worked, I don't know what to do
You can try flash twrp through odin then magisk/ supersu through twrp