Database Info

Install custom recovery and root on Cubot J5?

I have tried for a few days to install a custom recovery but no luck. Perhaps someone can give me some advice?
I have tried Mediatek (MTK) Auto TWRP recovery porter, version 1.5 but it didn´t work.
This aswell twrp-recovery-cubot-j5-root from getdroidtips but nope...
Chip on phone Mtk6580 and android 9.
Updated to the latest firmware release via spflashtool from cubot own site.
I guess that im to much of a newbie to get this done...
But atleast its updated, my main goal is to root the phone so thats why i need a custom recovery.
Thx in advance, and sorry for my english grammar, not my main language. :laugh:

jimboo80 said:
I have tried for a few days to install a custom recovery but no luck. Perhaps someone can give me some advice?
I have tried Mediatek (MTK) Auto TWRP recovery porter, version 1.5 but it didn´t work.
This aswell twrp-recovery-cubot-j5-root from getdroidtips but nope...
Chip on phone Mtk6580 and android 9.
Updated to the latest firmware release via spflashtool from cubot own site.
I guess that im to much of a newbie to get this done...
But atleast its updated, my main goal is to root the phone so thats why i need a custom recovery.
Thx in advance, and sorry for my english grammar, not my main language. :laugh:
Click to expand...
Click to collapse
My dear friend did you try:
https://www.cyanogenmods.org/how-to-root-cubot-j5-and-install-twrp-recovery/
btw why didn't Mediatek Auto TWRP recovery porter work? what was the issue?

I have the same problem the thread starter indicates in the title: I can install the TWRP recovery image that gopikrishnanrmg linked, but the installation of Magisk doesn't work. It says it installs successfully, but I can't get root rights and if I install the Magisk app, it says that Magisk is not installed. Magisk canary doesn't work either. Does someone have an idea what I might have done wrong? Or does that mean that the device is not supported by Magisk?

gopikrishnanrmg said:
My dear friend did you try:
btw why didn't Mediatek Auto TWRP recovery porter work? what was the issue?
Click to expand...
Click to collapse
Sorry for the late answer, life happens
I get it installed with that guide after unlocking flash state, but when it reboots it give me a message "orange state" and the phone resets.
and the recovery porter did not work for me, maybe i´m to old for this hehe was a while since i rooted a device, and i´m defenitly no hacker
btw if you need to look on the firmware cubot(dot)net has a downloadable link for the j5.

I have the same problem and I can't do anything about it, maybe some specific source or a hint in the form of YT

Has anyone figured out how to upload Twrp recovery to Cubot J5 ????

I was able to root Cubot J5.
CUBOT_J5_9061C_V14_20200506
Magisk 23.0(23000)
Cubot J5 is "Ramdisk No".
Must be booted in recovery mode.
Magisk in Recovery
Installation
The Magic Mask for Android
topjohnwu.github.io
Steps
1. Patch your boot.img and recovery.img with magisk
Img file can be downloaded
CUBOT FILE DOWNLOAD
Cubot Offical Website for Smartphones and Wearables. Simple and Trust, Cubot aims to be a credit worthy high-tech corporation in the world.
www.cubot.net
2.Edit the boot.img file with a hex editor.
Change 「736B69705F696E697472616D6673」 to 「77616E745F696E697472616D6673」
3.flashing the boot.img recovery.img and vbmeta.img .
vbmeta.img file can be downloaded
331 Cubot J5
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
fastboot flash boot magisk_patched-23000_boot_binay_edit.img
fastboot flash boot magisk_patched-23000_boot.img
fastboot flash recovery magisk_patched-23000_recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4.Must be booted in recovery mode to enter root state.
adb reboot recovery
or
Press and hold the Power key and the Volume UP key when booting.

たろう said:
I was able to root Cubot J5.
CUBOT_J5_9061C_V14_20200506
Magisk 23.0(23000)
Cubot J5 is "Ramdisk No".
Must be booted in recovery mode.
Magisk in Recovery
Installation
The Magic Mask for Android
topjohnwu.github.io
Steps
1. Patch your boot.img and recovery.img with magisk
Img file can be downloaded
CUBOT FILE DOWNLOAD
Cubot Offical Website for Smartphones and Wearables. Simple and Trust, Cubot aims to be a credit worthy high-tech corporation in the world.
www.cubot.net
2.Edit the boot.img file with a hex editor.
Change 「736B69705F696E697472616D6673」 to 「77616E745F696E697472616D6673」
3.flashing the boot.img recovery.img and vbmeta.img .
vbmeta.img file can be downloaded
331 Cubot J5
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
fastboot flash boot magisk_patched-23000_boot_binay_edit.img
fastboot flash recovery magisk_patched-23000_recovery.im
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4.Must be booted in recovery mode to enter root state.
adb reboot recovery
or
Press and hold the Power key and the Volume UP key when booting.
Click to expand...
Click to collapse
I tried flashing your files but unfortunately got a bootloop again . I was on the same stock software, unlocked bootloader and tried to flash as you described.

weeman45 said:
I tried flashing your files but unfortunately got a bootloop again . I was on the same stock software, unlocked bootloader and tried to flash as you described.
Click to expand...
Click to collapse
Cause of bootloop.
1. vbmeta.img is not flushed.
2. The firmware version is different.
The version of this file is "CUBOT_J5_9061C_V14_20200506".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

