Can't load J700p into bootloader - Samsung Galaxy J7 Questions & Answers

So i recently flashed lineage 14.1 j7ltespr to my J700p, and the rom loaded up fine, but it won't recognize the sim card. As this is my daily driver that can't be the case, so i tried to flash a stock rom back on. I think i could get it to work, but the phone won't boot into bootloader anymore.
It has the most recent version of twrp for the model. And it will system boot, and boot recovery just fine. But when i try to boot loader, it just gives me a charging symbol, and freezes. I've been trying to fix this anyway i can for the last 12 hours.
I also tried adb, and odin. Odin gives me an auth error every time i try to load a stock rom. If anyone could help, i'd be very appreciative.
I'd take fixing the sim not found, the bootloader not coming up, or the NAND Write Start!! FAIL! (Auth) error
thank you for your time

J700P
tjjc4 said:
So i recently flashed lineage 14.1 j7ltespr to my J700p, and the rom loaded up fine, but it won't recognize the sim card. As this is my daily driver that can't be the case, so i tried to flash a stock rom back on. I think i could get it to work, but the phone won't boot into bootloader anymore.
It has the most recent version of twrp for the model. And it will system boot, and boot recovery just fine. But when i try to boot loader, it just gives me a charging symbol, and freezes. I've been trying to fix this anyway i can for the last 12 hours.
I also tried adb, and odin. Odin gives me an auth error every time i try to load a stock rom. If anyone could help, i'd be very appreciative.
I'd take fixing the sim not found, the bootloader not coming up, or the NAND Write Start!! FAIL! (Auth) error
thank you for your time
Click to expand...
Click to collapse
Can you go into settings an turn off adb root then you should be able to flash stock from Odin ! Use Odin 3.12.5 !!

peter couniaz said:
Can you go into settings an turn off adb root then you should be able to flash stock from Odin ! Use Odin 3.12.5 !!
Click to expand...
Click to collapse
Thank you peter for the advice. I tried what you suggested. Still no luck. Here is the output of the odin runs, they were all identical though i tried different roms, 3 different versions of odin, root on and off, as well as with debugging on and off. Same out put every time.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2970 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also the output on the download screen on the phone throws this error
SW REV CHECK FAIL : [aboot] Fused 2 > Binary 1
I hope that helps.

J700P
tjjc4 said:
Thank you peter for the advice. I tried what you suggested. Still no luck. Here is the output of the odin runs, they were all identical though i tried different roms, 3 different versions of odin, root on and off, as well as with debugging on and off. Same out put every time.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2970 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also the output on the download screen on the phone throws this error
SW REV CHECK FAIL : [aboot] Fused 2 > Binary 1
I hope that helps.
Click to expand...
Click to collapse
It all or nothing on this if you can get into recovery factory reset then wipe system an go into download mod an try Odin one last time ! But before all that make shore debugging is on an make shore you are using a Samsung usb cord best the one that came with the phone ! An use Odin 3.12.5 or older 3.13.01 doesn't work right for that phone !!! PS make the firmware file isn't mest up ! Get the latest firmware file !

Related

Boot Loop after failed root

Hello, at this point I don't care about rooting my phone. I would just like to fix it and restore it back to normal.
I have a Galaxy S6 Edge. The thing that's wrong with my phone is that it's on a boot loop and it can't go into recovery mode (or boot loader what ever its called). It also says when on the Samsung screen boot loop (RECOVERY IS NOT SEANDROID ENFORCING)
My model is G925TUVU2COF8 and it's running 5.1.1. Every time I try to flash my firmware in odin 3.10.6 I always get this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925TUVU2COF8_G925TTMB2COF8_G925TUVU2COF8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can somebody please help!
if you need your phone fast fixed, you could flash custom recovery and adb push a rom, for the odin problem idk..., after latest bootloader got myself a strange odin flash bug if i try to flash a stock rom :/
"My model is G925TUVU2COF8"
That's not the model, that's a firmware version.
Your model number is the G925T. Which is the tmobile S6 edge. The F8 firmware is 4 months old, which is probably why it's not working for you, you may unintentionally be trying to downgrade. You need G925TTMB3DOI1 firmware. You can get it here http://www.sammobile.com/firmwares/download/56137/G925TUVU3DOI1_G925TTMB3DOI1_TMB/ or google for a faster dl source.
It's fixed now!!! Thank you so much!
Sboot.bin is the bootloader part of firmware. Only the latest firmware will fix this issue. Glad your issue is now okay.

