Database Develop

Maybe hard bricked? Android won't start without PW after 3.1.3 update....never set pw

hello all....sooo..I have been attempting to bring my op3 to stock...so, I unrooted, applied the 3.1.3 update and UNCHECKED "OEM Unlocking" in dev options (i think that is where i screwed up) and went to the "all in one tool kit" and clicked on "lock bootloader"...it all went well, but when the phone rebooted, it is saying "To start android, enter password"..but I never even set a password..is there a default password or something I should be entering? also, I have tried to relock bootloader, format the phone..and obviously it is saying that "flashing not allowed" or "oem unlock is not allowed".......what in the world do I do to get this phone working again? Thanks a lot.
oh, also, I can't reboot back into TWRP, which seems obvious since the bootloader is now locked.
I can run fastboot commands of course, but nothing seems to stinking work here!
Device is not showing up when I run "adb devices"
I really appreciate any help! This is frustrating. I should have just kept the "oem unlocking" checked in dev options
update 1: hmm, well got an update....I just kept entering random passwords and it finally said "phone will be wiped after next failed attempt"..I was fine with that, so i typed something in...and the phone rebooted and it booted back up to a screen that says "decryption unsuccessful" the password you entered is correct, but unfortunatley your data is corrupt. To resume using your phone, you need to perform a factory reset...and it has a button at the bottom that says "reset"...so, i hit the "reset" button and the phone reboots and tried to go into recovery and the "one plus" boot logo flashes VERY quickly and then the phone just seems to shut down, screen goes black..I wait a bit and power the phone back on and it goes back to that same "decryption unsuccessful" screen...
I can NOT get into stock recovery (that was replaced with TWRP, anyway) or TWRP.....if i try to fastboot into recovery the phone will reboot and the "one plus logo" will flash very fast and then just go to a blank screen.....
update 2: I got adb to work...gonna play with that and see if I can do anything.
update 3: Here is a link to a video showing what I am talking about when I say the "oneplus logo" just flashes...
Video starts out with me just pushing the power button..then it looks like it is going to boot up..then hits that decryption unsuccessful screen..so, I tap reset, at this point, it will reboot and attempt to go into the recovery partition and wipe data...but, you can see that it just reboots and the one plus logo flashes, screen goes black and eventually the notification LED turns solid white.
so, next in the video..I power the device off and try to manually enter recovery mode (vol- + pwr) and same thing, oneplus logo flashes and blank screen. Anyway, here is the link to the video.
https://goo.gl/photos/EU2ZSkFw1JrdExeQ8
update 4: Level 2 OnePlus Support did NOT fix the issue. He didn't even give me a reason when I asked what the issue was, however, I did see that it failed out when he attempted to use the MSM tool. he escalated to the next level of support.

I wonder it it has the oneplus one bug to where if u relock ur bootloader u can't unlock it, also I don't think u need to relock if u r flash an OTA just unroot and refresh stock recovery (which no one has pulled yetyet, that has been tested), u may want to contact oneplus and see if they will give u that stock OS to fastboot files, also with the pw issues, all u had to do was boot into twrp and goto file manager and delete the pw key, it's somewhere in this forum that shows u how to do it, i think it's in one of the 3 trwp threads

cms062407 said:
hello all....sooo..I have been attempting to bring my op3 to stock...so, I unrooted, applied the 3.1.3 update and UNCHECKED "OEM Unlocking" in dev options (i think that is where i screwed up) and went to the "all in one tool kit" and clicked on "lock bootloader"...it all went well, but when the phone rebooted, it is saying "To start android, enter password"..but I never even set a password..is there a default password or something I should be entering? also, I have tried to relock bootloader, format the phone..and obviously it is saying that "flashing not allowed" or "oem unlock is not allowed".......what in the world do I do to get this phone working again? Thanks a lot.
oh, also, I can't reboot back into TWRP, which seems obvious since the bootloader is now locked.
I can run fastboot commands of course, but nothing seems to stinking work here!
Device is not showing up when I run "adb devices"
I really appreciate any help! This is frustrating. I should have just kept the "oem unlocking" checked in dev options
Click to expand...
Click to collapse
Can you try and install the file via normal, recovery?

Edu616 said:
Can you try and install the file via normal, recovery?
Click to expand...
Click to collapse
hmm, well got an update....I just kept entering random passwords and it finally said "phone will be wiped after next failed attempt"..I was fine with that, so i typed something in...and the phone rebooted and it booted back up to a screen that says "decryption unsuccessful" the password you entered is correct, but unfortunatley your data is corrupt. To resume using your phone, you need to perform a factory reset...and it has a button at the bottom that says "reset"...so, i hit the "reset" button and the phone reboots and tried to go into recovery and the "one plus" boot logo flashes VERY quickly and then the phone just seems to shut down, screen goes black..I wait a bit and power the phone back on and it goes back to that same "decryption unsuccessful" screen...
I can NOT get into stock recovery (that was replaced with TWRP, anyway) or TWRP.....if i try to fastboot into recovery the phone will reboot and the "one plus logo" will flash very fast and then just go to a blank screen.....

Bradl79 said:
I wonder it it has the oneplus one bug to where if u relock ur bootloader u can't unlock it, also I don't think u need to relock if u r flash an OTA just unroot and refresh stock recovery (which no one has pulled yetyet, that has been tested), u may want to contact oneplus and see if they will give u that stock OS to fastboot files, also with the pw issues, all u had to do was boot into twrp and goto file manager and delete the pw key, it's somewhere in this forum that shows u how to do it, i think it's in one of the 3 trwp threads
Click to expand...
Click to collapse
Unfortunately, I can not boot into TWRP to do anything
I am pretty sure the problem is it won't boot into TWRP because the bootloader is now locked, again and I do not have stock recovery of course, since I installed TWRP.
Is there no way that you know of to relock the bootloader without having to actually go into the dev options and select "OEM unlocking"? any sort of command I can run? I can't seem to find any
Thanks, sir.

cms062407 said:
Unfortunately, I can not boot into TWRP to do anything
I am pretty sure the problem is it won't boot into TWRP because the bootloader is now locked, again and I do not have stock recovery of course, since I installed TWRP.
Is there no way that you know of to relock the bootloader without having to actually go into the dev options and select "OEM unlocking"? any sort of command I can run? I can't seem to find any
Thanks, sir.
Click to expand...
Click to collapse
ok since ur recovery partition if f'd, u can be our guinea pig, download this "stock recovery" (download the recovery.emmc.win and rename to recovery.img and flash via fastboot (fastboot flash recovery recovery.img), this was the only stock recovery pulled via twrp, he did it as a twrp backup, can't do any more damage than u have now and let us know if it works so we can have a real stock recovery
if it does work and u get stock recovery u should be able to sideload the Oxygen OS 3.1.3 zip file and install and have a clean install, u may be able to unlockbootloader via dev options and fastboot
MAKE SURE U DOWNLOAD THE 1st FILE, NOT THE SECOND, ITS AN MD5 file and that wont work, the file should be about 64mb for the stock recovery

Bradl79 said:
ok since ur recovery partition if f'd, u can be our guinea pig, download this "stock recovery" (download the recovery.emmc.win and rename to recovery.img and flash via fastboot (fastboot flash recovery recovery.img), this was the only stock recovery pulled via twrp, he did it as a twrp backup, can't do any more damage than u have now and let us know if it works so we can have a real stock recovery
if it does work and u get stock recovery u should be able to sideload the Oxygen OS 3.1.3 zip file and install and have a clean install, u may be able to unlockbootloader via dev options and fastboot
MAKE SURE U DOWNLOAD THE 1st FILE, NOT THE SECOND, ITS AN MD5 file and that wont work, the file should be about 64mb for the stock recovery
Click to expand...
Click to collapse
going to try now! will update in a couple of minutes.

