Related
I been searching around all over the place and I am just hitting my head against the wall. Any help would be appreciated.
This is my setup: hboot 1.5 S-ON, I have unlocked using the HTC method. I have Revolutionary CWM recovery installed.
I am looking to update the Kernel and Radio/PRI of the phone to the latest versions. (I haven't done it in a very long time.)
By what I read, since I have hboot 1.5 updating the kernel seems close to impossible. I did read that I may have to go to a Stock Rom and update via sprint OTA to get the latest updates then unlock again? That doesnt sound right to me.
I am all types of confused. Part of this was started because I wanted to try the MeanROM (link:http://forum.xda-developers.com/showthread.php?t=1466362) and also update my phone. Everything I try to do fails or I cant do because of the 1.5 or the S-ON.
Hopefully i am making some sense. I dont know what I have to do to get the latest kernel or if it even is possible.
If you are rooted already the only thing you need to do is install flash GUI app (you can get it in the market) and flash the kernel (boot.img) file before you flash the ROM and you should be OK
There is a myth that if your on 1.5 s-on your doomed, that's not true. It does mean that you'll need an extra step to do things but you'll be able to get things done without issues.
Sent from my Xoom using Tapatalk
megabiteg said:
If you are rooted already the only thing you need to do is install flash GUI app (you can get it in the market) and flash the kernel (boot.img) file before you flash the ROM and you should be OK
There is a myth that if your on 1.5 s-on your doomed, that's not true. It does mean that you'll need an extra step to do things but you'll be able to get things done without issues.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply, so I understand I can load that application, unzip the rom I want which will have the boot.img. Then flash that boot.img and then install that rom, is that correct? Lastly, does this also update the radio and pri?
spiderz13 said:
Thank you for the reply, so I understand I can load that application, unzip the rom I want which will have the boot.img. Then flash that boot.img and then install that rom, is that correct? Lastly, does this also update the radio and pri?
Click to expand...
Click to collapse
If your firmware is compatible with the Rom and kernel yes. If not, you will brick your phone or features will not work as they have to do. After you install flash GUI go to browse button and you will be advertised that file is too large for a kernel or recovery image, then asks if it is a valid Rom zip file. Tap yes and it will search the kernel inside the Rom. After it finishes tap flash and after reboot in recovery(you have to have recovery.img in root of your SD card), next wipe dalvik and cache, install zip and wait until the phone finishes. It is also recommended to you to make a nandroid backup before install anything.
spiderz13 said:
Thank you for the reply, so I understand I can load that application, unzip the rom I want which will have the boot.img. Then flash that boot.img and then install that rom, is that correct? Lastly, does this also update the radio and pri?
Click to expand...
Click to collapse
For the EVO 3D, much like the EVO 4G, the custom ROMs generally do not contain the radio or pri images.
There are some different reasons for this, but one of the common reasons being some users claim to experience different radio performance based on their geographic loation in relation to different versions of the radio and pri images.
luis4ever said:
If your firmware is compatible with the Rom and kernel yes. If not, you will brick your phone or features will not work as they have to do. After you install flash GUI go to browse button and you will be advertised that file is too large for a kernel or recovery image, then asks if it is a valid Rom zip file. Tap yes and it will search the kernel inside the Rom. After it finishes tap flash and after reboot in recovery(you have to have recovery.img in root of your SD card), next wipe dalvik and cache, install zip and wait until the phone finishes. It is also recommended to you to make a nandroid backup before install anything.
Click to expand...
Click to collapse
The only clarification to this post would be having recovery.img in the root of your SD card is not required for rebooting into recovery mode. In order for a custom recovery to load, when rebooting into recovery mode, the recovery.img has to have been flashed previously. Flash Image GUI can also flash the recovery.img to the recovery partition so when you reboot into recovery, the proper custom recovery loads. Most users flash custom recoveries infrequently when compared to how often they flash ROMs so the process for flashing the recovery process isn't covered as often.
In general, regarding the OP's original question of flashing the "MeanROM", the Flash Image GUI thread provides a great beginner step by step guide I wrote to help walk thru the general overview and process. I've quoted it below for easy reference.
Appreciate all the support of Flash Image GUI! I'll echo the optimism for hboot 1.5 s-on unlocked users, most everything is still possible. HTC just requires an extra few steps which can be frustrating, but once they are learned, the process is fairly smooth.
Hope the clarification helps iron out any confusion on the details!
HTC Unlock - Hboot 1.5 Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using HTC method for Hboot 1.5 users
2) Load this application, Flash Image GUI, onto the device, either through the Market or the link provided in this OP.
3) Download ROM .zip file to the sdcard on the device.
4) Open up Flash Image GUI, select Browse and select the ROM .zip file, downloaded to /sdcard in the previous step.
5) Flash Image GUI will provide a warning, reminding that the ROM .zip file will *need* to be flashed in the custom recovery afterward.
6) Flash Image GUI will index the full ROM .zip file searching for the kernel and kernel modules. Once located, the Flash Image button should be enabled.
7) Select the Flash Image button and Flash Image GUI will load the kernel modules and kernel from inside the ROM zip file.
8) Select reboot recovery.
9) Inside the custom recovery, load/flash the ROM zip file.
10) Reboot to normal Android mode and all should work including Wifi!
Click to expand...
Click to collapse
I would be grateful of some help. I have successfully unlocked the Bootloader, flashed a custom kernel and rooted my Xperia Z Ultra on 4.4.2.
The problem I have is when trying to flash CM11 nightly using TWRP and CWM Recovery. I carry out the wipes in TWRP, then proceed to select the CM11 latest nightly to flash. On swiping the bar to begin the flash, the process fails and the following message displays:
"E: Unknown File System: 'datamedia'
Updating partition details...
Running book script...
Finished running boot script.
Installing '/external_sd/Xperia Root/CM11/cm-11
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
This package is for "C6802, C6806, C6833, C6843 to
E: Error executing updater binary in zip '/exter
Error flashing zip /external_sd/Xperia Root/CM
Updating partition details...
FAILED
(I think some of the text to the right of the window has been cut off)
When I Power Off my device in TWRP a message displays saying I don't have root, do I wish to install supersu. I went with this message and assume supersu installed when I powered off. However, on powering back on and re-entering TWRP and trying again, I am still unable to flash my CM11 zip.
I have also re-downloaded the CM11 zip, all to no avail.
To confirm, I can access TWRP and CWM, but can't install my CM11 nightly zip. I have tried installing from the internal SD to no avail.
pretty pixel said:
I would be grateful of some help. ...
Click to expand...
Click to collapse
Flash the boot.img from the ROM zip using flashtool and put the phone into fastboot mode. Hold the vol up key when connecting the ZU to the PC (phone powered off of cause) and select fastboot mode in flashtool flashing dialog. you will have to change to .img from .sin in the file open box
Thank you so much for the reply and support. I'm new to the ZU coming from a Samsung Galaxy Note 2, so please forgive my inexperience.
When you say "Flash the boot.img from the ROM zip", do you mean the CM11 nightly ROM? I only have the ZIP file downloaded from CM website.
Could you please explain the process in simpler terms please?
Thank you again
pretty pixel said:
Thank you so much for the reply and support. I'm new to the ZU coming from a Samsung Galaxy Note 2, so please forgive my inexperience.
When you say "Flash the boot.img from the ROM zip", do you mean the CM11 nightly ROM? I only have the ZIP file downloaded from CM website.
Could you please explain the process in simpler terms please?
Thank you again
Click to expand...
Click to collapse
Quick explanation of what the issue is:
Some kernels/recoveries are ported from the Z1 so tell the ROM installer script that it is running on the wrong type of phone. As you have a ZU (I hope) we can get around this by flashing a new kernel and recovery to the phone, this is the boot.img that you can extract from the ROM zip that you are trying to flash.
This assumes that the phone has an unlocked bootloader, if not you cant run a custom ROM
Save the ROM to the internal storage of the phone (I always use /sdcard/0/Downloads)
Open the CM ROM zip in 7zip/winzip/etc and just extract the boot.img to somewhere (desktop will do)
Open flashtool (https://unrestrict.li/flashtool)
Select the thunder bolt
Select fastboot mode
Select 'Select kernel to flash'
Open the folder where you saved the boot.img file, and change the file type at the bottom from *.sin to *.img and open boot.img
With the phone powered off connect to the PC while holding the vol up key
Wait for about 1-2 seconds (you will see OK in the main flashtool window)
Reboot into the new recovery and flash the ROM like normal
Thank you so much for your support. I will follow your instructions this afternoon, when I have some free time and report back
I've just followed your instructions and they worked perfectly! Thank you so much
After, I flashed the boot.img with Flashtool I was able to install the CM11 rom without issue And I now have a new recovery - CWM which is fine.
Am I correct in thinking that future CM11 zips should now install OK, without having to flash the boot.img each time?
Many thanks again.
pretty pixel said:
I've just followed your instructions and they worked perfectly! Thank you so much
After, I flashed the boot.img with Flashtool I was able to install the CM11 rom without issue And I now have a new recovery - CWM which is fine.
Am I correct in thinking that future CM11 zips should now install OK, without having to flash the boot.img each time?
Many thanks again.
Click to expand...
Click to collapse
Yep that is correct, and any other ROM should install just fine as well.
That's great, Thank you again
Through rooting and flashing CM11 on the Z Ultra, it's made it so much nicer to use and taught me lots too.
Install CM11 Z ULTRA
Ola amigo, se possivel faça um tutorial ensinando a flashear a cm 11 no Z ultra brasileiro.
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.
Hello all,
It's a long time that's i haven't post a thread here but i have a question.I have a Poco with MIUI Global 9.6 Stable (9.6.25.0) for ROM with a Android Version 8.1.0 OPM 171019.011 with root acces, unlocking bootloader and TWRP 3.3.0-0 installed.
I would upgrade my phone to something "newer" (A ROM with Android 12 if possible) and conserv the root access and my apps.
I have read that now ,we should have 3 files to do that (firmware,system and vendor) to make a wipe and install new ROM with TWRP.
So my question:
-Is it possible to upgrade Android 8.1.0 to Android 12 witn a new ROM? (i have read something about kernel in Android12 but haven't understand all)
-Have i missed some steps or just download files,boot TWRP,wipe and install newer ROM+firmware and vendor appropriate is good?
-Which ROM do you recommend?
Thanks for the previous answers.
devil1 said:
Hello all,
It's a long time that's i haven't post a thread here but i have a question.I have a Poco with MIUI Global 9.6 Stable (9.6.25.0) for ROM with a Android Version 8.1.0 OPM 171019.011 with root acces, unlocking bootloader and TWRP 3.3.0-0 installed.
I would upgrade my phone to something "newer" (A ROM with Android 12 if possible) and conserv the root access and my apps.
I have read that now ,we should have 3 files to do that (firmware,system and vendor) to make a wipe and install new ROM with TWRP.
So my question:
-Is it possible to upgrade Android 8.1.0 to Android 12 witn a new ROM? (i have read something about kernel in Android12 but haven't understand all)
-Have i missed some steps or just download files,boot TWRP,wipe and install newer ROM+firmware and vendor appropriate is good?
-Which ROM do you recommend?
Thanks for the previous answers.
Click to expand...
Click to collapse
It's not possible to switch from stock ROM to custom without doing clean install. You will have to root again.
First update to latest Official Stock ROM, then take backup of your files to your PC or to SDCard (if you have one) , flash to latest Official TWRP and check my POCO F1 Ultimate Collection & Guides. You can find everything there. I have awarded recommended ROMs in my collection.
Feel free to ask if you have any question regarding the guides.
Thanks for the answer.I have begin to read your guides.
If i understand good,it's not possible to conserv my root,unlock bootloader and twrp when i upgrade to android 12? Automaticaly i should root again my phone and restore with titanium backup my files,contact,....?
devil1 said:
Thanks for the answer.I have begin to read your guides.
If i understand good,it's not possible to conserv my root,unlock bootloader and twrp when i upgrade to android 12? Automaticaly i should root again my phone and restore with titanium backup my files,contact,....?
Click to expand...
Click to collapse
First you need to take backup of your files to PC or External SDCard.
Then you should update to latest version of MIUI via OTA if it's possible or via TWRP (you can use the stock recovery rom to do it via twrp). (You can also use my guides for clean install stock rom)
Then you should unlock your bootloader if it's not already unlocked.
Then flash latest Official TWRP.
Then flash latest firmware (not vendor) just to make sure you are on the latest. (You should be on latest firmware after updating to the latest MIUI version)
Then Wipe everything + format data according to my guides and flash the ROM you want. If you choose A12 Pixel Experience or crDroid keep in mind that these ROMs use their own recovery because these are encrypted by default ROMs and TWRP can't handle the decryption of A12 encrypted ROMs yet. So to make OTA updates and that stuff work correctly devs of these ROMs decide to use their own recovery which can handle the decryption of encrypted roms and as result to make OTA update work fine. Check the installation instructions of these roms in their threads. (Afterwards you can use adb sideload to flash stuff using these recoveries)
After that, flash Magisk since you want root.
Then you can restore titanium backup if you want.
OK i follow your instruction.Thanks
Hello retrial,
I have now updating my phone to MIUI Global 12.0.3 Stable with Android Version 10QKQ1.My phone is not yet rooted and now he is encrypted.The recovery is now Mi-Recovery 3.0
I have unlock again my bootloader.
Now to follow your instruction,i should flash the latest TWRP.
I have take TWRP-3.6.0_9-0-berylium in your guide.
I think i should do Fastboot Method because i'm now in Mi-Recovery?i'm right?
No problem with the encryption?
Thanks.
i have find this video.This is not the good phone but i think that the installation is the same:
devil1 said:
Hello retrial,
I have now updating my phone to MIUI Global 12.0.3 Stable with Android Version 10QKQ1.My phone is not yet rooted and now he is encrypted.The recovery is now Mi-Recovery 3.0
I have unlock again my bootloader.
Now to follow your instruction,i should flash the latest TWRP.
I have take TWRP-3.6.0_9-0-berylium in your guide.
I think i should do Fastboot Method because i'm now in Mi-Recovery?i'm right?
No problem with the encryption?
Thanks.
Click to expand...
Click to collapse
Yes use Fastboot Method to flash TWRP. No problem with encryption.
After that follow my clean install custom rom guide to flash the ROM you want. Also please check the instructions in the threads of ROMs you want to flash. A12 crDroid and PE use their own recoveries.
Basically tell me which ROM you want to flash to help you exactly with steps.
Hello retrial,
i have a problem to install TWRP-3.6.0-9-0 on my pocophone.Everything working fine but in step 8 of your guide,i can't find my twrp.img that i have copied in 2 different case to test :
8. Boot into Recovery by typing in cmd: fastboot boot <recovery_filename>.img (The file may not be named identically to what stands in this command, so adjust accordingly and write the full path of it, check the example below).
This command will not flash permantly the recovery, it will just temporary boot into it and afterwards you will flash permantly the twrp.img you copied into your Internal Storage or SDcard in recovery partition.
For example: fastboot boot C:\Users\Retrial\Desktop\twrp-3.5.2_9-0-beryllium.img
Have you an idea to why i cannot find my twrp.img in the boot mode?
devil1 said:
Hello retrial,
i have a problem to install TWRP-3.6.0-9-0 on my pocophone.Everything working fine but in step 8 of your guide,i can't find my twrp.img that i have copied in 2 different case to test :
8. Boot into Recovery by typing in cmd: fastboot boot <recovery_filename>.img (The file may not be named identically to what stands in this command, so adjust accordingly and write the full path of it, check the example below).
This command will not flash permantly the recovery, it will just temporary boot into it and afterwards you will flash permantly the twrp.img you copied into your Internal Storage or SDcard in recovery partition.
For example: fastboot boot C:\Users\Retrial\Desktop\twrp-3.5.2_9-0-beryllium.img
Have you an idea to why i cannot find my twrp.img in the boot mode?
Click to expand...
Click to collapse
Send a screenshot what you type in cmd and where you have the twrp.img
Or you mean you can't find it in your device while you are booted on TWRP?
i cannot find the twrp.img in my device.The step 8 of your tutorial.
I have copied the files but cannot find it in the cases.I have take TWRP-3.6.0-9-0
The link of the files: https://eu.dl.twrp.me/beryllium/twrp-3.6.0_9-0-beryllium.img.html
devil1 said:
i cannot find the twrp.img in my device.The step 8 of your tutorial.
I have copied the files but cannot find it in the cases.I have take TWRP-3.6.0-9-0
The link of the files: https://eu.dl.twrp.me/beryllium/twrp-3.6.0_9-0-beryllium.img.html
Click to expand...
Click to collapse
Are you sure you select Install Image?
ok i have download an other twrp.img and this time it's ok.i can go to the end of the tutorial but when i reboot my device mi-recovery 3.0 come back.I have tried 2 times but all the time mi-recovery3.0 come back
Have you an idea?
Should i take a additional command like in the video i have send you in the thread "fastboot flash recovery"?
devil1 said:
ok i have download an other twrp.img and this time it's ok.i can go to the end of the tutorial but when i reboot my device mi-recovery 3.0 come back.I have tried 2 times but all the time mi-recovery3.0 come back
Have you an idea?
Should i take a additional command like in the video i have send you in the thread "fastboot flash recovery"?
View attachment 5549731
Click to expand...
Click to collapse
I have all the steps on my guide. Please read it carefully. It boots back to mi recovery because you haven't flash TWRP yet just booted into. After boot into TWRP u need to flash twrp in recovery section so it will stay after reboot.
Please read the steps.
Download portable Minimal ADB and Fastboot and latest Official TWRP recovery.
Open cmd from minimal adb and fastboot and write:
fastboot boot and the path you have TWRP.
Example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-3.6.0_9-0-beryllium.img
Then proceed with the rest steps in my guide. Connect ur device to pc while u are booted into TWRP and copy TWRP.img to your device. Then in TWRP press Install Image and select the twrp.img u just copied into ur device. Select recovery and done.
I have made a video to show you what happened (sorry for the bad quality and the moove) :
I think a video is easyest to understand my problem.For information my bootloader is unlock and usb debugging ok.
devil1 said:
I have made a video to show you what happened (sorry for the bad quality and the moove) :
I think a video is easyest to understand my problem.For information my bootloader is unlock and usb debugging ok.
Click to expand...
Click to collapse
Hmm strange, probably of MIUI. Anyway since you are going to flash custom rom, when u flash twrp in recovery go back and select wipe and wipe everything (read my clean install guide), go back press format data type yes, and then reboot to TWRP.
EDIT: I just saw u rebooted to system. That's not what we want. Press reboot to recovery.
i reboot first to bootloader after have flash the twrp.img in recovery.That's only the second time that i reboot to system to use the normal mode of the phone and reboot after to recovery mode to show you that mi recovery is back.
devil1 said:
i reboot first to bootloader after have flash the twrp.img in recovery.That's only the second time that i reboot to system to use the normal mode of the phone and reboot after to recovery mode to show you that mi recovery is back.
Click to expand...
Click to collapse
The TWRP flashed correctly. You overlap it again by pressing reboot to recovery from MIUI updater.
Don't do that...do the combination to boot to TWRP after flashing it. Power+Volume Up.
And continue with clean install steps in my guide to flash custom rom.
In my guide I write nowhere to boot to MIUI and press from MIUI Updater reboot to recovery, please stick to my guide and you will be fine.
Poco f1 update not
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?