Related
Well I was looking for an Honami Rom days ago,
and I flashed THIS: http://forum.xda-developers.com/showpost.php?p=47112717&postcount=74
Then when I tried installing CM11 or AOKP it fails, only STOCK based ROMS work
I reflashed the firmware with flashtool and repaired with PC Companion
but when I go to CWM I still get status 7 error when flashing CM11
Can anyone help?
I'm on Xperia V with unlocked bootloader
Allen Hu said:
Well I was looking for an Honami Rom days ago,
and I flashed THIS: http://forum.xda-developers.com/showpost.php?p=47112717&postcount=74
Then when I tried installing CM11 or AOKP it fails, only STOCK based ROMS work
I reflashed the firmware with flashtool and repaired with PC Companion
but when I go to CWM I still get status 7 error when flashing CM11
Can anyone help?
I'm on Xperia V with unlocked bootloader
Click to expand...
Click to collapse
Umm, that's odd..... Try to install TWRP and flash CM11 or whatever with it
St.Jimmy90 said:
Umm, that's odd..... Try to install TWRP and flash CM11 or whatever with it
Click to expand...
Click to collapse
TWRP not working too :silly::crying:
Allen Hu said:
TWRP not working too :silly::crying:
Click to expand...
Click to collapse
Same problem. Have you find any solution?
zaize said:
Same problem. Have you find any solution?
Click to expand...
Click to collapse
Flash AOKP mr2 every time when you switch Roms, IDK why but you should be able to flash other roms after doing this
Allen Hu said:
Flash AOKP mr2 every time when you switch Roms, IDK why but you should be able to flash other roms after doing this
Click to expand...
Click to collapse
Man thats crazy - but it worked! Thank you :victory:
zaize said:
Man thats crazy - but it worked! Thank you :victory:
Click to expand...
Click to collapse
Allen Hu said:
Flash AOKP mr2 every time when you switch Roms, IDK why but you should be able to flash other roms after doing this
Click to expand...
Click to collapse
St.Jimmy90 said:
Umm, that's odd..... Try to install TWRP and flash CM11 or whatever with it
Click to expand...
Click to collapse
First flash kernel of ROM that you're going to install via fastboot, then reboot to recovery and flash ROM :laugh:
Allen Hu said:
Well I was looking for an Honami Rom days ago,
and I flashed THIS: http://forum.xda-developers.com/showpost.php?p=47112717&postcount=74
Then when I tried installing CM11 or AOKP it fails, only STOCK based ROMS work
I reflashed the firmware with flashtool and repaired with PC Companion
but when I go to CWM I still get status 7 error when flashing CM11
Can anyone help?
I'm on Xperia V with unlocked bootloader
Click to expand...
Click to collapse
Does the error say only "status 7", or does it say anything else also, such as "this device is xxxx, etc."?
Antiga Prime said:
Does the error say only "status 7", or does it say anything else also, such as "this device is xxxx, etc."?
Click to expand...
Click to collapse
The problem is already solved here...
it showed the " this device is "mint"" or something like that
Allen Hu said:
Flash AOKP mr2 every time when you switch Roms, IDK why but you should be able to flash other roms after doing this
Click to expand...
Click to collapse
St.Jimmy90 said:
Umm, that's odd..... Try to install TWRP and flash CM11 or whatever with it
Click to expand...
Click to collapse
Aria.A97 said:
First flash kernel of ROM that you're going to install via fastboot, then reboot to recovery and flash ROM :laugh:
Click to expand...
Click to collapse
Allen Hu said:
The problem is already solved here...
it showed the " this device is "mint"" or something like that
Click to expand...
Click to collapse
Ok, I know the problem is "solved", but it's not really solved if you don't know what is going on; this problem is not odd. In order for you to flash a file, there is a file in the zip named "updater-script" in the "/Meta-inf/com/google/android/" folder which has the commands that are run when you flash it, be it with CWM or TWRP. The first two lines of that file read the device identification from the "build.prop" file that comes with the ROM you currently have installed, so, if that ROM is identifying your device incorrectly, or using strings that aren't exactly like the ones contained in the "updater-script", it won't work.
Now, flashing a different ROM before flashing the ROM you're going to use without wiping /system and /data is a dumb thing to do, IMO, because the "updater-script" files don't always erase everything and leave behind remnants of the previous ROM, which is why tons of people complain about little bugs and problems with their ROMs, when other people who do in fact flash properly don't have these problems and therefore can't help them, and then these people blame it on the ROM, saying it has bugs and other stuff when in fact they don't know what they are doing.
All this to say, instead of having to flash an entire different ROM as per what @Allen Hu suggested, what I do is extract the "updater-script" file and delete the first two lines that say:
assert(getprop("ro.product.device") == "LT29i" || getprop("ro.build.product") == "LT29i" ||
getprop("ro.product.device") == "hayabusa" || getprop("ro.build.product") == "hayabusa" || abort("This package is for \"LT29i,hayabusa\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Click to expand...
Click to collapse
In my case, the ROM is made for an LT29I, not an LT25, but you get the point.
After deleting that line (with Notepad++, not Windows notepad), just add the script file back, and you can flash it on any device you like, and that would be a proper solution.
Many thanks
Antiga Prime said:
Ok, I know the problem is "solved", but it's not really solved if you don't know what is going on; this problem is not odd. In order for you to flash a file, there is a file in the zip named "updater-script" in the "/Meta-inf/com/google/android/" folder which has the commands that are run when you flash it, be it with CWM or TWRP. The first two lines of that file read the device identification from the "build.prop" file that comes with the ROM you currently have installed, so, if that ROM is identifying your device incorrectly, or using strings that aren't exactly like the ones contained in the "updater-script", it won't work.
Now, flashing a different ROM before flashing the ROM you're going to use without wiping /system and /data is a dumb thing to do, IMO, because the "updater-script" files don't always erase everything and leave behind remnants of the previous ROM, which is why tons of people complain about little bugs and problems with their ROMs, when other people who do in fact flash properly don't have these problems and therefore can't help them, and then these people blame it on the ROM, saying it has bugs and other stuff when in fact they don't know what they are doing.
All this to say, instead of having to flash an entire different ROM as per what @Allen Hu suggested, what I do is extract the "updater-script" file and delete the first two lines that say:
In my case, the ROM is made for an LT29I, not an LT25, but you get the point.
After deleting that line (with Notepad++, not Windows notepad), just add the script file back, and you can flash it on any device you like, and that would be a proper solution.
Click to expand...
Click to collapse
Thank you for solving this properly, it worked perfectly for me!
worked for me
Antiga Prime said:
Ok, I know the problem is "solved", but it's not really solved if you don't know what is going on; this problem is not odd. In order for you to flash a file, there is a file in the zip named "updater-script" in the "/Meta-inf/com/google/android/" folder which has the commands that are run when you flash it, be it with CWM or TWRP. The first two lines of that file read the device identification from the "build.prop" file that comes with the ROM you currently have installed, so, if that ROM is identifying your device incorrectly, or using strings that aren't exactly like the ones contained in the "updater-script", it won't work.
Now, flashing a different ROM before flashing the ROM you're going to use without wiping /system and /data is a dumb thing to do, IMO, because the "updater-script" files don't always erase everything and leave behind remnants of the previous ROM, which is why tons of people complain about little bugs and problems with their ROMs, when other people who do in fact flash properly don't have these problems and therefore can't help them, and then these people blame it on the ROM, saying it has bugs and other stuff when in fact they don't know what they are doing.
All this to say, instead of having to flash an entire different ROM as per what @Allen Hu suggested, what I do is extract the "updater-script" file and delete the first two lines that say:
In my case, the ROM is made for an LT29I, not an LT25, but you get the point.
After deleting that line (with Notepad++, not Windows notepad), just add the script file back, and you can flash it on any device you like, and that would be a proper solution.
Click to expand...
Click to collapse
works fine
Allen Hu said:
Flash AOKP mr2 every time when you switch Roms, IDK why but you should be able to flash other roms after doing this
Click to expand...
Click to collapse
Hi, i have the same problem, but i don't know were i can find the AOKP, can you please help with this?
Thank you
celupapas said:
Hi, i have the same problem, but i don't know were i can find the AOKP, can you please help with this?
Thank you
Click to expand...
Click to collapse
http://xfer.aokp.co/get.php?p=AOKP/tsubasa/aokp_tsubasa_jb-mr2_milestone-1.zip
Here you go
Well if this doesn't work you can try deleting some lines in updater-script as the method provided above?
Allen Hu said:
Here you go
Well if this doesn't work you can try deleting some lines in updater-script as the method provided above?
Click to expand...
Click to collapse
Thanks a lot, I flash AOKP and this work, everything is normal again.
Never happen but I read that the problem was the rom and some problems with the recovery.
Hello,
I have tried to install CM12 using CWM but I got this error.
After deleting the first line on updater-script file I got another error:
Creating symlinks....
symlink: some symlinks filederror in /storage/...
(Status 7)
installation aborded.
I have tried to delete also the second line and the third and the 4th but every time the same error.
Do you have any idea of what is happening?
Can you please provide some basic instructions on how to install this custom ROM with Flashtool?
Thank you
nicu.s said:
Hello,
I have tried to install CM12 using CWM but I got this error.
After deleting the first line on updater-script file I got another error:
Creating symlinks....
symlink: some symlinks filederror in /storage/...
(Status 7)
installation aborded.
I have tried to delete also the second line and the third and the 4th but every time the same error.
Do you have any idea of what is happening?
Can you please provide some basic instructions on how to install this custom ROM with Flashtool?
Thank you
Click to expand...
Click to collapse
First, you can't just go deleting lines; if they are there, it's for a reason. Second, I'm pretty sure your CWM version isn't up to date in order to flash a CM12 ROM. And, you can't flash a Custom ROM with Flashtools.
What you can do, however, is extract the boot.img from the ZIP file, flash that kernel with Flashtool, and then Flash the ROM in what most likely would now be TWRP recovery.
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.
Guys, some auto rotate work but mostly it not. Whether, am on custom or stock ROM.
Please help me with this issue.
How to make auto rotate work perfectly?? Or I should go to service centre???
did you ever upgrade to Q rom then downgrade back to pie because this causes this sensor issue. And you have to flash back original miui version to get sensors working again
sam00561 said:
did you ever upgrade to Q rom then downgrade back to pie because this causes this sensor issue. And you have to flash back original miui version to get sensors working again
Click to expand...
Click to collapse
Yes. Now so what I have to do??? Flash q ROM or pie ROM with fastboot. Pls let me know bro
If you were on pie then flash back to that one and it should fix. Please be careful not to select clean and lock in mi flash settings. Only select clean all.
sam00561 said:
If you were on pie then flash back to that one and it should fix. Please be careful not to select clean and lock in mi flash settings. Only select clean all.
Click to expand...
Click to collapse
You mean miui q ROM.
Basically flash back the rom which came with your phone I assume that would have been pie .
sam00561 said:
Basically flash back the rom which came with your phone I assume that would have been pie .
Click to expand...
Click to collapse
Yes it was pie but I don't know version. So can I flash q rom.
Am already on miui pie
I think it might not work like that I think you have to flash back to pie first then you can flash to Q. And where did you buy the phone.
sam00561 said:
I think it might not work like that I think you have to flash back to pie first then you can flash to Q. And where did you buy the phone.
Click to expand...
Click to collapse
Buyed from flipkart
gurwinderr84 said:
Buyed from flipkart
Click to expand...
Click to collapse
Are you in India
sam00561 said:
Are you in India
Click to expand...
Click to collapse
Hnji, India
I had this exact same issue this week and I fixed it now I'll be happy to help you fix it too.
here's some question and I want them answered fully to expedite the process
what's your rom version number and is it Global, Eu, China?
Are you using orange fox recovery?
don't worry it's easy to fix once you know how =)
kitsune_snake said:
I had this exact same issue this week and I fixed it now I'll be happy to help you fix it too.
here's some question and I want them answered fully to expedite the process
what's your rom version number and is it Global, Eu, China?
Are you using orange fox recovery?
don't worry it's easy to fix once you know how =)
Click to expand...
Click to collapse
He's in India so likely best option is the stable India rom to flash. I tried posting the link but xda won't allow.
kitsune_snake said:
I had this exact same issue this week and I fixed it now I'll be happy to help you fix it too.
here's some question and I want them answered fully to expedite the process
what's your rom version number and is it Global, Eu, China?
Are you using orange fox recovery?
don't worry it's easy to fix once you know how =)
Click to expand...
Click to collapse
Am on India miui 10.3.5.0 using oragefox recovery
kitsune_snake said:
I had this exact same issue this week and I fixed it now I'll be happy to help you fix it too.
here's some question and I want them answered fully to expedite the process
what's your rom version number and is it Global, Eu, China?
Are you using orange fox recovery?
don't worry it's easy to fix once you know how =)
Click to expand...
Click to collapse
Please tell me solution
Wow are you still trying to fix this issue can you join the k20 pro telegram group there's many developer in there who can help straight away.
Yes pls help to solve issue
gurwinderr84 said:
Please tell me solution
Click to expand...
Click to collapse
Okay, so when you updated to Q and then reverted back to P you messed up the persist.img, it's a part of the phone that regulates many sensor with the proper value.
what we need to do is fix the persist.img, luckily Orange fox will help up in that regard!
So first things first we need to get a replacement persist.img
Start by booting into Orange fox and make a backup of everything except internal storage.
go to https://xiaomifirmwareupdater.com/miui/raphael/ and get the latest china rom for fastboot (at the time of this writing, it's V10.3.17.0.PFKCNXM )
Once it has finished downloading open it like a zip using 7zip, inside should be a .TAR file, open it again like a zip and inside that unarchived TAR file should be a folder called "image" and within that one, will be a file called "persist.img".
Take the persist file and put it in your phone's storage, in orange fox select the file and options will be presented to you as to where to flash the image file, select of course the persist partition.
after this wipe cache and reboot.
The first boot will have a couple of issues, the phone will need to recalibrate itself, follow the instructions on the screen (open the front camera, clibrate gyro, etc).
After that you should be all set my friend
kitsune_snake said:
Okay, so when you updated to Q and then reverted back to P you messed up the persist.img, it's a part of the phone that regulates many sensor with the proper value.
what we need to do is fix the persist.img, luckily Orange fox will help up in that regard!
So first things first we need to get a replacement persist.img
Start by booting into Orange fox and make a backup of everything except internal storage.
go to https://xiaomifirmwareupdater.com/miui/raphael/ and get the latest china rom for fastboot (at the time of this writing, it's V10.3.17.0.PFKCNXM )
Once it has finished downloading open it like a zip using 7zip, inside should be a .TAR file, open it again like a zip and inside that unarchived TAR file should be a folder called "image" and within that one, will be a file called "persist.img".
Take the persist file and put it in your phone's storage, in orange fox select the file and options will be presented to you as to where to flash the image file, select of course the persist partition.
after this wipe cache and reboot.
The first boot will have a couple of issues, the phone will need to recalibrate itself, follow the instructions on the screen (open the front camera, clibrate gyro, etc).
After that you should be all set my friend
Click to expand...
Click to collapse
Where to flash persist.img from orangefox recovery ?? System or Vendor??? Flash 2 time fastboot ROM but not solved out the issue. Also, by mistake on 3rd attempt got bootloader locked. So, now what I do??
gurwinderr84 said:
Where to flash persist.img from orangefox recovery ?? System or Vendor??? Flash 2 time fastboot ROM but not solved out the issue. Also, by mistake on 3rd attempt got bootloader locked. So, now what I do??
Click to expand...
Click to collapse
Allright, first I never mentionned anything about flashing a fastboot rom, so you need to take it easy and follow instructions attentively (don't panic it's all gonna be okay)
Since you relocked your bootloader you just have to unlock it again using the many guides posted on this forum (I will not help you with this since there's already plenty of thread on the subject)
after your bootloader is back to an unlocked state, you re-installed OrangeFox and you flashed the ROM you want follow the procedure I typed to the letter and you'll be fine.
As for how to flash the "persist.img". In the "files" tab in OrangeFox just tap on the "persist.img" file and in the window that opens you will have a chance to select to which partition you wanna flash the file (you need of course to select the "persist" partition)
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.