Hi, I'm trying to relock my phone but I can't get it to boot, 1 logo and Android logo below appear and then it shuts down and reboot to this screen again and finally I end up in recovery. If I unlock my phone I can get it to boot properly.
I suspect a wrong vbmeta. I'm on A14, I've searched everywhere trying to find the appropriate one, but no one works.
Any help?
Hi,
Did you read this one:
https://forum.xda-developers.com/t/stuck-on-red-dot-twrp-screen.4405605/
I had the same problem and tried everything but IMPOSSIBLE to relock bootloader.
Out of last hope, I tried to flash all the partitions of A17 with mtkclient but my phone was then completely bricked (couldnt even access to fastboot or the chinese error message)
Send it to oneplus customer service and they fixed it for free. It would be so nice to have an unbrick tool or a relock bootloader method (the one with mtkclient presented on this forum doesn't seem to work all the time)
JustMan said:
Hi,
Did you read this one:
https://forum.xda-developers.com/t/stuck-on-red-dot-twrp-screen.4405605/
Click to expand...
Click to collapse
Yes I read that but that's not exactly the same. I wasn't stuck at this boot logo, I mean the red dot. I was stuck "before".
Anyway I've fixed it.
I've fixed the problem.
Originaly I was rooted on A14. I've managed to update to A17 while rooted.
Then I relock the bootloader with the tutorial you can find on the forum.
I had multiple issues rooted. My phone seems much more stable now relocked.
I think all the issues I had where caused by inapropriate boot.img or vbmeta.img.
It can be tricky sometimes to find these files matching your oos version.
Anakill said:
I've fixed the problem.
Originaly I was rooted on A14. I've managed to update to A17 while rooted.
Then I relock the bootloader with the tutorial you can find on the forum.
I had multiple issues rooted. My phone seems much more stable now relocked.
I think all the issues I had where caused by inapropriate boot.img or vbmeta.img.
It can be tricky sometimes to find these files matching your oos version.
Click to expand...
Click to collapse
i have no problems all working as well. Did you re lock with Python method?
Mr.Vag said:
i have no problems all working as well. Did you re lock with Python method?
Click to expand...
Click to collapse
Yes python mtk.
Related
Hi, I literally opened the nexus 9 out of the box, powered it on & after choosing a wifi network it began updating, the device crashed during this update and now it won't boot! I've tried & searched for everything, anyone have any ideas?
Booting to recovery with HW buttons, wiping cache/userdata/factory reset - Nada!
Can boot into fastboot, no permission to flash as oem unlock is disabled!
I cant get into the tablet to unlock fastboot oem unlock within devOpitons or usb debugging etc, (com.android.phone has stopped on boot) black screen indefinitely.
I can't flash any images while it is locked
surely there must be a simple method?
desperate here
Return it
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
VermontKindBud said:
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
Click to expand...
Click to collapse
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
syko9 said:
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
Click to expand...
Click to collapse
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
cam30era said:
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
Click to expand...
Click to collapse
Alright thanks for the info, guess it shall be replaced thanks.
syko9 said:
Alright thanks for the info, guess it shall be replaced thanks.
Click to expand...
Click to collapse
Welcome. And FWIW: there's a button for that.
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Ripx88 said:
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Click to expand...
Click to collapse
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
cam30era said:
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
Click to expand...
Click to collapse
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Ripx88 said:
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Click to expand...
Click to collapse
No problem. That's how we learn.
cam30era said:
No problem. That's how we learn.
Click to expand...
Click to collapse
Indeed I'm still new to nexus devices. I've been flashing on Samsung devices for years so I'm still stuck in my Odin ways. Just got the N9 less then a week ago. The whole fastboot thing was foreign at first but I'm getting there lol. Thank you again.
Hello,
situation ist this:
Cyanogen Recovery is installed and there is no rom on the phone. But it won't install a new one through apply update. So I tried installing twrp through fast boot. But it failed with:
FAILED (remote: Device not unlocked cannot flash or erase)
So i tried to unlock it which gave me:
FAILED (remote: oem unlock is disabled)
oem devices gave me tampered = false and unlocked = false
What can I do.
Would appreciate help
Morishno
Flash stock recovery and try unlock again.
Dumb Question but how exactly do I do that?
Just flash it via fast boot? And where do i get it?
Morishno said:
Dumb Question but how exactly do I do that?
Just flash it via fast boot? And where do i get it?
Click to expand...
Click to collapse
You can get it from oneplus downloads section, if you cant find it ask me... Yes you have to flash official stock recovery through fastboot
Exodusche said:
Flash stock recovery and try unlock again.
Click to expand...
Click to collapse
cva_kabil said:
You can get it from oneplus downloads section, if you cant find it ask me... Yes you have to flash official stock recovery through fastboot
Click to expand...
Click to collapse
Not really, OP reports that the unlock command gave him FAILED (remote: oem unlock is disabled)
Hey OP, did you enable OEM Unlocking from Developer options ?
Joshwin Aranha said:
Not really, OP reports that the unlock command gave him FAILED (remote: oem unlock is disabled)
Hey OP, did you enable OEM Unlocking from Developer options ?
Click to expand...
Click to collapse
If not is there any other way?
cva_kabil said:
If not is there any other way?
Click to expand...
Click to collapse
I'm sorry but i do not know any other method that works without flipping that switch in Developer Options.
Joshwin Aranha said:
I'm sorry but i do not know any other method that works without flipping that switch in Developer Options.
Click to expand...
Click to collapse
You dont need to be sorry, thats okay i jus asked... Maybe OP didnt enable oem unlocking.
I didnt enable oem unlocking because it wasnt necessary. The device was unlocked and twrp and cyanogenmod were installed. But somehow cyanogen recovery was installed. Super user was away and I tried to reinstall it. Not knowing the recovery had changed I chose twrp/cwm to install it what resulted in a boot loop. No problem I thought just flash a ROM which didn't worked. No problem just flash a proper recovery it didn't worked. And somehow the device is locked again..
Sorry I was little brief when I said flash stock recovery. I believe if you revert back completely stock you can start the process from the beginning again. That would mean fastboot flash stock recovery then any firmware of OnePlus X. I'm not sure how a bootloader can relock itself.
Exodusche said:
Sorry I was little brief when I said flash stock recovery. I believe if you revert back completely stock you can start the process from the beginning again. That would mean fastboot flash stock recovery then any firmware of OnePlus X. I'm not sure how a bootloader can relock itself.
Click to expand...
Click to collapse
But I couldn't flash twrp.. Is it possible to flash the stock recovery with a locked boot loader? I don't have access to the phone at the moment and i want to gather as much information possible thats why i'm asking
Morishno said:
But I couldn't flash twrp.. Is it possible to flash the stock recovery with a locked boot loader? I don't have access to the phone at the moment and i want to gather as much information possible thats why i'm asking
Click to expand...
Click to collapse
I'm not sure but this has been addressed many times. Comb the threads you will find the information you need.
Exodusche said:
I'm not sure but this has been addressed many times. Comb the threads you will find the information you need.
Click to expand...
Click to collapse
Found a hard brick guide. You mean that?
So I just remembered something was able to help someone else with a similar issue. If you can boot Into something and your rooted download the app Rashr. With it you can flash stock recovery and be back in business.
The problem is i dont have anything to Boot
//UPDATE: So I tried booting with fastboot boot but it said cannot boot device isn't unlocked.
Edited
So i managed to save the Phone using the Hard Brick Guide. Thanks everyone!
Thank goodness for the hard brick guide. ?
Exodusche said:
I think your gonna have to go through the hard bricked guide.
Click to expand...
Click to collapse
Yeah i did that and it worked thank you
I have access to an engineering bootloader for the Tmo Note8 and I would like to know how to test if it is unlocked.
Is there a specific process to determine if the bootloader is locked? Are there steps to permanently unlock the bootloader from an engineering bootloader?
I've searched all the Note8 forums and haven't found any answers.
Sent from my SM-G892U using Tapatalk
reukiodo said:
I have access to an engineering bootloader for the Tmo Note8 and I would like to know how to test if it is unlocked.
Is there a specific process to determine if the bootloader is locked? Are there steps to permanently unlock the bootloader from an engineering bootloader?
I've searched all the Note8 forums and haven't found any answers.
Click to expand...
Click to collapse
Flashing it and then checking if you can unlock it would be how to go about it. Except you can't flash unsigned images without unlocking so it's a catch 22 really. And it may just brick your phone even if you flashed it successfully. No way of knowing if that bootloader will even boot your device or play nice with the other partitions.
Gizmoe said:
Flashing it and then checking if you can unlock it would be how to go about it. Except you can't flash unsigned images without unlocking so it's a catch 22 really. And it may just brick your phone even if you flashed it successfully. No way of knowing if that bootloader will even boot your device or play nice with the other partitions.
Click to expand...
Click to collapse
The eng bootloader is signed, so there is no problem flashing the eng bootloader. I just do not know how to test if it is unlocked, as I can't find a recovery image to flash, and I do not know how to create one myself.
Sent from my SM-G892U using Tapatalk
reukiodo said:
The eng bootloader is signed, so there is no problem flashing the eng bootloader. I just do not know how to test if it is unlocked, as I can't find a recovery image to flash, and I do not know how to create one myself.
Sent from my SM-G892U using Tapatalk
Click to expand...
Click to collapse
probably just the combo files that are used for samfail imo. if you want to upload and have me check them lmk but more then likely all you have is the combo firmware we have been using since day one
Team DevDigitel said:
probably just the combo files that are used for samfail imo. if you want to upload and have me check them lmk but more then likely all you have is the combo firmware we have been using since day one
Click to expand...
Click to collapse
https://drive.google.com/file/d/1PIVZs-uB8kKb9YbY_fAcYJCGIfdb27W5/view?usp=drivesdk
This might only work on the T-Mobile version.
reukiodo said:
https://drive.google.com/file/d/1PIVZs-uB8kKb9YbY_fAcYJCGIfdb27W5/view?uk
This might only work on the T-Mobile version.
Click to expand...
Click to collapse
Do you have the boot.img that matches this?
Unable to check the rest without as it won't boot the combo img.
Yes it is a eng img.
We are on multi csc devices so all are same for flashing sake, as long as it's not the exynos.
Please remove the public link and we can move to pm/telegram and speak further
Team DevDigitel said:
Do you have the boot.img that matches this?
Unable to check the rest without as it won't boot the combo img.
Yes it is a eng img.
We are on multi csc devices so all are same for flashing sake, as long as it's not the exynos.
Please remove the public link and we can move to pm/telegram and speak further
Click to expand...
Click to collapse
I disabled the link, though not sure why I should? I haven't gotten telegram yet. I just want to know if it is unlocked for flashing custom recovery such as TWRP.
reukiodo said:
I disabled the link, though not sure why I should? I haven't gotten telegram yet. I just want to know if it is unlocked for flashing custom recovery such as TWRP.
Click to expand...
Click to collapse
No one has compiled twrp for snapdragon because we dont have a unlocked bl. Removing link is primarily to avoid people flashing this or reposting it with incorrect info and causing confusion.
If I can get the boot.img as well that is compiled for this bootloader I can get a running system and see if it can be unlocked. Otherwise without it there's no way to determine some of the important factors here. Just flashing against device to test is quite risky.
The bl is compatible with all snapdragon and does install correctly but it won't boot with the combo imgs we use for samfail or a stock img.
Link is still active fyi and I've sent you a pm with telegram info. It's a group for us and a few other devs that can work with us to get things sorted.
I used the engineering bootloader with Odin, after it flashed showed it as an eng boot loader not user, says Samsung official and is still locked. I booted with a binary .img booted and oem option from the settings was there, showed the same unlocked img on boot as samfail also. But I didn't do much other than check those things. I tried to load samfail system but it didn't load I figured as much seeing samfail boot.img is user-test not user-release and has custom binary but I don't know that much
I am wondering if we don't have to leave the eng boot loader on and oem toggled for a week like exyos versions before we can flash custom binary
DroidisLINUX said:
I used the engineering bootloader with Odin, after it flashed showed it as an eng boot loader not user, says Samsung official and is still locked. I booted with a binary .img booted and oem option from the settings was there, showed the same unlocked img on boot as samfail also. But I didn't do much other than check those things. I tried to load samfail system but it didn't load I figured as much seeing samfail boot.img is user-test not user-release and has custom binary but I don't know that much
I am wondering if we don't have to leave the eng boot loader on and oem toggled for a week like exyos versions before we can flash custom binary
Click to expand...
Click to collapse
I'm wondering if after flashing this engineering bootloader we can root phone just by simply using command prompt and sideloading root files. Any ideas? I don't know enough to do this.
Sent from my [device_name] using XDA-Developers Legacy app
Eudeferrer said:
I'm wondering if after flashing this engineering bootloader we can root phone just by simply using command prompt and sideloading root files. Any ideas? I don't know enough to do this.
Click to expand...
Click to collapse
I don't believe so, until we can get it unlocked, when in download mode it says the boot loader is still locked and says system secure in red and official binaries but if we can get the boot loader to say unlocked then I believe it will probably be possible. At least it says eng boot loader and tells us it's locked and that means it can be unlocked it's just a matter of time until someone gets it unlocked now
I am glad I haven't updated to boot loader 3 now, this is bootloader 2 so if you go to oreo you won't be able to use this when and if it's unlocked
DroidisLINUX said:
I don't believe so, until we can get it unlocked, when in download mode it says the boot loader is still locked and says system secure in red and official binaries but if we can get the boot loader to say unlocked then I believe it will probably be possible. At least it says eng boot loader and tells us it's locked and that means it can be unlocked it's just a matter of time until someone gets it unlocked now
I am glad I haven't updated to boot loader 3 now, this is bootloader 2 so if you go to oreo you won't be able to use this when and if it's unlocked
Click to expand...
Click to collapse
Has anyone tried the same procedure/comands used to unlock the Pixel XL? Would they even work I this phone if it had this eng bootloader? I wish I knew enough about this stuff to try it out or even know if it would work.
Sent from my [device_name] using XDA-Developers Legacy app
DroidisLINUX said:
I used the engineering bootloader with Odin, after it flashed showed it as an eng boot loader not user, says Samsung official and is still locked. I booted with a binary .img booted and oem option from the settings was there, showed the same unlocked img on boot as samfail also. But I didn't do much other than check those things. I tried to load samfail system but it didn't load I figured as much seeing samfail boot.img is user-test not user-release and has custom binary but I don't know that much
I am wondering if we don't have to leave the eng boot loader on and oem toggled for a week like exyos versions before we can flash custom binary
Click to expand...
Click to collapse
you could test,
but if you look under the info on the boot up screen, secure boot is still set to : enabled
IE: each and every boot it checks for a modified boot.img and if found it fails secure check.
I never tested the oem unlock options etc, or waiting any time frame, just mostly seeing what we could use with it.
The phone wont boot a modified system as well. has to be unrooted stock system + stock boot.img to boot with the eng bootloader.
Unfortunately i havent heard anything back, was hoping we could get the boot.img that is ENG so we can boot the entire setup and go.
I impulsively unlocked the boot-loader on my Mate 20 Pro last night because Funky Huawei was selling the codes for $20. Today I can't really think of a good reason I actually need the bootloader unlocked since I have no interest in rooting my phone and there are update methods for manually flashing firmware that don't require an unlocked bootloader. In fact, the tool posted on XDA for updating firmware with an unlocked bootloader apparently requires that you be rooted to use it.
Is there a way to relock the bootloader?
The only mention I could find in these threads was someone who said you need to factory reset the phone and then go back into fast-boot. I don't think the person who wrote that even tried it and that he was just making a generalization.
Does anyone know if there are actual steps that relock the bootloader without bricking the phone--which the e-recovery restore method might do since it will try to install an older firmware than is currently on my phone.
I might just keep it unlocked anyway but I was curious if there was a known relock method that works on this phone.
jhs39 said:
I impulsively unlocked the boot-loader on my Mate 20 Pro last night because Funky Huawei was selling the codes for $20. Today I can't really think of a good reason I actually need the bootloader unlocked since I have no interest in rooting my phone and there are update methods for manually flashing firmware that don't require an unlocked bootloader. In fact, the tool posted on XDA for updating firmware with an unlocked bootloader apparently requires that you be rooted to use it.
Is there a way to relock the bootloader?
The only mention I could find in these threads was someone who said you need to factory reset the phone and then go back into fast-boot. I don't think the person who wrote that even tried it and that he was just making a generalization.
Does anyone know if there are actual steps that relock the bootloader without bricking the phone--which the e-recovery restore method might do since it will try to install an older firmware than is currently on my phone.
I might just keep it unlocked anyway but I was curious if there was a known relock method that works on this phone.
Click to expand...
Click to collapse
Have a look at my post in thread below .. have done this method a few times and works for me.
https://forum.xda-developers.com/ma...ocking-bootloader-magisk-root-t3885422/page22
jhs39 said:
I impulsively unlocked the boot-loader on my Mate 20 Pro last night because Funky Huawei was selling the codes for $20. Today I can't really think of a good reason I actually need the bootloader unlocked since I have no interest in rooting my phone and there are update methods for manually flashing firmware that don't require an unlocked bootloader. In fact, the tool posted on XDA for updating firmware with an unlocked bootloader apparently requires that you be rooted to use it.
Is there a way to relock the bootloader?
The only mention I could find in these threads was someone who said you need to factory reset the phone and then go back into fast-boot. I don't think the person who wrote that even tried it and that he was just making a generalization.
Does anyone know if there are actual steps that relock the bootloader without bricking the phone--which the e-recovery restore method might do since it will try to install an older firmware than is currently on my phone.
I might just keep it unlocked anyway but I was curious if there was a known relock method that works on this phone.
Click to expand...
Click to collapse
Use dload method, but pba that will erase everything like your 1st setting of your phone. Phone will be locked again, FRP will still unlocked.
Sent from my LYA-L29 using Tapatalk
does dload method altso come with recovery_ramdisk fixed? for us that have modified it for root or twrp??
So that the device becomes out of the box like new?
Yes, recovery_ramdisk back to stock with dload method
Sent from my LYA-L29 using Tapatalk
i can confirm dload method lock back the bootloader.
i had install an alternate fw but was not satisfied cause too much features were not working, i used first erecovery to download official fw but unlock bl was still present. then i try dload and phone was completly reset with bl locked.
dload method isn't working for me. I extracted the UPDATE.APP from the firmware version that is currently installed on my phone (using the update_full_base version), created a dload folder on my external card, copied the UPDATE.APP into that folder and then did the dial code and selected update from memory card. My phone reboots and then I get an error that says that the update failed.
Do I need to use the UPDATE.APP from a specific build to get this to work?
I installed firmware via the Funky Huawei method. It seems to have relocked the bootloader because the warning about the bootloader being unlocked doesn't come up when the phone boots but the data on my phone wasn't erased. Can the bootloader be relocked without erasing all the data on the phone? If so this is the first I've heard of it.
jhs39 said:
I installed firmware via the Funky Huawei method. It seems to have relocked the bootloader because the warning about the bootloader being unlocked doesn't come up when the phone boots but the data on my phone wasn't erased. Can the bootloader be relocked without erasing all the data on the phone? If so this is the first I've heard of it.
Click to expand...
Click to collapse
Go to fastboot mode and check if bootloader is locked again.
Sent from my LYA-L29 using Tapatalk
ubersapian said:
Have a look at my post in thread below .. have done this method a few times and works for me.
https://forum.xda-developers.com/ma...ocking-bootloader-magisk-root-t3885422/page22
Click to expand...
Click to collapse
Will we able to reclaim warranty after relock? Anyway the service guys would be able to know that the bootloader was unlocked before?
Soo what is the legit way to relock the bootloader and the FRP?
is the FRP from stock/defualt locked?
Verstuurd vanaf mijn LYA-L29 met Tapatalk
Hi everyone, first of all, thanks for reading and trying to help out.
I have a 1+7t Pro Indian unit. I unlocked the Bootloader on my device and installed Magisk but as I saw that there were not much benefits of rooting at the moment since twrp is not also available yet so no flashing of custom roms.
So I tried to relock the Bootloader. For that I Flashed the stock rom from scratch so that no modifications stay in the system and then tried "fastboot oem lock". This however got me into a bricked stage where I got following error:
"Your device is currept. It can not be trusted and will not boot."
This comes with a red exclamation mark and nothing happens means it gets bricked. I also tried "fastboot flashing lock". That did not work either. I did unbrick it without any issue but I want to relock the Bootloader just in case I need to sell the device.
Has anyone faced the same problem or could help me out here?
Any help much appreciated and thanks in advance!!
Chandler_Bing_1995 said:
Hi everyone, first of all, thanks for reading and trying to help out.
I have a 1+7t Pro Indian unit. I unlocked the Bootloader on my device and installed Magisk but as I saw that there were not much benefits of rooting at the moment since twrp is not also available yet so no flashing of custom roms.
So I tried to relock the Bootloader. For that I Flashed the stock rom from scratch so that no modifications stay in the system and then tried "fastboot oem lock". This however got me into a bricked stage where I got following error:
"Your device is currept. It can not be trusted and will not boot."
This comes with a red exclamation mark and nothing happens means it gets bricked. I also tried "fastboot flashing lock". That did not work either. I did unbrick it without any issue but I want to relock the Bootloader just in case I need to sell the device.
Has anyone faced the same problem or could help me out here?
Any help much appreciated and thanks in advance!!
Click to expand...
Click to collapse
Same here when I was trying to lock bootloader of my 7T (non pro) yesterday. I figured out a solution. Simply download unbrick tool, connect device in Qualcomm EDL mode and flash proper firmware (choose between india and O2 (which mean global) firmware. After restoring firmware with MSM tool your device bootloader will be locked again.
EugenStanis said:
Same here when I was trying to lock bootloader of my 7T (non pro) yesterday. I figured out a solution. Simply download unbrick tool, connect device in Qualcomm EDL mode and flash proper firmware (choose between india and O2 (which mean global) firmware. After restoring firmware with MSM tool your device bootloader will be locked again.
Click to expand...
Click to collapse
Thanks a lot, will try that.
Chandler_Bing_1995 said:
Thanks a lot, will try that.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261684661