たろう said:
Cause of bootloop.
1. vbmeta.img is not flushed.
2. The firmware version is different.
The version of this file is "CUBOT_J5_9061C_V14_20200506".
Click to expand...
Click to collapse
Thanks for your reply! When i woke up today i thought i can just as well restore the stock rom but found the phone booting.
The boot was just taking way longer because of the factory reset (through oem unlock).
I just installed the root checker and it is working fine!
After years of having this phone and trying to root it you just saved it. Thank you!
Do you have plans to install GSI images on it as well?
*update* i'm able to boot a lineageos 18.1 GSI with your images. I flashed the system and afterwards your boot, recovery and vbmeta and it worked.
*update2* I wanted gApps so i tried the lineageos 19.1 image which was too big. After that i tried an AOSP one with lite gApps.
I think i messed up badly. I can't get back into fastboot and not even the spflash tool is able to flash something. When pressing Volume down+power it briefly detects it but won't write the firmware. I'll try different versions later and report back but for now it's dead
*uodate3* It's back again. I had to re-install the mediatek drivers for the tool to work. After a stock boot i was able to unlock the bootloader and install LOS again. I will go for an image with gapps next.
Thank you again for providing your images and support!

weeman45 said:
Thanks for your reply! When i woke up today i thought i can just as well restore the stock rom but found the phone booting.
The boot was just taking way longer because of the factory reset (through oem unlock).
I just installed the root checker and it is working fine!
After years of having this phone and trying to root it you just saved it. Thank you!
Do you have plans to install GSI images on it as well?
*update* i'm able to boot a lineageos 18.1 GSI with your images. I flashed the system and afterwards your boot, recovery and vbmeta and it worked.
*update2* I wanted gApps so i tried the lineageos 19.1 image which was too big. After that i tried an AOSP one with lite gApps.
I think i messed up badly. I can't get back into fastboot and not even the spflash tool is able to flash something. When pressing Volume down+power it briefly detects it but won't write the firmware. I'll try different versions later and report back but for now it's dead
*uodate3* It's back again. I had to re-install the mediatek drivers for the tool to work. After a stock boot i was able to unlock the bootloader and install LOS again. I will go for an image with gapps next.
Thank you again for providing your images and support!
Click to expand...
Click to collapse
I'm so glad to hear that.
I have no plans to install GSI images.

たろう said:
I'm so glad to hear that.
I have no plans to install GSI images.
Click to expand...
Click to collapse
You really helped a lot. I'm always glad to tinker with spare phones.
For anyone else stumbling upon this thread trying to install a GSI image: Here is how i succeeded.
1. Enable unlocking in your developer settings
2. Use "fastboot flashing unlock" to enable flashing (this performs a factory reset)
3. wipe your system partition with "fastboot erase system"
4. Flash your GSI image wizh "fastboot flash system 'path-to-your-GSI' "
5. flash the provided vbmeta with "fastboot --disable-verity --disable-verification flash vbmeta 'path-to-vbmeta.img' "
I had success with lineageos 18 A/B with gapps. Make sure that it's not too big in size or else you will get an error message stating it is too big.
If you have troubles getting into recovery/fastboot, use the SPflashtool to revover your stock firmware (be sure to NOT format all because you will lose your IMEI information in that process!) and try again

Hi,
i tried to root my Cubot J5 by doing the following:
flash system system.img (from CUBOT_J5_9061C_V14_20200506 .zip)
fastboot flash boot magisk_patched-23000_boot.img
fastboot flash recovery magisk_patched-23000_recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot in recovery mode
When check for root with root checker basic, systems says, that magisk is crashed several times. And after this root checker states that no root is granted.
Any idea?

pat2858 said:
Hi,
i tried to root my Cubot J5 by doing the following:
flash system system.img (from CUBOT_J5_9061C_V14_20200506 .zip)
fastboot flash boot magisk_patched-23000_boot.img
fastboot flash recovery magisk_patched-23000_recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot in recovery mode
When check for root with root checker basic, systems says, that magisk is crashed several times. And after this root checker states that no root is granted.
Any idea?
Click to expand...
Click to collapse
I have no idea.
if possible to initialize with flash tool and then try again.

Tried it, but no luck.
Don't know why magisk is crashing all the time.

pat2858 said:
Tried it, but no luck.
Don't know why magisk is crashing all the time.
Click to expand...
Click to collapse
Is the Magisk version 23?
I have not confirmed the latest version(24~)

[Guide] Unlocking Bootloader and Disabling VerifiedBoot

