A guy over at the oficial oneplus forum (https://forums.oneplus.net/threads/aging-mode.468296/)
found out that if you press vol up and down at the same time the phone boots from a different partition,
instead of sde18(boot) it starts from sde19(boot_aging)
after comparing boot.img with boot_aging.img
it seams that the ramdisk ist the same, just that boot_aging contains an additional kernel module: wlan_aging.ko
also the kernel itself is 2 MB larger than the default one...
Anyhow this mode is probably not use in normal phone operation but rather some part of post production testing/burn-in
So we could probably use it for something useful....
Like switching between two kernels without the full multiboot....
Or may be having two different recoveries...
This is indeed very interesting and could potentially be useful. Switching over between the modified TWRP and standard TWRP could then be a thing?
could be worth a try..
MisterCoolBeans said:
This is indeed very interesting and could potentially be useful. Switching over between the modified TWRP and standard TWRP could then be a thing?
Click to expand...
Click to collapse
Not two different twrp versions since its the boot partition but we could use two different kernels
Solution for a native dualboot maybe?..
This isin't the boot used for unbricking the phone ?
As far as i understand the unbrick process, no it is not.
I think i can be used for dual boot just as well as for a alternative recovery. to my understanding the difference between boot, boot_aging, and recovery is which is booted when. I think if we would blast recovery to boot the phoen would always by default start with recovery, and if we flash boot to recovery we could also implement a sort of dual boot just that than we wouldn't have any recovery.... just my 2 cent
About dualboot, look here: http://forum.xda-developers.com/oneplus-3/how-to/op3-partitions-t3454215 we dont have a spare 3 GB partition, so if we want to dual boot, the new kernel has to be modded to have the system image in the data partition.
Or we use the 1,5 GB unused pace on the last block device as you can see in the partition overvirew I made, for CM with pico gaps that could be enough.
Actually that could be really cool, to have a secondary OS on the phone that does not conflict with the main one
Does that work with unlocked bootloader?
I tryed to press vol up+vol down + power and i get to the normal bootlaoder boot menu,
when i press in the menu power agian it shows a oneplus logo and text fastboot mode but it enters twrp and that is it.
I wonder if this key combination is only avilable when the bootloader is locked...
Apparently you can boot from that partition using the Engineering mode: *#36446337#
if you select "auto aging" the software will than ask you if you wont to reboot...
Anyone remember this thread?
There apparently is a bootloader bug that allows to unlock it without getting the usual boot screen: https://securityresear.ch/2017/02/08/oneplus3-bootloader-vulns/
I wonder if once used these method to unlock you get the option back to boot into the aging boot partition, and if this could be used for something useful.
Like having two different recoveries or switching between different kernels with only one reboot.
One of the most interesting threads currently in OP3 section.
I hope our kernels and recoveries devs join OP in this interesting, challenging and potentially useful quest.
I think the kernel devs will already know about this, so it's probably not that much of a breakthrough, sorry to be that guy although it does remind me of the secondary boot.img for the unbrick of a nexus 5
Related
Ok, so I got the Z3c just recently since CyanogenMod now apparently supports it (odd it's not listed in devices on the wiki, but it's on their standard build system, so this is not even an unofficial build.) I found t here's even an official TWRP build for it. I really kind of need TWRP on there as I need to be able to do all of the numerous stuff it can do without having to hook it up to a computer with adb/fastboot/etc every single time. There are a huge number of features and conveniences to TWRP that CWM and CyanogenMod recovery both lack (frankly it feels like TWRP is a modern recovery and those two still feel like they date back to the Android 2.x days. I can remember the stock recovery on my Archos 43 back in the day being practically the same as what I get with CyanogenMod recovery especially.)
Anyway, this one is a bit odd. I've also setup a Z2 Tablet for my grandmother with TWRP + CyanogenMod and there are no troubles at all there. I put TWRP on it and it works normally basically. However, on this Z3c it's going a bit wonky. CyanogenMod somehow seems to be replacing the recovery with its own. I've disabled automatic updates and the option to update the recovery was never even enabled at all. If I flash using dd directly to the partition as the official TWRP page says I once again have TWRP, but then the system either won't boot at all (staying stuck on the SONY logo) or it just boots straight to TWRP over and over as if TWRP were the normal system instead of the recovery.
I'm wondering whether something is just going really wrong or if, alternately, there's some oddity like it having some sort of "boot to recovery" flag that gets set and does not clear? Is this something I can fix, or am I just stuck with CyanogenMod putting its own recovery on there without asking?
Honestly, SONY did a lot of things great on their devices, but not having a true separate bootloader/recovery is something I will never be comfortable with.
I tried flashing to boot once with, as you know, the expected results. Most of the time I did as I said in the original post and followed those instructions exactly though.
And I would just swear at at least one point I rebooted back into TWRP and it was still there before CyanogenMod replaced it. Oh, and from the TWRP page on this device:
This utility is designed to work in conjunction with the current methods that most AOSP ROMs use for the ramdisk and can also be used on stock kernels. This setup means that you must have a kernel or boot image installed that will use the FOTAKernel method. Most AOSP based ROMs like OmniROM or CyanogenMod will support this method. Some stock kernels may also support the FOTAKernel method.
Click to expand...
Click to collapse
Note they explicitly specify that CyanogenMod supports its method.
Ok, I think I was misunderstanding something. It looks like CyanogenMod essentially has its own boot partition and this goes to a separate location. Rather than being "replaced" it's just going to CyanogenMod's separate recovery instead of TWRP. If so this begs the question of how one even gets to TWRP there (which isn't mentioned on that page at all.)
EDIT: It's a pain, but I tried fastboot flashing it to boot. It still goes straight into TWRP every time if I do that. The "recovery-from-boot" file is not present in /system. (It's a pain because I have to "reinstall" CyanogenMod and wait for it to optimize everything again now.) It's when I flash with fastboot that it gets stuck always booting straight into the recovery. Ironically, if I flash CyanogenMod's own boot image back on there manually it still gets stuck always going into recovery -- just CyanogenMod's recovery instead of TWRP.
EDIT2: I ran across this post: http://forum.xda-developers.com/showpost.php?p=58830666&postcount=206 I'm still getting CyanogenMod's own recovery though even when I follow that exactly.
EDIT3: Ok, I think I found a solution. Not sure if this is the best possible way to do it, but I found out that XZDualRecovery apparently works with CyanogenMod fine. I just have to remember to flash it after flashing CyanogenMod in the recovery and then during the bootup process I have to wait for the light to go green (instead of earlier in the process as that just gives me CyanogenMod's recovery still.) If I hold down once it goes green I get TWRP. http://forum.xda-developers.com/showthread.php?t=2261606
I tried recovery. The problem is, boot and recovery are the same thing on SONY devices like this. Anyway, that XZDualRecovery isn't perfect -- for one it ignores the setting for brightness, leaving the screen at 100% (which not only hurts my eyes, but obviously isn't good for it.) Other than that though this thing works very well.
All I can tell you here is that I tried flashing to recovery instead of boot and it didn't work. Perhaps there's some special way you have to trigger it beyond the usual methods (perhaps like the way XZDualRecovery has its own portion of the startup where the LED goes green and the motor vibrates to let you know it's time to press a button if you want it to boot one of its recoveries.) Nothing mentions this anywhere that I could find though and I definitely haven't triggered it on my own.
Given that it works at all but is determined to either utterly ignore TWRP or go straight to only its own recovery it must have some sort of check then and just simply reject TWRP I guess.
Anyway, a this point there's really nothing I can do with it. I lack the development experience, time, or knowledge to go about trying to fix it and submit patches or whatever. I'm just going to stick with XZDualRecovery since it works fine in every way except ignoring the brightness setting (I do hate that, but at least on long operations it still shuts off the display.) Just to be clear, you do understand that XZDualRecovery DOES let me boot TWRP from it? I don't know if it may be a modified version or something (the fact that it's ignoring the brightness setting makes me think it may be) but everything seems to work normally within it other than that (I'm wondering if that may be more an issue with the startup process.)
In developer options there is an option that should be unchecked. Can't remember but it's says not to update recovery or something similar
Indeed. I always uncheck that first thing and actually disable automatic updates entirely anyway (this is about updating through the standard interface. I update by downloading builds and installing through TWRP for several reasons that I won't get into right now.) Unfortunately though, that is kind of a separate thing really. It's more just in reference to the fact that CyanogenMod now has its own actual recovery so you can set it to automatically update that part as well. Just to be completely clear though, because of the way it works, TWRP would no longer come up after installing CyanogenMod at all and it can't be just simply flashed back on. I guess feherneoh has the right of it really. Perhaps it's compressed incorrectly (or shouldn't be compressed at all) or whatever. If I knew what I was doing I could probably manually do this part myself, but I don't really feel very confident about that. I'll just stick to XZDualRecovery with its TWRP 2.8.7.0 build that works great in every other way but the fact it ignores the display brightness setting.
What could cause Options to appear in chinese after pressing the power button to boot up please? It has happened to me several times, and the only word in English characters is 'USB'. Usually after some playing around I can get the phone to boot, but if there is a simple way I would be glad to know it.
nottheusualtoday said:
What could cause Options to appear in chinese after pressing the power button to boot up please? It has happened to me several times, and the only word in English characters is 'USB'. Usually after some playing around I can get the phone to boot, but if there is a simple way I would be glad to know it.
Click to expand...
Click to collapse
Probably, your recovery is still stock, which definitely has chinese lang option.
How about replacing the stock recovery with TWRP? You will still receive OTA and can install it
Or simply, dont boot into recovery.
Excuse my ignorance but how am I managing to boot into recovery by mistake on stock Android? If I know that, I can probably avoid doing it. Thanks for help
Pressing volume key whilst booting, can't remember if it's up or down, will boot into recovery.
nottheusualtoday said:
Excuse my ignorance but how am I managing to boot into recovery by mistake on stock Android? If I know that, I can probably avoid doing it. Thanks for help
Click to expand...
Click to collapse
Nobody said that you are mistakenly choosing the recovery. What he meant was, may be you have the original stock recovery and it is stuck in Chinese.
The easiest way out is to flash TWRP recovery. But take care to learn whether you need the official TWRP or the modified one. Better choose the modified one named 3.0.2-22 as it is said to be compatible with all ROMs including stock.
tnsmani said:
The easiest way out is to flash TWRP recovery. But take care to learn whether you need the official TWRP or the modified one. Better choose the modified one named 3.0.2-22 as it is said to be compatible with all ROMs including stock.
Click to expand...
Click to collapse
If you don't require twrp functions I wouldn't bother, just try an avoid touching volume keys whilst booting.
Really good advice
I'm sure that advice about not holding the volume keys while booting is really good. I have had problems also while powering down, which I can quite believe
may have been caused due to this. The design of the Oneplus 3 makes the volume keys a natural place to grip, being, immediately opposite the power key. Maybe
Oneplus could consider this as they start designing the Oneplus 4!!
Has anyone managed to get any Treble ROMs working? I tried the 3 from this post but they just cause a bootloop https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
Do yourself a favour and remove your password / pin / pattern as i've just flashed one via fastboot (no treble recovery)
And it didn't work, now i can't get back into TWRP.
Any ideas?
No new treble ROMs work with our P20 pro's.. its the same for me which is why I'm back on stock for now... As every new version of treble ROMs I have tried do not boot for me they just stick me in a boot loop as well, its the same for the new version of lineageos.. Not sure if it will ever be fixed in the future though on newer builds considering the whole Huawei locking bootloader permanently thing... will probably put developers off Huawei phones all together...
danielfrancisarthurs said:
No new treble ROMs work with our P20 pro's.. its the same for me which is why I'm back on stock for now... As every new version of treble ROMs I have tried do not boot for me they just stick me in a boot loop as well, its the same for the new version of lineageos.. Not sure if it will ever be fixed in the future though on newer builds considering the whole Huawei locking bootloader permanently thing... will probably put developers off Huawei phones all together...
Click to expand...
Click to collapse
How did you get back to Stock? I have no OS now at all lol, i'm in limbo
Erecovery I used.. when booting and you get the unlock boot screen it will tell you to hold volume up I think for 3 seconds to go to erecovery and then just download and restore stock firmware and recovery and let the phone do it's work!
danielfrancisarthurs said:
Erecovery I used.. when booting and you get the unlock boot screen it will tell you to hold volume up I think for 3 seconds to go to erecovery and then just download and restore stock firmware and recovery and let the phone do it's work!
Click to expand...
Click to collapse
Yea i used eRecovery a little earlier myself, we really need twrp which actually allows decryption or even twrp which allows treble
Either that or decrypt and use no verity, haven't bothered with all that yet.
After today though, jesus i'm thinking about it, i literally ended up with nothing, all my wifi networks in work need a second log in, something which eRecovery can't offer.
Completed it when i got home.
Have you managed to install any treble roms? Has anybody?
I don't think it's possible on my device in it's current state, i tried TWRP, Fastboot, several different roms on both and nothing.
Spotted this earlier, might actually work on our devices, what do you think?
https://forum.xda-developers.com/hu...rp-3-2-1-0-t3782866/post76668571#post76668571
It's a treble recovery from the p20 lite forum, similar device, might work, anyone fancy trying it
PS: If i flash this can i just flash my Unofficial TWRP from our forum should it not work? Or can damage be done?
I have no idea! I assume the issues are because of twrp or something in that area.. I have tried flashing system images via fastboot but for some reason I get errors trying it.. I'm not sure what the main issue is on why they don't boot but i would strongly suggest to not try flashing any twrp that's not specifically for our device as you could brick or even break your phone!
danielfrancisarthurs said:
I have no idea! I assume the issues are because of twrp or something in that area.. I have tried flashing system images via fastboot but for some reason I get errors trying it.. I'm not sure what the main issue is on why they don't boot but i would strongly suggest to not try flashing any twrp that's not specifically for our device as you could brick or even break your phone!
Click to expand...
Click to collapse
Apparently you don't need to use twrp at all, I've successfully flashed system images, via fastboot, but they've never booted which is horrible because there's just nothing else here.
In regards to flashing twrp, again apparently if it goes wrong then we can just flash the stock recovery, personally I think flashing another functional recovery would work too. But in all fairness the one in the p20 lite thread doesn't work any more than ours does in the pro thread.
Just hoping things move along.
Yeah I'd assume so.. I haven't been able to flash any image via fastboot but I'd assume it's the ROMs not the recovery.. anyway just heard that Huawei have released the Source code for the P20 so maybe it might be good news for the treble ROMs if they were to implement fixes for the boot loops!
danielfrancisarthurs said:
Yeah I'd assume so.. I haven't been able to flash any image via fastboot but I'd assume it's the ROMs not the recovery.. anyway just heard that Huawei have released the Source code for the P20 so maybe it might be good news for the treble ROMs if they were to implement fixes for the boot loops!
Click to expand...
Click to collapse
Sounds superb on any other flagship in the world, really hope this one picks up, it's a great device, never been happier with a stock ROM before, I think with all aosp lineage ROMs there's going to be huge issues fixing the cameras. Twos hard enough, 3 lol very hard.
Not trying to be negative just a bit worried is all
Can someone take a video of the boot loop
There's actually a method to how this phone loops. It could indicate the problem
Not sure about the camera but there's always ports into the future.. anything is possible! But could be a while till we are able to be booting any decent treble ROMs.. but then again as the source code has been released it may not be that long.. depends how quick the developers for treble react and whether or not they have a Huawei device to work with to fix our issues..
All we can do is hope!
---------- Post added at 11:12 PM ---------- Previous post was at 11:09 PM ----------
I will give it a try flashing a system image again tomorrow and take a video of it if I'm able to! But someone else needs to give it a try too just incase I don't get time please? The best way I can explain it is once the system.img is flashed in twrp I restart system as normal and it boots up normally with the Huawei logo when phone turns on then goes to bootloader unlocked screen and press different buttons for different options to boot from or wait until device boots normally so I wait for it to boot normally and soon as I get past the unlocked bootloader screen it just instantly reboots and just keeps rebooting doing that!
virtyx said:
Can someone take a video of the boot loop
There's actually a method to how this phone loops. It could indicate the problem
Click to expand...
Click to collapse
What signs are you looking for?
First time I tried it went from the press up for 3 seconds page then black, then vibrate then back to solid white Huawei, repeated 3 times until eRecovery asked to wipe.
For me after that point I flashed another and it went through to a lower case android sign, changing times from white to silver in a flow type effect, it stayed that way for around 10 minutes then back to eRecovery, flashing another treble ROM did the same thing.
Currently running: c782, 110, L09 p20 Pro, unofficial twrp and magisk.
The initial installation was via twrp, subsequent flashes wereb performed via fastboot.
Thats pretty much the same for me of what happens! Just boots then get a boot loop and black screen and back to the Huawei logo again from the start.. never able to actually boot a rom..
danielfrancisarthurs said:
Thats pretty much the same for me of what happens! Just boots then get a boot loop and black screen and back to the Huawei logo again from the start.. never able to actually boot a rom..
Click to expand...
Click to collapse
I thought the idea of treble was to match the Android version?
Seems as though it's trial and error with what's allowed.
Treble is still a work in development at the moment.. it doesn't help as well that Huawei are being assholes and making developers want to stay away from Huawei completely due to the whole locking bootloader thing but hopefully there are a couple of developers out there that keeps our devices in mind and hopefully means we will see a fix for our devices soon.. but when that is I have no idea..
danielfrancisarthurs said:
Treble is still a work in development at the moment.. it doesn't help as well that Huawei are being assholes and making developers want to stay away from Huawei completely due to the whole locking bootloader thing but hopefully there are a couple of developers out there that keeps our devices in mind and hopefully means we will see a fix for our devices soon.. but when that is I have no idea..
Click to expand...
Click to collapse
Aye it looks grim, that being said though, the stock ROM with a few tweaks is excellent, I've never once liked a stock ROM before on any device.
Root is easy, twrp is workable, bootloader was a breeze, we only have one actual ROM (LOS) but by all accounts even the p20 Pro camera works exactly the same on that, with that in mind what more do we need?
Course I'd like to be up to my neck in baked ROMs but if you're honest we truly only stick with one or two, as it turns out the two we have are pretty great.
Maybe I'm being optimistic
Just had a reply from another thread, quite interesting...
dladz said:
So in order...
Wipe
Flash ROM / IMG
Factory rest via twrp?
We're you referring to me by the way?
Click to expand...
Click to collapse
Yes, lol
the way i did it was with a stock recovery and system image
boot into erecovery and do a factory reset or a fastboot -w
boot back into the bootloader
flash the system image for the treble rom
then go into erecovery and do a factory reset
and then it should boot no problem at all
twrp cant wipe properly on treble roms
ive done the same on my p20 lite today, all stock and no issues booting at all
let me know how you get on
:good:
From this thread
https://forum.xda-developers.com/huawei-p20-lite/development/recovery-twrp-3-2-1-0-t3782866/page2
Hi, i have been occupied all day to get this to work, it just doesnt. i have followed the exact steps you layed out but when i try to factory reset after flashing the treble rom using fastboot it just gives me the error: "reset failed". I have tried using other GSI images but none work, had to restore my phone thrice because of this. I dont know what is the issue. These are the steps i followed:
1. Went completely stock ( no twrp or root )
2. Successfully factory reset my device.
3. Boot into fastboot and then flash a treble GSI.
4. as soon as the device turned on, went to the recovery to attempt a data wipe but at around 60% of the process completion the recovery gives the error with a red exclamation mark enclosed in the circle.
My device is a CLT-29 (C185). Was really looking forward to treble as my previous device was a Oneplus.
psycho.b94 said:
Hi, i have been occupied all day to get this to work, it just doesnt. i have followed the exact steps you layed out but when i try to factory reset after flashing the treble rom using fastboot it just gives me the error: "reset failed". I have tried using other GSI images but none work, had to restore my phone thrice because of this. I dont know what is the issue. These are the steps i followed:
1. Went completely stock ( no twrp or root )
2. Successfully factory reset my device.
3. Boot into fastboot and then flash a treble GSI.
4. as soon as the device turned on, went to the recovery to attempt a data wipe but at around 60% of the process completion the recovery gives the error with a red exclamation mark enclosed in the circle.
My device is a CLT-29 (C185). Was really looking forward to treble as my previous device was a Oneplus.
Click to expand...
Click to collapse
Ah the OnePlus , got the 5 still with me, great phone, great development.
Perhaps if your device was debrand? Could that be it?
Maybe it's just not meant to be
Hi there!
Just a quick question. Finally afer so much time since the actual update to emui 9.1 (Psmart Fig-lx1) Ive finally managed to get that **** done - i mean rooting that mother****er
From what I gathered if I want to reboot the phone I have to hold that power vol + button 'n 'stuff. So question remains simple.
**So if i would instal a magisk module and it reboots my phone - do I need to just hold that vol + button and the planet wont go boom, or is ther aleoso some specific stuff You need to co?
**Also - what does 'recovery mode option in Magisk Manager means?
Cheers!
Why would you have to hold the vol + button to reboot at all? That's not normal.
Sent from my LG-US998 using Tapatalk
kenbo111 said:
Why would you have to hold the vol + button to reboot at all? That's not normal.
Sent from my LG-US998 using Tapatalk
Click to expand...
Click to collapse
A recent method on installing magisk trough a patched recovery image require exacly that. And it's not the end. When You boot normally no buttons - You've got non rooted system (without magisk)
When You keep Vol+ till splash screen You've got system with magisk (full root)
And when You keep that VoL allll the way - You suppose to boot into recovery.
I too don't know how they pulled this off but just in case something wouild go wronga after instalation of the meodules I'd like to know in advence
That's wierd! I've never heard of that before
Sent from my LG-US998 using Tapatalk
kenbo111 said:
That's wierd! I've never heard of that before.
Click to expand...
Click to collapse
It's uncommon, but not unheard of. Rebooting that way be needed for devices where a Magisk patched boot image is swapped with the recovery image (since the modified boot image couldn't be put in place of the original, untampered one for some reason). In such cases, if you reboot to recovery, the Magisk modified boot image will be loaded instead of the recovery, which will lead to booting into a rooted ROM. This is how root also works for Samsung S9 and Note 9.
shadowstep said:
It's uncommon, but not unheard of. Rebooting that way be needed for devices where a Magisk patched boot image is swapped with the recovery image (since the modified boot image couldn't be put in place of the original, untampered one for some reason). In such cases, if you reboot to recovery, the Magisk modified boot image will be loaded instead of the recovery, which will lead to booting into a rooted ROM. This is how root also works for Samsung S9 and Note 9.
Click to expand...
Click to collapse
That sounds both incredibly annoying and tedious but also quite handy when it comes to recovering from bootloops when you aren't near a PC ?
Sent from my Pixel 3a XL using XDA Labs
Skittles9823 said:
That sounds both incredibly annoying and tedious but also quite handy when it comes to recovering from bootloops when you aren't near a PC ?
Click to expand...
Click to collapse
Yet, it is. That's why I'll never buy devices that can't be easily rooted. I forgot to add, since the images are swapped (original boot becomes recovery and recovery becomes Magisk patched boot), a normal reboot would lead to booting to recovery everytime and rebooting to recovery (either by a key combo or from the ROM itself) is needed to boot to system. Good times.
shadowstep said:
Yet, it is. That's why I'll never buy devices that can't be easily rooted. I forgot to add, since the images are swapped (original boot becomes recovery and recovery becomes Magisk patched boot), a normal reboot would lead to booting to recovery everytime and rebooting to recovery (either by a key combo or from the ROM itself) is needed to boot to system. Good times.
Click to expand...
Click to collapse
Ahh my brain hurts lmao.
I thought it would boot into an unrooted system if not using the recovery shortcut. Yea that does sound irritating.
Skittles9823 said:
Ahh my brain hurts lmao.
I thought it would boot into an unrooted system if not using the recovery shortcut. Yea that does sound irritating.
Click to expand...
Click to collapse
I am sure, lol. Also, if it boots to an unrooted system if not using the recovery shortcut and to a rooted system if using that recovery shortcut, how do you access recovery? Be glad you have a much more root-friendly device.
shadowstep said:
Also, if it boots to an unrooted system if not using the recovery shortcut and to a rooted system if using that recovery shortcut, how do you access recovery? Be glad you have a much more root-friendly device.
Click to expand...
Click to collapse
Haha yea, that's true.
Sent from my Pixel 3a XL using XDA Labs
shadowstep said:
Yet, it is. That's why I'll never buy devices that can't be easily rooted. I forgot to add, since the images are swapped (original boot becomes recovery and recovery becomes Magisk patched boot), a normal reboot would lead to booting to recovery everytime and rebooting to recovery (either by a key combo or from the ROM itself) is needed to boot to system. Good times.
Click to expand...
Click to collapse
In fact, the images are not swapped (at least on S10). If you hold the Vol key long enough, the recovery kernel will boot the recovery system, and if you release it, it'll boot android. So, a rooted system runs on the recovery kernel.
Keule-T said:
In fact, the images are not swapped (at least on S10). If you hold the Vol key long enough, the recovery kernel will boot the recovery system, and if you release it, it'll boot android. So, a rooted system runs on the recovery kernel.
Click to expand...
Click to collapse
Not sure about the S10, but they are definitely swapped for S9. More information can be taken from this XDA article (and the thread links referenced in it). :good:
given nice contidions, any phone can break just by using magisk modules that do tricky stuff to ur image. and since that applies on any magisk module for a varius of reasons, wellp there is no "safe" module. under certain circumstances every module can break **** down.
Hi,
Please indulge me if this it a bit silly, but I am confused about installing magisk from recovery. I flashed the patched image to recovery partition, as per the github guide (https%3A//topjohnwu.github.io/Magisk/install.html%23boot-image-patching, sorry for the encoding, system forbids me to post link cuz I am new). Yet at this point I am unsure about what to do next. This is what I see now when I boot my phone to recovery using key combo:
- Reboot system now
- Apply update from ADB
- Apply update from internal storage
- Wipe data/factory reset
- Wipe cache partition
- Mounts a storage
If I select "Reboot system now", nothing seem to happen and it all looks like a normal startup.
In short, I would like to know how to run to a ystem with Magisk enabled.
Thanks in advance!
You're not actually supposed to boot to recovery. You need to release the key combo once you see the splash screen. Reference:
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
Edit: and don't worry... Everyone's a noob at some point or another.
Didgeridoohan is right: It sounds like you're booting into your phone's stock recovery, instead of your custom recovery.
Forgive my presumptions, or if I sound condescending, but if you happened to have patched and flashed your partition mods with a PC, you might want to check if you even have a custom recovery installed. (I know that some phones aren't capable of having a custom recovery flashed, so your situation might be different.) If you don't have one, that would be the first step (most folks use TWRP). Once you can boot into your custom recovery, though, you should be good.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
Didgeridoohan said:
You're not actually supposed to boot to recovery. You need to release the key combo once you see the splash screen. Reference: ...install.html#magisk-in-recovery
Edit: and don't worry... Everyone's a noob at some point or another.
Click to expand...
Click to collapse
Right, this is the part where I get confused. I did follow the link you mentioned. After pressing [power] & [volume up] for about 8 seconds, I feel a vibration and the screen lights up, thats when i released the keys. I ended up getting that menu i describe above...(tears)...
Ideally, what should I see if things go right?
NeoHiPPy1980 said:
Didgeridoohan is right: It sounds like you're booting into your phone's stock recovery, instead of your custom recovery.
Forgive my presumptions, or if I sound condescending, but if you happened to have patched and flashed your partition mods with a PC, you might want to check if you even have a custom recovery installed. (I know that some phones aren't capable of having a custom recovery flashed, so your situation might be different.) If you don't have one, that would be the first step (most folks use TWRP). Once you can boot into your custom recovery, though, you should be good.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
Click to expand...
Click to collapse
No worries. Any suggestion is much ppreciated. Just to be sure (correct me if i m wrong), I thought that patching an image file is an independent way of installing magisk in case custom recovery is not available. So that s my case.
Anyhow, I would really like to learn a bit more about the situation where recovery partition contains both the stock recovery and custom recovery/patched image. There doesnt seem to be any difference whether i release the key combo or not once I see a splash screen. I always end up with that blue menu in recovery.
Wubwubdubdub said:
No worries. Any suggestion is much ppreciated. Just to be sure (correct me if i m wrong), I thought that patching an image file is an independent way of installing magisk in case custom recovery is not available. So that s my case.
Anyhow, I would really like to learn a bit more about the situation where recovery partition contains both the stock recovery and custom recovery/patched image. There doesnt seem to be any difference whether i release the key combo or not once I see a splash screen. I always end up with that blue menu in recovery.
Click to expand...
Click to collapse
If you don't mind my asking, which model of phone do you have? Most phones have a similar button combo, but are a bit quirky to get into the recovery.
Ex: On my LG V20, I have to hold Vol-, and Power, but release the power button at the splash screen for 0.5-1 seconds (while still holding Vol-) and then press/hold the Power button again...
As a suggestion, you may want to see if your phone has a similar quirk, depending on the make /model.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
[Solved] by flashing boot image instead of recovery image
I am still puzzled by the complications with booting into recovery mode. To work around it, I attemped installing Magisk using boot image patch and succeeded. Objective achieved yet question remains. Anyways, a big thanks to Didgeridoohan and NeoHiPPy1980. Knowing that someone will provide help is what stopped me from giving up.
NeoHiPPy1980 said:
If you don't mind my asking, which model of phone do you have? Most phones have a similar button combo, but are a bit quirky to get into the recovery.
Ex: On my LG V20, I have to hold Vol-, and Power, but release the power button at the splash screen for 0.5-1 seconds (while still holding Vol-) and then press/hold the Power button again...
As a suggestion, you may want to see if your phone has a similar quirk, depending on the make /model.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
Click to expand...
Click to collapse
I have a Ulefone, not sure if you ve heard of it
But that won't matter. I managed to get it working another way (see to my last post). I should probably have done that before making this post. Thanks for your assistance!
Great to hear you got things working, but why did you think you needed to use the recovery image for your device? Was any of the installation instructions unclear and in need of improvement (I'm just trying to learn for future reference)?
Didgeridoohan said:
Great to hear you got things working, but why did you think you needed to use the recovery image for your device? Was any of the installation instructions unclear and in need of improvement (I'm just trying to learn for future reference)?
Click to expand...
Click to collapse
Frankly, I find the Magisk Installation Guide to be one of very few documentation that is concise, coherent and user-friendly for both regular user and developer. So a big thumb up for you all! For your reference, here is the process of how I was lead to believe I needed the recovery img:
1.
I followed the instruction on "know your device" (https%3A//topjohnwu.github.io/Magisk/install.html#knowing-your-device). The first command returns nothing and the seconde comand returns true. Naturally, I assumed this means that my device is using system-as-root on a non-A/B device.
2.
I then read:
If your device is NOT A/B, but IS using system-as-root, then you will have to install Magisk to the recovery partition of your device. Follow the instructions in Boot Image Patching, but instead of using your boot image, use your recovery image. "
Click to expand...
Click to collapse
(https%3A//topjohnwu.github.io/Magisk/install.html#getting-started)
I am not sure if I misunderstood sth. At this point I still believe that according to the instruction I should have patched my recovery image. I do not know what system-as-boot actually is...
Yes, it does seem like your device is A-only system-as-root, which would normally mean you need to use the recovery image.
Unfortunately, with the Android ecosystem being as fractured as it is there will always be exceptions...
Thanks for the detailed response.
Hi Guys
Wubwubdubdub, I have got a question for you. I followed the same instructions as you mentioned in first post and ran into problems as well. How did you get around this problem? What is the difference between the two ways you mentioned here? (I believe I used the first way).
Wubwubdubdub said:
I flashed the patched image to recovery partition, as per the github guide
Click to expand...
Click to collapse
Wubwubdubdub said:
To work around it, I attemped installing Magisk using boot image patch and succeeded. Objective achieved yet question remains.
Click to expand...
Click to collapse
Thanks in advance!
MM