Database Develop

[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] Boot loop

Hi i recently installed xposed on my acer A-480FHD rooted tablet kitkat 4.4.4. The reason i installed xposed was for the app greenify. As i scrolled thru the settings for it i noticed it said "On some devices this may cause them to enter a boot loop" and something else i dont remember. I installed assuming i was not part of that list. When i installed it it told me that xposed would be running next time i boot up. After a few hours i decided to reboot it. Because why not. I rebooted it using chain fires app live boot and used its reboot option. Then i went into boot loop. If you need any more info i have some screen shots of my tablets details. Can you help me get my device out of boot loop? I am fine if you wanna debug my tablet live.

Should be easy
victolabs said:
Hi i recently installed xposed on my acer A-480FHD rooted tablet kitkat 4.4.4. The reason i installed xposed was for the app greenify. As i scrolled thru the settings for it i noticed it said "On some devices this may cause them to enter a boot loop" and something else i dont remember. I installed assuming i was not part of that list. When i installed it it told me that xposed would be running next time i boot up. After a few hours i decided to reboot it. Because why not. I rebooted it using chain fires app live boot and used its reboot option. Then i went into boot loop. If you need any more info i have some screen shots of my tablets details. Can you help me get my device out of boot loop? I am fine if you wanna debug my tablet live.
Click to expand...
Click to collapse
I think Xposed creates a rescue zip onto your SD card called Xposed-Disabler-CWM.zip
Try flashing that if you have a custom recovery. If you don't have a custom recovery or this doesn't fix it try reflashing the stock rom.

victolabs said:
Hi i recently installed xposed on my acer A-480FHD rooted tablet kitkat 4.4.4. The reason i installed xposed was for the app greenify. As i scrolled thru the settings for it i noticed it said "On some devices this may cause them to enter a boot loop" and something else i dont remember. I installed assuming i was not part of that list. When i installed it it told me that xposed would be running next time i boot up. After a few hours i decided to reboot it. Because why not. I rebooted it using chain fires app live boot and used its reboot option. Then i went into boot loop. If you need any more info i have some screen shots of my tablets details. Can you help me get my device out of boot loop? I am fine if you wanna debug my tablet live.
Click to expand...
Click to collapse
Whoa, an actual normal question about xposed. First time in a while.
You should be able to just reflash your rom

janekmuric said:
I think Xposed creates a rescue zip onto your SD card called Xposed-Disabler-CWM.zip
Try flashing that if you have a custom recovery. If you don't have a custom recovery or this doesn't fix it try reflashing the stock rom.
Click to expand...
Click to collapse
ldeveraux said:
Whoa, an actual normal question about xposed. First time in a while.
You should be able to just reflash your rom
Click to expand...
Click to collapse
victolabs said:
Hi i recently installed xposed on my acer A-480FHD rooted tablet kitkat 4.4.4. The reason i installed xposed was for the app greenify. As i scrolled thru the settings for it i noticed it said "On some devices this may cause them to enter a boot loop" and something else i dont remember. I installed assuming i was not part of that list. When i installed it it told me that xposed would be running next time i boot up. After a few hours i decided to reboot it. Because why not. I rebooted it using chain fires app live boot and used its reboot option. Then i went into boot loop. If you need any more info i have some screen shots of my tablets details. Can you help me get my device out of boot loop? I am fine if you wanna debug my tablet live.
Click to expand...
Click to collapse
Thanks for the help. None of those methods worked for me doe. As of this comment im reinstalling root now. But if others get in the same problem as i did i wont leave them in the dust. Here is what i did to fix my boot loop on my acer icona 8 A-840FHD.
First you wanna boot into stock recovery NOT CWM recovery. How i got into it was by holding the Power and volume up button at the same time. (assuming if your device is off) Then i was booted into recovery. If you are booted into fastboot then navigate to the "RECOVERY" Option using the volume keys and select it using the power button. The device will reboot into the appropriate menu. Then choose the option to WIPE your device, Factory reset Ect. After wipe is done reboot your tablet. Go thru the setup screen and proceed uninstall root using super su root manager. After that reboot tablet and update tablet to the latest ver. Then proceed to re-root tablet like you did the first time. And remember to not make the same mistake like last time. This is the guide i used to root my tablet.
http://forum.xda-developers.com/android/development/guide-root-acer-iconia-tab-8-a1-840fhd-t2933317
Guide 2.
Thanks! Victolabs