Code:
/* Your warranty is now void (or isn't ? who am I to judge ?) */
Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro.
Thanks to @barakcodam for leaking it, and @Rizezky for providing a Google Drive mirror of it.
Disclaimer
This tutorial requires adb and fastboot installed on your computer. So, you should prepare it first. How to install them ? google it according to your os (Windows/Linux/BSD/Mac).
Unlocking bootloader will wipe your data, backup it first.
Due to Android 10 Dynamic Partition, there's no fully-working TWRP available yet. So the only way to root your phone is patching boot.img through Magisk Manager. You can grab boot.img from Flashable Stock ROM .ozip
Unlocking Bootloader
download the deeptesting.apk for Realme 6 Pro : https://drive.google.com/file/d/16az-7SHoPyJhDIi4p4x7wj1cRUcsPwCM/view
open it and apply for in-depth test
Go to Developer options, enable OEM unlock and USB debugging
open In-depth test again and tap "Query verification status" on the top corner
tap "Start the in-depth test", and you'll will reboot to bootloader
on your computer, open cmd/terminal, and type :
Code:
fastboot flashing unlock
on your phone, select "yes". now your phone will reboot and data is being wiped, and you have unlocked bootloader.
Disabling Verified Boot
In order to boot a custom boot-partition (for magisk or custom kernel purposes) or custom recovery, you have to disable verified boot, otherwise you can't boot to the OS.
download vbmeta.img in the attachment
on your computer, open cmd/terminal, and type :
Code:
adb reboot bootloader
after entering fastboot, type :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Now you can flash your custom boot.img and it'll boot just fine.

nullxception said:
Code:
/* Your warranty is now void (or isn't ? who am I to judge ?) */
Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro.
Thanks to @barakcodam for leaking it, and @Rizezky for providing a Google Drive mirror of it.
Disclaimer
This tutorial requires adb and fastboot installed on your computer. So, you should prepare it first.
How to install them ? google it according to your os (Windows/Linux/BSD/Mac).
Unlocking bootloader will wipe your data, backup it first.
Unlocking Bootloader
download the deeptesting.apk for Realme 6 Pro : https://drive.google.com/file/d/16az-7SHoPyJhDIi4p4x7wj1cRUcsPwCM/view
open it and apply for in-depth test
Go to Developer options, enable OEM unlock and USB debugging
open In-depth test again and tap "Query verification status" on the top corner
tap "Start the in-depth test", and you'll will reboot to bootloader
on your computer, open cmd/terminal, and type :
Code:
fastboot flashing unlock
on your phone, select "yes". now your phone will reboot and data is being wiped, and you have unlocked bootloader.
Disabling Verified Boot
In order to boot a custom boot-partition (for magisk or custom kernel purposes) or custom recovery, you have to disable verified boot, otherwise you can't boot to the OS.
download vbmeta.img in the attachment
on your computer, open cmd/terminal, and type :
Code:
adb reboot bootloader
after entering fastboot, type :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Now you can flash your custom boot.img and it'll boot just fine.
Click to expand...
Click to collapse
Ah thank you...
Already tried with flashing disable DM verity but it failed and make me need to flash original boot.img file.
How can I so stupid not to flash vbmeta.img?
And yes, with this method I can confirm root with Magisk run smoothly.
:good::good::good:

What is your widevine level after that?

Maciejbbb said:
What is your widevine level after that?
Click to expand...
Click to collapse
L3 of course

nullxception said:
L3 of course
Click to expand...
Click to collapse
Is it reversible or can you hide it with magisk module like on some phones?

Maciejbbb said:
Is it reversible or can you hide it with magisk module like on some phones?
Click to expand...
Click to collapse
Reversible ? I don't know, can't confirm that.
Also there's still no patched widevine module that works for realme6pro.

Stock boot image is around 65 mb in size. But patched_boot.img with magisk is only 13.2 mb in size. So will it cause any damage when flashing patched boot image?

Muhammed159753 said:
Stock boot image is around 65 mb in size. But patched_boot.img with magisk is only 13.2 mb in size. So will it cause any damage when flashing patched boot image?
Click to expand...
Click to collapse
No, that 65mb is size of the whole partition block, not the actual size of the whole files inside of it.
If you try to manually unpack the boot.img, and then repack it, the size will go down to around that.

@AT nullexception Thanks for your reply. So Can I flash magisk patched boot image after flashing vbmeta.img? Will my phone get bootloop?

Stuck in Bootloader,
Does anyone has patched boot.img, as i unlocked the Bootloader then disabled the verification , flashed vbmeta.img, Installed TWRP and from TWRP flashed magisk.zip but now phone only boots to bootloader.
Do i need to flash back to stock or there is any other solution so i can get Root ?

Unable to find Patched Boot Img also No where to be found stock Firmware in "MBN" format as MSMdownloadtool is asking for Id and password.

SignatureBoy said:
Unable to find Patched Boot Img also No where to be found stock Firmware in "MBN" format as MSMdownloadtool is asking for Id and password.
Click to expand...
Click to collapse
Here my boot image files magisk_patched

SignatureBoy said:
Stuck in Bootloader,
Does anyone has patched boot.img, as i unlocked the Bootloader then disabled the verification , flashed vbmeta.img, Installed TWRP and from TWRP flashed magisk.zip but now phone only boots to bootloader.
Do i need to flash back to stock or there is any other solution so i can get Root ?
Click to expand...
Click to collapse
/////////////////////////////
Which version of magisk.zip did you flash?