cms062407 said:
going to try now! will update in a couple of minutes.
Click to expand...
Click to collapse
best of luck, i hope it does work out for u

Bradl79 said:
ok since ur recovery partition if f'd, u can be our guinea pig, download this "stock recovery" (download the recovery.emmc.win and rename to recovery.img and flash via fastboot (fastboot flash recovery recovery.img), this was the only stock recovery pulled via twrp, he did it as a twrp backup, can't do any more damage than u have now and let us know if it works so we can have a real stock recovery
if it does work and u get stock recovery u should be able to sideload the Oxygen OS 3.1.3 zip file and install and have a clean install, u may be able to unlockbootloader via dev options and fastboot
MAKE SURE U DOWNLOAD THE 1st FILE, NOT THE SECOND, ITS AN MD5 file and that wont work, the file should be about 64mb for the stock recovery
Click to expand...
Click to collapse
well, didn't work...I feel as if something is up with the encryption of the phone here is a screenshot of what happens when I try to flash the recovery.img....it always says "partition flashing is not allowed" when i try to flash anything.
{
"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"
}

cms062407 said:
well, didn't work...I feel as if something is up with the encryption of the phone here is a screenshot of what happens when I try to flash the recovery.img....it always says "partition flashing is not allowed" when i try to flash anything.
Click to expand...
Click to collapse
what is the error u get when u try to unlock the bootloader via fastboot?

Bradl79 said:
what is the error u get when u try to unlock the bootloader via fastboot?
Click to expand...
Click to collapse
Here is the error...which, I think, is because I unchecked "OEM unlocking" in dev options..

cms062407 said:
Here is the error...which, I think, is because I unchecked "OEM unlocking" in dev options..
Click to expand...
Click to collapse
yeah i think u r right, so u have no recovery or no OS installed, correct, i wonder if someone who is smarter than me on here can show u how to flash OOS manually yet, i can try to pull the partitions and send them to u and see if u can flash via fastboot, it may take me a bit, but i will upload them and have u download 3.1.3 partitions, i don't think u can flash recovery with out BL unlocked but u may be able to other partitions.

Bradl79 said:
yeah i think u r right, so u have no recovery or no OS installed, correct, i wonder if someone who is smarter than me on here can show u how to flash OOS manually yet, i can try to pull the partitions and send them to u and see if u can flash via fastboot, it may take me a bit, but i will upload them and have u download 3.1.3 partitions, i don't think u can flash recovery with out BL unlocked but u may be able to other partitions.
Click to expand...
Click to collapse
sure, it wouldn't hurt to try to manually flash...but I bet we get the same error

cms062407 said:
Here is the error...which, I think, is because I unchecked "OEM unlocking" in dev options..
Click to expand...
Click to collapse
OEM unlock essentially opens up the system partitions to be writeable, so since your system is still locked, it makes sense that you can't flash anything. There are a number of OnePlus/Qualcomm unbricking tutorials that you can lookup, but you'll need the right files and I don't think anyone has made a full unbricking set of partitions with flash instructions for the OnePlus 3. I could be wrong though. I think there could be hope for your phone, just not quite right away.

thank u @tesherx that would make sense on why he can't, i'll still upload them anyway so if anyone needs them for whatever reason.

Bradl79 said:
thank u @tesherx that would make sense on why he can't, i'll still upload them anyway so if anyone needs them for whatever reason.
Click to expand...
Click to collapse
I think those partitions will be part of the final solution, but there has to be flash maps with them as well to correctly identify the sizes,locations, etc. Considering the OnePlus 3's level of developer support so far, I think a complete unbricking tutorial won't be far away.

@cms062407 - sorry that you're going through this, this is a little weird though, oneplus should have given priority to unlock bootloader even when the os doesnt work.. i mean what will people do if their phone soft bricks ? its a dead phone since you cant flash files, enter recovery or factory reset !! this is just stupid of oneplus.. but then again if this was the case anyone would steal a oneplus3 and use it as their own... damn this is messed up.

Thanks. But, there will be a fix, right?

Have you tried to just erase your userdata partition to remove encryption with the command
Code:
fastboot format userdata
Hope you'll get through.

cms062407 said:
Thanks. But, there will be a fix, right?
Click to expand...
Click to collapse
Even if bootloader is locked, there should be some recovery, OnePlus or twrp. Isn't it there?

Bootloader relock after Bootloader was unlocked? & Boot Warning Screen Removal?

Hi Guys,
So i rooted my S10 and got TWRP installed.
But for me it is still unclear, what to do about the first message, that appears when you restart your phone.
Here:
{
"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"
}
Any Way to remove that?
And also I hear from people they somehow relock their bootloader again.
Didn't understand this step for now or what the use of this was? Maybe someone explain please, so it is clear for everyone.
But when I try this > Start Phone in Recovery > Hold Volume Up to Device Lock Option > Lock the Bootloader & Factory Reset >
it just brings me here and after that it does nothing!
Here - see top left.
it says:
>
VBMETA: Error verifiing vbmeta Image: OK_NOT_SIGNED (3)
CUSTOM VBMETA
VBMETA: No sign Info
VBMETA ,
<
Question 1: Is there a Way to remove the Startscreen Warning?
Question 2: What is the use of relocking the bootloader and how is it properly possible?
Hope this Thread brings some clear view on this.

||||| said:
Hi Guys,
So i rooted my S10 and got TWRP installed.
But for me it is still unclear, what to do about the first message, that appears when you restart your phone.
Here:
Any Way to remove that?
And also I hear from people they somehow relock their bootloader again.
Didn't understand this step for now or what the use of this was? Maybe someone explain please, so it is clear for everyone.
But when I try this > Start Phone in Recovery > Hold Volume Up to Device Lock Option > Lock the Bootloader & Factory Reset >
it just brings me here and after that it does nothing!
Here - see top left.
it says:
>
VBMETA: Error verifiing vbmeta Image: OK_NOT_SIGNED (3)
CUSTOM VBMETA
VBMETA: No sign Info
VBMETA ,
<
Question 1: Is there a Way to remove the Startscreen Warning?
Question 2: What is the use of relocking the bootloader and how is it properly possible?
Hope this Thread brings some clear view on this.
Click to expand...
Click to collapse
This Download screen is waiting for you to connect to your computer and fire up Odin and flash stock firmware.
See my post here:
https://forum.xda-developers.com/ga...bootloader-t3927663/post79698366#post79698366

