Feel free to haze me for what I'm sure is a stupid question.
After flashing the factory 5.1.1 image, is the Chainfire root method still the correct way to root? The 'fastboot flash boot' part made me wonder if it needs to be updated for the bootloader that shipped with the 5.1.1 image.
funkybside said:
Feel free to haze me for what I'm sure is a stupid question.
After flashing the factory 5.1.1 image, is the Chainfire root method still the correct way to root? The 'fastboot flash boot' part made me wonder if it needs to be updated for the bootloader that shipped with the 5.1.1 image.
Click to expand...
Click to collapse
Wrong question.
There is no "correct" or "incorrect" method. FWIW, it's a Nexus device. You don't need these automated tools. Just fastboot flash the TWRP image, boot to recovery and flash the latest SuperSU zip from recovery. Done.
cam30era said:
Wrong question.
There is no "correct" or "incorrect" method. FWIW, it's a Nexus device. You don't need these automated tools. Just fastboot flash the TWRP image, boot to recovery and flash the latest SuperSU zip from recovery. Done.
Click to expand...
Click to collapse
Thanks but that wasn't really my question and I hadn't planned to use the auto-root CF version. To clarify what I'm confused about: The manual CF Root process involves a step "fastboot flash boot {img}", and when checking the CF repository I see that this boot image was based on 5.0.x. From other threads I had understood the 5.1.1 factory image includes a new bootloader image, and this made me wonder if flashing the bootloader that ships with the chainfire root package would be a potential problem. I'm still curious about this, but now also:
Your response suggests I could avoid CF altogether if I'm willing to flash a non-stock recovery. Is that correct?
yeah I would skip CF and just do it the manual way. copy SuperSU to your device first.
@funkybside,
No. Flash all of the stock .img files except recovery. Fastboot flash TWRP.img instead. Then boot to recovery from fastboot on your device and flash the SuperSU.zip.
Alternatively, if you want to keep the stock recovery, you can
fastboot boot recovery "name of TWRP.img". Then flash the SuperSU.zip.
y2whisper said:
yeah I would skip CF and just do it the manual way. copy SuperSU to your device first.
Click to expand...
Click to collapse
That's the part that generated my question. Inside the SuperSU.zip are inject.img and patched.img. The readme states patched.img needs flashed with 'fastboot flash boot patched.img', and the package was made before the 5.1.1 drop. For all I know it's fine to do this, but since it's flashing a boot image I figured better safe than sorry and decided to post. I have searched here and all root threads/links seem pointed to videos using toolkits/CF-AutoRoot so I wasn't comfortable with following them. FWIW - At the moment I'm stock factory 5.1.1 image, stock recover, unlocked BL, not rooted.
Trying to be a self sufficient as I can...quickly becoming 'that guy'. ugh. The core question is does the patched.img inside SuperSU.zip cause any problems with a factory 5.1.1 unlocked device, due to potential differences between the factory 5.1.1 boot image and the one included in SuperSU.zip.
No you're just learning. I rooted my after without problems but I wonder if a new version will be done now that 5.1.1 is done for the N9
funkybside said:
That's the part that generated my question. Inside the SuperSU.zip are inject.img and patched.img. The readme states patched.img needs flashed with 'fastboot flash boot patched.img', and the package was made before the 5.1.1 drop. For all I know it's fine to do this, but since it's flashing a boot image I figured better safe than sorry and decided to post. I have searched here and all root threads/links seem pointed to videos using toolkits/CF-AutoRoot so I wasn't comfortable with following them. FWIW - At the moment I'm stock factory 5.1.1 image, stock recover, unlocked BL, not rooted.
Trying to be a self sufficient as I can...quickly becoming 'that guy'. ugh. The core question is does the patched.img inside SuperSU.zip cause any problems with a factory 5.1.1 unlocked device, due to potential differences between the factory 5.1.1 boot image and the one included in SuperSU.zip.
Click to expand...
Click to collapse
SuperSU is not device specific. 2.46 works fine on 5.1 on Nexus 6. I doubt the changes between 5.1 and 5.1.1 are significant enough to require a new version.
i use CF SuperSU Root Tool
1. Extract the earlier downloaded CF Auto zip folder on your computer.
2. Enable Developer Options on Nexus 9: in the About Device > tap Build Number multiple times until you see the new tab Developer Options. In here, check Enable OEM Unlock and USB Debugging.
3. Enter the Bootloader mode from your computer by running this command (open command prompt with Shift + Right Click > Open the command window here), adb reboot bootloader
4. Execute the root file,
Windows: run root-windows-bat
OS X: chmod +x root-mac.sh
run root-mac.sh
Linux: chmod +x root-linux.sh
run root-linux.sh
Once the command window finishes executing, your Nexus 9 will reboot.
Thanks to all of you. I guess I stop worrying and just give it a go. It seems like anyone who's had experience rooting 5.1.1 has not had any concerns or problems related to SuperSU.zip's patched.img being listed with a 5.0.x version on the CF site.
/me crosses fingers.
Edit: IT'S ALIVE! Thanks again folks.
In case anybody stumbles onto this thread, you might as well go with the "autoroot" method. Autoroot is smart enough to adapt to new boot images, and does not require installation of a custom recovery. What it is essentially, IS a custom recovery bundled with the root bits.
You "fastboot boot autoroot.img" the device. It loads the autoroot.img to memory, and executes it, and installs the internal root bits to the /system partition.
Also note: With a Nexus device, it is NEVER necessary to INSTALL a custom recovery image, since you can RUN a custom recovery image without actually installing it.
fastboot boot bootable.img
doitright said:
In case anybody stumbles onto this thread, you might as well go with the "autoroot" method. Autoroot is smart enough to adapt to new boot images, and does not require installation of a custom recovery. What it is essentially, IS a custom recovery bundled with the root bits.
You "fastboot boot autoroot.img" the device. It loads the autoroot.img to memory, and executes it, and installs the internal root bits to the /system partition.
Also note: With a Nexus device, it is NEVER necessary to INSTALL a custom recovery image, since you can RUN a custom recovery image without actually installing it.
fastboot boot bootable.img
Click to expand...
Click to collapse
I would only disagree on one point. This is fine as long as the user understands how to use ADB and fastboot, and how to get out of trouble if something goes wrong. We've seen too many inexperienced users get into trouble with automated tools who don't have the SDK installed on their PC and don't understand how to install drivers.
Related
I have an MDK S4. I have been running beanstown's rom for months with TWRP 2.5.0.2 with no issues. Today I decided to flash clockworkmod touch recovery in terminal emulator using the following command:
su
dd if=/sdcard/ recovery-clockwork-touch-6.0.4.4-jfltevzw.img of=/dev/block/mmcblk0p21
So now my phone won't boot at all. All I get is a screen that says:
Secure fail: kernel
System software not authorized by Verizon Wireless has been found on your phone...
UGH!!!! So now what? Do I need to do the following or is there another way around it?
http://forum.xda-developers.com/showthread.php?t=2301259
Please advise asap. Thanks.
mochamoo said:
I have an MDK S4. I have been running beanstown's rom for months with TWRP 2.5.0.2 with no issues. Today I decided to flash clockworkmod touch recovery in terminal emulator using the following command:
su
dd if=/sdcard/ recovery-clockwork-touch-6.0.4.4-jfltevzw.img of=/dev/block/mmcblk0p21
So now my phone won't boot at all. All I get is a screen that says:
Secure fail: kernel
System software not authorized by Verizon Wireless has been found on your phone...
UGH!!!! So now what? Do I need to do the following or is there another way around it?
http://forum.xda-developers.com/showthread.php?t=2301259
Please advise asap. Thanks.
Click to expand...
Click to collapse
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
k1mu said:
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
Click to expand...
Click to collapse
Thank you. My s4 is rooted. I *think* that I have solved my issue. I was able to get it to go into Odin mode power+vol down. I didn't connect to a computer (am at work and all of my android tools are at home). I just cancelled out of Odin mode and it booted up just fine. Now I tried to go into recovery again and got the same error as above and was able to get out of it the same way. I was able to go into ROM manager and flash regular non-touch CWM recovery and was able to boot to it without issue.
I suspect that my flash of the touch via terminal emulator didn't work right. Can anyone who has done it this way let me know how long the flash should take? I was at the su prompt and entered the dd line above (copy and pasted to avoid typos). It appeared to do something...there were some numbers maybe 5 or 6 per line and then it went back to the prompt so thought it was done. This didn't take it more than about 15 seconds to do. What should I see here?
I know that I can just flash it via ROM manager but wanted to be able to do it myself without rom manager and also be able to flash the latest twrp img if I want to (goo.im seems broken at the moment). Maybe I will try to do it via Odin later.
TIA.
you rock
I just got this same error and your steps worked perfect
Same problem except on i545vrufnk1
k1mu said:
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
Click to expand...
Click to collapse
Hello, I went to flash a recovery package with flashify and got the black screen with kernel fail. I was on the latest nk1 kernel.
please help
Hi! I'm really sorry to revive such an ancient thread but I've a similar problem.
I tried to use the dd command to update TWRP and wound up at this spot, but I was running a custom 5.1.1 system (jflte dev something or other from oct 2014 - recovery needed to be updated in order to install 7.1.1). So I tried to ODIN back to the old bootloader because I read it may have just become locked again, and now the system seems broken or missing, I'm not sure which. Phone no longer boots into the system and I get this error at recovery, so I'm hoping that if I flash an older factory image onto the phone, it'll restore it.
My question is, if I flash a stock image onto the phone, will it overwrite the bootloader and make my custom recovery dreams impossible? I went as far as to transplant the insides of this phone into a replacement when it first broke to maintain my MDK bootloader, so I'm really hoping I didn't **** myself here.
----
Edit:
So I've fixed my phone! The whole ordeal wasn't too too bad, but it was somewhat time consuming and difficult to divine on my own.
Now, I realize now I may have actually flashed the wrong .img file, which may have caused this whole issue. I'm actually not certain, because through the method that I fixed this problem with, I was able to flash what I would later find out was an incorrect .img for the recovery (jfltexx instead of jfltevzw ) but it did work properly, and I only found out when I got an error on trying to install the LineageOS zip.
I tried a bunch of things, but the one that worked was converting a twrp .img file to a .lok (loki) file. At the time of this writing, it happens that there's a bug in the latest twrp version that also prevents you from installing the system, but downgrading back to an older version will work, and I assume after 3.1.2 the bug will be fixed.
In order to do this, I wiped the system back to an MDK 4.2.2 system image I found here: https://forum.xda-developers.com/showthread.php?t=2301259
(dead link? Here's an archive: https://archive.is/LDnaY - I hit a bunch of dead links when I was figuring this process out and it was frustrating)
which preserved the mdk bootloader (because flashing anything newer than this will lock the bootloader, I've been told. I didn't dare try.)
I rooted that image by downgrading to the prerelease kernel and using motochopper to root, then upgraded back to the mdk kernel.
Then I grabbed the loki_tool from this thread:
https://forum.xda-developers.com/lg-g2/general/guide-how-to-flash-cwm-6-0-4-4-lokitool-t2813514
(Dead link? Here's an archive: https://archive.is/F7k29 )
and used a twrp .img file to create the recovery.lok file
Flashing through this method restored my custom recovery, and also made the samsung unlocked padlock bootscreen go away (I miss it already!). Having Android 7.1.2 on this phone is quite a treat though!
Hope that anyone else who winds up here in the future finds this useful! And I hope those links
Really didn't want to make a new thread about this but honestly people just jumped to conclusions without being helpful in my previous thread.
Long story short I'm trying to manually get 4.4.2: http://forum.xda-developers.com/showthread.php?t=2664561
I saw that I needed to get s-off, which requires root. Bootloader was already unlocked and so did everything here: http://forum.xda-developers.com/showthread.php?t=2273376
I installed CWM. It said to install a superuser tool so I installed SuperSU.
"You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead." was the next line. <-- I saw that message. Installed a kernel that he recommended: http://forum.xda-developers.com/showthread.php?t=2255900
After reboot I get SuperSU error: There is no SU binary installed and SuperSU cannot install it. If you just upgraded to Android 4.3, you need to manually re-root- consult the relevant forums for your device etc.
Can anyone help me get the proper SU Binary installed? Not a beginner to rooting as I've had had several previous phones before. Never encountered something as annoying as this.
On 4.3, 3.17.502.3.
I had the same issue when I installed 4.4.2 on my international One.
What I done to root was;
- downloaded SuperSU v1.80 zip from here.
- download SuperSu from the Play Store
- in SuperSU, select the option to install binaries via TWRP/CWM. (If it doesn't reboot to recovery, manually enter recovery)
- flash the supersu v1.80 zip and reboot
- open SuperSu and install the binaries using the normal option.
That then enabled my root. I'd tried quite a few different variations and this was the only method that worked for me.
Sent from my HTC One or Note 3 via XDA Premium 4
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
mch277 said:
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
Click to expand...
Click to collapse
You seem very confused about the whole rooting process ... what was the point in flashing the stock recovery ? Are you trying to install the OTAPkg.zip ?
what Rom are you wanting to install and whats flashing stock recovery have to do with it ?
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
mch277 said:
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
Click to expand...
Click to collapse
I wrote the thread you linked too
http://forum.xda-developers.com/showthread.php?t=2659374
and yes it is necessary to have stock recovery to take an OTA, but your post didn't mention taking OTA it said you had no SU installed.
to get into stock recovery
boot to bootloader
choose recovery
wait for black screen, hold vol up and then power
you will see something about sdcard fail .. ignore it till the menu comes up
then choose to flash OTAPkg.zip from sdcard
Recently I attempted to root my Nexus 9 (running 6.0.1, latest OTA update) using this guide: phandroid.com/2014/11/05/how-to-root-nexus-9
It didn't go so well and I ended up in a bootloop after completing the steps. I managed to resolve this by following the steps on the Google Developer Factory Images page using the latest Nexus 9 (Wi-Fi only) image (I did not re-lock the bootloader, however).
After this, the device booted fine, however it is not rooted (apps cannot get root access and rootchecker and supersu both state that it is not rooted). I would appreciate some help here, as I am not sure where I went wrong (for example does flashing the factory image de-root?) or how to gain root from here. Most of the guides I have seen are for android 5.0, and I am not sure if the software used/linked is still compatible. I am not planning on moving away from stock android on this device, so a custom recovery is not necessary for me, and most guides include installing CWM or TWRP (I'm not against this, I just figured it's not necessary.)
If anyone could link any guides that are still valid (or tell me what to do) it would be much appreciated!
That guide is way out of date and links you to wrong files. Flashing factory images will remove root.
Get latest TWRP image .
Boot your device to bootloader mode. Attach to PC issue this comand "fastboot boot <name of twrp.img>".
Have latest supersu.zip on your device before hand. Use the Temporarily booted TWRP to install that zip.
corkiejp said:
That guide is way out of date and links you to wrong files. Flashing factory images will remove root.
Get latest TWRP image .
Boot your device to bootloader mode. Attach to PC issue this comand "fastboot boot <name of twrp.img>".
Have latest supersu.zip on your device before hand. Use the Temporarily booted TWRP to install that zip.
Click to expand...
Click to collapse
Thanks! I've just gotten around to following your instructions, and that was totally painless. Much simpler and faster than anything I found elsewhere, too (Guess all the guides I found were hopelessly outdated).
Will this method work for all current devices (assuming I have the correct TWRP, of course)?
@Sithon
Should work with most nexus devices.
Other devices may have locked bootloaders and need different methods to root. Check the device forum.
The root programs either don't work or are run by
extremely shady companies like KingoRoot. If I ask something here, no one answer or I get incomplete answers.
There's contradictory information everywhere, like I heard I need root to be able to install a custom recovery.
And I heard I need to install the custom recovery to be able to root. Wtf?
Even the guys who create the programs like Clockworkmod provide no info, where is clockwork recovery?
Why is it conspicuously missing from the creator's website? Why does TWRP also provide no info on their website?
Is this some conspiracy to keep rooting out of the reach of anyone but the android elite?
I have seriously never seen such a frustrating mess in my entire career in IT of over 20 years.
Because the software rooting method is find security hole on device an exploit it. But Google has strengthened the security that was first put in place in Lollipop, essentially making it unfeasible to launch the su daemon with the required permissions just by modifying the /system partition. So only Systemless Root method will work on Marshmallow or above.
For how to root Marshmallow device, I suggest you to take a look at SuperSU forum.
Hope this help you
EXA Lab said:
Because the software rooting method is find security hole on device an exploit it. But Google has strengthened the security that was first put in place in Lollipop, essentially making it unfeasible to launch the su daemon with the required permissions just by modifying the /system partition. So only Systemless Root method will work on Marshmallow or above.
For how to root Marshmallow device, I suggest you to take a look at SuperSU forum.
Hope this help you
Click to expand...
Click to collapse
Thanks a lot! Could you tell me do I need to root it before I can flash a custom recovery like TWRP or Clockwork Recovery or can I flash those with fastboot regardless of the the tablet being rooted?
I was able to unlock the bootloader.
androidferret said:
Thanks a lot! Could you tell me do I need to root it before I can flash a custom recovery like TWRP or Clockwork Recovery or can I flash those with fastboot regardless of the the tablet being rooted?
I was able to unlock the bootloader.
Click to expand...
Click to collapse
If you are using fastboot, you don't need to worry about root.
You can flash recovery with fastboot.
androidferret said:
Thanks a lot! Could you tell me do I need to root it before I can flash a custom recovery like TWRP or Clockwork Recovery or can I flash those with fastboot regardless of the the tablet being rooted?
I was able to unlock the bootloader.
Click to expand...
Click to collapse
If you have a device with unlocked bootloader, then rooting it is easy.
First what you need to prepare:
1. A PC that have adb and fastboot installed
2. A custom recovery that match your device (TWRP Recovery for example)
3.. Enable the Usb Debugging on your device
How to:
1. Connect your PC and device with cable
2. Open cmd and enter this command:
Code:
adb reboot bootloader
3.Once your device boots into bootloader mode, enter this command:
Code:
fastboot flash recovery \Path-where-you-stored-the-twrp-file\twrp.img
4. Once TWRP is successfully flashed on your device, run the following command:
Code:
fastboot reboot
After that, you can boot into twrp recovery and install the SuperSU zip file to root the device.
Thats it, the usual way to root an android device. But if your device brand is Samsung, you have to flash recovery throught odin.
Hope this solve your problem.
EXA Lab said:
If you have a device with unlocked bootloader, then rooting it is easy.
First what you need to prepare:
1. A PC that have adb and fastboot installed
2. A custom recovery that match your device (TWRP Recovery for example)
3.. Enable the Usb Debugging on your device
How to:
1. Connect your PC and device with cable
2. Open cmd and enter this command:
Code:
adb reboot bootloader
3.Once your device boots into bootloader mode, enter this command:
Code:
fastboot flash recovery \Path-where-you-stored-the-twrp-file\twrp.img
4. Once TWRP is successfully flashed on your device, run the following command:
Code:
fastboot reboot
After that, you can boot into twrp recovery and install the SuperSU zip file to root the device.
Thats it, the usual way to root an android device. But if your device brand is Samsung, you have to flash recovery throught odin.
Hope this solve your problem.
Click to expand...
Click to collapse
You must be one of those Android elite he was talking about.
ninjasinabag said:
You must be one of those Android elite he was talking about.
Click to expand...
Click to collapse
lol not really, just a simple android lover
EXA Lab said:
lol not really, just a simple android lover
Click to expand...
Click to collapse
Thanks EXA Lab I really appreciate your help, but I have a local/generic brand device (SPC purchased in Spain)
It's not an international brand so there are no custom recoveries for it. Is there anything I can do in this case?
What is the name of your device?
gb_14 said:
What is the name of your device?
Click to expand...
Click to collapse
It's this:
SPC Glow 10.1 3G 3.1
SKU 9765108B
Designed in Europe, Assembled in China.
spc-universe.com
Smart Products Connection S.A.
androidferret said:
It's this:
SPC Glow 10.1 3G 3.1
SKU 9765108B
Designed in Europe, Assembled in China.
spc-universe.com
Smart Products Connection S.A.
Click to expand...
Click to collapse
The only way for you to try is to use some one-click root tool like KingRoot or something.
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?