Muhammed159753 said:
/////////////////////////////
Which version of magisk.zip did you flash?
Click to expand...
Click to collapse
20.1
---------- Post added at 08:51 PM ---------- Previous post was at 08:49 PM ----------
Felix Siahaan said:
Here my boot image files magisk_patched
Click to expand...
Click to collapse
Thank you so much but i am afraid to flash it again as it was really hard to revive it back i had to send it to Service center, and pretended that the newest update has done all issues.
They were not agreeing to flash as bootloader was unlocked then after so many request they agreed and said do not update the fone to lastest update.
Boot loader is unlocked so tell me how can i do the root session STEP BY STEP please
and also if you have the MBN version of the stock rom then give me the link as MSMDOWNLOADTOOL does not work without Paid ID and Password.

nullxception said:
Code:
/* Your warranty is now void (or isn't ? who am I to judge ?) */
Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro.
Thanks to @barakcodam for leaking it, and @Rizezky for providing a Google Drive mirror of it.
Disclaimer
This tutorial requires adb and fastboot installed on your computer. So, you should prepare it first. How to install them ? google it according to your os (Windows/Linux/BSD/Mac).
Unlocking bootloader will wipe your data, backup it first.
Due to Android 10 Dynamic Partition, there's no fully-working TWRP available yet. So the only way to root your phone is patching boot.img through Magisk Manager. You can grab boot.img from Flashable Stock ROM .ozip
Unlocking Bootloader
download the deeptesting.apk for Realme 6 Pro : https://drive.google.com/file/d/16az-7SHoPyJhDIi4p4x7wj1cRUcsPwCM/view
open it and apply for in-depth test
Go to Developer options, enable OEM unlock and USB debugging
open In-depth test again and tap "Query verification status" on the top corner
tap "Start the in-depth test", and you'll will reboot to bootloader
on your computer, open cmd/terminal, and type :
Code:
fastboot flashing unlock
on your phone, select "yes". now your phone will reboot and data is being wiped, and you have unlocked bootloader.
Disabling Verified Boot
In order to boot a custom boot-partition (for magisk or custom kernel purposes) or custom recovery, you have to disable verified boot, otherwise you can't boot to the OS.
download vbmeta.img in the attachment
on your computer, open cmd/terminal, and type :
Code:
adb reboot bootloader
after entering fastboot, type :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Now you can flash your custom boot.img and it'll boot just fine.
Click to expand...
Click to collapse
will u help me in unlocking the bootloader for vivo iqoo3 i have tried everything for unlocking the bootloader but i have not got any success with that
kindly give the reply as early as possible

kkrraazzyy said:
will u help me in unlocking the bootloader for vivo iqoo3 i have tried everything for unlocking the bootloader but i have not got any success with that
kindly give the reply as early as possible
Click to expand...
Click to collapse
1. Don't quote the whole post
2. With such brands like vivo, you have no choice but stay locked forever

To deactivate verify boot every time patched vbmeta need to flash. Is it ok to flash same vbmets v2 for all future updates
Thans

nullxception said:
1. Don't quote the whole post
2. With such brands like vivo, you have no choice but stay locked forever
Click to expand...
Click to collapse
Is it ok to flash same vbmets v2 for all future updates

Not working on A25

Will this work on all versions of the realme 6 pro?
I've got the rmx2063 version and I want to root it with magisk' will I be able to do it after doing this?
Many thanks

Unbrick your Realme C12