robbo1947 said:
This Download screen is waiting for you to connect to your computer and fire up Odin and flash stock firmware.
See my post here:
https://forum.xda-developers.com/ga...bootloader-t3927663/post79698366#post79698366
Click to expand...
Click to collapse
Thanks your post was very useful!
After I flashed stock firmware again - do I still have TWRP then?
Scenario 1. Your phone is rooted with Magisk.
Go into Developers options and check OEM options, the switch must be ON (to the right). If it isn't turn it ON.
Turn off your phone. Press and hold the Bixby and Volume-down button, then connect with USB to your computer. (The cable shouldn't be connected until after you press the buttons).
Within seconds of USB connection the Download screen will appear. You will see 3 optiions, choose and Long press volume up and hold button until you see the 2 options at bottom of screen. Choose and hold volume up until screen goes off. Then the S10 logo screen will briefly apppear, before it flicks back to the Download screen with the words 'VBMETA: Error verifying vbmeta image etc' at the top, as the image below.
This is all good so far. Leave the phone exactly as it is with this screen showing and make sure the phone is still connected to the computer.
On your computer, fire up Odin3_v3.13.1, you can leave the Reboot option in Odin ticked. Locate your firmware on your computer and put the 4 file parts (BL, AP. CP and CSC) into Odin.
Let Odin finish.
The phone will reboot ready for setup.
The Unlocked bootloader warning screen will be gone.
Click to expand...
Click to collapse
But why should we relock the bootloader in the first place?
Only so we don't have the bootscreen-warning anymore?
Or does it have some other purpose as well?
And I see what I was stuck at, I didn't flashed the stock firmware, but tried to flash the patched stock rom again.
Because the bootloader was locked, It stuck at the flashing process everytime. So thats basically why this thread was created to bring some clarity about this.

||||| said:
Thanks your post was very useful!
After I flashed stock firmware again - do I still have TWRP then?
But why should we relock the bootloader in the first place?
Only so we don't have the bootscreen-warning anymore?
Or does it have some other purpose as well?
And I see what I was stuck at, I didn't flashed the stock firmware, but tried to flash the patched stock rom again.
Because the bootloader was locked, It stuck at the flashing process everytime. So thats basically why this thread was created to bring some clarity about this.
Click to expand...
Click to collapse
To remove the warning screen and be rooted flash Soldier's Splash Screen Changer.

ExtremeGrief said:
To remove the warning screen and be rooted flash Soldier's Splash Screen Changer.
Click to expand...
Click to collapse
Great Tip! Thanks
Soldier's Splash Screen Changer

re-lock Samsung S20 OEM after flashing
For those who may still be interested in knowing the EASY way of doing this:
This is what i did for the S20 (snapdragon)
After flashing stock firmware, the bootloader (OEM) stays unlocked, meaning that things like GooglePay and some bank apps wont work. The way to fix this is by re-locking the oem after you have flashed your new stock rom. Here are the steps to do that (since it took me a while to figure out and there is hardly any info online) - bear in mind this works if you have NOT tripped Knox and its using a stock rom and do these steps at your own risk - always have a backup just in case:
How to re-lock bootloader (for S20):
1. Turn off your device.
2. Press Volume down + volume up and insert usb cable to your phone to start the download mode
3. Read the text below on the Download Mode screen
to block or unblock the Bootloader.
4.- Long press the vol (+) button to enter unlock mode.
LOCK BOOTLOADER SCREEN:
5. Read the 2 options available, one will say to lock the lock the bootloader, the other to lock. Press the relevant volume button (was down on mine) until the phone restarts (this will erase your data and restart automatically).
6. Go into developer mode and then uncheck the unlocked oem option, restart your phone.
That's it! Now you have a device with an OEM locked, so everything will work as expected, again, as long as its a stock rom and you have NOT tripped Knox by root etc.

Hello,
Can you tell me how did you escape the downloading window (after you tried to re-lock the bootloader). Mine seems to have stuck and I tried to long press Vol Down and Power button, but the phone reboots and comes to this screen again.
I also tried to flash a few rom, but everytime it was blocked by OEM lock. I am not sure what was the CSC of the phone (as I bought it from someone who is now not in my contact). Is there any way I can find the stock rom with limited information?
My phone is Samsung SM-G977B (5G). I just know that it is a european version.
Any ideas?

masrhad said:
Hello,
Can you tell me how did you escape the downloading window (after you tried to re-lock the bootloader). Mine seems to have stuck and I tried to long press Vol Down and Power button, but the phone reboots and comes to this screen again.
I also tried to flash a few rom, but everytime it was blocked by OEM lock. I am not sure what was the CSC of the phone (as I bought it from someone who is now not in my contact). Is there any way I can find the stock rom with limited information?
My phone is Samsung SM-G977B (5G). I just know that it is a european version.
Any ideas?
Click to expand...
Click to collapse
See my post here:
https://forum.xda-developers.com/ga...bootloader-t3927663/post79698366#post79698366

[GUIDE][SM-T510/T515]Unlock/TWRP/Odin HowTo/Root - Tab A 10.1 (2019)

The purpose of this thread is to have one post with links to all of the following guides:
Unlock Bootloader by @mingkee
TWRP Recovery by @Magendanz
Custom ROM Nexus Stock by @Magendanz - current release is SM-T510 only
Custom ROM LineageOS 16.0 by @Magendanz - SM-T510 only
All credit to @Magendanz and @mingkee for those.
Below are my own observations which supplement but do not replace the guides above. The original posts includes important information not quoted below. You need to read the relevant guides above (depending on what you want to do), and you may get some additional benefit from reading my thoughts below before following the guides above.
***​Contents​
Overview
Downloads
Buttons
Unlock Bootloader
Rooting
How to use Odin
***​Overview​To root your device you need to first install the TWRP recovery. @Magendanz includes TWRP in his ROMs, so you have two options, TWRP without custom ROM, or TWRP with custom ROM.
To be able to install a ROM or recovery you first need to unlock your bootloader.
WARNING - take note of the kernel version of the custom ROM or TWRP you intend to use, e.g. T510XXU2ASI4. Newer bootloader releases will sometimes prevent downgrading, so if you flash a firmware/ROM/TWRP with a later kernel version you may not be able to flash your desired custom ROM without problems, or flashing an older version than you are currently running may trigger anti-rollback mechanisms. Magendanz suggests matching the version exactly.
There are then two paths:
Original ROM:
Read the TWRP instructions
Download any zip you plan to flash (install) from TWRP (e.g. Multi-disable and Magisk) and save to your sdcard. Internal memory will be wiped (formatted) as a necessary step in installing TWRP (if you follow the instructions correctly). Note that the folder /sdcard is part of the devices internal memory, your actual sdcard data can be found in something like /storage/ABCD-1234 in Android, or external_sd in TWRP.
Unlock Bootloader - Click to see original post:
Disclaimer: your tablet warranty will void. Proceed with your own risk
Warning: your personal data, except on external SD card or USB drive, will be wiped during the process!
Prerequisite:
Host PC installed Samsung Smart Switch
USB C cable
Your tablet battery should be 70% or higher and you have done data backup
OEM Unlock enabled
1. About tablet
2. Software version
3. Hit Build Number few times
4. Enable USB Debugging
5. Allow your host computer
6. If you don't see OEM Unlocking, wait for 7 days or do the following trick
https://www.xda-developers.com/fix-m...galaxy-note-8/
Are you ready? Let's do it.
1. Turn your tablet off and disconnect USB cable
2. Press and hold both volume up and down buttons and connect to host computer
3. You should see factory reset screen, but this time you should see one more option. Press and hold volume up to unlock the bootloader.
4. If you see a warning screen on boot, the bootloader is unlocked.
Install TWRP recovery .tar.md5 file via Odin by following the TWRP instructions.
Click to see instructions from the TWRP OP -
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, select your update (.zip) file, and then swipe to install
Reboot to system
[Optional] Install Magisk to get root - see Rooting section below
Don't forget to install Multi-disabler before doing Format Data! (as described in the guide) - In TWRP tap Install then select the Multi-disabler zip file.
Custom ROM [Allow several hours for the custom ROM download]:
Read the custom ROM instructions: Nexus Stock / LineageOS 16.0
Download any zip you plan to flash (install) from TWRP (e.g. Magisk) and save to your sdcard. Internal memory will be wiped as a necessary step in installing TWRP (if you follow the instructions correctly). Note that the folder /sdcard is part of the devices internal memory, your actual sdcard data can be found in something like /storage/ABCD-1234 in Android, or external_sd in TWRP.
Unlock Bootloader - Click to see original post:
Disclaimer: your tablet warranty will void. Proceed with your own risk
Warning: your personal data, except on external SD card or USB drive, will be wiped during the process!
Prerequisite:
Host PC installed Samsung Smart Switch
USB C cable
Your tablet battery should be 70% or higher and you have done data backup
OEM Unlock enabled
1. About tablet
2. Software version
3. Hit Build Number few times
4. Enable USB Debugging
5. Allow your host computer
6. If you don't see OEM Unlocking, wait for 7 days or do the following trick
https://www.xda-developers.com/fix-m...galaxy-note-8/
Are you ready? Let's do it.
1. Turn your tablet off and disconnect USB cable
2. Press and hold both volume up and down buttons and connect to host computer
3. You should see factory reset screen, but this time you should see one more option. Press and hold volume up to unlock the bootloader.
4. If you see a warning screen on boot, the bootloader is unlocked.
Install custom ROM .tar.md5 file (which includes TWRP) via Odin, by following the custom ROM instructions.
Click for instructions from OP for Nexus Stock -
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
When TWRP launches, wipe data if installing for first time. (Not necessary for incremental upgrades.)
Reboot to system
Click for instructions from OP for LineageOS 16.0 -
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM to AP with Odin
When TWRP launches, wipe data if installing for first time. (Not necessary for incremental upgrades.)
Reboot to system
Note that "wipe data" means Wipe -> Format Data
[Optional] Install Magisk to get root - see Rooting section below
Dirty flash: If you had installed the custom ROM previously and are now updating to a newer version then all you need to do is use Odin to flash the latest tar.md5 file. It will enter TWRP after the flash, no need to Format Data, just reboot to system. Alternatively if the ROM developer provides a flashable zip, you can update with TWRP.
Some users have reported getting stuck on the boot animation after a dirty flash, I don't know if that still happens with the latest versions of @Magendanz's ROMs. If it does the solution is to boot into recovery and flash Multi-disabler.
For TWRP versions before v3.3.1-5 you MUST format the encrypted data partition after flashing TWRP or TWRP will hang on the splash screen. For later versions of TWRP you should format the encrypted data partition after flashing TWRP so that TWRP can access the data partition.
You can use TWRP to flash zip files, e.g. to install newer versions of TWRP itself, or custom ROM zips, as follows:
1. Download the zip file
2. Boot into Recovery
3. Install -> Select the TWRP zip file
4. Reboot to System
You *cannot* use TWRP to flash tar.md5 files, and you must use Odin at least once to get TWRP installed in the first place.
***​Downloads​You may not need ALL of these downloads, this is just a handy list of some of the downloads mentioned in the guides
Samsung Smart Switch (for USB drivers)
Magisk - Download Latest Stable zip file to flash in TWRP (see Rooting below) and Latest Magisk Manager to install as an app
Odin
Multi-disabler (required by TWRP only tar.md5)
Firmwares SM-T510 SM-T515 - allow several hours, at least, for the firmware downloads to complete
WARNING - take note of the kernel version of the custom ROM you intend to use, e.g. T510XXU2ASI4 and your current version (Settings | About tablet). Newer bootloader releases will sometimes prevent downgrading, so if you flash a firmware with a later kernel version you may not be able to flash your desired custom ROM without problems, or flashing an older version than you are currently running may trigger anti-rollback mechanisms. Magendanz suggests matching the version exactly.
***​Buttons​
Power On: Hold the Power button for 3 seconds
Boot to Recovery (Before unlocking bootloader) Power On and Press and hold Power and Volume Up until you see Recovery running.
Boot to Recovery (After unlocking bootloader) Power On and then press Power and Volume Up as soon as you see the unlocked bootloader warning. No need to hold.
Boot to Download: Press and hold Volume Up and Volume Down and connect to computer with USB cable.
***​Unlock Bootloader​Read the Unlock Bootloader Guide FIRST​Click to see Unlock Bootloader original post...
Disclaimer: your tablet warranty will void. Proceed with your own risk
Warning: your personal data, except on external SD card or USB drive, will be wiped during the process!
Prerequisite:
Host PC installed Samsung Smart Switch
USB C cable
Your tablet battery should be 70% or higher and you have done data backup
OEM Unlock enabled
1. About tablet
2. Software version
3. Hit Build Number few times
4. Enable USB Debugging
5. Allow your host computer
6. If you don't see OEM Unlocking, wait for 7 days or do the following trick
https://www.xda-developers.com/fix-m...galaxy-note-8/
Are you ready? Let's do it.
1. Turn your tablet off and disconnect USB cable
2. Press and hold both volume up and down buttons and connect to host computer
3. You should see factory reset screen, but this time you should see one more option. Press and hold volume up to unlock the bootloader.
4. If you see a warning screen on boot, the bootloader is unlocked.
After unlocking the bootloader every time you turn the device on a warning about the bootloader being unlocked will appear for ten seconds, unless you dismiss it by pressing the power button.
If you are holding the Power button and Volume Up to boot into recovery this warning screen will flash on and off briefly, at which point you can stop holding down the buttons. Recovery will start a few seconds later.
***​Rooting​Root can be achieved by flashing Magisk in TWRP (you also need to install the Magisk Manager app). From Magisk 19.3 onwards there is no longer a need to use Magisk Manager to patch a tar.md5 file or anything like that.
You can even install Magisk the first time TWRP runs after flashing one of @Magendanz's tar.md5 files in Odin.
To do so follow @Magendanz's guide up to the point where you have Factory Reset/Wiped Data in TWRP then:
1. Reboot to Recovery
2. Install -> Select the Magisk zip file
3. Reboot to System
4. Install Magisk Manager
Otherwise you can start by installing the Magisk Manager app at any time.
Note: You will need to re-install Magisk after a TWRP update.
***​How to use Odin​Odin is a Windows tool for firmware flashing on Samsung devices via USB. Odin can be used to flash firmware, kernels, recoveries or ROMs to your device.
* Firmware zip (or rar) files need to be extracted and then install via Odin. Flashable zip files (e.g. new versions of TWRP or custom ROMs) can only be flashed from TWRP, not Odin, though you need to flash a TWRP tar.md5 file using Odin in the first place *
Preparing the device
Charge the device to at least 80%.
Bootloader unlocked
In developer options, turn USB debugging on. Click on Build number in Settings several times until you see the toast notification "You are now a developer". Go to Developer Options and turn on the USB debugging option.
- In the stock ROM Build number can be found here: Settings | About Tablet | Software Information and the "Developer Options" menu item appears below About Tablet in the main Settings screen.
- The locations may be different in custom ROMs. In the Nexus based ROM the locations are Settings | About phone for Build number, and System | Advanced for Developer options
Turn off the phone, hold down the Volumn Up and Volume Down buttons and connect the device to the computer with a USB cable (preferably the cable that came with the device). A warning will appear saying "A custom OS can cause critical problems in phone and installed applications".
Press the Volume Up button briefly to continue.
The device is now in Download mode.
Install Odin version 3.13.3.
When you run it a dialog will pop up in English and Chinese. Click OK.
The Odin window looks like this:
{
"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"
}
Above ID:COM on the left is the progress bar, below ID:COM is the connection indicator which changes colour (and shows the COM id) when your device is connected in Download mode.
Below that is the "Log" tab which gives verbose output showing what's happening. Normally you will not need to go near the Option or Pit tabs.
There are four buttons in the middle of the screen corresponding to the types of file that you can flash: BL (boot loader), AP (Application Processor, PDA), CP (Core Processor, phone/modem), CSC (Consumer Software Customization)
Depending on what you are flashing you will need to load one or more files. To load each file type click on the corresponding button and select the file to be flashed.
Odin will show the following in the "Log" while the file is being processed:
Code:
<OSM> Enter CS for MD5
<OSM> Check MD5... Do not unplug the cable...
<OSM> Please wait...
For AP_ files this can take some time, during which the button will remain greyed out. When the file has loaded the "Log" will say:
Code:
<OSM> Checking MD5 finished Successfully...
<OSM> Leaving CS...
... the button will be enabled again, the text field beside the button will be filled with the fullpath of the selected file, and the checkbox next to the button ticked.
@Magendanz's TWRP and ROM files are both single files flashed to AP, so just click the AP button and the select the tar.md5 file.
If you are flashing firmware ( e.g. https://samfrew.com/model/SM-T510/ ) unzip the download into separate files and load each with the correspong button. The filenames begin with BL_..., AL_... etc so you'll know which is which.
There will be both a CSC_ and HOME_CSC_ file. You could flash HOME_CSC_ to keep your device's settings and data but normally you should use CSC_ for a clean install. If you have an SM-T515 then you'll have a CP_ file too, but if you have a SM-T510 then your firmware will not have a CP_ file because that's for the phone (SM-T510 is wifi only), so just leave CP alone, only load BL, AP and CSC.
Verify that your device is connected in download mode. The box below ID:COM should show the COM id of the connected device and there should be a line in the "log" saying something like <ID:0/008> Added!!
Click Start to flash the selected files. DO NOT UNPLUG THE CABLE UNTIL THE PROCESS IS COMPLETE. You can follow the progress in Odin and on the Download screen on your device. To flash a ROM or firmware will take several minutes.
If you are flashing one of @Magendanz's tar.md5 files then your device will reboot into TWRP once the install is complete. At that point continue following @Magendanz's guide.
Note: You will need to turn on USB debugging again after flashing firmware, or a clean install of a ROM, before you can use Odin to flash again. Also check that OEM unlock is still turned on.

Hi,
Please help, my tablet SM-T515 got stuck at: teamwin Recovery Project 3.3.1-1 ...blue with black/gray screen, at boot. I can't do anything, it keeps on looping to this screen. If I try to do a Power+VolumeDown it resets the tablet but I can't do anything else, nor entering in Download mode or shut it down. I have no idea how to fix it. Can anyone give me some hints, please ?! PS: I wanted to root it...I might have downloaded on the tablet with ODIN some weird TWRP (I didn't found this post before starting the process from some weird site ... ).
Please, help me,
D

@DdDnt The difficulty in rebooting into Download mode is timing. After triggering a reboot by holding Power+VolumeDown for 7 seconds you need to immediately switch to holding Vol Up + Vol Down then connect the cable.
Alternatively you can wait for the battery to run out, then you can press and hold volume buttons and connect. Should get you into Download mode.
The next steps are
Flash stock firmware via Odin
Reboot into system and turn on USB debugging again in Developer options, verify that OEM unlock is still set
Flash TWRP or Custom ROM via Odin

MossyTC said:
@DdDnt The difficulty in rebooting into Download mode is timing. After triggering a reboot by holding Power+VolumeDown for 7 seconds you need to immediately switch to holding Vol Up + Vol Down then connect the cable.
Alternatively you can wait for the battery to run out, then you can press and hold volume buttons and connect. Should get you into Download mode.
The next steps are
Flash stock firmware via Odin
Reboot into system and turn on USB debugging again in Developer options, verify that OEM unlock is still set
Flash TWRP or Custom ROM via Odin
Click to expand...
Click to collapse
Hey, first of all thanks for the nice guide. I followed it to flash Nexus ROM for my T515 but I messed up the tablet and ended up in the emergency recovery mode. No biggie though, I have flashed back to original stock ROM but I can't seem to find OEM unlock option now in my developer settings (the tablet is still unlocked though, I have to use my power key while turning on to skip the warning screen)
So basically, now I can't figure out why I can't flash the nexus rom but was able to flash official firmware and why I don't have OEM unlock option in my developer settings.
Also, I made a clean install of Windows 10, downloaded the good drivers and used my best type C cord and plugged it directly into the motherboard and not into the front I/O panel, and still no luck with the nexus ROM.
P.S. I'm tagging @Magendanz, just in case you find it interesting how odin refuses to flash your Nexus rom. If you want to, I could test the nexus rom on the latest T515 firmware, perhaps the fw refuses to go below the current version I'm on?
P.P.S : added Odin output
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1303)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3048 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> param.bin
<ID:0/003> product.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Download mode screen spits out Only official released binaries are allowed to be flashed so I guess it is a matter of bootloader unlocking after all?

[deleted]

@fpozar There are two problems that I know of that can cause a FAIL on the product.img line in Odin -
USB debugging not turned on
Incomplete boot loader unlock
Looks like option 2.
As Magendanz has said elsewhere -
Did you reboot with the USB cable inserted holding Vol Up & Vol Down to get the light blue Warning screen and then long press Vol Up to finish unlocking bootloader? A short press, rebooting to bootloader from stock recovery, or adb reboot bootloader in debugging mode won't cut it.
Click to expand...
Click to collapse
Update: More from Magendanz, on missing OEM unlock option:
This is what the VaultKeeper "feature" does. You've got to open Developer Options with internet connectivity for it not to automatically undo your efforts to unlock.
Click to expand...
Click to collapse
So connect to wifi before doing the Developer options thing, then try the bootloader thing.

MossyTC said:
@fpozar There are two problems that I know of that can cause a FAIL on the product.img line in Odin -
USB debugging not turned on
Incomplete boot loader unlock
Looks like option 2.
As Magendanz has said elsewhere -
Update: More from Magendanz, on missing OEM unlock option:
So connect to wifi before doing the Developer options thing, then try the bootloader thing.
Click to expand...
Click to collapse
Yes, I have done the light blue screen long press step.
Now I've held vol buttons while starting the tablet and chose the short click step (the long click step only leads me to locking bootloader again) and entered a bit different looking download mode (the same one you get by using recovery to enter bootloader, but with a bit more colorful text on the sides), but to no avail, the flashing didn't go through and only lead me to emergency recovery. And again, flashing stock worked.
Secondly, OEM trick worked for me, it appeared when I connected to my home network and made it that oem unlock was greyed out and said "oem unlocked".
Tommorrow I'll try to lock the bootloader and unlock it again. It's really weird though because the blue screen part was done correctly it seems (because long pressing leads me to locking).
Bootloader screenshot when entered by volume + and - combination

I'm a bit confused on what I've been doing wrong and where to proceed from here. These are the steps I've done on my most recent try:
1) Downloaded:
- Samsung Smart Switch
- TWRP 3.3.1.5 .tar.md5
- Magisk (Latest Magisk Manager)
- Odin
- Firmware T510 (XAR-T510XXU1ASEF-20190605151710.zip)
- Multi-disabler
2) Followed Unlock Bootloader from mingkee
3) Installed TWRP recovery via Odin
4) Rebooted back into stock ROM
5) Installed Magisk.apk
6) Using Magisk Manager > Selected AP_T510XXU1ASEF_CL15874928_QB23938566_REV02_user_low_ship_meta_OS9.tar.md5
7) That gave me magisk_patched.tar which I moved over to my desktop
8) Boot back into download mode
9) Flash the magisk_patched under AP, TWRP under BL, and HOME_CSC under CSC
10) Then Odin said it failed
Honestly I was pretty confused by the steps going from guide to guide so I'm not sure where I went wrong.
Also I'm not sure where I'm suppose to be flashing multi-disabler. The guide just said don't forget to install it but I'm not sure at which step I should be installing it via TWRP.
Any help would be appreciated.
Edit:
I tried again going with just steps from [GUIDE]Comprehensive T510 root guide.
I unlocked bootloader > patched the AP file I downloaded > Tried flashing the AP file only using Odin and it gave me an error:
"Only official released binaries are allowed to be flashed"

