Database Develop

[Q] From TWRP back to stock Recovery & locked Bootloader, keeping root & Custom ROM?

[Q] From TWRP back to stock Recovery & locked Bootloader, keeping root & Custom ROM?
Hey everyone,
around new years eve I found out that the Android Device Manger's remote wipe is not secure enough for my needs, as it doesn't wipe the data (pictures, app data etc.) on the virtual "sdcard" of the HTC One's storage. So a potential thief could easily access my Custom Recovery and simply by flashing a custom ROM gain access to the data.
I described the problem in more detail over here: http://forum.xda-developers.com/showthread.php?t=2598154
While unlocking a friend's phone I noticed that during the "fastboot oem unlock" procedure all data is wiped from the device. Something I totally forgot about.
This behavior is exactly what I want if my device gets stolen.
I can accept the hassle to deal with a temporary custom recovery or ways to perform an online nandroid, without the comfort of a Custom Recovery and having to lock the Bootloader again after every Custom ROM upgrade. (Yes, it will be a pain in the b*ttocks, but I want my data to be inaccessible.)
What do I have:
HTC One (international GSM version)
HTCdev.com unlocked
SuperCID
TWRP as Custom Recovery
Rooted CustomRom (SinLess in my case) installed
What I want:
Bootloader to be locked (so that you can't simply flash a Custom Recovery)
Stock Recovery (so that you can't simply flash a Custom ROM)
being able to make a nandroid backup, before unlocking again
keeping root and the Custom ROM
keeping SuperCID (req. for SinLess)
I don't want to make a mistake, so I am asking for some guidance. :angel:
I am assuming correctly that just flashing the Stock Recovery image is enough to get rid of TWRP?
I know that this temporary loading of a Recovery was a thing some time ago (HTC Desire), but I haven't looked into it for years now.
Is this still possible and how do I do it? Does this allow me to perform a nandroid backup with a locked bootloader?
Otherweise: If my bootloader is locked and my recovery reverted to stock, is there a way to nandroid backup my HTC One? I know about the App "Online Nandroid" (Play Store Link) that allows to perform a nandroid backup on a rooted phone without booting to recovery. Does it work with the HTC One?
What happens if I "relock" this htcdev.com unlocked phone? Will I simply be able to use "fastboot oem unlock" (followed by a full wipe) to unlock the bootloader again? Or are there more strings attached, like requiring htcdev.com again or any other problems?
Is the CID setting affected by any of this?
Am I missing something else?
Will the following routine be my way to go if I want to flash something (ROM, Kernel etc.)?
Backup Apps: Titanium Backup
Perform full nandroid Backup (App: Online Nandroid?)
Pull nandroid Backup, Titanium Backup Files and all Data from /sdcard/
Unlock phone --> result: full wipe of device (no big deal, as everything is backed up)
Flash Custom Recovery
Push Installation files for (rooted) Custom ROM, Kernel etc.
Push Titanium Backup Files
Install (rooted) Custom ROM, Kernel etc.
Boot Phone, set it up as usual and restore Titanium Backup
Push Data back to /sdcard/
Flash Stock Recovery
Relock Bootloader
Is this correct?
Or did I miss something?
Thanks in advance

noone? :angel:
I would highly appreciate any guidance on this. Thanks in advance

spaboleo said:
noone? :angel:
I would highly appreciate any guidance on this. Thanks in advance
Click to expand...
Click to collapse
Well, instead of doing what ur trying to do, you can encrypt the phone. A full phone encryption will prevent any changes made to any of the phone partitions. Thus, a ROM cannot be flashed in TWRP recovery, which serves your purpose and is easier than what u mentioned. However, decryption will factory reset the phone.
To answer your points:
1. Yes, flashing the Stock Recovery image will get rid of TWRP. But, im not 100% sure whether the ROM will work properly on stock recovery
2. You can definitely load a recovery without flashing it. Not tried on a locked bootloader. Sorry
3. Not sure whether the Root will be maintained after locking the bootloader and flashing stock recovery. If it is, then the Online Nandroid will definitely work
4. No strings attached. oem unlock will definitely do the trick
5. Nope, u will still be S-OFF. No CID is changed

spaboleo said:
no one?
Click to expand...
Click to collapse
Since you have s-off just use revone to unlock the bootloader without wiping data.
Procedure to lock things down:
Code:
fastboot flash recovery stock_recovery.img
fastboot oem lock
Procedure to return to unlocked/custom recovery:
Code:
adb push revone /data/local/tmp
adb shell
su
cd /data/local/tmp
chmod 755 revone
./revone -u
reboot bootloader
fastboot flash recovery twrp_recovery.img
You could also do revone with file explorer and terminal emulator and then flash TWRP directly in the OS using Flashify. This would allow you to return to unlocked with custom recovery without needing a computer.

raghav kapur said:
Well, instead of doing what ur trying to do, you can encrypt the phone. A full phone encryption will prevent any changes made to any of the phone partitions. Thus, a ROM cannot be flashed in TWRP recovery, which serves your purpose and is easier than what u mentioned. However, decryption will factory reset the phone.
To answer your points:
1. Yes, flashing the Stock Recovery image will get rid of TWRP. But, im not 100% sure whether the ROM will work properly on stock recovery
2. You can definitely load a recovery without flashing it. Not tried on a locked bootloader. Sorry
3. Not sure whether the Root will be maintained after locking the bootloader and flashing stock recovery. If it is, then the Online Nandroid will definitely work
4. No strings attached. oem unlock will definitely do the trick
5. Nope, u will still be S-OFF. No CID is changed
Click to expand...
Click to collapse
Thank you
Well I looked into encryption and it would require to use a PIN or Password lock instead of the Patternlock I prefer.
There was some mod that derived a PIN from a pattern input to work around this limitation, but I don't think it's the best idea to fiddle around with system files of that level.
But after reacing cschmitt's post, about the fact that there is a way to unlock the bootloader without wiping, my whole thoughts from the initial post are pointless
I guess using Android encryption is the only way.
Is it possible to use phone encryption together with location-based (wifi-based) disabling of the encryption using the "SecureSettings Plugin" for Tasker?
cschmitt said:
Since you have s-off just use revone to unlock the bootloader without wiping data.
Procedure to lock things down:
Code:
fastboot flash recovery stock_recovery.img
fastboot oem lock
Procedure to return to unlocked/custom recovery:
Code:
adb push revone /data/local/tmp
adb shell
su
cd /data/local/tmp
chmod 755 revone
./revone -u
reboot bootloader
fastboot flash recovery twrp_recovery.img
You could also do revone with file explorer and terminal emulator and then flash TWRP directly in the OS using Flashify. This would allow you to return to unlocked with custom recovery without needing a computer.
Click to expand...
Click to collapse
Wow! Thanks for pointing that out.
So the bootloader lock does not offer the sufficient protection that I am looking for
Unless...I return to S-On each and every time a I want to flash a rom or an Update.
Can I be sure that with S-On revone does not work to unlock the bootloader without wiping?
(edit: Warning Comment: don't do that...read below)
Thanks everyone

spaboleo said:
Thank you
Well I looked into encryption and it would require to use a PIN or Password lock instead of the Patternlock I prefer.
There was some mod that derived a PIN from a pattern input to work around this limitation, but I don't think it's the best idea to fiddle around with system files of that level.
But after reacing cschmitt's post, about the fact that there is a way to unlock the bootloader without wiping, my whole thoughts from the initial post are pointless
I guess using Android encryption is the only way.
Is it possible to use phone encryption together with location-based (wifi-based) disabling of the encryption using the "SecureSettings Plugin" for Tasker?
Wow! Thanks for pointing that out.
So the bootloader lock does not offer the sufficient protection that I am looking for
Unless...I return to S-On each and every time a I want to flash a rom or an Update.
Can I be sure that with S-On revone does not work to unlock the bootloader without wiping?
Thanks everyone
Click to expand...
Click to collapse
Nope, sorry. Remote encryption is impossible. You will need to manually choose the encryption option in security settings
P.S. Please hit the THANKS button if you think I helped you

spaboleo said:
Wow! Thanks for pointing that out.
So the bootloader lock does not offer the sufficient protection that I am looking for
Unless...I return to S-On each and every time a I want to flash a rom or an Update.
Can I be sure that with S-On revone does not work to unlock the bootloader without wiping?
Click to expand...
Click to collapse
The locked bootloader still offers the same level of protection. Unlocking via fastboot still wipes data, and the only way to unlock it via revone (which does not wipe data) is to be booted into the OS, which is protected by your password/PIN/pattern lock. (You might want to disable ADB while not using it, but in current versions ADB require authorization before it will connect to a new computer, and that would require unlocking your device with the password/PIN/pattern in order to approve the connection.)
If you have a locked bootloader with stock recovery it's not possible to use revone to unlock the bootloader via fastboot or adb, so you're still protected.
You cannot use revone to unlock bootloader if s-on.
An whatever you do do not go back to s-on.

cschmitt said:
The locked bootloader still offers the same level of protection. Unlocking via fastboot still wipes data, and the only way to unlock it via revone (which does not wipe data) is to be booted into the OS, which is protected by your password/PIN/pattern lock. (You might want to disable ADB while not using it, but in current versions ADB require authorization before it will connect to a new computer, and that would require unlocking your device with the password/PIN/pattern in order to approve the connection.)
If you have a locked bootloader with stock recovery it's not possible to use revone to unlock the bootloader via fastboot or adb, so you're still protected.
You cannot use revone to unlock bootloader if s-on.
An whatever you do do not go back to s-on.
Click to expand...
Click to collapse
I was initially S-OFF. I had to S-ON the phone to give it for warranty repair. I can simply use Rumrunner to S-OFF the phone again right? Or are there any other complications?
Thank you

raghav kapur said:
I was initially S-OFF. I had to S-ON the phone to give it for warranty repair. I can simply use Rumrunner to S-OFF the phone again right? Or are there any other complications?
Click to expand...
Click to collapse
There have been a number of cases of going back to s-on with locked bootloader and then not being able to unlock the bootloader again or regain root, so could not s-off again.

cschmitt said:
The locked bootloader still offers the same level of protection. Unlocking via fastboot still wipes data, and the only way to unlock it via revone (which does not wipe data) is to be booted into the OS, which is protected by your password/PIN/pattern lock. (You might want to disable ADB while not using it, but in current versions ADB require authorization before it will connect to a new computer, and that would require unlocking your device with the password/PIN/pattern in order to approve the connection.)
If you have a locked bootloader with stock recovery it's not possible to use revone to unlock the bootloader via fastboot or adb, so you're still protected.
You cannot use revone to unlock bootloader if s-on.
An whatever you do do not go back to s-on.
Click to expand...
Click to collapse
Thank you!
I thought the revone command was operable via fastboot/adb from the bootloader as well.
That is good news.
So one question remains.
Is there a way to access data from the stock recovery (maybe locating via "adb shell ls..." and then using "adb pull...") when s-off with a locked bootloader?
Assuming adb is turned off in the OS (developer options) if not used?
If this isn't possible this seems to be the perfect solution
I thank you sincerely!

spaboleo said:
So one question remains.
Is there a way to access data from the stock recovery (maybe locating via "adb shell ls..." and then using "adb pull...") when s-off with a locked bootloader?
Assuming adb is turned off in the OS (developer options) if not used?
Click to expand...
Click to collapse
All that's available in stock recovery in the ability to flash an HTC signed zip (official OTA, for example) and to factory reset.
There is no backup/restore/adb access/file manager like in a custom recovery.

Perfect :good: :laugh:
Sorry for asking that many questions, but as user the motto is "better safe than sorry".
I unlocked and s-offed my HTC One around June-August 2013 and besides a quick TWRP update here and there and a monthly ROM upgrade there was absolutely no need to fiddle around with it more.
Aftermarket development has become that reliable that it's actually possible to find a good "set it and forget it" daily driver setup.
And since I am not a developer and don't deal with those questions on a regular basis, I'm always not 100% sure if I get all the facts right.
Thanks for helping me out with this one!
I'm going to try it next weekend or next week: Going to backup my data and simulate a potential theft with the locked bootloader and reverted to stock recovery. Remote-Wiping the device, unlocking the bootloader conventionally via fastboot and making sure that this wipes all user-data on the phone. And then I'm going to give that booted into OS, revone unlock a try and simulate a potential rom upgrade, just as you described it.
Right now I just can't risk my daily driver phone, as I wouldn't have the time to set it up again.
Thanks for your extended help
Finally feeling secure again on Android.

!!!Please Answer THIS!!!

I just came to know that unlocking my xiaomi device will erase its data !!!!
Is this true??????
this thread says this only!!! -> https://twrp.me/xiaomi/xiaomiredmi4x.html
:crying::crying:

KCstark said:
I just came to know that unlocking my xiaomi device will erase its data !!!!
Is this true??????
this thread says this only!!! -> https://twrp.me/xiaomi/xiaomiredmi4x.html
:crying::crying:
Click to expand...
Click to collapse
Unlocking bootloader always erases Data Partition. First check that yours one is unlocked or not, not most devices are come locked. Unlocking will take time as Xiaomi gives you permission to unlock by their own software.

Make a backup, get all your data off then root it. I'm not entirely sure if you can unlock without erasing, but you should never be in a position where you can't afford to reinstall your applications.
This is why it is always best to get twrp on your phone asap so you can back up it.

No, unlocking bootloader doesn't wipes data but you must backup everything just in case anything goes wrong.
it is always recommended to backup everything when flashing ROM, kernel, mod, zip, flashing rom via fastboot method and recovery. in short you should backup everything in all this cases.

shohabmsk said:
Unlocking bootloader always erases Data Partition. First check that yours one is unlocked or not, not most devices are come locked. Unlocking will take time as Xiaomi gives you permission to unlock by their own software.
Click to expand...
Click to collapse
Actually I know most part and have already done getting permission but this was just a quick question as that's my sister's device and she won't accept its data being erased still thanks for your quick answer...
And by the way that device's bootloader is locked I have checked it.
.....:good:

metelhammer said:
No, unlocking bootloader doesn't wipes data but you must backup everything just in case anything goes wrong.
it is always recommended to backup everything when flashing ROM, kernel, mod, zip, flashing rom via fastboot method and recovery. in short you should backup everything in all this cases.
Click to expand...
Click to collapse
Have u done it your self if yes did u lose any of your data. Plz let me know......

KCstark said:
Have u done it your self if yes did u lose any of your data. Plz let me know......
Click to expand...
Click to collapse
Yes i have flashed recovery and roms i always do backup important thing and i take screenshot of installed apps before making any changes and save them to pc or to cloud storage.
there was issue i had was when i flashed TWRP 3.2.1.0 via adb i do not why but it asked me for password i didn't know to password so i had to wipe everything including internal storage and data.
latest twrp is must which is TWRP 3.2.1.0 in order to flash Oreo based ROM.
i was using TWRP 3.0.2-0 before and i had no issue with this recovery i has flashed several nougat roms on this recovery even have upgraded and downgraded from miui9 to miui 8 everything worked perfectly.
i don't know why but i wasn't able to flash any marshmallow based or nougat based roms on TWRP 3.2.1.0 recovery.
yes i did lose data when upgrading from TWRP 3.0.2-0 to TWRP 3.2.1.0 but i had done backup so no issues.
i would highly recommend you to do backup if you are making any changes in your device.

metelhammer said:
Yes i have flashed recovery and roms i always do backup important thing and i take screenshot of installed apps before making any changes and save them to pc or to cloud storage.
there was issue i had was when i flashed TWRP 3.2.1.0 via adb i do not why but it asked me for password i didn't know to password so i had to wipe everything including internal storage and data.
latest twrp is must which is TWRP 3.2.1.0 in order to flash Oreo based ROM.
i was using TWRP 3.0.2-0 before and i had no issue with this recovery i has flashed several nougat roms on this recovery even have upgraded and downgraded from miui9 to miui 8 everything worked perfectly.
i don't know why but i wasn't able to flash any marshmallow based or nougat based roms on TWRP 3.2.1.0 recovery.
yes i did lose data when upgrading from TWRP 3.0.2-0 to TWRP 3.2.1.0 but i had done backup so no issues.
i would highly recommend you to do backup if you are making any changes in your device.
Click to expand...
Click to collapse
Thanks bro

you need to install stock rom after unlocking
Unlocking Xiaomi Redmi4x santoni bootloader doesn't delete the data partition, but after unlocking the bootloader your phone won't boot, you need to install the same stock rom it was on phone previously.
Download MIUI Stock ROMs (if you didn't make OTA update from MIUI, check Older versions and download the correct ROM)
You can copy the ROM image to phone before unlocking or if you have already unlocked and stuck in boot, you can copy the ROM to an USB flash drive.
You need ADB installed on your PC.
Download the TWRP for Xiaomi Redmi 4X image.
If you want to restore the existing state of your phone, you need to make a backup of the data partition.
Press Volume Down + Power until phone gets in FASTBOOT.
Connect phone to PC with USB cable.
From PC command prompt type the command: fastboot.exe boot twrp-3.2.1-0-santoni.img
TWRP will start on your phone, you can backup all of the partitions, but you need only the data partition to restore.
Now Install the stock rom (you can select USB OTG if ROM is on USB drive), then RESTORE the backed up DATA partition only.

How to safely back to stock (factory state - get warranty)?

I want to back to stock on my Xiaomi A2 (full factory state - bootloader locked, no TWRP etc.) to get ma warranty back.
My current status:
- bootloader and critical unlocked
- loaded V10.0.8.0.PDIMIXM ROM (Fastboot official) from https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445 (used edl mode)
- previously I installed TWRP, decryption disabler and magiks
My last way to install ROM was by edl mode - downloaded fastboot version and used MiFlash tool (clean all). Previously I tried to run flash_all.bat from fastboot ROM, but it stopped on lashing devcfg_a (FAILED (remote: Flashing is not allowed for Critical Partitions), but I have critical unlocked.
My question is: Should I use MiFlash with edl mode to back to full stock with "clean all and lock" mode? Is it safe? I am afraid of locking bootloader and missing something what should be done before (I read it can brick the phone).
Should I install recovery first (missing in fastboot package), enable encryption or do something more?

Just flash fastboot image and relock and it'll be fine

I've reinstalled stock rom just yesterday, i had the same error with Mi Flash, i've flashed all manually from ADB, if you're coming from an Android Q ROM flash back the persist partition (i've a full Pie Backup) first or your WiFi MAC will disappear, when you've installed all (if the phone boot with Android One and everything Is working) just lock the bootloader (i've just used Oem Lock, idk about critical partitions) and you're good to go

When I used Mi A2 Toolkit, there were 3 options when I was unlocking bootloader: "Unlock OEM", "Unlock Flashing" and "Unlock flashing critical". I am not sure if executed all of them, but I am sure they were at least 2 of them.
So do I have to lock in the opposite way "Lock flashing critical", "Lock flashing" and "Lock OEM" or just "Lock OEM"? I need to be sure.
Can something happen if I will try to lock in that way, but I didn't unlock if before?

There is a toggle in developer options, "OEM Unlocking," which needs to be toggled on to lock or unlock the bootloader with fastboot. I would leave the bootloader and critical both unlocked until you are ready to use the warranty. If you have a bad flash and then lock the bootloader or critical then you might have a hard time getting everything working again.

Correct way to lock the bootloader?

What is the correct steps to factory reset and lock the boot loader.
I don't want to brick the P5.
I am trading in the P5 and I am second guessing myself on the step for this method.

Use the Android Flash Tool. It's foolproof and gives you the option to relock the bootloader and wipe data.
To manually lock the bootloader, reboot to bootloader, and use ADB:
fastboot flashing lock
If you intend to manually flash the factory image via ADB, make sure this is the LAST thing you do.

V0latyle said:
Use the Android Flash Tool. It's foolproof and gives you the option to relock the bootloader and wipe data.
To manually lock the bootloader, reboot to bootloader, and use ADB:
fastboot flashing lock
If you intend to manually flash the factory image via ADB, make sure this is the LAST thing you do.
Click to expand...
Click to collapse
Kool, I did not know that the flash tool would do this.

vandyman said:
Kool, I did not know that the flash tool would do this.
Click to expand...
Click to collapse
Yep. You can force flash all partitions too, as well as disable verity and verification. It's honestly the easiest way to factory flash.

Question 12 Pro Bootloop - bricked?

Hi everyone,
I'm afraid that my 12 Pro commited suicide... :/
It's pretty new, only 2 weeks old now. I was using it with the latest Xiaomi.eu ROM a did not have any problems - tilll yesterday.
Out of nowhere it started lagging and crashed during normal use. After the reboot it seemed to be fine again.
But in the following hours it crashed several times and rebooted by itself. Even while sitting on the table with screen off.
Finally it ended in a bootloop.
What I've tried so far:
- reflash Xiaomi.eu ROM without wiping data
- reflash Xiaomi.eu ROM with data wipe
- reflash Global ROM with the Mi Flash Tool and "clean all"
- reflash Global ROM with the Mi Tool, "clean all" and Relock Bootloader
- factory reset in stock recovery
- start without inserted SIM card
What is working:
Fastboot
Recovery Mode (and ADB sideload using the Mi Tool option in recovery mode)
Unlocking the BL using the official Xiaomi Unlock tool
Occasionally it boots into system but crashes afer a short time, so I'm not eben able to complete the setup assistant.
Most of the time it just hangs at the boot screen (the one with the Mi Logo, "Powered by Android" text and open lock at the top).
Any suggestions how to bring it back to life?
Pio

It sounds like hardware problems.

Flash it back to the original rom that came with the phone.
Then check if the problem occurs again or not.
When not than it is a problem with the EU rom, and when it has the same problem it probably is an hardware issue.

Unlock bootloader again.
Flash with full Chineese ROM (i assume that yours is a Chinese edition) with the option bootloader relock selected.
Please note, you are good to flash Global ROM on the top of any Chinese ROM including xiaomi.eu ROM. But do not choose relocking because it will brick your phone permanently.
Avoid your step,
"- reflash Global ROM with the Mi Tool, "clean all" and Relock Bootloader"

smohanv said:
Unlock bootloader again.
Flash with full Chineese ROM (i assume that yours is a Chinese edition) with the option bootloader relock selected.
Please note, you are good to flash Global ROM on the top of any Chinese ROM including xiaomi.eu ROM. But do not choose relocking because it will brick your phone permanently.
Avoid your step,
"- reflash Global ROM with the Mi Tool, "clean all" and Relock Bootloader"
Click to expand...
Click to collapse
Nope, I have the Global Edition.
So flashing the Chinese Rom and locking the BL is probably not the best idea
The device is at the service center at the moment, let's hope it won't take too long.

Worst out of worst, I can perform soldering and replace the nand chip of the device to recover it

I got my 12 Pro back und it's running fine so far.
Have had some random reboots in the past but they seem to be gone since the .18 update

Hi
That's exactly what I did. Is there any way to fix it?
Avoid your step, "- reflash Global ROM with the Mi Tool, "clean all" and Relock Bootloader"
smohanv said:
Unlock bootloader again.
Flash with full Chineese ROM (i assume that yours is a Chinese edition) with the option bootloader relock selected.
Please note, you are good to flash Global ROM on the top of any Chinese ROM including xiaomi.eu ROM. But do not choose relocking because it will brick your phone permanently.
Avoid your step,
"- reflash Global ROM with the Mi Tool, "clean all" and Relock Bootloader"
Click to expand...
Click to collapse

That's exactly what I did. Is there any way to fix it?
What a situation?
You have locked the bootloader on a CN version with a Global rom or vice versa?

NOSS8 said:
That's exactly what I did. Is there any way to fix it?
What a situation?
You have locked the bootloader on a CN version with a Global rom or vice versa?
Click to expand...
Click to collapse
I opened the bootloader and uploaded the global rom to Chinese. I locked the bootloader. I got into a loop. Now I can't open the bootloader to load the new firmware