What is a brick?​If there is no usual way to recover your mobile, then it is called brick in my opinion. That means if you can't able to go to recovery and fastboot mode or the device is just blank with no sign of life.
When brick happens?​It will happen because of locking bootloader with custom images or just because of Mediatek/Realme strange behaviour.
What we have to do if brick happens?​Simply we have to flash stock firmware with Smart Phone Flash Tool(aka SPFlash Tool). With only SPFlash Tool we can't do anything, since we don't have permission for it. But with the advent of MTK-bypass, we can have full control over our device. If we don't have this MTK-bypass, then we have search for costly alternative's.
You can't flash only if your eMMC is damaged, which is the worst case because oppo phones are prone to eMMC failure.
Click to expand...
Click to collapse
Where to get firmware to flash?​Download decrypted .ofp firmware from https://drive.google.com/file/d/1SOmRxix9_UtjOLLanXPYxf4YK1NrA_RW/view
Thanks to @bx2_nero for it.
What is the procedure for using MTK-bypass and SPFlashTool?​MTK-bypass is a Python script and it needs different USB ways for working. So with these two in place, we can get our work done.
Linux Users​For Linux we have to use FireISO or patched kernels for working of MTK-bypass.
Use the Linux guide by @bx2_nero at https://forum.xda-developers.com/t/...our-realme-6-6i-india-6s-linux-method.4251077
Windows Users​For Windows we have to use libusb32 filter for MTK-bypass working.
Use the guide by @daeSundae at https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/
MTK-bypass Official instructions​See Github ReadMe at https://github.com/MTK-bypass/bypass_utility and XDA support thread at https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377/
Credits​xyzz / xyz`: GitHub | XDA
chaosmaster / k4y0z: GitHub | XDA
Dinolek: GitHub | XDA
References​- https://forum.hovatek.com/thread-37957.html
- https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/
- https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/
- https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
- https://forum.xda-developers.com/t/...ash-tool-authentication.4236881/post-84627359

MTKClient
After MTK-bypass got success, @viperbjk who is a reverse engineer came up with a FOSS replacement of SP Flash Tool.
MTKClient combines MTK-bypass and SP Flash Tool together and with many improvements and new features.
Ability to flash partitions without Scatter file
Ability to Readback partitions without specifying address and length
Ability to Format partitions without specifying address and length
Run multiple commands without reconnecting the device
Flash protected partitions(opporeserve2, special_preload, my_custom and cdt_engineering) with locked bootloader
Unlock bootloader without need of in-depth test/Deep testing app from Realme
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
www.github.com

Reserved

I need help, my C12 is stuck on fastboot mode. This happened after flashing a GSI using TWRP and flashing the image in the Super (System and Vendor) partition.
I tried rebooting to recovery mode by executing fastboot reboot recovery but it says that bootloader is not known.
I also tried to flash a GSI (taught it might fix the problem) using fastboot flash system system.img but it says that no partition named system exists.
Please suggest what I should do.

Bro, can you make a video about this? my realme c12 got hardbricked after I flashed ozip file from stock recovery while bootloader is unlocked. it got hardbricked when I reboot it after flashing ozip

DFM23 said:
Bro, can you make a video about this? my realme c12 got hardbricked after I flashed ozip file from stock recovery while bootloader is unlocked. it got hardbricked when I reboot it after flashing ozip
Click to expand...
Click to collapse
What is the present state of the device? Can you able to boot to fastboot mode?

HemanthJabalpuri said:
What is the present state of the device? Can you able to boot to fastboot mode?
Click to expand...
Click to collapse
it has no sign of life, cant go to recovery or fastboot. when I connect it to pc it goes connect and disconnected.

How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.

youcancallmekhen said:
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
Click to expand...
Click to collapse
Use latest platform tools

youcancallmekhen said:
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
Click to expand...
Click to collapse
HemanthJabalpuri said:
Use latest platform tools
Click to expand...
Click to collapse
Sir I've finally able to reboot to recovery. I've tried flashing the OZIP file for my model but after some time it says Installation failed. When I was still using custom recovery, I wasn't able to mount System and Vendor. My bootloader is also unlocked sir.
Should I lock my bootloader sir?

youcancallmekhen said:
Should I lock my bootloader sir?
Click to expand...
Click to collapse
Don't lock bootloader.
Download this https://drive.google.com/file/d/1jLdDz7M0G_KPDn4jXjTeuFnO1C-MFaBs/view (It is from A.87 UI 1.0 Stock ROM)
Extract above 7z file and flash ONLY super partition from it and TWRP from https://androidfilehost.com/?fid=7161016148664807816 with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery TWRP.img
fastboot reboot recovery
Now enable 'Skip Treble Compatibility error' in TWRP settings and flash stock ROM .ozip in TWRP.
Thanks

HemanthJabalpuri said:
Don't lock bootloader.
Download this https://sourceforge.net/projects/realmec11/files/Fastboot-ROM/[email protected]/download
Extract above 7z file and flash ONLY super partition from it with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery stock-recovery.img
fastboot reboot recovery
Now flash stock ROM .ozip in stock recovery.
Thanks
Click to expand...
Click to collapse
Oh my, thank you so much sir. You have no idea how much you are helping me sir! My parents will be so happy, and we won't waste money… Thank you so much sir…
I'll update you sir after doing these, thank you sir! ♥

HemanthJabalpuri said:
Don't lock bootloader.
Download this https://sourceforge.net/projects/realmec11/files/Fastboot-ROM/[email protected]/download
Extract above 7z file and flash ONLY super partition from it with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery stock-recovery.img
fastboot reboot recovery
Now flash stock ROM .ozip in stock recovery.
Thanks
Click to expand...
Click to collapse
I don't have much data left today sir, so I will download this later. Thank you very much again sir, you're my hero!

DFM23 said:
it has no sign of life, cant go to recovery or fastboot. when I connect it to pc it goes connect and disconnected.
Click to expand...
Click to collapse
Follow the guide and you can get your mobile back to life.
Thanks

HemanthJabalpuri said:
Follow the guide and you can get your mobile back to life.
Thanks
Click to expand...
Click to collapse
thank you bro, Ill follow your guide then. btw does the RMX2185 firmware you provided works with realme c12? I look it up and saw that it was for realme c11

DFM23 said:
thank you bro, Ill follow your guide then. btw does the RMX2185 firmware you provided works with realme c12? I look it up and saw that it was for realme c11
Click to expand...
Click to collapse
Yes, both use same firmware.

I tried the guide but when I click download on sp flash tool it would stay in red bar for 1 min or more then message will appear saying STATUS_EXT_RAM_EXCEPTION. I have read a same comment here in xda about realme c12 I dont know if its only on realme c12.

Thanks for your works sir, you are super awesome!

I rooted My Device (Realme X2 Pro) by Magisk. And Since My Device Bootloader was unlocked I Unrooted/Uninstalled MAgisk.
While Locking Bootloader My Device is Stuck where It displays { The Current Image (boot/recovery) have been destroyed dand cannot boot. Please flash the correct Image or Contact Customer Service to fix it }
While Trying to ENter the Fast Boot Mode {By pressing Volume + - and Power Button} Its Unresponsive
It shows Realme Logo And chrging Display for a Instant
Do you Know any way around to fix my Problem?

Bhuprab said:
I rooted My Device (Realme X2 Pro) by Magisk. And Since My Device Bootloader was unlocked I Unrooted/Uninstalled MAgisk.
While Locking Bootloader My Device is Stuck where It displays { The Current Image (boot/recovery) have been destroyed dand cannot boot. Please flash the correct Image or Contact Customer Service to fix it }
While Trying to ENter the Fast Boot Mode {By pressing Volume + - and Power Button} Its Unresponsive
It shows Realme Logo And chrging Display for a Instant
Do you Know any way around to fix my Problem?
Click to expand...
Click to collapse
Since your device is Qualcomm, I don't know. In any device, we have to flash stock rom (or atleast the partitions that are modified) to get device in working state.
You may get better help at https://forum.xda-developers.com/f/realme-x2-pro-questions-answers.9439/
Thanks

[SOLVED] Doogee S88 Plus reboot loop with magisk root

after patching boot.img with Magisk and flashing over the patched boot.img, the phone (Doogee S88 Plus) will just infinitely reboot after the message `Your device has been unlocked and can't be trusted`
luckily, patching the original boot.img back fixes it (albeit flashing it back is kindof tricky, have to reboot multiple times while holding down the volume-down button before i can re-flash)
so it's not bricked, but i haven't been able to root it either, any suggestions?
fwiw, i'm using this firmware: https://drive.google.com/drive/folders/13bxhk-eEsJ81FmJWZaEEsOkZBMsYJE3x