On a custom rom but cannot get into recovery >_>

EDIT: So after various attempts at rooting(pureRoot, multi-tool etc - I was able to root and install the updated su binary With the Windroid app. Also, I now know that Vol Up selects in fastboot. thanks to all who replied.
So I have the Moto X 2014 pure edition & thought I had rooted and unlocked bootloader. (I did because I'm on a custom ROM now...) But somehow I retardedly forgot to flash gApps and now don't have any way of getting apps etc restored. I go into fast boot and hit "recovery" but it doesn't do anything. The only way I was able to flash this custom ROM was because I had twrp manager app installed on stock ROM. But now since I can't get any of my apps back, I'm stuck. I got superSu apk but it says binary needs to be updated and keeps coming up with an error every time I try. I'm thinking I need to root again? I'm kinda at a loss... Don't know what happened. Any help is appreciated! Thanks

Flash twrp recovery.
Sent from my XT1095 using Tapatalk

I'm pretty sure I did that like 3 times through adb before I switched over to a custom ROM.. Couldn't get into it so that's why I downloaded the twrp app. :/

lilly0x said:
I'm pretty sure I did that like 3 times through adb before I switched over to a custom ROM.. Couldn't get into it so that's why I downloaded the twrp app. :/
Click to expand...
Click to collapse
Not to assume anything, but are you hitting the power button to select recovery from the fastboot menu? That was my mistake, lol. New to Moto. You have to hit volume up instead of power. That acts as the enter key for Moto. At least on this device. If that's what you're doing, can you connect to a computer and fastboot boot twrp.img ?

Wait so power isn't enter? I've been hitting power. -_- I could have swore power got me into recovery when I first rooted... I'm gonna try and if that's the problem. I'm such a fail at phones.

Okay so I got into recovery. d'oh! (Volume up selects. It says RIGHT THERE. Sorry guys lol) anyway, now my root apps can't verify root access. So I think I have to root again? It's been a couple years so please bear with me :/

Phone stuck in Samsung logo

Hi guys, I need help please!
I am using Samsung Note 3 SM-N9005 ARMv7 Lollipop 5.0. Rooted it with Kingoroot. "installed" TWRP through Flashify.
I downloaded Xposed Framework xposed-v86-sdk21-arm.zip onto my phone and installed it through TWRP in Flashify. Everything seemed fine, got the message install successful, I selected "reboot" instead of "clear cache/dalvik". Phone went into reboot...Samsung Note 3...Samsung logo...and stuck there. I understand that it takes some time for first boot, and I waited, but almost an hour and its still showing the same screen. So I tried to power off the phone, but it restarted again and stuck in the same logo screen. I tried to go into recovery mode hoping to get TWRP to do a reset or something, but no TWRP! Was only given option of "volume up - continue(to odin mode)" and "volume down - cancel(restart phone)". No option for factory reset either. So i booted odin, and tried to flash openrecovery-twrp-2.6.3.7-hlte.img.tar, got the messaged passed, phone rebooted and again stuck in Samsung logo. Tried recovery mode and still no TWRP! Please help!!:crying: :crying: :crying:
p.s. phone won't power off, only way to do it is to remove the battery.

Samsung phones stock ROMs need an special version of Xposed framework. Geez, it is on the official thread:
Known issues:
- Bootloops on Samsung stock ROMs. That's due to Samsung's changes to ART. There are unofficial builds that work around this by deodexing and adjusting the ROM.
Click to expand...
Click to collapse

Archy12 said:
Hi guys, I need help please!
I am using Samsung Note 3 SM-N9005 ARMv7. Rooted it with Kingoroot. "installed" TWRP through Flashify.
I downloaded Xposed Framework xposed-v86-sdk21-arm.zip onto my phone and installed it through TWRP in Flashify. Everything seemed fine, got the message install successful, I selected "reboot" instead of "clear cache/dalvik". Phone went into reboot...Samsung Note 3...Samsung logo...and stuck there. I understand that it takes some time for first boot, and I waited, but almost an hour and its still showing the same screen. So I tried to power off the phone, but it restarted again and stuck in the same logo screen. I tried to go into recovery mode hoping to get TWRP to do a reset or something, but no TWRP! Was only given option of "volume up - continue(to odin mode)" and "volume down - cancel(restart phone)". No option for factory reset either. So i booted odin, and tried to flash openrecovery-twrp-2.6.3.7-hlte.img.tar, got the messaged passed, phone rebooted and again stuck in Samsung logo. Tried recovery mode and still no TWRP! Please help!!:crying: :crying: :crying:
p.s. phone won't power off, only way to do it is to remove the battery.
Click to expand...
Click to collapse
When you flash TWRP, you have to have reset unchecked in Odin, when the flash finishes you pull the battery and then boot into recovery via button combo. If you don't do that TWRP doesn't stick. From there flash the Xposed uninstaller so you can boot properly.
Sent from my SCH-R220

io_gh0st said:
Samsung phones stock ROMs need an special version of Xposed framework. Geez, it is on the official thread:
Click to expand...
Click to collapse
Thank you for you reply. Yes, I understand that, which was why I have been trying to find the correct version. Did a few searches using my phone type and version and found a list of sdk21.zips...so i selected the latest version..

mattzeller said:
When you flash TWRP, you have to have reset unchecked in Odin, when the flash finishes you pull the battery and then boot into recovery via button combo. If you don't do that TWRP doesn't stick. From there flash the Xposed uninstaller so you can boot properly.
Sent from my SCH-R220
Click to expand...
Click to collapse
Thank you for your reply, I'll try that now.

mattzeller said:
When you flash TWRP, you have to have reset unchecked in Odin, when the flash finishes you pull the battery and then boot into recovery via button combo. If you don't do that TWRP doesn't stick. From there flash the Xposed uninstaller so you can boot properly.
Sent from my SCH-R220
Click to expand...
Click to collapse
I tried it, unchecked "reboot", flashed TWRP, power off. When I tried button combo, I can't boot into recovery. It either keep giving me the restarting loop (power on, samsung note 3..then power off, and on again..) or if i let go of the power button at note 3, it goes to the samsung logo and stuck there.
update: I kept trying, and finally got a little different response. I pressed volume up + home + power buttons, and got 3 small lines of colorful words...
Recovery booting
Recovery is not seandroid enforcing
Set warranty bit : recovery
and then the phone turns off and start again
Tried different combinations, so far only the volume up sequence showed something a little different.

Archy12 said:
I tried it, unchecked "reboot", flashed TWRP, power off. When I tried button combo, I can't boot into recovery. It either keep giving me the restarting loop (power on, samsung note 3..then power off, and on again..) or if i let go of the power button at note 3, it goes to the samsung logo and stuck there.
update: I kept trying, and finally got a little different response. I pressed volume up + home + power buttons, and got 3 small lines of colorful words...
Recovery booting
Recovery is not seandroid enforcing
Set warranty bit : recovery
and then the phone turns off and start again
Tried different combinations, so far only the volume up sequence showed something a little different.
Click to expand...
Click to collapse
If you your phone does not boot into TWRP right after you flash it it will not stick and you need to flash it again. To get into recovery is power+home+volume up
Sent from my SCH-R220

mattzeller said:
If you your phone does not boot into TWRP right after you flash it it will not stick and you need to flash it again. To get into recovery is power+home+volume up
Sent from my SCH-R220
Click to expand...
Click to collapse
Could it be the TWRP versions doesn't work on my phone?
I tried openrecovery-twrp-2.6.3.7-hlte.img.tar and also twrp-2.8.7.0-hlte-4.4.img.tar both getting the same results "recovery is not seandroid enforcing" when I pressed vol up + home + power

Archy12 said:
Could it be the TWRP versions doesn't work on my phone?
I tried openrecovery-twrp-2.6.3.7-hlte.img.tar and also twrp-2.8.7.0-hlte-4.4.img.tar both getting the same results "recovery is not seandroid enforcing" when I pressed vol up + home + power
Click to expand...
Click to collapse
That is ok, you get that when you have modified system/recovery. Means your are not fully stock. If you had full stock unrooted unmodified system and recovery that goes away, nothing to worry about. If you are still having problems follow these step exactly:
1) Pull battery out of phone then put it back in
2) boot to download mode (power+home+volume down)
3) open Odin on computer (run as admin)
4) plug phone into computer
5) Uncheck a. Reboot and f. Reset time in Odin
6) flash TWRP (TWRP.img file goes in AP)
7) after successful flash unplug phone and pull battery
8) put battery back in and boot directly to recovery (power+home+volume up)
If you let it boot normally without going into TWRP first, it does not stick
Sent from my SCH-R220