@Orite I'm sorry that I haven't been clearer, but I did say to read the relevant guides and read my thoughts below.
In the OP I said
Root can be achieved by flashing Magisk in TWRP (you also need to install the Magisk Manager app). There is no longer a need to use Magisk Manager to patch a tar.md5 file or anything like that.
Click to expand...
Click to collapse
Full details in the Rooting section in the OP.
You should have been following the TWRP Recovery guide for installing TWRP which clearly states at what point to install Multi-disabler.
If you can boot into TWRP you can flash the Multi-disabler zip file. Tap Install then select the zip file. That should fix the problem of not being able to flash via Odin, though you don't need Odin to install Magisk.

Update : So today I've reunlocked bootloader again and still got stuck at product.img step. Again, this is all on fresh windows and Odin works on original firmware.
This time, the error message displayed on my tablet is :
SYSTEM REV. CHECK FAIL. DEVICE:2 BINARY:1 (PRODUCT)
I can only assume this is some anti rollback feature similar to what happens on LG devices when you try to flash software older than what you're currently at.
I guess now we wait for dev's confirmation and if anyone else has something smart to say please feel free to join the discussion. I would try and download older official firmware and try to flash nexus while on something older, but my network connection is kinda unstable and it takes hours to download without a paid account.
Just to avoid questions, my method of unlocking followed exactly the link in the OP and method of flashing was following the mini guide on Nexus rom's OP.
EDIT : For all the T515 users, it seems odin isn't allowed (by some security features) to downgrade bootloader, and since Nexus ROM is based on May update for T515, anyone on updates newer than May can't flash the ROM. I found the answer on Galaxy s9 forums so that might be untrue for our device, but I didn't see many of us T515 users talking about custom roms so that might be it, and the error code makes sense.
Thanks again @MossyTC for trying to help

