How is Huawei handling root? Is it suspected to work or will this be a problem?
I guess the rooting process may be a bit similar to the Mate 20s. It took a while before root became available for Mate and the process relies on a somewhat compilicated procedure involving FunkeyHuawei and buying credits. If you really want to have root then probably better to wait or to buy a phone which is easier to root.
Hi,
Somewhat agree. Root might take time.
What I can confirm is that oem unlock is not greyed out.
P30 Pro dev options https://imgur.com/a/unJy0ZX
So do you think that someone will cook TWRP and magisk?
I already extracted the ram disk and tried patching it with Magisk.
It didn't boot.
Any other bright ideas?
JazonX said:
I already extracted the ram disk and tried patching it with Magisk.
It didn't boot.
Any other bright ideas?
Click to expand...
Click to collapse
Hope that someone will find a solution, maybe on chinese forums. I can't buy a non-rootable phone.
JazonX said:
I already extracted the ram disk and tried patching it with Magisk.
It didn't boot.
Any other bright ideas?
Click to expand...
Click to collapse
Is not ramdisk that you need to patch, try patch stock Recovery, at least works with EMUI 9.
kilroystyx said:
Is not ramdisk that you need to patch, try patch stock Recovery, at least works with EMUI 9.
Click to expand...
Click to collapse
Yeah, It was called Ramdisk_recovery
That's the one, isn't it?
JazonX said:
Yeah, It was called Ramdisk_recovery
That's the one, isn't it?
Click to expand...
Click to collapse
Is "RECOVERY_RAMDIS.img", in the tool is missing the "K". You can rename it to "RECOVERY_RAMDISK.img"
If you need to flash in the fastboot use this command:
fastboot flash recovery_ramdisk recovery_ramdisk.img
My p30 pro arrive today and i thought i can root it with this tutorial
https://myphoneupdate.com/root-huawei-p30-pro-unlock-bootloader-install-twrp-recovery/
And now i read here that its not possible? That is very Bad if this is so :/
Sorry for Bad English
Edit: oh... Yes now i See no Service sells this Codes at the Moment..
kilroystyx said:
Is "RECOVERY_RAMDIS.img", in the tool is missing the "K". You can rename it to "RECOVERY_RAMDISK.img"
If you need to flash in the fastboot use this command:
fastboot flash recovery_ramdisk recovery_ramdisk.img
Click to expand...
Click to collapse
Yeah, I figured it. Output was patched_boot img. It flashed without any issues. But couldn't reboot afterwards. Went into bootloop, and then back to eRecovery. Normal boot is fine. Patched boot didn't work.
JazonX said:
Yeah, I figured it. Output was patched_boot img. It flashed without any issues. But couldn't reboot afterwards. Went into bootloop, and then back to eRecovery. Normal boot is fine. Patched boot didn't work.
Click to expand...
Click to collapse
:crying::crying::crying:
JazonX said:
Yeah, I figured it. Output was patched_boot img. It flashed without any issues. But couldn't reboot afterwards. Went into bootloop, and then back to eRecovery. Normal boot is fine. Patched boot didn't work.
Click to expand...
Click to collapse
Unfortunately this means that Magisk is not ready to patch EMUI9.1
Has anyone tried the process ?
I might be doing it wrong, Please give it a try from your end as well!
JazonX said:
Has anyone tried the process ?
I might be doing it wrong, Please give it a try from your end as well!
Click to expand...
Click to collapse
Can you upload your stock img RECOVERY_RAMDISK?
I'll patch for you and then if the CRC/SHA is different you can try mine.
kilroystyx said:
Can you upload your stock img RECOVERY_RAMDISK?
I'll patch for you and then if the CRC/SHA is different you can try mine.
Click to expand...
Click to collapse
I have uploaded it here.
JazonX said:
I have uploaded it here.
Click to expand...
Click to collapse
Patched by me is different from yours.
Link:
https://mega.nz/#!ZZgHgapa!NO5_2VxavqN7v9RNwTlxjNTmKR40rOyWIW6k18LRJ-w
You can check the MD5, first is one that you patched and second is the one patched by me
Enclosed you can find the Magisk version used by my.
Check mine and let me know if it works.
kilroystyx said:
Patched by me is different from yours.
Link:
https://mega.nz/#!ZZgHgapa!NO5_2VxavqN7v9RNwTlxjNTmKR40rOyWIW6k18LRJ-w
You can check the MD5, first is one that you patched and second is the one patched by me
Enclosed you can find the Magisk version used by my.
Check mine and let me know if it works.
Click to expand...
Click to collapse
How to flash? Don't we need to unlock the bootloader first, if so I have to buy a unlock code right? I'm om 0.124
Puksom said:
How to flash? Don't we need to unlock the bootloader first, if so I have to buy a unlock code right? I'm om 0.124
Click to expand...
Click to collapse
Yes, to flash you need bootloader unlocked.
Don't waste your money yet, let's first JazonX test the recovery_ramdisk.img patched by me.
JazonX, have you tried? I hope it works
Related
I need the stock recovery image (from 23.16.3.victara_retca.retca.en.CA) so I can flash the 6.0 update since it won't work with TWRP.
Any help? Google isn't providing me with much.
Does it have to be from the Canadian variant (not sure if the recovery images are different between variants)?
Tried looking here for the correct zip, which should contain the recovery image?
ellisbodds said:
Does it have to be from the Canadian variant (not sure if the recovery images are different between variants)?
Tried looking here for the correct zip, which should contain the recovery image?
Click to expand...
Click to collapse
I have no clue. I doubt it would have to be the retCA version. I'm sure everything besides radio and system will be the same.
This is from the latest RETCA XT1097 5.1 firmware:
VICTARA_RETCA_XT1097_5.1_LPE23.32-48.3_cid14_CFC.xml.zip
ellisbodds said:
Does it have to be from the Canadian variant (not sure if the recovery images are different between variants)?
Tried looking here for the correct zip, which should contain the recovery image?
Click to expand...
Click to collapse
Gus.Ottawa said:
This is from the latest RETCA XT1097 5.1 firmware:
VICTARA_RETCA_XT1097_5.1_LPE23.32-48.3_cid14_CFC.xml.zip
Click to expand...
Click to collapse
Thank you both! I'll play around with these files and make it work
DonDizzurp said:
Thank you both! I'll play around with these files and make it work
Click to expand...
Click to collapse
Any update on whether this worked for you? I'm in the same boat
jullyfush said:
Any update on whether this worked for you? I'm in the same boat
Click to expand...
Click to collapse
Worked perfectly.
My process
- Flash stock 5.1 using fastboot (Steps can be found on Motorola's site or somewhere on XDA)
- Install Marshmallow OTA
- Flash cracked boot.img for Marshmallow. This step is needed in order for TWRP to stick and for you to root without getting stuck on the warning screen. (I'll find the link for you if you can't. It's somewhere on XDA.)
- Flash TWRP
- Create backup so I don't have to go through this process next time haha
DonDizzurp said:
Worked perfectly.
My process
- Flash stock 5.1 using fastboot (Steps can be found on Motorola's site or somewhere on XDA)
- Install Marshmallow OTA
- Flash cracked boot.img for Marshmallow. This step is needed in order for TWRP to stick and for you to root without getting stuck on the warning screen. (I'll find the link for you if you can't. It's somewhere on XDA.)
- Flash TWRP
- Create backup so I don't have to go through this process next time haha
Click to expand...
Click to collapse
Awesome! Thanks for the tip. I got as far as the 6.0 OTA (RETCA), and am now trying to get root back again. Where did you find the cracked boot.img?
Cheers!
jullyfush said:
Awesome! Thanks for the tip. I got as far as the 6.0 OTA (RETCA), and am now trying to get root back again. Where did you find the cracked boot.img?
Cheers!
Click to expand...
Click to collapse
Grab it from here
http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
DonDizzurp said:
Grab it from here
http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Click to expand...
Click to collapse
Something odd has happened since upgrading to 6.0.
'adb devices' still sees my phone, but 'fastboot devices' no longer sees anything, and making a desktop back-up with adb now creates a file containing 0 bytes.
Everything else seems fine. Are there some new permissions I need to give before this will work?
Thanks again.
Edit: I managed to get fastboot working, however now I've run into a new problem.
To confirm, when you say flash the cracked boot.img for Marshmallow, I should execute 'fastboot flash boot boot.img' for the cracked boot.img?
I'm getting the error: mismatched partition size (boot)
I can still enter TWRP with fastboot, but it's not permanent without the cracked boot.img
Am I missing a step?
Edit #2: Finally got TWRP to stick another way and have root now. Thanks for everything!
Hello everyone.
Unfortunately my lg g4 bootlooped. And after extensive Google search, i see that most models have a tot file which disables big cores so u can run the phone on the small cores
Does the T-Mobile variant have such a tot file? if yes then can somebody give me the link? if no then can somebody create one using the following info?
Agimax said:
Why not just edit the files below for the two large cores (if you have root):
/sys/devices/system/cpu/cpu4/online (open file and change from a one to a zero)
/sys/devices/system/cpu/cpu5/online (open file and change from a one to a zero)
You could also just have the startup file do it (can modify the ripped system partition & put back on phone):
etc/dir/init.qcom.post_boot.sh (find your processor code - 8992 and add echo lines there with the rest of the cpu commands)
Click to expand...
Click to collapse
Please I'd be highly thankful if someone can help
XeniX_Force said:
Hello everyone.
Unfortunately my lg g4 bootlooped. And after extensive Google search, i see that most models have a tot file which disables big cores so u can run the phone on the small cores
Does the T-Mobile variant have such a tot file? if yes then can somebody give me the link? if no then can somebody create one using the following info?
Please I'd be highly thankful if someone can help
Click to expand...
Click to collapse
no such thing for any american variant
raptorddd said:
no such thing for any american variant
Click to expand...
Click to collapse
Cant someone with a working G4 crate one? i quoted a person who has given the way how to...
XeniX_Force said:
Cant someone with a working G4 crate one? i quoted a person who has given the way how to...
Click to expand...
Click to collapse
not sure . i cant...
sort of read this quickly does this help.? https://www.xda-developers.com/nexus-6p-bootloop-fix/
raptorddd said:
not sure . i cant...
sort of read this quickly does this help.? https://www.xda-developers.com/nexus-6p-bootloop-fix/
Click to expand...
Click to collapse
Well he also created modified boot images which disable the big cores. Can't someone create that for our device?
maybe @steadfasterX can
XeniX_Force said:
Well he also created modified boot images which disable the big cores. Can't someone create that for our device?
maybe @steadfasterX can
Click to expand...
Click to collapse
TWRP installed?
Then u could just modify the init file but I believe its too late. once bootlooping the run is over afaik.
.
steadfasterX said:
TWRP installed?
Then u could just modify the init file but I believe its too late. once bootlooping the run is over afaik.
.
Click to expand...
Click to collapse
yeah I'm bootlooped
Someone also fixed the Nexus 6 bootloop by creating modified images which disable the big cores.
Can't we(mostly you, you're the big dev) create a similar modified image that we can flash through LGUP?
XeniX_Force said:
yeah I'm bootlooped
Someone also fixed the Nexus 6 bootloop by creating modified images which disable the big cores.
Can't we(mostly you, you're the big dev) create a similar modified image that we can flash through LGUP?
Click to expand...
Click to collapse
you may have overseen it but I asked: TWRP installed?
and new question: bootloader unlocked?
I can't create TOT files
.
steadfasterX said:
you may have overseen it but I asked: TWRP installed?
and new question: bootloader unlocked?
I can't create TOT files
.
Click to expand...
Click to collapse
I'm bootlooped. can't reach anything except download mode
and yeah bootloader was unlocked.
oh you can't create tot files? aren't they just system images?
XeniX_Force said:
I'm bootlooped. can't reach anything except download mode
and yeah bootloader was unlocked.
oh you can't create tot files? aren't they just system images?
Click to expand...
Click to collapse
Afaik you need a box to create tot files.
Besides this I have never created any big core disabling but I know @the_naxhoo has.
if you can reach the download mode you could flash with the lglaf shell a modified boot image which is doing the job. If you do not have Linux get your copy of FWUL which has everything on board (like the lglaf shell).
The modded boot image has to disable the cores either by the cmdline or the sys echo or both. I saw that cmdline thing during my unlock attempts and think those are much better then the echo to sys..
Creating a kdz would be maybe possible
creating a TWRP zip for sure but I'm very very busy at the moment...
So just one more time (as still not answered.. ) do you had TWRP installed before the bootloop occurs?
...and If so what happens when you try to get into it?
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Afaik you need a box to create tot files.
Besides this I have never created any big core disabling but I know @the_naxhoo has.
if you can reach the download mode you could flash with the lglaf shell a modified boot image which is doing the job. If you do not have Linux get your copy of FWUL which has everything on board (like the lglaf shell).
The modded boot image has to disable the cores either by the cmdline or the sys echo or both. I saw that cmdline thing during my unlock attempts and think those are much better then the echo to sys..
Creating a kdz would be maybe possible
creating a TWRP zip for sure but I'm very very busy at the moment...
So just one more time (as still not answered.. ) do you had TWRP installed before the bootloop occurs?
...and If so what happens when you try to get into it?
.
Click to expand...
Click to collapse
i had twrp but now when i try to access twrp i get to wipe everything screen which then hangs when I choose yes
yeah I can get FWUL but i need steps to know what to do....
I even asked @XCnathan32 who just fixed the Nexus 6p bootloop to have a look into our device maybe he can benefit from this information u just posted.
XeniX_Force said:
i had twrp but now when i try to access twrp i get to wipe everything screen which then hangs when I choose yes
yeah I can get FWUL but i need steps to know what to do....
I even asked @XCnathan32 who just fixed the Nexus 6p bootloop to have a look into our device maybe he can benefit from this information u just posted.
Click to expand...
Click to collapse
Cmdline is how I disabled the cores on the Nexus, the fix is easy to do on a boot.img, but LG uses the KDZ files, which use a totally different file structure, and I'm not sure if the LG flash tool has file checks, even on unlocked bootloaders. I will do some research and see what I can do. If anyone has any knowledge on modifying kdz files, please tell me.
XCnathan32 said:
Cmdline is how I disabled the cores on the Nexus, the fix is easy to do on a boot.img, but LG uses the KDZ files, which use a totally different file structure, and I'm not sure if the LG flash tool has file checks, even on unlocked bootloaders. I will do some research and see what I can do. If anyone has any knowledge on modifying kdz files, please tell me.
Click to expand...
Click to collapse
asked steadfasterx about kdz and his reply is as follows
steadfasterX said:
me too. never created KDZs yet but there are tools for it - afaik.
My first approach would have been to flash the boot image in the download mode with the lglaf shell (https://github.com/steadfasterX/lglaf/tree/g4) .
requires to do a flash of a modified boot image with dd on /dev/block/mmcblk0 with the correct seek ..
.
Click to expand...
Click to collapse
XCnathan32 said:
Cmdline is how I disabled the cores on the Nexus, the fix is easy to do on a boot.img, but LG uses the KDZ files, which use a totally different file structure, and I'm not sure if the LG flash tool has file checks, even on unlocked bootloaders. I will do some research and see what I can do. If anyone has any knowledge on modifying kdz files, please tell me.
Click to expand...
Click to collapse
you may take a look on this: https://forum.xda-developers.com/showthread.php?t=2179431
not sure if that works though.. (quite old)
.
steadfasterX said:
you may take a look on this: https://forum.xda-developers.com/showthread.php?t=2179431
not sure if that works though..
.
Click to expand...
Click to collapse
But cant we just create a modified boot img and twrp img and flash through lglaf. then flash a rom zip though twrp?
XeniX_Force said:
But cant we just create a modified boot img and twrp img and flash through lglaf. then flash a rom zip though twrp?
Click to expand...
Click to collapse
sure thats what I said before
.
steadfasterX said:
sure thats what I said before
.
Click to expand...
Click to collapse
can u provide a stock boot img for Nathan to edit?
XeniX_Force said:
can u provide a stock boot img for Nathan to edit?
Click to expand...
Click to collapse
sure what was your installed ROM and version? best would be a link to it as well..
.
steadfasterX said:
sure what was your installed ROM and version? best would be a link to it as well..
.
Click to expand...
Click to collapse
stock. i was using lineage but I returned to stock and got bootloop after some days.
XeniX_Force said:
stock. i was using lineage but I returned to stock and got bootloop after some days.
Click to expand...
Click to collapse
tell me the exact version. v10h, v10n, v20g, v20o .. there are dozens of versions out there..
.
Hey dudes,
since no one ever did this, I uploaded all Oreo Stock (retbr) for or beloved XT1789-05 released so far.
Here are the link:
https://www.dropbox.com/sh/emeuwiyaxpqqu56/AABKMNnrmMOwR5S0pBH2d7lWa?dl=0
The folder also contains RSD-lite for Mac and Linux users.
Enjoy.
if you are a Linux or Mac user and don't know how to use RSD, *I'll show you how to do with simple steps.
here we go:
1- Unzip the RSD-lite folder on your desktop;
2- Unzip the firmware zip and copy all files to the RSD folder on your desktop;
3- Open your terminal and go to the RSD-lite folder and connect your cellphone on USB with USB DEBUBBING ON;
4- Type this commands and hit ENTER after every line:
adb reboot bootloader
if you are on Linux;
bash rsd-flash.sh flashfile.xml
if you are on Mac:
./rsd-flash.sh flashfile.xml
press enter to start the flash from terminal
5- Watch for any errors. If no errors at the end of the script then press enter to reboot the device.
Many thanks to @Liboicl for the Linix script and @rootjunky for Mac script.
I'll keep adding the firmware on this folder as soon they pop up .
Does it flash to both slots? If not, this won't prepare the -05 model for AOSP ROMs. The T-Mobile flash all and Sprint ones flash to both slots via .sh or .bat files
Uzephi said:
Does it flash to both slots? If not, this won't prepare the -05 model for AOSP ROMs. The T-Mobile flash all and Sprint ones flash to both slots via .sh or .bat files
Click to expand...
Click to collapse
It flash both partitions, the script just compile all fastboot comands
darthxa said:
It flash both partitions, the script just compile all fastboot comands
Click to expand...
Click to collapse
So if you do "fastboot --set-active=_b" it will boot to system just fine?
Uzephi said:
So if you do "fastboot --set-active=_b" it will boot to system just fine?
Click to expand...
Click to collapse
As soon I get home I'll Test and do do sure
Uzephi said:
So if you do "fastboot --set-active=_b" it will boot to system just fine?
Click to expand...
Click to collapse
That's what I got
Perhaps it's because I have patched boot image in system B
But if that helped...
darthxa said:
That's what I got
Perhaps it's because I have patched boot image in system B
But if that helped...
Click to expand...
Click to collapse
That happened because the bootloader noticed slot B doesn't have Oreo firmware on it. I'll make a .sh and .bat for you in a couple of days for AOSP from the files in that zip. It will be firmware only, no system or OEM images as it will be for AOSP prep more than back to stock.
Uzephi said:
That happened because the bootloader noticed slot B doesn't have Oreo firmware on it. I'll make a .sh and .bat for you in a couple of days for AOSP from the files in that zip. It will be firmware only, no system or OEM images as it will be for AOSP prep more than back to stock.
Click to expand...
Click to collapse
Let me ask you, do you know if this particular model is eu version or America version? I'm trying install twrp ....
darthxa said:
Let me ask you, do you know if this particular model is eu version or America version? I'm trying install twrp ....
Click to expand...
Click to collapse
Installing twrp shouldn't matter the model. Just boot to twrp and flash the zip, it will edit your current boot image and not mess with any special properties like radio stuff that differ from model to model.
Hello. The new firmware has been released with the March patch NASH_OPXS27.109-34-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. Would you kindly be able to post the link? Thanks!!!
solocchi said:
Hello. The new firmware has been released with the March patch NASH_OPXS27.109-34-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. Would you kindly be able to post the link? Thanks!!!
Click to expand...
Click to collapse
Hi, I found it here https://plus.google.com/communities...1/stream/74c3716d-1a33-42b4-a515-63f32f4401e1, specificially in this post https://plus.google.com/111081030652026277798/posts/APCeCosyCX3 just by searching for exactly the filename you provided above with google.
Thanks for the link. I already know it but it doesn't work. I tried again and appear the message: access denied.
If you can download it and share it could be great.
solocchi said:
Thanks for the link. I already know it but it doesn't work. I tried again and appear the message: access denied.
If you can download it and share it could be great.
Click to expand...
Click to collapse
it's weird, i've got 2 pc, 1 access denied and download fine for the other
ilovemeow said:
it's weird, i've got 2 pc, 1 access denied and download fine for the other
Click to expand...
Click to collapse
I can not with any pc. If you have downloaded the firmware I would ask you kindly to post it. Thank you.
solocchi said:
I can not with any pc. If you have downloaded the firmware I would ask you kindly to post it. Thank you.
Click to expand...
Click to collapse
http://myown1gbb2.ddns.net:13955/sharing/sQf3mIAgr
password: MotoZ2ForceXT1789
ilovemeow said:
http://myown1gbb2.ddns.net:13955/sharing/sQf3mIAgr
password: MotoZ2ForceXT1789
Click to expand...
Click to collapse
Thanks!!!
darthxa said:
... for our beloved XT1789-05 ...
Click to expand...
Click to collapse
I wouldn't go as far as beloved
For me, this is actually the worst Moto phone I've ever owned (and I've owned 4 of them), specially by the price I paid for it... the phone doesn't worth not even half the price.
In fact, this is my last Moto ever, I'm done with Moto/Lenovo or any other Chinese crap for that matter.
Uzephi said:
I'll make a .sh and .bat for you in a couple of days for AOSP from the files in that zip.
Click to expand...
Click to collapse
I don't mean to push you or anything, I'm just curious if you were able to make the .bat/.sh file for this version (retbr)?
felipevsw said:
I don't mean to push you or anything, I'm just curious if you were able to make the .bat/.sh file for this version (retbr)?
Click to expand...
Click to collapse
My bat file in my thread will only work with official releases from the Motorola Firmware Team (MFT). I.E. with the official firmware and my .bat you will be able to take OTAs again. I cannot guarantee any other zips.
First of all i want to make clear that, i am new to this community, so for any inconvenience please forgive me.
I was curious about what will be the safest way to root my Android 11 devices running on MIUI Global 12.5.2 .
i watched a lot of YouTube videos but didn't come up with an answer i am looking for, i got confused a lot some people suggest doing without pc and some with some apps.
I would be glad if someone can explain to me, the best way to root Android device and do's and dont's before and after rooting the device. And how can i prevent my device from:
Getting hard/soft Brick.
Losing Data.
Data encryption.
And the things i should get familiar with before rooting.
Thanks to everyone in advance
akram0010 said:
First of all i want to make clear that, i am new to this community, so for any inconvenience please forgive me.
I was curious about what will be the safest way to root my Android devices running on MIUI Global 12.5.2 .
i watched a lot of YouTube videos but didn't come up with an answer i am looking for, i got confused a lot some people suggest doing without pc and some with some apps.
I would be glad if someone can explain to me, the best way to root Android device and do's and dont's before and after rooting the device. And how can i prevent my device from:
Getting hard/soft Brick.
Losing Data.
Data encryption.
And the things i should get familiar with before rooting.
Thanks to everyone in advance
Click to expand...
Click to collapse
You can not root without losing data, unlocking Xiaomi bootloader wipe all your data. For rooting, take a look Magisk instruction https://topjohnwu.github.io/Magisk/install.html very easy
akram0010 said:
Thanks for letting me know, it means i would have to backup my data first.
Click to expand...
Click to collapse
Make backup of data,apps, unlock bootloader then you can root your phone with magisk. Unlocking bootloader wiping all data.
DungxCt said:
You can not root without losing data, unlocking Xiaomi bootloader wipe all your data. For rooting, take a look Magisk instruction https://topjohnwu.github.io/Magisk/install.html very easy
Click to expand...
Click to collapse
In this page it tells, if you plan to install custom kernels install it after magisk, is it necessary to install custom kernel.
What if i don't install any kernel, will the default kernel be still there?
akram0010 said:
In this page it tells, if you plan to install custom kernels install it after magisk, is it necessary to install custom kernel.
What if i don't install any kernel, will the default kernel be still there?
Click to expand...
Click to collapse
You miss understand it, it doesn't mean you HAVE TO install custom kernel after root. Just mean: "If you WANT to, just do it after intall Magisk"
DungxCt said:
You miss understand it, it doesn't mean you HAVE TO install custom kernel after root. Just mean: "If you WANT to, just do it after intall Magisk"
Click to expand...
Click to collapse
Can i follow this , because i have the same device and also both have Android 11 however the miui is miui global 12.5.1where mine is miui global 12.5.2
akram0010 said:
Can i follow this , because i have the same device and also both have Android 11 however the miui is miui global 12.5.1where mine is miui global 12.5.2
Click to expand...
Click to collapse
Yes, If you want your device to become a brick.
Use https://play.google.com/store/apps/details?id=com.xiaomiui.downloader&hl=en_US&gl=US to download ur using version and extract the boot.img ur own
DungxCt said:
Yes, If you want your device to become a brick.
Use https://play.google.com/store/apps/details?id=com.xiaomiui.downloader&hl=en_US&gl=US to download ur using version and extract the boot.img ur own
Click to expand...
Click to collapse
First of all, i want to thank you for helping me so far.
I downloaded the App as you said and selected my version, now ita shows me three options to download OTA, RECOVERY, FASTBOOT.
which one should i download, and what am i gonna do with them after downloading?
akram0010 said:
First of all, i want to thank you for helping me so far.
I downloaded the App as you said and selected my version, now ita shows me three options to download OTA, RECOVERY, FASTBOOT.
which one should i download, and what am i gonna do with them after downloading?
Click to expand...
Click to collapse
Also it shows the version:
V12.5.4xxxxxxxxxxx
Click to expand...
Click to collapse
However mine is:
V12.5.2xxxxxxxxx
Click to expand...
Click to collapse
akram0010 said:
Also it shows the version:
However mine is:
Click to expand...
Click to collapse
Tap older version and download the recovery. Use https://github.com/ssut/payload-dumper-go to extract boot.img from payload.bin. Look how here https://www.xda-developers.com/how-to-install-magisk/
DungxCt said:
Tap older version and download the recovery. Use https://github.com/ssut/payload-dumper-go to extract boot.img from payload.bin. Look how here https://www.xda-developers.com/how-to-install-magisk/
Click to expand...
Click to collapse
I tapped on the older version, however mine version, i.e (12.5.2.0 RJCINXM ), is not listed.
I checked a couple of websites too, on them only this version is not listed others are like 12.5.3.0 etc
akram0010 said:
I tapped on the older version, however mine version, i.e (12.5.2.0 RJCINXM ), is not listed.
I checked a couple of websites too, on them only this version is not listed others are like 12.5.3.0 etc
Click to expand...
Click to collapse
I want to know, would it matter if i go for 12.5.4.0 version? cause the device model is same in both versions.
akram0010 said:
I want to know, would it matter if i go for 12.5.4.0 version? cause the device model is same in both versions.
Click to expand...
Click to collapse
Yea no prob, just the get boot.img from it
DungxCt said:
Yea no prob, just the get boot.img from it
Click to expand...
Click to collapse
Let me get it straight, you mean the ROM version doesn't matter, however the ROM should be same as that of the device model.
akram0010 said:
Let me get it straight, you mean the ROM version doesn't matter, however the ROM should be same as that of the device model.
Click to expand...
Click to collapse
Yea, just get the boot.img from the ROM you are using then all good.
DungxCt said:
Yea, just get the boot.img from the ROM you are using then all good.
Click to expand...
Click to collapse
Sure, from where would i get this boot.img, i mean from recovery ROM or FASTBOOT ROM?
akram0010 said:
Sure, from where would i get this boot.img, i mean from recovery ROM or FASTBOOT ROM?
Click to expand...
Click to collapse
Recovery ROM, unzip and extract from payload.bin.
Use https://github.com/ssut/payload-dumper-go to extract boot.img from payload.bin. Look how here https://www.xda-developers.com/how-to-install-magisk/.
I said it already, at #10
DungxCt said:
Recovery ROM, unzip and extract from payload.bin.
Use https://github.com/ssut/payload-dumper-go to extract boot.img from payload.bin. Look how here https://www.xda-developers.com/how-to-install-magisk/.
I said it already, at #10
Click to expand...
Click to collapse
Yes you said, problem is i am using Linux Ubuntu, i have adb and fastboot setup, however this payload dumper would it work on Linux
akram0010 said:
Yes you said, problem is i am using Linux Ubuntu, i have adb and fastboot setup, however this payload dumper would it work on Linux
Click to expand...
Click to collapse
can you even check and see?
akram0010 said:
Yes you said, problem is i am using Linux Ubuntu, i have adb and fastboot setup, however this payload dumper would it work on Linux
Click to expand...
Click to collapse
Can i do it manually? i mean extracting the boot.img from the recovery ROM manually.
Hello everyone,
Can someone help me with fixing my Persist Partition?
My Fingerprint Scanner doesn't work, and I found out it might be due to a corrupt /Persist.
I've tried extracting a Payload.bin (from the latest OTA Firmware) but it doesn't contain any Persist Images.
Can anyone either send me their Persist.img or help me find a original Persist.img from the Stock ROM?
Thanks in advance!
Fatal_Scythe said:
Hello everyone,
Can someone help me with fixing my Persist Partition?
My Fingerprint Scanner doesn't work, and I found out it might be due to a corrupt /Persist.
I've tried extracting a Payload.bin (from the latest OTA Firmware) but it doesn't contain any Persist Images.
Can anyone either send me their Persist.img or help me find a original Persist.img from the Stock ROM?
Thanks in advance!
Click to expand...
Click to collapse
Here you go...
Andrologic said:
Here you go...
Click to expand...
Click to collapse
Thank you!
If I may ask, is this your Persist, or is this from an Official ROM?
Fatal_Scythe said:
Thank you!
If I may ask, is this your Persist, or is this from an Official ROM?
Click to expand...
Click to collapse
It's mine. Persist is not part of the ROM, that's why you can extract it from there. It's factory installed in its own partition.
Andrologic said:
It's mine. Persist is not part of the ROM, that's why you can extract it from there. It's factory installed in its own partition.
Click to expand...
Click to collapse
That makes sense.
Though I kinda think that it's dumb that it's kind-of-impossible to obtain an "official" Persist Image from Asus since others like Xiaomi just put it into their Firmwares too, but alrighty I guess.
Will flash tomorrow and hopefully it helps.
Andrologic said:
It's mine. Persist is not part of the ROM, that's why you can extract it from there. It's factory installed in its own partition.
Click to expand...
Click to collapse
Well, kind of expected that but it doesn't work.
The Contents of my Persist Partition don't seem to change no matter how often I "erase" and "flash" the Persist.img. Calibrating with the "Factory Test" Tool also gives me an "get calibrate failed" error again so yeah.... Guess I'll go with Face Unlock for now.
Thank you very much though for your quick help.
Fatal_Scythe said:
Well, kind of expected that but it doesn't work.
The Contents of my Persist Partition don't seem to change no matter how often I "erase" and "flash" the Persist.img. Calibrating with the "Factory Test" Tool also gives me an "get calibrate failed" error again so yeah.... Guess I'll go with Face Unlock for now.
Thank you very much though for your quick help.
Click to expand...
Click to collapse
How do you flash it? Try using TWRP and if that doesn't work you should be able to flash it with the device in EDL mode.
Andrologic said:
How do you flash it? Try using TWRP and if that doesn't work you should be able to flash it with the device in EDL mode.
Click to expand...
Click to collapse
I tried all of that actually. It flashed just fine, but that's pretty much it.