[SOLVED] Trying to get stock recovery back - Honor 7X Questions & Answers

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!

Related

[HOW-TO] HUAWEI NOVA-PLUS root with MAGISK

Yes,its working...
REMOVE ALL OTHER ROOT...working or not befor installing magisk....may end with....something you dont want...
Maybe it would be best to start with a freshly factory resetted phone.... (anyway,to erase all errors in TWRP,youll format/data so... )
you need bootloader unlock... followed instructions HERE don't forget to OEM UNLOCK in /settings/Developer section on phone..(enable it while pressing repeatedly on Phone version (in ''about phone also in settings)
You need MINIMAL ADB on pc...HERE
You need TWRP recovery installed...HERE
but before doing all that...BE SHURE to have the original UPDATE.APP (firmware from huawei) somewhere on your pc
you will need the BOOT.img from your original firmware... (extract it from the update.app (update.zip for huawei firmware)
HERE
extract the boot.img somewhere on your pc... like on your desktop...
then,youll need 2 magisk things...
the LATEST magisk ZIP file...
and the LATEST MAGISK APK...
FOLLOW THESE INSTRUCTIONS (from Magisk post...i did it and its working :silly: )
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager
For installing Magisk the first time
Make sure to remove any other root, best to restore your boot image back to stock
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
the ADB method is the best...
after reboot,in magisk app,youre supposed to be GREEN checked....
after that,if all green,you can FIX that DATA problem in TWRP...saying cant mount or blablabla...
DO a backup cuz yess,youll loose everything... Hisuite for your apps
in twrp, FORMAT DATA... ...wipe data factory reset...re install your things then,youll be able to do recoverys ect. in twrp
dont forget to RE INSTALL magisk APK after formatting and factory reset
IT WILL take some time TO BOOT... so let it do its thing...
Now about magisk modules...all of them ive tried ended in (blablabla not a magisk module)...
no big deal....just dload the zip and look for the app or file in it... and apply to where it belongs... like new Oreo Emojis...ive dloaded the zip,found the file, then paste the file in /system/fonts...then reboot
now...if i made a mistake somewhere in my explanations well... sorry....
WARNING
IF youre device is bricked or what so ever... its not MY fault....you do that on your own......Ive done it,followed MAGISK instructions and its working....
Not shure about it...DONT DO IT....
DON'T DO TWRP backups with fingerprints/nip/code unlock methods activated on your phone... i had to factory reset phone cuz code was not working.
YES there's a way to recover anyway... THANKS HENKATE
Regarding fingerprint, boot in recovery and go to advanced > file manager and delete data/system/locksettings.db
Then advanced > terminal and type:
cd data/system
rm -rf *.key
Then reboot and you won't have secured lockscreen
MAGISK modules are HERE
Magisk MANAGER is available on PLAYSTORE
BEFORE making a twrp backup... (after data format ect.)...
you may want to FIX the huawei theme manager not working problem for some of us... the FIX is HERE
Thanks to Henkate
Youll need a good file system manager...i'm using ROOT EXPLORER and theres that new FX file explorer
does it work with android 7?
tanlikar1 said:
does it work with android 7?
Click to expand...
Click to collapse
Yes. In fact, this was meant for Android 7, but it should work on Android 6 too.
Absolutely...Im on Nougat emui5
does anyone have stock rom for MLA-L12C636B340 ?
Do you mean original firmware ?
Maybe you can still get it via firmware finder...
virusdunil said:
Do you mean original firmware ?
Maybe you can still get it via firmware finder...
Click to expand...
Click to collapse
ya
Working on Nova?
Does it work in the non plus Nova as well? Any experiences?
Worked on Can-L11. Tested. No need format data, in twrp tree, i add img, that work with encrypted data.
I can't get this to work on my MLA-03, i have TWRP installed and unlocked b/l. I tried to flash RR and Lineage but getting "can't mount" errors up the ying yang. Anyone with MLA-03 got any tips? Is there a certain recovery that is recommended?
Cooks_08 said:
I can't get this to work on my MLA-03, i have TWRP installed and unlocked b/l. I tried to flash RR and Lineage but getting "can't mount" errors up the ying yang. Anyone with MLA-03 got any tips? Is there a certain recovery that is recommended?
Click to expand...
Click to collapse
hi...yes and its a bit confusing...but,just follow instructions for LOS install...forget about /mount data and after flashing ,just reboot
virusdunil said:
hi...yes and its a bit confusing...but,just follow instructions for LOS install...forget about /mount data and after flashing ,just reboot
Click to expand...
Click to collapse
Got the flash working. Used Garak's Twrp and now i got. Thanks.
Does it work for android 8.0 or Huawei nova 2s in particular? I did make unlock the bootloader, but i could not find reliable root method. Please help with advice. Thank you.
Mezo21 said:
Does it work for android 8.0 or Huawei nova 2s in particular? I did make unlock the bootloader, but i could not find reliable root method. Please help with advice. Thank you.
Click to expand...
Click to collapse
Hi there,
I have Nova 2s, carefully follow this thread's instructions, it will 100% works : https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
Thanks for the guidance, Magisk is doing very well.
Only TWRP is missing, but later.
Huawei Nova
CAN-L01C432B382
Magisk modules not working even if i rooted. Cant install modules from magisk app and twrp .zip
meskafonas said:
Magisk modules not working even if i rooted. Cant install modules from magisk app and twrp .zip
Click to expand...
Click to collapse
did you format data as f2fs? If yes, magisk doesn't go well along with it. If no, then you would get better support at magisk thread
virusdunil said:
Yes,its working...
REMOVE ALL OTHER ROOT...working or not befor installing magisk....may end with....something you dont want...
Maybe it would be best to start with a freshly factory resetted phone.... (anyway,to erase all errors in TWRP,youll format/data so... )
you need bootloader unlock... followed instructions HERE don't forget to OEM UNLOCK in /settings/Developer section on phone..(enable it while pressing repeatedly on Phone version (in ''about phone also in settings)
You need MINIMAL ADB on pc...HERE
You need TWRP recovery installed...HERE
but before doing all that...BE SHURE to have the original UPDATE.APP (firmware from huawei) somewhere on your pc
you will need the BOOT.img from your original firmware... (extract it from the update.app (update.zip for huawei firmware)
HERE
extract the boot.img somewhere on your pc... like on your desktop...
then,youll need 2 magisk things...
the LATEST magisk ZIP file...
and the LATEST MAGISK APK...
FOLLOW THESE INSTRUCTIONS (from Magisk post...i did it and its working :silly: )
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager
For installing Magisk the first time
Make sure to remove any other root, best to restore your boot image back to stock
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
the ADB method is the best...
after reboot,in magisk app,youre supposed to be GREEN checked....
after that,if all green,you can FIX that DATA problem in TWRP...saying cant mount or blablabla...
DO a backup cuz yess,youll loose everything... Hisuite for your apps
in twrp, FORMAT DATA... ...wipe data factory reset...re install your things then,youll be able to do recoverys ect. in twrp
dont forget to RE INSTALL magisk APK after formatting and factory reset
IT WILL take some time TO BOOT... so let it do its thing...
Now about magisk modules...all of them ive tried ended in (blablabla not a magisk module)...
no big deal....just dload the zip and look for the app or file in it... and apply to where it belongs... like new Oreo Emojis...ive dloaded the zip,found the file, then paste the file in /system/fonts...then reboot
now...if i made a mistake somewhere in my explanations well... sorry....
WARNING
IF youre device is bricked or what so ever... its not MY fault....you do that on your own......Ive done it,followed MAGISK instructions and its working....
Not shure about it...DONT DO IT....
DON'T DO TWRP backups with fingerprints/nip/code unlock methods activated on your phone... i had to factory reset phone cuz code was not working.
YES there's a way to recover anyway... THANKS HENKATE
Regarding fingerprint, boot in recovery and go to advanced > file manager and delete data/system/locksettings.db
Then advanced > terminal and type:
cd data/system
rm -rf *.key
Then reboot and you won't have secured lockscreen
Click to expand...
Click to collapse
Do you have this problem with fingerprint? [emoji853] https://r.tapatalk.com/shareLink?ur...share_tid=3907398&share_fid=3793&share_type=t
Enviado desde mi HUAWEI CAN-L11 mediante Tapatalk

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"

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.

Softbricked Mi10t Lite (gauguin)

Hello guys,
I have rooted 2 days ago my phone with TWRP and Magisk; everything worked fine until I tried to change somethin in /system/ folder. It always said I dont have write rights. So I decided to go back to stock rom. I have downloaded the stock rom for my phone (gauguin, Global 12.0.8.0 , Android 10.) Now I have the following problem. My device is soft bricked.
So i decided to google and try to flash another Rom for my phone. I found one here.
https://xiaomirom.com/en/rom/mi-10t-lite-gauguin-global-fastboot-recovery-rom/
How Can I flash that file? its .tgz
I have stock rom installed and I cant flash TWRP
Thanks in advance
Francesco
here is what comes when I try to flash. It fails aftter Flashing super :
error hosted at ImgBB
Image error hosted in ImgBB
ibb.co
Francescohub said:
here is what comes when I try to flash. It fails aftter Flashing super :
Click to expand...
Click to collapse
Unpack TGZ archive, then untar TAR file again. You will see folder with images and script files. Run "flash_all_except_storage.bat".
Francescohub said:
here is what comes when I try to flash. It fails aftter Flashing super :
error hosted at ImgBB
Image error hosted in ImgBB
ibb.co
Click to expand...
Click to collapse
Get it too work ?
_mysiak_ said:
Unpack TGZ archive, then untar TAR file again. You will see folder with images and script files. Run "flash_all_except_storage.bat".
Click to expand...
Click to collapse
For the love of god, I just spent 3 hours to install fastboot ROM and did not succeed. No idea what went wrong, but at the end I finally restored my device..
1. download recovery ROM and transfer it to internal SD
2. download fastboot ROM, unpack it
3. modify flash_all_except_storage.bat and delete lines with CRCLIST and SPARCECRCLIST
4. run the script
5. phone will keep rebooting on MI logo
6. boot to TWRP "fastboot boot twrp.img"
7. install recovery ROM from TWRP
8. (install Magisk), reboot phone to system
For some reason fastboot flashing doesn't install /odm partition correctly. I have the latest drivers, android tools, tried 2 PCs, 2 different USB cables, different USB ports, using Mi Flash, nothing helped. The only solution was to flash recovery rom from TWRP. Fortunately no data has been lost.
Francescohub said:
Hello guys,
I have rooted 2 days ago my phone with TWRP and Magisk; everything worked fine until I tried to change somethin in /system/ folder. It always said I dont have write rights. So I decided to go back to stock rom. I have downloaded the stock rom for my phone (gauguin, Global 12.0.8.0 , Android 10.) Now I have the following problem. My device is soft bricked.
So i decided to google and try to flash another Rom for my phone. I found one here.
https://xiaomirom.com/en/rom/mi-10t-lite-gauguin-global-fastboot-recovery-rom/
How Can I flash that file? its .tgz
I have stock rom installed and I cant flash TWRP
Thanks in advance
Francesco
Click to expand...
Click to collapse
Can you boot into fastboot? You said it's soft bricked so I imagine you can. Reply and I'll get back to you, I soft bricked mine and fixed it fine.
Hey guys, I was finally able to flash the Rom.
I used to flash a Rom with Xiaomi Flash, accidentaly it was a wrong rom, which I saw later on.
So I installed TWRP recovery with fastboot commands and downloaded the right rom. I used to download the EEA Rom instead of Global Rom. So I transfered the EU Rom to micro SD Card and flashed it with TWRP.
Everything is working now, except the access to /system folder, after I rooted with magisk 20.4. Even with the newest Version it does not work.
So I tried in the terminal the following command while I was in /system folder: mount -o rw,remount/ But this does also not work. How can I get acess to it?
Sorry for my english again
Francescohub said:
Hey guys, I was finally able to flash the Rom.
I used to flash a Rom with Xiaomi Flash, accidentaly it was a wrong rom, which I saw later on.
So I installed TWRP recovery with fastboot commands and downloaded the right rom. I used to download the EEA Rom instead of Global Rom. So I transfered the EU Rom to micro SD Card and flashed it with TWRP.
Everything is working now, except the access to /system folder, after I rooted with magisk 20.4. Even with the newest Version it does not work.
So I tried in the terminal the following command while I was in /system folder: mount -o rw,remount/ But this does also not work. How can I get acess to it?
Sorry for my english again
Click to expand...
Click to collapse
Think you storage is corrupted what I did was download the ROM for my phone open the tar ROM to you see a file says images flash all and other stuff play rom folder in mi flash tool folders and open CMD use flash all in ROM folder
Make sure your phone is in fastboot before you use the flash all file it will return your phone to stock ROM

Question A32 4G root and twrp

Hi forum readers,
I think about buying an A32 4G (SM-A325FZKGEUB). In two threads here it was mentioned that rooting was successful. But how about twrp? I found an article on unofficialtwrp.com with description and download of an unofficial twrp and vbmeta.img with another tool for also unencrypting the data partition.
1) With all previous phones I only used xda stuff. What do you think, is it safe to use unofficial twrp?
2) If that twrp fails, I think it is possible to get the original recovery back using Odin. Correct?
3) Is it safe to use the vbmeta.inf and tool to unencrypt the data? I don't need Knox and also not Safety Net. Would it be possible to revert to factory status using Odin?
4) Ist necessary to unlock the bootloader for only flashing the Magisk-patched boot image? How about encrypted data?
Many Greetings
Florian
To root you need bootloader unlocked, if it isn't your phone will fail to flash and it will boot on EDM. If twrp fails you can always flash a .tar as AP containing only recovery.img
@ZModder, thank you for your hint. I was already successfully unlocking and installing Magisk 23. Because of your hint I dared to flash TWRP from the above mentioned web site. It didn't boot. But I could successfully return to original recovery. So waiting for a real device specific TWRP.
fbalder18 said:
@ZModder, thank you for your hint. I was already successfully unlocking and installing Magisk 23. Because of your hint I dared to flash TWRP from the above mentioned web site. It didn't boot. But I could successfully return to original recovery. So waiting for a real device specific TWRP.
Click to expand...
Click to collapse
how did you install Magisk? could you tell?
kkintr0 said:
how did you install Magisk? could you tell?
Click to expand...
Click to collapse
1st: Download appropriate firmware for your region and version of Samsung.
2nd: Unlock your bootloader. This will wipe your data.
3rd. Download magisk manager from github.
4th. Open Magisk and check what Ramdisk says.
4th: Extract your downloader firmware. There should be AP.... File. Open it via 7zip. Inside there you should have boot.img.lz4. Extract that file. If Ramdisk Says NO. Do the same with recovery file.
5th: Zip your boot file to tar format and place it on your phone.
6th: Open Magisk. and Press first Install Button.
7th: Press Select and Patch File. Magisk should create a new file inside Downloads folder. Called magisk..patched...etc Insert that file inside your pc. Do the same with recovery file if needed.
8th. Get into Download mode. You can do this by first turning off your phone and pressing both volume keys as you insert your usb cable.
9th: Open Odin File. If you have recovery file uncheck autoreboot. Place your patched file inside AP section.
10th: Reboot your phone and wipe your data.
11th: Volia!

Categories

Resources