Hey guys, I am new to the forum and this is my first time posting, yesterday I made a stupid mistake of flashing my Xiaomi 6 MIUI to Lineage OS, I didn't do it correctly and it resulted a bootloop, I managed to flash back the stock rom via fastboot, it did boot up into MIUI, but I cannot connect to network as nothing is shown there and it just stucks in updating...
I also have TWRP but somehow Xiaomi recovery had taken over and I have no idea how to enter TWRP, (tried volume up + PWR, both volume + PWR, volume down + PWR which just gives me fastboot, Volume up plus + home...) is there anyway for me to get to TWRP and maybe I can try to flash Lineage?
Or how can I flash back to the stock rom via fastboot/TWRP, thank you for your help~!
Flash twrp from fastboot, make a fastboot format userdata and from twrp wipe all and then flash firmware, rom of your choice, gapps if you want and the others. Then reboot.
ccelik97 said:
Flash twrp from fastboot, make a fastboot format userdata and from twrp wipe all and then flash firmware, rom of your choice, gapps if you want and the others. Then reboot.
Click to expand...
Click to collapse
hey there, thank you so much for your reply!!!
Stupidly I made a terrible mistake of relocking from the miflash tool and nope it doesn't work... Now will TWRP flash if my phone is locked???
And could you please tell me the instructions as I am a complete noob, thank you once again!
CaptainBilly said:
hey there, thank you so much for your reply!!!
Stupidly I made a terrible mistake of relocking from the miflash tool and nope it doesn't work... Now will TWRP flash if my phone is locked???
And could you please tell me the instructions as I am a complete noob, thank you once again!
Click to expand...
Click to collapse
No you can't do anything with a locked bootloader. But since you have permission to unlock your bootloader with xiaomi's tool then unlock it again. (To be honest I've first unlocked at octover and haven't locked it again so I don't know if you'd have to wait for another 3 days. But after getting it unlocked it'd be okay, you'll be able to use fastboot so no worries)
ccelik97 said:
No you can't do anything with a locked bootloader. But since you have permission to unlock your bootloader with xiaomi's tool then unlock it again. (To be honest I've first unlocked at octover and haven't locked it again so I don't know if you'd have to wait for another 3 days. But after getting it unlocked it'd be okay, you'll be able to use fastboot so no worries)
Click to expand...
Click to collapse
Okay then! Thank you! I just unlocked it! But now I have no idea how to reflash TWRP, could u please help?
I have the minimal ADB and fastboot installed, but currently when I type fastboot flash recovery recovery.img, both powershell/cmd says cannot load recovery.img...
CaptainBilly said:
Okay then! Thank you! I just unlocked it! But now I have no idea how to reflash TWRP, could u please help?
I have the minimal ADB and fastboot installed, but currently when I type fastboot flash recovery recovery.img, both powershell/cmd says cannot load recovery.img...
Click to expand...
Click to collapse
Do you have a file called recovery.img at the same directory with the fastboot binary file? If no either rename it or write the recovery img 's actual name in terminal after fastboot flash recovery.
ccelik97 said:
Do you have a file called recovery.img at the same directory with the fastboot binary file? If no either rename it or write the recovery img 's actual name in terminal after fastboot flash recovery.
Click to expand...
Click to collapse
I am not sure what fastboot binary file is...sorry, but I think what you meant is having TWRP file at the same location as the Minimal ADB and Fastboot program? If so yes I do, I did save the TWRP as the same location AND I did renamed it recovery.img, should I use MIUI Recovery Tool to install TWRP for me?
Thanks once again! Really appreciated.
CaptainBilly said:
I am not sure what fastboot binary file is...sorry, but I think what you meant is having TWRP file at the same location as the Minimal ADB and Fastboot program? If so yes I do, I did save the TWRP as the same location AND I did renamed it recovery.img, should I use MIUI Recovery Tool to install TWRP for me?
Thanks once again! Really appreciated.
Click to expand...
Click to collapse
Check the file name correctly. Windows doesn't show every extension name so maybe the file you see as "recovery.img" is actually "recovery.img.img". Enable to show all extensions from explorer settings (search for it in Google because I forget it too even though I'm doing it on all windows pcs I use
And for what that so called "fastboot binary file" is just that "fastboot" file in adb and fastboot folder. It's a binary type file and that's why I'm referring to it as a binary file (it has executable codes in it). And the difference from a text file is while a text file has a structure like "file start"+"the actual text in it"+"file end", a binary file has executable codes in it so you execute it (like typing "fastboot flash recovery twrp.img ; it means you're running fastboot to execute it's flash function to recovery partition of your device, and the file you want to use as the input is twrp.img in this example. It's good to learn.)
ccelik97 said:
Check the file name correctly. Windows doesn't show every extension name so maybe the file you see as "recovery.img" is actually "recovery.img.img". Enable to show all extensions from explorer settings (search for it in Google because I forget it too even though I'm doing it on all windows pcs I use
And for what that so called "fastboot binary file" is just that "fastboot" file in adb and fastboot folder. It's a binary type file and that's why I'm referring to it as a binary file (it has executable codes in it). And the difference from a text file is while a text file has a structure like "file start"+"the actual text in it"+"file end", a binary file has executable codes in it so you execute it (like typing "fastboot flash recovery twrp.img ; it means you're running fastboot to execute it's flash function to recovery partition of your device, and the file you want to use as the input is twrp.img in this example. It's good to learn.)
Click to expand...
Click to collapse
Thank you SO MUCH!!! your the best!!! Now I installed TWRP!!!
what should we do next? wipe portion? what does that mean? thanks!
CaptainBilly said:
Thank you SO MUCH!!! your the best!!! Now I installed TWRP!!!
what should we do next? wipe portion? what does that mean? thanks!
Click to expand...
Click to collapse
Not portion, but partition. Partitions are simply the different parts on a storage. For example when you open a file explorer on your device you see your sdcard folder which is in data partition. System files are in system partition, kernel is in boot partition etc.
And yes simply in twrp under wipe select advanced wipe and select all of them, wipe. After that from the same screen select format data, type yes to confirm and reboot to recovery again.
Then while in twrp copy files you want to flash to your device (or use an usb flash drive with otg, which I prefer but for this don't forget to tick usb otg in mount section in twrp)
Personally I flash firnware, rom, gapps and reboot, configure my account settings and auto download apps etc. Then when finished go back to recovery and flash magisk (flash magisk after booting into the system at least for once or most likely you won't pass safetynet checks) for root and the other things (e.g. font).
ccelik97 said:
Not portion, but partition. Partitions are simply the different parts on a storage. For example when you open a file explorer on your device you see your sdcard folder which is in data partition. System files are in system partition, kernel is in boot partition etc.
And yes simply in twrp under wipe select advanced wipe and select all of them, wipe. After that from the same screen select format data, type yes to confirm and reboot to recovery again.
Then while in twrp copy files you want to flash to your device (or use an usb flash drive with otg, which I prefer but for this don't forget to tick usb otg in mount section in twrp)
Personally I flash firnware, rom, gapps and reboot, configure my account settings and auto download apps etc. Then when finished go back to recovery and flash magisk (flash magisk after booting into the system at least for once or most likely you won't pass safetynet checks) for root and the other things (e.g. font).
Click to expand...
Click to collapse
oopsies sorry, I am very new to this and thanks for your really helpful explanation, I will wipe all now that includes dalvik,cache, system and data and internal storage, but what firmware should I flash and how do I know which one do I need? I am going for Linegae os btw.
Thanks once again, if without ur help my phone will essentially be dead :good:
ccelik97 said:
Not portion, but partition. Partitions are simply the different parts on a storage. For example when you open a file explorer on your device you see your sdcard folder which is in data partition. System files are in system partition, kernel is in boot partition etc.
And yes simply in twrp under wipe select advanced wipe and select all of them, wipe. After that from the same screen select format data, type yes to confirm and reboot to recovery again.
Then while in twrp copy files you want to flash to your device (or use an usb flash drive with otg, which I prefer but for this don't forget to tick usb otg in mount section in twrp)
Personally I flash firnware, rom, gapps and reboot, configure my account settings and auto download apps etc. Then when finished go back to recovery and flash magisk (flash magisk after booting into the system at least for once or most likely you won't pass safetynet checks) for root and the other things (e.g. font).
Click to expand...
Click to collapse
I will wipe all now! Thankyou! but one question how do I know which firmware I need to flash and what do you mean by going back and flash magisk?
I am planning to flash lineage os if possible! Thanks once again for your help! if its without you I would probably never have it functional again
CaptainBilly said:
I will wipe all now! Thankyou! but one question how do I know which firmware I need to flash and what do you mean by going back and flash magisk?
I am planning to flash lineage os if possible! Thanks once again for your help! if its without you I would probably never have it functional again
Click to expand...
Click to collapse
You're welcome but I'm pretty sure you'd figure it out yourself if you've wanted.
Which lineageos? And I suggest you to wait for the official los (next week I think) and try omnirom official for example. Officials are better for newcomers but try to not to spam the threads with the questions without doing some research first. You know I could just ignore your topic in the beginning and maybe nobody would answer it and you'd be on your own with all those comments on other threads without a proper preliminary knowledge.
ccelik97 said:
You're welcome but I'm pretty sure you'd figure it out yourself if you've wanted.
Which lineageos? And I suggest you to wait for the official los (next week I think) and try omnirom official for example. Officials are better for newcomers but try to not to spam the threads with the questions without doing some research first. You know I could just ignore your topic in the beginning and maybe nobody would answer it and you'd be on your own with all those comments on other threads without a proper preliminary knowledge.
Click to expand...
Click to collapse
Thank you!
I had successfully flashed Lineage OS 15.1, will be tweaking a bit and decide if I wanna go for another custom rom or flash back to MIUI
CaptainBilly said:
oopsies sorry, I am very new to this and thanks for your really helpful explanation, I will wipe all now that includes dalvik,cache, system and data and internal storage, but what firmware should I flash and how do I know which one do I need? I am going for Linegae os btw.
Thanks once again, if without ur help my phone will essentially be dead :good:
Click to expand...
Click to collapse
you can flash lineageos or MIUI by TWRP,just simply flow the wipe,then flash miui or lineageos ,but if you flash miui,you might go back to mi official recovery instead of TWRP(poor English).
laijirong said:
you can flash lineageos or MIUI by TWRP,just simply flow the wipe,then flash miui or lineageos ,but if you flash miui,you might go back to mi official recovery instead of TWRP(poor English).
Click to expand...
Click to collapse
How do you even get the phone to be recognised to initiate the flash if its stuck in constant boot loop??
Normally your laptop or pc needs to recognise the phone before it can start the flash right?
Shanrom said:
How do you even get the phone to be recognised to initiate the flash if its stuck in constant boot loop??
Normally your laptop or pc needs to recognise the phone before it can start the flash right?
Click to expand...
Click to collapse
vol + and power ,if not you might have it repaired.
Poor English.
Related
So after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root ; i modified the contents so it would fit the moto phone a bit better:, but thnx goes to Ibolito over at the pixel 3 forums
1 ) Download the latest Android factory image for your device ("see this guide on where to find it.
2 ) Extract the "boot.img" file from the downloaded image and copy it to your phone.
Warning! Make absolutely sure the firmware is exactly the same as the installed one. If not, you might loose touch.
Be aware that LMSA will download the latest firmware, even if it is not yet installed. That might break your touchscreen
Click to expand...
Click to collapse
3 ) Download latest Magisk Manager application on your phone and install it :
Link
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched.img
edit: i received a comment that the name might be something like Magisk_patched_somerandomletters_.img since the latest magisk update
5 ) Enable adb debugging on your phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
extra: You could test a single boot with that image by typing "fastboot boot magisk_patched.img"
if it boots fine you should have root for this single boot / magisk would show as installed.
9 ) When it's done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and check if everything is good, and it should be
extra info:
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Edit: rewritten entire post so it would look more like a guide, and extra warning because a lot of people seem to loose touch if they don't have the exact same firmware downloaded as on their phone.
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
testtubebaby said:
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
Click to expand...
Click to collapse
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
pjottrr said:
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
Click to expand...
Click to collapse
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Sorry, no idea, i found the provided link via google,
testtubebaby said:
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
zuggi_m said:
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Click to expand...
Click to collapse
@zuggi_m , how does posting the same url help?
i don't see a retgb here ....
Maybe someone with more dev experience can tell if you need the exact same firmware or if the version numbers are the same it is ok to use that file ?
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
mingkee said:
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
Click to expand...
Click to collapse
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
pjottrr said:
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
Click to expand...
Click to collapse
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
mingkee said:
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
Click to expand...
Click to collapse
maybe i'm missing your point here, my description is just so people who have to figure it out can just use my steps to get root, it is indeed based on fastboot flashing . so i'm not sure what you are trying to say, or am i misinterpreting something?
https://forum.xda-developers.com/motorola-one-hyper/development/rom-omnirom-t4044405
I did root on One Hyper (shipped with Android 10) using fastbootd method
Used old method soft brick my One Hyper
That's why I'd like to know
pjottrr said:
so after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root
you need to download the firmware for our device,
That can be found here;
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETEU/
after that, extract, patch, fastboot install patched version, done.
I did have some issues with the current magisk manager ( from highonandroid, i did find another source, installed version 7.5.1 of the magisk manager from this source
and that one was able to patch the boot.img
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Click to expand...
Click to collapse
There's a head up
US version: Sofia
The rest: Sofiar
I will buy US G Power in May and let's the fun begin
Check out One Hyper general to install Dolby Atmos and it can be toggle on/off.
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
CCivale said:
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
Click to expand...
Click to collapse
So you should know G Stylus ROM is Sofiap.
Be aware the way Android 10 flashing is different.
Download and install the latest ADB in order to access fastbootd (fastboot reboot fastboot) and flash boot, recovery, dtbo, vbmeta, and super
Hmmmm, I will have to read more about fastbootd in your other thread.
I did use the boot.img for the sofiap.
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
hazd said:
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
Click to expand...
Click to collapse
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
pjottrr said:
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
rsdsecure-cloud.motorola.com/download/SOFIA_RETAIL_QPM30.80-51_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
hazd said:
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
Click to expand...
Click to collapse
I downloaded the kernel and waiting for the unit.
I can flash full ROM with fastboot and fastbootd, but just flashing kernel would be much faster.
Moreover, check One Hyper general to get Dolby Atmos because you can turn on and off anytime you want.
I successfully dirty flashed Realme UI V 2.0 over stock android 10 without losing anything and now on Android 11.
Links available in telegram channel for Rm5p.
Anybody can do it...just dont forget to flash vbmeta with disable verity......
SShots
Do you have steps how to do it? I didnt actually get the steps in the telegram.
Kristopher28 said:
Do you have steps how to do it? I didnt actually get the steps in the telegram.
Click to expand...
Click to collapse
Yes, I will post now
Dirty flash Realme UI V 2.0. (Zero risk of losing any data if things are done as mentioned)
Things you will need.
1. A PC to use fastboot command.
Will definitely need adb and fastboot drivers installed. (folder C:/ADB)
2. You need to be on stock firmware V c.14, the latest one.
3. Custom recovery. Orangefox recovery R .11 stable version. (any other recovery latest version might work, just find the keywords mentioned)
Note: You will lose any custom recovery installed after Android 11 installation. (use system recovery and recovery ROM provided in telegram to revert back to A10 )
I am going to use Orangefox recovery as base here.
Download from telegram:
Realme UI 2.0 ozip and vbmeta.img, recovery.img (if you want-I have not installed any recovery as of now)
Download and place the vbmeta.img in your ADB folder.
Reboot phone to recovery and DO NOT WIPE anything.
Inside recovery find the entry called TERMINAL (under MENU), open it and type this first:
--------------------------------------------------------------------------------------------
setprop ro.separate.soft 19691
--------------------------------------------------------------------------------------------
xxxxxx [do not type this line]- just for your infoxxxxxxxxxxxxxxxxxxxxxxxxx
-[setprop(space)ro(dot)separate(dot)soft(space)19691]-----[do not type this line]
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Press enter
Back to ROM installation under FILES browse to UI V2 ozip.
Flash Realme UI 2.0 ozip (4fab98b6-6964-4c1d-9c5c-dcd92064ae14.ozip)
CAUTION - do not press reboot but instead just go back to MENU find option REBOOT and select reboot to BOOTLOADER or fastboot mode.
Now in your PC, press SHIFT + right mouse button on ADB folder and select OPEN COMMAND WINDOW HERE
In the command window type or paste this command
(copy below command from here and in the command window mouse-right-click and select paste) then press enter:
--------------------------------------------------------------------------------------------
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
--------------------------------------------------------------------------------------------
You should see SUCCESS message in your PC command window.
Then reboot your phone by selecting START in orangefox recovery.
I really love UI 2. Everyone should try this----safely.
Ensure your fastboot command works. I had a slight issue with fastboot on windows 7 x64 bit. I had win 7 x86 abd installation folder. Copy pasted the files from there to X64 and problem solved.
I was rooted while in A10 and magisk installed, didnt uninstall it, still had no issues. Just in case if any issue arise, I suggest you uninstall Magisk in A10 and proceed with A11 installation.
jijojamie said:
Dirty flash Realme UI V 2.0. (Zero risk of losing any data if things are done as mentioned)
Things you will need.
1. A PC to use fastboot command.
Will definitely need adb and fastboot drivers installed. (folder C:/ADB)
2. You need to be on stock firmware V c.14, the latest one.
3. Custom recovery. Orangefox recovery R .11 stable version. (any other recovery latest version might work, just find the keywords mentioned)
Note: You will lose any custom recovery installed after Android 11 installation. (use system recovery and recovery ROM provided in telegram to revert back to A10 )
I am going to use Orangefox recovery as base here.
Download from telegram:
Realme UI 2.0 ozip and vbmeta.img, recovery.img (if you want-I have not installed any recovery as of now)
Download and place the vbmeta.img in your ADB folder.
Reboot phone to recovery and DO NOT WIPE anything.
Inside recovery find the entry called TERMINAL (under MENU), open it and type this first:
--------------------------------------------------------------------------------------------
setprop ro.separate.soft 19691
--------------------------------------------------------------------------------------------
xxxxxx [do not type this line]- just for your infoxxxxxxxxxxxxxxxxxxxxxxxxx
-[setprop(space)ro(dot)separate(dot)soft(space)19691]-----[do not type this line]
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Press enter
Back to ROM installation under FILES browse to UI V2 ozip.
Flash Realme UI 2.0 ozip (4fab98b6-6964-4c1d-9c5c-dcd92064ae14.ozip)
CAUTION - do not press reboot but instead just go back to MENU find option REBOOT and select reboot to BOOTLOADER or fastboot mode.
Now in your PC, press SHIFT + right mouse button on ADB folder and select OPEN COMMAND WINDOW HERE
In the command window type or paste this command
(copy below command from here and in the command window mouse-right-click and select paste) then press enter:
--------------------------------------------------------------------------------------------
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
--------------------------------------------------------------------------------------------
You should see SUCCESS message in your PC command window.
Then reboot your phone by selecting START in orangefox recovery.
I really love UI 2. Everyone should try this----safely.
Ensure your fastboot command works. I had a slight issue with fastboot on windows 7 x64 bit. I had win 7 x86 abd installation folder. Copy pasted the files from there to X64 and problem solved.
I was rooted while in A10 and magisk installed, didnt uninstall it, still had no issues. Just in case if any issue arise, I suggest you uninstall Magisk in A10 and proceed with A11 installation.
Click to expand...
Click to collapse
Is your phone rooted?
I have actually found a bug in the rui 2.0 where phone storage can't be read i thought my phone is bricked for good, but instead i installed their rui recovery then i format my phone and it's okay now
Kristopher28 said:
I have actually found a bug in the rui 2.0 where phone storage can't be read i thought my phone is bricked for good, but instead i installed their rui recovery then i format my phone and it's okay now
Click to expand...
Click to collapse
If it was a bug, I would have encountered the same, but no. Except the windows version I used caused fastboot command error once and that too solved within minutes, I had zero errors. I was rooted on A10, but not on A11.
Please elaborate what you encountered. Maybe you did something wrong or else tips that might be helpful for others.
jijojamie said:
If it was a bug, I would have encountered the same, but no. Except the windows version I used caused fastboot command error once and that too solved within minutes, I had zero errors. I was rooted on A10, but not on A11.
Please elaborate what you encountered. Maybe you did something wrong or else tips that might be helpful for others.
Click to expand...
Click to collapse
Well in my case i did a clean wipe to avoid issues flashing the official rom , as you can see in the telegram post I did everything it shows there 1st is wiping in twrp (dalvik, data,system,cache, and vendor) then i installed the c.14 then terminal and so forth but i think there's a wrong part I've done where i dont use the commands in fastboot properly, flashing vbmeta where the disable verification is in. In my case i just flash the vbmeta with "fastboot flash vbmeta vbmeta.img" but after i understand that you have to use a specific commands for the vbmeta i flash it again with the proper codes. Then after that i reboot the phone and it works, but the problem where i dont have a storage is there.
Kristopher28 said:
Well in my case i did a clean wipe to avoid issues flashing the official rom , as you can see in the telegram post I did everything it shows there 1st is wiping in twrp (dalvik, data,system,cache, and vendor) then i installed the c.14 then terminal and so forth but i think there's a wrong part I've done where i dont use the commands in fastboot properly, flashing vbmeta where the disable verification is in. In my case i just flash the vbmeta with "fastboot flash vbmeta vbmeta.img" but after i understand that you have to use a specific commands for the vbmeta i flash it again with the proper codes. Then after that i reboot the phone and it works, but the problem where i dont have a storage is there.View attachment 5347851
Click to expand...
Click to collapse
After i saw the problem i wipe the data by using the rui 2.0 stock recovery then the problem is gone but there's another bug where a specific files cant read by the phone. I dont know if its a bug or i just flashed wrong but it cannot read it. So i decided to go back to the rui 1.0 c.14 patch. And after i got back my files is okay and ready to be use.
I dont know but the early access of 2.0 seems a little bit buggy for me
Kristopher28 said:
" but there's another bug where a specific files cant read by the phone."
Click to expand...
Click to collapse
This is what i didn't understand. You mean to say, after rom installation you got into Ui 2.0 Android 11 and you cannot access your storage inside file manager.
Or else did you mean you got into bootloop.
After custom rom installation we have to do a data format to actually boot into it.
Try doing a factory reset or wipe data.
By the way i am using rm5p Indian variant.
Flashing the vbmeta wrongly or wrong command usage May cause trouble. You may get boot destroyed msg but that can be solved by getting back to FB and installing properly the vbmeta.
jijojamie said:
After custom rom installation we have to do a data format to actually boot into it.
Try doing a factory reset or wipe data.
By the way i am using rm5p Indian variant.
Click to expand...
Click to collapse
Oh i think that's it. Because after i flash the rom and made a mistake in flashing vb meta verification. i didnt wipe the data i just reboot the system and I thought that it worked but as i discovered there's no storage. So after i saw that i flash the rui 2.0 stock recovery then wipe the data.
jijojamie said:
This is what i didn't understand. You mean to say, after rom installation you got into Ui 2.0 Android 11 and you cannot access your storage inside file manager.
Click to expand...
Click to collapse
Yeah after the rom and then the vbmeta error it got worked but as soon as i open the storage there was none. After that i installed the rui 2.0 stock recovery and then wipe the data and then restart. After that the storage seems fine, but a specific files i want to see in my sd card is nowhere to be found. The "android data" specifically.
Kristopher28 said:
Yeah after the rom and then the vbmeta error it got worked but as soon as i open the storage there was none. After that i installed the rui 2.0 stock recovery and then wipe the data and then restart. After that the storage seems fine, but a specific files i want to see in my sd card is nowhere to be found. The "android data" specifically.
Click to expand...
Click to collapse
Now, this is precise. I just tried to access the data folder through es file explorer. Then system asked to grant permission and then system file manager came up. I just granted permission in that and the data folder is listed and visible.
Please be more specific which ROM did you dirty flash?
Its ok I managed to find the telegram group and files. I will try this out on monday after i have made a backup of my phone.
Point number 2. Stock firmware latest.
Cant find the files . Which telegram channel.
Link plz
Hi, as written in the title, I would like to root my phone. I never touch root with xiaomi (the only thing I've done is unlock bootloader)
I usualy root samsung's phone
I want to know if it possible to have my phone rooted with magisk, twrp as custom recovery with android 11
Sorry if my english is bad, sorry if wrong place/category
The best way is to searc already written threat..
Or watch YouTube.
You need to download ADB ,ind ADB folder put oFox or TWRP ,depens what tou want from recovery. in that folder, holding shift+left click open powershell, then type , fastboot flash recovery _name of recovery.img
Fastboot boot name of recovery.img
And that it.
tze_vitamin said:
The best way is to searc already written threat..
Or watch YouTube.
You need to download ADB ,ind ADB folder put oFox or TWRP ,depens what tou want from recovery. in that folder, holding shift+left click open powershell, then type , fastboot flash recovery _name of recovery.img
Fastboot boot name of recovery.img
And that it.
Click to expand...
Click to collapse
Of course I have already searched
If I write here, it is because I did not find some information
Flash twrp, like you say, yes but is twrp for this phone compatible with android 11 or 10 only ?
Most of guide I found say "root ... android 10" or just root without precise the version
That's why I want to be sure
Rooting with Magisk is pretty much always the same, doesn't matter if Samsung or Xiaomi.
1. Download https://androidfilehost.com/?fid=2188818919693773066 (link from https://forum.xda-developers.com/t/...-lite-mi10i-redmi-note-9-pro-5g-beta.4228655/)
2. "fastboot boot twrp_xyz.img" (don't flash custom recovery as internal memory can't be decrypted in TWRP afterwards)
3. install magisk.zip
Works on stock Android 11.
_mysiak_ said:
Rooting with Magisk is pretty much always the same, doesn't matter if Samsung or Xiaomi.
1. Download https://androidfilehost.com/?fid=2188818919693773066 (link from https://forum.xda-developers.com/t/...-lite-mi10i-redmi-note-9-pro-5g-beta.4228655/)
2. "fastboot boot twrp_xyz.img" (don't flash custom recovery as internal memory can't be decrypted in TWRP afterwards)
3. install magisk.zip
Works on stock Android 11.
Click to expand...
Click to collapse
(don't flash custom recovery as internal memory can't be decrypted in TWRP afterwards)
Is it still possible to backup/restore in case of problem ?
No need to reset ?
Xyphoseos said:
(don't flash custom recovery as internal memory can't be decrypted in TWRP afterwards)
Is it still possible to backup/restore in case of problem ?
No need to reset ?
Click to expand...
Click to collapse
Backup most probably yes, I never tried restore so can't confirm. But obviously you will need to "hot boot" TWRP whenever you want to use it, so you must have PC at hand.
_mysiak_ said:
Backup most probably yes, I never tried restore so can't confirm. But obviously you will need to "hot boot" TWRP whenever you want to use it, so you must have PC at hand.
Click to expand...
Click to collapse
Ive read in some guide (that there were not clearly) twrp is flashed, phone reseted and vmbeta disable (or something like that) this make us able to see those crypted data in twrp
Maybe Im wrong
Xyphoseos said:
Ive read in some guide (that there were not clearly) twrp is flashed, phone reseted and vmbeta disable (or something like that) this make us able to see those crypted data in twrp
Maybe Im wrong
Click to expand...
Click to collapse
I don't know about this. I want my phone encrypted, so I boot TWRP after every OTA update to root it again..
_mysiak_ said:
I don't know about this. I want my phone encrypted, so I boot TWRP after every OTA update to root it again..
Click to expand...
Click to collapse
okay, thank you for your help !
Root like this prevent me from ota updates right ?
Xyphoseos said:
okay, thank you for your help !
Root like this prevent me from ota updates right ?
Click to expand...
Click to collapse
For incremental ("small" OTA) update you will need to restore stock images in Magisk.
Full ("big" OTA) update can be installed without any further steps.
In both cases, after a reboot you will have updated system with no root, so you need to reinstall Magisk from TWRP.
What Android you have. I am on A11 and Orangefox working perfect
Hi,
having Android 11
"reboot bootloader" doesn't seem to work on my Sharp.
"reboot sideload" works: is there a version of that "twrp img" that can be sideloaded on Android 11?
( has to be a zip )
petit-lion said:
Hi,
having Android 11
"reboot bootloader" doesn't seem to work on my Sharp.
"reboot sideload" works: is there a version of that "twrp img" that can be sideloaded on Android 11?
( has to be a zip )
Click to expand...
Click to collapse
If "reboot bootloader" is the command line and does not work, do it manually ?
Btw, thank you again @_mysiak_ , everything works like a charm
_mysiak_ said:
Rooting with Magisk is pretty much always the same, doesn't matter if Samsung or Xiaomi.
1. Download https://androidfilehost.com/?fid=2188818919693773066 (link from https://forum.xda-developers.com/t/...-lite-mi10i-redmi-note-9-pro-5g-beta.4228655/)
2. "fastboot boot twrp_xyz.img" (don't flash custom recovery as internal memory can't be decrypted in TWRP afterwards)
3. install magisk.zip
Works on stock Android 11.
Click to expand...
Click to collapse
Xyphoseos said:
If "reboot bootloader" is the command line and does not work, do it manually ?
Click to expand...
Click to collapse
What I mean is "adb reboot bootloader" just reboots, does not go into bootloader.
Manually, the vol-down power goes into "factory reset", there is no other option.
It's a Sharp, and these phones are known not to be very bootloader-tolerant.
Only "adb reboot sideload" works and goes into "sideload" mode, waiting for a ZIP file to be uploaded.
Then, the "sideload" zip must contain a valid signature, and "edify" commands.
That motivated my question:
For Android 11, is there a zip sideloadable of twrp, with a valid signature?
petit-lion said:
What I mean is "adb reboot bootloader" just reboots, does not go into bootloader.
Manually, the vol-down power goes into "factory reset", there is no other option.
It's a Sharp, and these phones are known not to be very bootloader-tolerant.
Only "adb reboot sideload" works and goes into "sideload" mode, waiting for a ZIP file to be uploaded.
Then, the "sideload" zip must contain a valid signature, and "edify" commands.
That motivated my question:
For Android 11, is there a zip sideloadable of twrp, with a valid signature?
Click to expand...
Click to collapse
I dont know, sorry
petit-lion said:
What I mean is "adb reboot bootloader" just reboots, does not go into bootloader.
Manually, the vol-down power goes into "factory reset", there is no other option.
It's a Sharp, and these phones are known not to be very bootloader-tolerant.
Only "adb reboot sideload" works and goes into "sideload" mode, waiting for a ZIP file to be uploaded.
Then, the "sideload" zip must contain a valid signature, and "edify" commands.
That motivated my question:
For Android 11, is there a zip sideloadable of twrp, with a valid signature?
Click to expand...
Click to collapse
Not sure why you discuss Sharp phone in this topic, but nevertheless, "adb sideload" mode is for stock ROM updates/installations. As far as I'm aware, it is not possible to install anything else this way.
_mysiak_ said:
Not sure why you discuss Sharp phone in this topic, but nevertheless, "adb sideload" mode is for stock ROM updates/installations. As far as I'm aware, it is not possible to install anything else this way.
Click to expand...
Click to collapse
Sorry, I saw "root Android 11" and jumped into it.
Desperate to find an access to that damn Sharp.
petit-lion said:
Sorry, I saw "root Android 11" and jumped into it.
Desperate to find an access to that damn Sharp.
Click to expand...
Click to collapse
You will need either unlocked bootloader + device specific custom recovery, or functional exploit which could root the phone. You are most probably out of luck, so buying a phone with good support on XDA might save you some headaches.
_mysiak_ said:
You will need either unlocked bootloader + device specific custom recovery, or functional exploit which could root the phone. You are most probably out of luck, so buying a phone with good support on XDA might save you some headaches.
Click to expand...
Click to collapse
Learned the lesson
But this Sharp Sense 3 was offered to me by a carrier.
It had initially Android 9 Pie on it, and, biiig mistake, let it upgrade itself
(no upgrade until root from now on!)
Anyway, that's an interesting challenge. Had a look at the open-source visible code from Sharp, checked the 'recovery.cpp' part, and tried all the 'reboot' allowed in the code (eg oem-xxx ...).
Saw the "panic" code (Snapdragon 630 has a panic mode), but could not trigger it.
Saw the part from the Google code handling the sideload signature, and this one will be hard to beat!
And, unfortunately the part handling 'bootloader', Sharp cutstomized, is not visible.
To be continued...
I have a mi10t lite with vodafone brand. I would like to have a europe firmware so i can receive the last ota and so on..
is this a way I can do too?
Last night I do have a problem with the custom rom that I have installed, because of the battery problem keeps on dropping, so I decided to go back to the official stock rom which is for global however after flashing the fastboot rom via Miflash Tool, I have a welcome message that says Find Device storage corrupted. Your device is unsafe now. I thought that I just need to activate this to the device admin, after a reboot I tried to check it out if this message if this message will still pop up, and it keeps on popping up. I have flashed the rom again and it keeps on happening.
Things that I have Tried:
So I tried to check for other ways that I could get rid of this but this doesnt work on the terminal via TWRP. "
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now".
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now". How to fix "Find Device storage corrupted. Your device is unsafe now" ? (At your own risk... I'm not responsible for damage or brick) Required : - Be rooted and...
forum.xda-developers.com
".
The one that works:
Things that you needed:
1. Download Mi Flash Tool(https://www.xiaomiflash.com/)
2. Minimal ADB and Fastboot
3. 7zip or BreeZip
4. TWRP A12(
TWRP A12.rar
drive.google.com
) if you are using other MIUI and devices and want to check it this will work then just use your twrp that is recommended for your mui device.
5. Global Rom (https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.6.0.RKHMIXM/)
warning: make sure that you are using the right rom for your device, my device that I am using is a global variant so I need to flash a global version, if you are using other MIUI device and want to check it out just download the miui that works for you must be on a later update of the rom if the latest current rom that you are working on right now didnt work.
Steps to follow.
1. Extract the Rom which you have downloaded using the 7zip or BreeZip, so for me I extracted the version 12.5.6.0 take note that this is not the latest rom but for this to work we need to be in a later update this rom is an android version 11.
2. after extracting the fastboot rom file type TGZ you will notice that the one that you extracted is on a TAR file type, and you need to extract the TAR file type for you to have the folder "alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global_62b4f5d6ca"
3. Using the Mi Flash Tool, just pick the clean all and start the flashing.
4. After flashing the rom set up the phone but do not update it.
5. On your extracted folder for the rom go to the folder that says images and look for 'persist" this is an img file. copy the persist img file and paste it on your Internal memory of your phone.
6. Turn off your phone and go to fastboot by pressing the volume down as well as the power button. You will notice that the fastboot logo is the older version since we are using an older rom.
7. Extract the TWRP A12 and you should have the disc recovery image of it, copy and paste it on your Minimal ADB and Fastboot folder and rename it "recovery".
8. While you are on the Minimal ADB Fastboot folder make sure that your phone is plug in to the usb port on your computer, click the cmd here on the Minimal ADB and Fastboot Folder and you should able to run the cmd.
9. run the following commands:
fastboot devices (then press the enter)
warning: make sure that the fastboot devices is able to see your device.
after seeing the device run this command:
fastboot boot recovery.img (then press enter)
the device should boot to the twrp if its on chinese look for settings and set it to english. we are not flashing the twrp we are just going to use it temporarily thats why we are only going to boot it to twrp recovery.
10. On your twrp, go to install, click the install image and look for your persist.img that we have copied earlier to your internal memory
you should find it on the sdcard folder. just flash and you will see that you have successfully flashed the persist image and then just reboot your phone.
After rebooting your phone you will notice that the "Find Device storage corrupted. Your device is unsafe now." will not prompt. Since I already have the current fastboot rom I have tried to flash the current fastboot rom and locked my device and fixed the problem permanently without any problem.
You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter)
Summary guide:
1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img"
2. Put persist.img into your device's internal memory and go to TWRP
3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition
4. Restart the device, it should work fine
uvzen said:
You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter)
Summary guide:
1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img"
2. Put persist.img into your device's internal memory and go to TWRP
3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition
4. Restart the device, it should work fine
Click to expand...
Click to collapse
Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp.
mizuhored said:
Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp.
Click to expand...
Click to collapse
If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently).
uvzen said:
If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently).
Click to expand...
Click to collapse
Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it.
mizuhored said:
Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it.
Click to expand...
Click to collapse
Could you please confirm if flashing persist.img doesn't mess up with sensor like fingerprint, l1, compass etc..? I have seen other forums talking about possibility of losing these in case perist is flashed from rom. I have this message for some time now, but all other sensors work fine, even l1 certification and saftynet. Thanks in advance.
So I found my old Huawei p9 and want to put Lineage on it. Andy Yan's site give me the xz of the img but how do I get it to the correct zip for TWRP (already loaded)?
SephRobbertse said:
So I found my old Huawei p9 and want to put Lineage on it. Andy Yan's site give me the xz of the img but how do I get it to the correct zip for TWRP (already loaded)?
Click to expand...
Click to collapse
Extract using 7zip, the .img is inside the archive.
Boot to TWRP, connect via USB, and transfer the .img to your device. Then, go to Install > Install images > select /System > select the LineageOS.img and flash.
Keep in mind that if you want to flash a GApps package, you must do it right after flashing /system. You may have to resize the /system partition if you get an error about not having enough space.
V0latyle said:
Extract using 7zip, the .img is inside the archive.
Click to expand...
Click to collapse
Thanks yea I have that. But cant get it installed (ADB or Fastboot).
SephRobbertse said:
Thanks yea I have that. But cant get it installed (ADB or Fastboot).
Click to expand...
Click to collapse
See my edits to the post above.
I'm not familiar with Huawei devices, but if you're able to flash partitions directly from the bootloader, then you'd need to flash the LIneageOS to system: fastboot flash system lineageos.img. You can make this easier by just typing fastboot flash system, leave a space after "system", then just drag and drop the LineageOS .img into the command window.
V0latyle said:
See my edits to the post above.
I'm not familiar with Huawei devices, but if you're able to flash partitions directly from the bootloader, then you'd need to flash the LIneageOS to system: fastboot flash system lineageos.img. You can make this easier by just typing fastboot flash system, leave a space after "system", then just drag and drop the LineageOS .img into the command window.
Click to expand...
Click to collapse
Many thanks.