can't flah stock firmware

when I boot it just gives me some kernel is not seandroid enforcing so i'm trying to flash a stock firmware. G900P_SPR_G900PVPU3BOG1_G900PSPT3BOG1_Original.zip. is the name of file and its for a sprint S5.
Here is the odin output
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HELP ME please.
I can flash the backup although it gets stuck at yellow boot screen. but that does get rid of the seaandroid enforcing
If someone could help me as well I'm having a similar problem. I have tried using multiple Odin versions and many stock SM-G900P 4.4.2 firmwares from multiple sources, but always have the same messages pop up.
Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_G900PVPU1BOA6_G900PSPT1BOA6_CL3859396_QB3804569_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
USB debugging is on and Odin does recognize the device is connect, I have also already installed the drivers again just to be sure. I have used Odin before with no trouble maybe its the fact the phone is from sprint and on lollipop since sprint is stingy on unlocking -_-. If someone could point me in the right direction or 100% working firmware links I'd appreciate it. I have also tried going about this through Heimdall and failed not even being able to obtain the pit file. If someone could provide a working one I'd also appreciate it I am fully aware it may brick the phone as everything else may do. Or show me the me the step by step to flash with Heimdall with a .tar. I'll take any advice thank you
you can try the newer firmware ok4
maybe this will work . unzip and place md5 in ap slot of odin
http://forum.xda-developers.com/spr...t/rom-sprint-ok4-stock-tar-file-odin-t3262667
Sprint new locked bootloaders
unteaglejohnk said:
when I boot it just gives me some kernel is not seandroid enforcing so i'm trying to flash a stock firmware. G900P_SPR_G900PVPU3BOG1_G900PSPT3BOG1_Original.zip. is the name of file and its for a sprint S5.
Here is the odin output
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HELP ME please.
Click to expand...
Click to collapse
I have the same problem myself and it took me a few minutes to realize what the problem is. I just got a new phone from Sprint because my other one the USB port was basically broken I couldn't connect or charge. So after a few failed attempts at flashing a ROM I decided to look at my firmware and realized that it was the new updated bog1 version. Sprint decided to lock all the boot loaders so as of this moment I don't know how to flash any ROM or downgrade as the bootloader will not let you. As a matter of fact just last night I was walking into Walmart I pulled my phone out of my pocket to look at it and it was just finishing up installing some security policy updates. My phone then immediately restarted and got stuck at the spark screen. Just the fact that I was rooted sent my phone into a boot loop. As of right now the only thing I can do is reflash the stock bog 1. I have managed to get access to this one and I'm working on modifying the bootloader in anyway I can. I'm a little newer to this but I catch on pretty quick. As of now I have all the permissions unlocked for me to access all the files in that stock bog1 rom but haven't found a way to make them stick yet. I'm going to have to break down each individual file and hopefully I can come up with a solution or anybody for that matter because I'm a few months away from my contract being up and if I can't root my phone and customize it I don't want it. If they want my phone lock down and toddler mode then they can pay for it that's how I look at it lol. Make sure you turn off automatic security updates. There's also a post in here of how to clean that out so you don't have the newest security policy update. I know the exact file the bootloader is in but haven't found a way to get into it or modify it yet even though I have permission. It shows it copying /deleting but doesnt change. There is way too many people in this world to not have someone come up with a solution by now and anytime I search for it I get results from a year to five years ago , hardly anything recent thanks google. I also posted on times and started a thread I'm trying but I'm not as advanced as some of these developers on here but I am determined lol
I finally got it to boot up. Just took like 20 mins. Now it boots sometimes while others it won't and says process has stopped responding after the yellow screen. Why does it do this. The rom is official rom directly off Samsung kids.
may have cracked bootloader BOG1 G900P
i have been playing in thr sys files and today i managed to get a custom animation boot installed. after that i flashed a modded bog1 file from philz. it took and succesfully booted and am now reinstalling all my apps. i think i over wrote or blocked my bootloader. ill get back when i know for sure:laugh:
http://samsung-updates.com/device/?id=SM-G900P

Boot Loop Even After Reset

