[Question] regarding installation of Magisk from recovery - Magisk

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

Related

[Q] No functional recovery image... now what.

Ok, so after using clockwork rom manager on my nook color and seeing how convenient it was, I thought, "hey maybe this would be good on my milestone." WRONG. I flashed the clockwork recovery (they even had an option for milestone) and when I rebooted into recovery from the software (either in rom manager or the reboot power option) it just rebooted straight into android. When I held the power and camera keys, it just took me to bootloader.
Under rom manager, there was also an option to flash the RA recovery, but that didn't seem to help (exact same behavior as clockwork recovery).
I'm currently running the CM7 mod and prior to this fiasco, I was using RA 1.7 (pretty sure). edit: RA 1.7 was my girlfriend's HTCmagic, I just remembered that I would have had some version of openrecovery on this phone.
So, I guess my question is, what are my next steps here? I'd really like to stop flying without a recovery. My only shred of an idea was to flash a stock image from rsdlite and set my milestone all the way back to stock and then reroot and re everything, but if someone has a better idea, I'd be very open to that as my plan seems like a big hassle.
A) not really the place for this post but anywa
B) you should beable to just flash the Vulnerable recovery http://android.doshaska.net/rootable then you can install a recovery from this forum thats for our phone!
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Tyfighter said:
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Click to expand...
Click to collapse
Quite alright if you have any more problems feel free to just PM me
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1139120
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Tyfighter said:
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Click to expand...
Click to collapse
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
zacthespack said:
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Click to expand...
Click to collapse
what your doing (power + camera) is meant to put you into the bootloader mode... to get into recovery, hold 'x' on the physical keyboard and then hold the power button. This will get you into recovery. Hope this helps.
~D
are you sure that you did in fact flash the vulnerable bootloader, and not a newer, non-vulnerable one? sounds like that.. exploit fails, system reboots. also, if you are running an original rom right now, it does check the bootloader every reboot and flashes the non-vulnerable one!
Tyfighter said:
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
Click to expand...
Click to collapse
I'm a bit confused with how you're getting into Recovery mode, but the way to enter recovery is to hold Power + X, then Camera + Vol Up when you see the Motorola Logo.
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
EDIT: Despite RSD lite saying that the process as a success, the reflash did nothing.
Tyfighter said:
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
Click to expand...
Click to collapse
Where did you get the VR sbf? android.doshaska.net/rootable ?
Yep, that's the one.
EDIT: Finally got up the guts to load the official Telus sbf into RSD lite and pull the trigger. It seems like this is probably beyond salvage now. Once again, many thanks to everyone, and if all goes well, I hope to only be in the ranks of the unrooted/unmodded for a few minutes.
EDIT the second: Okay, so flash to stock went perfectly. Everything works, including recovery, but not openrecovery. I can get to the menu to flash the .zip, but it fails the esignature check. Which I'm assuming points to Vulnerable recovery not flashing correctly or perhaps my file is corrupt, or maybe something more exotic and exciting. I flashed SHOLS_U2_03.11.0 if that's relevant.
For those interested, everything is up and functional again.
I had to first flash back to stock, then flash the vulnerable recovery located at http://modmymobile.com/forums/downloads.php?do=file&id=28089 , then the standard, boot to recovery, blah blah blah, install a new rom.
Let this be a lesson to the rest of you; Clockwork Rom Manager does not, I repeat, does NOT seem to work on our milestones. Which is a real shame...
I realize this is a double post, but I'm just so darned jubilant to be able to update my rom again.

[Q&A] [RECOVERY] TWP 2.7.1.0 for One Mini 2