update: finally managed to root it, the final piece of the puzzle was that S88 Plus wanted the magisk-patched boot.img signed with the publicly-available-private-key from https://forum.hovatek.com/thread-35862.html
screenshot:
https://imgur.com/EbjK0qX

the magisk-patched + signed boot.img if anyone is interested:

where boot.img ?

and you chose which twrp ?

avalondrey said:
where boot.img ?
Click to expand...
Click to collapse
avalondrey said:
and you chose which twrp ?
Click to expand...
Click to collapse
i did not use twrp at all, i only used magisk, and the boot.img is the file i uploaded above with the name "magisk_patched-23000_TY62U.img" , just rename it to "boot.img"

does your phone has a vbmeta.img?
It control if the image is signed, if you don't flash an empy vbmeta.img the system will bootloop.
It was a problem when rooting the Ulefone Armor 8-11

root is ok , flash tool, install boot and reboot

Harlock1978 said:
does your phone has a vbmeta.img?
It control if the image is signed, if you don't flash an empy vbmeta.img the system will bootloop.
It was a problem when rooting the Ulefone Armor 8-11
Click to expand...
Click to collapse
interesting, yes the phone has a vbmeta.img, and no i did not patch the vbmeta.img, and i did experience the reboot-loop, but signing the patched boot.img fixed the reboot loop without touching the vbmeta.img

This did it..dont flash vbmeta...the Boot ist the only Thing you Need...flashing vbmeta will end in bootloop...maybe a signed vbmeta...but why trying when Boot is enough...

after hours of trying I finally got it working.
Because I tried so much stuff I'm not exactly sure what was the key.
The signed boot.img flashed with sp flash tool alone did not work - i did not have the device unlocked with fastboot at that moment.
Then I tried a lot of different stuff.
I _think_ what was needed is these two things:
- signed boot.img from @hans henrik
- unlocking bootloader with fastboot (fastboot flashing unlock && fastboot flashing unlock_critical)

How did you unlocked it? And are you running gsi rom?
I have the s88 pro and i like to install custom rom

the doogee s88 plus should support galileo GPS standard Pu on mine it does not show any gaileo satelites. could anybody check?

Hi please help me i have doogee S88 plus and i use this guild https://unofficialtwrp.com/twrp-3-4-0-root-doogee-s88-plus/
now me phone keeps restarting, show "orange state", logo launches, I tried different combinations of buttons but nothing helped
what can i do or is there any way i can get it back to normal?
only now found this thread, currently the phone has a bootloop after these three commands
fastboot erase userdata
fastboot flash vbmeta vbmeta.img
fastboot flash recovery recovery.img

OK, i use sp flash tool but when i turn on me phone i see a bars on screen
i tried with all the stock roms i found, everywhere the same, the phone seems to work but instead of images there are stripes
this rom worked
OneDrive
onedrive.live.com

I finally managed to root my phone after days of endless boot loops (fixed by flashing stock using SP flash tool). Turns out I didn't need to flash an empty vbmeta or install TWRP at all. I was able to root it by following this guide https://www.hovatek.com/forum/thread-35862.html. For some reason your patched magisk image didn't work on my S88 Plus, so I made my own using the stock boot image from the official Doogee website (which appears to be the same one used in your patched version?) and Magisk 25.2 apk. For the Hovatek guide, I used python2 since python and python3 did not work. I currently have a red "Not Verify" watermark and an NVRAM WARNING: Err = 0x10 wifi network error, but should be able to resolve those with root access from guides I read earlier.
I would also like to install a GSI (lineageos preferably) but have had no success since nothing seems to officially support the S88 Plus even though it is project treble compatible, and I have ran into boot loops so far.
I have attached my working magisk_patched.img but would recommend building it from scratch using the linked guide to avoid any issues.