mattzeller said:
That is ok, you get that when you have modified system/recovery. Means your are not fully stock. If you had full stock unrooted unmodified system and recovery that goes away, nothing to worry about. If you are still having problems follow these step exactly:
1) Pull battery out of phone then put it back in
2) boot to download mode (power+home+volume down)
3) open Odin on computer (run as admin)
4) plug phone into computer
5) Uncheck a. Reboot and f. Reset time in Odin
6) flash TWRP (TWRP.img file goes in AP)
7) after successful flash unplug phone and pull battery
8) put battery back in and boot directly to recovery (power+home+volume up)
If you let it boot normally without going into TWRP first, it does not stick
Sent from my SCH-R220
Click to expand...
Click to collapse
Thank you very much!!! I am finally able to boot into TWRP and did a restore, now my phone is back on!! Strange though, I was doing exactly those steps earlier but not successful. Anyways, Thank you very much!! <3
Oh, since I'm here, can you give me advise on which version xposed framework I should get? (Although I don't think my phone is touchwiz, is there a way to find out/confirm? I'm a noob as you can see)

Archy12 said:
Thank you very much!!! I finally able to boot into TWRP and did a restore, now my phone is back on!! Strange though, I was doing exactly those steps earlier but not successful. Anyways, Thank you very much!! <3
Oh, since I'm here, can you give me advise on which version framework I should get? (Although I don't think my phone is touchwiz, is there a way to find out? I'm a noob as you can see)
Click to expand...
Click to collapse
Ok, now that TWRP is on there things should be easier. You are on Stock ROM, it is TouchWiz. You will need to flash a custom ROM that is deodexed. If you like the stock look, feel, and options look in the threads for your device for a stock deodexed ROM. Or you can flash CM. Depending on what version of Android you decide to run will dictate which version of Xposed you install.
Sent from my SCH-R220

