Related
Hi,
there is something wrong with my Xperia Tablet Z. After upgrading from CyanogenMod 11 to CyanogenMod 12 a few Mouth ago the Custom Recovery i've installed before was replaced with CyanogenMod-Recovery. Because CM doesn't work very well i downgraded to Stock-ROM using Flashtool. Because i couldn't find a Way to root Firmware 4.2.x and higher i downgraded to 4.1.2 and rooted with towelroot. The Bootloader is unlocked (checked with *#*#7378423#*#*).
But when i try to install TWRP it failed. This is the error with Fastboot
Code:
fastboot flash recovery twrp.img
fastboot flash recovery twrp.img
sending 'recovery' (10688 KB)...
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.359s
All drivers are installed. I've tried this on Ubuntu 16.04 and Windows 7 with installed Flashtool and also with installed ADB Installer (https://forum.xda-developers.com/showthread.php?p=48915118#post48915118). I tried it with three usb cables and different usb ports.
It also doesn't work with TWRP Manager (https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=de) and the Official TWRP App (https://play.google.com/store/apps/details?id=me.twrp.twrpapp&hl=de). TWRP Manager show me this error
Code:
Flashing recovery was unsuccessful. Either you already have thos recovery installed or another error has occuured. Would you like to attempt to recovery now?
When i try to reboot the App freeze.
The Official TWRP App seems to install the recovery ("was successfully installed"), but i can't reboot into recovery with VOL+ (also tried VOL-). The Table starts normally.
Maybe there is something wrong with my Tablet now? Is there any other Way to flash a Recovery or to flash a Custom-Rom or a pre-rooted Stock-Rom? As i said before i can't root it with a Firmware higher 4.1.x. Update with the internal Update fuction also failed. So at the moment i can use [email protected] or a higher Version without root.
@PiereMallao
Sony devices, in particular, tabz don't have separate recovery partition. So you need to flash kernel with built-in recovery (see crDroid, RR, LA firmware threads), or you have to flash TWRP to FOTA partition.
Hi,
after some years with my pollux_windy left untouched, I decided I'd install my first custom ROM. But I'm having serious trouble to do so, and it seems unsolvable to me after hours of despair (I've been trying for almost 10 hours now).
I was on Lollipop (firmware .222), first unlocked my bootloader, then rooted my tablet (using kingroot). Then I tried to install twrp, and the only way I managed to do this was through this "TabZ-lockeddualrecovery2.8.26" thing. Only, I couldn't manage to flash anything, ended up bricking my tablet.
I then flashed a stock 5.0.2 ROM (.454), retried installing twrp via the same method, and although I manage to access twrp, I get the same error each time I want to flash a new ROM (tried CM/LineageOS 14.1 and ResurrectionRemix v5.7.0), which is : "E: error executing updater binary in zip [insert name of the .zip]".
If I hear Rootk1t correctly, I should flash a kernel with a built-in recovery first... But, doing some research, it looks like you need a working recovery in the first place to flash a custom kernel.
I'm completely lost in this... How can I get that damn recovery to work, and/or get a custom ROM ?
Edit : Alright, with a good 3 hours-long night and a lucky shot, I managed to install LineageOS ! I used twrp recovery (from the dualrecovery thingy-thing) to wipe clean the device, then tried to install the ROM. It gave me the same error message about updating binary. So I rebooted the device into fastboot (couldn't access the recovery anyway... not sure if it's normal), flashed the "boot.img" from the ROM using Flashtool, then rebooted again the device. On the bootlogo, I tried to enter recovery with Vol-, and it worked. i then flashed with ease the ROM. Maybe it will help somebody !
Hapaxx said:
If I hear Rootk1t correctly, I should flash a kernel with a built-in recovery first... But, doing some research, it looks like you need a working recovery in the first place to flash a custom kernel.
Click to expand...
Click to collapse
yep, one just need to
fastboot flash boot boot.img
Click to expand...
Click to collapse
enter recovery and flash firmware zip, gapps, etc from it.
Root works now, but i can't install TWRP 3.0.2.0 (but XZDualRecovery works).
Sony devices, in particular, tabz don't have separate recovery partition. So you need to flash kernel with built-in recovery (see crDroid, RR, LA firmware threads), or you have to flash TWRP to FOTA partition.
Click to expand...
Click to collapse
Hapaxx said:
So I rebooted the device into fastboot (...), flashed the "boot.img" from the ROM using Flashtool, then rebooted again the device.
Click to expand...
Click to collapse
If i understand correct Hapaxx flashed the boot.img form the LineageOS 14.1 Image? I don't want to install a Custom-ROM. crDroid is for Nexus. Where can i download a Kernel with build-in Recovery for tabz? or can i use the same crDroid also for tabz?
how can i flash the recovery to fota? can i do this with the same *.img or do i need an other image?
i just unlocked my bootloader and i dont know what else to do, i would like to install lineage 14.1 but i dont know what path to follow, i also hit the whole command not allowed thing, and what Hapaxx said, i'm unable to understand, could someone give a clear set of commands to follow? please? what to do in order so i dont brick my tablet.
Hi PiereMallao,
i have the same Odyssey behind me! Sony Xperia Tablet Z SGP321 LTE (16GB)
1. First check Bootloader unlocked with Flashtools 0.9.18.6. Check!
2. Install SGP321_10.1.1.A.1.307_Unbranded.ftf with Flashtools 0.9.18.6. Check!
3. Developertools on. USB-Debugging on. unknown sources on. Check!
4. Root with Doomlord_Rootkit_v18.rar. Check!
5. Check with App "Root-Checker" in Google PlayStore. Check!
6. And now I try to install TWRP for 3 days !
First try with TabZ-lockeddualrecovery2.8.26-RELEASE.combined.zip its ok, but i come only once after the installation in the recovery mode. Afterwards I have it with Vol+ or Vol- tried. It always starts the normal system.
7. With Fastboot -
Code:
fastboot flash recovery twrp.img
fastboot flash recovery twrp.img
target didn't report max-download-size
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.359s
How can i check Bootloader unlock ? In Android Tablet Z i didnt have a keyboard to put in the hex-code *#*#7378423#*#* ?
In Flashtools i checked Bootloader unlock so i have no idea at this Point.
What can I do ?
sorry, i have so solution for this problem. i have given up. theonly way i know to ceck the bl is unlocked or not is flashtool.
I'm having issues with this as well. Trying to install LineageOS 14.1, I can initially get twrp onto the tablet, flash LineageOS 14.1.. boot into it, set up (it is recommended to reboot the tablet once before flashing gapps) ...however, rebooting wipes twrp out. I'm not used to this FOTA thing (first i've ever heard of it) so not sure how to get twrp to 'stick' and not get wiped out
I got it installed this weekend. First secret was fastboot TWRP to boot, not recovery:
Fastboot flash boot twrp-------.img
Make sure you have the right TWRP image.
Then boot into recovery and TWRP comes up.
Flash lineage and gapps.
See:
https://forum.xda-developers.com/xp...de-tutorial-sony-xperia-tablet-z-lte-t3392831
bowguy said:
I got it installed this weekend.
Click to expand...
Click to collapse
I'm a little confused about part 14.
Download app from Play Store : Recovery Manager for Xperia. (done)
Chose FOTAkernel -> Backup. (this makes the app unresponsive for me so i skipped it for now)
Then TWRP -> Download. (done)
then the rest of the steps are confusing. b/c following that guide twrp is already on there (flashed via fastboot), and so why am i replacing the fastboot flashed twrp with the twrp just downloaded in the above step?
and what does the fotakernel have to do with all this? am i suppose to replace the fotakernel with the twrp image downloaded above?
the steps in that guide need more detailed elaboration
x000x said:
I'm a little confused about part 14.
Download app from Play Store : Recovery Manager for Xperia. (done)
Chose FOTAkernel -> Backup. (this makes the app unresponsive for me so i skipped it for now)
Then TWRP -> Download. (done)
then the rest of the steps are confusing. b/c following that guide twrp is already on there (flashed via fastboot), and so why am i replacing the fastboot flashed twrp with the twrp just downloaded in the above step?
and what does the fotakernel have to do with all this? am i suppose to replace the fotakernel with the twrp image downloaded above?
the steps in that guide need more detailed elaboration
Click to expand...
Click to collapse
I never did step 14. Looks straight forward. You should ask this question on that thread
bowguy said:
I never did step 14. Looks straight forward. You should ask this question on that thread
Click to expand...
Click to collapse
Have you rebooted and tried to get back into twrp after you installed the rom? I did the first few steps of the guide a few days back, but every time after flashing the rom it would wipe twrp. I think the only way to get twrp to 'stick' permanently is to complete all the steps
x000x said:
Have you rebooted and tried to get back into twrp after you installed the rom? I did the first few steps of the guide a few days back, but every time after flashing the rom it would wipe twrp. I think the only way to get twrp to 'stick' permanently is to complete all the steps
Click to expand...
Click to collapse
After installing twrp via fastboot per the directions, then reboot into recovery I had few problems. The only issues I had are solved by installing the ROM first - not gapps. Boot and run setup. Then boot recovery and install gapps.
I never had issues with twrp after installing. Power off, power on and rock volume up/volume down until you are in recovery
bowguy said:
After installing twrp via fastboot per the directions, then reboot into recovery I had few problems. The only issues I had are solved by installing the ROM first - not gapps. Boot and run setup. Then boot recovery and install gapps.
I never had issues with twrp after installing. Power off, power on and rock volume up/volume down until you are in recovery
Click to expand...
Click to collapse
Are you using twrp-3.0.2-0-pollux_windy?
x000x said:
Are you using twrp-3.0.2-0-pollux_windy?
Click to expand...
Click to collapse
Yes.
I never bothered with step 14 in the guide. It works fine as is.
P.S.
As per my post on the guide referenced, I installed Rashr and flashed TWRP that way. Seemed to work perfectly. TWRP now shows 3.0.2 which is correct version. No change to system boot. Nice app
Rootk1t said:
@PiereMallao
Sony devices, in particular, tabz don't have separate recovery partition. So you need to flash kernel with built-in recovery (see crDroid, RR, LA firmware threads), or you have to flash TWRP to FOTA partition.
Click to expand...
Click to collapse
Bro please give me link to twrp latest for sgp321 m going to unlock bootloader using" flash tool" is it ok
Please tell me how to flash recovary too
Is it ok if i root my tab after unlocking bootloader using king root ajnd flash using flashify
Is ressuraction remex stableto use tell me bugs
?
i had equal problem
FAILED (remote: Command not allowed)
i also have the same problem with my huawei chc u23 gplay mini bricked no recovery please help
Hi,
i have a problem rooting my Pixel 3.
it already worked, then i installed another rom which i did not like, so i re-installed the stock image from google (9.0.0 PQ1A.181205.006, Dec 2018).
But, here comes the problem, i can not install Magisk. When i do, my Pixel does not boot to system, but boots back to recovery or says can´t load android system.
this is how i do it:
1. flash factory image
2. boot to system
3. boot twrp
4. flash Magisk v18.0
also tried:
1. flash factory image
2. boot twrp directly
3. flash Magisk v18.0
this does not work. what i also tried is patch the stock boot.img with magisk and flash it to boot_a and boot_b. also did not work.
what am i doing wrong?
thnaks in advance for your help!
Spocki990 said:
Hi,
i have a problem rooting my Pixel 3.
it already worked, then i installed another rom which i did not like, so i re-installed the stock image from google (9.0.0 PQ1A.181205.006, Dec 2018).
But, here comes the problem, i can not install Magisk. When i do, my Pixel does not boot to system, but boots back to recovery or says can´t load android system.
this is how i do it:
1. flash factory image
2. boot to system
3. boot twrp
4. flash Magisk v18.0
also tried:
1. flash factory image
2. boot twrp directly
3. flash Magisk v18.0
this does not work. what i also tried is patch the stock boot.img with magisk and flash it to boot_a and boot_b. also did not work.
what am i doing wrong?
thnaks in advance for your help!
Click to expand...
Click to collapse
You've got the kernel and recovery messed up on your device from the failed flash of twrp and magisk. I would start over by flashing the factory image using the flash all batch file with the -w edited out of it. Then try again booting twrp, not flashing it. Once you try to flash the twrp image file you pretty much have to start over with the stock boot image. When you boot into twrp you'll want to allow modifications. You also need to setup a pin or pattern security for your system so twrp will decrypt your device.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks for the hint. It works now. But had to use the patched boot image from this link.
https://www.google.de/amp/s/forum.x...o-root-pixel-3-xl-magisk-t3856712/amp/?espv=1
Spocki990 said:
Thanks for the hint. It works now. But had to use the patched boot image from this link.
https://www.google.de/amp/s/forum.x...o-root-pixel-3-xl-magisk-t3856712/amp/?espv=1
Click to expand...
Click to collapse
you are my hero. My phone was stuck in the situation you describe after installing active edge. I was thinking about wipe my pixel 3 until I saw your post. Thank you !:good:
Was searching in preparation of my K30 arriving, and found an unofficial version of TWRP is now available.
https://www.google.com/amp/s/unofficialtwrp.com/unofficial-twrp-3-3-1-xiaomi-redmi-k30/amp/
Note: I've not tried it myself, as I don't have the phone yet.
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
ddaggebi said:
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
Click to expand...
Click to collapse
please give instalation guide also
ddaggebi said:
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
Click to expand...
Click to collapse
Thanks for the info @ddaggebi
I used the K30 TWRP from https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914 to fastboot boot to TWRP and dump stock boot, recovery and misc (using e.g. `dd=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img`). Then I patched the boot.img with Magisk Manager Canary. :good:
Any idea why that TWRP recovery installer .bat overwrites the misc partition? Temp booting the .img directly with fastboot boot seemed to work fine without their patched misc, so I'm sticking with that for now.
Again, be sure to fastboot boot recovery and then dump your ROM's misc first if you plan on flashing the recovery using that batch script, since you might need to flash it back along with the ROM's recovery for OTAs to succeed.
I can understand rooting here but is twrp installed permanently here? I mean to flash any rom do we always need fastboot command to boot twrp or its staying always and working normally??
Hard_Rock83 said:
I can understand rooting here but is twrp installed permanently here? I mean to flash any rom do we always need fastboot command to boot twrp or its staying always and working normally??
Click to expand...
Click to collapse
Yes. But some features are limited for now.
btw I installed eu rom in case stock rom replaces TWRP to stock recovery.
osm0sis said:
I used the K30 TWRP from https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914 to fastboot boot to TWRP and dump stock boot, recovery and misc. Then I patched the boot.img with Magisk Manager Canary. :good:
Any idea why that TWRP recovery installer .bat overwrites the misc partition? Temp booting the .img directly with fastboot boot seemed to work fine without their patched misc, so I'm sticking with that for now.
Also here is the latest Magisk Canary (20308) patched stock boot.img to simplify rooting for those just getting started on this device. Simply fastboot flash boot it..
Click to expand...
Click to collapse
Ok so the question is can we reboot to recovery normally or we need to manually type fastboot command to boot to recovery..
I am still searching for twrp , which can normally appears while rebooting to recovery
LR.Team twrp-3.4.0-0209 will be installed by default when you install Eu rom.
I can reboot into recovery as normal (by pressing "vol up" & "power" button). To install root, I can simply go to "Advanced" -> "Install Root" or by using boot.img method. One thing which I can't do is deleting (or changing file name) to system file to remove some of the unwanted app.
It works very well
https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914
Followed the instructions on several websites such as this one here at XDA:
https://www.xda-developers.com/how-to-install-twrp/
All goes well until I get to this line:
fastboot flash recovery recovery.img (latest TWRP image, renamed)
The command prompt window just sits there and says "(waiting for any device)"...
Most websites and forum threads seem to indicate that this is a problem with the drivers. Can anyone confirm?
FWIW, I did a total reflash of the latest stock ROM from this thread:
https://forum.xda-developers.com/ga...icial-stock-fw-update-odin-thread-xx-t3825204
so I currently have only the "stock" recovery.
I'd rather not root it quite yet. Help please?
P.S. The phone shows up in Device Manager and for "adb devices"; the phone's bootloader has been unlocked... can't see what I'm missing... I'm using a Windows 10 computer... I removed any screen locking mechanisms (PIN, fingerprint, etc.)...
Follow this instructions https://forum.xda-developers.com/galaxy-note-9/development/recovery-twrp-galaxy-note9-exynos-t4097441
Most samsung device use odin to install twrp
ACC18 said:
Follow this instructions https://forum.xda-developers.com/galaxy-note-9/development/recovery-twrp-galaxy-note9-exynos-t4097441
Most samsung device use odin to install twrp
Click to expand...
Click to collapse
Thanks. I'm trying it with 3.4.0-0
Do I flash this file while I'm still in TWRP? Or do I reboot the phone and go back *into* TWRP to flash it?
>After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
Edit: I tried flashing no-verity-opt while still in TWRP. Got the dreaded:
"Verification failed.
Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."
I *really* tried to follow the instructions exactly, and think I did.
Was it because I tried to flash 3.4.0-0...?
I am currently re-flashing the stock firmware again.
Dougmeister said:
Thanks. I'm trying it with 3.4.0-0
Do I flash this file while I'm still in TWRP? Or do I reboot the phone and go back *into* TWRP to flash it?
>After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
Edit: I tried flashing no-verity-opt while still in TWRP. Got the dreaded:
"Verification failed.
Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."
I *really* tried to follow the instructions exactly, and think I did.
Was it because I tried to flash 3.4.0-0...?
I am currently re-flashing the stock firmware again.
Click to expand...
Click to collapse
You need to format data after install twrp. This is avoiding internal data encrypted.
After twrp installed, do format data from twrp. Of course all of ur data on internal erased. And then take custom rom. I suggest devbase rom, this have "no verity encrypt" when u install this rom. Devbase is stock firmware for easy upgrade for rooted phone. And this is easy to install for beginner
Sorry for bad English
ACC18 said:
You need to format data after install twrp. This is avoiding internal data encrypted.
After twrp installed, do format data from twrp. Of course all of ur data on internal erased. And then take custom rom. I suggest devbase rom, this have "no verity encrypt" when u install this rom. Devbase is stock firmware for easy upgrade for rooted phone. And this is easy to install for beginner
Sorry for bad English
Click to expand...
Click to collapse
No worries. Thank you for your help.
I use Odin to install the Devbase ROM, right? Or can I use TWRP?
Edit: apparently it works just fine to install it with TWRP.
Thank you so much. This time TWRP works just fine for me and the new ROM is great.
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
stvmnn said:
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
Click to expand...
Click to collapse
Hi.
I´m interested. I´m not able to root the MI 8A MIUI 11 global 11.0.2.0 QCPMIXM. I achieved install TWRP . But I can´t install MAGISK . It don´t show me any error, but it isn´t installed. I ´ve tried many versions 20.0, 20.1, 20.2, 20.3 20.4 21.0 and 21.1. neither of them are successfull with TWRP.
Neither with magisk manager apk 7.5.1 and above. These are installed but then I download magisk 20.4 version, but this isn´t installed.
how did you it? please.
Yajirobai said:
Hi.
I´m interested. I´m not able to root the MI 8A MIUI 11 global 11.0.2.0 QCPMIXM. I achieved install TWRP . But I can´t install MAGISK . It don´t show me any error, but it isn´t installed. I ´ve tried many versions 20.0, 20.1, 20.2, 20.3 20.4 21.0 and 21.1. neither of them are successfull with TWRP.
Neither with magisk manager apk 7.5.1 and above. These are installed but then I download magisk 20.4 version, but this isn´t installed.
how did you it? please.
Click to expand...
Click to collapse
Your bootloader needs to be unlocked and USB debugging enabled first of course. TWRP Recovery should be installed.
To do this, you need the adb and fastboot binaries installed on a PC/Laptop. I use Ubuntu and installing these is trivial via apt package manager:
Debian based:
Code:
sudo apt install adb fastboot
RedHat based:
Code:
yum install adb fastboot
If you use Windows, the install and use of these binaries is a little different. I don't use Windows so you'll have to do a quick search to find out how to install and use these binaries. The commands listed below will work no matter what OS you use.
Connect your phone to your PC/Laptop via it's USB cable and reboot it to TWRP Recovery:
Power off the phone, then power on while holding the volume up button until you see the TWRP logo. Log into TWRP to decrypt.
Next, you need to pull the current boot.img from your ROM to patch it for root access:
Code:
adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
There should be a boot.img on your phone's internal storage, copy it to your PC/Laptop. From TWRP, reboot your phone to fastboot.
Now, we'll use this most excellent, free resource to patch the boot.img file which will give root access:
https://patcher.yaalex.xyz/
Check the 'Include Magisk' checkbox on the website before submitting image.
Important: After you upload your boot.img file to the website, be patient. This could take 10 minutes or more to complete, just wait until you get a prompt to download the patched image. You will be provided a patched_boot.img file from the website once it is finished.
Finally, all you need to do is flash the patched_boot.img to your phone:
Code:
fastboot flash boot patched_boot.img
Boot your phone to the ROM:
Code:
fastboot reboot
Install Magisk Manager if you haven't already, and enable Magisk Hide in the settings. Magisk Manager should report root access is available and SafetyNet test should pass.
I typed all this up from memory so if you run into trouble or are confused by any step, let me know and I will gladly clarify/fix the steps.
I hope this helps others achieve root on this phone. Let me know how it goes and happy de-bloating!
Rollback instructions:
If your phone fails to boot don't panic. You can restore your original boot.img if needed to regain access. Reboot your phone to fastboot:
Boot phone while holding the down volume button until you see the fastboot logo.
Next, flash the original boot.img to the boot partition:
Code:
fastboot flash boot boot.img
Now just reboot to ROM and all should be restored:
Code:
fastboot reboot
stvmnn said:
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
Click to expand...
Click to collapse
Iirc redmi 8a is an ab device, and yes this device is as customisable as any other Qualcomm. What gsi image are you flashing?
Actually he is not way off ..... i am NOT able to find a Custom Non MIUI ROM with full VoLTE support. VoLTE fix for GSI's ( if at all it worked ! ) does not work for Havoc. twrp root is all good. I want a NON MIUI ROM that can regional variants ( Europe and Asia ) and supports VoLTE