@fpozar
Magendanz doesn't explicitly say so in his OPs, but in some of his posts he does suggest matching the kernel versions.
magendanz said:
Well, TWRP is going to use a custom kernel based on the latest kernel source release, which as of yesterday is T510XXU2ASI4. The custom recovery uses this, but it will also substitute a new boot partition with the custom kernel so that Knox boot security features are disabled and you can still boot to system. I'd think the goal would be to match them as closely as possible. That said, often newer bootloader releases will prevent downgrading, so it's not entirely without risk to use the newest release. The safest bet is to always match the version exactly.
Click to expand...
Click to collapse
Anyway it looks like you're stuck with stock until there's a newer t515 custom ROM.

Thank you. I was finally able to figure it out with your response.

Hi, I have seem to messed up my process somehow, this tutorial seems kind of out of place.
When i try moving the multidisabler to my phone, it looks like all my folders and files are encrypted inside twrp and from the mounted drive on my pc.
I tried installing multidisabler using an OTG which worked on twrps side, i then rebooted and launched into OEM. after restarting from OEM android, i now receive a message when trying to do anything involving turning on my tablet "Only Official Release Binary Aloud" I cant do anything with it now. It just Shows that msg and the samsung logo, and then goes away, never booting, never entering recovery.
I tried to google this and it came up with something about knox, which i know nothing about. I really hope i didn't just brick my device.

