Database Develop

how to install custome recovery in lenovo k3 note (Marshmallow)

I update my phone from lollipop to Marshmallow.
Now I try many times to install TWRP recovery with many different versions but it can't work and boot... Please give me solution for this.. model no. Is Lenovo k50a30.

mayurchhapra said:
I update my phone from lollipop to Marshmallow.
Now I try many times to install TWRP recovery with many different versions but it can't work and boot... Please give me solution for this.. model no. Is Lenovo k50a30.
Click to expand...
Click to collapse
I think your model number is k50a40. Follow this guide for flash TWRP recovery.
https://forum.xda-developers.com/k3-note/general/sp-flash-tool-tutorial-to-install-twrp-t3346041

I've installed the latest stable firmware by SP Flash (K50-T5_USR_ST1614_5.294.1_1604011150_mp1V2.39_CN) but now I was reading about that the Marshmallow roms need to be flashed with patched boot image for custom recoveries. I've just found S422_Patched_boot.img (I hope that file is all what I need). Could sb explain me how to do this?? The next move will be gapps/root and finally try to fix IMEI on my yellow but I am stuck...

kandolkandol said:
I've installed the latest stable firmware by SP Flash (K50-T5_USR_ST1614_5.294.1_1604011150_mp1V2.39_CN) but now I was reading about that the Marshmallow roms need to be flashed with patched boot image for custom recoveries. I've just found S422_Patched_boot.img (I hope that file is all what I need). Could sb explain me how to do this?? The next move will be gapps/root and finally try to fix IMEI on my yellow but I am stuck...
Click to expand...
Click to collapse
I don't know flashing patched boot.img is required to flash custom recovery. I flashed custom recovery directly without flashing patched boot image and it working well.

OK I did it. If u have K30-T5 (MarshalRom 6.0) it will works. Instruction below.
1. Copie K50-T5_PATCHED_BOOT_1621_DEV.RAR file to your device
2 Flash TWRP 3.x via SP Flash
3. Enter to the installed Recovery Mode
4. Choose instal that file what I've wrote above
5. Swipe to confirm Flash
6. Reboot system
I want to fix my IMEI now. I'd like to use SN Writer but I don't know which file MD1DB, and APDB should I select on Marshmallow.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Viper 4 android on G5S Plus working via Magisk module

Unlocked, rooted, magisk installed. Stock 7.1.1, resurrected kernel v3.0, TWRP 3.2.1 r15
All good.
Driver installed.
Processing is always: No
Anyone got it working? Tried everything under the sun.

barbaroja said:
Unlocked, rooted, magisk installed. Stock 7.1.1, resurrected kernel v3.0, TWRP 3.2.1 r15
All good.
Driver installed.
Processing is always: No
Anyone got it working? Tried everything under the sun.
Click to expand...
Click to collapse
I'm on validus 8.0, twrp r15, and it's all good...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try uninstalling the driver and re-installing. I am using SuperSU 2.82sr5 though, so if Magisk is the issue I'm probably not much help here.
Also - stupid question - you renamed the vendor/etc/audio_effects.conf file, right? I don't think it would install the driver if you didn't...just thought I'd ask tho to be sure.

startswithPendswithOOH said:
I'm on validus 8.0, twrp r15, and it's all good...
Try uninstalling the driver and re-installing. I am using SuperSU 2.82sr5 though, so if Magisk is the issue I'm probably not much help here.
Also - stupid question - you renamed the vendor/etc/audio_effects.conf file, right? I don't think it would install the driver if you didn't...just thought I'd ask tho to be sure.
Click to expand...
Click to collapse
Yeah works on 8 but doesnt seem to work on rooted stock as the OP describes. Installs fine, shows the drivers are there but nothing changes.

bishop0114 said:
Yeah works on 8 but doesnt seem to work on rooted stock as the OP describes. Installs fine, shows the drivers are there but nothing changes.
Click to expand...
Click to collapse
Yep, ur right...my bad. Somehow I misread the the OP as 7.1 resurrection & thought they were referring to resurrection remix ROM. Damn, I really need to get some glasses.
I tried to get it working on stock with SuperSU instead of magisk & got the same results as OP. Strange.

I git it working on stock rom without any changes in files. I installed the Resurrected Kernel, Magisk 14.6, V4A Magisk version after that was done I opened the app and changed FX Compatability mode to Compatible and didn't even have to change anything regarding files or removing the Audio Fx app. Hope this helps

Root Updating

Hello,
I have Magisk installed with TWRP on the official rom. I have a system update how can I install it?

selimsandal141 said:
Hello,
I have Magisk installed with TWRP on the official rom. I have a system update how can I install it?
Click to expand...
Click to collapse
*Visit the first link first and if you want then use 2nd one*
You can use orangefox recovery for ota updates, but you have to setup it first.
First backup everything you need ,via magisk and migrate. Also the Internal storage.
Read all replies from this thread. You'll understand everything.
https://forum.xda-developers.com/k20-pro/help/k20-pro-wont-update-installed-orange-t3980705
There is one more method, but you have to wait for it, everytime. Here's the link
https://forum.xda-developers.com/mi-9t/how-to/guide-ota-updates-stock-recovery-t3975027
Sent from my Redmi K20 Pro using Tapatalk

I just flash the recovery zip of the whole rom, then I reflash ofox recovery (fastboot) and magisk

