Related
I've got quite a problem.
A few weeks ago, I unlocked the bootloader on my phone and flashed SuperSu to root it.
Today I decided to lock it back for personal reasons, wiping everything.
After it wiped, the phone kinda softbricked. When it turns on the OnePlus logo flashes for a second and turns off.
Won't let me unlock bootloader again, got stock recovery. Tried to use sideload, but ADB can't read the file. My guess it's too large.
What can I do?
I had same problem. Follow the steps. Unlock it again and reboot to the system.
There enable developer option, enable debugging, enable unlock bootloader option.
Rebooted to fastboot mode
Install stock recovery
Adb sideload 3.2 full firmware.
After that reboot your phone to fastboot mode.
Unlock bootloader.
This should do it.
Sent from my ONEPLUS A3003 using Tapatalk
It's like you didn't even read what I wrote...
I said it doesn't boot to system, OnePlus logo appears for a split second and phone turns off.
Bootloader is locked and I cannot flash anything.
ADB Sideload won't read files. Gives the 'cannot read' error.
You know that you can load to bootloader by pressing volume up and power button right?
Sent from my ONEPLUS A3003 using Tapatalk
Monskiller said:
I've got quite a problem.
A few weeks ago, I unlocked the bootloader on my phone and flashed SuperSu to root it.
Today I decided to lock it back for personal reasons, wiping everything.
After it wiped, the phone kinda softbricked. When it turns on the OnePlus logo flashes for a second and turns off.
Won't let me unlock bootloader again, got stock recovery. Tried to use sideload, but ADB can't read the file. My guess it's too large.
What can I do?
Click to expand...
Click to collapse
You should be fine so long as you didn't deactivate the"OEM UNLOCK " option from the developer setting....
do the following
1. press and hold the volume up an power buttons simultaneously to enter the boot loader menu.
2.select start option from the bootloader menu sorry that menu is the boot loader.
3. now connect to pc and use the "fastboot devices" command to see if your pc recognizes you op3 as an android device.
4.type "fastboot oem unlock"
5. flash the custom recovery thru fastboot
5. enter custom recovery and flash your desired rom.
hope this works for you!
ajaysoranam said:
You should be fine so long as you didn't deactivate the"OEM UNLOCK " option from the developer setting....
do the following
1. press and hold the volume up an power buttons simultaneously to enter the boot loader menu.
2.select start option from the bootloader menu sorry that menu is the boot loader.
3. now connect to pc and use the "fastboot devices" command to see if your pc recognizes you op3 as an android device.
4.type "fastboot oem unlock"
5. flash the custom recovery thru fastboot
5. enter custom recovery and flash your desired rom.
hope this works for you!
Click to expand...
Click to collapse
And if by mistake I have deactivate the "OEM UNLOCK " what can I do?
I relocked the bootloader. Which wiped to factory reset.
That wipe deactivated the ability to unlock bootloader until reactivated from the system, which I cannot get to because the phone turns off/bootlops before loading it.
This happened quite a few times on this forum, there is really no reason to relock the bootloader on the op3, it is covered through warranty, but u will have to contact oneplus and they should walk u through and send u files to unbrick it if u r lucky
ovidiu1982 said:
And if by mistake I have deactivate the "OEM UNLOCK " what can I do?
Click to expand...
Click to collapse
then you better get in touch with the op customer service. they will, from what i know, fix it thru a remote connection sitting.
I have no solution for you, but I wonder if you went back to stock recovery first before you relocked the bootloader? I think if you have TWRP and try to relock the bootloader, this happens. NOT that its helpful to you, but if this is the case and you can verify it, might help others avoid making the same mistake.
As far as your problem is concerned, I would look for unbricking guides. I know I saw at least one guide that lets you recreate the entire partition table manually and make it just like new for the OP2 (and has the company's blessings to do so). So it should apply here as well. Sorry, do not remember where I saw this, but must have been either on xda or the oneplus forums.
karthikrr said:
I have no solution for you, but I wonder if you went back to stock recovery first before you relocked the bootloader? I think if you have TWRP and try to relock the bootloader, this happens. NOT that its helpful to you, but if this is the case and you can verify it, might help others avoid making the same mistake.
As far as your problem is concerned, I would look for unbricking guides. I know I saw at least one guide that lets you recreate the entire partition table manually and make it just like new for the OP2 (and has the company's blessings to do so). So it should apply here as well. Sorry, do not remember where I saw this, but must have been either on xda or the oneplus forums.
Click to expand...
Click to collapse
I have stock recovery. I did boot TWRP first and let it change system by mistake, but reflashed stock later. That's what might have caused the bootloop once I relocked.
So I guess if you decide to relock in the future, don't flash TWRP, cause it bootloops, even if stock is reflashed.
Bro don't worry now.
I am gonna guide you out of this.
First install an adb package like this.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Now get a toolkit like this.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Try to connect to fastboot and check for your device in the toolkit.
If failed then kill process adb in your task manager.
Now once connected.
Check OEM status and bootloader status.
Unlock if required.
Now.
Push twrp to your phone .
Then boot into it through the toolkit.
Now load a full ROM.
http://forum.xda-developers.com/oneplus-3/development/rom-op3lite-debloated-tweaked-fast-t3404996
Just copy paste it using your file manager on PC.
Them flash first make it boot and then root.
Hope this helped.
Monskiller said:
I have stock recovery. I did boot TWRP first and let it change system by mistake, but reflashed stock later. That's what might have caused the bootloop once I relocked.
So I guess if you decide to relock in the future, don't flash TWRP, cause it bootloops, even if stock is reflashed.
Click to expand...
Click to collapse
Nah, I think this happens only if you let TWRP modify the system partition. But, I have not and am not willing to test it out
karthikrr said:
Nah, I think this happens only if you let TWRP modify the system partition. But, I have not and am not willing to test it out
Click to expand...
Click to collapse
Don't test it. I've already done it by mistake.
It replaced recovery with TWRP by allowing the modification of system and even after reflashing stock it'll bootloop on relocking recovery.
So I found something useful then.
Hey, i think i found a solution for you. I don't know if i can post here xda thread links, so search "EDL Mode xda" on Google and the first link it is. Hope i helped
I wonder if anyone is able to help.
my 5x is stuck in bootloop. i can downkey on volume to menu but te recovery options just leads back to bootloop.
my bootloader is locked and from the bootloop i cant access the phones developer options as the phone wont boot up.
is there any way of unlocking the phone so i can reflash stock from a phone that wont boot up
MIni
oldsnow said:
I wonder if anyone is able to help.
my 5x is stuck in bootloop. i can downkey on volume to menu but te recovery options just leads back to bootloop.
my bootloader is locked and from the bootloop i cant access the phones developer options as the phone wont boot up.
is there any way of unlocking the phone so i can reflash stock from a phone that wont boot up
MIni
Click to expand...
Click to collapse
The actual bootloader unlocking is done in bootloader mode with fastboot.
Try unlocking it in fastboot anyway and see what happens. If your rom is corrupt it might not stop you.
Try restoring the stock image and see what it does, if it fails try unlocking the bootloader, ignoring the oem unlock process.
Are you on stock recovery? Are you on a custom rom? If you are have you tried dirty flashing it?
Have you tried clearing cache and delvik cache?
Darke5tShad0w said:
I don't think stock images require you to unlock the bootloader anymore.
Click to expand...
Click to collapse
When did that change? Reference?
sfhub said:
When did that change? Reference?
Click to expand...
Click to collapse
I checked again and it seems they were talking about OTA's. opps.
Then when I went to download the full image the other day they had changed it from a required warning to just a "if necessary" and I put it together wrong.
UPDATE 17.06.2019 - NEW RMM/KG bypass patch
UPDATE 23.02.2019 - Pie and more
Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything.
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about this guide!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Flashing any custom binary will trigger knox and you may lose your warranty. Make sure you know what you do to your device.
Introduction
December 2017 update (for some even older) brought us a different lock, that creates panic among users as usual. As described here by my friend @BlackMesa123, this is not a lock to developement, rather an advanced lock for theft or scams. This has a bypass too, specially when you`re the owner of the device.
How it works
This lock is in bootloader, but the trigger to it is inside the system, it`s hard to reproduce, but usually happens when you plug another country sim than your firmware country, because changing the country might not seem as a traveling guy and more like a thief. If you are on stock rom all this time, you might not feel the change, as the device reboots and wipes data, but it will eventually boot. The nice thing comes if you already have custom binary installed (rooted kernel or twrp), as you can`t boot anymore because bootloader is preventing you to boot on custom binaries and alter the system.
Devices confirmed to have the lock:
Any other Samsung device manufactured after 2017
Samsung Galaxy S9 & S9+ - SM-G960F & SM-G965F
Samsung Galaxy Note 8 - SM-N950F
Samsung Galaxy S8 & S8+ - SM-G950F & SM-G955F
Samsung Galaxy A8 & A8+(2018) - SM-A530F & SM-A730F
Samsung Galaxy A Series (2017) - SM-A320F/FL, SM-A520F & SM-A720F
Samsung Galaxy Note FE - N935F
How to know if you are locked
There are 3 things at this chapter:
1. "Only official released binaries are allowed to be flashed" message shows up and now you know for sure you got locked outside your phone
2. Missing OEM unlock toggle in developer settings, if your device has FRP
3. "RMM state = Prenormal" in download mode
How to unlock
1. As i personally did, and other users reported, if you face any of the things above, flash latest full stock fw of your country with Odin, boot up, don`t reboot, don`t unplug the sim and don`t disconnect the network connection for 7 full days (168h). It seems that after 7 days of uptime, RMM state resets and you can flash TWRP again without issues. You can see uptime in settings/about device/status.
2. Some users reported this guide was working in first Oreo fw releases, can't guarantee it still works.
How to avoid getting locked again
Unfortunately bootloader can`t be reverted to older revisions, so we need to live with this. My friend @BlackMesa123 made some investigation and found out how to disable this lock. After waiting those 7 days, go to settings/developer option and enable OEM unlock. In order to never get locked again, flash TWRP for your device (install instructions below), boot into TWRP (do not boot into rom yet as you might get locked again), download and flash his fix from here (don`t forget to thank him too for his findings).
You can keep this zip near and flash it after flashing any custom rom, to be sure you don`t get locked again. The zip contains an universal script that disables the services responsable. Can be flashed on any device, if the device has the lock, won`t get locked again, if not, nothing will happend. I like to say "better safe than sorry".
How to safely install TWRP
Considering you are already unlocked (waited those 7 days), follow the next steps carefully:
Make sure you downloaded latest Odin, samsung usb drivers installed, latest RMM-State_Bypass fix (download links are in #2 post) and latest TWRP available for your device
Put RMM-State_Bypass.zip in external sdcard
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Reboot the phone into download mode and connect the usb cable
Open Odin, go into options and untick Auto-reboot and put the TWRP tar file in AP tab of odin, hit Start and wait
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Power" + "Vol. Down" + "Vol. Up" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Vol. Up" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
***Don't boot into rom because it will lock your device again!!!!
Once the custom recovery booted, swipe to "Allow modification" and flash RMM-State_Bypass.zip as normal zip
Now you can reboot into rom and hopefully never get locked again.
If any of above steps fail, redo from step 1, more carefully this time.
How to safely root
Considering you already unlocked (waited those 7 days) and you have TWRP installed, follow the next steps carefully:
Download root zip and no-verity-opt-encrypt-6.0 (download links are in #2 post) and drop the zips into external sdcard
Boot into TWRP and swipe "Allow modifications"
Go into Wipe menu and select "Format data" - note that this will erase all your data including internal storage
Reboot recovery, swipe to "Allow modification" and flash RMM-State_Bypass.zip
Flash no-verity-opt-encrypt-6.0 zip downloaded at step #1 to disable data partition encryption
Flash root zip downloaded at step #1
Reboot the phone into system
After booting up in setting wizard make sure to uncheck diagnostic data
If any of above steps fail, redo from step 1, more carefully this time.
You can read more about it here here, here, here, here or here.
Credits
@BlackMesa123
@RicePlay33
@Yahia Angelo
@TaifAljaloo
@ananjaser1211
Useful links
Samsung Firmware download - Updato / Sammobile / Samsung-Firmware.org / Samsung-Updates.com
Samsung Usb Drivers
Odin 3.13.1
Latest SuperSU stable or test/beta
Latest Magisk stable or test/beta
NEW-RMM-State_Bypass
no-verity-opt-encrypt-6.0
FAQ
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes?
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Q: Why not formatting data at twrp install?
A: Phone will boot even if data is encrypted if you don't root. Also system partition is not encrypted meaning you can flash RMM-State_Bypass anyway.
Reserved for later use [emoji16]
corsicanu said:
Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything.
[*]After booting up in setting wizard make sure to uncheck diagnostic data
[/LIST]
Click to expand...
Click to collapse
The above item, diagnostic data, may have been the reason for blocking again the RMM STATE, since it was the only thing I did not do?
Perfect... Merci (bien suivre les indications et aucun problèmes...)
In Odin Mode:
FRP unlock
OEM unlock
[email protected] said:
Perfect... Merci (bien suivre les indications et aucun problèmes...)
In Odin Mode:
FRP unlock
OEM unlock
Click to expand...
Click to collapse
If you read again first post you'll see i already mentioned to make sure you have the OEM unlock toggle as On.
The toggle reflects the state of OEM unlock:
Toggle ON - phone unlocked, OEM off, FRP off.
Toggle OFF - phone locked, OEM on, FRP on.
Sent from my SM-A530F using Tapatalk
corsicanu said:
If you read again first post you'll see i already mentioned to make sure you have the OEM unlock toggle as On.
The toggle reflects the state of OEM unlock:
Toggle ON - phone unlocked, OEM off, FRP off.
Toggle OFF - phone locked, OEM on, FRP on.
Sent from my SM-A530F using Tapatalk
Click to expand...
Click to collapse
Question does twrp get flashed permanent ?
Sent from my LEX720 using xda premium
mchlbenner said:
Question does twrp get flashed permanent ?
Sent from my LEX720 using xda premium
Click to expand...
Click to collapse
Yes.
Sent from my SM-A530F using Tapatalk
Update?
corsicanu said:
If you read again first post you'll see i already mentioned to make sure you have the OEM unlock toggle as On.
The toggle reflects the state of OEM unlock:
Toggle ON - phone unlocked, OEM off, FRP off.
Toggle OFF - phone locked, OEM on, FRP on.
Sent from my SM-A530F using Tapatalk
Click to expand...
Click to collapse
Hello can you tell me how install official firmware update? The best way?
- With Flashfire and keep root etc... (maybe too TWRP)
- Or Odin and reroot?
Thanks for your response...
[email protected] said:
Hello can you tell me how install official firmware update? The best way?
- With Flashfire and keep root etc... (maybe too TWRP)
- Or Odin and reroot?
Thanks for your response...
Click to expand...
Click to collapse
Personally i'd recommend flashing using odin. Flash the FW in odin, force it reboot in download mode, flash twrp, force the phone in twrp, flash again rmm bypass and you'll have updated fw with lock disabled.
Regards.
Sent from my SM-A530F using Tapatalk
corsicanu said:
Personally i'd recommend flashing using odin. Flash the FW in odin, force it reboot in download mode, flash twrp, force the phone in twrp, flash again rmm bypass and you'll have updated fw with lock disabled.
Regards.
Sent from my SM-A530F using Tapatalk
Click to expand...
Click to collapse
Install via Odin andOK but lose all... After the problemis impossible install TWRP (Little red line in (Odin) Download Mode who said "Only official released binaries are allowed to be flashed (RECOVERY)"), and my FRP and my OEM always OFF ...
Or waiting like describe here: https://forum.xda-developers.com/galaxy-note-8/help/official-released-binaries-allowed-to-t3681883
[email protected] said:
Install via Odin andOK but lose all... After the problemis impossible install TWRP (Little red line in (Odin) Download Mode who said "Only official released binaries are allowed to be flashed (RECOVERY)"), and my FRP and my OEM always OFF ...
Or waiting like describe here: https://forum.xda-developers.com/galaxy-note-8/help/official-released-binaries-allowed-to-t3681883
Click to expand...
Click to collapse
You have to developers in settings and click on about 7 times enable OEM unlock.
I hear what been happening idea!
Zips you need make sure you get them and flash all.
SuperSU.zip.
RMM-state-by pass mesa.zip
NO-verity-no-encrypt ashyx.zip
Don't put sim card in then boot up go to developers setting enable OEM unlock.
Make sure all your drivers are installed.
Setup Odin next put your phone in download mode next flash twrp.
Then hold volume up and down +power when screen turn black hold power+ volume+.
You will go into twrp flash all your zips then reformat data and reboot.
Make sure you swipe to allow modifications.
You should boot up fine but slow.
Sent from my LEX727 using xda premium
mchlbenner said:
You have to developers in settings and click on about 7 times enable OEM unlock.
I hear what been happening idea!
Zips you need make sure you get them and flash all.
SuperSU.zip.
RMM-state-by pass mesa.zip
NO-verity-no-encrypt ashyx.zip
Don't put sim card in then boot up go to developers setting enable OEM unlock.
Make sure all your drivers are installed.
Setup Odin next put your phone in download mode next flash twrp.
Then hold volume up and down +power when screen turn black hold power+ volume+.
You will go into twrp flash all your zips then reformat data and reboot.
Make sure you swipe to allow modifications.
You should boot up fine but slow.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Thanks for your help...
I'll remove my sim card in then boot up go to developers setting, but i've not enable OEM unlock line.
My drivers are OK.
The first time for the root it was easy, now problem persist with OEM....(maybe due update with latest A730FXXU2ARC9).
I'm waiting a few days to see if OEM unlock reappears...
[email protected] said:
Thanks for your help...
I'll remove my sim card in then boot up go to developers setting, but i've not enable OEM unlock line.
My drivers are OK.
The first time for the root it was easy, now problem persist with OEM....(maybe due update with latest A730FXXU2ARC9).
I'm waiting a few days to see if OEM unlock reappears...
Click to expand...
Click to collapse
Are you locked out?
Sent from my LEX727 using xda premium
mchlbenner said:
Are you locked out?
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Sorry for my bad English, i don't understand this???
It does remove lock code or Bootloader? (i'll remove all code who work with this phone...)
I'm not locked to any carrier...
I read this:
Firmware to last version and this update blocked the bootloader.
In Europe latest firmware's are locked so you can't flash TWRP via Odin.
But countries like India, Turkey etc.... there isn't any problem.
https://forum.xda-developers.com/samsung-a-series-2017/help/help-flash-twrp-t3715529
[email protected] said:
Sorry for my bad English, i don't understand this???
It does remove lock code or Bootloader? (i'll remove all code who work with this phone...)
I'm not locked to any carrier...
I read this:
Firmware to last version and this update blocked the bootloader.
In Europe latest firmware's are locked so you can't flash TWRP via Odin.
But countries like India, Turkey etc.... there isn't any problem.
https://forum.xda-developers.com/samsung-a-series-2017/help/help-flash-twrp-t3715529
Click to expand...
Click to collapse
Actually after 7-9 days the OEM Unlock reappears in developer settings...
And you can again via Odin reinstall TWRP and SuperSU...
But don't forget erase data (factory reset), otherwise you may have some problems...
:laugh:
[email protected] said:
Actually after 7-9 days the OEM Unlock reappears in developer settings...
And you can again via Odin reinstall TWRP and SuperSU...
But don't forget erase data (factory reset), otherwise you may have some problems...
:laugh:
Click to expand...
Click to collapse
Make sure you do all your installs with twrp before you reformat your device.
Keep in mind after reformat all you had on your sdcard is gone mtp doest work on twrp.
If you reboot without those zips you will be locked out for around 168 hours again.
Sent from my LEX727 using xda premium
mchlbenner said:
Make sure you do all your installs with twrp before you reformat your device.
Keep in mind after reformat all you had on your sdcard is gone mtp doest work on twrp.
If you reboot without those zips you will be locked out for around 168 hours again.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Thank you that happened to me ... And wait again ...
Because the first time it worked, but i'll erase some applications like knox ... (with root uninstaller), and after reboot black screen and red message, and nothing... Require to install the firmware via Odin and wait 168h.:fingers-crossed:
[email protected] said:
Thank you that happened to me ... And wait again ...
Because the first time it worked, but i'll erase some applications like knox ... (with root uninstaller), and after reboot black screen and red message, and nothing... Require to install the firmware via Odin and wait 168h.:fingers-crossed:
Click to expand...
Click to collapse
this what did with and it worked I did this with no SIM card in you will have to reformat first.
make sure you have a micro sdcard for device.
install usb driver for device and download odin and set it up.
download twrp and root,mesascustom kernel v1.zip, no verify no encrypt.ashy yx. zip.
flash recovery with odin in ap after pass unplug hold power and volume up down at the same time.
when right when download leaves then push on power and volume up you will boot into twrp then make sure you have put in micro sdcard and swipe to allow modifications and then reformat device.
I chose to reboot to recovery.
go to micro sdcard and do your install.
then reboot phone after check your phone root and you check everything turn of your phone.
put in SIM card and turn on phone.
the no SIM will work that is what I did.
Sent from my SM-A730F using xda premium
Hello, Need precision my english is limited ...
mchlbenner said:
this what did with and it worked I did this with no SIM card in you will have to reformat first.
make sure you have a micro sdcard for device.
install usb driver for device and download odin and set it up.
download twrp and root,mesascustom kernel v1.zip, no verify no encrypt.ashy yx. zip.
flash recovery with odin in ap after pass unplug hold power and volume up down at the same time.
when right when download leaves then push on power and volume up you will boot into twrp then make sure you have put in micro sdcard and swipe to allow modifications and then reformat device.
I chose to reboot to recovery.
go to micro sdcard and do your install.
then reboot phone after check your phone root and you check everything turn of your phone.
put in SIM card and turn on phone.
the no SIM will work that is what I did.
------------------------------------------------------------------------------------------------
I have a problem to translate your message, if I understand I proceed like this:
I've Odin already installed and drivers...
I remove my sim card, and insert a Micro-SD card on my device,
1. I'll reformat my phone (return stock via settings).
2. i'll install TWRP recovery via Odin and i'll reboot directly to Recovery mode and swipe to allow
modifications and then reformat device.
3. I'll reboot in recovery mode and install "mesascustom kernel v1.zip" and "no verify no encrypt.ashy yx.zip"
from my SD-card.
4. Then i'll reboot phone after check your phone root and you check everything turn off your phone.
I'll put my SIM card and turn on phone.
The no SIM will work that is what I did.
What does mean the no SIM will work ? (no band active?) and Should i install "RMM-State_Bypass" too...? in step 3.
Thank you for correcting me if I made a mistake and it will be perfect...
Thank you in advance.
Gil
Click to expand...
Click to collapse
HELP. (SOLVED)
Hi Guys, yesterday I have tried to lock my bootloader again on android 9, after not successfully security patch update, after I lock my bootloader the phone has erased all system, , I have downloaded the factory image from google site but every stock image I flash I get stuck in the google white screen, I can’t update by sideloading, because when I lock the bootloader all system gone.. I CAN ACCESS THE FASTBOOT MODE AND RECOVERY MODE phone stuck on boot screen with google logo help….. I have tried many stock images but same problem with all versions..
Also get he messege "Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
PLS HELP..
zetareticuli said:
HELP.
Hi Guys, yesterday I have tried to lock my bootloader again on android 9, after not successfully security patch update, after I lock my bootloader the phone has erased all system, , I have downloaded the factory image from google site but every stock image I flash I get stuck in the google white screen, I can’t update by sideloading, because when I lock the bootloader all system gone.. I CAN ACCESS THE FASTBOOT MODE AND RECOVERY MODE phone stuck on boot screen with google logo help….. I have tried many stock images but same problem with all versions..
Also get he messege "Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
PLS HELP..
Click to expand...
Click to collapse
You probably should look into this.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
With a locked bootloader, you cannot flash system images. You need to be unlocked to do so.
But it seems that you did something wrong when re-locking the bootloader: It is normal that a factory reset is performed, but the OS should stay on the phone.
So I would first unlock the bootloader again - both fastboot flashing unlock and fastboot flashing unlock_critical, like described here: https://developers.google.com/android/images
Also note that you always need to update the Android SDK Platform-Tools, like descibed in the link. As always: Those who can read do have an advantage
Then you should be able to flash the latest factory image again and are ready to go.
Badger50 said:
You probably should look into this.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
I couldn't dig myself out of a soft brick the other day too. That saved me as well. Worked like a charm the first time.
zetareticuli said:
HELP.
Hi Guys, yesterday I have tried to lock my bootloader again on android 9, after not successfully security patch update, after I lock my bootloader the phone has erased all system, , I have downloaded the factory image from google site but every stock image I flash I get stuck in the google white screen, I can’t update by sideloading, because when I lock the bootloader all system gone.. I CAN ACCESS THE FASTBOOT MODE AND RECOVERY MODE phone stuck on boot screen with google logo help….. I have tried many stock images but same problem with all versions..
Also get he messege "Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
PLS HELP..
Click to expand...
Click to collapse
Sounds like you may have made some changes to your partitions, then locked the bootloader.
I would unlock the bootloader again, and reflash all the partitions to factory.
Then lock bootloader again.
exist2resist said:
Sounds like you may have made some changes to your partitions, then locked the bootloader.
I would unlock the bootloader again, and reflash all the partitions to factory.
Then lock bootloader again.
Click to expand...
Click to collapse
SOLVED WITH [TOOL] Deuces Bootloop-Recovery & Flashing Script v4.4/v4.5
Thanks alot guys
mikelikesbikes said:
I couldn't dig myself out of a soft brick the other day too. That saved me as well. Worked like a charm the first time.
Click to expand...
Click to collapse
Thanks my friend works like a charm..
exist2resist said:
Sounds like you may have made some changes to your partitions, then locked the bootloader.
I would unlock the bootloader again, and reflash all the partitions to factory.
Then lock bootloader again.
Click to expand...
Click to collapse
Solved with [TOOL] Deuces Bootloop-Recovery & Flashing Script v4.4/v4.5..
Hello
I was on an android 9.0 GSI image.
After disabling developer options in settings the device couldn't boot.
It was showing "custom firmware blocked by FRP lock" error.
I couldn't enter TWRP recovery as well. So I restored stock firmware through odin.
I tried to toggle on OEM unlock in settings with no result, after reboot it remains OEM and FRP locked. I also tried to OEM unlock through combination firmware but the toggle doesn't work.
Does anyone know if there is a solution to this problem ?
Thanks in advance,
NoirX said:
Hello
I was on an android 9.0 GSI image.
After disabling developer options in settings the device couldn't boot.
It was showing "custom firmware blocked by FRP lock" error.
I couldn't enter TWRP recovery as well. So I restored stock firmware through odin.
I tried to toggle on OEM unlock in settings with no result, after reboot it remains OEM and FRP locked. I also tried to OEM unlock through combination firmware but the toggle doesn't work.
Does anyone know if there is a solution to this problem ?
Thanks in advance,
Click to expand...
Click to collapse
Probably going to have to wait 7 days
*Detection* said:
Probably going to have to wait 7 days
Click to expand...
Click to collapse
I tried that too but i think the issue is a little bit more complicated. The toggle is there but it does nothing. On stock firmware it goes through a factory reset as expected but the device remains oem locked. On combination firmware the toggle is there too, but it won't switch on. Thank you.
I have a similar issue....
Waited a full week for the OEM Unlock.
Ticked it last night.
Rebooted to download mode > Flashed TWRP > Passed.
Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF
Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.
Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???
I used the Patched ODIN here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Combined with TWRP 3.2.3-0 recovery....
AMDPOWERFIST said:
I have a similar issue....
Waited a full week for the OEM Unlock.
Ticked it last night.
Rebooted to download mode > Flashed TWRP > Passed.
Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF
Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.
Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???
I used the Patched ODIN here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Combined with TWRP 3.2.3-0 recovery....
Click to expand...
Click to collapse
Why are you using a patched ODIN?
Uncheck "Auto Reboot" in ODIN settings, once TWRP has flashed disconnect USB then power off the phone and immediately boot into recovery, do not let it reboot first
*Detection* said:
Why are you using a patched ODIN?
Uncheck "Auto Reboot" in ODIN settings, once TWRP has flashed disconnect USB then power off the phone and immediately boot into recovery, do not let it reboot first
Click to expand...
Click to collapse
I'll try with normal Odin next time. I do suspect this might have been the issue.
AMDPOWERFIST said:
I have a similar issue....
Waited a full week for the OEM Unlock.
Ticked it last night.
Rebooted to download mode > Flashed TWRP > Passed.
Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF
Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.
Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???
I used the Patched ODIN here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Combined with TWRP 3.2.3-0 recovery....
Click to expand...
Click to collapse
@*Detection*, I had the exact same issue as yours tonight when I tried to install TWRP for the first time. Red code errors then an automatic restart and then default back to normal Recovery. As far as I know I used normal Odin and I followed installation instructions to the letter. So back to square one for me. I'll definitely have another crack in 7 days. Interested to know how you went with your second effort. If you had success please post what you did step by step.
And @AMDPOWERFIST, out of interest, how do you power the phone OFF from the Download screen? I know how to restart. Thanks.
bulky68 said:
@*Detection*, I had the exact same issue as yours tonight when I tried to install TWRP for the first time. Red code errors then an automatic restart and then default back to normal Recovery. As far as I know I used normal Odin and I followed installation instructions to the letter. So back to square one for me. I'll definitely have another crack in 7 days. Interested to know how you went with your second effort. If you had success please post what you did step by step.
And @AMDPOWERFIST, out of interest, how do you power the phone OFF from the Download screen? I know how to restart. Thanks.
Click to expand...
Click to collapse
Just realised that I got the 2 posters mixed up in my previous post. My apologies @*Detection* and @AMDPOWERFIST.