Does unlocking Bootloader on the T510 change Widevine from L1 to L3? This is my only hestitation to bootloader unlock and root

trashbag1 said:
this tutorial seems kind of out of place.
Click to expand...
Click to collapse
This isn't really a tutorial, more like additional information to help you follow the guides linked in the OP.
When i try moving the multidisabler to my phone, it looks like all my folders and files are encrypted inside twrp and from the mounted drive on my pc.
Click to expand...
Click to collapse
You're internal data is encrypted by default by Android, but the version of TWRP we're using can't handle encryption. We get around that by disabling encryption by wiping the data partition as one of the first things we do when TWRP starts up, as per the instructions in Magendanz's threads. Ideally you should have the Multi-disabler zip on your sdcard before flashing TWRP. I have amended the instructions above to suggest as much.
I tried installing multidisabler using an OTG which worked on twrps side, i then rebooted and launched into OEM. after restarting from OEM android, i now receive a message when trying to do anything involving turning on my tablet "Only Official Release Binary Aloud" I cant do anything with it now. It just Shows that msg and the samsung logo, and then goes away, never booting, never entering recovery.
I tried to google this and it came up with something about knox, which i know nothing about. I really hope i didn't just brick my device.
Click to expand...
Click to collapse
Is your device an SM-T515? You may be having the same problem as @fpozar.
Can you get into Download mode again?

tomdot said:
Does unlocking Bootloader on the T510 change Widevine from L1 to L3? This is my only hestitation to bootloader unlock and root
Click to expand...
Click to collapse
I don't know what will affect Widevine.
I think the bootloader can be relocked, but I can't check right now.

The bootloader *can* be locked, I know as I've done it yesterday. In fact, it can be relocked and renlocked as many times as you want. To lock it follow the guide to unlocking but when you enter the light blue menu, holding vol up will lead you to locking and reseting your tab

another guide? lol pretty soon will b only guide threads in here lol

fpozar said:
The bootloader *can* be locked, I know as I've done it yesterday. In fact, it can be relocked and renlocked as many times as you want. To lock it follow the guide to unlocking but when you enter the light blue menu, holding vol up will lead you to locking and reseting your tab
Click to expand...
Click to collapse
"And resetting". That's the problem. You can't relock without resetting and having to start over from scratch.

elliwigy said:
another guide? lol pretty soon will b only guide threads in here lol
Click to expand...
Click to collapse
Yeah, well there are about twelve Galaxy Series A models and the geniuses at xda put them all in one bucket, so lots of Guides in the Guides, News & Discussion section, lots of ROMs in ROMs, Kernels & Recoveries, etc.

Mi A2 - Failed to boot - after system update

Hello everyone, yesterday morning, Sunday 12/15/19, the system message "restart the device to make the system update effective".
So I do as I have always been.
The phone, an Mi A2, goes into bootloop and then a white screen appears on a black background with the title:
"<!> Failed to boot"
"Press the Volume keys to select then the Power button to continue.
RETRY
POWER OFF "
Choosing "RETRY" verifies bootloop 3 or 4 times and then the recovery mode screen appears which says:
"Can't Load Android system. Your data may be corrupted. You should get the message you need to perform at factory data reset and erase all user data stored on this device."
It gives me the choice between:
-Try again
-Factory data reset
Choosing "Try again" returns the same routine as when "RETRY" is selected In the previous black background screen, bootloop and then the black background white screen described at the beginning.
I MUST ACCESS AND SAVE THE VERY IMPORTANT CONTENT. :crying:
I have all the photos and videos of my newborn daughter. I usually backup but this inconvenience suddenly caught me.
I surfed and I saw that many people found this problem after an update .. but I never found any solutions. I called the Xiaomi center in Novara indicated by the site but they told me that they only serve as a collection center to send to the assistance in the company Xiaomi, saying that the assistance resets the phone to restore its functioning and does not save the data. I tried to start the fastboot, the device is recognized by the PC and shows the locked bootloader. The program MiFlash asks me to start to install a set of drivers and then immediately generate an unhandled exception and crash.
Attached the images.
Can you help me? I do not know what to do..
{
"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"
}

You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".

Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.

Aerobatic said:
Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.
Click to expand...
Click to collapse
Thank you, can you explain me better what I should try to do?

HTCDevil said:
You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".
Click to expand...
Click to collapse
Is there any guide to do that?

pedrix82 said:
Is there any guide to do that?
Click to expand...
Click to collapse
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.

pedrix82 said:
Thank you, can you explain me better what I should try to do?
Click to expand...
Click to collapse
First you can try to search this forum and read dozens of discussions of the same issue. Meanwhile you can plug in power adapter and reboot several times with pauses, probably sometimes switching to stock recovery and to fastboot mode, and then leave phone powered for a night.

HTCDevil said:
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.
Click to expand...
Click to collapse
Thanks....I will try, I don't remember if I enabled the usb debugging mode, for sure I saw with fastboot that I have the bootloader Locked.