I am getting a note3 and wanted to install xposed on it. the phone is running 4.3. with that version there is no need for flashing correct? simply download apk and install?

mattzeller said:
Ok, now that TWRP is on there things should be easier. You are on Stock ROM, it is TouchWiz. You will need to flash a custom ROM that is deodexed. If you like the stock look, feel, and options look in the threads for your device for a stock deodexed ROM. Or you can flash CM. Depending on what version of Android you decide to run will dictate which version of Xposed you install.
Sent from my SCH-R220
Click to expand...
Click to collapse
I am quite used to the look and functionity of the current version I am using...which is lollipop 5.0. My phone is Samsung Note 3 SM-N9005 ARMv7 international Qualcomm. I'll need to flash custom ROM and then get a "matching" xposed framework,correct? Could you please direct me as to how to get xposed framework to work please?

Archy12 said:
I am quite used to the look and functionity of the current version I am using...which is lollipop 5.0. My phone is Samsung Note 3 SM-N9005 ARMv7 international Qualcomm. I'll need to flash custom ROM and then get a "matching" xposed framework,correct? Could you please direct me as to how to get xposed framework to work please?
Click to expand...
Click to collapse
Just go to the threads for your device and flash a TouchWiz based deodexed ROM
Sent from my SCH-R220
---------- Post added at 07:41 AM ---------- Previous post was at 07:38 AM ----------
trulosdoulos said:
I am getting a note3 and wanted to install xposed on it. the phone is running 4.3. with that version there is no need for flashing correct? simply download apk and install?
Click to expand...
Click to collapse
Correct, you would need this one:
http://dl-xda.xposed.info/modules/de.robv.android.xposed.installer_v33_36570c.apk
Sent from my SCH-R220

There is now an Xposed framework package supporting Stock (odexed) TouchWiz ROMS: http://forum.xda-developers.com/showpost.php?p=65373013&postcount=3960

[Question] regarding installation of Magisk from recovery

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