Hello there! I'm looking for help regarding unlocking the bootloader on my Xiaomi 11 Lite 5G NE. I specifically wanted to do it without erasing my entire phone, because I've spent days on tweaking settings and mostly making it look aesthetically pleasing. Some of you might ask me about just backing it up, but the problem is that I don't really have enough storage on my SD Card to back it up entirely. Thanks for any answers beforehand! For now, have a great rest of your day/night.
You will not be able to unlock bootloader without erasing data that process is automated and cannot be changed
You can't do a complete backup or see files in folders with protected access if your bootloader is locked. But when unlocking, the data that you want to backup or look into gets erased.
This is why my first action when getting a new phone is to unlock the bootloader.
This is not a question of space. You can backup to an USB stick or to network with a booted TWRP. But you can only boot TWRP if your bootloader is unlocked ...
Related
Hi I want to format my drive and start with a completely clean system. The problem is I am not too good at using adb and fastboot.
So I used my wife's old sgs5 as a test device. I even had an SD card in there as backup. Somehow I dormated the dam SD card too.
I thought that if you sideload it would install it for you just like a twrp flash bit I can't seem to her it to work. Drivers are installed and it is detecting my device. I'm not sure what I'm doing wrong.
If someone could give me a step by step for setting this up I would forever be grateful.
I don't care about the s5 it's just a test device . But I want to root my.pixel
Thanks
First thing, the s5 is WAAAAYYY different than our pixel. That goes for partitions, flashing, adb/fastboot commands, etx. You could test and play with it all you want but as soon as you hop to the pixel it's a whole different game.
So your end goal is root on the stock rom?
If so you'll have to unlock the bootloader.
When you unlock the bootloader the device will factory reset (that takes care of your "clean" part).
After unlocking the bootloader, reboot to bootloader, fastboot boot twrp, install latest magisk, reboot.
Hello,
I have a Mi Max 3 6GB/128GB which I got from the UK which arrived unlocked and with Global Stable ROM installed which actually updated to V10.3.3.0.PEDMIXM by OTA - I tested.
fastboot getvar anti shows failed, so I assume no Anti Rollback Protection, which I thought a little strange, it being MIUI 10 with (after OTA) June 2019 security patch.
I spent the last couple weeks setting up the phone to my liking (I have 300 apps installed) and finally finished yesterday.
Then I wanted to uninstall some Google/Facebook/Xiaomi bloatware using the excellent "Xiaomi ADB/Fastboot Tools".
I was pretty careful in my opinion to only remove the safe ones (the tool claims to only show you the safe ones) like Music, Video, MiPay, MiCloud, MiForum, MiSIM and all Facebook in the ADB section of the tool.
The I switched in fastboot and thought it would be a good idea to wipe Cache (nothing else).
Upon restart the Mi Max 3 first shows the black boot screen with unlock written at the bottom, then changes to the normal boot boot screen with MIU and the points at the bottom showing that it is busy booting. It stayed there for a while and I thought maybe it was rebuilding the cache and it took that long, but after 30 min still no luck.
Then I fired up the "Xiaomi ADB/Fastboot Tools" on my PC again and it told me the phone was in ADB mode, I could reboot into system mode, where the same thing happened - no progress in booting.
I cannot turn off my phone either, but I can switch from sastem boot (which gets stuck) into fastboot mode via ADB.
Would someone know what's wrong and what I can do to get my phone out of that bootloop while hopefully maintaining all my data and setups, on which I worked for weeks?
Thank you so much for your help!
P.S .: In case it could help: I could read out the phone properties of the Mi Max using the "Xiaomi ADB / Fastboot Tools" while it was softbricked, meaning the ro. init. persist. sys. and dalvik. values of the smartphone. I am happy to post them here, if requested.
Hi,
Do you have an SD card? If so, remove it, because as you cleared the cache, I think it might be a problem with encryption (lost reference).
In your case, I believe a reset will work again, but you will lose application configuration data. Via ADB you can backup files only.
If you do not have unlock bootloader, be very careful as you will not be able to flash TWRP or others.
Good luck!
Thanks, the phone came from the vendor with Global Stable ROM and unlocked. It may be an unofficial unlock, though I was able to install OTAs.
I don't have SDCard.
How can I do ADB backup?
I was able to flash official TWRP just a few minutes but it couldn't access data, maybe because it is encrypted. Now I think I will try and install latest Orange Fox r10 stable, which I think should be able to handle decryption, so that maybe I will be able to get at my date.
Any other advice?
Hi,
Now that you have TWRP, clear cache / dalvik from TWRP and try starting again, maybe start system.
About copy via adb follows a link below:
https://www.lifewire.com/use-minimal-adb-and-fastboot-4582201
in step 2
"
The command to move files from your computer to your phone is adb push.
To move files from your phone to your computer the command is adb pull.
"
Through TWRP you may also be able to back up. Go to (mount partitions) and select all partitions.
Make sure the TWRP MTP option is on, it will allow the device to be mounted via usb on your computer.
I use TWRP I use nijel8, it works very well.
https://forum.xda-developers.com/mi-max-3/development/recovery-twrp-3-2-3-1-nitrogen-t3866084
If you can't launch system, you will have to reinstall the Rom.
Good luck!
PS.
More help for adb.
https://forum.xda-developers.com/android/help/adb-fastboot-commands-bootloader-kernel-t3597181
Thanks for your advice!
I first used the official TWRP and I was able to flash it and start it.
But then the wipe of cache and dalvik failed.
And I could not mount data etc..
When I tried to repair the file system with TWRP I got error 255 - unable to repair data from fsck.f2fs.
Then I saw in your signature that you use nijel8's TWRP and I read that thread, and I started to understand, that my TWRP errors most likely originate from TWRP not being able to decrypt my partitions.
However, towards the end of the thread it seemed that nijel8 stopped working on that project and then Xiaomi once again changed the encryption in MIUI 10/Pie and so it was recommended first to use an obscure Chinese TWRP and then to move on to Orange Fox Recovery Project, which supposedly can handle the decryption better. So that's what I got and I am just about to install it and see if I can rescue or even repair anything.
If you have any other tips for me, I would be very grateful.
You have explored the possibilities well, at the moment I dont have more options regarding current system recovery / backup.
The encryption error resolves you by formatting the user partition by TWRP, in the option to format f2fs plus the installation of a custom Rom or Xiaomi.eu.
Look for tutorials and other reviews before testing these procedures.
Remember that there is a big achance of your ARB model as well.
Good luck.
PS. You can try dirty flash. Find an recovery Rom same version, and flash via TWRP.
My goal is to create a system backup (including Android OS) of my Galaxy S9 (SM-G960F), just like I can do on my PC using Acronis True Image or other similar programs, because now I have Pie but Android 10 is available, and I want to be able to roll back in case of bugs.
I've found out one of the best ways of doing this is using TWRP. Flashing a custom recovery means making changes (editing recovery partition), but some say TWRP can be run even without being installed, and that was my intent. I tried on my old Galaxy S5 mini and I could successfully run TWRP without rewriting recovery partition.
However, it turned out that bootloader unlocking is needed. No problem, I thought: I'll unlock it, backup system, and lock it again. But when I tried to switch the 'OEM unlock' item, a dialog appeared saying that my device would have been formatted and Samsung Knox services would stop working.
I was wondering:
- if I do enable OEM unlock and erase data, setting OEM unlock to off would reactivate Knox services?
- is there a way to actually unlock bootloader without erasing data?
- is there any hidden method to boot TWRP without unlocking bootloader?
- is there any better way to backup whole system and data?
I may have already partially answered the last question: using adb backup I backup as much data as possible, and by downloading OS image from Sammobile.com I have an OS backup. Can it work? If I decide to "restore" that kind of backup there would be any kind of data that would be lost during this particular roll back procedure?
Thanks in advance.
If my English is odd or incorrect, that's because it isn't my primary language. I'm from Italy - land of Pizza and Coronavirus.
Greetings.
I had issues updating my Honor. Every time I would try the update, after downloading it, it would boot into TWRP with the message failed to unmount /system: device or resource busy.. Then, if I rebooted, the update simply didn't work (I was stuck in an older version of EMUI 8.0, I don't quite recall the precise number). Actually, the same error message would come every time I simply booted into TWRP.
At this point, after a backup, I thought I could just wipe the /system partition and then flash a zip, containing a new ROM, from the TWRP; I wiped the partition and rebooted, and of course the phone started into TWRP, because there wasn't a system anymore. The problem is: TWRP is stuck at splashscreen, and I can't access it anymore.
I tried going into fastboot, but only to find myself with the message Phone Unlocked, FRP Locked, and I was unable to boot another version of the TWRP.
Another thing I did was to boot into the e-Recovery, and from there if I tried restore to factory settings, it would boot again into the stuck TWRP; and if I tried to download latest version and restore, the download would fail because I couldn't retrieve package info.
I then tried a solution I've seen in this forum, namely , with a Windows 10 machine that I used as an hotspot (actually I wasn't able to use the same IP from primary and secondary DNS, only for primary).
I understand that the only thing left to do is to pay some amount of money to some company that would give me the FRP unlock key based on my IMEI, and I actually tried that, with HCU-Client, but after buying 12 credits, they reimbursed them for no appareantly no reasons. Did somebody use this method, perhaps with another company? And did it work?
tl; dr: honor 7x bricked: stuck into fastboot with FRP lock, can't open twrp, don't have system, need help to know if I can actually pay a company to give me the key for the FRP unlock.
Sadly my phone is corrupt and cant start anymore ... I want to use Newsflasher to rescue my Phone.
Before I want to use TWRP to make a backup. But I cannot enter TWRP.
As far as I understood TWRP cannot be installed on XZ2 compact, but it can be temporarily flashed (as I of course did to get my LineageOS Android 11).
But now when I flash it TWRP asks for a Password.
I just have my regular Screen Unlock Password - but if I type it in it tells me PASSWORD FAILED.
How can that be? Which other Password could it be? I dont know any ...
Obviously I would just remove the screen lock in Android. But it's corrupt x(
I want to do this before I have to do the wipe with Newflasher
If I ignore data encryption then it tells me when booting system that I have no OS installed ...
So then I will never be able to get my data back because encryption with password is still active and I cannot boot to turn it off?
And TWRP is bugged so it does not accept my real password? (How can that be omg ...)
Nothing can done now u have to flash flash a fastboot rom on your device without backup
That is
the_arxyn said:
Nothing can done now u have to flash flash a fastboot rom on your device without backup
Click to expand...
Click to collapse
That is what I was already thinking but yes let it be :/
I will use the old file that I used 2 years ago and also worked when I had to do the same.
For a strange reason it does not work when executing in the original created folder (by Xperifirm), but only if I push it on a external Hard Drive?
Otherwise it will tell FINISHED but it just took 3 seconds, which it will also do if it is played in any other folder ...
Anyways it asked me for a weird reason if I want to keep my userdata. I was thinking that there is no way to install a new OS but still keep the old data. I did it but then at the end of the Flashing it told the Sync did not work. I still booted up and it tells that it cant load the Android. So I dont know if this happened because I either left the user data intact or because that sync at the end did not work.
I'm just now scared to erase it when trying again, just in case that indeed I could safe my data.
So what is the story behind that *Erase User data Y / N*. Can I indeed keep my files this way?