Hi, I was trying to rollback my one plus 10 pro from android 13 to android 12. But then it failed. Luckily my bootloader is unlocked, so i tried fastbootenhanced but still no luck. Do i need to msm my device now? I can still access fastboot, fastbootd and recovery. Any insight to what should i do? and I think partitions are messed up as it requires me to check "ignore unknown partition".
Here's a link to roll back ....
Don't use this link it might not be trusted.
to downgrade from android 13 to android 12 you must use rollback package. otherwise your device will brick and you can only save it with msm
Related
Hi everyone,
While trying to install LineageOS (following the guide here) my phone is now stuck on "Your device is booting".
Note that I had my phone rooted before so OEM unlock and TWRP were already done/installed.
Unfortunately my backup seems to not have worked and I believe I might have erased more than I should, including system and vendor. So now I'm stuck with installing any OS to be honest.
My phone is an ARM64, prague, WAS-LX1A.
Can anyone help me please?
Thanks!
I was able to use the dload method to get back to stock rom.
Hello,
I am on MIUI 10.3.5 (PFKINXM - Android version 9 PKQ1.181121.001) and it is showing no updates. When I click on "download latest package", it says "Can't download, wait 1 - 2 mins and retry". I downloaded 10.4.8 package manually and choose update package. This gives me a message saying "this rom is in beta testing, are you sure you have a beta account linked". Bought 2 days back from flipkart.
How do I update it to android 10?
I have faced the same issue but now I have updated to 4.8 after unlocking
u have 2 options wait for miui 11 or to unlock your bootloader and flash the latest update which will erase all your data
even if you choose to unlock booloader and updating from custom recovery you will face an issue which says
'this is for raphelin., your device is raphel' error 7 in TWRP
to solve it you need to edit the update_script file
do note that this process is quite tricky and you can brick your device or else your device may stuck in bootloops
trinadhchinna7 said:
I have faced the same issue but now I have updated to 4.8 after unlocking
u have 2 options wait for miui 11 or to unlock your bootloader and flash the latest update which will erase all your data
even if you choose to unlock booloader and updating from custom recovery you will face an issue which says
'this is for raphelin., your device is raphel' error 7 in TWRP
to solve it you need to edit the update_script file
do note that this process is quite tricky and you can brick your device or else your device may stuck in bootloops
Click to expand...
Click to collapse
Thank you very much for your reply. So I am not alone with this kind of issue.
Will wait for my 168 hours to complete before I can unlock the bootloader. Then will update it , keeping in mind your advice.
Thanks again
trinadhchinna7 said:
I have faced the same issue but now I have updated to 4.8 after unlocking
u have 2 options wait for miui 11 or to unlock your bootloader and flash the latest update which will erase all your data
even if you choose to unlock booloader and updating from custom recovery you will face an issue which says
'this is for raphelin., your device is raphel' error 7 in TWRP
to solve it you need to edit the update_script file
do note that this process is quite tricky and you can brick your device or else your device may stuck in bootloops
Click to expand...
Click to collapse
But do you know if MIUI 11 brings android 10 update as well?
Hey,
I need HELP.
I have Redmi 9. Unfortunately, I do not remember which ROM and which MIUI was installed. I think it was 12 GLOBAL.
I've tried to install TWRP and magisk, though something went wrong and I'm now in bootloop. I can get into fastboot but don't know how to continue from this position,
My thoughts that I've tried to install TWRP or magisk that don't fit to my phone.
Phone is unlocked.
unofficial twrp 3.4.2 Root Xiaomi Redmi 9 (Lancelot) claims to be a working TWRP and instructions for installing Magisk. (I don't have the phone, so I can't test it.)
nir182 said:
Hey,
I need HELP.
I have Redmi 9. Unfortunately, I do not remember which ROM and which MIUI was installed. I think it was 12 GLOBAL.
I've tried to install TWRP and magisk, though something went wrong and I'm now in bootloop. I can get into fastboot but don't know how to continue from this position,
My thoughts that I've tried to install TWRP or magisk that don't fit to my phone.
Phone is unlocked.
Click to expand...
Click to collapse
well your best bet is to download the stock rom and flash it with sp flash tool using the brom bypass, only thing you have to know is which exact miui version you had, otherwise if you have an unlocked bootloader you don't have to worry that much as it will not harm your phone
razers211 said:
well your best bet is to download the stock rom and flash it with sp flash tool using the brom bypass, only thing you have to know is which exact miui version you had, otherwise if you have an unlocked bootloader you don't have to worry that much as it will not harm your phone
Click to expand...
Click to collapse
can it be done if cant go into fastboot mode ?
be careful when flashing your stock rom do not flash with format all mode or else you imei will be lost
Hello all. first post here as i only recently found this great site. So ive been wanting a rooted phoje for a long time now as i iswd to jailbreak my uphone back when i used apple and hadnt learned of Androida greatness. I got a pixel 5a and i love it! Its different and i just love it. Maybe more than my s21ultra even. Anyways I updated to android 12 beta and then tried to root my device. I've never done this before so i tried to learn as much as possible. Anyways I followed the magisk tutorials and unlocked my boot loader and downloaded the boot.IMG for Android 12 and patched the image then did the fastboot and adb stuff only to end up with my phone not working. Clearly I did something wrong. It originally said on the fastboot menu failed to load or verify boot image. And was stuck on that menu. Tried to recover reboot and it stayed the same. Somehow I got it to restart then it was in a bootloop going to google to the unlocked bootloader warning screen over and over. I got frustrated and left it. It died and put it on the charger and it was in rescue or recovery mode saying no command. I got it into recovery menu and tried to factory reset and now it boot to the white google screen. I wanna flash it back to android 11 that it came with so I can eventually try and root it again as that seems much more successful then Android 12. ANy help is very appreciated and I am a SUPER noob at this and don't know about any of it so please keep that in mind when replying. Thanks
You needed to disable verification and dm-verity when flashing the android 12 beta.. You're stuck at fastboot now because of this..
The solution is to use the Google flashing tool, and re-flash android 11 w/ wiping the data selected.. You can try without having wipe data selected, up to you.
P.S. while I recommend you stay on Android 11 if you want a less buggy rooted phone, follow guide #1 on this thread here if you wanna use android 12 beta w/ Magisk:
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com
bobpiesz said:
You needed to disable verification and dm-verity when flashing the android 12 beta.. You're stuck at fastboot now because of this..
The solution is to use the Google flashing tool, and re-flash android 11 w/ wiping the data selected.. You can try without having wipe data selected, up to you.
P.S. while I recommend you stay on Android 11 if you want a less buggy rooted phone, follow guide #1 on this thread here if you wanna use android 12 beta w/ Magisk:
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the help I really appreciate it! I'm gonna give it an attempt right now.
I am facing the same type of problems for so long now.
Seems Magisk breaks booting when on the 12 S bootloaders :c even with disable-verity and disable verification in any step of the process
Disabling verity and verification is no longer required with Magisk 23016.
Follow my guide here, use the Factory Image method.
After some time I got a second Axon 10 and I spend some time figuring out what was possible with this phone in terms of root, custom ROM etc.
My results are as follows.
What is working:
Android 9 + Magisk and TWRP
Android 9 + TWRP + Custom ROMs (LineageOS 16 and patched GSI)
Android 10 + Magisk and TWRP
Android 10 + Magisk and MicroG flashed via Magisk (= stock ROM without Google Services)
Android 11 + Magisk
What is not working:
Android 11 + Magisk + TWRP (TWRP logo flashes randomly but TWRP does not load).
Android 11 + Magisk + MicroG (the nanolx patching script does not work with Android 11 as of yet)
Encryption in Custom ROMs
Method to flash files via EDL
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
Unlock Bootloader:
Before you try any of the files, you MUST unlock your bootloader!
BACKUP of your data as it will be lost!
Download the EDL tool from this Thread
If your phone is not on android 9, you must go back to Android 9 first. e.g. by using my Android 9 1.9 backup.
After you restored it, restart while holding the volume + key and do a factory reset / format data.
Boot into EDL again and unlock the bootloader.
Now you are on android 9 with unlocked bootloader.
From here you can follow the other guides in the form and install TWRP or lineageos. Or flash one of my files below.
Flashing EDL files:
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
I put all my files into this MEGA account: MEGA
Android 10 version 2.9 Magisk + TWRP
Android 11 version 3.5 stock
Android 11 version 3.5 Magisk
Android 10 version 2.10 stock
Android 10 version 2.10 Magisk (TWRP can be flashed with Magisk)
Install MicroG:
Only works on Android 9 and 10.
Before you install MicroG you must patch the stock ROM to allow for signature spoofing.
The patcher script I used is on https://downloads.nanolx.org/NanoDroid/Stable/ When I write these lines the up-to-date-version is NanoDroid-patcher-23.1.2.20210117.zip
Reboot.
Install MicroG from the Magisk repository.
After a restart there will be error messages that google apps keep crashing. With each warning, disable the apps one by one.
When you reboot again, no errors should appear and MicroG should report that it is fully working.
You can add the Bromite Framework and give F-droid system rights. Both are available from the Magisk repo.
Updates will likely install the Google apps again and uninstall Magisk...
Revive phone:
Not really related, but I bricked my phone several times.
If your phones does not boot anymore or hangs in a bootloop, try accessing the EDL mode.
The easy way:
Boot while holding volume -
The hard way:
Old Volume +, volume - and power until you end up in EDL. The screen will be black, so it helps if you have the Phone connected to Windows and can hear the system sound when the USB sees a connection.
In anyway you can then use the EDL tool to restore / flash an EDL image.
On custom ROM support:
Well there is LineageOS 16 by Unjustified Dev. https://forum.xda-developers.com/t/rom-unofficial-zte-axon-10-pro-9-lineageos-16-0.3992127/ It works well. But has a patch level that is outdated by now.
On top of it you can install the GSI ROMs created by Rafyvitto. The latest one is Resurrection Remix https://forum.xda-developers.com/t/...nofficial-resurrection-remix-q-8-6-7.4172527/
with a security patch level of mid 2021. Which is recent enough to use. The stock roms are not much better.
With both Custom ROMs, encryption is not working which poses a privacy/security risk when your phone is stolen. Do not forget that your phone does not only contain your photos and data but also your passwords to your accounts.
Added Android 10 2.10 files.
Its nice to see anything new for this phone. I wish I can use these roms but I have the American version.
Hi and thanks for your work and your files.
I'm stuck on "Loading the programmer: prog_ufs_firehose_sdm855.elf >>>", if I try to recover your edl files with EDL Tool, v 3.25.
I have to choose option 2: "Restore Full EDL from backup", right?
Is there a way to check if the bootlaoder is really unlocked?
Thanks in advance
OK, I was able to solve the problem with the "programmer" and try the backups. The next step was almost clear. The device is stuck in bootloop. I've already tried all the backups I could find on Mega. After the EDL Tool has done its work and the device has restarted, the mobile phone goes into the boot loop. And now? So the starting position was: Android 9 with an open bootloader. Maybe someone has an idea?
After I couldn't get the device out of the bootloop, I flashed the A2020G_PRO_V1.6_FULL_EDL via MiFlash and then did an OTA update to 1.8.
Then I tried unlocking the bootloader again, which unfortunately didn't work. The flash is carried out without errors, but the device then apparently does not start in the desired Fastboot mode.
Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.
brian117 said:
Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.
Click to expand...
Click to collapse
Maybe you need to switch the slot in TWRP. It sounds as if you install it to the other slot (like A) an then boot B. Or vice versa.