Develop Bugs

Softbrick'd. No idea what to do.

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

Oneplus 3 Bricked - Unbrick doesn't work...

Hello guys,
my Oneplus 3 is hard bricked, I tried the methods in the Mega Unbrick guide, my device already gets shown as Qualcomm 9008 ... in Device Manager, so I started the MSM DownloadTool and it flashed anything without errors. But when the phone reboots I get a black screen and the white led is on.
I can't even boot to stock recovery (Volume down + power doesn't work and rebooting to recovery through fastboot doesn't work, too....) my bootloader is locked and all attempts to unlock the bootloader are failing with the error "remote: oem unlock is not allowed"
So at the moment I'm stuck in fastboot and nothing else works -.-
Can someone please help me?
The unbrick tool has an old firmware, can I replace the files with files from a newer firmware?
Thanks!

Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.

Puddi_Puddin said:
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Click to expand...
Click to collapse
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.

min-dfreak said:
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
Click to expand...
Click to collapse
Ye thats the only thing you can currently do... May i ask what you have done how did it get bricked?

I just updated AICP ota and after flashing the update my phone didn't boot up. The screen went black immediately.
So I thought that it is maybe a Problem with the ROM and I tried to go back to stock.
Flashed the stock recovery and locked the bootloader, but I couldn't boot to the stock recovery.
There it started...

Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.

drmuruga said:
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
Click to expand...
Click to collapse
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.

min-dfreak said:
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
Click to expand...
Click to collapse
Never but never lock your bootloader...

If recovery, boot or system partition is modified. There's no harm in re locking otherwise..

Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off

Dsn Fouad said:
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Click to expand...
Click to collapse
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)

SivaMaxwell said:
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
Click to expand...
Click to collapse
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?

Dsn Fouad said:
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Click to expand...
Click to collapse
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload

SivaMaxwell said:
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
Click to expand...
Click to collapse
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?

Dsn Fouad said:
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Click to expand...
Click to collapse
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery

SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Thanks i will download and give it a try

SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working

Dsn Fouad said:
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Click to expand...
Click to collapse
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP

SivaMaxwell said:
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
Click to expand...
Click to collapse
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it

Dsn Fouad said:
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Click to expand...
Click to collapse
Even if the bootloader is locked, you can boot into the current rom and unlock simply by going to advanved options.
It is a very simple process.

[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018

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]

Well done corsi ?

Nice guide fam

Wow @partcyborg
Sent from my SM-G892A using Tapatalk @elliwigy @beaups

progro420 said:
Wow @partcyborg
Click to expand...
Click to collapse
?? this write up is for unlocked F variants.. not usa locked SD variants

elliwigy said:
?? this write up is for unlocked F variants.. not usa locked SD variants
Click to expand...
Click to collapse
It says any Samsung is why I asked, lol
Sent from my SM-G892A using Tapatalk

progro420 said:
It says any Samsung is why I asked, lol
Click to expand...
Click to collapse
i dont recall ever seeing vaultkeeper prop value on SD variants.. im on p2xl now and also dont see it so might be specific to exynos chipsets? only time will tell (pun intended)

progro420 said:
It says any Samsung is why I asked, lol
Sent from my SM-G892A using Tapatalk
Click to expand...
Click to collapse
My bad, edited the title.
elliwigy said:
i dont recall ever seeing vaultkeeper prop value on SD variants.. im on p2xl now and also dont see it so might be specific to exynos chipsets? only time will tell (pun intended)
Click to expand...
Click to collapse
Vaultkeeper prop is tied to vaultkeeper service, that indeed seems to be samsung exynos related service.
Anyway US Samsung variants are very well known for bootloader lock, so even if you had this, bootloader won't let you flash anything.
Regards.
Sent from my SM-A530F using Tapatalk

progro420 said:
Wow @partcyborg
Click to expand...
Click to collapse
elliwigy said:
?? this write up is for unlocked F variants.. not usa locked SD variants
Click to expand...
Click to collapse
Yea, this is the new thing that made everyone panic thinking oreo was blocking comsy flashing a bit ago (lol). Idk if usa sds have this on oreo or not as i havent looked.
Thanks OP for calling out non-us snapdragon in the subject, that will definitely lead to less misunderstanding and privmsgs to me ?️
PS
That last comment was not directed at you @progro420, it sounds like it was not clear at all at first the scope of this thing so im glad you brought it to my attention)