Q&A for [RECOVERY] TWP 2.7.1.0 for One Mini 2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWP 2.7.1.0 for One Mini 2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
new twrp's won't work
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Hornochse7958 said:
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Click to expand...
Click to collapse
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
kativiti said:
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
Click to expand...
Click to collapse
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Hornochse7958 said:
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Click to expand...
Click to collapse
Read this tread. Someone had the same problem
http://forum.xda-developers.com/one-mini-2/help/rooting-htc-one-mini-2-t2880936
Unresponsive after boot up from dead battery
THanks to U-ra I get the enjoy my fav DSP Viper!!!
Cheers Man,
I have a small niggling problem that I can't work out, My battery tends to die alot, once I place the phone on charge after a flat battery, the phone auto boots to Twp, I am really cool with that but the annoying thing is buttons and screen are unresponsive? I can't do a thing, just have the Twp menu. The power of button does turn the screen off/on but thats its. Tried doing factory resets, reboots holding down power, vol buttons. Just nothing.
only way around it is to use adb and reboot command.
Is anyone else experiencing this problem.
http://forum.xda-developers.com/one...recovery-twp-2-7-1-0-one-mini-2-t2801370/page 4 here's the answer, so far
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
gibihr said:
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
Click to expand...
Click to collapse
I'll try to get to it this weekend.
HELP TWRP stuck at swipe to unlock
Hello all,
for unknown reason the phone restarded and now is stuck at swipe to unlock but it is not working. I try to hold power+volume down, but no way to turn it off. What can I do?
Thanks in advance
PS: well, it restarted... I don't know what happend but now it's ok
sorry for sounding like a newb
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
akubenz said:
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
Click to expand...
Click to collapse
you can try but i think someone here couldn't unlock bootloader trough HTC Dev.
Help: Stock rom updated between boots, TWRP non responsive, fastboot doesnt recognise
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
I think I have found the solution for myself: I went back into the stock rom and did a factory reset (from within android booted up as normal), which after completion rebooted me into TWRP which now works fine (is responding to touch again, and i can flash the Cyanogen image now). Hopefully this helps someone else in this situation one day, or maybe I am the only idiot that needed to ask hehe. I should clarify that after flashing TWRP I lost access to the fastboot screen and could not push anything over ADB or fastboot commands from windows (plugged in via USB). Holding down volume down and power booted directly into TWRP, and i had no way to get to fastboot screen. After doing factory resent from within the Android OS, holding volume down and power booted me to the fastboot screen, and only when I selected "Recovery" did it take me to TWRP, and I was again able to run fastboot and ADB commands from PC. Weird (or maybe not if you know more than me), but there it is...
snorglamp said:
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
Click to expand...
Click to collapse
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
corbeau56 said:
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
Click to expand...
Click to collapse
I do indeed know the difference between the bootloader and recovery, its just that the bootloader (Hboot) was not longer accessible in my situation and TWRP (the recovery) was imposing itself when you would normally expect to find the bootloader (i.e. my bootloader was for all intents and purposes replaced by my recovery, while I am sure this is not true in fact, it was in effect). As I say, doing a factory reset from within the OS restored the bootloader (HBoot) and I was able to continue modding. I am today extremely happy with my fully secured cyanogenmodded HTC One Mini 2 via TWRP recovery method. I hope that is somewhat clearer.
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
corbeau56 said:
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
Click to expand...
Click to collapse
That may well have been an alternative solution to my problem, however it was fixed by the factory reset and volume down and power then took me to HBoot (this would appear to contradict what you have said above, but maybe volume down and power does different things depending on how what you have done to the phone, not sure), so I cannot confirm whether or not that also would have worked for me. Good suggestion though, especially if you are not in a position to do a factory reset. and it would certainly be easier if it worked...I am convinced my problem was the result of a conflict between the TWRP version i installed (downloaded from here) and the android update that occurred between boots.
I am indeed able to get into bootloader/hboot and successfully flashed cyanogenmod from TWRP. I can confirm post flashing TWRP and Cyanogenmod, holding volume down and power takes me to HBoot (and then the option to go to fastboot or recovery).
Holding power up and power just loads cyanogenmod for me now as if I had just pressed power.
I thought I should confirm whether or not holding volume up vs volume down with power results in bootloader vs recovery loading. For me, they both took me to TWRP.
Also, TWRP doesnt seem to work on HTC One Mini 2 after you do anything to set up your phone. It just doesnt recognise touch input any more so you cant do anything with it. However the fix i noted earlier (factory reset) even works with other roms installed, confirmed for cyanogenmod 11 and 12 nightlies as at the date of this post. After factory reset TWRP works again, but if you go through the setup steps and start installing apps, TWRP goes unresponsive again. I hope we might get an official TWRP update soon!

Alternative boot mode vol + and - at once

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

Chinese on boot

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!!

Does installing any modules is actually safe?

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.

Categories

Resources