Develop Bugs

Xiaomi 6 problem!

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.

Bricked my phone, please help

I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l

jetzecazemier said:
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
Click to expand...
Click to collapse
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?

mrmazak said:
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
Click to expand...
Click to collapse
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error) I am frp unlocked by the way.

jetzecazemier said:
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error)
Click to expand...
Click to collapse
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447

mrmazak said:
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
Click to expand...
Click to collapse
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917

jetzecazemier said:
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
Click to expand...
Click to collapse
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.

mrmazak said:
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
Click to expand...
Click to collapse
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?

jetzecazemier said:
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
Click to expand...
Click to collapse
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.

mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
Alright, I'll try that before I have a look at that thread

mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?

jetzecazemier said:
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
Click to expand...
Click to collapse
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip

mrmazak said:
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
Click to expand...
Click to collapse
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?

jetzecazemier said:
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
Click to expand...
Click to collapse
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder

mrmazak said:
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
Click to expand...
Click to collapse
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.

jetzecazemier said:
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
Click to expand...
Click to collapse
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer

mrmazak said:
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
Click to expand...
Click to collapse
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.

jetzecazemier said:
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
Click to expand...
Click to collapse
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar

mrmazak said:
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
Click to expand...
Click to collapse
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?

jetzecazemier said:
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
Click to expand...
Click to collapse
Yes.
The lazy tool has recovery with encryption working

I got it working on EMUI8 but I decided to flash the aosp rom cuz i prefer stock android. Can't seem to get twrp to install tho. I keep getting "1 was unexpected at this time"

[SOLVED] Trying to get stock recovery back

Hi, I flashed TWRP to be able to install magisk on my friend's Honor 7x (BND-L21 C432) and now that magisk is flashed and configured I want to go back to the stock recovery. I've downloaded the update.zip with the Firmware Finder app, and I've extracted the recovery_ramdisk.img from the UPDATE.APP file.
But once flashed (with fastboot) I can't access it, it gives me ERROR MODE, like if the img was invalid.
Any help?
Thanks!

Did you download and flashed the correct build file? Which recovery you flashed?

shashank1320 said:
Did you download and flashed the correct build file? Which recovery you flashed?
Click to expand...
Click to collapse
I was using correct version, but I wasn't using HuaweiUpdateExtractor. After using it to get the img it worked well.
Thanks!

eXtremeDevil said:
Hi, I flashed TWRP to be able to install magisk on my friend's Honor 7x (BND-L21 C432) and now that magisk is flashed and configured I want to go back to the stock recovery. I've downloaded the update.zip with the Firmware Finder app, and I've extracted the recovery_ramdisk.img from the UPDATE.APP file.
But once flashed (with fastboot) I can't access it, it gives me ERROR MODE, like if the img was invalid.
Any help?
Thanks!
Click to expand...
Click to collapse
this install zip, should restore the recovery-from-boot.p file, the file that causes stock recovery to be replaced. I have not confirmed on this device but it is a generic solution that should work.

mrmazak said:
this install zip, should restore the recovery-from-boot.p file, the file that causes stock recovery to be replaced. I have not confirmed on this device but it is a generic solution that should work.
Click to expand...
Click to collapse
Thanks anyway, I was able to *correctly* extract the img file
What does that file exactly? Is there a backup of the recovery on the phone?? I assuming we're talking about normal recovery, not the second eRecovery thing, right?

eXtremeDevil said:
Thanks anyway, I was able to *correctly* extract the img file
What does that file exactly? Is there a backup of the recovery on the phone?? I assuming we're talking about normal recovery, not the second eRecovery thing, right?
Click to expand...
Click to collapse
Stock Android has a feature to make a recovery image from the boot.img. By checking the contents of the recovery partition and comparing a checksum. When the sum does not match, the file "recovery_from_boot.p" takes over and builds it's own recovery image.
When you install twrp and "swipe to allow system modification" that file gets renamed to end with ".bak"
This zip file verifies the recovery script is on the phone e, and if it is, it will remove the .bak extension . That makes the system .restore (make) stock recovery on the next boot up

Thanks for the info!

rooting ( after unlocking bootloader)

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.

Question Find Device storage corrupted. Your device is unsafe now.( POCO F3 and Other MIUI Devices)

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.