Hello, so basically I edited the build.prop file but it saved incorrectly and I was left with a 0B build.prop file, phone rebooted, stuck at boot screen, the rest are tears from my mystake, can anyone give a copy of an orignal build.prop, thank you in advance
And if someone could help a bit with the rest (restore the said file as I can only access fastboot and recovery mode which only lets me wipe, safe boot or reboot, or if I should flash a stock image), it would be greatly apreciated,
Willno said:
Hello, so basically I edited the build.prop file but it saved incorrectly and I was left with a 0B build.prop file, phone rebooted, stuck at boot screen, the rest are tears from my mystake, can anyone give a copy of an orignal build.prop, thank you in advance
Click to expand...
Click to collapse
flash stock firmware with miflashotool and done
tutibreaker said:
flash stock firmware with miflashotool and done
Click to expand...
Click to collapse
Thanks for the help, it did work, I'll be more carefull next time
Willno said:
Thanks for the help, it did work, I'll be more carefull next time
Click to expand...
Click to collapse
the system and vendor partitions are read only, so any change to it will result in a file with 0b, the best and safer way to mod stock firmware is using magisk modules or this: https://forum.xda-developers.com/t/...system-partitions-to-read-write-mode.4521131/
tutibreaker said:
the system and vendor partitions are read only, so any change to it will result in a file with 0b, the best and safer way to mod stock firmware is using magisk modules or this: https://forum.xda-developers.com/t/...system-partitions-to-read-write-mode.4521131/
Click to expand...
Click to collapse
Ok thank you, when you talk about the magisk modules are you refering to another one in particular or the one in the link you provided which mentions it, thank you
Willno said:
Ok thank you, when you talk about the magisk modules are you refering to another one in particular or the one in the link you provided which mentions it, thank you
Click to expand...
Click to collapse
Any should work. All magisk module can be disabled easily.
Related
HI
I´ve rooted my Nexus 6 on MPA44I
1) twrp-2.8.7.1-shamu
2) BETA-SuperSU-v2.49
3) Despair.M.Shamu.R6.4.zip
but i can´t use apps like Adaway , its saying "can´t create /system/etc/hosts: read only file-system"
Root Checker says "got root"
Titanium Backup works
how can i get full Access to stop these anoying ads?
thanks for your help
you need to flash the unencrypted img before flashing Despair. and fwiw the order i use is: unencrypted img, then the kernel, then SU
cmh714 said:
you need to flash the unencrypted img before flashing Despair. and fwiw the order i use is: unencrypted img, then the kernel, then SU
Click to expand...
Click to collapse
funny, i am on preview 3, didnt flash the unencrypted img, but despair kernel, and i have full root access, including write.
Just flashed Preview 3. Could you guys please add a few links and maybe a little bit more detailed description? Thanks!
f2 said:
Just flashed Preview 3. Could you guys please add a few links and maybe a little bit more detailed description? Thanks!
Click to expand...
Click to collapse
try a different radio until you find one that you like, they all work.
and you do not have to flash an unencrypted boot.img before flashing despair.
simms22 said:
try a different radio until you find one that you like, they all work.
and you do not have to flash an unencrypted boot.img before flashing despair.
Click to expand...
Click to collapse
Thanks, I decided to use a JDX rom instead. That one was pretty much stock but pre-rooted...
f2 said:
Thanks, I decided to use a JDX rom instead. That one was pretty much stock but pre-rooted...
Click to expand...
Click to collapse
cool, thats what im using
Okay guys I think I've exhausted all of my options here's the short version of what's going on. I started the OTA update on my s5 and it got interrupted ( I don't really know how ) and it won't go past the Samsung boot screen (and it now says custom with an unlocked pad). After doing extensive research and downloads I can get the phone into Odin mode and into recovery mode. I tried flashing the stock rom, down grade roms and kernels of all variants through Odin and through recovery with no luck . Odin fails at secure system check and stock recovery says failed to find /system build.prop (no such file or directory). Viewing the recovery log It says my os is (oc4) and my bootloader is (oi5) no help from Samsung or AT&T. In Odin I am able to flash the oc4 kernel, modem and stock partitions. It says current binary SAMSUNG official system status custom Knox warranty void 0x0
Any advice would be greatly appreciated.
If anybody could help or is willing please let me know
Cam Shaft08 said:
If anybody could help or is willing please let me know
Click to expand...
Click to collapse
Try flashing this rom it is uploaded by muniz_ri
androidfilehost
. com
/
?fid=24052804347848936
it is oi5 it will pass secure check try it
it helped me with same problem
syedrazaabbas said:
Try flashing this rom it is uploaded by muniz_ri
androidfilehost
. com
/
?fid=24052804347848936
it is oi5 it will pass secure check try it
it helped me with same problem
Click to expand...
Click to collapse
I'm down loading it now. If it is the same one that has been up it won't work because I need an md5 and it will not sideload. I have to odin flash an md5.
Cam Shaft08 said:
I'm down loading it now. If it is the same one that has been up it won't work because I need an md5 and it will not sideload. I have to odin flash an md5.
Click to expand...
Click to collapse
make it odin flashable by using any tar.md5 program and then flash it the required files i do the same
syedrazaabbas said:
make it odin flashable by using any tar.md5 program and then flash it the required files i do the same
Click to expand...
Click to collapse
What program do you recommend
Cam Shaft08 said:
What program do you recommend
Click to expand...
Click to collapse
kindly tell me which files do you required i will convert and upload it for you
syedrazaabbas said:
kindly tell me which files do you required i will convert and upload it for you
Click to expand...
Click to collapse
Modem, kernel, recovery, stock partition. Basically I am trying to flash the rom in md5 section. Unless you want to convert the whole rom to md5 flashable for me.
Thank you for all of your help.
Cam Shaft08 said:
Modem, kernel, recovery, stock partition. Basically I am trying to flash the rom in md5 section. Unless you want to convert the whole rom to md5 flashable for me.
Thank you for all of your help.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0BzQYyLb6zJczbE9SY0k5UVljMWs/view?usp=sharing
here are the files you are asking each file is seperate use AP button for boot and recovery and CP button for modem and Non-hlos
cheers
syedrazaabbas said:
https://drive.google.com/file/d/0BzQYyLb6zJczbE9SY0k5UVljMWs/view?usp=sharing
here are the files you are asking each file is seperate use AP button for boot and recovery and CP button for modem and Non-hlos
cheers
Click to expand...
Click to collapse
I am downloading them now. Thank you so much for all of your help. I will let you know what happens!! You have been a huge help.
OK I flashed all of those files with no errors. All 4 took perfect. Still stuck though. Could you upload the system file? An .md5 system file. I think it's system.ext4 when I watch odin flash. Thank you again for all your help.
Bump
Cam Shaft08 said:
Bump
Click to expand...
Click to collapse
hi sorry for the late as i was out of town so i will convert and upload the system.ext4 soon as it is a big file it need some time to upload dont worry will upload it today
syedrazaabbas said:
hi sorry for the late as i was out of town so i will convert and upload the system.ext4 soon as it is a big file it need some time to upload dont worry will upload it today
Click to expand...
Click to collapse
No need to be sorry. I understand you have a life outside of xda . I'm trying to be as patient as I can its just that I miss my phone
Cam Shaft08 said:
No need to be sorry. I understand you have a life outside of xda . I'm trying to be as patient as I can its just that I miss my phone
Click to expand...
Click to collapse
https://drive.google.com/folderview?id=0BzQYyLb6zJczdDhQS2hyTXpMQ0E&usp=sharing
here you go
step 1 : Download all 14 parts according to order and put them into a new folder
step 2 : download winrar and install it if you already have skip it
step 3 : open part 1 in winrar and extract it , it will auto detect all 14 parts
finally you will have the file , it took me so many hours to upload the full file .
Cheers
syedrazaabbas said:
https://drive.google.com/folderview?id=0BzQYyLb6zJczdDhQS2hyTXpMQ0E&usp=sharing
here you go
step 1 : Download all 14 parts according to order and put them into a new folder
step 2 : download winrar and install it if you already have skip it
step 3 : open part 1 in winrar and extract it , it will auto detect all 14 parts
finally you will have the file , it took me so many hours to upload the full file .
Cheers
Click to expand...
Click to collapse
Awesome!!! THANK YOU!!!!!!!!!
syedrazaabbas said:
https://drive.google.com/folderview?id=0BzQYyLb6zJczdDhQS2hyTXpMQ0E&usp=sharing
here you go
step 1 : Download all 14 parts according to order and put them into a new folder
step 2 : download winrar and install it if you already have skip it
step 3 : open part 1 in winrar and extract it , it will auto detect all 14 parts
finally you will have the file , it took me so many hours to upload the full file .
Cheers
Click to expand...
Click to collapse
This is what I keep getting.
Cam Shaft08 said:
This is what I keep getting.
Click to expand...
Click to collapse
try to fresh your bootloader oi5
https://www.androidfilehost.com/?fid=24052804347851013
then after flashing this try the file again I hope it will help again
syedrazaabbas said:
try to fresh your bootloader oi5
https://www.androidfilehost.com/?fid=24052804347851013
then after flashing this try the file again I hope it will help again
Click to expand...
Click to collapse
It didn't work. Do you have any other suggestions or do you knew how to or can upload the kernel md5, modem md5, recovery md5, or can you do the full rom? Sorry to be such a pain but I just don't know what else to do. Ya know getting any help around is like pulling teeth.
Cam Shaft08 said:
It didn't work. Do you have any other suggestions or do you knew how to or can upload the kernel md5, modem md5, recovery md5, or can you do the full rom? Sorry to be such a pain but I just don't know what else to do. Ya know getting any help around is like pulling teeth.
Click to expand...
Click to collapse
hey syedrazaabbas im having the exact same problem. i flashed the files you kindly provided and same problem wont flash the system file. Im pretty compident with programs and phones so if there is a program i can use i will make a .tar.md5 oidin file myself if it is posible to do. thanks again, sorry i also searched and searched. it seems as if the att S5 section of XDA is a ghost town, i know it can be over whelming at times (i know im a mechanic and deal with my fair share) but i dont beleve in not helping if i have the means to do so.
Tom
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..
.
I went to codeworks page:
There are 4 files for the x522 in firmware and 4 in modems. I am assuming the "19s" firmware is for India so is the "20s" for the US?
But the 4 files in the modem section is confusing, which one/one's are for the US model x522? here is the link for the modems https://host.llamasweet.tech/codeworkx/lineage/s2/
Thanks
S2_x522-na-op-ifxnaop5802102141s-5.8.021s
leo221 said:
S2_x522-na-op-ifxnaop5802102141s-5.8.021s
Click to expand...
Click to collapse
Thanks but there is no file with that name listed in codeworks page is there? I have provided a link in the OP.
veda1 said:
Thanks but there is no file with that name listed in codeworks page is there? I have provided a link in the OP.
Click to expand...
Click to collapse
find here
https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079
leo221 said:
find here
https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079
Click to expand...
Click to collapse
Oh you mean flash that entire rom? And will that install the bootloader and modem? In any case, i tried flashing those files but they won't flash, any suggestions?
Since those roms won't flash i had to look for individual bootloader and modem and stumbled into those files by codeworks, and i am assuming you are saying that those aren't the correct files?
veda1 said:
Oh you mean flash that entire rom? And will that install the bootloader and modem? In any case, i tried flashing those files but they won't flash, any suggestions?
Since those roms won't flash i had to look for individual bootloader and modem and stumbled into those files by codeworks, and i am assuming you are saying that those aren't the correct files?
Click to expand...
Click to collapse
I just flashed 21S today on my 522. what recovery do you have right now? that's pure stock. flashing will erase everything and restore factory rom. https://youtu.be/v_aohNnvT_Q
leo221 said:
I just flashed 21S today on my 522. what recovery do you have right now?
Click to expand...
Click to collapse
twrp-3.2.1-0-s2, can't remember if i had the same one or one version older than the current one; when i tried it. Should i try it again? But the question is will it install the origibnal boot loader and modem? because i was playing with those in the past and flashed the wrong ones i think, and it will be great if i can go back to the original ones.
leo221 said:
I just flashed 21S today on my 522. what recovery do you have right now? that's pure stock. flashing will erase everything and restore factory rom. https://youtu.be/v_aohNnvT_Q
Click to expand...
Click to collapse
Yep its still happening. Tried to flash it right now and it says "can't read" error.
veda1 said:
twrp-3.2.1-0-s2, can't remember if i had the same one or one version older than the current one; when i tried it. Should i try it again? But the question is will it install the origibnal boot loader and modem? because i was playing with those in the past and flashed the wrong ones i think, and it will be great if i can go back to the original ones.
Click to expand...
Click to collapse
it certainty restores boot. not sure about modem, I never touched it. you have nothing to loose flashing it. it supposed to be bone stock. just delete two lines in the script and re-save zip. you have to do wipe, wipe data, then mount, copy zip, flash, reboot. in that order, I wasted hours today finding out that order is required. otherwise, it won't load.
https://forum.xda-developers.com/le-2/help/help-restoring-s3-x522-to-stock-rom-t3809619
leo221 said:
it certainty restores boot. not sure about modem, I never touched it. you have nothing to loose flashing it. it supposed to be bone stock. just delete two lines in the script and re-save zip. you have to do wipe, wipe data, then mount, copy zip, flash, reboot. in that order, I wasted hours today finding out that order is required. otherwise, it won't load.
https://forum.xda-developers.com/le-2/help/help-restoring-s3-x522-to-stock-rom-t3809619
Click to expand...
Click to collapse
Updated script according to the video, still not flashing, says "cannot read error"
veda1 said:
Updated script according to the video, still not flashing, says "cannot read error"
Click to expand...
Click to collapse
then you have a more complicated problem than mine. I had stock fastboot, and twrp.
leo221 said:
then you have a more complicated problem than mine. I had stock fastboot, and twrp.
Click to expand...
Click to collapse
Unbelievable! It actually worked after the 2nd attempt. Even got the 21s update. Thanks :good:
The original question is still unanswered about which one is the correct firmware for the US model amng the firmware provided by codeworks, hopefully someone knows that and will share in interest of others that might have the same problem.
Thanks again @leo221 for providing a clear and easy solution.
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