Related
Hi all! Im not a motorola user of any sorts, but a friend of mine, who's not a great english speaker and doesn't have an xda account, bricked, or at least so it seems, his Moto X 2014 (xt1097).
He tells me that Motorola and Google now include a checkbox in the "developer options" which, without being checked, will not allow the user to unlock the bootloader via the almighty fastboot oem unlock command.
That being said, the problem is now pretty clear: he cant access that dev option setting, because of the initial bootloop, thus being stuck with an unlock-able bootloader...
I know that it's a not good practice to go all gung ho flashing roms, without a unlocked bootloader and TWRP installed; at least I wouldn't sleep easy without them.
So... what's next? Is there a RSD method to flash the phone back to complete stock? Is there a way to check that checkbox via ADB? Any input will be much appreciated.
ad astra said:
He tells me that Motorola and Google now include a checkbox in the "developer options" which, without being checked, will not allow the user to unlock the bootloader via the almighty fastboot oem unlock command.
Click to expand...
Click to collapse
This is only true if he upgraded to 5.1, which it sounds like he did.
ad astra said:
That being said, the problem is now pretty clear: he cant access that dev option setting, because of the initial bootloop, thus being stuck with an unlock-able bootloader.
Click to expand...
Click to collapse
First what did he do to get into the bootloop? Was he part of the 5.1 soak test and then he tried to flash back to 5.0 to take the OTA?
He needs to try to get into bootloader mode. When the screen powers on, he needs to press and hold the power button until the screen turns off. Then immediately press and hold the vol down button, then after 2 seconds or so, w/o releasing the volume down, press and hold the power button. Keep pressing both power and vol down and hold them for about 4 seconds then release them both. That should get him into bootloader mode.
ad astra said:
I know that it's a not good practice to go all gung ho flashing roms, without a unlocked bootloader and TWRP installed; at least I wouldn't sleep easy without them.
Click to expand...
Click to collapse
You in fact cannot flash a ROM with a locked bootloader.
ad astra said:
So... what's next? Is there a RSD method to flash the phone back to complete stock? Is there a way to check that checkbox via ADB? Any input will be much appreciated.
Click to expand...
Click to collapse
First, get him into bootloader mode. Then you need to tell us what version of the bootloader is he on? Is it 60.14 or 60.11? And is this the Brazil XT1097?
JulesJam said:
This is only true if he upgraded to 5.1, which it sounds like he did.
Click to expand...
Click to collapse
Yep, that's exactly the case.
JulesJam said:
First what did he do to get into the bootloop? Was he part of the 5.1 soak test and then he tried to flash back to 5.0 to take the OTA?
Click to expand...
Click to collapse
If i'm not mistaken it was the other way around. He tried to update to 5.1 (I believe that the zip was form a different vendor).
JulesJam said:
He needs to try to get into bootloader mode. When the screen powers on, he needs to press and hold the power button until the screen turns off. Then immediately press and hold the vol down button, then after 2 seconds or so, w/o releasing the volume down, press and hold the power button. Keep pressing both power and vol down and hold them for about 4 seconds then release them both. That should get him into bootloader mode.
Click to expand...
Click to collapse
Already tried. The bootloader is locked. Tried to unlock (with fastboot), error appears which points to the checkbox in developer tools not being set to true.
JulesJam said:
You in fact cannot flash a ROM with a locked bootloader.
Click to expand...
Click to collapse
I understand what you mean, I meant that you can flash updates from sdcard with stock recovery.
JulesJam said:
First, get him into bootloader mode. Then you need to tell us what version of the bootloader is he on? Is it 60.14 or 60.11? And is this the Brazil XT1097?
Click to expand...
Click to collapse
Btw, he ended up sending the phone back to his carrier, for RMA, and got a new one. So.. we didn't check that. What's the difference between both? Now he managed to flash (with unlocked bootloader) the 5.1 rom and his bootloader version shows 60.16.
On the other hand, the phone's argentinian made. The flashing process which resulted in brick was as follows: 1) updated the stock 4.x.x movistar argentina rom with a brazilian 4.4.4 rom over stock recovery (he tells me that, as both roms are latinamerican, recovery update of those roms is possible). Then he seems to have updated to 5.1 soak. And then, and I dont reaaaly understand why.... he flashed another 5.1 soak that should have been only used for upgrading directly from 5.0.
The point is, he got locked out of any possible recovery method by being unable to unlock his bootlader (which we could access but was obviously locked for flashing).
Anyway, I think this thread will be of general interest so I'll continue to provide info on the case.
ad astra said:
Already tried. The bootloader is locked. Tried to unlock (with fastboot), error appears which points to the checkbox in developer tools not being set to true.
Click to expand...
Click to collapse
That wasn't the point of getting into bootloader mode. The point was to flash back to stock system. That would stop the bootloop then he could boot into system, go into settings and enable unlocking.
---------- Post added at 12:28 AM ---------- Previous post was at 12:27 AM ----------
ad astra said:
Btw, he ended up sending the phone back to his carrier, for RMA, and got a new one.
Click to expand...
Click to collapse
That is fine if that was an option, but those CLNR devices from the carriers are crap. All he had to do when he was in bootloader mode was flash back to stock.
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
ad astra said:
The point is, he got locked out of any possible recovery method by being unable to unlock his bootlader (which we could access but was obviously locked for flashing).
Click to expand...
Click to collapse
No he did not. If you can get into bootloader mode then you can flash system back to stock, then you can boot and enable the OEM unlocking.
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
ad astra said:
the 5.1 rom and his bootloader version shows 60.16.
Click to expand...
Click to collapse
OK so this is yet another 5.1 bootloader version. The only one I have seen is 60.14.
JulesJam said:
That wasn't the point of getting into bootloader mode. The point was to flash back to stock system. That would stop the bootloop then he could boot into system, go into settings and enable unlocking.
---------- Post added at 12:28 AM ---------- Previous post was at 12:27 AM ----------
That is fine if that was an option, but those CLNR devices from the carriers are crap. All he had to do when he was in bootloader mode was flash back to stock.
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
No he did not. If you can get into bootloader mode then you can flash system back to stock, then you can boot and enable the OEM unlocking.
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
OK so this is yet another 5.1 bootloader version. The only one I have seen is 60.14.
Click to expand...
Click to collapse
But how? His bootloader was locked, and we even tried to use recovery to flash back a stock image which returned an error. We tried this using adb sideload and it didn't work. We even edited the .xml file and tried the nokia flashing tool, which also resulted in a failed attempt.
Maybe im missing something... but I only know of 3 methods of flashing via bootloader:
1) fastboot command.
2) adb sideload.
3) vendor flash tool (like Odin, and nokias RDS or something like that).
ad astra said:
The flashing process which resulted in brick was as follows: 1) updated the stock 4.x.x movistar argentina rom with a brazilian 4.4.4 rom over stock recovery (he tells me that, as both roms are latinamerican, recovery update of those roms is possible). Then he seems to have updated to 5.1 soak. And then, and I dont reaaaly understand why.... he flashed another 5.1 soak that should have been only used for upgrading directly from 5.0. .
Click to expand...
Click to collapse
Thanks, so he tried to take a different model's 5.1 OTA when already on 5.1.
---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------
ad astra said:
But how?
Click to expand...
Click to collapse
mfastboot flash system system.img
You need the system.img file of course for your model. This is why I encourage everyone to use Motorola Device Manager to upgrade - it leaves a copy of the image files on your computer.
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
ad astra said:
But how? His bootloader was locked,
Click to expand...
Click to collapse
You don't need an unlocked bootloader to flash a signed image. Unlocking your bootloader is only needed to flash unsigned images and to disable write protection.
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
ad astra said:
we even tried to use recovery to flash back a stock image which returned an error. We tried this using adb sideload and it didn't work.
Click to expand...
Click to collapse
You don't do it through recovery - you do it through bootloader mode.
JulesJam said:
Thanks, so he tried to take a different model's 5.1 OTA when already on 5.1.
---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------
mfastboot flash system system.img
You need the system.img file of course for your model. This is why I encourage everyone to use Motorola Device Manager to upgrade - it leaves a copy of the image files on your computer.
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
You don't need an unlocked bootloader to flash a signed image. Unlocking your bootloader is only needed to flash unsigned images and to disable write protection.
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
You don't do it through recovery - you do it through bootloader mode.
Click to expand...
Click to collapse
Nice. I was about to test that :/ But i desisted because i thought it was the same as the normal fastboot... Damn, why didn't I try that when I stumbled upon that yesterday......
Thanks for the info! And also thanks for the tip on the motorola deivce manager upgrade thing. The LG suite does the same thing and so I keep my stock image safely stored.
ad astra said:
Maybe im missing something... but I only know of 3 methods of flashing via bootloader:
1) fastboot command.
Click to expand...
Click to collapse
Yes, this works. You don't need an unlocked bootloader to do it, but you do need mfastboot if the image file you have is a single image file. If you have the system already broken down into chunks, you can use regular fastboot.
ad astra said:
3) vendor flash tool (like Odin, and nokias RDS or something like that).
Click to expand...
Click to collapse
The one you want for a Moto X is the Motorola tool - RSDLite. RSDLite has mfastboot as a part of it.
You needed mfastboot to flash a single file system.img. Regular fastboot from the SDK won't work. mfastboot is motorola's version of fastboot.
Regular fastboot can only flash chunks of system. I think they have to be 256MB or less in size.
---------- Post added at 12:44 AM ---------- Previous post was at 12:41 AM ----------
ad astra said:
Nice. I was about to test that :/ But i desisted because i thought it was the same as the normal fastboot... Damn, why didn't I try that when I stumbled upon that yesterday......
Click to expand...
Click to collapse
I was trying to help you, but you didn't post back.
JulesJam said:
I was trying to help you, but you didn't post back.
Click to expand...
Click to collapse
Dont get me wrong. You did help me (thats why i left u a thanks) :good: My friend just went and did his thing on his own. I probably live in a different time zone, and my work doesn't allow me to be online the whole day. It was really late when I posted, I wasn't expecting a reply on the fly so I went to sleep. I continued this thread just because of curiosity.
On a side note, my friend checked his phone and, it seem'd alright, closed box and all. He worked a time at Motorola so he knows what was getting into. It seems the whole mess happened because of a forum post which indicated that he was flashing a soak test rom, when it was actually a final release (or something like that). This last, ended up messing up his system.
The only way to recover the original phone would have been to flash 5.1 or newer firmware to it. Had the bootloader been unlocked he could have just flashed 5.0.x without an issue(skipping motoboot and gpt).
Nobody should ever mess around with soak files unless they have an unlocked bootloader.
Steve-x said:
The only way to recover the original phone would have been to flash 5.1 or newer firmware to it. Had the bootloader been unlocked he could have just flashed 5.0.x without an issue(skipping motoboot and gpt).
Nobody should ever mess around with soak files unless they have an unlocked bootloader.
Click to expand...
Click to collapse
Agreed. Very poor judgement on behalf of my friend. Lesson learnt I guess, now he's bootloader is unlocked and he managed to flash 5.1 as previously intended.
It seems that the guy who posted the soak mistakenly posted the wrong file and caused a lot of problems for a lot of people... but, nevertheless u cant trust everything to go right... so that's my friends own fault for not unlocking, backing up and investigating enough.
i had the same problem.... any solution for bootloop Moto X 2014 whith Locked Bootloader?
Lussardi said:
i had the same problem.... any solution for bootloop Moto X 2014 whith Locked Bootloader?
Click to expand...
Click to collapse
Have you tried erasing cache and data? If that does not work you could flash your stock firmware.
Could you tell us what you did to get into your bootloop. More info helps us know how to fix your problem.
Sent from my XT1095 using Tapatalk
AGISCI said:
Have you tried erasing cache and data? If that does not work you could flash your stock firmware.
Could you tell us what you did to get into your bootloop. More info helps us know how to fix your problem.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I tried all options, fastboot erase userdata, fastboot erase cache, Flash lollipop 5.1 via RSD nothing seems works
Lussardi said:
I tried all options, fastboot erase userdata, fastboot erase cache, Flash lollipop 5.1 via RSD nothing seems works
Click to expand...
Click to collapse
You still have not told us what you did that caused the bootloop.
Sent from my XT1095 using Tapatalk
AGISCI said:
You still have not told us what you did that caused the bootloop.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I do not know ... a customer came in for repair, so do not know the reason why he stayed so.
I have a N920p Sprint Note 5. It had 5.1.1 i rooted it and flashed 6.0.1 stock rom with Odin. I then rooted that and have flashed DarthStalker and MoAR. I had Moar on it and had someone remote unlock it. It wouldnt accept my tmobile sim still. It wasnt saying Invalid sim just wouldnt connect to any network, so I reflashed stock rom with odin and had it remote unlocked again. Suposedly its unlocked right now but when Tmobile sim is inserted it will not connect to network. Ive tried changing the mode and multiple APN settings. My question is if a phone is unlocked why does flashing the phone with a different rom relock it. and can anyone tell me what I AM DOING WRONG. I contacted sprint about having them unlock the phone before I had it remote unlocked and they said that they unlocked it but it would take 48 hours I waited and called back and the new rep said phone as already unlocked but it would still say invalid sim when i inserted my sim card. Pulling my hair out here. HELP?!
Friend. Flash stock 6.0, root it, recovery, flash lamlazy rom, insert your tmobile sim...then get back with ur result
---------- Post added at 02:46 PM ---------- Previous post was at 02:45 PM ----------
Make sure oem unlock is enabled
kumuyi said:
Friend. Flash stock 6.0, root it, recovery, flash lamlazy rom, insert your tmobile sim...then get back with ur result
---------- Post added at 02:46 PM ---------- Previous post was at 02:45 PM ----------
Make sure oem unlock is enabled
Click to expand...
Click to collapse
once i flash new rom I will loose the remote unlock and phone will go back to invalid sim
Apathy772 said:
once i flash new rom I will loose the remote unlock and phone will go back to invalid sim
Click to expand...
Click to collapse
Will i used sprint and didn't face any of such. I only did what i asked you to do and I'm in Africa
kumuyi said:
Will i used sprint and didn't face any of such. I only did what i asked you to do and I'm in Africa
Click to expand...
Click to collapse
im in america and it will relock my phone
Apathy772 said:
im in america and it will relock my phone
Click to expand...
Click to collapse
Well then, do as i did, sell it, and buy n920c. Save ur self the hassle
Is it possible to have (systemless) xposed installed with magisk with a locked bootloader ?
robuser007 said:
Is it possible to have (systemless) xposed installed with magisk with a locked bootloader ?
Click to expand...
Click to collapse
No, because you need root to use Xposed wich requires TWRP ergo an unlocked bootloader.
gee2012 said:
No, because you need root to use Xposed.
Click to expand...
Click to collapse
But you can use systemless root.
robuser007 said:
But you can use systemless root.
Click to expand...
Click to collapse
Yes but how are you going to flash it? With stock recovery its not possible. Btw locking a bootloader when you plan to root or use mods is NEVER a good idea, besides that in the case of OnePlus it doesn`t void warranty so it would be unwise to not unlock or relock the bootloader.
If your device gets bricked while your bootloader is locked, you're going to get screwed. The most you can hope for is a complete phone reformat through one of the unbrick guides
Can't we flash bootloader from fastboot or recovery in op3?
Used to flash I'm Redmi note 3 and then twrp worked fine even with locked bootloader
---------- Post added at 03:15 PM ---------- Previous post was at 03:12 PM ----------
Just found the sticky post in guides section, u can flash bootloader file from fastboot while still keeping twrp recovery intact.
Hope that's what you are looking for
The thread in guides section is one plus 3t resources.
Navi44 said:
Can't we flash bootloader from fastboot or recovery in op3?
Used to flash I'm Redmi note 3 and then twrp worked fine even with locked bootloader
---------- Post added at 03:15 PM ---------- Previous post was at 03:12 PM ----------
Just found the sticky post in guides section, u can flash bootloader file from fastboot while still keeping twrp recovery intact.
Hope that's what you are looking for
The thread in guides section is one plus 3t resources.
Click to expand...
Click to collapse
Do you have the link, can't find the thread ?
robuser007 said:
Do you have the link, can't find the thread ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3t/how-to/p-oneplus-3t-resource-t3510236/page3
Need help badly:
I Lost OEM unlock option when I installed a custom rom. I have waited for 7 days and the option wouldnt appear in the settings. I believe if I reboot this, Id be stuck in binary blah blah and Id be back in stock rom again and be jailed for 7 days.
Im currently rooted. Ive read an article about DrKetan OEM patch. Can I be able to install that without using TWRP? Like the app Flashify or Flashfire?
Any insights please?
Thanks
I wish to restore my TWRP backup but I cant get to TWRP as I believe id be stuck in " only official binary blah blah"
I first unlocked the boot loader but didn't worked than I was unable to find the one unlock option again in developer mode even after reflashing the firmware.
In the Odin mode it is written oem lock off
Can somebody guide me how to show that option again
sangreal327 said:
Need help badly:
I Lost OEM unlock option when I installed a custom rom. I have waited for 7 days and the option wouldnt appear in the settings. I believe if I reboot this, Id be stuck in binary blah blah and Id be back in stock rom again and be jailed for 7 days.
Im currently rooted. Ive read an article about DrKetan OEM patch. Can I be able to install that without using TWRP? Like the app Flashify or Flashfire?
Any insights please?
Thanks
Click to expand...
Click to collapse
Some roms hide the OEM unlock option to avoid accidentally switching it and then locking you out ie only official binaries. Search in the thread of the rom you are using to see if that is the case.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Malikzeeshanarif said:
I first unlocked the boot loader but didn't worked than I was unable to find the one unlock option again in developer mode even after reflashing the firmware.
In the Odin mode it is written oem lock off
Can somebody guide me how to show that option again
Click to expand...
Click to collapse
Try using this great guide
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
stonedpsycho said:
Some roms hide the OEM unlock option to avoid accidentally switching it and then locking you out ie only official binaries. Search in the thread of the rom you are using to see if that is the case.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Try using this great guide
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Click to expand...
Click to collapse
Does installing a new firmware Will replace the one unlock or not
i ended up switching to a note 8 last week and i cant get updates even though i am using an att sim card on an att phone, this phone was given to me by a family member and it was frp locked but i got it unlocked, it was on the march update but because of the great people of xda i was able to update it through recovery to the april update, i couldnt go any further because i updated too far on bootloader 3 and couldnt get upgraded to bootloader 4 or 5, i tried odin but it will either immediately stop after clicking start saying 0 succeeded fail 1 but it doesnt have the red fail message and other times it will just be stuck on setup connection or initialization and i cant get it to work at all and i would like to get updates because maybe the note 8 will eventually get android 9(will be very late but it will be time to switch carriers anyways by the time it comes out)
Use this Odin version :
https://drive.google.com/file/d/1AAEvLMPzhib2AlvvZqLL8oVhxnI_lqgJ/view?usp=drivesdk
Also
This is the ATT Note 8 thread with latest firmware.
https://forum.xda-developers.com/att-galaxy-note-8/how-to/att-oreo-ota-updates-t3756025
---------- Post added at 09:01 PM ---------- Previous post was at 08:59 PM ----------
Also another hint : use another USB Port
Cool Person said:
Use this Odin version :
https://drive.google.com/file/d/1AAEvLMPzhib2AlvvZqLL8oVhxnI_lqgJ/view?usp=drivesdk
Also
This is the ATT Note 8 thread with latest firmware.
https://forum.xda-developers.com/att-galaxy-note-8/how-to/att-oreo-ota-updates-t3756025
---------- Post added at 09:01 PM ---------- Previous post was at 08:59 PM ----------
Also another hint : use another USB Port
Click to expand...
Click to collapse
ok, ive tried several usb ports but hopefully this version of odin works better because i tried rooting my s7 before i got a note and it worked fine with my version of odin
billdauterive23 said:
ok, ive tried several usb ports but hopefully this version of odin works better because i tried rooting my s7 before i got a note and it worked fine with my version of odin
Click to expand...
Click to collapse
and now my phone isnt detected by odin at all
billdauterive23 said:
and now my phone isnt detected by odin at all
Click to expand...
Click to collapse
Does it get detected by pc? is this after flashing or just odin 3.13?
Cool Person said:
Use this Odin version :
https://drive.google.com/file/d/1AAEvLMPzhib2AlvvZqLL8oVhxnI_lqgJ/view?usp=drivesdk
Also
This is the ATT Note 8 thread with latest firmware.
https://forum.xda-developers.com/att-galaxy-note-8/how-to/att-oreo-ota-updates-t3756025
---------- Post added at 09:01 PM ---------- Previous post was at 08:59 PM ----------
Also another hint : use another USB Port
Click to expand...
Click to collapse
I was able to get it to detect my phone but it still either freezes at setup connection, intialization or it will fail with a complete write operation fail error or a device info error, and most of the time it just stops after setup connection and doesn't continue, I have tried several usb ports and cords and I don't have another computer to use right at this moment, I was able to flash my s7 just fine with odin 3.13.1 so I have no idea why my new note phone is being a pain in the a**
billdauterive23 said:
I was able to get it to detect my phone but it still either freezes at setup connection, intialization or it will fail with a complete write operation fail error or a device info error, and most of the time it just stops after setup connection and doesn't continue, I have tried several usb ports and cords and I don't have another computer to use right at this moment, I was able to flash my s7 just fine with odin 3.13.1 so I have no idea why my new note phone is being a pain in the a**
Click to expand...
Click to collapse
How about smart switch on the PC? Does it recognize it as well and can you do a firmware recovery using smart switch?
Last bet I would bring it to a Samsung shop and get them to fix it under warranty.
BluePhnx said:
How about smart switch on the PC? Does it recognize it as well and can you do a firmware recovery using smart switch?
Last bet I would bring it to a Samsung shop and get them to fix it under warranty.
Click to expand...
Click to collapse
It doesn't even say there is an update in smart switch, the phone works it's just I can't get otas from att even though I have an att sim card and the phone is att branded, it's just a minor annoyance because I would like to have the latest version and have it be able to be updated maybe it's because the phone is still in the 7 day rmm lock state
billdauterive23 said:
It doesn't even say there is an update in smart switch, the phone works it's just I can't get otas from att even though I have an att sim card and the phone is att branded, it's just a minor annoyance because I would like to have the latest version and have it be able to be updated maybe it's because the phone is still in the 7 day rmm lock state
Click to expand...
Click to collapse
7 day rmm lock state? Are talking about the OEM unlock switch in developer options? That's only for the exynos models Sm-n950f/ds. You won't get that on snapdragon because you have a locked bootloader. So rmm and the 7 day wait period doesn't affect you. But if its something else, sorry.
Your device is SM-N950U1 or SM-N950U?
Maybe take it back to att and see if they have any luck on updating the phone if not ask them for a replacement one.
BluePhnx said:
7 day rmm lock state?
Your device is SM-N950U1 or SM-N950U?
Maybe take it back to att and see if they have any luck on updating the phone if not ask them for a replacement one.
Click to expand...
Click to collapse
So the rmm lock on the note 8 and above keeps you from enabling oem unlock for 7 days which could keep odin from flashing any firmwares official or not. My model number is N950U
If I can't fix it myself I'll just deal with it for now and get it fixed later because its not really bothering me too much other than I just got this phone from someone else
billdauterive23 said:
So the rmm lock on the note 8 and above keeps you from enabling oem unlock for 7 days which could keep odin from flashing any firmwares official or not. My model number is N950U
Click to expand...
Click to collapse
Just edited my post above yours.
Your phone has a locked bootloader!
The OEM unlock is only for exynos international models.
Won't do you any good.
BluePhnx said:
Just edited my post above yours.
Your phone has a locked bootloader!
The OEM unlock is only for exynos international models.
Won't do you any good.
Click to expand...
Click to collapse
Yeah, but the thing is that the oem unlock switch might also be a switch that allows flashing official firmwares because it was also kinda like that on my old phone in the sense that if it was checked not only was factory reset protection disabled but it also allowed me to flash official firmwares without as much trouble, but I'm not really sure so correct me if I'm wrong
billdauterive23 said:
So the rmm lock on the note 8 and above keeps you from enabling oem unlock for 7 days which could keep odin from flashing any firmwares official or not. My model number is N950U
Click to expand...
Click to collapse
Okay you'll need the comsey Odin to flash the sm-n950u1 firmware on your sm-n950u model.
Do a search on how to convert sm-n950u to sm-n950u1.
On is Samsung carrier unlock version and the other is carrier version. (Doesnt mean bootloader unlock, both are bootloader locked)
BluePhnx said:
Okay you'll need the comsey Odin to flash the sm-n950u1 firmware on your sm-n950u model.
Do a search on how to convert sm-n950u to sm-n950u1.
On is Samsung carrier unlock version and the other is carrier version. (Doesnt mean bootloader unlock, both are bootloader locked)
Click to expand...
Click to collapse
Right, also will this still work if I'm on oreo
billdauterive23 said:
Yeah, but the thing is that the oem unlock switch might also be a switch that allows flashing official firmwares because it was also kinda like that on my old phone in the sense that if it was checked not only was factory reset protection disabled but it also allowed me to flash official firmwares without as much trouble, but I'm not really sure so correct me if I'm wrong
Click to expand...
Click to collapse
Samsung changed that since the s8 days. SNAPDRAGONs won't get the OEM unlock switch at all anymore it's useless now so you'll never see it in developer options because they locked down the bootloader for the USA/Canada models which are snapdragons.
BluePhnx said:
Samsung changed that since the s8 days. SNAPDRAGONs won't get the OEM unlock switch at all anymore it's useless now so you'll never see it in developer options because they locked down the bootloader for the USA/Canada models which are snapdragons.
Click to expand...
Click to collapse
Ok, so all I need to know now is if I can flash the u1 firmware even though I'm on Android 8 because I thought I heard that it was patched with that update
billdauterive23 said:
Right, also will this still work if I'm on oreo
Click to expand...
Click to collapse
It's just a modified Odin that skips the device model check. Be careful though.
Just make sure you have the right model.
What's your baseband say after the n950..... ?
---------- Post added at 08:08 AM ---------- Previous post was at 08:06 AM ----------
billdauterive23 said:
Ok, so all I need to know now is if I can flash the u1 firmware even though I'm on Android 8 because I thought I heard that it was patched with that update
Click to expand...
Click to collapse
Hmm good question!
---------- Post added at 08:12 AM ---------- Previous post was at 08:08 AM ----------
Here read this thread out.
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-sm-n950u-u1-t3685884/page1
Looks like you'll need a new modified version of Odin for oreo. Read the first post on first page.
BluePhnx said:
It's just a modified Odin that skips the device model check. Be careful though.
Just make sure you have the right model.
What's your baseband say after the n950..... ?
---------- Post added at 08:08 AM ---------- Previous post was at 08:06 AM ----------
Hmm good question!
---------- Post added at 08:12 AM ---------- Previous post was at 08:08 AM ----------
Here read this thread out.
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-sm-n950u-u1-t3685884/page1
Looks like you'll need a new modified version of Odin for oreo. Read the first post on first page.
Click to expand...
Click to collapse
ok, i might see if i can downgrade to nougat because i have a feeling the oreo version is seriously borked
billdauterive23 said:
ok, i might see if i can downgrade to nougat because i have a feeling the oreo version is seriously borked
Click to expand...
Click to collapse
You'll better be on bootloader v3 then because if you'd on bootloader v4 you can't downgrade to nougat.
To find out the bootloader version it's the 5 number from the right of this n950usqu"5"crg7 notice the "5" that's the bootloader version.
You can find by baseband in about phone software info or dial *#1234# (look at the ap line)
You can go up but you can't go down!
Sent from my SM-N950F using Tapatalk