I'm trying to install Hex Kernel on my Mi A2 with Pie, but I'm unable to use TWRP in it. TWRP doesn't boot, and doing the "fastboot boot twrp.img" makes the phone start booting and just shut down. I need another method to flash the kernel.
Can anybody help me, please?
Cuesta4 said:
I'm trying to install Hex Kernel on my Mi A2 with Pie, but I'm unable to use TWRP in it. TWRP doesn't boot, and doing the "fastboot boot twrp.img" makes the phone start booting and just shut down. I need another method to flash the kernel.
Can anybody help me, please?
Click to expand...
Click to collapse
Your bootloader is unlocked?
Aziziamran said:
Your bootloader is unlocked?
Click to expand...
Click to collapse
Yes. Both for normal and critical flashing.
Sent from my Mi A2 using XDA Labs
Cuesta4 said:
Yes. Both for normal and critical flashing.
Click to expand...
Click to collapse
Maybe you should try another recovery such as PBRP or unofficial TWRP..
Aziziamran said:
Maybe you should try another recovery such as PBRP or unofficial TWRP..
Click to expand...
Click to collapse
Tried both already, neither worked. I went back to Oreo and now it's all ok. Better wait for a decent Pie version.
Sent from my Mi A2 using XDA Labs
@Cuesta4 How came back to Oreo since Pie?
Yeah/%# said:
@Cuesta4 How came back to Oreo since Pie?
Click to expand...
Click to collapse
Your phone is Mi A2 or Mi 6X?
If it's the first, just unlock the bootloader and critical flashing then download any stock Oreo ROM and flash it through EDL. You'll then be able to boot custom TWRP and flash a Custom ROM. I'm using CRDroid Pie with Hex Kernel. It's not my favorite, but it's the most stable.
Cuesta4 said:
I'm trying to install Hex Kernel on my Mi A2 with Pie, but I'm unable to use TWRP in it. TWRP doesn't boot, and doing the "fastboot boot twrp.img" makes the phone start booting and just shut down. I need another method to flash the kernel.
Can anybody help me, please?
Click to expand...
Click to collapse
Try installing Hex in the active (on which your is is installed) partition.
Like I have Havoc installed on b, twrp and Magisk installed on a. Installing Hex on b would be my best shot. You can toggle active partitions from reboot menu in twrp.
New TWRP available now for PIE
My friend TWRP 3.3 Supporting Android Pie (version 3.3) is available now.
So all you gotta do is Ublock bootloader . normal and critically.
boot twrp 3.3 using "fastboot boot twrp.img"
copy the hex kernal you want to flash in your phones internal storage and flash it.
this works fine i have done it successfully.
Related
Removed
Which TWRP did you try flashing? Official or modified one?
Try with modified 3.0.2-22, if you haven't yet.
Sent from my OnePlus 3 using Tapatalk
Thanks for the reply.
Flashed modified 3.0.2-22 before flashing new CE build.
Post corrupting recovery partition, tried flashing back the same recovery...resulting in blackscreen tho.
Explorer23 said:
Which TWRP did you try flashing? Official or modified one?
Try with modified 3.0.2-22, if you haven't yet.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Did you try mega unbrick guide?
Sent from my ONEPLUS A3000 using Tapatalk
yes, tried with MSMDownloadTool from that post, since the device isn't in Qualcomm diagnostic mode, that didn't help much.
Explorer23 said:
Which TWRP did you try flashing? Official or modified one?
Try with modified 3.0.2-22, if you haven't yet.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
tdamocles said:
Did you try mega unbrick guide?
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
I'm facing almost same situation, haven't flashed wrong twrp, have tried 3.0.2.22 and screwed up...not able to flash any other twrp. Have side loaded OOS 3.5.5 and rebooted to get official recovery and succeeded as well but as soon as have flashed official twrp resulting black screen. Again flashed 3.0.2.22 through fastboot mode and working... In short, I can't use any recovery other then 3.0.2.22. Any guidance and help would be highly appreciated....
Sent from Tapatalk
I also use .22 recovery and no problem. The problem is not the recovery, its a noob problem.
indeed that seems to be the problem here.
Tried flashing modified recovery again (-22), successfully booted into recovery now.
What's causing this issue, any pointers guys ?
can't go back to official twrp for some reason.
deeplyyoung said:
I'm facing almost same situation, haven't flashed wrong twrp, have tried 3.0.2.22 and screwed up...not able to flash any other twrp. Have side loaded OOS 3.5.5 and rebooted to get official recovery and succeeded as well but as soon as have flashed official twrp resulting black screen. Again flashed 3.0.2.22 through fastboot mode and working... In short, I can't use any recovery other then 3.0.2.22. Any guidance and help would be highly appreciated....
Sent from Tapatalk
Click to expand...
Click to collapse
Well technically we should be able to get back to official recovery.
Care to explain the "noob" problem mate ?
Schrotty35 said:
I also use .22 recovery and no problem. The problem is not the recovery, its a noob problem.
Click to expand...
Click to collapse
Schrotty35 said:
I also use .22 recovery and no problem. The problem is not the recovery, its a noob problem.
Click to expand...
Click to collapse
Well accepted its noob problem, appreciating if you help us, instead of pointing noob @#$%.
Want to use multiROM but not able to flash any other recovery.
Any other way to hard reset the device which fixed recovery partitions (I'm sure we messed with partitions).
Edit: even I'm using 3.0.2.22 without any issues but if I want to use any other recovery(official twrp or multiROM twrp, not able to boot into it, truly noob thing as per your post)
Official TWRP is not compatible with CE ROMs. Try first flashing official OOS (3.2.7 or older) with -22 and then flashing official TWRP.
Sent from my OnePlus 3 using Tapatalk
deeplyyoung said:
I'm facing almost same situation, haven't flashed wrong twrp, have tried 3.0.2.22 and screwed up...not able to flash any other twrp. Have side loaded OOS 3.5.5 and rebooted to get official recovery and succeeded as well but as soon as have flashed official twrp resulting black screen. Again flashed 3.0.2.22 through fastboot mode and working... In short, I can't use any recovery other then 3.0.2.22. Any guidance and help would be highly appreciated....
Sent from Tapatalk
Click to expand...
Click to collapse
I'm trying to get stock recovery I have modified twrp but whenever I flash the cb full zip twrp doesn't get overwritten
To Reproduce the issue.
1. Flash modified TWRP (-22) version via fastboot
2. Flash CE ROM latest 3.5.5 from recovery
3. Reboot into system, successfully booted.
4. Tried flashing official TWRP, results in Blackscreen (in my case flashed incorrect TWRP, then flashed official one)
5. flashing back (-22) version of TWRP, recovery seems working...however if one wants to switch to official or MultiRom's TWRP, results in Blackscreen.
Hope this gives detailed understanding
Edit:
Gonna try the same with 3.2.7 OOS. Thanks Mate
Explorer23 said:
Official TWRP is not compatible with CE ROMs. Try first flashing official OOS (3.2.7 or older) with -22 and then flashing official TWRP.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Explorer23 said:
Official TWRP is not compatible with CE ROMs. Try first flashing official OOS (3.2.7 or older) with -22 and then flashing official TWRP.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
thanks Buddy, appreciated your help, gonna try this ASAP & will revert with results.
not able to get full zip of 3.2.7, trying with 3.2.6
Yeah, flashing full stock oos might do the trick, there's something related to firmware, it's a long story to understand and I'm not fully getting it, anyway, flash the full stock, boot it up, your device may get encrypted again and then flash the official twrp via fastboot, don't use flashify
I'll try to keep an eye out here rather than on the multi-boot thread
Sent from my Darkside of Oneplus 3
power off phone, keep pressed vol-up+vol-down and connect usb cable, phone will enter qualcomm download mode, then flash with MSM Download Tool.
Explorer23 said:
Official TWRP is not compatible with CE ROMs. Try first flashing official OOS (3.2.7 or older) with -22 and then flashing official TWRP.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
xanthrax said:
Yeah, flashing full stock oos might do the trick, there's something related to firmware, it's a long story to understand and I'm not fully getting it, anyway, flash the full stock, boot it up, your device may get encrypted again and then flash the official twrp via fastboot, don't use flashify
I'll try to keep an eye out here rather than on the multi-boot thread
Sent from my Darkside of Oneplus 3
Click to expand...
Click to collapse
Yesssss!! Trick worked, have flashed FULL zip OnePlus3Oxygen_16_OTA_015_all_1609141252_c38077177cfc4e74 over OnePlus3Oxygen_16_OTA_007_all_1610310039_bc5bc09fd9af4ceb with stock recovery, device encrypted again but no issues, then fastboot official TWRP worked & then fastboot MRTWRP worked....
now my Question:- pls help, enable us to get some knowledge
I want to use MultiROM, so decryption procedure will do.
1} if i again flash OnePlus 3 OxygenOS 3.5.5 Community Build as primary using MultiROM twrp, is it gonna work?
2} I want to use DU(MM), PAC-MAN(MM), exodus, MIUI, aicp (7.1) or HydrogenOS H2OS whats the best possibilities & way.
3} which one can be use as primary
4} can i flash FreedomOS CE 1.10 [OOS 3.5.5 CB] using multiROM twrp as primary?
5} can I swap FreedomOS CE 1.10 [OOS 3.5.5 CB] as secondary & flash HydrogenOS H2OS as primary?
I wish just to fastboot TWRP and then to flash an eu ROM.
Which twrp.img to choose?
zost said:
I wish just to fastboot TWRP and then to flash an eu ROM.
Which twrp.img to choose?
Click to expand...
Click to collapse
You can choose the one you like, both xuefer and mine will boot without a problem using "fastboot boot recovery.img".
If you have any problem just contact me!
Many thanks for the answer, I will use yourTWRP, being xuefer's TWRP is still in alpha status.
Tried iscle TWRP today, with no success. The same problem as desribed by fendetestasxx in that TWRP thread.
zost said:
Tried iscle TWRP today, with no success. The same problem as desribed by fendetestasxx in that TWRP thread.
Click to expand...
Click to collapse
Yeah it seems like my twrp gets overwritten by the stock one in the official miui builds... you can use xuefer recovery if you want, it works very well as well.
Edit: as I just said in the TWRP post: If you are using the STOCK MIUI ROM, you will need to remove the file "/system/recovery-from-boot.p" using the file manager inside TWRP or otherwise it will get replaced with the stock MIUI recovery.
I flashed latest TWRP with fastboot command on CMD.
TWRP works but after I reset the TWRP was deleted and I can get STOCK recovery.
I can boot up TWRP only if I connect my device to computer and use command FASTBOOT BOOT RECOVERY.IMG
Why?
If u flashed a rom,.then before booting you must flash the root file or a custom kernel in order to keep the TWRP.
Unleashed by my rooted OP3T on 8.0
I do not flashing another rom, only new open beta versions and flash files.
saarxee said:
I do not flashing another rom, only new open beta versions and flash files.
Click to expand...
Click to collapse
New open beta is another Rom buddy.
Unleashed by my rooted OP3T on 8.0
But I dont need custom kernel and root.
saarxee said:
But I dont need custom kernel and root.
Click to expand...
Click to collapse
You have to flash at least Magisk/SuperSU or custom kernel in order to keep TWRP intact after each reboot. Not sure about modified stock kernels with dm-verity and forceencrypt disabled, they may work too.
This is the nature of stock ROM.
saarxee said:
But I dont need custom kernel and root.
Click to expand...
Click to collapse
OOS enforces encryption and restores the stock recovery when you reboot your phone.
Custom ROMs, custom kernels, and Magisk all prevent that from happening.
If you want plain OOS (stable or Open Beta) and keep TWRP, then use Xennet's patched boot image. See https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053
Sent from my OnePlus3T using XDA Labs
I flashed magisk on TWRP and TWRP deleted again after restart.
What can I do?
Reflash your current ROM via TWRP and flash Magisk right after ROM without restarting
Today I flashed open beta 24 and after that Magisk and wipe dalvik and restart recovery and I got stock recovery and dont TWRP.
saarxee said:
Today I flashed open beta 24 and after that Magisk and wipe dalvik and restart recovery and I got stock recovery and dont TWRP.
Click to expand...
Click to collapse
Like I said, use Xennet's patched boot image.
Sent from my OnePlus3T using XDA Labs
What to do about this file? flash it and install TWRP again? or only flash it and restart to recovery?
Why I need to change my boot file? If my device dont booting up after the flash?
saarxee said:
Why I need to change my boot file? If my device dont booting up after the flash?
Click to expand...
Click to collapse
Because stock will always revert to stock recovery.
If the device doesn't boot, then you're using an incompatible boot image
(it seems that Magisk/SuperSU isn't enough)
I flashed this boot patched image and choose restart to recovery and stock recovery again...
I have the same problem - twrp gets erased after booting in OS Since beta 24
I don't know guys what's wrong with your devices, I'm using Open Beta 24 with custom kernel and TWRP boots everytime.
I use stock kernel, maybe that is the clue.
Viktorrr said:
I use stock kernel, maybe that is the clue.
Click to expand...
Click to collapse
Then maybe you should flash the modified kernel that is especially modified to not restore the stock recovery.....
gizahNL said:
Then maybe you should flash the modified kernel that is especially modified to not restore the stock recovery.....
Click to expand...
Click to collapse
Correct, as I pointed out in this post https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867/post76049932
Sent from my OnePlus3T using XDA Labs
gizahNL said:
Then maybe you should flash the modified kernel that is especially modified to not restore the stock recovery.....
Click to expand...
Click to collapse
BillGoss said:
Correct, as I pointed out in this post https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867/post76049932
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
OP said that it didn't work:
I flashed this boot patched image and choose restart to recovery and stock recovery again...
Click to expand...
Click to collapse
my mi a2 started bootlooping after a certain update, but did not do anything about it because at second or third forced reboot it will boot normally, now it started acting up and it would not boot after several dozen reboots so i tried to flash the lastest stock rom, i unlocked the bootloader and started flashing but when the flashing reached vendor b phone rebooted by itself entering the bootloop, i tried this many times, same result flashing ended at vendor , after changing the partition to a it booted and tried a software update then again after download it entered bootlooping , so i tied again to flash several times with different stock roms, even tried miflash in edl mode, everything is the same, now i managed to boot again after the last flashing but if i restart it it for shure go into a bootloop again, i dont know what else to do, i dont know why, but pressing power and vol + does not take me into recovery, only vol- takes me to fastboot, also tried to boot into twrp via fastboot but it says ok the screen lits up and then again bootloop, please please anyone can offer some assistance ?? Thanks
try flash a custom rom, if flash is successful and phone boots, try to revert it to stock rom again via miflash and used version 11.0.14.
Sent from my Xiaomi Mi A2 using Tapatalk
How to flash custom ? I cant boot into twrp, is there other way ?
tedulus said:
How to flash custom ? I cant boot into twrp, is there other way ?
Click to expand...
Click to collapse
unlock your bootloader first, there is already a guide in this group related to your question, kindly search it.
Sent from my Xiaomi Mi A2 using Tapatalk
1ntr0v3rt3ch said:
unlock your bootloader first, there is already a guide in this group related to your question, kindly search it.
Sent from my Xiaomi Mi A2 using Tapatalk
Click to expand...
Click to collapse
My bootloader is unlocked.
1ntr0v3rt3ch said:
unlock your bootloader first, there is already a guide in this group related to your question, kindly search it.
Sent from my Xiaomi Mi A2 using Tapatalk
Click to expand...
Click to collapse
if i try "fastboot boot twrp.img" it says ok the screen goes dark and it reboots in bootloop
Maybe try extract a custom rom e.g.
https://forum.xda-developers.com/t/rom-11-official-pixel-extended-rom-2021-1-10.4215727/ , convert dat.br to .img by googling and find useful tools and then fastboot flash the .img files?
Hi.
So I recently found that my phone is using boot_b to boot up the phone, and I entered TWRP and change the boot solt to boot_a. In result, the device kept rebooting in the first page of boot (Powered by android page). And after I switch back to boot slot b the issue disappear. At first I thought the boot image was currupted and I flash the downloaded rom from xiaomirom.com and flash it using miflash via fastboot. The issue presists after flashing even without any modification (magisk/twrp/etc.). Then I thought that maybe the flash didnt include boot_a so I did:
`fastboot boot TWRP.img`
and then change the boot slot to boot_a and flashed again via fastboot. The issue still presists after that and now I have no idea what is wrong.
So I just want to ask that is anyone experiencing the same issue as me? And also how to fix the issue?
Thanks.
MiracleYueYue said:
Hi.
So I recently found that my phone is using boot_b to boot up the phone, and I entered TWRP and change the boot solt to boot_a. In result, the device kept rebooting in the first page of boot (Powered by android page). And after I switch back to boot slot b the issue disappear. At first I thought the boot image was currupted and I flash the downloaded rom from xiaomirom.com and flash it using miflash via fastboot. The issue presists after flashing even without any modification (magisk/twrp/etc.). Then I thought that maybe the flash didnt include boot_a so I did:
`fastboot boot TWRP.img`
and then change the boot slot to boot_a and flashed again via fastboot. The issue still presists after that and now I have no idea what is wrong.
So I just want to ask that is anyone experiencing the same issue as me? And also how to fix the issue?
Thanks.
Click to expand...
Click to collapse
Start by restoring the phone with this tool.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Then downloaded an old Xiaomi Eu rom fastboot.zip and installed it in fastboot mode (scrip included in the zip first install.bat).
Then install the Twrp and update via OTA.
NOSS8 said:
Start by restoring the phone with this tool.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Then downloaded an old Xiaomi Eu rom fastboot.zip and installed it in fastboot mode (scrip included in the zip first install.bat).
Then install the Twrp and update via OTA.
Click to expand...
Click to collapse
Hi. Thanks for your reply.
I have been used this tool to flash my phone. And I tested with another Xiaomi 12 Pro to make sure that the rom is correct. Turns out that the rom IS correct...
MiracleYueYue said:
Hi. Thanks for your reply.
I have been used this tool to flash my phone. And I tested with another Xiaomi 12 Pro to make sure that the rom is correct. Turns out that the rom IS correct...
Click to expand...
Click to collapse
I thought you want to install the TWRP to install a Xiaomi EU rom but maybe this is not the case.
The device is bought in china btw.
NOSS8 said:
I thought you want to install the TWRP to install a Xiaomi EU rom but maybe this is not the case.
Click to expand...
Click to collapse
No... I am just trying to slove the reboot issue with _a
MiracleYueYue said:
No... I am just trying to slove the reboot issue with _a
Click to expand...
Click to collapse
Dont relock the bootloader with Miflash.
Don't worry about the A/B slots.
NOSS8 said:
Dont relock the bootloader with Miflash.
Don't worry about the A/B slots.
Click to expand...
Click to collapse
I never lock the BL back.. lol
So the boot issue with _a doesn't matters? Dont know when the issue start but im pretty worried for the issue
MiracleYueYue said:
I never lock the BL back.. lol
So the boot issue with _a doesn't matters? Dont know when the issue start but im pretty worried for the issue
Click to expand...
Click to collapse
I also have this phone with TWRP, it seems to me that when I installed it I did not select any slot, by default it installs on A.
NOSS8 said:
I also have this phone with TWRP, it seems to me that when I installed it I did not select any slot, by default it installs on A.
Click to expand...
Click to collapse
Ummm I dont think we are on the same page.
I mean that if i change the boot slot to A in the Reboot secrion in TWRP the SYSTEM jams ans reboot when it tries to boot, and slot B boots normally.
MiracleYueYue said:
Ummm I dont think we are on the same page.
I mean that if i change the boot slot to A in the Reboot secrion in TWRP the SYSTEM jams ans reboot when it tries to boot, and slot B boots normally.
Click to expand...
Click to collapse
Why Install TWRP?
Use Miflash and that's it.
MiracleYueYue said:
Hi.
So I recently found that my phone is using boot_b to boot up the phone, and I entered TWRP and change the boot solt to boot_a. In result, the device kept rebooting in the first page of boot (Powered by android page). And after I switch back to boot slot b the issue disappear. At first I thought the boot image was currupted and I flash the downloaded rom from xiaomirom.com and flash it using miflash via fastboot. The issue presists after flashing even without any modification (magisk/twrp/etc.). Then I thought that maybe the flash didnt include boot_a so I did:
`fastboot boot TWRP.img`
and then change the boot slot to boot_a and flashed again via fastboot. The issue still presists after that and now I have no idea what is wrong.
So I just want to ask that is anyone experiencing the same issue as me? And also how to fix the issue?
Thanks.
Click to expand...
Click to collapse
Most probable reason is that you have previous version or ROM in slot A, while in slop B is the latest, one you are using. Same has happened to me. You can download recovery version of the ROM you are using and flash it in TWRP to slot A. I did that with Global ROM V13.0.7.0.SLBMIXM and now I have it on both slots working fine.