[GUIDE] Gigaset GS5 (rephone) root with Magisk + unlock bootloader

hello I'm not sure if this is the right place to post this in but I'll be putting together a small guide on how to root the Gigaset GS5​the phone I own is called "rephone" it's apparently a sustainable version of the Gigaset GS5 with a removable battery recycled plastic etc etc. But specs wise it is the same as the Gigaset GS5
anyways I did this yesterday so it's possible that I forgot some steps, if you encounter issues feel free to leave a comment and I'll try to assist you
prerequisites:​- make sure you actually have this device
- make sure you are on Android 12 (ota update)
- make sure you back up your data
- make sure you read this guide carefully
UNLOCKING BOOTLOADER WILL WIPE ALL YOUR DATA!!! MAKE SURE TO BACK EVERYTHING UP​Proceed with caution, I am not responsible for anything that may happen to your phone, you are doing it at your own risk
Easy method (flashing pre-made boot.img) :​I would not recommend this method because I extracted the kernel from my rephone and I don't know if the firmware/kernel for that is 1:1 with the GS5, ideally you want to extract the boot.img of your own device but that takes way more time so only proceed with this if you're at a pinch or are too lazy to extract your own boot.img
Also please download CPU-Z on your device and check your Build ID under the System tab, if it matches with mine then feel to proceed with this method, if not then do not proceed and instead extract your own boot.img and patch that
Build ID for my rephone is: 2000_000170_00_12.0_V06_20221025
Set up adb&fastboot on your computer (google 15 second adb installer)
Grab the patched boot.img from my GitHub and copy it to C:/adb or wherever you installed adb&fastboot: https://github.com/astolfoaddict/GigasetGS5-Magisk
Unlock developer options in your phone and enable OEM Unlocking
Power off your device and hold volume up+power until you boot into bootloader
Select and boot into Fastboot Mode, connect device to your computer
At this point you're in fastboot, open CMD in C:/adb
Your bootloader is probably locked, to check run this command: fastboot getvar unlocked if the result is no, your bootloader is locked
To unlock your bootloader run this command and follow the instructions on your device: fastboot flashing unlock (THIS WILL WIPE YOUR DATA)
Once you unlock your bootloader, wipe your vbmeta partition. Follow Method 3 in this guide: https://www.hovatek.com/forum/thread-32719.html
Now flash the boot.img: fastboot flash boot boot.img
Reboot, set up the device, install Magisk Manager and enjoy!
Advanced method (extracting and patching your own boot.img) :​In this method we'll be extracting the boot partition from your device so you can patch it with Magisk and flash
Proceed with caution!
Install Mediatek VCOM drivers, follow this guide: https://www.hovatek.com/forum/thread-440.html
Dump your boot_a partition with MTK Client by running python mtk r boot_a boot.img follow this guide: https://www.hovatek.com/forum/thread-40865.html
Install Magisk Manager and patch your boot.img
Unlock bootloader, flash empty vbmeta and boot by following the method above
Important:
- Make sure you run python mtk r boot_a boot.img in MTK Client
- If you don't see Mediatek VCOM drivers in Device Manager after using the auto installer, try installing the drivers manually (check guide)
- Also booting into BROM mode is tricky, what usually works for me is:
Power off device and connect to PC
As it starts up and shows you the battery charge, wait until the screen goes out
At this point you should run the python command in MTK Client
Hold volume down+power and check the terminal
If you want to extract the entire firmware follow this guide: https://www.hovatek.com/forum/thread-21970.html
Be aware that your chipset will not be listed in WwR MTK so what you do is open Template.ini with Notepad++ and add MT6768 under the CPU section, don't worry about the chipset not matching what this phone has (MT6769), adding MT6769 to CPU and exporting scatter file will not let you import it in SP flash tool
Special thanks to axonasif and supremegamers for the guide I pulled most of the stuff out of: https://github.com/supremegamers/mt6769​Also thanks to hovatek for their helpful resources regarding MTK flashing/drivers/etc. <3​

Hy
Ubuntu Touch with Waydroid works fine with Gigaset GS5......only Unlock Bootloader and flash with UB Port Installer..........
and you can flash Sailfish Port per Fastboot .............

yeah you can install GSIs too like lineage os and other stuff

astolfoaddict said:
yeah you can install GSIs too like lineage os and other stuff
Click to expand...
Click to collapse
Hy
have you some flashable files from lineage os...........??????? im searching found nothing............would be great
Thanks

astolfoaddict said:
yeah you can install GSIs too like lineage os and other stuff
Click to expand...
Click to collapse
its only a fake to install GSI image!!!!!! Dont work!!!!!!

hugolight said:
its only a fake to install GSI image!!!!!! Dont work!!!!!!
Click to expand...
Click to collapse
what do you mean?

astolfoaddict said:
what do you mean?
Click to expand...
Click to collapse
i have found no one GSI img file to flash my gigaset gs5!!!!!!

hugolight said:
i have found no one GSI img file to flash my gigaset gs5!!!!!!
Click to expand...
Click to collapse
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
try this one, boots and works just fine on my device.

