Related
Hello,
I have a Mi Mix 3, MIUI global 10.2 stable, 10.2.2.0 PEEMIXM.
I managed to root, install TWRP and gcam after a few days of trying.
* Two days ago I updated from phone settings (About phone, Check updates ...)
* I lost both root and TWRP.
* I tried exactly the previous methods to root and phone stuck at booting (three dots flicking on the screen) - via PC / adb / fastboot.
* After that, I reset phone to factory settings and try again - boot in fastboot, try to flash TWRP and I get this error message: error cannot load TWRP.img file (not available or missing).
I also mention:
1. Phone was already rooted by the same procedure
2. Phone is unlocked
3. Dev options / USB debugging check
4. I renamed TWRP.img with recovery.img
5. I even try "TWRP" without extension ".IMG" (last week before the update I succeeded this way - no .img in the name of the file)
Please help
I need something so that I can root phone again AND won't delete TWRP and root after next update.
Thx very very much.
Any software update on this phone will overwrite TWRP if it has a recovery partition image, which most Xiaomi updates do have. There is a way to block it from getting overwritten by booting the phone, which has been implemented in the latest versions of the Chinese TWRP image. I do not know if they have been implmented on the official TWRP for our device.
Based on what you posted, it sounds like you probably need to reboot into the bootloader and use fastboot flash recovery "TWRPIMAGE.IMG" to install TWRP, then hold VOL Down + Power and reboot into TWRP. Once that is done, you can root again using MAGISK or whatever you choose to use for root.
PWn3R said:
Any software update on this phone will overwrite TWRP if it has a recovery partition image, which most Xiaomi updates do have. There is a way to block it from getting overwritten by booting the phone, which has been implemented in the latest versions of the Chinese TWRP image. I do not know if they have been implmented on the official TWRP for our device.
Based on what you posted, it sounds like you probably need to reboot into the bootloader and use fastboot flash recovery "TWRPIMAGE.IMG" to install TWRP, then hold VOL Down + Power and reboot into TWRP. Once that is done, you can root again using MAGISK or whatever you choose to use for root.
Click to expand...
Click to collapse
Thank you very much for your time and information. I must add that I was able to flash TWRP according to the procedure explained above, but I couldn't enter/access TWRP recovery. Then, I tried to re-flash TWRP and I always get the message: "error cannot load 'twrp.img' no such file or directory"
And I've tried several methods, several TWRP, different USB cables - almost everything you can imagine. Still, I cannot load the TWRP.img - it's not found. I must say I follow exactly the procedure explained in every posts.
What options do I have?
If you are using adb to load twrp, try putting it in the c/ of your pc, and putting twrp image in the adb folder, and if that didnt work, try renaming the img file to pocorecovery
I spent all day trying to find a way to root my phone after moving from Lineage OS to Oxygen OS 10.01. Namely, https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853.
The problem is that the information given is out of date as of a few days ago, and installing the patched bootloader broke wifi, calling, and probably all sorts of other things.
I want to make sure this is as simple as possible for people having the same issues!
Before You Download
You MUST be running Oxygen OS 10.01 exactly.
You MUST be on a OnePlus 6 (not a OnePlus 6T)
You MUST have an unlocked bootloader (Google for instructions, "fastboot oem unlock", this will require a factory reset)
Install ADB and Fastboot on your computer (Google for instructions)
Installation Instructions
Make sure you're running Oxygen OS 10.01 for the OnePlus 6. If you're on an earlier version and need to install, download HERE and install it as a local upgrade (Google for instructions).
Download and install Magisk Manager. I'm using Version 7.40.
Download my modified boot image here
Put your OnePlus 6 in Fastboot mode and plug it into your computer (Google for instructions)
Place my boot file, new_boot_image_xda.img, in the same folder Fastboot is running
Run fastboot flash boot new_boot_image_xda.img
Run fastboot reboot or otherwise reboot your phone.
If you want to do this on other devices:
Extract boot.img from your ROM's zip file's payload.bin using Payload Dumper 64 (I can't post external links, Google it)
Place boot.img in your phone's local storage
Open Magisk Manager on Android, then "Install Magisk" -> "Patch a File" -> select boot.img
Move the modified boot image (magisk_patched.img) to your computer
Enter the fastboot commands from above, replacing new_boot_image_xda.img with your modified boot image
May be a dumb question: Do I lose data? There's no step of wiping, but I'm afraid this may be necessary.
Oh, and another question: how about updates? Will I lose my data on further updates?
And I'm sure I need to unlock my bootloader before.
jacdelad said:
May be a dumb question: Do I lose data? There's no step of wiping, but I'm afraid this may be necessary.
Oh, and another question: how about updates? Will I lose my data on further updates?
And I'm sure I need to unlock my bootloader before.
Click to expand...
Click to collapse
Unlocking the bootloader triggers a factory reset (nothing in internal storage is lost, but you lose apps and settings), and you need to do this before rooting. If your bootloader is unlocked, you shouldn't have to wipe anything unless you miss an instruction or install it on the wrong version. You won't be able to update OTA without losing root.
If you're new to rooting, just be prepared to lose your data no matter what, because it's incredibly easy to follow the wrong advice and end up bricked. There have been times where the only thing my OP6 can do is display a white LED because with the wrong command, I wiped everything from the boot partition, recovery partition, and internal storage. For that reason, you might wait a week or so for more documentation on rooting this phone with this version of OOS.
mouthofrandom said:
Unlocking the bootloader triggers a factory reset (nothing in internal storage is lost, but you lose apps and settings), and you need to do this before rooting. If your bootloader is unlocked, you shouldn't have to wipe anything unless you miss an instruction or install it on the wrong version. You won't be able to update OTA without losing root.
If you're new to rooting, just be prepared to lose your data no matter what, because it's incredibly easy to follow the wrong advice and end up bricked. There have been times where the only thing my OP6 can do is display a white LED because with the wrong command, I wiped everything from the boot partition, recovery partition, and internal storage. For that reason, you might wait a week or so for more documentation on rooting this phone with this version of OOS.
Click to expand...
Click to collapse
Nah, no problem. I have this phone since it came out and use custom ROMs since then, do not really new. I know that unlocking the bootloader resets my phone. I was just wondering if I can install your image without unlocking, because I'm currently locked (had a problem with the latest Syberia update and choose to stay with OOS). And how to update when OOS 10.0.2 arrives.
I tried it and it worked fine, but today after uninstalling some blotware and rebooting I am stucked on the bootloader warning page which takes me to the fastboot mode after a minute or so (this is what used to happen to me whenever I flash a magisk patch boot file) Now I'm downloading the stock rom to get the stock boot.img.
This one video is for oneplus 6t
Pretty clean guide
I went through the process of using Smali and Magisk on my phone. Everything was good. Since I was doing this for PoGo, I decided to "clean-up" by disabling some of the settings. I turned off OEM unlocking, reboot the phone in to the bootloader and did a adb flashing lock. I rebooted the phone and not get the error "Can't find a valid operating system". I can boot in to the bootloader with the power button + down volume but I can't unlock the bootloader with ADB and fastboot.
Am I screwed?
I'm also not able to boot in to recovery. I also get the error "Can't find valid operation system"
Well probably too late to reply.
I'm not an expert, i'm newbee but when i installed my custom rom i met some problems to reboot. I solved them by re-installing firm operating system. You can do it by connecting your device with a good usb cable and go to google website : android flash tool
This will reinstall a new an clean system (but erase your data if not saved before).
After that you can install a custom rom from the begining.
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
BillyWroth said:
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
Click to expand...
Click to collapse
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
CriGiu said:
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
Click to expand...
Click to collapse
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
BillyWroth said:
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
Click to expand...
Click to collapse
hello, im having maybe a similiar case with my phone (in this case its a MI A3) i installed "succefully" evolution x 6.3 on my phone and everthing was ok with a few bugs, the only problem was that mi cannot connect to internet, so i decided to restart the phone and now my phone just don't turn on, the power button don't respond and i cannot start up my phone and its just a black screen, if u remeber ¿can u pass the tutorial that u saw on reddit? maybe it can help me
Hello everyone,
I need some help with the following situation:
Using Odin I successfully flashed my Galaxy A32 5G with Android 13 (as indicated by the green PASS in Odin).
When the phone tries to reboot, I get the dreaded error message, "Can't load Android system. Your data may be corrupt....."
On my PC I issued the command, >adb devices, but no devices were found.
This is probably because I did not enable USB debugging, when the phone was still working.
I'm trying to avoid doing a factory reset, because I don't want all my data wiped.
According to the following article, you can flash an OTA file using "adb sideload" command, even without enabling USB debugging.
However, everything else I've read says that adb commands work only when USB debugging is enabled.
Fix “Can’t Load Android System Your Data May Be Corrupt” Without Resethttps://www.droidwin.com/fix-cant-load-android-system-your-data-may-be-corrupt-without-reset/
Can someone perhaps clarify whether or not USB debugging is required for using adb commands?
Thank you very much,
Peter
plee12 said:
Hello everyone,
I need some help with the following situation:
Using Odin I successfully flashed my Galaxy A32 5G with Android 13 (as indicated by the green PASS in Odin).
When the phone tries to reboot, I get the dreaded error message, "Can't load Android system. Your data may be corrupt....."
On my PC I issued the command, >adb devices, but no devices were found.
This is probably because I did not enable USB debugging, when the phone was still working.
I'm trying to avoid doing a factory reset, because I don't want all my data wiped.
According to the following article, you can flash an OTA file using "adb sideload" command, even without enabling USB debugging.
However, everything else I've read says that adb commands work only when USB debugging is enabled.
Fix “Can’t Load Android System Your Data May Be Corrupt” Without Resethttps://www.droidwin.com/fix-cant-load-android-system-your-data-may-be-corrupt-without-reset/
Can someone perhaps clarify whether or not USB debugging is required for using adb commands?
Thank you very much,
Peter
Click to expand...
Click to collapse
I think, In stock recovery only the adb sideload command works so it don't need USB Debugging to be turned ON.
aiSanaul said:
I think, In stock recovery only the adb sideload command works so it don't need USB Debugging to be turned ON.
Click to expand...
Click to collapse
Thanks for your input. Encouraged by your input, I read the article again and realized that I have to put the phone in sideload mode first.
So, I went back to the stock recovery mode and selected the menu item, "Apply update from ADB". Then I see the message on the phone, "Now send the package you want to apply....with adb sideload <filename>". Now that I thought the phone was in sideload mode, on the PC I entered ">adb devices". This time it recognized the device and displayed the device name. However, it also displayed the word, "unauthorized", after the device name. According to the article, if sideload is properly entered, it should display the word, "sideload".
Anyway I tried entering ">adb sideload update.zip", and I got the error message, "device unauthorized".
So, any idea how to get the phone to be authorized?
If this is not possible, I was thinking of replacing the stock recovery with a custom recovery like TWRP. This way I can at least back up all my data first before doing a factory reset. However, I believe installing TWRP requires the bootloader to be unlocked, which automatically wipes all data. So, this defeats the purpose of installing TWRP in the first place
Is there some trick to install TWRP without unlocking the bootloader?
Thank you
plee12 said:
Thanks for your input. Encouraged by your input, I read the article again and realized that I have to put the phone in sideload mode first.
So, I went back to the stock recovery mode and selected the menu item, "Apply update from ADB". Then I see the message on the phone, "Now send the package you want to apply....with adb sideload <filename>". Now that I thought the phone was in sideload mode, on the PC I entered ">adb devices". This time it recognized the device and displayed the device name. However, it also displayed the word, "unauthorized", after the device name. According to the article, if sideload is properly entered, it should display the word, "sideload".
Anyway I tried entering ">adb sideload update.zip", and I got the error message, "device unauthorized".
So, any idea how to get the phone to be authorized?
If this is not possible, I was thinking of replacing the stock recovery with a custom recovery like TWRP. This way I can at least back up all my data first before doing a factory reset. However, I believe installing TWRP requires the bootloader to be unlocked, which automatically wipes all data. So, this defeats the purpose of installing TWRP in the first place
Is there some trick to install TWRP without unlocking the bootloader?
Thank you
Click to expand...
Click to collapse
As you already know this is not possible without unlocking bootloader, I will explain further more to make it easy to understand.
If you don't unlock your bootloader and try flashing TWRP on your phone using ODIN Flash Tool then maybe your phone get into an veification error and your phone will end up in a softbrick. You can repair your phone by flashing your phone's stock firmware using ODIN Flash Tool, eventually you will wnd up loosing all your data.
Also unlocking bootloader in Samsung devices is so easy by turning OEM Unlocking in Developer options, but you don't seem to have access to your phone.
An Unlocked Bootloader is the PASS, which allows you to do custom thing to your phone. So without it, this won't work, maybe that is why you got that error “Can’t Load Android System Your Data May Be Corrupt”.
ALTERNATIVELY you can try flashing your phone's OLD original Stock Firmware using ODIN Flash Tool and see what happens. You can also try flashing TWRP through ODIN Flash Tool. Only flash OFFICIAL TWRP made for your device (if any), otherwise you don't have options I guess.
also Why didn't you Unlocked Bootloader before flashing a custom rom? because of warranty?
aiSanaul said:
As you already know this is not possible without unlocking bootloader, I will explain further more to make it easy to understand.
If you don't unlock your bootloader and try flashing TWRP on your phone using ODIN Flash Tool then maybe your phone get into an veification error and your phone will end up in a softbrick. You can repair your phone by flashing your phone's stock firmware using ODIN Flash Tool, eventually you will wnd up loosing all your data.
Also unlocking bootloader in Samsung devices is so easy by turning OEM Unlocking in Developer options, but you don't seem to have access to your phone.
An Unlocked Bootloader is the PASS, which allows you to do custom thing to your phone. So without it, this won't work, maybe that is why you got that error “Can’t Load Android System Your Data May Be Corrupt”.
ALTERNATIVELY you can try flashing your phone's OLD original Stock Firmware using ODIN Flash Tool and see what happens. You can also try flashing TWRP through ODIN Flash Tool. Only flash OFFICIAL TWRP made for your device (if any), otherwise you don't have options I guess.
also Why didn't you Unlocked Bootloader before flashing a custom rom? because of warranty?
Click to expand...
Click to collapse
Thanks very much for your detailed explanations and for your continued support.
Let me answer your question first about why I didn't unlock the bootloader before flashing a custom ROM. Let me backtrack and explain how this problem came about in the first place. My phone was doing an automatic system update two weeks ago (Android 13). After downloading and installing, it tried to boot up. That's when it got stuck in an infinite rebooting loop. At that point, I had no way to change any settings on the phone.
Also, to clear up any confusion, I was not trying to flash a custom ROM. I was simply trying to flash the stock ROM (Android 13), supposedly the same firmware version as the OTA that broke my phone after the automatic system update. I was thinking that perhaps there was an internet glitch during the automatic system update process, which corrupted the OS. So, I was just trying to re-install the same version as the OTA to see if that would solve the problem.
I had also thought about flashing the original version that came with the device (Android 11). But, I think I read somewhere that either Samsung phones do not allow the user to downgrade, or even if it does allow you do so, the downgrading process will wipe out the existing data on the phone. Perhaps you can confirm that or not?
In the meantime, as you suggested, I will look into how to flash TWRP.
Thank you