I just installed TWRP onto my Samsung Galaxy S8. It was installed successfully, but when I try getting into the TWRP mode by pressing power+bixby+vol-up, the phone vibrates and displays a pink light at the top left before returning to a normal boot-up screen and my phone unlocks normally. When my phone is done booting up, I get a grey box saying:
"
[PDP]
back-up : fail
setup-wizard [FINISH]
"
I suspect this has something to do with the fact that I've gonked up the phone a couple of years ago. I had to send the phone to Samsung to get it fixed, I stayed away from rooting until now when I've gotten a new phone. What I'm asking here is, is this the cause? And how do I fix it so I can get into TWRP mode so I can complete my root?
MariusNullTre said:
I just installed TWRP onto my Samsung Galaxy S8. It was installed successfully, but when I try getting into the TWRP mode by pressing power+bixby+vol-up, the phone vibrates and displays a pink light at the top left before returning to a normal boot-up screen and my phone unlocks normally. When my phone is done booting up, I get a grey box saying:
"
[PDP]
back-up : fail
setup-wizard [FINISH]
"
I suspect this has something to do with the fact that I've gonked up the phone a couple of years ago. I had to send the phone to Samsung to get it fixed, I stayed away from rooting until now when I've gotten a new phone. What I'm asking here is, is this the cause? And how do I fix it so I can get into TWRP mode so I can complete my root?
Click to expand...
Click to collapse
Are you sure your bootloader was unlocked before you flashed TWRP?
Droidriven said:
Are you sure your bootloader was unlocked before you flashed TWRP?
Click to expand...
Click to collapse
How do I unlock my bootloader? Does it imply, having gone into the bootloader mode before flashing TWRP? If that is the case, no, I hadn't gone into the original recovery mode before flashing twrp, if not, what does it imply? Also, how do I fix?
MariusNullTre said:
How do I unlock my bootloader? Does it imply, having gone into the bootloader mode before flashing TWRP? If that is the case, no, I hadn't gone into the original recovery mode before flashing twrp, if not, what does it imply? Also, how do I fix?
Click to expand...
Click to collapse
You mean to tell me that in the process of finding and flashing TWRP for your device, you did not see anything telling you that you had to make sure the bootloader was unlocked before flashing it? If you didn't then you did a poor job of researching the process of flashing TWRP and rooting your device because it is usually mentioned in all guides for flashing TWRP.
No, I meant, did you check to make certain that your bootloader is unlocked before you flashed TWRP? I asked about bootloader because you can't flash anything custom if the bootloader is locked.
I don't know if your bootloader is locked or not. Just because I'm asking, does not mean that was locked.
If it is locked, you have to unlock it and then flash TWRP, if it is already unlocked, you do not have to unlock it.
Unlocking bootloader on Samsung usually involves enabling the OEM unlock setting in the device's settings. Enabling this setting does not necessarily mean that your bootloader is unlocked, you also need to boot into download mode and check the RMM or KG status to see if it says "prenormal", "checking" or "unlock". If it says "prenormal" it is locked and you can't flash TWRP.
Droidriven said:
You mean to tell me that in the process of finding and flashing TWRP for your device, you did not see anything telling you that you had to make sure the bootloader was unlocked before flashing it? If you didn't then you did a poor job of researching the process of flashing TWRP and rooting your device because it is usually mentioned in all guides for flashing TWRP.
No, I meant, did you check to make certain that your bootloader is unlocked before you flashed TWRP? I asked about bootloader because you can't flash anything custom if the bootloader is locked.
I don't know if your bootloader is locked or not. Just because I'm asking, does not mean that was locked.
If it is locked, you have to unlock it and then flash TWRP, if it is already unlocked, you do not have to unlock it.
Unlocking bootloader on Samsung usually involves enabling the OEM unlock setting in the device's settings. Enabling this setting does not necessarily mean that your bootloader is unlocked, you also need to boot into download mode and check the RMM or KG status to see if it says "prenormal", "checking" or "unlock". If it says "prenormal" it is locked and you can't flash TWRP.
Click to expand...
Click to collapse
I did turn on the OEM unlock before flashing. Did not see the RMM or KG status though. The flash was successful though. It just doesn't want to open TWRP as it cancels and shows me a pink light right as it's about to open TWRP.
Droidriven said:
You mean to tell me that in the process of finding and flashing TWRP for your device, you did not see anything telling you that you had to make sure the bootloader was unlocked before flashing it? If you didn't then you did a poor job of researching the process of flashing TWRP and rooting your device because it is usually mentioned in all guides for flashing TWRP.
No, I meant, did you check to make certain that your bootloader is unlocked before you flashed TWRP? I asked about bootloader because you can't flash anything custom if the bootloader is locked.
I don't know if your bootloader is locked or not. Just because I'm asking, does not mean that was locked.
If it is locked, you have to unlock it and then flash TWRP, if it is already unlocked, you do not have to unlock it.
Click to expand...
Click to collapse
The information on the S8 are really poor. I used to root a lot of phones until a few years ago. Finding a manual for the S8 (Rom install, first TWRP,...) Seems to be impossible. I just find many contradicting information.
One manual sais there is nothing to unlock. I shall just use Odin to falsch the rom. Done. Other manuals go by TWRP as I know it. And so on.
Related
So I upgraded to Nougat on my P9 Lite, unlocked boot loader, used twrp, flashed roms and everything went smooth. Saw a more up-to-date version with no bugs, so I had to downgrade to MM first.
I followed a guide, but I messed up somewhere and ended up having my bootloader locked, and I can't access the OS to enable developer options and oem unlock from settings. The reason why I can't access the OS is that I am stuck in the setup. I am stuck at the part where I have to sign in to my google account. It doesn't show a keyboard, only a microphone, and I can't use that for my password (it won't let me).
Any ideas?
TL;DR messed up during downgrading from Nougat to MM, now TWLR is gone, bootloader is locked and my main issue is that when I get to the google account sign in part during OS setup, there is no keyboard (I can only use dictation) so I can't sign in... So I'm stuck
Also, can I unlock bootloader without access to OS, without being able to navigate to settings, enable developer options and then oem unlock?
1. Stuck in OS setup? Signing in to Google? Hey, it's not obligatory, can't you just skip it?
2. Flashing ROMS locked your bootloader, it's normal, but I'm sure it didn't change the "oem unlock" setting you had surely enabled before. Go to fastboot mode and check Bootloader and FRP status on the bottom of the screen. If FRP is unlocked, you will be able to unlock bootloader again.
3. If you have your TWRP gone (flashed by stock ROM), flash the recovery partition manually - fastboot flash recovery TWRP.img (download from Meticulus Project site).
Jagiel88 said:
1. Stuck in OS setup? Signing in to Google? Hey, it's not obligatory, can't you just skip it?
2. Flashing ROMS locked your bootloader, it's normal, but I'm sure it didn't change the "oem unlock" setting you had surely enabled before. Go to fastboot mode and check Bootloader and FRP status on the bottom of the screen. If FRP is unlocked, you will be able to unlock bootloader again.
3. If you have your TWRP gone (flashed by stock ROM), flash the recovery partition manually - fastboot flash recovery TWRP.img (download from Meticulus Project site).
Click to expand...
Click to collapse
It is obligatory, I couldn't skip it. I tried to use other methods of signing in, but then it asked me to reset password at the end.
Both Phone and FRP are locked
I think I have missed this, but I can't do it via fastboot because I keep getting "Command not allowed" whenever I try to unlock bootloader or do anything via fast boot.
Also, thank you so much for your time and input. It is much appreciated.
That's weird, I flashed my phone several times with different ROMS (not Nougat) and this setting (oem unlock / FRP unlocked) stayed enabled. Don't know where it sits then and how to change it without getting inside OS. But - what about TWRP? Oh right, you won't be able to flash it without unlocked bootloader... Oh, crap. I would try SRK Tool for Huawei to play with bootloader, it uses fastboot so shouldn't help, but maybe, just maybe? Maybe try flashing whole ROMs through dload folder on SD? Stock 120, 161, Nougat, I would try these. I hope there is some way to unlock FRP, probably it's possible in DC-unlocker (it's a paid software).
Jagiel88 said:
That's weird, I flashed my phone several times with different ROMS (not Nougat) and this setting (oem unlock / FRP unlocked) stayed enabled. Don't know where it sits then and how to change it without getting inside OS. But - what about TWRP? Oh right, you won't be able to flash it without unlocked bootloader... Oh, crap. I would try SRK Tool for Huawei to play with bootloader, it uses fastboot so shouldn't help, but maybe, just maybe? Maybe try flashing whole ROMs through dload folder on SD? Stock 120, 161, Nougat, I would try these. I hope there is some way to unlock FRP, probably it's possible in DC-unlocker (it's a paid software).
Click to expand...
Click to collapse
Yes, it's very weird. I haven't done the process a lot. But I've flashed a couple of phones I had before, went smooth. Nothing major like this happened before.
I will consider the SRK Tool and I did not know about the DC-Unlocker tool, thank you for telling me about it.
Flashing whole roms through dload folder only works with Nougat for some reason, and I keep getting stuck in the signing in problem because of no keyboard, someone told me that's incomplete software, I'm hoping that's the case, any ideas where can I get it from?
Again thank you Jagiel88 for your time and advice xD
No problem, unfortunately I haven't tried Nougat yet, so search for help on down/upgrade Nougat beta <-> Marshmallow threads .
youssefSamir said:
Yes, it's very weird. I haven't done the process a lot. But I've flashed a couple of phones I had before, went smooth. Nothing major like this happened before.
I will consider the SRK Tool and I did not know about the DC-Unlocker tool, thank you for telling me about it.
Flashing whole roms through dload folder only works with Nougat for some reason, and I keep getting stuck in the signing in problem because of no keyboard, someone told me that's incomplete software, I'm hoping that's the case, any ideas where can I get it from?
Again thank you Jagiel88 for your time and advice xD
Click to expand...
Click to collapse
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
islandman75 said:
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
Click to expand...
Click to collapse
There is 1 thing to unlock in settings . U have OEM lock
youssefSamir said:
Yes, it's very weird. I haven't done the process a lot. But I've flashed a couple of phones I had before, went smooth. Nothing major like this happened before.
I will consider the SRK Tool and I did not know about the DC-Unlocker tool, thank you for telling me about it.
Flashing whole roms through dload folder only works with Nougat for some reason, and I keep getting stuck in the signing in problem because of no keyboard, someone told me that's incomplete software, I'm hoping that's the case, any ideas where can I get it from?
Again thank you Jagiel88 for your time and advice xD
Click to expand...
Click to collapse
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
ScaleneVirus288 said:
There is 1 thing to unlock in settings . U have OEM lock
Click to expand...
Click to collapse
Can't access to any OS. I definetly know i had OEM unlocked, then after unlocking via fastboot, I wasn't able anymore to access the system.
islandman75 said:
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
Can't access to any OS. I definetly know i had OEM unlocked, then after unlocking via fastboot, I wasn't able anymore to access the system.
Click to expand...
Click to collapse
Unlock bootloader, after that you able to flash rom.
You use this command?
fastboot oem unlock YOUR_OEM_CODE
If you tip:
fastboot devices
What's you see?
I think i made i grave mistake. I want to upgrade my p9 lite to nougat so I decided to unroot my phone. The unrooting is successful with the device still booting. So next thing i want is to flash back my stock recovery so I can update my phone through OTA (this is where I made a mistake.) I tried doing it by flashing a full MM Rom that i got directly from huawei through dload method. The flashing went smoothly or so I thought. My phone got stuck in a boot loop and I cant seem to access recovery. eRecovery is also inaccessible so I tried reflashing the full MM Rom through dload method but I can't get it to work anymore. I tried it several times with no luck. I also tried reflashing meticulus' twrp through fastboot method but I always get an error saying "remote command not allowed". The bootloader is still unlock btw.
Someone help me. I don't know what to do anymore... :crying:
NikkoVicedo said:
I think i made i grave mistake. I want to upgrade my p9 lite to nougat so I decided to unroot my phone. The unrooting is successful with the device still booting. So next thing i want is to flash back my stock recovery so I can update my phone through OTA (this is where I made a mistake.) I tried doing it by flashing a full MM Rom that i got directly from huawei through dload method. The flashing went smoothly or so I thought. My phone got stuck in a boot loop and I cant seem to access recovery. eRecovery is also inaccessible so I tried reflashing the full MM Rom through dload method but I can't get it to work anymore. I tried it several times with no luck. I also tried reflashing meticulus' twrp through fastboot method but I always get an error saying "remote command not allowed". The bootloader is still unlock btw.
Someone help me. I don't know what to do anymore... :crying:
Click to expand...
Click to collapse
The bootloader appears unlocked, and says so, but it's not...I encountered the same situation with my colleagues device, you need to unlock it either way(careful this will wipe all your data if on nougat, but if on MM after unlocking keep phone connected to PC as it reboots and quickly press vol down+ power to get back to bootloader In order to flash TWRP, this will preserve your data partition and system), and try again, you need format that data partition by using changing format to f2fs then ext4...after this reboot, if it can't, reinstall the file In dload folder and go to stock recovery(disconnect phone from PC to do this if it fails) and do a factory reset.
.... if this fails, debrand And install MM or NOUGAT for your newly debranded system.
If this fails, which is highly unlikely,PM for un orthodox methods.
_New World Order (NWO)_
daner[email protected] said:
The bootloader appears unlocked, and says so, but it's not...I encountered the same situation with my colleagues device, you need to unlock it either way(careful this will wipe all your data if on nougat, but if on MM after unlocking keep phone connected to PC as it reboots and quickly press vol down+ power to get back to bootloader In order to flash TWRP, this will preserve your data partition and system), and try again, you need format that data partition by using changing format to f2fs then ext4...after this reboot, if it can't, reinstall the file In dload folder and go to stock recovery(disconnect phone from PC to do this if it fails) and do a factory reset.
.... if this fails, debrand And install MM or NOUGAT for your newly debranded system.
If this fails, which is highly unlikely,PM for un orthodox methods.
_New World Order (NWO)_
Click to expand...
Click to collapse
The problem is I cannot access recovery anymore. After trying to flash back full rom from huawei, i cannot access recovery anymore no matter how hard i try. eRecovery is also not accessible so i cannot turn off my phone. I tried flashing twrp trough fastboot i keep getting an error saying "remote command not allowed". Dload method is not working anymore. If only I can find a way to flash twrp, then I can restore the dump i made using meticulus' twrp.
NikkoVicedo said:
The problem is I cannot access recovery anymore. After trying to flash back full rom from huawei, i cannot access recovery anymore no matter how hard i try. eRecovery is also not accessible so i cannot turn off my phone. I tried flashing twrp trough fastboot i keep getting an error saying "remote command not allowed". Dload method is not working anymore. If only I can find a way to flash twrp, then I can restore the dump i made using meticulus' twrp.
Click to expand...
Click to collapse
Assuming that you have the unlock code, what happens if you try unlock bootloader again irrespective what status it is now?
_New World Order (NWO)_
[email protected] said:
Assuming that you have the unlock code, what happens if you try unlock bootloader again irrespective what status it is now?
_New World Order (NWO)_
Click to expand...
Click to collapse
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.
NikkoVicedo said:
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.
Click to expand...
Click to collapse
Hi guys, i Got the SAAAAAME Problem, this is all about what i PMd to you danerrickcuba FRP lock and bootloader unlocked. can't go to recovery, but has access to fastboot and wasn't able to do anything to fastboot.
Already fixed my phone. Had to pay 15 euros for DC Phoenix (this software saved me from bringing my phone to huawei service center to have it fix. Thank god!) so I can fix my phone. Recovery, eRecovery, Dload method working, and relocked bootloader. Currently updating my phone through OTA. Tnx danerrickcuba for suggesting methods to fix my phone....
NikkoVicedo said:
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.
Click to expand...
Click to collapse
i have the same problem
bootloader unlock and frp lock ,bootlooping,rec&e-rec destoryed
if you do not log out google /shut down "find my phone"/check oem-unlock in developer mode before downgrading or flashing ,you will get "frp lock" warning
bootlooping may come from wrong update.app. eg. i use dload method to flash rollback(5.0-B300) pkg in EMUI4.1 , my rec and e-rec are destoryed
however, i think fastboot command could do nothing to "bootloader unlock ,frp lock,rec and e-rec destoryed ". i do not know how DC-phoenix fix this and i pay a new motherboard for my mistake
try https://forum.xda-developers.com/showpost.php?p=71338813&postcount=29
Is it possible to re-flash the stock bootloader? I believe mine is corrupt somehow.
It's a bit hard to explain how it's acting without actually seeing it, but it acts sporadic and barely works half the time. For example I can't reboot into the bootloader via adb, trying to power off the phone via bootloader doesn't work, and 9/10 times I try to turn my phone on it goes right to the bootloader.
Not to mention it takes ~15 seconds of holding the power button to get the phone to boot.
Installing Lineage was pretty much a brute force trial and error until it wanted to work.
Any suggestions?
Edit: Realized this is probably in the wrong forum, mod feel free to move it accordingly.
jAm-0 said:
Is it possible to re-flash the stock bootloader? I believe mine is corrupt somehow.
It's a bit hard to explain how it's acting without actually seeing it, but it acts sporadic and barely works half the time. For example I can't reboot into the bootloader via adb, trying to power off the phone via bootloader doesn't work, and 9/10 times I try to turn my phone on it goes right to the bootloader.
Not to mention it takes ~15 seconds of holding the power button to get the phone to boot.
Installing Lineage was pretty much a brute force trial and error until it wanted to work.
Any suggestions?
Edit: Realized this is probably in the wrong forum, mod feel free to move it accordingly.
Click to expand...
Click to collapse
To answer your question, yes, you can reflash the stock bootloader. To do so, in addition to unlocking your bootloader via:
Code:
fastboot flashing unlock
You also need to run the following:
Code:
fastboot flashing unlock_critical
This will allow the bootloader to be overwritten (reinstalled) when you reflash the factory images from Essential's website. The downside here is that just like conventionally unlocking your bootloader this will also wipe your data, it's unavoidable. I believe it would also require you to go back to stock before reinstalling Lineage properly, I'm not 100% sure about that one. It's possible that you may be able to get away with flashing one of the stock firmware dumps from this forum on top of Lineage (8.0B3 preferably, it you intend to return to Lineage), I'm just not sure if they contain the bootloader image, you'd have to check and see. Whatever you flash, you want to make sure it includes a file named abl.
return.of.octobot said:
To answer your question, yes, you can reflash the stock bootloader. To do so, in addition to unlocking your bootloader via:
Code:
fastboot flashing unlock
You also need to run the following:
Code:
fastboot flashing unlock_critical
This will allow the bootloader to be overwritten (reinstalled) when you reflash the factory images from Essential's website. The downside here is that just like conventionally unlocking your bootloader this will also wipe your data, it's unavoidable. I believe it would also require you to go back to stock before reinstalling Lineage properly, I'm not 100% sure about that one. It's possible that you may be able to get away with flashing one of the stock firmware dumps from this forum on top of Lineage (8.0B3 preferably, it you intend to return to Lineage), I'm just not sure if they contain the bootloader image, you'd have to check and see. Whatever you flash, you want to make sure it includes a file named abl.
Click to expand...
Click to collapse
I've fallen victim to way too many bootloops in my quest to get magisk, so I've flashed the factory images probably 10 times. I might just have a defective device.
Welp here's to not giving up and getting Magisk on lineage!!:good:
return.of.octobot said:
To answer your question, yes, you can reflash the stock bootloader. To do so, in addition to unlocking your bootloader via:
Code:
fastboot flashing unlock
You also need to run the following:
Code:
fastboot flashing unlock_critical
This will allow the bootloader to be overwritten (reinstalled) when you reflash the factory images from Essential's website. The downside here is that just like conventionally unlocking your bootloader this will also wipe your data, it's unavoidable. I believe it would also require you to go back to stock before reinstalling Lineage properly, I'm not 100% sure about that one. It's possible that you may be able to get away with flashing one of the stock firmware dumps from this forum on top of Lineage (8.0B3 preferably, it you intend to return to Lineage), I'm just not sure if they contain the bootloader image, you'd have to check and see. Whatever you flash, you want to make sure it includes a file named abl.
Click to expand...
Click to collapse
Does reinstalling the factory image from Essential reinstall the bootloader or should I still run the unlocks (even if Im already unlocked)?
jAm-0 said:
Does reinstalling the factory image from Essential reinstall the bootloader or should I still run the unlocks (even if Im already unlocked)?
Click to expand...
Click to collapse
You have to do the flashing unlock critical if you have not to flash things like bootloader, boot, and modem.
jAm-0 said:
Is it possible to re-flash the stock bootloader? I believe mine is corrupt somehow.
It's a bit hard to explain how it's acting without actually seeing it, but it acts sporadic and barely works half the time. For example I can't reboot into the bootloader via adb, trying to power off the phone via bootloader doesn't work, and 9/10 times I try to turn my phone on it goes right to the bootloader.
Not to mention it takes ~15 seconds of holding the power button to get the phone to boot.
Installing Lineage was pretty much a brute force trial and error until it wanted to work.
Any suggestions?
Edit: Realized this is probably in the wrong forum, mod feel free to move it accordingly.
Click to expand...
Click to collapse
jAm-0 said:
Does reinstalling the factory image from Essential reinstall the bootloader or should I still run the unlocks (even if Im already unlocked)?
Click to expand...
Click to collapse
If you've already unlocked your bootloader you do not need to run fastboot flashing unlock again, however you do need to run fastboot flashing unlock_critical as it is required in order to overwrite the bootloader.
return.of.octobot said:
If you've already unlocked your bootloader you do not need to run fastboot flashing unlock again, however you do need to run fastboot flashing unlock_critical as it is required in order to overwrite the bootloader.
Click to expand...
Click to collapse
Great to know, thanks for the info. Too bad my phone is hardbricked now.
Wont power on
Wont connect to pc
No fastboot
No recovery
Beautiful paper weight
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Spooderman46 said:
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Click to expand...
Click to collapse
I'm not even sure if you can lock the bootloader in stock+ Oreo, but it should be possible. What you can do is go back to MM (MM B10 should be fine), then use a fastboot package for MiFlash (such as A2017U_FASTBOOT_UNLOCK_EDL, it works even though you have a G) or maybe check if EDL Tool has an option to install fastboot, i don't remember.
The other way around it is not locking it and just using a modified bootloader to conceal the 5 second screen. Good enough for sending the phone with warranty. If you'll sell it you might be able to sell it for more if the bootloader is unlocked
Choose an username... said:
I'm not even sure if you can lock the bootloader in stock+ Oreo, but it should be possible. What you can do is go back to MM (MM B10 should be fine), then use a fastboot package for MiFlash (such as A2017U_FASTBOOT_UNLOCK_EDL, it works even though you have a G) or maybe check if EDL Tool has an option to install fastboot, i don't remember.
The other way around it is not locking it and just using a modified bootloader to conceal the 5 second screen. Good enough for sending the phone with warranty. If you'll sell it you might be able to sell it for more if the bootloader is unlocked
Click to expand...
Click to collapse
Thanks I checked the Axon 7 Toolkit and turns out it does have fastboot unlock as part of the process of unlocking the bootloader. Though it techinically doesn't support Oreo I chose the nougat one and it still did the trick albeit with another hardbrick, once locking the bootloader I had to wait for the battery to drain again before I could get into EDL and flash back to Oreo. Very painful proccess, would not recommend, should have just used your method of going back to marshmallow locking then updating again. Thanks anyway mate, the help was much appreciated.
Spooderman46 said:
Thanks I checked the Axon 7 Toolkit and turns out it does have fastboot unlock as part of the process of unlocking the bootloader. Though it techinically doesn't support Oreo I chose the nougat one and it still did the trick albeit with another hardbrick, once locking the bootloader I had to wait for the battery to drain again before I could get into EDL and flash back to Oreo. Very painful proccess, would not recommend, should have just used your method of going back to marshmallow locking then updating again. Thanks anyway mate, the help was much appreciated.
Click to expand...
Click to collapse
I never mentioned the axon7toolkit. That one is finicky, I don't recommend it. I was talking about EDL Tool (you might even find it if you google it), it's here in the ROMs, kernels, development section.
Spooderman46 said:
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Click to expand...
Click to collapse
you need to flash original stock rom for your device trough edl. (rom your device came from factory,you need B11 marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)
Predatorhaze said:
you need to flash original stock rom for your device trough edl. (rom your device came from factory,you need B11 marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)
Click to expand...
Click to collapse
Repeatedly posting the exact same thing in every thread will only get you banned again, you sure you want that?
SaintZ93 said:
Repeatedly posting the exact same thing in every thread will only get you banned again, you sure you want that?
Click to expand...
Click to collapse
Sorry
Hi, I wiped my phone and flashed my normal global ROM with "clean all and lock" by mistake rushing. Now I cannot flashing anything to my phone in fast boot. Just says its in locked state. Phone can only go to fastboot or stock recovery. Cannot flash TWRP or anything. I also cant use the mi unlock bootloader because it says its not linked to this device.
On the recovery screen it says "This MIUI version cant be installed on this device". I have researched and as far as I know I have to put it in EDL mode which I dont want to take the back off for. Is there a cable I can get? Is there another method to unlock the boot loader or get into the phone?
Its a k20 on the box i bought from China with global ROM. The store in New Zealand wont help me because its from China
Vanmanman said:
Hi, I wiped my phone and flashed my normal global ROM with "flash and lock" by mistake rushing. Now I cannot flashing anything to my phone in fast boot. Just says its in locked state. Phone can only go to fastboot or stock recovery. Cannot flash TWRP or anything. Can anyone help me to get my bricked phone back?
Click to expand...
Click to collapse
Did you try to unlock bootloader again?
kh0ngm0tdiemtua said:
Did you try to unlock bootloader again?
Click to expand...
Click to collapse
yes it wont let me. It says this device is not linked to the account or somthing