Wanted to find out if there was a way to revert to the stock rom without hassle.
Yeah, you can use LMSA for that.
arsradu said:
Yeah, you can use LMSA for that.
Click to expand...
Click to collapse
will it lock my bootloader though? Also did you face any issues while using that
rowhen_ said:
will it lock my bootloader though? Also did you face any issues while using that
Click to expand...
Click to collapse
No. And no.
Just make sure your power is stable, so it doesn't interrupt the flashing process.
Also, if you're doing that, I'm curious whether or not your OEM Unlocking option is still ON after flashing stock ROM. It should be ON. If it's not, don't attempt to lock back the bootloader or you may end up in a brick.
arsradu said:
No. And no.
Just make sure your power is stable, so it doesn't interrupt the flashing process.
Also, if you're doing that, I'm curious whether or not your OEM Unlocking option is still ON after flashing stock ROM. It should be ON. If it's not, don't attempt to lock back the bootloader or you may end up in a brick.
Click to expand...
Click to collapse
yeah, it's turned on by default
rowhen_ said:
yeah, it's turned on by default
Click to expand...
Click to collapse
Is it still on after flashing back stock ROM?
Cause, in my case, it's not. It's greyed out, and turned OFF. And it's driving me crazy, cause I don't know why is it still OFF.
arsradu said:
Is it still on after flashing back stock ROM?
Cause, in my case, it's not. It's greyed out, and turned OFF. And it's driving me crazy, cause I don't know why is it still OFF.
Click to expand...
Click to collapse
i havent flashed the stock rom yet so cant say, would it pose an issue if the OEM unlocking button is greyed out?
rowhen_ said:
i havent flashed the stock rom yet so cant say, would it pose an issue if the OEM unlocking button is greyed out?
Click to expand...
Click to collapse
No, but it would pose an issue if it's OFF and you want to relock the bootloader. Don't even attempt relocking your bootloader if that option is OFF.
That option can be:
1. active (not greyed out) with toggle ON or OFF.
2. inactive (greyed out) with toggle ON or OFF.
What's important is the position of that toggle. Because, what that says is that the bootloader is still unlockable.
YES, it is unlocked right now. And you might even get a message telling you that, but if the toggle is OFF, that means the bootloader is no longer unlockable (or get_unlock_ability=0).
Why is this bad? Well, because if you want to relock the bootloader, and something goes wrong, and you end up in an unbootable situation (with an error like "no valid operating system could be found"), you won't be able to unlock the bootloader again to fix your issue, or at least flash another ROM or something so you can boot back into the OS.
Fastboot will complain that the OEM Unlocking option is OFF, and will not allow you to flash anything. And obviously, you won't be able to boot back into the OS to turn it on.
So, be very careful about that option!
If you don't plan on relocking the bootloader, no worries. But if you do, be very, very careful what does that option say.
You can read more about it here.
arsradu said:
No, but it would pose an issue if it's OFF and you want to relock the bootloader. Don't even attempt relocking your bootloader if that option is OFF.
That option can be:
1. active (not greyed out) with toggle ON or OFF.
2. inactive (greyed out) with toggle ON or OFF.
What's important is the position of that toggle. Because, what that says is that the bootloader is still unlockable.
YES, it is unlocked right now. And you might even get a message telling you that, but if the toggle is OFF, that means the bootloader is no longer unlockable (or get_unlock_ability=0).
Why is this bad? Well, because if you want to relock the bootloader, and something goes wrong, and you end up in an unbootable situation (with an error like "no valid operating system could be found"), you won't be able to unlock the bootloader again to fix your issue, or at least flash another ROM or something so you can boot back into the OS.
Fastboot will complain that the OEM Unlocking option is OFF, and will not allow you to flash anything. And obviously, you won't be able to boot back into the OS to turn it on.
So, be very careful about that option!
If you don't plan on relocking the bootloader, no worries. But if you do, be very, very careful what does that option say.
You can read more about it here.
Click to expand...
Click to collapse
That makes sense. Yeah I dont mind the unlocked bootloader, no plans on relocking it.
Also The LMSA doesnt seem to detect my phone, is there like a guide I that I can follow to flash the stock ROM? (I'm currently on PE 12 )
rowhen_ said:
That makes sense. Yeah I dont mind the unlocked bootloader, no plans on relocking it.
Also The LMSA doesnt seem to detect my phone, is there like a guide I that I can follow to flash the stock ROM? (I'm currently on PE 12 )
Click to expand...
Click to collapse
You don't really need a guide. But yeah, LMSA won't detect the phone anymore because of the custom ROM.
You need the Rescue option and you need to enter your IMEI for the device to be detected. Everything else is self explanatory. The device needs to be in fastboot mode for this procedure. And make sure the cable is ok. I would recommend using the original cable.
arsradu said:
You don't really need a guide. But yeah, LMSA won't detect the phone anymore because of the custom ROM.
You need the Rescue option and you need to enter your IMEI for the device to be detected. Everything else is self explanatory. The device needs to be in fastboot mode for this procedure. And make sure the cable is ok. I would recommend using the original cable.
Click to expand...
Click to collapse
I flashed the stock rom and yes, the bootloader option is greyed out but unlocked. But tbh the rom's pretty trash lol. This was the reason I started considering custom rom's in the first place.
rowhen_ said:
I flashed the stock rom and yes, the bootloader option is greyed out but unlocked. But tbh the rom's pretty trash lol. This was the reason I started considering custom rom's in the first place.
Click to expand...
Click to collapse
So the OEM Unlocking option is ON in your case? Could you please help me with a screenshot, for reference? I'm trying to understand why mine is OFF.
Also, which custom ROM did you have before going back to stock ROM?
arsradu said:
So the OEM Unlocking option is ON in your case? Could you please help me with a screenshot, for reference? I'm trying to understand why mine is OFF.
Also, which custom ROM did you have before going back to stock ROM?
Click to expand...
Click to collapse
No Its turned off but greyed out. And the subtext below it says "bootloader already unlocked". Sorry cant share screenshots because I've already switched to lineage os 20. The stock rom was almost unusable
rowhen_ said:
No Its turned off but greyed out. And the subtext below it says "bootloader already unlocked". Sorry cant share screenshots because I've already switched to lineage os 20. The stock rom was almost unusable
Click to expand...
Click to collapse
Ah ok. But why do you say it was almost unusable? I didn’t have any issues with it? Also, in the meantime, I’ve relocked my bootloader, and thank Goodness, everything went fine.
What do you like in LineageOS? Personally I don’t like it.
arsradu said:
Ah ok. But why do you say it was almost unusable? I didn’t have any issues with it? Also, in the meantime, I’ve relocked my bootloader, and thank Goodness, everything went fine.
What do you like in LineageOS? Personally I don’t like it.
Click to expand...
Click to collapse
It was stuttering like crazy, the battery life was surprisingly trash. I prefer Pixel Experience 13 over Lineage OS but I was facing some minor issues with it so stuck with Lineage
rowhen_ said:
It was stuttering like crazy, the battery life was surprisingly trash. I prefer Pixel Experience 13 over Lineage OS but I was facing some minor issues with it so stuck with Lineage
Click to expand...
Click to collapse
That's weird... I've got no stuttering, battery is pretty damn good, so is signal, and I've got IMS services, which are pretty important to me. Also, Tap to Pay now works again, after locking the bootloader.
Well, I'm glad Lineage works for your! I also prefer PE. But...there are some issue right now. And I'm waiting for a new update which could potentially fix them.
Related
[SOLVED] I followed this thread to get everything updated and make sure I was all stock, and then went to bootloader and ran fastboot flashing lock to relock the bootloader. Everything working great now.
I'm trading my Verizon Pixel XL for a normal Pixel, and need to relock the bootloader first. I haven't installed a custom kernal or ROMs or anything, so can I just lock via fastboot safely?
I don't want to do something that will brick it!
I'm aware this is stupid and I'd rather just leave it, but dude is sketched out by warning on startup and won't trade till it's gone :/
Thanks!
[Edit] it should maybe be noted that I haven't installed any updates since rooting, and I'm not sure if those are important first or not?
burnface said:
[SOLVED] I followed this thread to get everything updated and make sure I was all stock, and then went to bootloader and ran fastboot flashing lock to relock the bootloader. Everything working great now.
I'm trading my Verizon Pixel XL for a normal Pixel, and need to relock the bootloader first. I haven't installed a custom kernal or ROMs or anything, so can I just lock via fastboot safely?
I don't want to do something that will brick it!
I'm aware this is stupid and I'd rather just leave it, but dude is sketched out by warning on startup and won't trade till it's gone :/
Thanks!
[Edit] it should maybe be noted that I haven't installed any updates since rooting, and I'm not sure if those are important first or not?
Click to expand...
Click to collapse
Hey man, do you remember which FW built were you on ? NDE63X ?
andrep182 said:
Hey man, do you remember which FW built were you on ? NDE63X ?
Click to expand...
Click to collapse
Yes if you are stock you can safely lock the bootloader.
run
fastboot flashing lock
phone will factory reset and appear frozen on that screen 30seconds or so.
milan187 said:
Yes if you are stock you can safely lock the bootloader.
run
fastboot flashing lock
phone will factory reset and appear frozen on that screen 30seconds or so.
Click to expand...
Click to collapse
Cool man, thanks!
andrep182 said:
Hey man, do you remember which FW built were you on ? NDE63X ?
Click to expand...
Click to collapse
Damn. I honestly don't remember... I didn't do enough with that phone for anything specific to stick out.. Sorry!
burnface said:
Damn. I honestly don't remember... I didn't do enough with that phone for anything specific to stick out.. Sorry!
Click to expand...
Click to collapse
It's all good man. My heart was pounding as I about to hit 'yes' for locking my bootloader. Did the deed and all is well =) Thanks!
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Update: I have returned my device to Google and they processed a replacement
i am just curious, how were planning on flashing a rom with locked bootloader?
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Paradoxxx said:
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Click to expand...
Click to collapse
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Yeah at that point... Not sure what is Google saying about that. Maybe RMA it ?
Saying something like that should work.
"I was using my device, and suddenly it froze and nothing responded. It suddenly rebooted and shown this error message."
gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Sorry didn't get, What do you mean by OP has nothing to loose?
Badger50 said:
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
How did you recover your devices from that state earlier when you did the same thing?
ram4ufriends said:
Sorry didn't get, What do you mean by OP has nothing to loose?
Click to expand...
Click to collapse
since your phone is now essentially a brick, you can try just about anything without worry of bricking your phone.
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
You cannot flash full images, but you can still flash OTAs... download the full OTA instead, and install (sideload) it from the stock recovery. Be sure to select the SAME build number you were on to begin with- eg. If you were on 8.1, use the 8.1 OTA. There will be a mode there for "Apply update from ADB". You put the phone into "sideload mode" and then send the OTA to the phone via adb. This will work regardless whether you have usb debugging enabled or not. Follow the directions given on the included link.
ram4ufriends said:
How did you recover your devices from that state earlier when you did the same thing?
Click to expand...
Click to collapse
I didn't. They are still paperweights sitting in a drawer!
I got the same message yesterday after doing... God knows what. I can't even remember what went wrong.
My first thought was to flash a factory image. But it didn't helped at first. Probably, because i was trying to flash another factory image and not the one that came as stock on my phone.
So if you don't remember, which image it was, try all of them Hopefully, you'll get your phone booted again.
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
dontbeweakvato said:
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
Click to expand...
Click to collapse
Meh...you know how it is bro....**it happens!
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
ArminasAnarion said:
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
Click to expand...
Click to collapse
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
mitchdickson said:
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
ArminasAnarion said:
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
Click to expand...
Click to collapse
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
mitchdickson said:
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
ArminasAnarion said:
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
Click to expand...
Click to collapse
What's wrong with it? You're telling him to call Google and say that for some reason, all the sudden his device won't boot.
This is why I don't fault Verizon for selling bootloader locked phones.
Sent from my taimen using XDA Labs
Hey guys, last week i wanna flash a custom rom on my SM-a520f/DS but my OEM unlock was missing,I thought i just had to wait for 7 days but it won't show even after 7 days
Now i flashed official stock rom and will try to wait again for 7 days, but if this doesn't work then imma bout to lose my mind.
What can i do if it doesnt oem unlock doesnt p
Appear even if you reflashed stock romm
MitchiePitchie said:
Hey guys, last week i wanna flash a custom rom on my SM-a520f/DS but my OEM unlock was missing,I thought i just had to wait for 7 days but it won't show even after 7 days
Now i flashed official stock rom and will try to wait again for 7 days, but if this doesn't work then imma bout to lose my mind.
What can i do if it doesnt oem unlock doesnt p
Appear even if you reflashed stock romm
Click to expand...
Click to collapse
Maybe a factory reset would help, I dunno...
TechGuyOnTechIT said:
Maybe a factory reset would help, I dunno...
Click to expand...
Click to collapse
Just reflashed stock rom and waiting 7 days. I'll update if it works:fingers-crossed:
MitchiePitchie said:
Just reflashed stock rom and waiting 7 days. I'll update if it works:fingers-crossed:
Click to expand...
Click to collapse
Well this SHOULD fix the issue. If not, then I suspect the phone's internal clock is messed and needs complicated repair, but this a very very very VERY rare occasion, and I doubt you don't have this issue.
My phone just flashed a ok TWRP, but after I accidentally restarted, the phone didn't put me in OEM jail. Talk about lucky!
Just wait 7 days, activate developer options, click unlock oem, flash twrp via odin and after that is done IMMEDIATELY hold power and plus so it doesn't get you back to oem jail. After you are in TWRP, try not to turn it off to keep the recovery, and either install a zip that removes the 7 day jail or a cudtom rom. If you don't have a microsd to transfer from your pc to your phone, just use adb sideload. If you have any questions, just reply!
TechGuyOnTechIT said:
Well this SHOULD fix the issue. If not, then I suspect the phone's internal clock is messed and needs complicated repair, but this a very very very VERY rare occasion, and I doubt you don't have this issue.
My phone just flashed a ok TWRP, but after I accidentally restarted, the phone didn't put me in OEM jail. Talk about lucky!
Just wait 7 days, activate developer options, click unlock oem, flash twrp via odin and after that is done IMMEDIATELY hold power and plus so it doesn't get you back to oem jail. After you are in TWRP, try not to turn it off to keep the recovery, and either install a zip that removes the 7 day jail or a cudtom rom. If you don't have a microsd to transfer from your pc to your phone, just use adb sideload. If you have any questions, just reply!
Click to expand...
Click to collapse
WAIT, so you need to wait 7 days before activating developer's option? Does that put you in prenormal rmm state? Because i already activated my developer's option, If thats the case then i already messed up
MitchiePitchie said:
WAIT, so you need to wait 7 days before activating developer's option? Does that put you in prenormal rmm state? Because i already activated my developer's option, If thats the case then i already messed up
Click to expand...
Click to collapse
No, you haven't messed up! The 7 day jail doens't block you access to developer options, but doesn't let you enable OEM unlock. I was suggesting you should do this just to make sure you are not in the 7 day jail. Again, if you can check that option, then there is not a problem. Just try to have your jail patcher zip handy so you won't have to deal with this problem. Again, if you have any questions, just reply!
TechGuyOnTechIT said:
No, you haven't messed up! The 7 day jail doens't block you access to developer options, but doesn't let you enable OEM unlock. I was suggesting you should do this just to make sure you are not in the 7 day jail. Again, if you can check that option, then there is not a problem. Just try to have your jail patcher zip handy so you won't have to deal with this problem. Again, if you have any questions, just reply!
Click to expand...
Click to collapse
Okay, the OEM unlock didn't showed up and my rmm state is still prenormal after 7 days even in flashing stock. I might retry this again in another rom carrier. I'm really at the end of my rope here
MitchiePitchie said:
Okay, the OEM unlock didn't showed up and my rmm state is still prenormal after 7 days even in flashing stock. I might retry this again in another rom carrier. I'm really at the end of my rope here
Click to expand...
Click to collapse
Don't give up! Try to go to download mode, flash a complete Samsung rom (with bootloader, modem, recovery and rom). I guess you can find a stock samsung rom on google or via smart switch. Download mode only blocks installing THIRD PARTY ROMS, not the stock ones. Try that and give a reply.
TechGuyOnTechIT said:
Don't give up! Try to go to download mode, flash a complete Samsung rom (with bootloader, modem, recovery and rom). I guess you can find a stock samsung rom on google or via smart switch. Download mode only blocks installing THIRD PARTY ROMS, not the stock ones. Try that and give a reply.
Click to expand...
Click to collapse
I'll try to flash the rom again and wait 7 days, I'll boot ip without sim and sd card first
TechGuyOnTechIT said:
Don't give up! Try to go to download mode, flash a complete Samsung rom (with bootloader, modem, recovery and rom). I guess you can find a stock samsung rom on google or via smart switch. Download mode only blocks installing THIRD PARTY ROMS, not the stock ones. Try that and give a reply.
Click to expand...
Click to collapse
Man I already flashed stock rom and waited 7 days, I ain't doing that stuff again I'll just sell this phone if I don't find any other way.
MitchiePitchie said:
Man I already flashed stock rom and waited 7 days, I ain't doing that stuff again I'll just sell this phone if I don't find any other way.
Click to expand...
Click to collapse
Seriously? Are you SURE you don't see OEM unlock in developer options, because any Samsung device SHOULD have the 7 day lift period. If you confirm that you don't see it, the only thing left to do is to contact a samsung expert. Don't feel embarrassed that you ask samsung for a third party thing, they must help you even though that may result in voiding your warranty.
Honestly, this is a pretty uncommon issue :/
TechGuyOnTechIT said:
Seriously? Are you SURE you don't see OEM unlock in developer options, because any Samsung device SHOULD have the 7 day lift period. If you confirm that you don't see it, the only thing left to do is to contact a samsung expert. Don't feel embarrassed that you ask samsung for a third party thing, they must help you even though that may result in voiding your warranty.
Honestly, this is a pretty uncommon issue :/
Click to expand...
Click to collapse
I'll try reflashing a carrier rom (Globe) not a XTC (openline) rom and if this doesn't work then i dont know what will:fingers-crossed:
MitchiePitchie said:
I'll try reflashing a carrier rom (Globe) not a XTC (openline) rom and if this doesn't work then i dont know what will:fingers-crossed:
Click to expand...
Click to collapse
Samsung support centre could also help.
TechGuyOnTechIT said:
Seriously? Are you SURE you don't see OEM unlock in developer options...Honestly, this is a pretty uncommon issue :/
Click to expand...
Click to collapse
I have the same issue. Started with Android 7, rooted phone, flashed Hades ROM v6 ( Android 8) which is fine, but I no longer see OEM Unlock in Developer options (presumably I did before installing Hades). Have tried the date fudge:
https://forum.xda-developers.com/samsung-a-series-2017/help/guide-oem-unlock-oreo-t3791774
more than once. No joy. Hades is fine, but I'd like to try the OneUI Android 9 ROM...
Corbynista said:
I have the same issue. Started with Android 7, rooted phone, flashed Hades ROM v6 ( Android 8) which is fine, but I no longer see OEM Unlock in Developer options (presumably I did before installing Hades). Have tried the date fudge:
https://forum.xda-developers.com/samsung-a-series-2017/help/guide-oem-unlock-oreo-t3791774
more than once. No joy. Hades is fine, but I'd like to try the OneUI Android 9 ROM...
Click to expand...
Click to collapse
If you are still on hades, the dev removed the OEM unlock toggle to prevent noobs from disabling it which would bootloop your phone and twrp would also not boot. Most if not all custom roms remove it. So you can flash Oneui
Corbynista said:
I have the same issue. Started with Android 7, rooted phone, flashed Hades ROM v6 ( Android 8) which is fine, but I no longer see OEM Unlock in Developer options (presumably I did before installing Hades). Have tried the date fudge:
https://forum.xda-developers.com/samsung-a-series-2017/help/guide-oem-unlock-oreo-t3791774
more than once. No joy. Hades is fine, but I'd like to try the OneUI Android 9 ROM...
Click to expand...
Click to collapse
When you are on cfw, as the guy said, there is no need. The rom is third party, meaning it's not official, thus it remains unlocked. But if you are on stock rom, then the oem unlock will be shown.
iloveoreos said:
If you are still on hades, the dev removed the OEM unlock toggle to prevent noobs from disabling it which would bootloop your phone and twrp would also not boot. Most if not all custom roms remove it. So you can flash Oneui
Click to expand...
Click to collapse
TechGuyOnTechIT said:
When you are on cfw, as the guy said, there is no need. The rom is third party, meaning it's not official, thus it remains unlocked. But if you are on stock rom, then the oem unlock will be shown.
Click to expand...
Click to collapse
I wondered if this was the case. Thanks to you both.
TechGuyOnTechIT said:
Samsung support centre could also help.
Click to expand...
Click to collapse
that ain't an option for me since they dont really respond. You know any other option if it doesn't even show this week too?
i reflashed stock rom like 5 times now
MitchiePitchie said:
that ain't an option for me since they dont really respond. You know any other option if it doesn't even show this week too?
i reflashed stock rom like 5 times now
Click to expand...
Click to collapse
Punch your phone, return it, and get another one.
SnowFuhrer said:
Punch your phone, return it, and get another one.
Click to expand...
Click to collapse
Nooooo! Don't do that! That would be a waste! Maybe its a bug. Try to flash twrp even though it doesn't show you kem unlock, and if that still doesn't work, give up trying systemless rooting and go full supersu by doing a one-click root (kingroot, etc). Maybe that helps. If it still not working, then I will finally recommend bailing and just getting another one . Sorry...
Weird screen behavior, it seem to me that it isn't a hardware fault, cause when plugging in a charger the phone is able to show the MI logo, but not the charging icon
The phone is able to boot and i can hear the phone locking and unlocking, can see that the screen is on because of the backlight, but there is no image, SO FRUSTRATING!!
If you have any idea of what's going on and can give me a tip, i would thank you so much, the phone has been on this state for a long time
Don't know how to upload videos, if you think that can help diagnose it i can upload it and share a link or something
Hugask said:
Weird screen behavior, it seem to me that it isn't a hardware fault, cause when plugging in a charger the phone is able to show the MI logo, but not the charging icon
The phone is able to boot and i can hear the phone locking and unlocking, can see that the screen is on because of the backlight, but there is no image, SO FRUSTRATING!!
If you have any idea of what's going on and can give me a tip, i would thank you so much, the phone has been on this state for a long time
Don't know how to upload videos, if you think that can help diagnose it i can upload it and share a link or something
Click to expand...
Click to collapse
What did you do before?
Did you flash something?
Is it device unlocked?
This happen also in fastboot/recovery mode?
SubwayChamp said:
What did you do before?
Did you flash something?
Is it device unlocked?
This happen also in fastboot/recovery mode?
Click to expand...
Click to collapse
I hadnt updated my Rom, Pixel experience, in a while, so i took the opportunity and flashed an (at the time) beta Pixel Experience Android 10, i reverted and everything was fine for about one day i think, then some artifacting wich would come and go until the display gived up completly (about an hour between the two)
Yes, it is unlocked, and when in fastboot/recovery the screen is lighted up but not showing anything
My guess is that i have a low level firmware issue, as i had problem with those before (was running a custom ROM from day 1, so i had to manually update firware to use newer versions of PE (still pie version) and almost bricked my device
Hugask said:
I hadnt updated my Rom, Pixel experience, in a while, so i took the opportunity and flashed an (at the time) beta Pixel Experience Android 10, i reverted and everything was fine for about one day i think, then some artifacting wich would come and go until the display gived up completly (about an hour between the two)
Yes, it is unlocked, and when in fastboot/recovery the screen is lighted up but not showing anything
My guess is that i have a low level firmware issue, as i had problem with those before (was running a custom ROM from day 1, so i had to manually update firware to use newer versions of PE (still pie version) and almost bricked my device
Click to expand...
Click to collapse
Then try the next:
- Flash a different vendor.
- Flash a different kernel.
- Revert to stock ROM, no need to lock or nothing, just flash first the recovery ROM but if it doesn't result then flash the fastboot ROM through EDL, so that you know you can boot to EDL mode without need to open the back cover, this will restore all the original images.
SubwayChamp said:
Then try the next:
- Flash a different vendor.
- Flash a different kernel.
- Revert to stock ROM, no need to lock or nothing, just flash first the recovery ROM but if it doesn't result then flash the fastboot ROM through EDL, so that you know you can boot to EDL mode without need to open the back cover, this will restore all the original images.
Click to expand...
Click to collapse
Ok, so... i think i have all the files, but i'm really lost, how am i supposed to flash the vendor, firmware and stock ROM via fastboot?
Also, i put the device in fastboot, so... thats a win i guess (screen working surprisingtly)
I'm just not finding how to do this, it's been a while that i havent messed with this side of android, if you could help me it would mean the world for me
Hugask said:
Ok, so... i think i have all the files, but i'm really lost, how am i supposed to flash the vendor, firmware and stock ROM via fastboot?
Also, i put the device in fastboot, so... thats a win i guess (screen working surprisingtly)
I'm just not finding how to do this, it's been a while that i havent messed with this side of android, if you could help me it would mean the world for me
Click to expand...
Click to collapse
You can flash some images invoking the right partition, I mean, you can flash vendor image onto the vendor partition using
Code:
fastboot flash vendor vendor.img
, and in case you need to flash all the ROM you should use MiFlash tool
SubwayChamp said:
You can flash some images invoking the right partition, I mean, you can flash vendor image onto the vendor partition using
Code:
fastboot flash vendor vendor.img
, and in case you need to flash all the ROM you should use MiFlash tool
Click to expand...
Click to collapse
Ok, so... i am NOT keeping up with what i need to do, i found a vendor update in a site but it is not an image, i am so confused, i don't how was i able to mess around with this i am basically a noob, i feel so dumb, this should have been so easy and here i am having trouble
If you could make a step by step instruction or send a link where i can get a vendor .img it would be perfect thanks in advance
Hugask said:
Ok, so... i am NOT keeping up with what i need to do, i found a vendor update in a site but it is not an image, i am so confused, i don't how was i able to mess around with this i am basically a noob, i feel so dumb, this should have been so easy and here i am having trouble
If you could make a step by step instruction or send a link where i can get a vendor .img it would be perfect thanks in advance
Click to expand...
Click to collapse
Ok, update what is the current status of your device, you said screen now displaying, Did you refer only to fastboot mode? Could you see the bunny in fastboot? But booted up on system screen is displaying nothing?
SubwayChamp said:
Ok, update what is the current status of your device, you said screen now displaying, Did you refer only to fastboot mode? Could you see the bunny in fastboot? But booted up on system screen is displaying nothing?
Click to expand...
Click to collapse
Yes, that is correct, i can see the fastboot screen 100%, no artifacts, just plain working, still no recovery (if i remember right i have orange fox) or ROM screen
Hugask said:
Yes, that is correct, i can see the fastboot screen 100%, no artifacts, just plain working, still no recovery (if i remember right i have orange fox) or ROM screen
Click to expand...
Click to collapse
And what do you want to do now? Did you unlock bootloader?
SubwayChamp said:
And what do you want to do now? Did you unlock bootloader?
Click to expand...
Click to collapse
I actually want to check that, i took the phone to a tecnitician and he may have locked the bootloader
I think the next step would be flashing the vendor, firmwares and stock rom again, right?
Hugask said:
I actually want to check that, i took the phone to a tecnitician and he may have locked the bootloader
I think the next step would be flashing the vendor, firmwares and stock rom again, right?
Click to expand...
Click to collapse
if your bootloader is locked, you can't flash through fastboot mode either vendor or stock ROM, you should need to use EDL method or you can re-unlock bootloader and this way will work. Anyway i don't understand what actually your issue is.
SubwayChamp said:
if your bootloader is locked, you can't flash through fastboot mode either vendor or stock ROM, you should need to use EDL method or you can re-unlock bootloader and this way will work. Anyway i don't understand what actually your issue is.
Click to expand...
Click to collapse
The issue is the display not working, and it's gotta be a firmware issue as it's on my desk right now showing a bunny, also i am not used to fastboot flash anything, i just was used to recoveries and what not
Just runned some code and it's locked, this is getting better and better oh boy
How am i gonna unlock this if i can't even unlock the phone? last time with screen working it was already a nightmare, having to wait for miui account, do i have any method of doing this without using EDL?
Hugask said:
The issue is the display not working, and it's gotta be a firmware issue as it's on my desk right now showing a bunny, also i am not used to fastboot flash anything, i just was used to recoveries and what not
Just runned some code and it's locked, this is getting better and better oh boy
How am i gonna unlock this if i can't even unlock the phone? last time with screen working it was already a nightmare, having to wait for miui account, do i have any method of doing this without using EDL?
Click to expand...
Click to collapse
Well, this make sense although it's not clear if you did unlock it previously and after that at some time you did lock it again.
If you didn't unlock it previously you would need to bind your Mi account to the device and enable USB debugging and OEM unlock options but if you didn't before without a screen working you have a more difficult way, confirm me if that is the case.
Anyway I got happily surprised when I bought this device some months ago at the first attempt I could unlock it without have to wait time, try it and see what happen.
SubwayChamp said:
Well, this make sense although it's not clear if you did unlock it previously and after that at some time you did lock it again.
If you didn't unlock it previously you would need to bind your Mi account to the device and enable USB debugging and OEM unlock options but if you didn't before without a screen working you have a more difficult way, confirm me if that is the case.
Anyway I got happily surprised when I bought this device some months ago at the first attempt I could unlock it without have to wait time, try it and see what happen.
Click to expand...
Click to collapse
It was unloked and i locked again, don't know if this helps my case or if i am royally screwed up
And yeah, Xioami does make difficult to do the process of unlocking but only to recently released devices, aparently to stop re-sellers to buy the cheaper chinese rom and put the global version on them, i think that when a device doenst get made anymore makes sense that they would make it more easy (i bought the device 2 weeks after launch)
Hugask said:
It was unloked and i locked again, don't know if this helps my case or if i am royally screwed up
And yeah, Xioami does make difficult to do the process of unlocking but only to recently released devices, aparently to stop re-sellers to buy the cheaper chinese rom and put the global version on them, i think that when a device doenst get made anymore makes sense that they would make it more easy (i bought the device 2 weeks after launch)
Click to expand...
Click to collapse
Ok, of course this makes a huge difference, if you did unlock it previously then you couldn't receive any wait time, I wonder why you didn't try it if you didn 't. Check if MiUnlock tool unlock your device instantly.
SubwayChamp said:
Ok, of course this makes a huge difference, if you did unlock it previously then you couldn't receive any wait time, I wonder why you didn't try it if you didn 't. Check if MiUnlock tool unlock your device instantly.
Click to expand...
Click to collapse
OMG THIS WORKED
It's been sucessfully unlocked
Hugask said:
OMG THIS WORKED
It's been sucessfully unlocked
Click to expand...
Click to collapse
Hmm, OK, now you have your way sorted out, you can try with a custom ROM (all of them contain a vendor) or in case a custom ROM doesn't solve it you have to try a stock ROM through Mi Flash tool.
SubwayChamp said:
Hmm, OK, now you have your way sorted out, you can try with a custom ROM (all of them contain a vendor) or in case a custom ROM doesn't solve it you have to try a stock ROM through Mi Flash tool.
Click to expand...
Click to collapse
Ok, but how am i gonna flash a rom with fastboot? Is that a thing?
Also, i don't think the vendor is gonna be my only problem, but also the firmware, is there a way to flash firmware without the recovery and trough fastboot?
Hugask said:
Ok, but how am i gonna flash a rom with fastboot? Is that a thing?
Also, i don't think the vendor is gonna be my only problem, but also the firmware, is there a way to flash firmware without the recovery and trough fastboot?
Click to expand...
Click to collapse
You can't be sure of that, sometimes the vendor correct the issue, sometimes the firmware.
Firmware it is in the stock ROM that can be flashed either through fastboot or EDL mode (be careful to not relock bootloader or you couldn't enable this time OEM unlock option). Now that you have the way more clear just do a search "how to flash stock ROM on Xiaomi devices either through fastboot or EDL mode", just keep in mind that you don't need to open the back cover of the device, usually from a device off (only on unlocked ones) you could send it to EDL by pressing both volume buttons at same time that it is connected to PC, I gave you the main tips, for the rest you will find a lot of tutorials.
If your bootloader is locked, one of the dumbest things you can do is try to install potentially unstable firmware. If something goes wrong, you won't be able to recover your device.
If you did anyway, the only way you should try to return to stock is with the Android Flash Tool, which should work as long as OEM Unlocking is enabled.
If you're on a device that cannot be unlocked, you should wait the Android 13 official release.
V0latyle said:
If your bootloader is locked, one of the dumbest things you can do is try to install potentially unstable firmware. If something goes wrong, you won't be able to recover your device.
If you did anyway, the only way you should try to return to stock is with the Android Flash Tool, which should work as long as OEM Unlocking is enabled.
If you're on a device that cannot be unlocked, you should wait the Android 13 official release.
Click to expand...
Click to collapse
I got my device from T-Mobile and yes the bootloader is locked. I was on the A13 beta and opted out. I am now back on A12. Yes it took some extra steps to get back to A12 but you can do it with a locked bootloader.
truckerdewd said:
I got my device from T-Mobile and yes the bootloader is locked. I was on the A13 beta and opted out. I am now back on A12. Yes it took some extra steps to get back to A12 but you can do it with a locked bootloader.
Click to expand...
Click to collapse
Not everyone has been so lucky. Glad it worked for you, though.
roirraW edor ehT said:
Not everyone has been so lucky. Glad it worked for you, though.
Click to expand...
Click to collapse
True. I posted the steps I followed in this thread.
Android Beta to Factory Reset mucked up, plus a bunch of troubleshooting I've already tried
Okay. The android beta program was messing with an app I use regularly so I backed up my phone on google 1 and all that fun stuff then did the opt out and just ran stuff like it was supposed to. Then, it got stuck in fastboot mode and said that...
forum.xda-developers.com
I'm a firm believer that unless you are using some apps (mostly banking apps) that will absolutely not work with these enabled, that before doing anything you should toggle on "OEM unlocking" and "USB debugging", regardless if you're using Stable or Beta or whatever you're doing. It will open up a bunch of possibilities to recover your phone if you hit a glitch in the matrix.
For me it's the very 1st thing I do when getting a new phone.
Lughnasadh said:
I'm a firm believer that unless you are using some apps (mostly banking apps) that will absolutely not work with these enabled, that before doing anything you should toggle on "OEM unlocking" and "USB debugging", regardless if you're using Stable or Beta or whatever you're doing. It will open up a bunch of possibilities to recover your phone if you hit a glitch in the matrix.
For me it's the very 1st thing I do when getting a new phone.
Click to expand...
Click to collapse
I'm not sure toggling these would trip device security. As long as the bootloader remains locked the device should meet HARDWARE_BACKED integrity (key attestation), and if the firmware is factory the device should meet BASIC integrity as well.
Sorry, but if you just enable the OEM unlock? Then, just in case things go bad, you can unlock bootloader...
V0latyle said:
I'm not sure toggling these would trip device security. As long as the bootloader remains locked the device should meet HARDWARE_BACKED integrity (key attestation), and if the firmware is factory the device should meet BASIC integrity as well.
Click to expand...
Click to collapse
We are not actually talking about tripping device security or being able to pass Play Integrity API, etc.. Even with the bootloader locked, apps can still check to see whether OEM Unlocking and USB Debugging are enabled, and if so, make it so the app fails to work properly, if at all. Apps can even check to see if you have Developer Options enabled.
USB debugging definitely does interfere with some apps being able to work. I have to disable it to use one of my apps and many others have reported the same for a variety of apps. I have also seen having OEM Unlocking enabled interfere with some apps as well, as reported by others.
In my case I just disable USB Debugging, use the app, then re-enable when done using the app.
gpvecchi said:
Sorry, but if you just enable the OEM unlock? Then, just in case things go bad, you can unlock bootloader...
Click to expand...
Click to collapse
Basically yes, as long as you have an unlockable bootloader, can get into fastboot, etc..
For example, if things go haywire for you and you have OEM unlocking enabled, you can use Android Flash Tool to help recover your device. Or you can use fastboot to manually unlock the bootloader and flash whatever.
Lughnasadh said:
We are not actually talking about tripping device security or being able to pass Play Integrity API, etc.. Even with the bootloader locked, apps can still check to see whether OEM Unlocking and USB Debugging are enabled, and if so, make it so the app fails to work properly, if at all. Apps can even check to see if you have Developer Options enabled.
USB debugging definitely does interfere with some apps being able to work. I have to disable it to use one of my apps and many others have reported the same for a variety of apps. I have also seen having OEM Unlocking enabled interfere with some apps as well, as reported by others.
In my case I just disable USB Debugging, use the app, then re-enable when done using the app.
Click to expand...
Click to collapse
Yeah I think my brain was somewhere else. Interesting though.
@Lughnasadh Just curious which apps? I've not come across any.
bobby janow said:
@Lughnasadh Just curious which apps? I've not come across any.
Click to expand...
Click to collapse
Of the ones I use, Spectrum TV requires USB Debugging to be disabled.
Lughnasadh said:
Of the ones I use, Spectrum TV requires USB Debugging to be disabled.
Click to expand...
Click to collapse
I obviously do not use Spectrum TV. I almost always have debugging on and have never come across a need to turn it off, I actually didn't even know it was a thing. But it makes sense since it is an opening into the device. One thing I have noticed when I flip the OEM switch though. I only keep it active when I'm either sideloading or, heaven forbid, install a beta or custom rom. After it's done and booted I flip the switch back off and it has me reboot for added security that is not available when the switch is active. What's that all about?
bobby janow said:
I obviously do not use Spectrum TV. I almost always have debugging on and have never come across a need to turn it off, I actually didn't even know it was a thing. But it makes sense since it is an opening into the device. One thing I have noticed when I flip the OEM switch though. I only keep it active when I'm either sideloading or, heaven forbid, install a beta or custom rom. After it's done and booted I flip the switch back off and it has me reboot for added security that is not available when the switch is active. What's that all about?
Click to expand...
Click to collapse
Yeah, if you go through the Magisk, SafetyNet and similar threads you'll see people who have come across apps that won't work when USB Debugging is enabled. It's really up to the app developer as to whether it checks for it or not.
I'm not entirely sure why after you switch OEM Unlocking off that it has you reboot as I've never switched it off once switched on. My guess would be that a reboot is needed to set ro.oem_unlock_supported to 0. But that's just a guess.
V0latyle said:
If your bootloader is locked, one of the dumbest things you can do is try to install potentially unstable firmware. If something goes wrong, you won't be able to recover your device.
If you did anyway, the only way you should try to return to stock is with the Android Flash Tool, which should work as long as OEM Unlocking is enabled.
If you're on a device that cannot be unlocked, you should wait the Android 13 official release.
Click to expand...
Click to collapse
The way Google implements there otas and installs now is a fail safe, the devices will not be bricked what so ever, if on stock that is