astolfoaddict said:
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
try this one, boots and works just fine on my device.
Click to expand...
Click to collapse
Hello dont work
fastboot flash system lineage.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/16 (131060 KB) OKAY [ 4.278s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed

astolfoaddict said:
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
try this one, boots and works just fine on my device.
Click to expand...
Click to collapse
hy can you post the direct link for correct image (gigaset gs5)........thanks

astolfoaddict said:
hello I'm not sure if this is the right place to post this in but I'll be putting together a small guide on how to root the Gigaset GS5​the phone I own is called "rephone" it's apparently a sustainable version of the Gigaset GS5 with a removable battery recycled plastic etc etc. But specs wise it is the same as the Gigaset GS5
anyways I did this yesterday so it's possible that I forgot some steps, if you encounter issues feel free to leave a comment and I'll try to assist you
prerequisites:​- make sure you actually have this device
- make sure you are on Android 12 (ota update)
- make sure you back up your data
- make sure you read this guide carefully
UNLOCKING BOOTLOADER WILL WIPE ALL YOUR DATA!!! MAKE SURE TO BACK EVERYTHING UP​Proceed with caution, I am not responsible for anything that may happen to your phone, you are doing it at your own risk
Easy method (flashing pre-made boot.img) :​I would not recommend this method because I extracted the kernel from my rephone and I don't know if the firmware/kernel for that is 1:1 with the GS5, ideally you want to extract the boot.img of your own device but that takes way more time so only proceed with this if you're at a pinch or are too lazy to extract your own boot.img
Also please download CPU-Z on your device and check your Build ID under the System tab, if it matches with mine then feel to proceed with this method, if not then do not proceed and instead extract your own boot.img and patch that
Build ID for my rephone is: 2000_000170_00_12.0_V06_20221025
Set up adb&fastboot on your computer (google 15 second adb installer)
Grab the patched boot.img from my GitHub and copy it to C:/adb or wherever you installed adb&fastboot: https://github.com/astolfoaddict/GigasetGS5-Magisk
Unlock developer options in your phone and enable OEM Unlocking
Power off your device and hold volume up+power until you boot into bootloader
Select and boot into Fastboot Mode, connect device to your computer
At this point you're in fastboot, open CMD in C:/adb
Your bootloader is probably locked, to check run this command: fastboot getvar unlocked if the result is no, your bootloader is locked
To unlock your bootloader run this command and follow the instructions on your device: fastboot flashing unlock (THIS WILL WIPE YOUR DATA)
Once you unlock your bootloader, wipe your vbmeta partition. Follow Method 3 in this guide: https://www.hovatek.com/forum/thread-32719.html
Now flash the boot.img: fastboot flash boot boot.img
Reboot, set up the device, install Magisk Manager and enjoy!
Advanced method (extracting and patching your own boot.img) :​In this method we'll be extracting the boot partition from your device so you can patch it with Magisk and flash
Proceed with caution!
Install Mediatek VCOM drivers, follow this guide: https://www.hovatek.com/forum/thread-440.html
Dump your boot_a partition with MTK Client by running python mtk r boot_a boot.img follow this guide: https://www.hovatek.com/forum/thread-40865.html
Install Magisk Manager and patch your boot.img
Unlock bootloader, flash empty vbmeta and boot by following the method above
Important:
- Make sure you run python mtk r boot_a boot.img in MTK Client
- If you don't see Mediatek VCOM drivers in Device Manager after using the auto installer, try installing the drivers manually (check guide)
- Also booting into BROM mode is tricky, what usually works for me is:
Power off device and connect to PC
As it starts up and shows you the battery charge, wait until the screen goes out
At this point you should run the python command in MTK Client
Hold volume down+power and check the terminal
If you want to extract the entire firmware follow this guide: https://www.hovatek.com/forum/thread-21970.html
Be aware that your chipset will not be listed in WwR MTK so what you do is open Template.ini with Notepad++ and add MT6768 under the CPU section, don't worry about the chipset not matching what this phone has (MT6769), adding MT6769 to CPU and exporting scatter file will not let you import it in SP flash tool
Special thanks to axonasif and supremegamers for the guide I pulled most of the stuff out of: https://github.com/supremegamers/mt6769​Also thanks to hovatek for their helpful resources regarding MTK flashing/drivers/etc. <3​
Click to expand...
Click to collapse
I’d put the devicees in fastboot mode and run:
fastboot getvar product
Gigaset k69v1_64
Rephone k69v1_64_k419
GS5 and Rephone not the same!!!!!!

astolfoaddict said:
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
try this one, boots and works just fine on my device.
Click to expand...
Click to collapse
Hy
Mobile Data work with this image?

Hy,
my bootloader is unloock.......cant flash any image......
FAILED (remote: 'Not enough space to resize partition')
what can i do????

Hi
i have the same rephone with Build like yours astolfoaddict : 2000_000170_00_12.0_V06_20221025
and did the easy UNLOCKING method.
then i flashed "fastboot flash system lineage-19.1-20230418-UNOFFICIAL-a64_bvS.img"
an now my phone hangs in a bootloop.
did i missed something like the recovery.img cause i dont have that or what i have done wrong ?

Hi everybody,
is this a working method for installing lineage 19 on a rephone? w2273 and hugolight do you had success?
In other words, should i try or not ;-)
thanks.....