Related
I flashed my stock unrooted n8010 with the n8000 leak files using odin, I did not used the modem. All good and everything working.
Now I want to get back to stock n8010 jb. When in download mode the device apears like n8000 and odin is not able to flash the stock n8010 firmware.
I installed twrp and rooted, modified buildprop to apear like n8010 and tried to flash a custom rom for n8010, no luck, I get a message that the rom is for n8010 and to try a rom for my device.
How can I trick twrp or odin to make them flash n8010 fw/rom ?
I don't have a nandroid backup,
Edit : I managed to flash 4.0.4 with odin (N8010XXALGC_N8010OXXALG4_COA). After the flash it was stuck at samsung logo, I rebooted in recovery (power+volume up, release only power at samsung...) and wiped cache, wiped data and reset. Now the device booted with android 4.0.4 and I'm downloading a 568.29 MB update. I'll see what happends next...
The goal is to get back to stock jb, official (with triangle away I gues)
Edit: I updated to JB, but when in download mode the device is still N8000, so the problem is still not solved.
Sent from my GT-N8010 using Tapatalk
KoRoZIV said:
I flashed my stock unrooted n8010 with the n8000 leak files using odin, I did not used the modem. All good and everything working.
Now I want to get back to stock n8010 jb. When in download mode the device apears like n8000 and odin is not able to flash the stock n8010 firmware.
I installed twrp and rooted, modified buildprop to apear like n8010 and tried to flash a custom rom for n8010, no luck, I get a message that the rom is for n8010 and to try a rom for my device.
How can I trick twrp or odin to make them flash n8010 fw/rom ?
I don't have a nandroid backup,
Edit : I managed to flash 4.0.4 with odin (N8010XXALGC_N8010OXXALG4_COA). After the flash it was stuck at samsung logo, I rebooted in recovery (power+volume up, release only power at samsung...) and wiped cache, wiped data and reset. Now the device booted with android 4.0.4 and I'm downloading a 568.29 MB update. I'll see what happends next...
The goal is to get back to stock jb, official (with triangle away I gues)
Edit: I updated to JB, but when in download mode the device is still N8000, so the problem is still not solved.
Sent from my GT-N8010 using Tapatalk
Click to expand...
Click to collapse
What version of Odin are you using ?Did you try to remove micro SD and full erase you tablets internal memory card? And why not 4.1.2 you install and not 4.0.4?
Because 4.1.2 gives me error, tried 3 versions of Odin: 3.04, 3.09, and 1.85. Tried 4.1.2 from 3 different sources to avoid a bad download. I can only flash 4.0.4, android shows me n8010 but in download mode is still n8000. I have no idea why, I just can't get rid of the n8000 in download mode.
Maybe I need to flash separate files, just like I did with 4.4.2, bootloader. Ap , csc but I don't know where to get those files for 4.1.2, I only have .tar.md5 files.
I attached a ss with odin eror when trying to flash stock 4.1.2
Sent from my GT-N8010 using Tapatalk
KoRoZIV said:
Because 4.1.2 gives me error, tried 3 versions of Odin: 3.04, 3.09, and 1.85. Tried 4.1.2 from 3 different sources to avoid a bad download. I can only flash 4.0.4, android shows me n8010 but in download mode is still n8000. I have no idea why, I just can't get rid of the n8000 in download mode.
Maybe I need to flash separate files, just like I did with 4.4.2, bootloader. Ap , csc but I don't know where to get those files for 4.1.2, I only have .tar.md5 files.
I attached a ss with odin eror when trying to flash stock 4.1.2
Sent from my GT-N8010 using Tapatalk
Click to expand...
Click to collapse
Did you have success installing the bootloader of the leak kitkat rom? Cause mine failed always, the AP file is the 1 working on me only. I have downloaded this TAR_MD5_PACKAGER here( http://forum.xda-developers.com/showpost.php?p=42393470&postcount=2 ) that I'm using to repack the stock and using 7zip to extract the content of the .tar.md5 files, maybe you can try repacking it seperately using this 2 program. And try to install it using Odin( I'm using Odin 1.85). By the way you can still install custom 4.1.2 rom's right, specifically for 8010 ? Lastly why do you wanna go back to stock 4.1.2 do you have problem with the leak rom?
P.S. Did you format your internal memory as I suggested? Cause once I install back to 4.1.2 have error before and have to install twice the rom( that is according to my experience which some think its not relate to installing error).maybe you can try to format all from the system to the internal memory via CWM recovery /mount section.Then try to install again and remove the SD card too.
I had no problems with the kit Kat files, flashed at the same time bl, csc and ap (no modem). I used odin 3.09. I managed to get back to 4.1.2 by flashing stock 4.0.4 then using OTA (im surprised it worked) . Someone else flashed directly 4.1.2 with mobile odin and worked, but with odin from pc you get an error.
The problem is that in download mode appears like n8000; hopefully, when official kk for n8010 is out we'll be able to fix that.
Sent from my GT-N8010 using Tapatalk
KoRoZIV said:
I had no problems with the kit Kat files, flashed at the same time bl, csc and ap (no modem). I used odin 3.09. I managed to get back to 4.1.2 by flashing stock 4.0.4 then using OTA (im surprised it worked) . Someone else flashed directly 4.1.2 with mobile odin and worked, but with odin from pc you get an error.
The problem is that in download mode appears like n8000; hopefully, when official kk for n8010 is out we'll be able to fix that.
Sent from my GT-N8010 using Tapatalk
Click to expand...
Click to collapse
Glad you manage to resolve some of your problem.Plese ignore my post above your's then.
The problem is not solved lol. I just gave up for the moment. It's a miracle that I didn't bricked the damn thing today
I'll stay with a 4.1.2 stock n8010 fw that is using an n8000 4.4.2 bootloader. Sexy
Sent from my GT-N8010 using Tapatalk
Well from everything I've read it seems the problem is that when we flashed the kitkat leak, flashing the bootloader is what allowed us to flash n8000 over our n8010. This could be why when we flash back using odin we get the error cause the bootloader isn't being flashed too so it's trying to flash n8010 onto what it reads as n8000. It seems that there are only a few solutions. 1we need to find a n8010 bootloader file which so far seems to be impossible to find. 2you can flash an original n8010 cmw or twrp back up it will return you to 4.1.2 n8010 but the bootloader will still be n8000. If this option isn't available to you then you can try 3 download a custom rom I have the darkmans customers stock as a backup and it still works going back to simple stock n 8010 but again the bootloader stays as n8000...
Basically until we can get an n8010 bootloader we are stuck with it...
I even rooted the 4.4.2 leak and tried to flash a custom 4.4.2 made for n8010 and did not let me (based on the same leak i think, so the same bootloader) and failed, twrp sees the device as n8000 and did not allowed me to use n8010 rom.
KoRoZIV said:
I even rooted the 4.4.2 leak and tried to flash a custom 4.4.2 made for n8010 and did not let me (based on the same leak i think, so the same bootloader) and failed, twrp sees the device as n8000 and did not allowed me to use n8010 rom.
Click to expand...
Click to collapse
I think I read somewhere that twrp can have issues with flashing 4.4.2 roms it needs to be the most up to date version of twrp... I tried cm 11 before and had to change to Cwm. But I went back to twrp and now it works
I used twrp 2.7, I think it's the latest.
Edit:
I reached a binary counter of 118
I used triangle away and reset it, however I'm still stuck with the n8000 4.4.2 bootloader.
N8000 bootloader
Same issue here, stuck on N8000 bootloader on my GT-N8010. After endless research I still can't find any solution but now the thing is, the official 4.4.2 KK is availble for the GT-8010, you guys think this is the solution, because I have read that though updating to the official Rom (via Odin Mobile) because Odin desktop fails, the device would still be stuck on the annoying N8000 bootloader?
Yes, even if you flash the n8010 4.4.2 with mobile Odin you will still have the damn n8000 bootloader.
Sent from my Nexus 5 using Tapatalk
KoRoZIV said:
Yes, even if you flash the n8010 4.4.2 with mobile Odin you will still have the damn n8000 bootloader.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Any way of downgrading the Bootloader, I've heard of a nandroid backup but I didn't do that before updating, is it possible to find one on the web?
You need a nandroid from a similar device, is possible but not sure if it will solve the problem.
Sent from my Nexus 5 using Tapatalk
KoRoZIV said:
You need a nandroid from a similar device, is possible but not sure if it will solve the problem.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I thought the official Rom would fix this but visibly no. So we don't have a choice of being stuck with the damn N8000 bootloader?
At the moment there is no solution that I know of.
Sent from my Nexus 5 using Tapatalk
N8010 on N8000 bootloader
Hi guys, isn't there a solution about this yet? I have the exact same problem with the N8000 bootloader, my device is a N8010 16GB from mexico and flashed the leaked N8000 kk stock rom. I will still look for a solution. TKS to all of you.
Mean time solution
Hi Guys, I found a way to flash te new N8010XXUDNE4 on the stuck n8000 bootlader, the bootloader problem remains, but it is possible to flash the n8010 stock rom via mobile odin, I did it and it's fully working, But I flashed a N8010XXUDNE4 customized without sboot.bin so it can be flashed via PC odin too, I'm still not allowed to post links here cause I'm new in forums so if you want the link to that rom let me know how to provide it to you.
Possible solution?
Have a look at my thread, does that look a viable approach?
http://forum.xda-developers.com/galaxy-note-10-1/help/recovering-n8010-leaked-locked-n8000-t2802516
ambmar78 said:
Hi Guys, I found a way to flash te new N8010XXUDNE4 on the stuck n8000 bootlader, the bootloader problem remains, but it is possible to flash the n8010 stock rom via mobile odin, I did it and it's fully working, But I flashed a N8010XXUDNE4 customized without sboot.bin so it can be flashed via PC odin too, I'm still not allowed to post links here cause I'm new in forums so if you want the link to that rom let me know how to provide it to you.
Click to expand...
Click to collapse
I got the Galaxy S6 yesterday and coming from Nexus 5, I wanted to remove the existing bloatware by flashing the XtrestoLite Deodexed ROM. This one here: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/rom-xtrestolite-deodexed-mod-edition-1-3-t3119968
I'm haven't had much experience in rooting and it's my first time flashing a custom ROM. The phone was running on Android 5.1.1.
Apparently I failed. I started with CF-Root but I wasn't sure if it was done correctly. This was followed by TWRP 2.8.7.1 . Then I tried booting up the phone and the boot logo just loops. I tried to wipe the cache as well as the Delvik-cache through TWRP but it's still the same. Then I tried to flash the stock ROM that I found online but I got the error "Nand Write Start" followed by "Fail". I seem to have tried everything and now I just want to get the phone to work again. It shouldn't be so hard.
Someone help me please :crying:
Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.
Gallitho said:
Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.
Click to expand...
Click to collapse
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Edit: I managed to do it through initialization. I'll update when it's done.
Edit 2: It worked! Thanks so much!
ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.
ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin
1qazwsx4 said:
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin
Click to expand...
Click to collapse
How could I transfer the flashable ROM to the phone when I can't have it boot up to connect to my computer?
Gallitho said:
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.
Click to expand...
Click to collapse
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Can you guys help me check if this post has the correct steps or is it missing anything like bootloader and root?
reddit.com/r/GalaxyS6/comments/39wwf6/should_i_install_xtrestolite_rom/cs7b7yq
ztmj96 said:
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Click to expand...
Click to collapse
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.
Gallitho said:
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.
Click to expand...
Click to collapse
1. So what is the correct order?
2. Did you have to manually unlock bootloader?
3. And is it a must to install uniKernel in order to root the device?
I have no idea how to proceed now.
This requires a lot more effort than I thought :fingers-crossed:
1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.
Gallitho said:
1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.
Click to expand...
Click to collapse
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.
ztmj96 said:
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.
Click to expand...
Click to collapse
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.
Gallitho said:
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.
Click to expand...
Click to collapse
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!
ztmj96 said:
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!
Click to expand...
Click to collapse
Glad to read that, dude!
Yep, our situations are identical and also happened at the same time haha.
Now's time to enjoy! :good:
Hey guys, Im in need of some expert help.. So basically I let a friend root my phone and install twrp, and all went well until he flashed Xposed. He wasn't aware that I had installed the marshmallow update. After he flashed xposed the phone wouldn't boot so he tried to flash the stock 6.0.1 ROM back from Sam mobile with no luck. Apparently it gets stuck in Odin when trying to flash the CM.bin and the sboot.bin files. I was able to flash the system and modem files on to get it to boot. when checking the phone im not seeing any IMEI as it says Unknown. Ive tried just the modem file and nadda.. any help would be appreciated. Also My phone detects now as a SM-G920F and not as it should SM-G920W8 Canadian version.
Update. Ive installed the Xtresto Lite through TWRP and it installed fine except it still detects the phone now as a SM-G920F and ive still got no modem working.
simonsez4200 said:
Hey guys, Im in need of some expert help.. So basically I let a friend root my phone and install twrp, and all went well until he flashed Xposed. He wasn't aware that I had installed the marshmallow update. After he flashed xposed the phone wouldn't boot so he tried to flash the stock 6.0.1 ROM back from Sam mobile with no luck. Apparently it gets stuck in Odin when trying to flash the CM.bin and the sboot.bin files. I was able to flash the system and modem files on to get it to boot. when checking the phone im not seeing any IMEI as it says Unknown. Ive tried just the modem file and nadda.. any help would be appreciated. Also My phone detects now as a SM-G920F and not as it should SM-G920W8 Canadian version.
Update. Ive installed the Xtresto Lite through TWRP and it installed fine except it still detects the phone now as a SM-G920F and ive still got no modem working.
Click to expand...
Click to collapse
Did you flash 920f modem?. Flash back to stock with odin or smart switch. Odin is a bit fussy though. Best us smart swith. It will do everything. You just have to enter model number and s.n. of the phone.
Sent from my SM-G925F
Any way to Downgrade to lollipop
i tried to flash lollipop by odin but fail
My phone : j700f
Hi.
This is is what I did.
Install TWRP, if you haven't, then install a CUSTOM lollipop ROM from this forum.
If you want stock lollipop, flash it via Odin - after flashing the custom lollipop ROM.
Good luck!
Not working
first flash stock MM then flash stock LL then flash custom LL
Try it again, and make sure that the auto reboot box and F.reset time box is checked in Odin Options
Make sure you flash your country frimware. Else it will fail in odin. And use latest odin.
Bro you need to download latest lollipop firmware
I had the same problem and it was solved by fresh firmware of latest date
Goodluck ?
Sent from my SM-G935F using Tapatalk
WHen I try to downgrade using odin I got error that "NAND Write Start!"
how I can fix???
Hey guys! I have a problem. I have flashed on my Galaxy S7 (Exynos version) the galaxy Note Fan Edition Port rom a couple of weeks ago, but now I flashed the latest stock firmware from Sammobile via odin and it always fails at the bootloader. I don't know why? I searched for many hours for a solution, but nothing works.... I hope somebody could help me
Here is the link for the note fan edition rom: https://forum.xda-developers.com/s7...-galaxy-note-fan-edition-port-vol1-0-t3633626
OEM unlock on?
Could also be that the latest bootloader prevents rolling back, so if you're trying to go from a newer bootloader to an older one it won't let you. You can probably just exclude the BL file and be fine.
Is that Fan Edition ROM you flashed not a S7 Edge rom made to work on the S7..! Maybe your phone shows up as a G935 now?
I have flashed android 8.0 manually from sammobile via odin and it got stuck on emergency recovery and I somehow got it into the download mode and every time I want to flash my stock firmware it says device 2 binary 1... I also flashed twrp recovery and wiped everything (system, data....) and tried again and it always fails in odin and says device 2 binary 1.. Im trying to find solution but everytime it fails. PLEASE HELP ME
daymonfeyenord said:
I have flashed android 8.0 manually from sammobile via odin and it got stuck on emergency recovery and I somehow got it into the download mode and every time I want to flash my stock firmware it says device 2 binary 1... I also flashed twrp recovery and wiped everything (system, data....) and tried again and it always fails in odin and says device 2 binary 1.. Im trying to find solution but everytime it fails. PLEASE HELP ME
Click to expand...
Click to collapse
Samething happened to me. I did the same thing u did but nothing worked.
Can someone plz help us to get odin download work again.
you should go for latest rom. download from here: https://samsung-firmware.org/model/SM-G930F/region/BTU/
You will be satisfy with this.
Hi! Same error but different situation.
I was on the latest firmware 8.0 ITV, I wanted to downgrade to nougat, so I downloaded the first 7.0 firmware BTU (the one that was the best for my S7).
I opened all the firmware files on odin 3.13.1 and I started the procedure but at a certain point everything stopped, on odin the message "failed" appeared and on the phone the message "sw rev check fail (bootloader) device 2 binary 1".
I tried with a different version of odin but the message remains the same, I also tried without flashing the BL file but nothing ... In the end I had to flash again the latest firmware oreo ITV and no errors appeared, but I find myself at the starting point
specific that my S7 has never had modding operations, the knox counter is perfectly at 0x0, I have always used only original firmware and never had problems with odin.
How can I downgrade without having in that error?
Hi just flash this version of latest nougat G930FXXS2DRDI, this is binary 2 firmware (XEO)