nothing to do...i tried ADB mode, but it is not enabled, only fastboot mode where i can do nothing because the bootloader is locked.
I also tried to install the Xiaomi tool, but it doesnt recognize the device.
i dont know what to do....

Did you try the factory data reset?

1N4148 said:
Did you try the factory data reset?
Click to expand...
Click to collapse
Hello...ehm...not, the aim is to recover all the data, photos and documents that are stored inside...

Same thing happened to me. You should manually switch the active partition in fastboot.

Zedsdeadbaby said:
Same thing happened to me. You should manually switch the active partition in fastboot.
Click to expand...
Click to collapse
Hi, I already tried to do what you suggest, but it is not possible with the bootloader Locked.
Anyway, can you tell me what I have to do to change the active partition? Maybe I don't do it as I should....

@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.

Aerobatic said:
@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.
Click to expand...
Click to collapse
Thanks,
It's really long time that I'm rebooting the mobile since it happened...
But cyclically and alternate I got the two image attached to the main post....

try a "fastboot continue" in adb

hello everyone, update.
unfortunately I was unable to recover anything and proceeded with the factory reset.
The phone has reset and everything is working.
So I thought to try to do a file recovery as you do for deleted files.
for the various recovery applications I need to root the device.
For this phone should be really simple but I'm still stuck in.
I followed one guide, then another, and then another .... all with the same procedures.
the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone.
but from this recovery, even if I install Magisk, with a successful results from the recovery, I do not root the device. I verified root with Magisk manager and rootchecker.
Help.... thanks

pedrix82 said:
... So I thought to try to do a file recovery as you do for deleted files.
Click to expand...
Click to collapse
I do no believe you'll be able to undelete files after factory reset.
pedrix82 said:
... for the various recovery applications I need to root the device. ... I followed one guide, then another, and then another .... all with the same procedures.
Click to expand...
Click to collapse
This guide works for everybody, except that
(1) there is obsolete "fastboot oem unlock" command stated which should better be changed to "fastboot flashing unlock", and
(2) guide does not mention that each unlock step is to be approved on phone, and
(3) guide skips step of patching stock boot.img in phone with MagiskManager, - while exactly this step creates archived copy of stock boot image in /data root, thus allowing to restore images (actually restoring stock boot image) before downloading next OTA, and
(4) only 1st variant - that is booting into patched boot image and then making "Direct Install" is safe - it allows to check that patched boot image is suitable for ROM.
pedrix82 said:
...the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone....
Click to expand...
Click to collapse
IMHO that just means that you did not do your homework (I mean you have not read guides and discussions and Google info with links I provided) well enough to understand that with A/B slots partitions structure there is no separate /recovery partition in phone (instead, recovery is embedded into /boot image), and thus we cannot just "flash TWRP" into MiA2.
Instead, TWRP can only be embedded into boot image (patching previously flashed suitable boot image), which is made by installing TWRP.zip in temporarily booted TWRP.img. Thus, if you want to have both root and permanent TWRP (I still do not see why anybody needs permanent TWRP with rooted stock), first get root with patched boot image, and then install TWRP patching this Magisk-patched boot image once more.
And I do think that "TWRP 4pda edition" is working better than so called "official TWRP".

Found the solution,
First u need to get to the recovery menu by pressing vol up + power, tap it multiple times after retry boot...you have to be quick...and eventually will get to the android robot pic with "no command"....keep pressing till you get to the full recovery menu. (this might take multiple tries)
Then go to update using adb. (you need all the files for adb, usb drivers, latest mi a2 update zip, you can find tutorials in youtube/google )
after updating it should boot up fine with all data intact.
If latest update versions dont boot, try repeating will older version.
Make sure you backup everthing afterwards! and enable oem unlocking &usb debugging for potential future issues.
Hope this helps!

Installing twrp on Sprint v40 flashed to us pie

Recently downgraded from Verizon 10.0 to us pie in order to root / install custom ROM. I've followed all guides and Its not going good. To start, I've successfully unlocked my bootloader after 2 failed attempts. However, when I try to enter fastboot after installing my default abl_a/b, it just boots normally. To get back into fastboot, I have to load the v35 image first . Even after getting into fastboot, I am still unable to flash twrp. The flash says completed and the phone turns on but boots normally.
Does anyone have a solution for this ? Is this blocked and is there any bypass ?

kris597 said:
Recently downgraded from Verizon 10.0 to us pie in order to root / install custom ROM. I've followed all guides and Its not going good. To start, I've successfully unlocked my bootloader after 2 failed attempts. However, when I try to enter fastboot after installing my default abl_a/b, it just boots normally. To get back into fastboot, I have to load the v35 image first . Even after getting into fastboot, I am still unable to flash twrp. The flash says completed and the phone turns on but boots normally.
Does anyone have a solution for this ? Is this blocked and is there any bypass ?
Click to expand...
Click to collapse
First, the phone doesn't have fastboot, normally. So, after you flash the normal (stock) abl back, you should not be able to get to fastboot, so that's expected.
Second, getting twrp on the device has changed, you don't 'boot it', you need your boot partition with twrp 'injected' into it already (that's the easiest way). Which version of US Open Pie do u have? Can't seem to find a boot partition of it with twrp injected, but that's what u need.
Also, do u know what your current slot is? If u flash something to the other slot, it won't change anything. Use 'fastboot getvar all' and at the bottom of the output it will tell you what current slot is.
cheers

I tried injecting twrp directly into both my boot partitions and it just bootloops. I am also currently on active slot a . Prior to this, I was attempting to flash twrp using Verizon 10.0. However, after following countless guides, I was unsuccessful and tried to do it on this current version
{
"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"
}

kris597 said:
I tried injecting twrp directly into both my boot partitions and it just bootloops. I am also currently on active slot a . Prior to this, I was attempting to flash twrp using Verizon 10.0. However, after following countless guides, I was unsuccessful and tried to do it on this current version View attachment 5453895
Click to expand...
Click to collapse
So, from your previous post this is us Open 20a correct? Even though it says UA, it's actually QA right?
Also, how did u 'try injecting directly to your boot partition'? Did u use twrp? How did u do that?
Remember, once u have twrp in the boot partition, you should be going directly to twrp, not boot the system. Format data, reboot recovery, flash magisk and dm-verity, then boot system (not before).
Have you tried posting in the guide u followed? Usually you'll find answers there most often.
cheers

AsItLies said:
So, from your previous post this is us Open 20a correct? Even though it says UA, it's actually QA right?
Also, how did u 'try injecting directly to your boot partition'? Did u use twrp? How did u do that?
Remember, once u have twrp in the boot partition, you should be going directly to twrp, not boot the system. Format data, reboot recovery, flash magisk and dm-verity, then boot system (not before).
Have you tried posting in the guide u followed? Usually you'll find answers there most often.
cheers
Click to expand...
Click to collapse
I loaded judypn twrp image into boot a/b using qfill. It just boot loops. I have posted in the guide. Unfortunately no luck

kris597 said:
I loaded judypn twrp image into boot a/b using qfill. It just boot loops. I have posted in the guide. Unfortunately no luck
Click to expand...
Click to collapse
That's not the way it works, it's supposed to be 'injected' by twrp itself, in the advanced options of twrp, there's a selection called 'inject twrp', and you give it the name of the twrp image (on the sd card) and it then injects that image into the current boot loader of the device (the actual 64 meg image on the hard drive boot partition of the device).
Post in this thread your current boot image, and the twrp image. If your device is crossflashed by lgup, then both a and b boot images are the same. If your device is booting a carrier image, be sure to pull the boot image from the current boot slot (as boot a and boot b will be different).
I'll inject the twrp image into it for you. Then u use qfil and flash it, boot directly to recovery (now twrp) from qfil (use key combo), and follow what I mentioned in prev post.