itspdp said:
*Visit the first link first and if you want then use 2nd one*
You can use orangefox recovery for ota updates, but you have to setup it first.
First backup everything you need ,via magisk and migrate. Also the Internal storage.
Read all replies from this thread. You'll understand everything.
https://forum.xda-developers.com/k20-pro/help/k20-pro-wont-update-installed-orange-t3980705
There is one more method, but you have to wait for it, everytime. Here's the link
https://forum.xda-developers.com/mi-9t/how-to/guide-ota-updates-stock-recovery-t3975027
Click to expand...
Click to collapse
FPSUsername said:
I just flash the recovery zip of the whole rom, then I reflash ofox recovery (fastboot) and magisk
Click to expand...
Click to collapse
Can I just flash stock recovery and update from OTA or should I migrate to OrangeFox (can you provide links or steps? I am not a professional sorry))
My version is in the attachment.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

selimsandal141 said:
Can I just flash stock recovery and update from OTA or should I migrate to OrangeFox (can you provide links or steps? I am not a professional sorry))
My version is in the attachment.
Click to expand...
Click to collapse
Yes you can flash stock recovery. It should work.
But I never tried that.
(Sorry for the too late reply)
Sent from my Redmi K20 Pro using Tapatalk

[Q] Can't install magisk On Android 7.1.2

Can't install magisk After I granted root access I know I have to patch Boot.img but I don't know how to do it without PC
Using Sm-t113 OS : LIneageOS 14.1 Android 7 1.
Any idea ?
Thanks for helps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

you are already rooted if you can grant access. version 22 of magisk works entirely differently than it did before and you don't need it, plus it requires a PC to use the file it creates for you.
stick to flashing the v21.4 zip via TWRP and make sure to get the magisk manager apk that goes with v21.4!
delete v22 and don't update your magisk again

3mel said:
just flash version 21.4 via TWRP, you definitely can't use magisk v22 without a PC.
Click to expand...
Click to collapse
3mel said:
just flash version 21.4 via TWRP, you definitely can't use magisk v22 without a PC.
Click to expand...
Click to collapse
L
3mel said:
just flash version 21.4 via TWRP, you definitely can't use magisk v22 without a PC.
Click to expand...
Click to collapse
Should I flash unsu.zip before flashing magisk 21.4?

Rasty#5587 said:
L
Should I flash unsu.zip before flashing magisk 21.4?
Click to expand...
Click to collapse
are you actually rooted now and just tried to update the app ?
if yes then just delete the app and get the earlier version that goes with the v21.4 zip. if you are rooted that should be enough as you haven't actually done anything with v22.
if you're not currently rooted then download and flash 21.4 zip and install the manager that goes with it (no idea what the version number of that is).
don't try to use version 22 or above and don't update your manager app
actually to be 100% safe ignore all that above and just download v21.4 flash it and install the magisk manager apk that goes with it I don't know what version you might've used if you are rooted and you could have problems if the zip and apk don't match.

Lineage Recovery

Hi note 3 neo users. I am trying to build lineage-17.1. I am not a developer.
I am just a fan of Aman Kumar (Firelord)
And trying to understand what he did and how he did without having this phone.
All credits goes to Firelord and hard working devs of Exynos5420 team
I am just trying to apply their and other devs work to our device
Made our device tree look like devices from this site, its a different cpu but not so much different from ours https://github.com/exynos5420
Taking logcats of errors and applying patches from this site to our kernel and device tree https://review.lineageos.org/
Finally i built a working lineage 17.1 recovery. You can flash atached image directly from twrp. Its not a big thing but first for our device. I worked hard to make it work and fit to our recovery partition.
Next step is a working twrp with android 10 support.
Kernel source
Device tree
Common device tree
Vendor files
Common vendor files
Soong for low ram pc
Manifest

Reserved

Reserved

Hello bro how r u doing? so the recovery you uploaded is fully working means in last thread you told there are many problem to be solved is that all problem solved now? and also currently in my phone i flashed twrp 3.0.2 and its working fine so should i have to flashed this file? sorry for asking this type of questions but for my understanding i am asking.

There are different types of recoveries to flash roms like twrp, cwm, stock an lineage.
Its not important to flash this to your device becouse its just a step to working lineage 17.1.
Its interface is like that;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mseskir said:
There are different types of recoveries to flash roms like twrp, cwm, stock an lineage.
Its not important to flash this to your device becouse its just a step to working lineage 17.1.
Its interface is like that;
View attachment 5369847
Click to expand...
Click to collapse
Thanks for reply, so now you are now working on rom right?

Twrp 3.5.2_10 is almost ready. Then i will start to 17.1 rom.

mseskir said:
Twrp 3.5.2_10 is almost ready. Then i will start to 17.1 rom.
Click to expand...
Click to collapse
that's amazing, waiting for 17.1

Hello bro what's happening any further success?

farazkhld2 said:
Hello bro what's happening any further success?
Click to expand...
Click to collapse
Nope, working on kernel. Trying to upstream. Twrp 3.5.2_10 is ready but rom is not booting. Stuck on this error; your kernel is not supporting ambient capabilities. Trying to fix.

Our kernel version is 3.4.39. I am upstreaming it to 3.4.113 step by step.
Now i am on 3.4.41. Patching updates, solving conflicts, compiling kernel and testing it for every incremental update like 3.4.40 to 3.4.41.
After we got a working 3.4.113 version kernel i think everything will be more easy.
I will share every 10 step like 3.4.50 - 3.4.60.... if anyone wants to test. We can use upstreamed kernel on lineageos 14.1 either.