Related
Credits:
- DooMLord -> his recovery sources on github, and his guidance on assisting me with setting up the build environment and for his kernel.sin unpacker.
- Sony Ericsson -> the kernel with this.
I wanted the stock kernel because of battery drain issues present in many custom kernels, mine included, because although I used the semc sources to compile my kernel, it still had worse battery drain than stock.
I have unpacked the zImage from the kernel.sin in the 4.0.2.A.0.42 and then made that and a modified ramdisk into a boot.img, which you can flash.
This is for people who want to stay with the stock kernel, but want clockworkmod recovery.
Kernel string version:
Code:
2.6.32.9-perf
[email protected] #1
Download: http://dl.dropbox.com/u/13729847/semc/kernels/stockCWM/boot.img
MD5: 1ad7e6db6258b73555f0e6ae73fe4fd6
To flash, use the command:
Code:
fastboot flash boot boot.img
If you are on linux:
Code:
./fastboot -i 0x0fce flash boot boot.img
Don't forget to say thanks if you use this!
Yo installed it the custom recovery works fine and now testing UPDATE-looks like its not starting up for me ill try a reflash UPDATE-its not working properly the system wont start man
Super interested in this since I went back to Stock rom moments ago so I can play FIFA 12. Will this work with the new HK 4.0.2.A.0.58 rom released as I have just put that on.
matknny said:
Super interested in this since I went back to Stock rom moments ago so I can play FIFA 12. Will this work with the new HK 4.0.2.A.0.58 rom released as I have just put that on.
Click to expand...
Click to collapse
wait now dat i think about it i have the same firmware as urs it doesnt work on it weird
matknny said:
Super interested in this since I went back to Stock rom moments ago so I can play FIFA 12. Will this work with the new HK 4.0.2.A.0.58 rom released as I have just put that on.
Click to expand...
Click to collapse
Yes, .42 and .58 use the same kernel.
Will this provide root? I only install Doom's for root & recovery, so if this does I'll use this instead. Thanks.
alreadyused said:
Will this provide root? I only install Doom's for root & recovery, so if this does I'll use this instead. Thanks.
Click to expand...
Click to collapse
No root, but you can flash RootXperia.zip in clockworkmod (search it on google: rootxperia.zip).
Done but having booted after installing and rebooted into recovery (which worked) then restarted to phone it wont boot. Black screen after Sony Logo.
Update: Boots after 15 minutes no battery but now android market is keep coming up unsuccessful
Update 2: It just will not boot so I had no choice but to flashtool 4.0.2.a.0.58 back to default. :-(
matknny said:
Done but having booted after installing and rebooted into recovery (which worked) then restarted to phone it wont boot. Black screen after Sony Logo.
Update: Boots after 15 minutes no battery but now android market is keep coming up unsuccessful
Update 2: It just will not boot so I had no choice but to flashtool 4.0.2.a.0.58 back to default. :-(
Click to expand...
Click to collapse
Actually had market problems myself too, it is very wierd :/
Doesn't work at all for me - fastbooted it left it for a bit
came back and got the red blinking light.
What is the trick to get a stock kernel.sin to a working boot.img ? (Spent most of this afternoon failing to get it to work). All I really want is ro.secure=0 (or ro.debuggable=1). fastbooting CWM is ok for me.
unrandomsam said:
Doesn't work at all for me - fastbooted it left it for a bit
came back and got the red blinking light.
What is the trick to get a stock kernel.sin to a working boot.img ? (Spent most of this afternoon failing to get it to work). All I really want is ro.secure=0 (or ro.debuggable=1). fastbooting CWM is ok for me.
Click to expand...
Click to collapse
Small how-to for creating insecure kernel
1) Unpack kernel.sin to get zImage and ramdisk (tools posted in my other thread)
2) unpack ramdisk
3) edit default.prop and set ro.secure=0 & ro.debuggable=1 then save file
4) repack ramdisk (cpio.gz)
5) repack into boot.img, using zimage + new packed ramdisk, using correct mkbootimg arguments
6) flash using fastboot
7) enjoy
PRO TIP:
Use ONLY LINUX FOR ALL OF THIS ELSE DEVICE WONT BOOT
Sent from my R800i using XDA App
DooMLoRD said:
Small how-to for creating insecure kernel
1) Unpack kernel.sin to get zImage and ramdisk (tools posted in my other thread)
2) unpack ramdisk
3) edit default.prop and set ro.secure=0 & ro.debuggable=1 then save file
4) repack ramdisk (cpio.gz)
5) repack into boot.img, using zimage + new packed ramdisk, using correct mkbootimg arguments
6) flash using fastboot
7) enjoy
PRO TIP:
Use ONLY LINUX FOR ALL OF THIS ELSE DEVICE WONT BOOT
Sent from my R800i using XDA App
Click to expand...
Click to collapse
Thats pretty much exactly what I did. (I did the initial split under windows though I will try again.)
I used the mkbootimg arguments from SE's building kernel blogpost.
help please
please help me somebody i have a problem i cant seem to fix , i flashed the doom kernel then flashed 4.3 icream sandwhich rom exactly like it said to do in the instructions re-booted ,It all booted up fine i played about with the rom for a few hours as you do then i went back to my backed up stock rom ,but heres where the problem happens on restoring my stock rom for some reason my camera doesnt work and playing youtube videos doesnt work and also when i try downloading from the market it just sits there for ever saying downloading but nothings happening i would be really greatfull if somebody can help me resolve this problem thanks..
are you asking this in all thread's?
flash stock rom with flashtool
help
@nickholtus where do i get the stock rom i cant find it plz help and also how do i use this flash tool thing help please somebody i need my phone working again because im going away for the week.
download flashtool
install drivers (in flashtool folder)
download stock (see development .42 .58 or .62)
flash with flashtool
DooMLoRD said:
Small how-to for creating insecure kernel
1) Unpack kernel.sin to get zImage and ramdisk (tools posted in my other thread)
2) unpack ramdisk
3) edit default.prop and set ro.secure=0 & ro.debuggable=1 then save file
4) repack ramdisk (cpio.gz)
5) repack into boot.img, using zimage + new packed ramdisk, using correct mkbootimg arguments
6) flash using fastboot
7) enjoy
PRO TIP:
Use ONLY LINUX FOR ALL OF THIS ELSE DEVICE WONT BOOT
Sent from my R800i using XDA App
Click to expand...
Click to collapse
Hey Doom, I'm trying to follow this, and I'm getting stuck
I downloaded the R800x 2.3.3 (3.0.1.E.0.88) TFT from here: http://forum.xda-developers.com/showpost.php?p=19438024&postcount=12
I unzipped it using xarchiver (installed on arch linux/available on sourceforge)
I ran unpack-kernelsin.pl, and I get two errors (that don't exit out of the perl script):
1) ramdisk written... gzip: no such file or directory
2) cpio: premature end of image
When I try to cpio-ing the ram disk, my computer just sits... How long should I wait, I have a netbook (i know, not the best for doing compiling) and the longest i've let it sit is about 10 minutes (i'm about to let it sit overnight to see if it'll work itself out)
If you could give me any pointers, that'd be outstanding
Thank you,
Pax
paxChristos said:
Hey Doom, I'm trying to follow this, and I'm getting stuck
I downloaded the R800x 2.3.3 (3.0.1.E.0.88) TFT from here: http://forum.xda-developers.com/showpost.php?p=19438024&postcount=12
I unzipped it using xarchiver (installed on arch linux/available on sourceforge)
I ran unpack-kernelsin.pl, and I get two errors (that don't exit out of the perl script):
1) ramdisk written... gzip: no such file or directory
2) cpio: premature end of image
When I try to cpio-ing the ram disk, my computer just sits... How long should I wait, I have a netbook (i know, not the best for doing compiling) and the longest i've let it sit is about 10 minutes (i'm about to let it sit overnight to see if it'll work itself out)
If you could give me any pointers, that'd be outstanding
Thank you,
Pax
Click to expand...
Click to collapse
for such things send me p.m.
Thanks to serajr here - https://forum.xda-developers.com/showpost.php?p=75505302&postcount=2973 Go directly to that post and give thanks.
You need:
Stock O ftf (best to use Flashtool/Xperifirm)
Modded boot img for 34.4.A.2.19 - https://mega.nz/#!AgtQ2Sob!JjLRcUVjuy6FNanjGY49g-YYmkcda04witfHp4hwvmo
Modded boot img for 34.4.A.2.32 - https://mega.nz/#!Z1tzEJbZ!e9ET_RtUpKjXRwnJa_TDsMrVwvT-hPxmk06KtryHOuc
Modded boot img for 34.4.A.2.85 - https://mega.nz/#!p5UwAabR!_ofmr_WdId9RdH48Xb3cZtSIzsQ6qcTJTAFYcKHFWJE
Kernel elf file to use with rootkernel [34.4.A.2.85] - https://mega.nz/#!M102lYTZ!9bj2KE-vbNWlej3Dw0NuiXJcfpgiy16svSHud73bLfw
Modded boot img for 34.4.A.2.107 - https://mega.nz/#!Nls0EQBR!Cc4lVcA85f8YeNTo8nMqsuwLzveW5duSbyeZDlI5kDE
Kernel elf file to use with rootkernel [34.4.A.2.107] - https://mega.nz/#!Zp10CASK!iGLE94Tj1SSk1U2p4KLpVrcGmD68C3YvqKMXD6VPFjI
Modded boot img for 34.4.A.2.118 - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA
Kernel elf file to use with rootkernel [34.3.A.2.118] - https://mega.nz/#!Ylcm1SwA!GuX9dfd2HAqLXy1jom-C6mgP0s4jYXl9qSySkvb_mtA
TWRP - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
1. Flash stock ftf from Xperifirm via Flashtool
2. After flash, connect in fastboot (before booting phone) and type in command line 'fastboot flash boot boot.img' (this assumes that your modified boot img is in the current directory,and is named 'boot.img'; otherwise, you need to edit the command accordingl)
3. Then type 'fastboot flash recovery twrp-3.2.1.img' (same note as above)
Done
Now, you can flash Magisk, (or whatever), and have root access.
If you want Drm fix, flash serajr's zip here - https://forum.xda-developers.com/attachment.php?attachmentid=4404527&d=1517335127
If you want to restore your own ta with munjeni tool, you will need to patch boot img yourself with rootkernel tool here - https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
How to get stock kernel elf and patch your boot img with rootkernel:
1. Download and build stock ftf from Xperifirm via Flashtool
2. Go to Flashtool > tools > sin editor, and navigate to stock kernel sin file, in the downloaded firmware folder. Click on sin file and choose 'exrract data', and it will create a kernel elf.
3. Follow the guide by serajr. You need only to put the kernel elf into rootkernel folder, then open a command prompt there and run 'rootkernel kernel.elf boot.img'. Answer all questions 'yes', unless you want to skip drm fix and restore your own ta, (if that's the case, you need your target file in that folder renamed to TA.img). After script runs, you will have a new boot img that you can use to follow the guide.
Done...
Magisk, MicroG, and Xposed tested... (update - I haven't tried yet, but I've read that Xposed not working on ...85; update 2 - confirmed, bootloop; update 3 - Xposed fix now available here - https://forum.xda-developers.com/x-compact/themes/xposed-fix-118-t3870673)
I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...
Can confirm the above method worked for me. I used the TA.img instead of drm fix, and i get root and security test still have widefine and fidokeys enabled.
Just slight reminder for linux user, you need to add execute permission on both `rootkernel` and `bootimg`, otherwise rootkernel tool will fail with permission issue.
levone1 said:
I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...
Click to expand...
Click to collapse
With which options is your modified boot image prepared?
maluus said:
With which options is your modified boot image prepared?
Click to expand...
Click to collapse
Dm-verity disable - yes
Force encrypt disable - yes
Drm fix - yes
For Drm fix you still have to flash serajr zip. If you want to restore ta with munjeni tool, you will need to patch boot yourself.
Op updated for 3-click root...
SuperSU,Xposed
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
...
Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).
I was able :laugh::good: Xposed release link
levone1 said:
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).
Click to expand...
Click to collapse
Oh, well. Thank you! It's working now.
Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks
Stephenhs said:
Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks
Click to expand...
Click to collapse
Can you try running the tool and creating the boot.img yourself? I use the singapore ftf and doesn't have problem booting the system (with the boot img I created myself). I do not put twrp on boot img though. I boot twrp from fastboot when needed
I created boot.img and everything works Thanks a lot!
I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...
Kianush said:
I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...
Click to expand...
Click to collapse
Post linked in op has special instructions for us with Xc - skip that part.
https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
hello guys, i've created a boot.img whit the tool of rootkernel whit my ta.backup but it does not work. the boot it's ok but if i chek my drm keys they say not provisioned. my ta.backup load 2.097.152 byte like the post shows. can someone help me? thanks
update:
sorry guys, i've done again the kernel patch whit my ta backup and this time goes perfect. i don't know why the first time didn't work but now it's ok!
I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).
Wxfdswxc said:
I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).
Click to expand...
Click to collapse
Twrp - https://forum.xda-developers.com/x-compact/development/twrp-3-2-1-decryption-t3751998
As for rebooting to system, can't say for sure... Root method involves only changing boot img, so shouldn't affect system. Any errors in fastboot, etc?
Original flash should be clean flash official stock ftf from Xperifirm. First boot could be 10 minutes...
Just picked the phone up, instantly unlocked the bootloader, flashed patched boot.img Magisk gave and root has been achieved.
Now to enjoy this beast as it should be enjoyed. Sure, the camera broke but screw the camera!
Hello my friend, excuse me. How do you get the boot.img file to Modify with Magisk manager? thank you very much!!
pablo19921989 said:
Hello my friend, excuse me. How do you get the boot.img file to Modify with Magisk manager? thank you very much!!
Click to expand...
Click to collapse
You get it from kernel.sin which can be found in the firmware. You can use rar to open it and extract kernel.sin.
I used a little tool called unsin.exe that converts the kernel.sin to kernel.img and you simply rename it to boot.img.
You put boot.img on your phone, load up Magisk, press install, press patch boot image.
It will put patched_boot.img in your downloads folder which you put on your pc and simply flash patched_boot.img via adb.
When you've done that, boot the phone and you have root.
thank youuuu so mach man. You're the best !!! I found the tool here, in xda (many thanks to Igor Eisberg). Your explanation has been clear and very useful to me. The file that I extracted from the firmware is "kernel_X-FLASH-ALL-B6B5.sin". And it worked !!!
Do not use your phone's camera? Sorry my bad english !!!
If the original posters are still around - what exactly do you mean by the camera isn't working? You aren't getting any photos at all?
I followed this but after converted the B6B5.bin into boot.img and flashed it, I got stuck with "your device is corrupted" and couldn't boot into recovery or anything. I'm on H8166 Dual Sim. Not sure if that makes a difference
Gkstates said:
I followed this but after converted the B6B5.bin into boot.img and flashed it, I got stuck with "your device is corrupted" and couldn't boot into recovery or anything. I'm on H8166 Dual Sim. Not sure if that makes a difference
Click to expand...
Click to collapse
I bricked mine as well, but in a different way... Can somebody please advise how to fix this? Thank you in advance, guys!
hi... greetings.
this is very important: I would love to see if u guide us the easiest/best way to unlock bootloader.
thx... have fun.
Dear specialists on the XDA,
Normally I ask no questions in order to save the precious time of people, however this time I have a problem which I fail to understand and cannot resolve using the documentation available on the internet.
I have committed extensive reading and know how to build software but am simply missing a link here.
Trying to boot a home build kernel on a oneplus7 pro device with no luck so far.
Here is the situation so far: I have after hours of headaches successfully built myself a kernel straight from the stock sources. No alterations just using the msm8150-perf.defconfig file and build successfully with clang 9.0.5. There are only a few warnings nothing serious and the dtb has many warnings but I get what I need. I have done this before for my oneplus 3 and indeed the kernel was working.
Assuming the kernel is in a functional state. I used the latest version of android image kitchen to unpack the boot image which I extracted (from the right active slot) and replaced the kernel file and repacked the boot.img successfully into a new image file.
No luck after trying to boot into the image using fastboot. Screen hangs forever. Bootloader is unlocked btw
So far I have tried:
1. Signing the boot image using boot signer
2. Unpack/repack using android image editor (which signs the image)
3. Repack using different kernel image files from xda which I expect to be good and working
4. Flash signed image straight into active slot.
5. Completely read through the anykernel1, 2 and 3 scripts to find answers.
No matter what I try. Kernel does not boot. Either the fastboot screen hangs forever or the system reboots back into its currently working active slot.
I have to add that this bootimage contains magisk.
I am out of ideas. Please help me out. I hope that you can point me into a good direction.
Hi, I've just bought a Cubot P50, it's a Chinese brand and seems more than decent for the price, I've rooted it with Magisk and I want to install TWRP on it but can't find anything for that brand. Has anyone came across a TWRP that might work on it?
Marko Lyno said:
Hi, I've just bought a Cubot P50, it's a Chinese brand and seems more than decent for the price, I've rooted it with Magisk and I want to install TWRP on it but can't find anything for that brand. Has anyone came across a TWRP that might work on it?
Click to expand...
Click to collapse
I have the same phone how did you root it ? If there a guide that is safe to use ? Thank you
Unlock the bootloader first, this step will factory reset your phone https://romprovider.com/unlock-bootloader-android/
On your PC:
1. Install Fastboot driver
2. Install MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed
3. Extract platform-tools
4. On your phone, Enable Developer Options, USB debugging and OEM Unlocking
5. Unlock bootloader (this step will factory reset your phone): Phone in fastboot mode, open command prompt on PC > fastboot devices > fastboot flashing unlock. Note this will cause the phone to show the "Orange State" warning on boot up. You can ignore this or remove it later.
(If device is unauthorised in ADB or Fastboot, go to Developer Options on phone, revoke USB debugging authorisation, disable then enable USB debugging. You should now get an authorisation confirmation dialogue when you try to connect with ADB/Fastboot. If not, type "adb kill-server", then "adb devices" or "adb start-server" in the command prompt).
6. Place boot.img on phone with USB file transfer (either from stock ROM, or read from phone using SP_Flash_Tool_v5.1924_Win) and patch it with Magisk v5.2. NO need to patch vbmeta.img
7. Transfer patched boot.img back to PC
8. Flash the patched boot.img to phone either with SP Flash Tool or Fastboot command in ADB (fastboot flash boot boot.img). Take care here, make sure it's the right image going to the right location and that ALL other files are de-selected, especially the preloader file, always de-select this when flashing any firmware unless you know what you're doing!
Phone is now rooted.
How to remove orange state warning on this device:
How to remove Orange, Yellow & Red state warnings on MTK
This guide will explain how to hide or remove Yellow, Red and Orange state warnings on a Mediatek Android device. Its ideal for those who feel irritated by constantly seeing these warnings on reboot.
www.hovatek.com
Edit: If you need a stock ROM for the phone it's here https://www.cubot.net/Support/id/78/cid/19.html#hh
Good evening, I would like to know if in the future it is possible to install a twrp with a custom rom?
Thank you have a nice day.
Good evening, I would like to know if in the future it is possible to install a twrp with a custom rom on the Cubot p50?
Thank you have a nice day.
Mark8:9 said:
Good evening, I would like to know if in the future it is possible to install a twrp with a custom rom on the Cubot p50?
Thank you have a nice day.
Click to expand...
Click to collapse
It is possible that in the future, developers may create custom ROMs and TWRP recoveries for the device, especially if it becomes popular among the Android community.
If a custom ROM and TWRP recovery becomes available for your device in the future, you will be able to flash it by following the instructions provided by the developer. Keep in mind that installing custom ROMs and recoveries comes with some risks, and it is important to backup your data and follow the instructions carefully to avoid damaging your device.
Good evening, can you tell me the correct procedure for how to Root the Cubot p50 smartphone? Thank you.
Mark8:9 said:
Good evening, can you tell me the correct procedure for how to Root the Cubot p50 smartphone? Thank you.
Click to expand...
Click to collapse
Well if you really want to know that, surely you would have read the entire thread? It's not that long. I gave complete instructions 5 posts up
Marko Lyno said:
Well if you really want to know that, surely you would have read the entire thread? It's not that long. I gave complete instructions 5 posts up
Click to expand...
Click to collapse
Good evening, be patient ... but where do I find Magisk 5.2 to download and how do I install it? Thanks good evening.
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
Just get the latest version and follow the instructions I posted.
Thanks for your work on the Cubot phone .Im a fan of them also. I found that twrp recovery 3.40 works on the Note 20/20Pro you just have to flash vbmeta BEFORE and AFTER you flash twrp to the device. Im also seeing separate websites claiming twrp 3.40 is also used with the Cubot P40 model. I dont see why it wouldnt work with the P50. Its worth a shot. Also theres alot more "familiars" with Mediatek phones like these in Hovatek forum. Since you already have information on how to root maybe consider starting your own P50 thread over there.
My references: https://www.hovatek.com/forum/thread-44810-post-233457.html#pid233457
elimoviebuff said:
Thanks for your work on the Cubot phone .Im a fan of them also. I found that twrp recovery 3.40 works on the Note 20/20Pro you just have to flash vbmeta BEFORE and AFTER you flash twrp to the device. Im also seeing separate websites claiming twrp 3.40 is also used with the Cubot P40 model. I dont see why it wouldnt work with the P50. Its worth a shot. Also theres alot more "familiars" with Mediatek phones like these in Hovatek forum. Since you already have information on how to root maybe consider starting your own P50 thread over there.
My references: https://www.hovatek.com/forum/thread-44810-post-233457.html#pid233457
Click to expand...
Click to collapse
Thanks for that. Is there a specific vbmeta to patch it with?
Good evening, can you give me the link to download a compatible cust recovery for the cubot p50? Thank you
The link is on the page just posted above. Here's the direct link to the file:
Hovatek
Download files
www.hovatek.com
Let us know if it works please, and what steps you took.
Good evening, how will I flash the lk file? Thanks.
Hi, you will have, or should have, downloaded a zip file containing a recovery.img. The recovery.img is the file you need to flash. Then follow the instructions here:
How to Install TWRP Recovery on Any Android 2022 [100% Working]
In this article, I will be showing you how you can install TWRP recovery on any Android smartphone. By following this guide you will be able to install
magiskapp.com
The TWRP Recovery file it refers to is the one you (hopefully) downloaded from this link:
Hovatek
Download files
www.hovatek.com
BUT, you also need to flash a vbmeta file BEFORE and AFTER the recovery.img, and I'm still unsure which vbmeta file it is, as elimoviebuff hasn't replied to my question regarding that.
Marko Lyno said:
Hi, you will have, or should have, downloaded a zip file containing a recovery.img. The recovery.img is the file you need to flash. Then follow the instructions here:
How to Install TWRP Recovery on Any Android 2022 [100% Working]
In this article, I will be showing you how you can install TWRP recovery on any Android smartphone. By following this guide you will be able to install
magiskapp.com
The TWRP Recovery file it refers to is the one you (hopefully) downloaded from this link:
Hovatek
Download files
www.hovatek.com
BUT, you also need to flash a vbmeta file BEFORE and AFTER the recovery.img, and I'm still unsure which vbmeta file it is, as elimoviebuff hasn't replied to my question regarding that.
Click to expand...
Click to collapse
I get it, but I have to flash the .bin to remove the yellow/red state on boot. I don't know how to install the lk.bin file. If you can help me. Thank you.
Ah I see, you're rooting the phone first. Ok I've just checked my own notes on this, so, if you have edited the lk.img file as described in that Hovatek thread, then do as follows:
When flashing with SP Flash Tool, make sure the correct lk.img file is chosen as SP Flash Tool chooses lk-verified.img by default (click along to the right of the file list under "Location" and choose your edited lk.img file here).
OR, flash with ADB (fastboot flash lk lk.img).
Then install Magisk on your phone if you haven't already.
boot.img is for rooting the phone, lk.img is only to remove the orange state message and the 5 second delay when the phone boots, it does not actually remove it's orange state and is not needed for the phone to be rooted.
To un-root, you should just flash the original boot.img and lk-verified.img from the stock firmware ROM file.
Marko Lyno said:
Ah I see, you're rooting the phone first. Ok I've just checked my own notes on this, so, if you have edited the lk.img file as described in that Hovatek thread, then do as follows:
When flashing with SP Flash Tool, make sure the correct lk.img file is chosen as SP Flash Tool chooses lk-verified.img by default (click along to the right of the file list under "Location" and choose your edited lk.img file here).
OR, flash with ADB (fastboot flash lk lk.img).
Then install Magisk on your phone if you haven't already.
boot.img is for rooting the phone, lk.img is only to remove the orange state message and the 5 second delay when the phone boots, it does not actually remove it's orange state and is not needed for the phone to be rooted.
To un-root, you should just flash the original boot.img and lk-verified.img from the stock firmware ROM file.
Click to expand...
Click to collapse
Good morning. Thank you for the information given.
I wanted to ask: is it necessary or useful to install an antivirus on your smartphone now that it's been rooted? Thank you.
I haven't but that's just down to personal choice really. It's certainly useful if you like to try stuff from unknown sources, although personally I've rarely encountered viruses on Android. I'm not saying they don't exist though.
Have you successfully rooted your phone then? What about TWRP, have you tried that yet?