AsItLies said:
That's not the way it works, it's supposed to be 'injected' by twrp itself, in the advanced options of twrp, there's a selection called 'inject twrp', and you give it the name of the twrp image (on the sd card) and it then injects that image into the current boot loader of the device (the actual 64 meg image on the hard drive boot partition of the device).
Post in this thread your current boot image, and the twrp image. If your device is crossflashed by lgup, then both a and b boot images are the same. If your device is booting a carrier image, be sure to pull the boot image from the current boot slot (as boot a and boot b will be different).
I'll inject the twrp image into it for you. Then u use qfil and flash it, boot directly to recovery (now twrp) from qfil (use key combo), and follow what I mentioned in prev post.
Click to expand...
Click to collapse
These are all the files i found / used. My device no longer has a carrier image as i crossflashed to global pie.
Im still a little confused. In all the guides i've followed, they've either used fastboot to booth twrp image and then install twrp after or load the twrp image straight into boot a/b.

kris597 said:
These are all the files i found / used. My device no longer has a carrier image as i crossflashed to global pie.
Im still a little confused. In all the guides i've followed, they've either used fastboot to booth twrp image and then install twrp after or load the twrp image straight into boot a/b.
Click to expand...
Click to collapse
I spoke too soon, my current device is LG G8, it has twrp, but unfortunately adb shell doesn't work on this twrp version. So I can't do this anymore.
I would suggest, in the guide you mention, I saw your last post but didn't know how to respond because you didn't say what command u used that resulted in:
downloading 'boot.img'... OKAY [ 2.124s]
booting... FAILED (remote: Failed to load/authenticate boot image: Load Error)
The version of twrp you have won't boot. twrp has to be 'injected' into the boot image, so you'll then have a boot image and twrp (recovery) will be in it.
Post again in that guide, so others can learn from it. But put in the exact command you were using to try to get to twrp, that would help a lot so others know what yer doing.
cheers

I should add, yes, this is confusing, sorry.
the guide you want to follow to get twrp is this one.
The reason(s) yer having trouble booting that version of twrp I believe it's because of 1) the engineering abl is Oreo, it won't boot anything that isn't Oreo based. 2) to be able to boot that version of twrp, follow the guide above and 'nuke laf' (back it up first, in case you need download mode - lgup, again).
so, as mentioned in the guide, in the 'nuke laf' section, you now get to fastboot by using the keys you'd normally use to get to lgup, but now u get a 'watered down' version of fastboot.
Pretty sure u can then use that version of fastboot to boot your version of twrp and then follow the directions in the guide to 'inject' it into ramdisk (the boot partition).
cheers

kris597 said:
These are all the files i found / used. My device no longer has a carrier image as i crossflashed to global pie.
Im still a little confused. In all the guides i've followed, they've either used fastboot to booth twrp image and then install twrp after or load the twrp image straight into boot a/b.
Click to expand...
Click to collapse
Managed to get a version of twrp that does what's needed, installed. The attached is your boot partition with twrp injected. Both a and b images were the same so it will work for both slots.
Flash it with qfil, then use key combo to go directly to recovery. Once in twrp, format data, reboot recovery, flash magisk (if wanted) and dm-verity-force... and you should be all set.
cheers

My phone is now unresponsize and stuck on a black screen. Was i supposed to boot a and b ?
I am unable to enter edl, download mode or any mode. It is completely unresponsize. Is it hard bricked ?
Edit: I was able to enter edl mode and restore my original boot partitions, however, im still stuck on a black screen and can only enter edl
AsItLies said:
Managed to get a version of twrp that does what's needed, installed. The attached is your boot partition with twrp injected. Both a and b images were the same so it will work for both slots.
Flash it with qfil, then use key combo to go directly to recovery. Once in twrp, format data, reboot recovery, flash magisk (if wanted) and dm-verity-force... and you should be all set.
cheers
Click to expand...
Click to collapse

kris597 said:
My phone is now unresponsize and stuck on a black screen. Was i supposed to boot a and b ?
I am unable to enter edl, download mode or any mode. It is completely unresponsize. Is it hard bricked ?
Edit: I was able to enter edl mode and restore my original boot partitions, however, im still stuck on a black screen and can only enter edl
Click to expand...
Click to collapse
wow what in the world did u do? You really need to say specifically the steps you did to get where u are now, I mean, telling me the results and saying 'what do I do' is assuming I expected this to happen?
this is totally unexpected. What, exactly, did u do?

AsItLies said:
wow what in the world did u do? You really need to say specifically the steps you did to get where u are now, I mean, telling me the results and saying 'what do I do' is assuming I expected this to happen?
this is totally unexpected. What, exactly, did u do?
Click to expand...
Click to collapse
I followed the steps correctly i believe. I have experience with rooting and flashing in the past but its entirely different with LG.
The steps i followed:
I entered EDL MODE, i flashed the boot_a_twrp to both my a & B slots and it was successful. After this, i tried to enter recovery mode and was left with a black screen, no vibration, screen or any form of life. Tried booting may times, holding down power + volume down for 4+ minutes but still no hope. I was then able to get back into edl where i flashed my original images back . Unfortunately, it is still not working. Sucks that i will have to buy a new phone now. I guess this is where i stop messing with my phone lol .

kris597 said:
I followed the steps correctly i believe. I have experience with rooting and flashing in the past but its entirely different with LG.
The steps i followed:
I entered EDL MODE, i flashed the boot_a_twrp to both my a & B slots and it was successful. After this, i tried to enter recovery mode and was left with a black screen, no vibration, screen or any form of life. Tried booting may times, holding down power + volume down for 4+ minutes but still no hope. I was then able to get back into edl where i flashed my original images back . Unfortunately, it is still not working. Sucks that i will have to buy a new phone now. I guess this is where i stop messing with my phone lol .
Click to expand...
Click to collapse
Wow, sorry to hear that. From what you're saying it sounds as though you did the right steps. To clarify, to exit edl mode is hold vol minus and power buttons until u hear the windows chime meaning 'disconnect' (usually only about 5 to 10 secs).
It is certain that newer phones are much more complicated, with dual slots and the challenge they present, and it's even worse with LG as they don't allow bl unlock and don't have fastboot, so getting those adds to the complexity.
You say you flashed the image to boot a and b, did u get a message about 'data overflow' by chance? (If so, that would explain the situation, but not how it happened). If an image was flashed to an incorrect partition (not that hard to make that mistake in qfil), and someone 'okays' the 'data overflow' message, it will **overwrite** nearby partition(s), resulting in a brick.
Assuming something like the above happened, there's an option, unfortunately it's a bit complicated also.

AsItLies said:
Wow, sorry to hear that. From what you're saying it sounds as though you did the right steps. To clarify, to exit edl mode is hold vol minus and power buttons until u hear the windows chime meaning 'disconnect' (usually only about 5 to 10 secs).
It is certain that newer phones are much more complicated, with dual slots and the challenge they present, and it's even worse with LG as they don't allow bl unlock and don't have fastboot, so getting those adds to the complexity.
You say you flashed the image to boot a and b, did u get a message about 'data overflow' by chance? (If so, that would explain the situation, but not how it happened). If an image was flashed to an incorrect partition (not that hard to make that mistake in qfil), and someone 'okays' the 'data overflow' message, it will **overwrite** nearby partition(s), resulting in a brick.
Assuming something like the above happened, there's an option, unfortunately it's a bit complicated also.
Click to expand...
Click to collapse
I believe i got a message similar to that
Edit: Cant be bothered to try any new methods. Will get a refurbished lg v60 from amazon. Had the v40 for 2 years. Its time to upgrade
cheers and thankyou for your help