Related
Hello guys,
i'm from germany and have big troubles with my Samsung Galaxy S4 GT-I9505G...
I have flashed the Google 4.3 edition on it. Some days later the trouble has begin.
If i startet apps like camera or mozilla it shutdown.
So i have tried to flash the original firmware with Odin.
The device started but than it is in the Bootloop, i have tried to flash with the 4 parts (bootloader,csc,phone,pit...)
but there is only an error. When I tried the 1 Part Versions there is also the Bootloop.
-> I used the Firmware Downloads from Handy-faq.de
I hope you can help me, i need my Phone xD
Tanks!
Morgotov said:
Hello guys,
i'm from germany and have big troubles with my Samsung Galaxy S4 GT-I9505G...
I have flashed the Google 4.3 edition on it. Some days later the trouble has begin.
If i startet apps like camera or mozilla it shutdown.
So i have tried to flash the original firmware with Odin.
The device started but than it is in the Bootloop, i have tried to flash with the 4 parts (bootloader,csc,phone,pit...)
but there is only an error. When I tried the 1 Part Versions there is also the Bootloop.
-> I used the Firmware Downloads from Handy-faq.de
I hope you can help me, i need my Phone xD
Tanks!
Click to expand...
Click to collapse
Try and download firmware from Sammobile and flash again with odin
jaythenut said:
Try and download firmware from Sammobile and flash again with odin
Click to expand...
Click to collapse
I've tried but no success.
So i show all data while flashing:
ODIN MODE *
Product Name: GT-I9505
Current Binary: Samsung Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-Config-LSB: 0x30
Write protection: enable
START [224,1440]
SW REV. CHECK FAIL:fused:2, Binary 1 *
*is written in red
I hope it helps I have tried a lot but nothing happens...
Realy noone can help me?
I have testet to repair bootloader with JTAG from this thread:
http://forum.xda-developers.com/showthread.php?t=2265477
but the Bootloader was unchanged!
Please help!
If the Odin flash is succesfull using the one part version, then you need to boot into recovery and select factory reset and/or wipe cache. That should probably fix it.
If not, be more specific. What firmware did you try to flash? Also what device do you have? Do you have the GT-I9505G or the GT-I9505?
Thanks for your Answer!
I tried to flash firmware 9505 German DBT with the last xxxMH5.
My Device is an GT-I9505G.
When i tried to boot in Recovery mode in the left corner is written "Recovery Boot" but then the screen turns black and
the device restart.
Flashing i tried both 4 Part and 1 part -> 4 part fails und 1 part is successfull but there is still the bootloop
Tanks for helping Lennyz!
Why do you flash I9505 roms on a I9505G? I'm don't know much about that device, but I thought the firmware can't be exchanged? Or am I wrong?
Do you have an unlocked bootloader? If so, I would try to flash cwm.
If no one else that has more knowledge about this responds in you thread, my suggestion would be the following.
1. Try this firmware: http://forum.xda-developers.com/showthread.php?t=2342377
if that fails
2. Try this method: http://forum.xda-developers.com/showthread.php?t=2360346
But then again, I don't own the device, so it's on you.
Lennyz1988 said:
Why do you flash I9505 roms on a I9505G? I'm don't know much about that device, but I thought the firmware can't be exchanged? Or am I wrong?
Do you have an unlocked bootloader? If so, I would try to flash cwm.
If no one else that has more knowledge about this responds in you thread, my suggestion would be the following.
1. Try this firmware: http://forum.xda-developers.com/showthread.php?t=2342377
if that fails
2. Try this method: http://forum.xda-developers.com/showthread.php?t=2360346
But then again, I don't own the device, so it's on you.
Click to expand...
Click to collapse
Thanksfor all your help!
I have done method 2 two times but than it works great!
Sorry but i have ab really big problem!
I had repair my phone with the Google Edition for S4.
But the phone often crashed when i open some apps, this crashes are very often.
Should I use the warranty or tried to flashed the original firmware but i won't want crash my bootloader.
Can this crashes are in connection with knox?
Thank for your help!
Good to hear you got your phone working again.
Try a factory reset, maybe that will help.
Hey guys, so I have a note 3 n9005,which i had rooted previously. This morning, I tried to flash the new touchwiz kitkat firmware via Odin and failed. Now the phone wouldn't boot up, but I an able to make it into the download mode. I have tried flashing several firmwares but neither of them works, I also had cm11 installed, so odpnt know f the bootloader has been updated or not...
So of anybody could please help me with this, that would be greatly appreciated
i have excatly the same problem tried to update s9005 via odin hong kong version to german 4.4.2 and now wont boot, odin fails only 20 seconds in read so many threads would also like to see some solutions to op.
CaptaiinCaveman said:
Hey guys, so I have a note 3 n9005,which i had rooted previously. This morning, I tried to flash the new touchwiz kitkat firmware via Odin and failed. Now the phone wouldn't boot up, but I an able to make it into the download mode. I have tried flashing several firmwares but neither of them works, I also had cm11 installed, so odpnt know f the bootloader has been updated or not...
So of anybody could please help me with this, that would be greatly appreciated
Click to expand...
Click to collapse
You also need to add some of the stuff it is written in download mode and the log in Odin when in fails. If you went to 4.4.2 on N9005 you can not return to 4.3 (which you should have read by now, there are only 200 posts in 50 threads about it). What kind of N9005 was yours (16/32/64GB), what region/CSC?
xclub_101 said:
You also need to add some of the stuff it is written in download mode and the log in Odin when in fails. If you went to 4.4.2 on N9005 you can not return to 4.3 (which you should have read by now, there are only 200 posts in 50 threads about it). What kind of N9005 was yours (16/32/64GB), what region/CSC?
Click to expand...
Click to collapse
I flashed the DBT FW again with this pit file created by HSDPilot http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77.
It worked and lash was complete now however i am stuck in SAMSUNG logo after restart.
ANy help?
solution
newapostlenew said:
I flashed the DBT FW again with this pit file created by HSDPilot http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77.
It worked and lash was complete now however i am stuck in SAMSUNG logo after restart.
ANy help?
Click to expand...
Click to collapse
hi i followed your instructions afte having the same problem.
once it was flashed and at the samsung logo
i took battery out, replaced it and started phone in recovery mode. go to wipe factory reset
then reboot
mine worked and is ok .
CaptaiinCaveman said:
Hey guys, so I have a note 3 n9005,which i had rooted previously. This morning, I tried to flash the new touchwiz kitkat firmware via Odin and failed. Now the phone wouldn't boot up, but I an able to make it into the download mode. I have tried flashing several firmwares but neither of them works, I also had cm11 installed, so odpnt know f the bootloader has been updated or not...
So of anybody could please help me with this, that would be greatly appreciated
Click to expand...
Click to collapse
darkman13 said:
i have excatly the same problem tried to update s9005 via odin hong kong version to german 4.4.2 and now wont boot, odin fails only 20 seconds in read so many threads would also like to see some solutions to op.
Click to expand...
Click to collapse
Do either of you have a 16 GB version?
Hi All,
My problem :
I wanted to install the official kitkat rom but I made a big mystake : I took N900 files instead of N9005...
After that I successfully installed the right bootloader and CWM.
I installed some cuustom roms but the setupwizard crash at the last step
I tried to flash the complete official 4.4.2 rom but odin failed with message on the phone : "ODIN : invalid ext4 image"
Anybody has any idea to help me ?
hi guys i manage to fix it, well mine anyway worked by flashing the pit i found on xda and selecting repartion on odin 3.7 along with german 4.4.2 to my n9005 from Hong Kong, re booted and done a factory reset via volume button also wiped cache and re started and it came back alive on the selected german rom 4.4.2. hope it hels others. ps my note 3 was from hong kong n9005 32gb
xclub_101 said:
You also need to add some of the stuff it is written in download mode and the log in Odin when in fails. If you went to 4.4.2 on N9005 you can not return to 4.3 (which you should have read by now, there are only 200 posts in 50 threads about it). What kind of N9005 was yours (16/32/64GB), what region/CSC?
Click to expand...
Click to collapse
hey, i wasnt trying to downgrade, i was going from cm11 to official 4.4.2. i've got a 32gb model from france i believe (the box has french written all over it so do the manuals)
newapostlenew said:
I flashed the DBT FW again with this pit file created by HSDPilot http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77.
It worked and lash was complete now however i am stuck in SAMSUNG logo after restart.
ANy help?
Click to expand...
Click to collapse
dude, you are god thank you so much for that, working perfect now
xclub_101 said:
You also need to add some of the stuff it is written in download mode and the log in Odin when in fails. If you went to 4.4.2 on N9005 you can not return to 4.3 (which you should have read by now, there are only 200 posts in 50 threads about it). What kind of N9005 was yours (16/32/64GB), what region/CSC?
Click to expand...
Click to collapse
After installing DBT NB4 FW ( or with Polish NB3 FW) my LTE speeds become almost 0.
I tried multiple installs.
Any guidance?
Quick tip: Uninstall KIES.
Kies is like a big brother.
Use ODIN 1.85 and tick update phone bootloader. That's how I fixed mine. The other versions of Odin wouldn't let me update bootloader.
Of course, before you do this Flash/wipe data in recovery mode.
But uninstalling KIES solved my issue.
Sent from my SM-N9005 using Tapatalk
SOLVED:
Finally got Odin to work! Tried it on an actual PC laptop and not my vmware macbook. It failed at 99% the first time so tried another USB port and it went up and passed! this is on 4.4.2. I guess the main reason why the other firmwares would fail was because I originally tried to flash odin 4.4.2 but at this point I had no idea about knox and that you cannot go back in firmwares. So my last attempt was to push 4.4.2 after looking into the phones info saying it was on I337MVLUFNC1 bootloader. I was starting to think I had bricked this phone! sound works and calls working fine! whoop!
some history on the device:
- S4 was on Beanstalk 4.4.2, rooted.
- phone was starting to freeze up on this ROM so
- decided to go back to stalk Rogers rom via ODIN
- tried Odin v 3.09/v3.07/3.04 all failed
- tried different cables and two different computers. failed
- So then I decided to load TWRP back in from ODIN = Pass!, I get into recovery and load up a backup. This works but had NO sound or video playback and calls wont go through/freeze phone in call app.
- more tinkering, thinking it was maybe the Kernel/Modem. I download different Kernel/modm for the phone and sound still didnt work.
- Tried Firnware I337MVLUEMK6_I337MOYAEMK6_RWC, as well as the current I337MVLUAMG1_I337MOYAAMG1_RWC both were downloaded from sammobile.com
- tried kies and it cant connect to phone or does anything.
Phone errors:
-top corner of display shows:
Odin mode
product name: sgh-I337M
Current Binary: Samsung official
System status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CBS - Config - LSB: 0x30
Write Protection: Enabled
eMMC Burst mode enabled
Currently:
- I can load TWRP anytime.
- I can also reload backups, install roms but sound, video, phone calls, mic dont work. some roms are super laggy as well.
- so phone is still useless atm.
ill try Odin again and copy the fail script.
it fails immediatly after system write.
iv searched knox trip, and some people have gotten stock firmware back on their device. but i have no way of doing so since odin fails horribly.. To my understanding if Knox has been tripped then you cannot downgrade firmware. but iv been trying to get 4.3 or even 4.4.2 on it and it fails.
actually i shouldnt say i tried to get 4.3 on it, because it seems i did get it on the phone at one point but then it had absolutly no signal. It would have signal for maybe 3 minutes then it drops it completely. tried APN settings and still wouldnt kick it. only thing I didnt try on that attempt was load up a different modem. which i should have.. but now cant even get that rom back on here as my sister deleted it..
any help would be appreciated.
Alright so im back on a backup from my other S4, running ok. signal is fine and wifi works. only thing is upon boot up i get:
- Unfortunately, Google Dialer has stopped.
- unfortunately, the process android.process.acore has stopped.
-unfortunately, the process android.process.meida has stopped.
i can hit ok many times but it keeps popping up.
so im still unable to do anything. i can still navigate through the phone but the pop ups come often.
UPDATE:
- Did a factory data reset within the phone and I dont get the pop ups anymore. but the Sound is still not working
one thing that's weird is when I use the app Phone Info the Sales Code (aka Region Code) is: ATT, but my working s4 with the same ROM says VMC under Region code? is this making my sisters phone not function properly? or maybe this is why I cannot flash stock rogers through odin because the phone is thinking its an ATT device and not a Rogers one?
Just wondering, since Knox is tripped am I able to still use Odin to flash to stock? Just want to clarify that before I waste more time with odin .
Iv tried rogers 4.2.2, 4.3 and pretty sure iv tried 4.4.2. But I'm going to download it and try that one again.
Phone was previously on 4.3 without signal. So I'm guessing that's the very least I can load up since Knox is tripped correct? I shouldn't have issues flashing Odin 4.4 stock rogers?
Just wondering why it fails once its writing to system..
I have tried to flash the Android 5.0.1 stock firmware N910FXXU1BOC3 on my Note 4 N910F and I'm getting some error in Odin when it's writing the hidden.img.ext4 and failing. On the device, in Download Mode i see the error message volume size is too big.
Right now i'm on Android 4.4.4 N910FXXU1ANK4.
First thought was that i left Reactivation Lock on and saw a bunch of other threads where it says that this might be the main issue as I am flash a different CSC Region ROM. I managed to get back to N910FXXU1ANK4 after the failed flash of N910FXXU1BOC3 with Kies3 and Emergency re-initialization (thank you Samsung for finally doing something useful with Kies). I disabled the reactivation lock and attempted again to flash N910FXXU1BOC3 but failed with the same error.
After some searching, i found that the issue might be because i have to re-partition the device in order to fit the new partiton sizes for Android 5.0.1.
This should be done with the Odin option to Re-partition but that requires a PIT file in order to have the re-partition information.
I have looked into the md5 archive for the N910FXXU1BOC3 ROM and initial 5.0.1 release for N910F N910FXXU1BOB4 ROM but I could not find a PIT file in order to re-partition.
Now my question is, when going from Android 4.4.4 N910FXXU1ANK4 to Android 5.0.1 N910FXXU1BOC3, do I have to re-partition with Odin, and if so, where do I get the correct PIT file ?
Thanks.
lolozaur said:
I have tried to flash the Android 5.0.1 stock firmware N910FXXU1BOC3 on my Note 4 N910F and I'm getting some error in Odin when it's writing the hidden.img.ext4 and failing. On the device, in Download Mode i see the error message volume size is too big.
Right now i'm on Android 4.4.4 N910FXXU1ANK4.
First thought was that i left Reactivation Lock on and saw a bunch of other threads where it says that this might be the main issue as I am flash a different CSC Region ROM. I managed to get back to N910FXXU1ANK4 after the failed flash of N910FXXU1BOC3 with Kies3 and Emergency re-initialization (thank you Samsung for finally doing something useful with Kies). I disabled the reactivation lock and attempted again to flash N910FXXU1BOC3 but failed with the same error.
After some searching, i found that the issue might be because i have to re-partition the device in order to fit the new partiton sizes for Android 5.0.1.
This should be done with the Odin option to Re-partition but that requires a PIT file in order to have the re-partition information.
I have looked into the md5 archive for the N910FXXU1BOC3 ROM and initial 5.0.1 release for N910F N910FXXU1BOB4 ROM but I could not find a PIT file in order to re-partition.
Now my question is, when going from Android 4.4.4 N910FXXU1ANK4 to Android 5.0.1 N910FXXU1BOC3, do I have to re-partition with Odin, and if so, where do I get the correct PIT file ?
Thanks.
Click to expand...
Click to collapse
hi,
i have a N910F.. When i went from stock Android v 4.4.4 to Lollipop .. German Rom.. BOB4 and after that again to BOC3 I did not repartion anything. in fact repartion must be untick , I only made sure that auto reboot was ticked and F. Reset Time ticked then, place the tar/(md5 )file in AP section of Odin. Switch phone off, boot into download mode, connect phone via usb and wait for blue color to light up ID:COM box (above auto reboot) check if everything is connected and correct boxes ticked and then flash.( see screenshot ) After flash your phone will "try" to boot up but will optimise apps first. This can take some time (my case about 10 min? or so)
Plse take note that i am referring from stock Rom v4.4.4 to stock Lollipop
v 5.0.1 Also you only flash the one file....... "tar"/(md5 ) thats all.
good luck
willcor said:
hi,
i have a N910F.. When i went from stock Android v 4.4.4 to Lollipop .. German Rom.. BOB4 and after that again to BOC3 I did not repartion anything. in fact repartion must be untick , I only made sure that auto reboot was ticked and F. Reset Time ticked then, place the tar/(md5 )file in AP section of Odin. Switch phone off, boot into download mode, connect phone via usb and wait for blue color to light up ID:COM box (above auto reboot) check if everything is connected and correct boxes ticked and then flash.( see screenshot ) After flash your phone will "try" to boot up but will optimise apps first. This can take some time (my case about 10 min? or so)
Plse take note that i am referring from stock Rom v4.4.4 to stock Lollipop
v 5.0.1 Also you only flash the one file....... "tar"/(md5 ) thats all.
good luck
Click to expand...
Click to collapse
Thank you for the reply, thinking back I don't think i tried to flash BOB4 first and then BOC3. I will try this today and come back with some feedback.
lolozaur said:
Thank you for the reply, thinking back I don't think i tried to flash BOB4 first and then BOC3. I will try this today and come back with some feedback.
Click to expand...
Click to collapse
hi ,
i personally , don't think it will make any difference or matters,
if you flash the one or the other ..but hey ..who knows ..?
Only reason ,i flashed BOB4 as it was the first Lollipop available and BOC3 was a later date ( March 2015 )
good luck
I have the similar issue. KK and BOB4 roms work and install perfectly. however I am having the same issues while installing BOC3 rom be it Stock or Custom.
So I finally managed to solve the issue. Seems that the image I was downloading from Sammobile was not that good.
I was trying to install N910FXXU1BOC3_N910FVFG1BOC2_CNX - Romania Vodafone. I was unable to install it no matter what I tried.
I was able to install N910FXXU1BOC3_N910FTPD1BOC1_TPD - Netherlands unknown, without any issues.
Something that i noticed is that when loading the tar with issues in Odin, total binary size was shown as 0 mb, while on the Netherlands tar file it was showing 3.3gb.
Also the tar sizes where a bit strange : RO CNX 3.6gb - NL TDP 3.4gb. So I would imagine that extra 200mb might be an issue for the partition size (suspecting bloatware maybe?).
Long story short, the tar file I was trying was the issue and downloading a different CSC file solved this for me.
Also, I tried an advice from the forum, where you extract the recovery.img and convert to tar and first flash that tar before the ROM, but that did not work in this case.
Thank you for the replies and support.
Does it void the warranty ? I am also on 4.4.4 ANK version and want to update fo 5.0.1 BOC3.
Sent from my SM-N910F using XDA Free mobile app
I installed the BOB4 like said willcor and do an antutu and, I know that it are subjective information, but I was exhausted of see the Meizu above our fairy note 4 (including with the last 4.4.4), but now, I will sleep much more well than yesterday...
Beko68 said:
Does it void the warranty ? I am also on 4.4.4 ANK version and want to update fo 5.0.1 BOC3.
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
If you're talking about knox (hehe of course, what else) knox still 0x0 after installation...
Doing this kept my knox counter at 0x0, but I did not root or install any custom recovery.
Slightly off topic but I would stay away from BOC3. Many people I know have had problems with BOC3 Firmware.
I am going to be re-flashing BOC3 when I get back home... I must admit when I flashed BOC3 I didn't do a fresh wipe before flashing it so might have been my problem.
Have you wiped your phone before flashing the firmware?
BNerd89 said:
Slightly off topic but I would stay away from BOC3. Many people I know have had problems with BOC3 Firmware.
I am going to be re-flashing BOC3 when I get back home... I must admit when I flashed BOC3 I didn't do a fresh wipe before flashing it so might have been my problem.
Have you wiped your phone before flashing the firmware?
Click to expand...
Click to collapse
Yes, I wiped from the recovery before and after the BOC3 upgrade and I must say that I like how BOC3 feels.
Battery life feels about the same for me - 50% when I get home (9-5), considering i have BT on all day as i have a smartwatch paired, exchange account, 3 gmails, skype push and a few others.
Love the new Smart Lock features with Trusted Places an On Body Detection.
One thing I noticed, manual check for updates on Security Policy Updates does not give any results, not sure if that is working correctly.
I tried rooting my galaxy j7 with Odin and the feedback I get Is binary size too large
Kindly help me out
#19
I have fixed when up wrong file pit
My phone is samsung note9 128gb
When i try to up file pit on rom . I had loss my store from 128gb to 32gb
I don't find any solotion on web
And i have go to setting , open development setting. Choose lock OEM. After that my phone restart and recover to 128gb
Please share this solution . I hope it can help many people up wrong file pit and loss data store like me .
File up wrong pit file odin by Lock Oem
Recover Lost data store .
need urgent help really.
my phone has been rooted and has twrp installed for months now with no issues, all of a sudden my phone rebooted to the samsung logo screen with the mentioned error message. i have no idea how and why this error has occured but my phone wont boot to system. i really dont want flash stock firmware as i havent backed things up, is there a way to fix this issue with out doing a full wipe?
you might have accidentally disable oem unlock. so phone is bricked , and you need to flash stock firmware with odin , no other choices . and as you know knox counter will stay 0x1 , root or no root, once you break knox its permanent as knox is hardware, once you root it break an electronic fuse so once you flash stock firmware I really suggest you to install custom rom and twrp again as many things will be blocked if you stay on stock firmware as your device will stay marked as " rooted "
robhug said:
you might have accidentally disable oem unlock. so phone is bricked , and you need to flash stock firmware with odin , no other choices . and as you know knox counter will stay 0x1 , root or no root, once you break knox its permanent as knox is hardware, once you root it break an electronic fuse so once you flash stock firmware I really suggest you to install custom rom and twrp again as many things will be blocked if you stay on stock firmware as your device will stay marked as " rooted "
Click to expand...
Click to collapse
Yeah I had to do firmware install in the end. It's just crazy though. I very rarely go into dev options, I had noto kernel installed and everything on stock aqh3, rooted with magisk and everything worked great, so annoying as this happened at 3am and I have slow internet connection and took me 2 hours to download the 3.5gb firmware file. Urgh o was on the verge of installing a custom rom too, ah well good job I had a lot of stuff saved in Samsung cloud.
sofir786 said:
Yeah I had to do firmware install in the end. It's just crazy though. I very rarely go into dev options, I had noto kernel installed and everything on stock aqh3, rooted with magisk and everything worked great, so annoying as this happened at 3am and I have slow internet connection and took me 2 hours to download the 3.5gb firmware file. Urgh o was on the verge of installing a custom rom too, ah well good job I had a lot of stuff saved in Samsung cloud.
Click to expand...
Click to collapse
yes hopefully cloud is our new god ^^ yes its annoying I agree but its also a great feeling to begin with a clean phone like new after a reset , and I have also a crappy download speed so yes its a pain to download 4gb , and even better when its corrupted and need to download agin good luck with your device
Hey guys I need help.
My phone got bricked as you said (I accidentally turned off OEM unlock on my rooted phone) so I tried to flash stock firmware, but odin fails and on my phone it says (sw rev. check fail. device:3 binary:2). Plz help!
My phone: S8+
FIRMWARE: CRF7
FRP LOCK: ON
OEM LOCK: ON
Just had the very same problem meself ?
Thank god for Odin and https://updato.com/
Bt like previous posters says its like havin a new phone apart from samsung pay not working
Can someone help??
I got the "FRP lock" on my Samsung S8 (Exynos) and tried to flash Stock Oreo but Odin fails and the device shows "KERNEL REV. CHECK FAIL. DEVICE:3 BINARY:2".
This stock Samsung Rom worked earlier today so it should be the right Rom for my phone.
Also tried to flash TWRP recovery via AP in Odin which failed with "RFP lock" message showing on the device..
I tried to add a snapshot here but couldn't.
Anyone please, I'm helpless..
nattyniz said:
Can someone help??
I got the "FRP lock" on my Samsung S8 (Exynos) and tried to flash Stock Oreo but Odin fails and the device shows "KERNEL REV. CHECK FAIL. DEVICE:3 BINARY:2".
This stock Samsung Rom worked earlier today so it should be the right Rom for my phone.
Also tried to flash TWRP recovery via AP in Odin which failed with "RFP lock" message showing on the device..
I tried to add a snapshot here but couldn't.
Anyone please, I'm helpless..
Click to expand...
Click to collapse
Your issue is trying to flash older firmware than what is on your phone. You will need to download firmware with bootloader ver. 3 or higher ( bl ver no. is 5th number from right of firmware name )
Flashing twrp failed because of locked bootloader.
spawnlives said:
Your issue is trying to flash older firmware than what is on your phone. You will need to download firmware with bootloader ver. 3 or higher ( bl ver no. is 5th number from right of firmware name )
Flashing twrp failed because of locked bootloader.
Click to expand...
Click to collapse
That helped. Flashing the right version worked just fine.
Thanks!!
FRP lock
Hi people,
I got the "FRP lock" on my Samsung S8 SM-G950F(Exynos) and tried to flash Stock Oreo but when I press start Odin say PASS but recovery won't start.
please help
i flashed my S8 SM-G9500 variant however the phone has been locked and it is saying that i need to see the samsung service provider for the device has been locked. how can i solve this problem
Mark Nyombi said:
i flashed my S8 SM-G9500 variant however the phone has been locked and it is saying that i need to see the samsung service provider for the device has been locked. how can i solve this problem
Click to expand...
Click to collapse
can you get a pic of the screen youre talking about?
Hello guys i rooted my S8+ G-955F and i turned off usb debugging and ome lock
And i have android 9 installed on my device, i tried all the way but for nothink , any help please