Hey guys, so my phone has been going in to boot loops. I would put it in recovery mode and clear the cache partition, that would get it to stop sometimes. Finally I did a factory reset. Now when its trying to set up my phone, it boot loops in the middle of that. So I used ODIN and tried to reinstall the firmware (OJ7), which was successful, but I'm back to boot loops during the phone set up process. Any ideas what to do next?
VanillaNasty said:
Hey guys, so my phone has been going in to boot loops. I would put it in recovery mode and clear the cache partition, that would get it to stop sometimes. Finally I did a factory reset. Now when its trying to set up my phone, it boot loops in the middle of that. So I used ODIN and tried to reinstall the firmware (OJ7), which was successful, but I'm back to boot loops during the phone set up process. Any ideas what to do next?
Click to expand...
Click to collapse
Have you did any modifications?
I installed an app on my phone that works in collaboration with a game. The app requires the phone to be rooted, but after researching the process to root a phone and the risk of voided Knox on 5.1.1 I decided against it and uninstalled the app. Its possible the app may have done something. But besides that there has not been any mods installed on my phone.
What causes the constant rebooting? Do I possibly have corrupted files that can be replaced with the recovery system? Any ideas would be helpful.
Is your bootloader unlocked?
Soooperstar said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
I am not sure. Can I check that from the recovery mode or download mode screen?
VanillaNasty said:
I am not sure. Can I check that from the recovery mode or download mode screen?
Click to expand...
Click to collapse
Don't think so. Have you tried to Odin Ol1?
Soooperstar said:
Don't think so. Have you tried to Odin Ol1?
Click to expand...
Click to collapse
Just got that on the Ol1 ODIN attempt.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925PVPU3BOI1_G925PSPT3BOI1_G925PVPU3BOI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Edit: Since that failed, my phone will now only go into download mode. It says "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." But Smart Switch is now saying I don't have an supported device.
VanillaNasty said:
Just got that on the Ol1 ODIN attempt.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925PVPU3BOI1_G925PSPT3BOI1_G925PVPU3BOI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Edit: Since that failed, my phone will now only go into download mode. It says "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." But Smart Switch is now saying I don't have an supported device.
Click to expand...
Click to collapse
Can you Odin previous firmware?
Soooperstar said:
Can you Odin previous firmware?
Click to expand...
Click to collapse
Soooperstar, I appreciate you taking the time to try to help me. I took the phone to the Samsung vendor. She worked on it for 2 hours and couldn't get it to stop going into boot loops. Its being shipped to Samsung now so they can fix it.
Thanks again.

Flashed Bootloader and Modem from Griffin Rom, now stuck at S6 boot screen.

So, i wanted to flash the griffin rom. Had the tyrannus rom installed before and started with flashing the bootloader and modem.
After it finished the phone restarted and booted up automatically. After a few hours ( i was at work) i finally wanted to flash the rom. When i got in recovery mode, twrp asked something about partitions and make changes or something ( never read it before) i agreed. after the phone rebooted it got stuck at the boot screen. ( The s6 logo). Even when i wanted to boot into recovery mode the "recovery is not seandroid enforcing" was staying there for ever. i couldnt get into recovery. So i wanted to flash the stock rom via odin. but in odin if i want to flash the stock rom or a bootloader, then odin fails with the message:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> cache.img
<ID:0/003> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm really lost. I would be glad if somebody could help me :/
You probably have a newer Bootloader than the Stock ROM you are trying to flash.
Flash a newer Stock ROM, that would match your bootloader version.

Odin firmware flashing always fails

I have a Galaxy note 10.1 running kitkat 4.4.2 (GT-N8000)
Yesterday i was browsing the internet when suddenly the device decided to shut down and went on a restart boot loop where it would show the "Samsung galaxy note 10.1" screen for a while and then reboot and re-show the same screen
i have tried entering recovery mode but the tablet keeps restarting without end the only thing i can access is download mode
So recently i tried flashing using Odin but when ever i try to flash any file it shows this error
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried flashing a stock recovery so i can try and wipe the current data
I have tried to download multiple stock roms from jelly bean to kitkat which all ended up failing
I have tried flashing the tablet with a "Repair rom" which contains the BL AP CSC and Modem files
i think that if i can still access the download mode that there is some hope to recover?
Any solutions?
Thanks in advance.
If i posted this in the wrong section forgive me i have just started out

Categories

Resources