Hi my device is network sim locked. Does rooting also disables this lock?

ShiShTuBaBu said:
Hi my device is network sim locked. Does rooting also disables this lock?
Click to expand...
Click to collapse
Unfortunately no.
Sent from my SM-A520F using Tapatalk

corsicanu said:
Unfortunately no.
Sent from my SM-A520F using Tapatalk
Click to expand...
Click to collapse
How can i solve this problem? would you help me?

ShiShTuBaBu said:
How can i solve this problem? would you help me?
Click to expand...
Click to collapse
Most likely you need an unlock code from z3x box or something, afaik there's nothing you can do from your pc. Try to reach a GSM center, maybe they can help you.
Sent from my SM-A520F using Tapatalk

corsicanu said:
Most likely you need an unlock code from z3x box or something, afaik there's nothing you can do from your pc. Try to reach a GSM center, maybe they can help you.
Sent from my SM-A520F using Tapatalk
Click to expand...
Click to collapse
oh ok thanks!

Hello there, first time posting here. I'm facing issues with checking whether or not my device is locked, because none of the signs you've listed are telling me anything.
Here's what I did in order :
1. I first checked if the OEM unlock button was present - and it was, so I promptly enabled it.
2. I went into download mode and checked for the RMM state. This is the odd part : There is no RMM entry in the top left in download mode (See attached picture). As you can see by the Knox trip, the picture was taken after my original attempt, but the first time around the information was the exact same.
3 : Seeing no issues, I went ahead and flashed TWRP, which actually worked without any errors - Odin did display "PASS".
4. I rebooted into TWRP, flashed the RMM bypass, and rebooted to ROM.
At this point, my A8 refused to boot and was stuck in a bootloop, so I flashed back the original firmware and now it's working again, although without root or TWRP.
I still see no signs of any sort of lock on the device. If I wanted to flash TWRP again it would likely do so without any issues, but being afraid of just causing another bootloop, I'd rather report about this before trying anything else. Should I just try again?
RESOLVED : I fixed it by very carefully following the following post : https://forum.xda-developers.com/ga.../twrp-3-2-1-1-a8-sm-a530f-02-02-2018-t3744169
It appears some devices, like mine, do not have RMM protection at all. If this is the case for you and you're experiencing the same issues I'm facing, follow the guide above and make sure to do it all very neatly and carefully. Once done, your device will be wiped clean, but rooted.

You can charge the phone that is fine no reboots during the 168 hour that renable oem so can enable oem unlock.
I sharing what work for me you did put it in the right sim 1 right.
This what I did .
When I got phone I did not put sim card in until I had root and everything done.
1) in stall Odin.
2)flash twrp
3)unplug phone boot into twrp by holding power and volume up and down when download mode disappears hold power and volume up you will boot into twrp.
Swipe to allow modifications then swipe to reformat.
4)go to sdcard you put in and install mesas custom kernel v1.
5) install no verity no encrypt ashy.zip.
6) install supsu if you want root.
Know to explain the was accidentally not planned.
Follow this you get TWRP and root.
Sent from my SM-A730F using xda premium

corsicanu said:
....
How to unlock
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.
.....
Click to expand...
Click to collapse
Is this lock reset again if script is uninstalled and stock rom flashed again?
Is there any chance that on NON-USA devices like A8 2018 can be installed TWRP and be able to revert back to stock without losing warranty in case of Samsung assistance??
Thanks!
Sent from my SM-G950F using Tapatalk

What happens if you accidentally disconnected your phone from the network connection? Can you reconnect and wait for the remaining time or do you have to flash the stock firmware again and wait for another 7 full days? Thank you

mate se bricked. have dc phoenix and hcu client for 1 more day please help me

i sold this phone to a friend and they tried to return stock with out knowing how trwp works. i can get to fastboot mode where it says bootlooder is unlocked and frp is locked
erecovery doesnt work and twrp isnt installed anymore. some times i do see a func: 11 no recovery. i cant seem to get fix it no matter what. any help making this phone work will tip on paypal 20 buucks.

