Related
Very strange behavior on my Xiaomi A1, running stock Android 8.0...
I have been using Magisk for quite some time, and did not have any issues. But this changed with the most recent (April) OTA update
After using for 1/2 a day or so, I found my phone hanging in 'Recovery mode', telling me that some system files are damaged. Restart did not heelp
So I reinstalled the phone using Mi-Flash-Tool, unlocked, installed the latest OTA, installed Magisk (direct method), and again after a couple of hours the phone ended in a boot-loop.
And again, I reinstalled the phone using Mi-Flash-Tool, installed the latest OTA, unlocked, installed the 'patched_boot.img', the phone booted, showed 'no Sim Card', a dimmed screen, and rebooted again and again..
So it seems it's getting worse ...
I have Magisk-Manager installed, with some Modules, but the most recent problems happen even before installing Magisk.
With the stock-installation (stock boot image) everything is fine.
Any idea what went wrong?
I'd like to know too. Our device is rather wonky. Sometimes it gets stuck on the boot animation. Other times, the baseband is damaged which causes the no SIM Card error. All of which is corrected on a reboot.
oreo27 said:
I'd like to know too. Our device is rather wonky. Sometimes it gets stuck on the boot animation. Other times, the baseband is damaged which causes the no SIM Card error. All of which is corrected on a reboot.
Click to expand...
Click to collapse
I tried several reboots, and finally decided to re-install
My Xiaomi A1 is acting more weird and worse ....
I have been following every lead I found, but no success:
Every of these 3 approaches started with Re-Flashing the original FW using MiFlashTool (keeping my data), and updating the latest OTA. => I assume having a clean system to start with. Magisk Safety Check says: OK
First approach:
1) After following the procedure 'fastboot oem unlock' and 'fastboot boot patched-boot.img' my A1 starts booting but hangs forever at boot-animation.
2) When I do a force reboot (hold on/off key for 15sec) the device boots normally.
3) Going to MagiskManager I see 'ctsProfile: false', and when trying to install I am only offered 'download' and 'patch boot image', but no 'direct install' => so it seems the patched boot-image is not installed
Second approach:
1) After following the procedure 'fastboot oem unlock' and 'fastboot flash boot patched-boot.img' my A1 starts booting but hangs forever at boot-animation.
2) A reboot does not help, A1 starts booting but hangs forever at boot-animation.
3) a 'fastboot flash boot_a original-boot.img' and 'fastboot flash boot_a original-boot.img' brings the A1 back to normal life, but of cause with no MAGISK installable
Third Approach:
1)After 'fastboot oem unlock' and 'fastboot boot recovery-3.2.1-2-oreo.img' my A1 boots into TWRP recovery
2) I install Magisk-v16.3.zip, and reboot.
3) Booting lasts a couple of minutes and then I see my homescreen, dimmed, with wrong time, 'No SIM Card found' - and the device reboots after 10-15 seconds. Additional reboots don't help
As nothing is installed, or I have to re-flash I am not able to provide any log files.
The only step I have not tried yet is a full factory reset ....
Any idea what is wrong?
First approach does nothing. You can't boot a boot image, it needs to be flashed.
Second approach should normally work. But just to make sure, the patched boot image is from your current firmware, right? If it doesn't match your current setup, that can cause issues.
Third approach: try this again, but experiment with keeping dm-verity and forced encryption.
Tiemichael said:
My Xiaomi A1 is acting more weird and worse ....
I have been following every lead I found, but no success:
Every of these 3 approaches started with Re-Flashing the original FW using MiFlashTool (keeping my data), and updating the latest OTA. => I assume having a clean system to start with. Magisk Safety Check says: OK
First approach:
1) After following the procedure 'fastboot oem unlock' and 'fastboot boot patched-boot.img' my A1 starts booting but hangs forever at boot-animation.
2) When I do a force reboot (hold on/off key for 15sec) the device boots normally.
3) Going to MagiskManager I see 'ctsProfile: false', and when trying to install I am only offered 'download' and 'patch boot image', but no 'direct install' => so it seems the patched boot-image is not installed
Second approach:
1) After following the procedure 'fastboot oem unlock' and 'fastboot flash boot patched-boot.img' my A1 starts booting but hangs forever at boot-animation.
2) A reboot does not help, A1 starts booting but hangs forever at boot-animation.
3) a 'fastboot flash boot_a original-boot.img' and 'fastboot flash boot_a original-boot.img' brings the A1 back to normal life, but of cause with no MAGISK installable
Third Approach:
1)After 'fastboot oem unlock' and 'fastboot boot recovery-3.2.1-2-oreo.img' my A1 boots into TWRP recovery
2) I install Magisk-v16.3.zip, and reboot.
3) Booting lasts a couple of minutes and then I see my homescreen, dimmed, with wrong time, 'No SIM Card found' - and the device reboots after 10-15 seconds. Additional reboots don't help
As nothing is installed, or I have to re-flash I am not able to provide any log files.
The only step I have not tried yet is a full factory reset ....
Any idea what is wrong?
Click to expand...
Click to collapse
Which option do you choose in the MiFlash tool? Try this:
1. Flash using MiFlash Tool (Save User Data) > Reboot
2. adb reboot bootloader or simply boot to Fastboot
3. Boot the TWRP img
4. Flash Magisk 16.3.
5. Reboot.
Didgeridoohan said:
First approach does nothing. You can't boot a boot image, it needs to be flashed.
Click to expand...
Click to collapse
Yes, according to 'fastboot help' it should not work ..
But I have used it sucessfully before, and there is a lot of threads advocation 'fastboot boot patched_boot.img' e.g. https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
Didgeridoohan said:
ust to make sure, the patched boot image is from your current firmware, right? .
Click to expand...
Click to collapse
I downloaded, and created the patched boot-image myself, no difference
Didgeridoohan said:
Third approach: try this again, but experiment with keeping dm-verity and forced encryption.
Click to expand...
Click to collapse
I will try when I have some time
Thank you!
oreo27 said:
Which option do you choose in the MiFlash tool? Try this:
1. Flash using MiFlash Tool (Save User Data) > Reboot
2. adb reboot bootloader or simply boot to Fastboot
3. Boot the TWRP img
4. Flash Magisk 16.3.
5. Reboot.
Click to expand...
Click to collapse
There is a OTA update after flashing, the rest is exactly my Third approach!
Thank you!
Tiemichael said:
There is a OTA update after flashing, the rest is exactly my Third approach!
Thank you!
Click to expand...
Click to collapse
It won't install properly though if Magisk is installed. To get the OTA update, you need to re-flash the stock boot.img.
oreo27 said:
It won't install properly though if Magisk is installed. To get the OTA update, you need to re-flash the stock boot.img.
Click to expand...
Click to collapse
It seems my comment was not clear:
My Third approach:
1) Flash the original ROM using MiFlash, with 'keep data'
2)OTA Update
3)Unlock Bootloader
4)Boot TWRP
5)install Magisk 16.3 via TWRP
6)Reboot
Is there anything wrong with this?
Thanks!
Tiemichael said:
It seems my comment was not clear:
My Third approach:
1) Flash the original ROM using MiFlash, with 'keep data'
2)OTA Update
3)Unlock Bootloader
4)Boot TWRP
5)install Magisk 16.3 via TWRP
6)Reboot
Is there anything wrong with this?
Thanks!
Click to expand...
Click to collapse
Nothing wrong with that. Should work... But, as always with the fragmented Android ecosystem: YMMV.
Didgeridoohan said:
Third approach: try this again, but experiment with keeping dm-verity and forced encryption.
Click to expand...
Click to collapse
I put both into TWRP terminal before installing Magisk: no difference
Thanks!
Tiemichael said:
It seems my comment was not clear:
My Third approach:
1) Flash the original ROM using MiFlash, with 'keep data'
2)OTA Update
3)Unlock Bootloader
4)Boot TWRP
5)install Magisk 16.3 via TWRP
6)Reboot
Is there anything wrong with this?
Thanks!
Click to expand...
Click to collapse
Looks good. I would insert a reboot to system between 2 and 3 to ensure that the OTA completes properly.
oreo27 said:
Looks good. I would insert a reboot to system between 2 and 3 to ensure that the OTA completes properly.
Click to expand...
Click to collapse
Thanks!
Yes, there is definitely a Reboot after the OTA
Finally - it's working! Not sure what was wrong ...
How did I fix it:
Note: Xiaomi published a new FW yesterday, which included the latest (April) OTA update-> so need for OTA !
1) Installed original ROM using MiFlash
2) Fastboot oem unlock
3) fastboot boot twrp-recovery
4) TWRP: install Magisk-Uninstaller.zip (to get rid of all Magisk remains)
5) reboot system
6) fastboot boot twrp-recovery
7) TWRP: install Magisg-16.3.zip
8) reboot
9) Open Magisk Manager, install module1, reboot (to detect any module causing problems)
10) Open Magisk Manager, install module2, reboot
At the moment I am a 'Happy Magiscian', but let's wait and see
Thanks to all to helped with their valuable comments!
This happens with the beta release of Magisk. Change to stable channel, then patch the boot.img and you will have no problems.
I am trying it on an old vivo phone and getting somewhat same error but my phone keeps getting on and off, it doesn't even boots up completely it just shows VIVO and then off .... again VIVO and then off, and it goes on. I flashed the original boot.img and my phone working but then I cant root my device.
First I unlocked the boot loader, although I doubt that’s needed for installing Magisk:
A2/Android (Oreo 8.1): Enabled developer options, enabled unlocking of boot loader, enabled debugging via USB.
PC/Linux: $ adb reboot bootloader
A2 boots into boot loader.
PC/Linux: $ fastboot oem unlock
Then I tried installing Magisk:
A2/Android: Re-enabled developer options, enabled debugging via USB, disabled automatic system updates (just in case, for later).
PC/Linux: $ adb reboot recovery
A2/Android: On the dialog asking for permission to allow USB debugging, selected to always allow from this computer and hit OK.
A2 displays screen with lying robot, saying No command. I held power, pressed volume-up once, released power.
A2 boots into recovery.
A2/Recovery: Selected Apply update from ADB.
PC/Linux:
$ adb sideload Magisk-v16.0.zip
Total xfer: 1.01x
A2/Recovery: Error message failed to verify whole-file signature
PC/Linux: Checked the zip file. It can be unzipped just fine, so it’s OK.
What else can I try?
PS: I do have detailed screen shots of the critical steps, but I don’t find an option to upload them to the forum.
You can't sideload the Magisk zip on a stock recovery. If you don't have a custom recovery installed you'll have to patch the boot image first with the Manager and then flash the patched image manually with fastboot. Check the installation instructions in the release thread.
Didgeridoohan said:
You can't sideload the Magisk zip on a stock recovery.
Click to expand...
Click to collapse
Thanks!
If you don't have a custom recovery installed you'll have to patch the boot image first with the Manager and then flash the patched image manually with fastboot. Check the installation instructions in the release thread.
Click to expand...
Click to collapse
Tried that, but did something extremely stupid in the process, knowing full on that this could cause an issue (I assumed things are easy to fix in case something goes wrong):
I did not run any system updates, leaving the Android 8.1 ROM at V9.6.5.0. (no problem so far)
I downloaded V9.6.10.0 of the ROM, and had Magisk patch the included boot.img to create patched_boot.img (still no problem)
I flashed patched_boot.img onto my A2. Now the device did not boot anymore. It hung at the loader animation showing a horizontal bar with varying colors.
To get the A2 to boot again, I obtained V9.6.9.0 of the ROM, I flashed the included boot.img, and I cleared the cache. Unfortunately, while the device boots into Android now, I cannot enable WLAN. It simply doesn’t work. Again, no surprise: V9.6.9.0 ≠ V9.6.5.0
Not being able to find the V9.6.5.0 ROM, I got the idea to update the half broken A2 to the latest ROM, i.e. V9.6.10.0. But how, without WLAN? Well, I found out that it is possible to use the WLAN connection of another Android device via Bluetooth. This is what I used, and I had to be very patient – it’s dog slow. Anyhow, I waited, and the installer started to do its job. The download succeeded, but the installation failed.
Phew, for now I’m out of options, and I’ve a non functioning device.
In another thread on the XDA Forums, I did find an unofficial dump of V9.6.5.0. But 1. I’m hesitant to install from unofficial dumps, and 2. the dump does not include a boot.img. Instead it includes one big payload.bin. Don’t know what to make out of that.
The alternative could be to install either V9.6.10.O or V9.6.9.O manually, possibly by flashing each partition image individually from fastboot. I don’t know, however, if that is a great idea.
PS: Sorry about the confusion with all those numbers.
Oh man... Flashing an update manually (each partition should work fine) is probably a good idea at this point.
Didgeridoohan said:
Oh man... Flashing an update manually (each partition should work fine) is probably a good idea at this point.
Click to expand...
Click to collapse
Went ahead with that. In fact, included in the full ROM archive are scripts for doing the update, sorted by an increasing number of steps performed:
flash_all_except_data.sh
flash_all.sh
flash_all_lock.sh
flash_all_lock_crc.sh
The last one also flashes CRC check sums into crclist and sparsecrclist. Included is a script to generate these check sums form the image files: flash_gen_crc_list.py
Here’s how I got back to a system that boots up fine:
PC/Linux: $ tar xfz jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz
PC/Linux: $ cd jasmine_global_images_V9.6.10.0.ODIMIFE_8.1
PC/Linux: $ fastboot flashing unlock
(reboot)
PC/Linux: $ fastboot flashing unlock_critical
(possibly reboot again)
PC/Linux: $ ./flash_all_lock_crc.sh
(went through smoothly, flashing CRC possibly not necessary)
Following this success, I did another attempt at installing Magisk:
PC/Linux: $ cp ../patched_boot.img images/boot.img
(created with Magisk Manager from the V9.6.10.0 boot.img)
PC/Linux: $ python2.7 flash_gen_crc_list.py
(thought it’s a good idea, but doesn’t help – see below)
PC/Linux: $ fastboot flashing unlock
(reboot)
PC/Linux: $ fastboot flashing unlock_critical
(possibly reboot again)
PC/Linux: $ ./flash_all_lock_crc.sh
(went through smoothly, flashing CRC possibly not necessary)
Unfortunately, upon reboot I get:
Code:
<!>
Your device is corrupt. It can’t be trusted
and will not boot
Visit this link on another device:
g.co/ABH
Eventually the device doesn’t show the message anymore, instead hanging permanently at a androidone logo.
Not locking the boot loader after flashing solves the issue, but: For security reasons, I don’t want to use a device with an unlocked boot loader!
Any idea?
Uh-oh! Now it seems like I eclipsed my previous stupidity.
In the Android developer settings, I disabled OEM unlocking. Then I rebooted the device, locked the boot loader: fastboot oem lock This was still possible.
As result, I get the aforementioned error message:
Code:
<!>
Your device is corrupt. It can’t be trusted
and will not boot
Visit this link on another device:
g.co/ABH
But now I cannot unlock the device anymore. fastboot oem unlock gives: FAILED (remote: Flashing Unlock is not allowed)
Bricked for good, right? :crying:
Oh... I saw your first message about getting things working (post #5), but I didn't have time to answer (work, work, work).
Now I wished I would have had the time, since I would have posted that you should never lock your bootloader on a modded device. The risk of something going wrong and not being able to unlock the bootloader again is too great...
If you're lucky there's still some kind of hack available that you can use, but you'd have to take that in your device's forum, where they know the device best.
That sucks... I hope you get things sorted. Good luck.
Didgeridoohan said:
Now I wished I would have had the time, […]
Click to expand...
Click to collapse
Don’t worry. I like to take systems to their limit.
[…] since I would have posted that you should never lock your bootloader on a modded device.
Click to expand...
Click to collapse
For security reasons, I don’t like the idea of leaving the boot loader open. While I understand that – due to encryption – it’s not possible to access my data, I assume it would be feasible to modify boot.img to install a rootkit in a few minutes. Just the thought of this being possible makes me uncomfortable and not trust the device for productivity use.
I wonder if I would also get the your device is corrupt message with Lineage installed.
If you're lucky there's still some kind of hack available
Click to expand...
Click to collapse
Yes, I’m betting on that, or perhaps the Xiaomi Mi Flash Tool can be used. (looking for an official download location)
feklee said:
I wonder if I would also get the your device is corrupt message with Lineage installed.
Click to expand...
Click to collapse
Did you preserve dm-verity when you patched the boot image? That sounds like dm-verity complaining...
Didgeridoohan said:
Did you preserve dm-verity when you patched the boot image? That sounds like dm-verity complaining...
Click to expand...
Click to collapse
No:
I’m almost certain that I did not enable dm-verity.
The device is corrupt message appears right after the reboot following ./flash_all_lock.sh or ./flash_all_lock_crc.sh, i.e. without any setup by Magisk Manager, and dm-verity is disabled by default.
BTW I got around to trying Xiaomi Mi Flash Tool, but it’s useless: It seems to be simply an ugly GUI for the fastboot commands. It cannot flash a device in locked state. In the end I was able to revive the device by opening it and using the test point method. Phew, gotta be more careful the next time…
I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?
features99 said:
I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?
Click to expand...
Click to collapse
Need more specific details, like specific method of rooting, version of Magisk, updating to what?, etc...
Unfortunately you may have to flash the factory image and start all over again if no one else can help you with it. At least you have the option. Sucks when that happens.
I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat
jljtgr said:
I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat
Click to expand...
Click to collapse
I agree. Flashing the factory image without the -w would likely allow him to boot up again. But it would be helpful for that person to tell us exactly what they did so we can help them avoid it in the future, e.g. maybe they flashed the stable version of Magisk instead of Beta or Canary, or maybe they tried a direct install instead of patching the boot image, etc...
Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
Also I didnt modify my own boot image, but one I downloaded from a matching build.
I really appreciate the help
features99 said:
Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
I really appreciate the help
Click to expand...
Click to collapse
I would try fastboot flashing the stock boot image first.
If Magisk says you're on a version before 21.0, the patched image won't work for Android 11. Stable is currently 20.4 released in March.
Lughnasadh said:
I would try fastboot flashing the stock boot image first.
Click to expand...
Click to collapse
tried that..it didnt work
features99 said:
tried that..it didnt work
Click to expand...
Click to collapse
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.
Lughnasadh said:
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.
Click to expand...
Click to collapse
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!
features99 said:
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!
Click to expand...
Click to collapse
No problem. Glad you got it going. As I see you've already found out, Magisk Beta 21.1 is a good way to go. Canary as well but then you may run into problems in the future when Canary gets updated since those are "cutting edge" builds.
Hello everyone.
My phone is currently on V409N30f_00_LGU_KR_OP_0126.kdz, i was successful in unlocking it via 9008 method, and just a moment ago i was also successful in patching it with magisk (thanks to great guide here: https://forum.xda-developers.com/t/root-eu-lmv405ebw-magisk.3912959/ ). I had some problems, mainly i didn't know that you actually need proper abl_a/abl_b to boot the OS (i thought it's not a part of boot process, unless you push some buttons, but that doesn't seem to be the case). My final problem is that i can't seem to be able to get a proper permanent fastboot installed, and by proxy i can't get TWRP as well. Therefore i have couple of questions here:
1. How to get proper fastboot on an encrypted phone with android Q? Do i have to get rid of the encryption? How?
2. From what I understand, the boot partition needs to be patched to include TWRP, similar to how magisk was prepared - is there guide how to do that?
3. Why the phone fails to boot if i try to sideload/fastboot to TWRP image provided on this forum?
Thanks in advance for all your support
Scorcerer said:
Hello everyone.
My phone is currently on V409N30f_00_LGU_KR_OP_0126.kdz, i was successful in unlocking it via 9008 method, and just a moment ago i was also successful in patching it with magisk (thanks to great guide here: https://forum.xda-developers.com/t/root-eu-lmv405ebw-magisk.3912959/ ). I had some problems, mainly i didn't know that you actually need proper abl_a/abl_b to boot the OS (i thought it's not a part of boot process, unless you push some buttons, but that doesn't seem to be the case). My final problem is that i can't seem to be able to get a proper permanent fastboot installed, and by proxy i can't get TWRP as well. Therefore i have couple of questions here:
1. How to get proper fastboot on an encrypted phone with android Q? Do i have to get rid of the encryption? How?
2. From what I understand, the boot partition needs to be patched to include TWRP, similar to how magisk was prepared - is there guide how to do that?
3. Why the phone fails to boot if i try to sideload/fastboot to TWRP image provided on this forum?
Thanks in advance for all your support
Click to expand...
Click to collapse
Follow this link for the 30f boot_a with twrp injected.
Let me try to clarify a bit; The engineering v35 abl is Oreo. So if you have it installed, the phone won't boot, unless your OS is Oreo (which it isn't).
So the purpose of having that abl isn't to boot the phone, it's only to be used for things like 'fastboot oem unlock' or 'fastboot flash abl_a abl_original_a.img'
it's not to boot the phone. And yes, absolutely it's a part of the boot process abl stands for 'android boot loader'.
So to make use of that v35 eng abl (after you've unlocked the boot loader), would be to flash it to the inactive slot on the phone (most people that would be abl_b). That way, you can use twrp to switch slots, use fastboot, then switch back to the active slot.
To use that proved boot_twrp_a.img, you need to 1st, save your original boot partition, just in case. Then flash it (using qfil) to boot_a (assuming that's your active slot). Then, don't boot the device, go directly to recovery. Once in twrp, format data. Then reboot recovery. Then flash magisk and dm_verity.
then u should be all set.
cheers
AsItLies said:
Follow this link for the 30f boot_a with twrp injected.
Let me try to clarify a bit; The engineering v35 abl is Oreo. So if you have it installed, the phone won't boot, unless your OS is Oreo (which it isn't).
So the purpose of having that abl isn't to boot the phone, it's only to be used for things like 'fastboot oem unlock' or 'fastboot flash abl_a abl_original_a.img'
it's not to boot the phone. And yes, absolutely it's a part of the boot process abl stands for 'android boot loader'.
So to make use of that v35 eng abl (after you've unlocked the boot loader), would be to flash it to the inactive slot on the phone (most people that would be abl_b). That way, you can use twrp to switch slots, use fastboot, then switch back to the active slot.
To use that proved boot_twrp_a.img, you need to 1st, save your original boot partition, just in case. Then flash it (using qfil) to boot_a (assuming that's your active slot). Then, don't boot the device, go directly to recovery. Once in twrp, format data. Then reboot recovery. Then flash magisk and dm_verity.
then u should be all set.
cheers
Click to expand...
Click to collapse
Thanks for the TWRP image, i'm gonna flash it after weekend, when i'll have acces to the phone and will report back
One more question here though, are fastboot flashable files also flashable via qfil ?
Scorcerer said:
Thanks for the TWRP image, i'm gonna flash it after weekend, when i'll have acces to the phone and will report back
One more question here though, are fastboot flashable files also flashable via qfil ?
Click to expand...
Click to collapse
Yes, absolutely. With qfil you can pretty much flash anything to any partition. That's why it's wise to be very very cautious, you could flash the wrong image to a partition, it won't stop you, and it could be too big of an image for that partition but qfil will keep writing it and write over the neighboring partition(s)!
Alright,
I went in and flashed v35 eng abl via qfill into abl_a. That gave me fasboot, which i used to do:
fastboot flash boot_b boot-twrp-30f_a.img (the twrp image i've got from you)
and
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
Then, i switched over to b slot, and rebooted straight to recovery.
In TWRP, i wiped data with formatting it, rebooted to recovery again (didn't got asked for password, i think that's a good thing), then installed magisk.zip via sideload (didn't have it on sd card) and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip afterwards.
I still have 2 problems though:
1. I can't mount vendor - in the log i'm getting "Failed to mount /vendor" (unknown error 150)
2. If i try to boot to system it loops over, i have to wait till it switches over to a slot, which gives me fastboot back, which i'm using to boot to recovery on slot B.
Should i just YOLO it and try to install Lineage directly from here (as i have TWRP)? That's my end goal...
EDIT:
I just noticed by DDing off the vendor_a it's reeeeeally different form vendor_b, and i'm considering copying stuff over, especially since i already did KDZ couple of times, so i'm not afraid of starting over.
EDIT: this let me mount /vendor finally, but boot to OS still loops.
Scorcerer said:
Alright,
I went in and flashed v35 eng abl via qfill into abl_a. That gave me fasboot, which i used to do:
fastboot flash boot_b boot-twrp-30f_a.img (the twrp image i've got from you)
and
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
Then, i switched over to b slot, and rebooted straight to recovery.
In TWRP, i wiped data with formatting it, rebooted to recovery again (didn't got asked for password, i think that's a good thing), then installed magisk.zip via sideload (didn't have it on sd card) and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip afterwards.
I still have 2 problems though:
1. I can't mount vendor - in the log i'm getting "Failed to mount /vendor" (unknown error 150)
2. If i try to boot to system it loops over, i have to wait till it switches over to a slot, which gives me fastboot back, which i'm using to boot to recovery on slot B.
Should i just YOLO it and try to install Lineage directly from here (as i have TWRP)? That's my end goal...
EDIT:
I just noticed by DDing off the vendor_a it's reeeeeally different form vendor_b, and i'm considering copying stuff over, especially since i already did KDZ couple of times, so i'm not afraid of starting over.
EDIT: this let me mount /vendor finally, but boot to OS still loops.
Click to expand...
Click to collapse
First thing I see is that you flashed, assuming what you typed above is exactly what you did, vbmeta wrong.
it should be fastboot --disa... --disa... flash vbmeta_b vbmeta_blank.img
The 1st parameter, after 'flash' should be the partition you want to flash to. Then, after that, the image you want to flash to it.
2nd, just ignore the 'can't mount vendor' in the output of when you zip install magisk or dm_verity, it's irrelevant.
So why is it bootlooping when trying to get to system? Possibly the incorrect vbmeta command? Or maybe you didn't format data? (for format, you have to type in 'yes'). Possibly it's not the right image for the os? It is, beyond doubt, 30f that you flashed?
cheers
AsItLies said:
First thing I see is that you flashed, assuming what you typed above is exactly what you did, vbmeta wrong.
it should be fastboot --disa... --disa... flash vbmeta_b vbmeta_blank.img
The 1st parameter, after 'flash' should be the partition you want to flash to. Then, after that, the image you want to flash to it.
Click to expand...
Click to collapse
But that's what i did - i didn't change the command in my command and i copy-pasted it straight from command line and it says vbmeta_b everywhere...
AsItLies said:
2nd, just ignore the 'can't mount vendor' in the output of when you zip install magisk or dm_verity, it's irrelevant.
So why is it bootlooping when trying to get to system? Possibly the incorrect vbmeta command? Or maybe you didn't format data? (for format, you have to type in 'yes'). Possibly it's not the right image for the os? It is, beyond doubt, 30f that you flashed?
cheers
Click to expand...
Click to collapse
Yup, i didn't change name of the boot image you provided so i won't make any mistake here. Also, i noticed that after i restored from KDZ it forced me to grant access to internet and downloaded some kind of patches - can it be that those affected the booting sequence somehow and i should just take clean dump of abl_b for example so that it can be patched properly?
Oh, just now it occured to me, i can basically take two dumps, one after kdz restore and the other after booting it, then compare them with md5 and i'll know if it actually does something to them...
EDIT: one more question, is KDZ restoring both slots properly? or only the currently active one?
Scorcerer said:
But that's what i did - i didn't change the command in my command and i copy-pasted it straight from command line and it says vbmeta_b everywhere...
Yup, i didn't change name of the boot image you provided so i won't make any mistake here. Also, i noticed that after i restored from KDZ it forced me to grant access to internet and downloaded some kind of patches - can it be that those affected the booting sequence somehow and i should just take clean dump of abl_b for example so that it can be patched properly?
Oh, just now it occured to me, i can basically take two dumps, one after kdz restore and the other after booting it, then compare them with md5 and i'll know if it actually does something to them...
EDIT: one more question, is KDZ restoring both slots properly? or only the currently active one?
Click to expand...
Click to collapse
hmmmm, confusing. So u speak of clean dump abl_b so it can be patched... but we never patch abl (a or b).
and no, the 'downloaded some kind of patches' are just updates to their specific apps, it's not making any change to 'system'.
when using lgup, you should first use Part D/L and choose all partitions (you can clearly see it's doing both a & b by the list). Also, if doing a 'refurbish', it should be updating both slots. Only 'upgrade' would do one side and then switch to that side.
cheers
Okay, so, step-by step, i'll try it once again and will also be taking notes meanwhile
First, i restored from KDZ by refurbishing V409N30f_00_LGU_KR_OP_0126.kdz to be exact.
Just now i flashed eng35 into abl_a which got me into fastboot no problem - the fastboot screens says SECURE BOOT is "yes" and DEVICE STATE "unlocked" which seems okay i guess...
Flashing the TWRP image you provided with
fastboot flash boot_b boot-twrp-30f_a.img
I intend to leave abl_a with fastboot for the future and so i plan to boot from b side
Now the vbmeta:
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
went in just fine.
Reboothing to recovery - set the b slot to be active:
fastboot set_active b
rebooting form the phone buttons directly into recovery...Got TWRP 3.3.1-0 - asks for password, i have to cancel it obviously. Swiping to allow modifications and going directly to Wipe->Format Data->yes - works and done, but complains about /vendor and /data/media/TWRP/.twrps.
Going back a bit and rebooting TWRP to recovery again - This time it doesn't ask me for password so i think i got rid of the encryption.
Flashing Magisk-v22-0.zip from their webpage, i'm clicking on add more zips and adding Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip as well, clicking on reboot system aaaaand bootloop
Okay good, making progress for sure.when I get back to my computer I'll post a link to the magisk and DM verity I use that I know will work. Not positive that those are the problem, but everything else seems to be exactly what you should be doing.
Scorcerer said:
Okay, so, step-by step, i'll try it once again and will also be taking notes meanwhile
First, i restored from KDZ by refurbishing V409N30f_00_LGU_KR_OP_0126.kdz to be exact.
Just now i flashed eng35 into abl_a which got me into fastboot no problem - the fastboot screens says SECURE BOOT is "yes" and DEVICE STATE "unlocked" which seems okay i guess...
Flashing the TWRP image you provided with
fastboot flash boot_b boot-twrp-30f_a.img
I intend to leave abl_a with fastboot for the future and so i plan to boot from b side
Now the vbmeta:
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
went in just fine.
Reboothing to recovery - set the b slot to be active:
fastboot set_active b
rebooting form the phone buttons directly into recovery...Got TWRP 3.3.1-0 - asks for password, i have to cancel it obviously. Swiping to allow modifications and going directly to Wipe->Format Data->yes - works and done, but complains about /vendor and /data/media/TWRP/.twrps.
Going back a bit and rebooting TWRP to recovery again - This time it doesn't ask me for password so i think i got rid of the encryption.
Flashing Magisk-v22-0.zip from their webpage, i'm clicking on add more zips and adding Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip as well, clicking on reboot system aaaaand bootloop
Click to expand...
Click to collapse
check this folder for the version of Magiisk I know works. Don't remember why, but have read the latest version of Magisk is a problem somehow. Pretty sure if you follow the steps as u did above, with this magisk, it will work.
cheers
Hiho, thanks for sticking with me.
I did everything the same except for using the Magisk you provided, and when i finally got to it, it bootlooped all the same
I tried to flash stuff in different order and stuff, but accomplished nothing.
And then I remembered i read somewhere that the OTA only does update one slot at a time, so i thought maybe Refurbish behaves the same and flashes the other slot (in my case it'd be A since i'm trying TWRP and stuff on B)
I started comparing partitions, and almost all of them were the same, except:
515cddf67500d0be189f6fc386bad7c7 /dev/block/by-name/OP_a
7fe5ca2a051d6dbb9ef191fbee0af98c /dev/block/by-name/OP_b
a4b4bbed1d0a0aa668d76558a9d10fb4 /dev/block/by-name/abl_a
4c47ecd7254de2dd84f88dbc3e31ccc2 /dev/block/by-name/abl_b
65c4413067309174d839b98b3c7eff0e /dev/block/by-name/laf_a
e7e47f8e1e05f21cf06c638bf537be67 /dev/block/by-name/laf_b
c62e2c813eeaba8682bb7dd5e26ffa8b /dev/block/by-name/oem_a
65b0e730e47fd0017c11852917ef1d2b /dev/block/by-name/oem_b
dd90de59c1b08c949326d1625a8e4d55 /dev/block/by-name/system_a
d192b99fd2cc8a48dd3f106d9f0f8233 /dev/block/by-name/system_b
Obviously abl_a is different since i installed v35 eng to it, but the rest should be the same, right?
Since they're not, can i just dd from a to be and be done with it? A slot always booted fine, but since I'm installing eng into it I never tried to do twrp and stuff there...
Aaaand it works
So the trick was just to make sure that the proper OS is actually here, and then, well, everything works like a charm i guess I used newer magisk, and so far everything looks okay
Now i'm gonna put in Lineage, but this should be easy
This also means that Refubish doesn't flash everything as we thought it's supposed to be
Scorcerer said:
Aaaand it works
So the trick was just to make sure that the proper OS is actually here, and then, well, everything works like a charm i guess I used newer magisk, and so far everything looks okay
Now i'm gonna put in Lineage, but this should be easy
This also means that Refubish doesn't flash everything as we thought it's supposed to be
Click to expand...
Click to collapse
yeah the only one I trust to flash everything would be part D/L. When doing it, you select ea individual partition, and they are all listed, both a and b slots.
The purpose of the 'dual' slots (and no recovery partition any longer) is to update 1 slot at a time, while the other slot is the older OS version. That's the way OTA's are suppose to happen. But if you use LGUP and do a Part D/L, then both sides have the same OS.
it's confusing. Good u got it working!
cheers
Hi AsltLies,
I could see that you sent a 30f boot_a image with TWRP injected on it for Scorcerer. I'm on identical situation. Only difference that i want to stay on Pie. Probably i cant use that file as i'm on Pie.
Could you point me please how do i get to inject TWRP on a boot_a pie firmware. My devide and situation is identical as for Mr. Scorcerer. V409N, korea version.
I would like to try this guide here as it seems very confiable
Thanks in advance.
sptw said:
Hi AsltLies,
I could see that you sent a 30f boot_a image with TWRP injected on it for Scorcerer. I'm on identical situation. Only difference that i want to stay on Pie. Probably i cant use that file as i'm on Pie.
Could you point me please how do i get to inject TWRP on a boot_a pie firmware. My devide and situation is identical as for Mr. Scorcerer. V409N, korea version.
I would like to try this guide here as it seems very confiable
Thanks in advance.
Click to expand...
Click to collapse
If you want to stay on Pie, your situation is easier, you can just follow the guide to unlock and then use fastboot to boot twrp, use 'ramdisk inject' to inject the twrp image. Reboot to recovery, format data, reboot recovery again, flash magisk and dm_verity.
cheers
sptw said:
Hi AsltLies,
I could see that you sent a 30f boot_a image with TWRP injected on it for Scorcerer. I'm on identical situation. Only difference that i want to stay on Pie. Probably i cant use that file as i'm on Pie.
Could you point me please how do i get to inject TWRP on a boot_a pie firmware. My devide and situation is identical as for Mr. Scorcerer. V409N, korea version.
I would like to try this guide here as it seems very confiable
Thanks in advance.
Click to expand...
Click to collapse
Didn't realize it was available, but follow for the 20n boot+magisk boot image. This Link
I'd suggest using qfil to (first backup your original boot partition) to flash this to your active boot partition. Then exit edl mode and use the key combo to go directly to recovery (now twrp). Format data, then reboot recovery, then flash magisk and dm_verity. All set!
cheers
Hi AsltLies,
Thanks for both of informations. Let me try to explain a bit more. I am able to root the device with magisk. I made a boot_a patched using magisk apk and inject diretly into boot_a using qfill. It works like a charm. No problem at all.
The problem is that there are something wrong with viper4android using magisk. I want the older 2.3.4 driver and it has a kind of problem using convolver and system inject. User app method does not work.
I own a LG V20 with viper4android on it, and i can confirm that there are something wrong with viper on LG V40. My LG V20 is not a Bang & Olufsen and not even Merodian tune. Maybe the problem lies on this meridian audio tuned on LG V40. Chances are great about that. Devices sound differents and i have to accept this. But...
I would like to try the method that i used to root the LGV20 : Supersu and not magisk. I dont care about safety net. I dont use it. And a second problem with magisk : two apk refuse to open with magisk root method. I know they work with rooted devices but using rootcloack on xposed and xposed is very hard to get to work on magisk ( very limited )
So, i would like to use SuperSu method and not magisk to inject the old 2.3.4 viper4android directly on TWRP. I know how i can do it to works using the original drive and apk from the original devs. ( I dont like the new version 2.7 )
So, sorry for the long explanation, but do you know how i can install TWRP without to use magisk? ( That [TWRP] LG V40 / Judypn does not work. I only get bootloop ).
Thanks again.
In time: Maybe i'm doing something wrong to install TWRP. Do i need to instal it in both slots ( a and b? Do i need to access TWRP using the slot that is not active and make the zips install from there and not from the active slot? It's a kind of confusion for me. I already read a lot about it, but i'm still in doubt how it really works. I'm not interested to use another ROM, just stock.
sptw said:
Hi AsltLies,
Thanks for both of informations. Let me try to explain a bit more. I am able to root the device with magisk. I made a boot_a patched using magisk apk and inject diretly into boot_a using qfill. It works like a charm. No problem at all.
The problem is that there are something wrong with viper4android using magisk. I want the older 2.3.4 driver and it has a kind of problem using convolver and system inject. User app method does not work.
I own a LG V20 with viper4android on it, and i can confirm that there are something wrong with viper on LG V40. My LG V20 is not a Bang & Olufsen and not even Merodian tune. Maybe the problem lies on this meridian audio tuned on LG V40. Chances are great about that. Devices sound differents and i have to accept this. But...
I would like to try the method that i used to root the LGV20 : Supersu and not magisk. I dont care about safety net. I dont use it. And a second problem with magisk : two apk refuse to open with magisk root method. I know they work with rooted devices but using rootcloack on xposed and xposed is very hard to get to work on magisk ( very limited )
So, i would like to use SuperSu method and not magisk to inject the old 2.3.4 viper4android directly on TWRP. I know how i can do it to works using the original drive and apk from the original devs. ( I dont like the new version 2.7 )
So, sorry for the long explanation, but do you know how i can install TWRP without to use magisk? ( That [TWRP] LG V40 / Judypn does not work. I only get bootloop ).
Thanks again.
In time: Maybe i'm doing something wrong to install TWRP. Do i need to instal it in both slots ( a and b? Do i need to access TWRP using the slot that is not active and make the zips install from there and not from the active slot? It's a kind of confusion for me. I already read a lot about it, but i'm still in doubt how it really works. I'm not interested to use another ROM, just stock.
Click to expand...
Click to collapse
Well... i got to install TWRP in slot a. No more encrypt data. Install Selinux ( SuperSu ) too. Reboot to recovery and no more ask for password, so it works. Data continue to be there. TWRP see the Selinux root, but it always return to TWRP. It does not matter reboot to system, recovery and power off, it always return to TWRP. So, i go to the EDL mode, install v35eng on abl_a, install ablpiestock again to abl_a and...TWRP again...I cant boot.
sptw said:
Well... i got to install TWRP in slot a. No more encrypt data. Install Selinux ( SuperSu ) too. Reboot to recovery and no more ask for password, so it works. Data continue to be there. TWRP see the Selinux root, but it always return to TWRP. It does not matter reboot to system, recovery and power off, it always return to TWRP. So, i go to the EDL mode, install v35eng on abl_a, install ablpiestock again to abl_a and...TWRP again...I cant boot.
Click to expand...
Click to collapse
Hmmm, not sure yet what's going on but I updated the link above in prev post, it now points to a gdrive folder called 20n.
There's a new boot image in it that has just twrp injected, no magisk. Try that and see if it doesn't help. Be sure though of which is your active slot. The way a treble enabled device does ota updates is it will update the inactive slot, with the new version, switch slots, and then boots the new version. What that means is the OLD version is now the inactive slot.
So if u are on 20n, be sure to flash the new image to that slot, not the old one. If need be, use twrp or fastboot (getvar all) will tell you which slot is active.
cheers
Device:Vivo 1802
Android version: 8.1
Magisk version name:canary build
Magisk version code:25101
ANDROID - Google Drive
drive.google.com
this folder contains
1. stock image
2. patched boot image
3. magisk log
4. cat /proc/mount
the stock boot.img being used is correct one cause it fixed bootloop upon flashing
Can't obtain boot log as it requires custom kernal
Someone please help
Kernal log has been included in same folder...
someone please help
someone please help
i have same device
with the issue
I forgot one important rule. Do not update magisk if it works. Stable channel or not. Got the same stuck on line 137 of uninstaller.sh in the latest version tried v23 the version I installed. When I reboot black screen heptic feedback goes crazy and blue notification led stays on. I am trying to uninstall the version from twrp. So after all these years it's still not stable.
it never was really working for me!
SwapScout said:
it never was really working for me!
Click to expand...
Click to collapse
It did work for me but I guess my device it too old for the new version. I hoped for backwards compatibility but it does not exist at all when you install the update you will simply automatically brick your device. I now used 15.3 just a little outdated facepalm, I need a new rom but too busy and lazy right now.. I had to manually flash back original boot.img from the firmware and run the uninstall script a few times. Never the less to say that it works horribly at least that is my experience.. But if it works, it does work good.
So if you guys wonder how to fix it.. First get the version you installed from here
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
If the extension is *.apk rename it to zip call it uninstall_25.zip or whatever boot the phone in fastboot and load TWRP image (from here https://twrp.me/Devices/). Make sure to use the correct TWRP version too, I've noticed that the normal non ROW version corrupts boot.img in the patching process even if it says in the console successfully installed, without errors!.. It has something to do with the firmware on your phone I guess? Idk but give it a try and keep a copy of your original boot.img and back-ups in general before you attempt to mess with Magisk and Xposed. I use a old dev dummy phone for this a older one it runs non offical firms and magisk with xposed. It's buggy and not stable but it's a old phone perfect to play with and mess up.
Put it in the ADB and fastboot bin folder for your device (fist download the correct adb & fastboot)
Run
Code:
@echo off
%~d0
CD "%~d0%~p0"
@echo off
title Fastboot TWRP ..
adb reboot bootloader
fastboot boot twrp.img
echo booting TWRP
pause >nul
Login if full device encryption etc.
Install select the uninstall zip (magisk version you installed) for example uninstall_25.zip
If that does not work (in my case)
Grab original boot.img from OEM firmware or firmware version you are running and flash it.
Code:
fastboot flash boot boot.img
I did try to fix SELinux context(in TWRP) but I don't advice you to do so because it warns you it can break the system even futher. Try this as last option.
NiTrOwow said:
It did work for me but I guess my device it too old for the new version. I hoped for backwards compatibility but it does not exist at all when you install the update you will simply automatically brick your device. I now used 15.3 just a little outdated facepalm, I need a new rom but too busy and lazy right now.. I had to manually flash back original boot.img from the firmware and run the uninstall script a few times. Never the less to say that it works horribly at least that is my experience.. But if it works, it does work good.
So if you guys wonder how to fix it.. First get the version you installed from here
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
If the extension is *.apk rename it to zip call it uninstall_25.zip or whatever boot the phone in fastboot and load TWRP image (from here https://twrp.me/Devices/). Make sure to use the correct TWRP version too, I've noticed that the normal non ROW version corrupts boot.img in the patching process even if it says in the console successfully installed, without errors!.. It has something to do with the firmware on your phone I guess? Idk but give it a try and keep a copy of your original boot.img and back-ups in general before you attempt to mess with Magisk and Xposed. I use a old dev dummy phone for this a older one it runs non offical firms and magisk with xposed. It's buggy and not stable but it's a old phone perfect to play with and mess up.
Put it in the ADB and fastboot bin folder for your device (fist download the correct adb & fastboot)
Run
Code:
@echo off
%~d0
CD "%~d0%~p0"
@echo off
title Fastboot TWRP ..
adb reboot bootloader
fastboot boot twrp.img
echo booting TWRP
pause >nul
Login if full device encryption etc.
Install select the uninstall zip (magisk version you installed) for example uninstall_25.zip
If that does not work (in my case)
Grab original boot.img from OEM firmware or firmware version you are running and flash it.
Code:
fastboot flash boot boot.img
I did try to fix SELinux context(in TWRP) but I don't advice you to do so because it warns you it can break the system even futher. Try this as last option.
Click to expand...
Click to collapse
my phone neither have custom recovery available 🥹….
and I cant build one….as it requires stock recovery.img if I am not wrong …….
Swapmema6be said:
my phone neither have custom recovery available 🥹….
and I cant build one….as it requires stock recovery.img if I am not wrong …….
Click to expand...
Click to collapse
It should be possible to load the uninstaller zip with the stock recovery if the bootloader is unlocked and if the stock recovery doesn't check signature verification if it will you will need to sign the zip with the keys in order to pass it. It's always best to get a phone with all these packages available if not, you're fed up with what you have stock garbage..
For your Vivo Y83 it seems there is no custom recovery image around, I could not find it. Meaning you will have to manually side-load it by using the "Install Update" option in the recovery. Again I hope for you that it does not check for signature verification, it probably will and then well. You're out of luck doing the repair and you will have to reflash a fresh new rom. You can try to build it if you have the original recovery.img but that requires more effort. If the phone even worth all the effort? I think there is a reason why they left out support. There are better devices on the market even older ones and newer ones. Look on kimovil, Idk not a fan of mediatek SoC devices.
I don
NiTrOwow said:
It should be possible to load the uninstaller zip with the stock recovery if the bootloader is unlocked and if the stock recovery doesn't check signature verification if it will you will need to sign the zip with the keys in order to pass it. It's always best to get a phone with all these packages available if not, you're fed up with what you have stock garbage..
For your Vivo Y83 it seems there is no custom recovery image around, I could not find it. Meaning you will have to manually side-load it by using the "Install Update" option in the recovery. Again I hope for you that it does not check for signature verification, it probably will and then well. You're out of luck doing the repair and you will have to reflash a fresh new rom. You can try to build it if you have the original recovery.img but that requires more effort. If the phone even worth all the effort? I think there is a reason why they left out support. There are better devices on the market even older ones and newer ones. Look on kimovil, Idk not a fan of mediatek SoC devices.
Click to expand...
Click to collapse
t really need that fix Bootloop…. I can fix Bootloop by flashing original boot.img…..thing is I want to root🥹