Related
Hello, I tried to install the latest paranoid android but now have a system that only freezes on boot or turns on into fastboot mode. The following is what I have done:
unlock bootloader
(system 23.1.A.1.28)
root using exploit for 5.0.2 with super su
installed recovery apk which installed some NDR tool as well to switch between recoveries
some phills touch ui was the default and teamwin only worked if selected from the NDR app and rebooted
booted into teamwin, did a full wipe
mtp wasn't working to copy ROM so did a reboot, also tried to sideload before reboot but the stupid twrp said the device was 'leo' instead of D6503 or whatever so it didn't want to work
phone stuck so tried to use fastboot to flash system pa-sirrius-rom.zip
also tried to flash system backup from twrp but it's a win.000 and win.001 file and not sure how to join them to get a working system.img??
why won't recovery boot and how do i get a working system again. how do i convert a twrp backup to one that fastboot recognises and isn't split in 2?
If you have an unlocked bootloader just download a kernel with recovery built in. Flash the kernel 'fastboot flash boot boot.img'. Your phones not booting anyway so it really doesn't matter what kernel, as long as it has built in recovery. Boot into TWRP and recovery your backup.
Edit:
I'd you have an unlocked bootloader, don't wast your time with apks that install recovery. I'm my experience they're always hacky. Just get a recovery for fota partition or a boot image with one built in.
Sent from my D6503 using Tapatalk
Thanks for the reply.
I finally found a boot.img with TWRP built in (from the cyanogen project). I also found out that I had to flash it (fastboot boot command doesn't seem to work).
I can boot the recovery just fine but it will not mount any partitions and the only thing listed in the wipe menu is "Dalavik Cache".
I have attached a screenshot of the TWRP log.
It won't let me post links because my experience is low.
i.imgur dot com cXBv1Y8.png
Edit:
I can format the system partition and even mount it from the command line, it just doesn't appear in the TWRP UI.
In the mount menu, it has a checkbox which I cannot uncheck that says "Only mount system read-only".
Edit:
Booted from the cyanogen recovery image which had its own adb sideload which I used to load cyanogen and now it's working!
Recently bricked my honor 5x used fast boot to get it out of boot loop. (Because I tried to its update my phone with twrp)now when I try to re flash twrp it gets replaced by the stock recovery Everytime . Please help!
Samething happend to me... cannot flash twrp because when i restart phone after flashing twrp, it gets replaced by stock recovery.
What i do now is to boot to twrp instead of flashing using this command:
Code:
fastboot boot twrp-3.0.0-0-kiwi.img
Hopefully there is a solution for this flashing problem.
FREAK0N said:
Samething happend to me... cannot flash twrp because when i restart phone after flashing twrp, it gets replaced by stock recovery.
What i do now is to boot to twrp instead of flashing using this command:
Code:
fastboot boot twrp-3.0.0-0-kiwi.img
Hopefully there is a solution for this flashing problem.
Click to expand...
Click to collapse
you can't just reboot after flashing recovery ...you have to boot directly to twrp after the flash with power + volume up (Skip the fastboot reboot step)
the simple way is to copy kiwi_twrp_3-21_recovery.img to your sdcard
fastboot boot kiwi_twrp_3-21_recovery.img
now in twrp choose install / image / then choose kiwi_twrp_3-21_recovery.img
next choose reboot / recovery
you now have kiwi_twrp_3-21_recovery.img
from then on adb reboot recovery from android
or power + volume up will enter TWRP
clsA said:
you can't just reboot after flashing recovery ...you have to boot directly to twrp after the flash with power + volume up (Skip the fastboot reboot step)
the simple way is to copy kiwi_twrp_3-21_recovery.img to your sdcard
fastboot boot kiwi_twrp_3-21_recovery.img
now in twrp choose install / image / then choose kiwi_twrp_3-21_recovery.img
next choose reboot / recovery
you now have kiwi_twrp_3-21_recovery.img
from then on adb reboot recovery from android
or power + volume up will enter TWRP
Click to expand...
Click to collapse
Thanks alot... i wil try it later.
Too many Links is what ADB Says
RootMega said:
Too many Links is what ADB Says
Click to expand...
Click to collapse
why are you using adb ?
did you read the instructions i posted
I have the stock recovery.
I cant get into twrp.
I tried to flash then go straight to twrp which gets replaced by stock bootloader
Idk it gets replaced everytime
Okay the adb thing stopped I got into twrp by doing the fastboot thing but when i boot into recovery it goes to the stock recovery.
RootMega said:
Okay the adb thing stopped I got into twrp by doing the fastboot thing but when i boot into recovery it goes to the stock recovery.
Click to expand...
Click to collapse
I really don't know why you don't seem to get it
it's this simple
you fastboot boot kiwi_twrp_3-21_recovery.img
now while in TWRP copy kiwi_twrp_3-21_recovery.img to the phone
Also copy SuperSU-v2.64.zip (or newer) to the phone
after the files are copied choose Install / Image / kiwi_twrp_3-21_recovery.img
next choose install / SuperSU.zip
next choose Reboot / Recovery
you now have TWRP recovery and you can enter it by using power + volume up
or from an app on the phone (I use Quickboot) or from a pc with adb reboot recovery
I have the same problem, i tried with your method but the system continue to replace bootloader, impossible to keep twrp on recovery
Edit : I try to install Root Checker, it detect my phone is root but impossible to access to TWRP, very strange
clsA said:
you can't just reboot after flashing recovery ...you have to boot directly to twrp after the flash with power + volume up (Skip the fastboot reboot step)
the simple way is to copy kiwi_twrp_3-21_recovery.img to your sdcard
fastboot boot kiwi_twrp_3-21_recovery.img
now in twrp choose install / image / then choose kiwi_twrp_3-21_recovery.img
next choose reboot / recovery
you now have kiwi_twrp_3-21_recovery.img
from then on adb reboot recovery from android
or power + volume up will enter TWRP
Click to expand...
Click to collapse
Tried this on my KIW-L21, as this is the only way I did not try it yet...
Did not work, unfortunately, I assume the OP could have the same problem as I already posted in the TWRP thread:
http://forum.xda-developers.com/showpost.php?p=66678377&postcount=509
(It is a shame people spam this thread with unlocking problems, though)
EarlyMon mentioned something about dual recovery partitions here: http://forum.xda-developers.com/showpost.php?p=66838009&postcount=529
So regardless how many times I flash TWRP it wont stick until the next reboot to recovery, as it gets replaced by the stock one all the time.
I am thankful for every news on that topic and I would happily help(to the extent I am able to) getting TWRP back onto our phones :good:
P.S.: I am not quite sure if the OP has another problem in flashing the recovery, though.
Nekly said:
Tried this on my KIW-L21, as this is the only way I did not try it yet...
Did not work, unfortunately, I assume the OP could have the same problem as I already posted in the TWRP thread:
http://forum.xda-developers.com/showpost.php?p=66678377&postcount=509
(It is a shame people spam this thread with unlocking problems, though)
EarlyMon mentioned something about dual recovery partitions here: http://forum.xda-developers.com/showpost.php?p=66838009&postcount=529
So regardless how many times I flash TWRP it wont stick until the next reboot to recovery, as it gets replaced by the stock one all the time.
I am thankful for every news on that topic and I would happily help(to the extent I am able to) getting TWRP back onto our phones :good:
P.S.: I am not quite sure if the OP has another problem in flashing the recovery, though.
Click to expand...
Click to collapse
So you are booting TWRP
Installing / TWRP.Img in TWRP and Reboot recovery and your not booting to TWRP ?
Just my two cents into this thread: apparently (from my personal experience, and EarlyMon seems to back this up) the Honor 5X for whatever reason allows the installation of TWRP but still keeps Huawei's stock recovery in place, unlike most phones. What's more, it randomly (yeah, guessing it's not random obviously, but I don't have the slightest clue what the pattern might be) decides to boot into stock recovery while I use the same hardware keys that have continuously booted me into TWRP up until that point. This behavior led me to believe I had bricked my phone for a day, lol (I made a recent post about it on this forum, in case anyone cares).
Bottom line: if you can't boot into TWRP even though you made sure to install it correctly, try changing the key combo. Vol down + Power not working for you? Try Vol Up. Neither work? Try Vol Up + Down + Power. Spice it out and it might solve your problems.
clsA said:
So you are booting TWRP
Installing / TWRP.Img in TWRP and Reboot recovery and your not booting to TWRP ?
Click to expand...
Click to collapse
That is correct:
Connected Phone to PC
ADB reboot bootloader
fastboot boot kiwi.img
install image kiwi.img
reboot recovery
Tada, Stock eMUI Recovery :[
I really had hoped it would do the trick, though.
Nekly said:
That is correct:
Connected Phone to PC
ADB reboot bootloader
fastboot boot kiwi.img
install image kiwi.img
reboot recovery
Tada, Stock eMUI Recovery :[
I really had hoped it would do the trick, though.
Click to expand...
Click to collapse
what version of TWRP are you using ? whats the real file name ?
Has anyone tried flashing TWRP with TWRP Manager from the play store?
Sm0k3d 0uT said:
Has anyone tried flashing TWRP with TWRP Manager from the play store?
Click to expand...
Click to collapse
Been there and done that. Same outcome.
clsA said:
what version of TWRP are you using ? whats the real file name ?
Click to expand...
Click to collapse
The last approach was done with the one from the first post of the TWRP thread here on XDA(https://goo.gl/53xai9) "kiwi_twrp_3-21_recovery.img"
I also tried the TWRP images from https://twrp.me/devices/huaweihonor5x.html but always the same result.
I can try with a specific image, just give me a link and I'll try to flash it. :fingers-crossed:
Hello, fellow Android hackers.
Short: I am trying to install CM on a L21, but fail booting into TWRP (getting only stock recovery).
What I did, working with a brand-new phone:
Unlock bootloader.
Flash TWRP 3.0.2.
Boot to TWRP. It worked.
Try flashing CM, which failed due to some failed assert. Googling revealed a thread on these forums which suggested I had to do a stock update to Marshmallow first.
Downloaded the update through EMUI's updater.
The updater booted to TWRP which aborted the installation because of a failed zip signature check.
I disabled signature checking and ran the installation again. It succeeded.
Tried to directly install CM over it. I got the error message stating I couldn't flash on top of incompatible data.
At this point, I probably should just have wiped system and flash CM, but for some reason I decided to boot to stock.
Here is where it all seems to have gone wrong.
Try to flash and boot to TWRP, like in steps 13 to 18.
Push the B340 UPDATE.APP to /sdcard/dload.
Start the phone using power + vol down + vol up.
I have verified that the phone is on B340 and the builtin updater won't find further updates.
(I have repeated this step and the following ones countless times.)
Boot to bootloader and flash TWRP. Yes, the command succeeds.
Code:
…$ sudo fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.418s]
writing 'recovery'...
OKAY [ 0.641s]
finished. total time: 2.059s
fastboot reboot
adb reboot recovery # boots to stock recovery
Boot to bootloader and flash TWRP.
Hold power + vol up
I read that the duration holding the keys matters, so I tried this very often, but I always got to one of two different stock recoveries.
Factory reset and cache wipe with one of the two stock recoveries.
I also considered crushing the phone on the wall on multiple occasions, but then decided it would not help me with my goal.
Okay.
L21 with B340, how u boot to TWRP? -_-
Also, the two stock recoveries have the menu options "Download latest version and recovery, Reboot, Shutdown" and "Reboot, Wipe data/factory reset, Wipe cache partition".
I humbly thank everyone in advance who might have some contributions to share.
ok . as i understand ,
First Charge Ur Phone Up To 50%+
Second : Go Back To Stock L 5.0.1
Third : download The latest Nightly Version OF CM + Recovery Rom | Recovey
Forth : Flash Recovery Only Throw ADB if u got any error please Attach here if success Go to step 5
Fifth : Shut Down And HOLD Volume-up + Power As soon u see Honor logo Release Power But Keep Volume Rocked Pressed !
Last : Install The Cm After U already copy To SD Card .
Gd Luck ! .
i will presume that you are on stock recovery,
now go to honor 5x repository and download b320 firmware
now place it in dload folder and flash
now boot to bootlader and try flashing twrp
then do not directly boot to revovery
just do fastboot reboot
then now do adb reboot recovery
youl be with twrp and forst things first ,compulsarily do a backup
then now assuming that you have transfered layest cm to sd card,
first goto wipe , then select all except internal and external sd cards , then wipe
now install, you should be good to go,
i had your issue when i was on b34p, but b320 is a great base and supports all custom roms..try it
(I am sorry for not answering sooner, but I have a lot on my plate right now. :/ )
Thanks for the replies.
Romiui said:
ok . as i understand ,
First Charge Ur Phone Up To 50%+
Second : Go Back To Stock L 5.0.1
Third : download The latest Nightly Version OF CM + Recovery Rom | Recovey
Forth : Flash Recovery Only Throw ADB if u got any error please Attach here if success Go to step 5
Fifth : Shut Down And HOLD Volume-up + Power As soon u see Honor logo Release Power But Keep Volume Rocked Pressed !
Last : Install The Cm After U already copy To SD Card .
Gd Luck ! .
Click to expand...
Click to collapse
2: As I understood it I only had to upgrade to M in the first place to be able to install CM. The downgrade will not undo whatever happened there?
3: I am not sure that I understand what you're trying to say, but I know of no way to flash recoveries via ADB. The point is that, as posted in the OP, flash via fastboot allegedly succeeds and as soon as I boot to the recovery, I'm back to stock.
thilak devraj said:
i will presume that you are on stock recovery,
now go to honor 5x repository and download b320 firmware
now place it in dload folder and flash
now boot to bootlader and try flashing twrp
then do not directly boot to revovery
just do fastboot reboot
then now do adb reboot recovery
youl be with twrp and forst things first ,compulsarily do a backup
then now assuming that you have transfered layest cm to sd card,
first goto wipe , then select all except internal and external sd cards , then wipe
now install, you should be good to go,
i had your issue when i was on b340, but b320 is a great base and supports all custom roms..try it
Click to expand...
Click to collapse
Thanks. I actually tried the dload method with B140 after writing this post, but it doesn't seem to work—same with B330 (the repo doesn't contain a B320 for L21). As far as I can tell, the dload install appears pretends to work fine: I'm getting a successful archive verification, an install meter and no error message. But the OS is not replaced.
I am uncertain if I need an actual microSD card—different sources seem to suggest different things here—but I generally would assume that, if there was no valid image in the right place, I would be getting an error message.
I am fine with whatever suggestion that wouldn't result in a brick. Data loss is fine, there's nothing on it.
A dumb question but do you disconnect the phone from PC or Mac after flashing twrp, firing fastboot reboot and quickly press power and vol up to boot to twrp.
If you already did that, try unlocking command once more and then try flashing it...
You can also try
Fastboot boot twrp_kiwi.img
To boot directly to twrp without flashing.
Hope any of it works.
ksdug said:
(I am sorry for not answering sooner, but I have a lot on my plate right now. :/ )
Thanks for the replies.
but I know of no way to flash recoveries via ADB.
D
Click to expand...
Click to collapse
All recoveries can be Flashed throw Fast-boot ADB Boss .
ksdug said:
(I am sorry for not answering sooner, but I have a lot on my plate right now. :/ )
Thanks for the replies.
2: As I understood it I only had to upgrade to M in the first place to be able to install CM. The downgrade will not undo whatever happened there?
3: I am not sure that I understand what you're trying to say, but I know of no way to flash recoveries via ADB. The point is that, as posted in the OP, flash via fastboot allegedly succeeds and as soon as I boot to the recovery, I'm back to stock.
Thanks. I actually tried the dload method with B140 after writing this post, but it doesn't seem to work—same with B330 (the repo doesn't contain a B320 for L21). As far as I can tell, the dload install appears to work fine: I'm getting a successful archive verification, an install meter and no error message. But the OS is not replaced.
I am uncertain if I need an actual microSD card—different sources seem to suggest different things here—but I generally would assume that, if there was no valid image in the right place, I would be getting an error message.
I am fine with whatever suggestion that wouldn't result in a brick. Data loss is fine, there's nothing on it.
Click to expand...
Click to collapse
glad you did it
thilak devraj said:
glad you did it
Click to expand...
Click to collapse
I rephrased that part as it was unclear. I didn't manage to pull off a downgrade.
muradulislam said:
A dumb question but do you disconnect the phone from PC or Mac after flashing twrp, firing fastboot reboot and quickly press power and vol up to boot to twrp.
If you already did that, try unlocking command once more and then try flashing it...
Click to expand...
Click to collapse
I did, but to no avail. Reunlocking had no effect either.
muradulislam said:
You can also try
Fastboot boot twrp_kiwi.img
To boot directly to twrp without flashing.
Hope any of it works.
Click to expand...
Click to collapse
I love you. I had totally forgotten about that. Using the boot command I managed to install CM, but I still cannot replace the stock recovery. Maybe I'll try letting CM write its own recovery with its next update, but I guess I'll leave it at that. The only downside is that my dad now needs me for doing updates. :/
Thanks very much.
ksdug said:
I rephrased that part as it was unclear. I didn't manage to pull off a downgrade.
I did, but to no avail. Reunlocking had no effect either.
I love you. I had totally forgotten about that. Using the boot command I managed to install CM, but I still cannot replace the stock recovery. Maybe I'll try letting CM write its own recovery with its next update, but I guess I'll leave it at that. The only downside is that my dad now needs me for doing updates. :/
Thanks very much.
Click to expand...
Click to collapse
wait......
you couldnt make it?? ok right now were are you at??
how to boot Honor 5x into TWRP
I know this is an old post, but since I tried for nearly a week to get my Honor 5x to boot in TWRP when pushing volume up + power button, I just wanted to post how I finally got it working, just in case anyone else should have the same problem...
1. First, I downloaded the latest stock rom. On my Honor 5x Android 5 (Lollipop) was installed, so I downloaded an Android 6 (marshmallow) stock rom. Make sure to get the correct version for your region (e.g. C432 for Europe). I found the correct rom file by simply googeling. If you are in a boot loop or do not have a working android on your phone, read instructions below.
2. I un-zipped the rom file and copied the update.app to my sd card to folder "dload"
3. I booted regularly into Android and started the update installation from the settings, where I could select option to install from SD card.
4. once that was done, i enabled USB debugging in developer tools and booted into TWRP from ADB with command
fastboot boot twrp-3.1.0-0-kiwi.img
5. Then, I installed SuperSu (SuperSU-v2.82-201705271822.zip)
6. Then, I flahed TWRP directly FROM TWRP. To do so, I clicked "Install" button, clicked "Install Image" and then selected TWRP file (which i copied to my SD card earlier). BE CAREFUL TO FLASH TWRP as Revovery (NOT boot). Actually, I first flashed twrp-3.0.0-0-kiwi.img, then directly after flashed twrp-3.0.2-0-kiwi.img and then I flashed twrp-3.0.0-1-kiwi.img (you see I was kind of desperate...). After that, from TWRP I booted into bootloader and again flashed twrp image from PC using adb:
fastboot flash recovery twrp-3.1.1-0-kiwi.img
7. from ADB, I again booted into TWRP
fastboot boot twrp-3.1.1-0-kiwi.img
8. ... where I once more installed TWRP.
After that I clicked reboot and selected to boot into Recovery. Then it finally worked.
After endless tries to get my phone to boot into TWRP when pushing volume up and power button, I am not sure which of the above steps made the difference. I think the important part is to update to the latest android version.
BTW: my first problem was I bricked my phone by trying to install lineageos from TWRP 3.1.1.1 and was in an endless bootloop. Here is how I got a regular android running:
I booted into bootloader (power + vol DOWN) and flashed the following files from adb (i got the files by extracting an android stock rom with Huawei Update Extractor (HuaweiUpdateExtractor_0.9.9.3.zip)):
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
Hope this helps...
It's better to post in a new thread, that will be more helpful for you
Hi,
I unlocked my Honor 9 bootloader using the "fastboot oem unlock 'unlock key'" method.
After that it did low level reset or something of the sort and booted to Android.
After that I wanted to install TWRP using fastboot, the problem is that every time I do "adb reboot bootloader" I get a message the device cannot be trusted (see pic) and it boots to android.
I tried pressing power button, up button (this gets me to the recovery), but it always gets back to Android and not to fastboot.
What can I do???
Thank you
Return fully stock, then try again
PalakMi said:
Return fully stock, then try again
Click to expand...
Click to collapse
How do I do that, use the original recovery?
OK, I managed to get to the bootloader by turning off the phone, pressing the volume down button and connecting the USB cable.
I flashed twrp and somehow booted to the recovery I wanted to flash the supersu.zip but all the folders and file names in the sdcard were gibberish.
I rebooted and everything was ok (not gibberish) but instead of having twrp I got the original recovery back.
Since then even if I flash using fastboot the twrp recovery I keep getting the original recovery.
In the fastboot screen there's a message "Android reboot reason: bootloader NA reboot_enter_fastboot_common_func" is it normal? (see pic)
And one last question, should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
UPDATE:
I managed to get twrp working.
I did fastboot oem relock, and then unlocked the bootloader again, and it booted to twrp (without re-flashing twrp).
When I tried to flash supersu all the files were gibberish (see pic), what am I missing?
If I wipe data it seems fine, but then I boot to system to copy the supersu file and once I load twrp it is gibberish again.
Also should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
Appreciate any help I can get.
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Midhon58 said:
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Click to expand...
Click to collapse
yeah I figured as much.
Didn't think of using external SD, thanks, was about to try adb sideload, I assume it would have worked too.
Many thanks, the external sd did the trick
Hi, here I bring you a small tutorial for upgrading your rooted Realme GT 2 Pro Global Version to latest update (RMX3301_11_A17), as you may know I am not responsible of any damage and I recommend you to back up your data.
First, uninstall all your modules from magisk (technically you could just deactivate them, I prefer uninstall though). Make sure Zygisk is deactivated and turn off all the super user permissions of your apps before the update step. You should deactivate Automatic system updates under developer settings as well.
Here the steps:
1. Go to settings and download the OTA, you´ll get the 200 mb one. Since what we need is the full OTA package, once it's been downloaded when it starts to be extracted force stop the Software Update app in your settings.
2. After previous step go to your file manager (in this case I use Mixplorer, for this you will need the app with root access) and go to the next directory: root/data/ota_package/OTA/ [a folder that starts like .ota], inside you are going to delete the ota file with .zip extension. This first two steps are a way to speed up the process of getting the full OTA.
3. Go again to your software update section in settings, you will see a notification from the app software update app, touch on continue. After that you will see a message of error, and you will see a button that says "Try again", keep clicking on try again several times. You'll see then that full OTA update will start automatically (about 5 gb in size).
4. From here you will have to wait until the "Install" button appears (it'll take a while). Next, you click install.
5. After reboot, transfer the boot.img file attached on this post to your device. Magisk patch it and transfer back to your PC.
6. Open your adb terminal, type the command adb reboot bootloader
7. Test recognition by typing fastboot devices
8. Next type: fastboot boot whatevernameofyourpatchedfile.img (it has to be in the platform tools folder)
9. Your device will boot with a temporary root, check everything is working ok in your device. After that you will go to magisk app, click on install, and in the Method section select "Direct Install", and then Let's go.
10. After reboot you'll have you magisk rooted device updated and working. Now you can install back your modules again.
boot
This method can be done on the phone with root preservation directly via Magisk. No need to copy/patch boot.img files manually, as long as you have restored image in Magisk at least once. This is explained below.
Important notes:
Do not restart the device or select "Install" in the OTA updater until Magisk is reinstalled to inactive partition. Otherwise it will boot into stock ROM, and patched boot.img must be flashed via fastboot to restore root.
In addition, after installing to inactive partition in Magisk, do not press restart on Magisk's prompt.
The auto-update should be disabled, including the "Auto Download" setting. Otherwise, the updater will attempt to download and install while Magisk is present, and show "Extraction Failed" error, and "Try Again". If that happens, the system will only allow to download a 5GB update instead. To reset it, you can clear Software Updater app data and cache via some root app manager.
When selecting "Restore Images" in Magisk, if a message shows in Magisk "Stock boot image not found", then you need to generate backup stock boot.img on the phone. This is only done once, but you will need a stock boot.img of your current ROM version.
- Copy current ROM version stock boot.img to storage
- Open Magisk and select install -> Patch file -> Select the stock boot.img
- Restart phone.
This will generate Magisk "backup image" folder where it will keep the stock, non-patched boot.img.
This is only done once, on any future update the error will not show.
Click to expand...
Click to collapse
The 300mb OTA update steps:
1. Go to updater and it should show 300-600mb update available. DO NOT press "Download"!
2. Go to Magisk, select to restore image. Do not restart when prompted by Magisk. If you get error, read note on top.
3. Go back to updater and select "Download". It will first download then extract. When it finishes extracting, DO NOT press Install!
4. Go back to Magisk and select install to inactive partition. Once it's done, do not restart via Magisk! Close Magisk.
5. Go back to updater, and press "Install" button
Click to expand...
Click to collapse
Extra notes:
1. If you press Download before removing Magisk, it will fail extracting and show "Try Again". Do not press try again. Go to a root app manager, and clear Data and Cache of com.oplus.ota Software updater. Then repeat the process by restoring images in Magisk first.
2. If you did press "Try Again", it will only allow you to download a 5GB update. Steps are similar as long as you restore Magisk. You might be also able to clear data and cache like in step above to reset it back to smaller update, but I haven't tested this yet.
3. If you restart by Magisk prompt, it will soft-loop. You can hold Vol Up + Power until it boots into non-root partition. Go to updater and press install. It will boot to rooted partition.
4. If you pressed Install in updater before installing Magisk to inactive partition, it will boot to updated partition without root.
5. I have tested the update methods with simply Uninstall -> Restore Images, while I had Magisk modules such as BCR, Shamiko, USF, LSPosed Zygisk. It works fine without the need of removing each module.
Extra side note: Update file is downloaded to: /data/ota_package/OTA/.otaPackage/mymanifest(...).zip
What is need of this lengthly process. Just wait for OTA to show in update. Only full package will show for rooted user. Let it download, Extract and verify. Before Pressing install Button, Go to Magisk and Install on inactive slot. Then Go back to updater and install button.
Phone will reboot and updated. Magisk working, All modules intact.
shivrajsingh said:
What is need of this lengthly process. Just wait for OTA to show in update. Only full package will show for rooted user. Let it download, Extract and verify. Before Pressing install Button, Go to Magisk and Install on inactive slot. Then Go back to updater and install button.
Phone will reboot and updated. Magisk working, All modules intact.
Click to expand...
Click to collapse
I know what you mean, in fact thank you for telling me that procedure is working well on our device hahaha, since there's no proper flashing tool and no TWRP yet, the idea behind that lengthy process is trying to reduce the risks to minimum n.n
Just confirmed that this works for a 300mb (before restoring images) update file instead of the full 5GB (after restoring images), updated the guide above.
vanya.ag said:
boot
Click to expand...
Click to collapse
now my fingerprint is broken
Quake94 said:
Notes:
When Magisk is removed using Restore Images, the Realme OTA updater will show a full 5GB update. If the Magisk is not removed, the OTA will be around 300mb. Both update files will work OK, there is just small difference in steps. The important part is to not restart the device or select "Install" in the OTA updater until Magisk is reinstalled to inactive partition. Otherwise it will boot into stock ROM, and a patched boot would need to be flashed via fastboot to restore root.
Click to expand...
Click to collapse
i followed your steps
it was an 5gb OTA update i dovnloaded it and extract it then i go to magisk and install to inactive slot after reboot now im in stock recovery what now?
Terrorigel97 said:
i followed your steps
it was an 5gb OTA update i dovnloaded it and extract it then i go to magisk and install to inactive slot after reboot now im in stock recovery what now?
Click to expand...
Click to collapse
What what? You post in multiple threads. In one of them you want to lock bootloader and keep it stock, but here you say you installed Magisk after OTA. You also talk about stock recovery that has nothing to do with bootloader.
Help yourself and read up, all the information is widely available.
Quake94 said:
What what? You post in multiple threads. In one of them you want to lock bootloader and keep it stock, but here you say you installed Magisk after OTA. You also talk about stock recovery that has nothing to do with bootloader.
Help yourself and read up, all the information is widely available.
Click to expand...
Click to collapse
I never said i will be on stock lol I was just asking if you can lock your bootloader again...
Terrorigel97 said:
I never said i will be on stock lol I was just asking if you can lock your bootloader again...
Click to expand...
Click to collapse
Lock only on clean, stock rom as per guide in the other thread.
Can't lock on rooted, but rooted can be reversed to stock clean.
EDIT: resolved, see bottom note.
A.19 update screwed something up for me.
I restored image in Magisk, installed a full 5GB update, reinstalled Magisk to inactive slot. Reboot via Magisk.
Phone went to softloop. I held Volume Up and Power, and at some point it switched back to previous slot with A18, works fine except no root.
Restarted to fastboot. Fastboot works OK.
When attempting to restart to bootloader, some "mascot" icon appears and chinese writing, and quits back to fastboot.
Manually switched active partition via fastboot --set_active to try to boot the A19.
Phone still softloops, again, restarted back to previous slot with A18.
Fastboot indicates unlocked bootloader.
Not sure what got messed up, and why bootloader mode refuses to start.
Not a big issue, because my old A18 works ok, so for anyone else reading this that got a softloop, I recommend simply holding Volume Up and Power to switch to old slot, instead of attempting to reflash and screwing both partitions up.
Anyone else in a similar situation?
EDIT: LOL I fixed it . I went to software updater, and "Install" button was displayed.
Pressing install restarted the phone into A19 with Magisk installed......
Very interesting! Because rebooting via Magisk or the --set-active command in fastboot resulted in softloop! So the "Install" must be doing some extra steps.
TLDR; after OTA update and reinstalling Magisk to inactive slot, do not reboot via Magisk, but via OTA updater "Install" button! My guide above was updated.
I confirm you have to reboot via the installer and not via Magisk, since I had to manually flash boot.img multiple times in the past.
Quake94 said:
EDIT: resolved, see bottom note.
A.19 update screwed something up for me.
I restored image in Magisk, installed a full 5GB update, reinstalled Magisk to inactive slot. Reboot via Magisk.
Phone went to softloop. I held Volume Up and Power, and at some point it switched back to previous slot with A18, works fine except no root.
Restarted to fastboot. Fastboot works OK.
When attempting to restart to bootloader, some "mascot" icon appears and chinese writing, and quits back to fastboot.
Manually switched active partition via fastboot --set_active to try to boot the A19.
Phone still softloops, again, restarted back to previous slot with A18.
Fastboot indicates unlocked bootloader.
Not sure what got messed up, and why bootloader mode refuses to start.
Not a big issue, because my old A18 works ok, so for anyone else reading this that got a softloop, I recommend simply holding Volume Up and Power to switch to old slot, instead of attempting to reflash and screwing both partitions up.
Anyone else in a similar situation?
EDIT: LOL I fixed it . I went to software updater, and "Install" button was displayed.
Pressing install restarted the phone into A19 with Magisk installed......
Very interesting! Because rebooting via Magisk or the --set-active command in fastboot resulted in softloop! So the "Install" must be doing some extra steps.
TLDR; after OTA update and reinstalling Magisk to inactive slot, do not reboot via Magisk, but via OTA updater "Install" button! My guide above was updated.
Click to expand...
Click to collapse
This sounds like what my phone is doing but maybe I am confused because you mention fastboot and the bootloader as two different things. Just to be clear, "adb reboot bootloader" is what you are calling the bootloader and "adb reboot fastboot" which goes into fastbootd mode is what you are calling fastboot?
If so then my phone is doing the exact same thing, I can boot to fastbootd mode but when I attempt to "adb reboot bootloader" then just like you said a little mascot with Chinese writing appears for a split second then it reboots back to the system. Did you get your bootloader working again by doing the install?
GIutton said:
This sounds like what my phone is doing but maybe I am confused because you mention fastboot and the bootloader as two different things. Just to be clear, "adb reboot bootloader" is what you are calling the bootloader and "adb reboot fastboot" which goes into fastbootd mode is what you are calling fastboot?
If so then my phone is doing the exact same thing, I can boot to fastbootd mode but when I attempt to "adb reboot bootloader" then just like you said a little mascot with Chinese writing appears for a split second then it reboots back to the system. Did you get your bootloader working again by doing the install?
Click to expand...
Click to collapse
There are four modes:
bootloader - adb reboot bootloader
fastboot - adb reboot fastboot (or the key combo)
fastbootd - fastboot reboot fastboot (from being already in fastboot)
recovery - adb reboot recovery (or the key combo)
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry
In my case the fastboot mode would start ok, just not the bootloader mode.
I didn't try fastbootd, but it would probably start ok.
I don't understand the fastbootd mode well though. I read somewhere that it is fastboot in Data partition.
I haven't tested rebooting to bootloader after fix, but can let you know.
EDIT: Booting to bootloader from fastboot (fastboot entered with key combo) gives me the mascot again, then it goes immediately back to fastboot. So I think I am in same position as you
Running "adb reboot fastboot" started "Fastbootd" mode (the one with wipe data/reboot/power off)
Running "fastboot reboot fastboot" from the "Fastbootd" would restart to "Fastbootd"
Running "fastboot reboot recovery" from the "Fastbootd" showed success, but 1. phone stayed in "Fastbootd" and 2. The phone deauthorized ADB (but still showed in device manager as "ossi" device)
Running "adb reboot bootloader" from System, showed the mascot and started the regular Fastboot.
Running "fastboot reboot fastboot" while the regular Fastboot was on, started "Fastbootd"
My suspicions are:
1. Regular fastboot mode is the one with green "START" on top. Somehow it is the same as bootloader. This is confirmed by Realme guide for unlocking/locking bootloader - they ask to use adb reboot bootloader, and then run a fastboot command.
2. "Adb reboot fastboot" starts the "userspace" fastboot called "fastbootd" which is isolated from bootloader and kernel.
This would mean the modes are:
bootloader/fastboot -> adb reboot bootloader (or the key combo)
fastbootd - adb reboot fastboot, or fastboot reboot fastboot (from being already in bootloader/fastboot)
recovery - adb reboot recovery (or the key combo)
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry
So you can get into the start menu (fastboot/bootloader) by using the button combo but if you try fastboot reboot bootloader it shows a mascot with chinese letters then goes right back to the start menu and adb reboot bootloader shows the mascot and goes into the start menu as well? I think your phone is fine. . . fastboot and the bootloader should both be the start menu right or is there a difference?
For me I get the realme logo then a screen glitch and boots to the system when I try the button combo. When I try adb reboot bootloader I get a mascot with Chinese letters then a screen glitch then boots into the system.
Added some extra notes in my guide. If Auto download was enabled in About Device -> Software Update, the updater will display "Extraction Failed" since it attempts to download and extract update while Magisk is present. It also locks itself out of "Local install". The updater will download 5GB update instead on a retry, and 5GB method would be used.
With the Auto download disabled, user can Restore Images via Magisk and then download and install the update.
I will test this on the next update rollout.
Revised guide after C.12 to C.13 update and testing the smaller update method. The process is much more straightforward than I initially thought. No need for "Local update".