jerrah said:
i sold this phone to a friend and they tried to return stock with out knowing how trwp works. i can get to fastboot mode where it says bootlooder is unlocked and frp is locked
erecovery doesnt work and twrp isnt installed anymore. some times i do see a func: 11 no recovery. i cant seem to get fix it no matter what. any help making this phone work will tip on paypal 20 buucks.
Click to expand...
Click to collapse
is it still rooted?

well. as i posted that i unbricked my mate se but now my phone thinks its an honor 7x l21 anyway to get it back to bnd l34

Have you tried flashing a Compatible TWRP. Without TWRP you can't do anything. Maybe try dload method. Are you sure you had TWRP recovery installed before brick. If so then let your phone drain of battery then plug in USB. It should show a three options menu if bootloader is unlocked. Press Volume up to boot into recovery. It should be TWRP. If not then try factory reset.

I have it up and running. I used the hold 3 button and upgrade mode. Only thing was I have a mate se and the only files I could find were for an honor 7x lc21 files but I had a bnd l34. So I have a honor 7x software. I’m unlocked boot loader and rooted again. How can I make it back to it saying my phone is a mate se. when I go to about phone it shows up as a generic_a14

Pretty sure you need to flash correct firmware via Hurupdater. To do that first download the correct firmware files for your model via Firmware Finder. Next download Hurupdater and rename the three files as suggested in Hurupdater thread. Finally flash a Compatible TWRP and place all four files (Hurupdater and three Firmware after renaming) into the same folder on your SD card as you will lose all data in Internal. Boot device into TWRP.
Go to:
Wipe -> Format Data -> YES.
Now back twice and go to:
Advanced Wipe -> Mark Dalvik/Art Cache, Cache, Data, Internal and System and swipe to Wipe. Next navigate to folder with files in SD card and select only Hurupdater to flash. Once flash completes, wipe Cache and then reboot. When phone shows warning screen, press Volume Up to boot into stock recovery and Wipe Data/Factory Reset. After that format Cache and reboot. First boot can take up to 10 minutes. Luck.

Then I gotta reunlock and root? I have my unlock code

Hurupdater doesn't lock the Bootloader. At least never did for me. It's important to note that Download files from Firmware Finder only as others may lock Bootloader. You will only need to reflash TWRP normally. After that your device should work Normally

ok ill try.

still says generic_a15 and now the camera wont work. and the setting looks very odd

jerrah said:
still says generic_a15 and now the camera wont work. and the setting looks very odd
Click to expand...
Click to collapse
I have seen this failure to update the build number before, and after flashing the nougat roll-back it fixed it.
.
I suggest you try my hwota thread and first try your correct l34/firmware. And if that does not help. Use the rollback firmware.

link to the roll back ?

caues it has 5.1 on it before i did the fix and now it has oero

jerrah said:
caues it has 5.1 on it before i did the fix and now it has oero
Click to expand...
Click to collapse
There is a link to it from the guide I suggested you to search for.
here.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649

Samsung j610fn stuck in bootloop even after nand erase and pit flash, please help !

Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.

stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.

stefan1301 said:
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
Click to expand...
Click to collapse
Sounds to me like the hardware itself is bricked or damaged. If that is the case, the only option is to replace the motherboard.
Sent from my SM-S767VL using Tapatalk

Try to flash latest rom

Here is the solution
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done

alaanhaliko said:
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
Click to expand...
Click to collapse
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk

Droidriven said:
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.

alaanhaliko said:
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
Click to expand...
Click to collapse
No, I'm talking specifically of FRP lock.
The point you make about binaries has nothing to do with FRP. Binaries can be blocked on both FRP locked and FRP unlocked devices. The binaries only prevent flashing firmware with a lower binary than the current binary installed on the device. Binary version is related to RMM or KG state, not FRP. FRP is directly related to MDM and only "partially" related to the things you mention and only because there are other "tamper-proof" elements that "can" trigger FRP. Have you ever noticed that a device that does not have a Google account signed in does not encounter FRP issues when the device is factory reset, but if there is a Google account signed in the device, factory reset triggers FRP? If it were as you you seem to be suggesting, FRP would be triggered on devices that have no Google account associated to them when attempting to flash/modify the device, but this is not what happens.
OEM unlock really only applies to unlocking bootloader in order to flash unapproved software or make modifications to the system partition without being blocked.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk