Database Info

[TWRP]Lenovo K8 Plus - XT1902-2 - Marino [RECOVERY]

This is Ported TWRP Recovery from a same MT6757 chipset model​--------------------------------------------------------------------------------------------------------------------​
{
"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"
}
Disclaimer
Your warranty is now void.:laugh:
I am not responsible for bricked devices, dead SD cards,thermonuclear war.
Please do some research before flashing it!
YOU are choosing to make these modifications.
you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
How to Flash
- Download the Latest TWRP Recovery Image Attached.
- Flash it via fastboot cmd or via sp flash tool.
- If you want stock recovery then flash stock recovery image with SP tool.
- It is recommended to flash TWRP via FASTBOOT.
How to use SP flash tool
- Install Vcom media tek driver on your pc.
- Boot into meta mode.
- More detail and download available on SPFT
BUGS
Nothing with my device.
Tell me if you found.
DOWNLOAD
Latest TWRP here
Note: This recovery is Android Version sensitive which means it only supports Nougat(7.x) firmware not Oreo(8.x) or Pie (9.x). Flashing this on k8+ running Oreo may brick your device.
THANKS
@GEEKOFIA for porting & customizing.
Arisch for his K8 Plus
GOOGLE for everything.
XDA for publishing.
OFFICIAL COMMUNITY
Official Telegram Group
Official Telegram Channel
======== GEEKOFIA ========
VISIT​

Requirements
1. Your Bootloader must be unlocked.
2. This TWRP is strictly for k8+ running on only nougat firmware (Android 7.x).
3. Internal Storage will be wiped.
Bugs
1. Nothing
2. You tell me
Note: This recovery is Android Version sensitive which means it only supports Nougat(7.x) firmware not Oreo(8.x) or Pie (9.x). Flashing this on k8+ running Oreo may brick your device.
Instructions
1. Go to the fastboot mode.
2. Now paste the recovery in adb folder.
3. Open the cmd by holding shift and press right click in adb folder and then click open powershell window here.
4. Now to confirm that device is connected by typing :-
Code:
fastboot devices
If your device seriel no. appers then it is okay.
6. After that type:-
Code:
fastboot flash recovery twrp-recovery-name.img
7. Now unplug your device and then hold power button till it turns off and then hold volume (-) after that press power button to boot into bootloader then choose recovery mode.
Now you are in TWRP mode.
Note:- After flashing recovery you must have to wipe Internal Storage(format data > yes) to remove encryption. Also, you must have to flash magisk so that it will patch boot.img through which system will not be able to overwrite TWRP again.
Download
TWRP
MAGISK
Q&A
Q: What is the dycrept password?
A: Click on cancel after that format data to remove this permanetly.
Q: Is the Screen black after booting to twrp ?
A: Yes,it is on locked state by default,you have to press power button to unlock it.
OFFICIAL COMMUNITY
Official Telegram Group
Official Telegram Channel
======== GEEKOFIA ========
VISIT​

Pls guide
Hi i am a newbie to rooting. Could you please give me detailed steps. I understood till the point of flashing twrp. After that do I have to wipe data and flash magisk right then? (I have tried installing twrp 2 times but every time after installing and restarting it shows android recovery only.)
One more thing, will I be able to upgrade to oreo through OTA if I have the stock android recovery ( although bootloader is unlocked)?

akiitd94 said:
Hi i am a newbie to rooting. Could you please give me detailed steps. I understood till the point of flashing twrp. After that do I have to wipe data and flash magisk right then? (I have tried installing twrp 2 times but every time after installing and restarting it shows android recovery only.)
One more thing, will I be able to upgrade to oreo through OTA if I have the stock android recovery ( although bootloader is unlocked)?
Click to expand...
Click to collapse
You need to boot your device (lenovo k8 plus) from this twrp. To do this type following code in cmd.
Code:
fastboot boot twrp-name.img
This will boot you to recovery mode (just wait couple seconds),the screen may be black if so,then press the power button and swipe to unlock the recovery screen. Now you have to flash the same twrp-recovery.img file into recovery partition.
If you don't flash twrp-recovery image during that live recovery session,you will not be able to reboot to twrp recovery again.
But if you don't want twrp recovery permanently,just need root access,then you can flash only magisk .zip during this live session and reboot your phone and install magisk manager apk and patch the stock boot image.By this process your phone will have root access without a TWRP recovery.

GEEKOFIA said:
You need to boot your device (lenovo k8 plus) from this twrp. To do this type following code in cmd.
Code:
fastboot boot twrp-name.img
This will boot you to recovery mode (just wait couple seconds),the screen may be black if so,then press the power button and swipe to unlock the recovery screen. Now you have to flash the same twrp-recovery.img file into recovery partition.
If you don't flash twrp-recovery image during that live recovery session,you will not be able to reboot to twrp recovery again.
But if you don't want twrp recovery permanently,just need root access,then you can flash only magisk .zip during this live session and reboot your phone and install magisk manager apk and patch the stock boot image.By this process your phone will have root access without a TWRP recovery.
Click to expand...
Click to collapse
Thank you.
1. What did you mean by "Now you have to flash the same twrp-recovery.img file into recovery partition." Please give detailed steps of how to do that once I reach the twrp screen after flashing twrp. sorry but I am new to all this
2. I have now rooted my phone by flashing patched_boot.img from dhruv aggarwal's post. Now how do I install twrp without losing root? Please give detailed steps(like what command, recovery mode or not...). Can I just flash the twrp.img file you have provided in the post using flashify app?
sorry for troubling you.

akiitd94 said:
You need to boot your device (lenovo k8 plus) from this twrp. To do this type following code in cmd.
Thank you.
1. What did you mean by "Now you have to flash the same twrp-recovery.img file into recovery partition." Please give detailed steps of how to do that once I reach the twrp screen after flashing twrp. sorry but I am new to all this
2. I have now rooted my phone by flashing patched_boot.img from dhruv aggarwal's post. Now how do I install twrp without losing root? Please give detailed steps(like what command, recovery mode or not...). Can I just flash the twrp.img file you have provided in the post using flashify app?
sorry for troubling you.
Click to expand...
Click to collapse
If you have root access then install flashify apk and choose the twrp image you want to flash.

Android 10 update TWRP not booting

Fastboot Stuck as saying booting with logo. Any Solution?
Sent from my GM1911 using Tapatalk

Were you updating to android 10 from 9 or from 10 beta? is it the 2 white dots spinning around the red dot?

I have a problem, I updated from 9 to 10 and lost root and twrp. Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens ?

equlizer said:
Were you updating to android 10 from 9 or from 10 beta? is it the 2 white dots spinning around the red dot?
Click to expand...
Click to collapse
From 9
Sent from my GM1911 using Tapatalk

Jarek84 said:
I have a problem, I updated from 9 to 10 and lost root and twrp. Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens [emoji29]
Click to expand...
Click to collapse
I got a solution
Twrp 3.3.1.65
Sent from my GM1911 using Tapatalk

Jarek84 said:
Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens
Click to expand...
Click to collapse
You can not flash TWRP in fastboot on this device. And that never worked for this device. I know it worked on lots of previous Android devices (standard method to install TWRP). But you should wipe from your mind that notion that it works on the 7 Pro.
The process for Android 9 was to boot TWRP (very different from flash TWRP). But fastboot boot command doesn't work on the Android 10 update. This is similar to the situation when the 7 Pro was first released, and OnePlus fixed the fastboot boot command a bit later.
Current root method, is to flash a patched boot image. But lots of folks seem to be having trouble rooting the new Android 10 stable (even using the proper method). Flashing the stock boot.img is another option (to get the phone working, but no root).

First fastboot stucked
Second no partition found
{
"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"
}
Sent from my GM1911 using Tapatalk

You are not supposed to "flash" twrp through windows. Once you "boot" with windows, you install twrp through twrp.

redpoint73 said:
You can not flash TWRP in fastboot on this device. And that never worked for this device. I know it worked on lots of previous Android devices (standard method to install TWRP). But you should wipe from your mind that notion that it works on the 7 Pro.
The process for Android 9 was to boot TWRP (very different from flash TWRP). But fastboot boot command doesn't work on the Android 10 update. This is similar to the situation when the 7 Pro was first released, and OnePlus fixed the fastboot boot command a bit later.
Current root method, is to flash a patched boot image. But lots of folks seem to be having trouble rooting the new Android 10 stable (even using the proper method). Flashing the stock boot.img is another option (to get the phone working, but no root).
Click to expand...
Click to collapse
False, it was possible on android 9 to flash twrp on this device. It worked perfectly. With android 10 that's not possible unfortunately unless you have it already installed on android pie and you are upgrading. Use the unofficial twrp latest build and flash it after you flash the android 10 update in twrp and you are golden.

Hello All,
I decided to hop back in and root my device. I'm running into the same issue as OP. I try to boot into TWRP and i just get a "fastboot mode" screen. Can anyone clarify if this is doable as of now? and how?
Sorry, I havent rooted a phone in 7+ years.

links2586 said:
Hello All,
I decided to hop back in and root my device. I'm running into the same issue as OP. I try to boot into TWRP and i just get a "fastboot mode" screen. Can anyone clarify if this is doable as of now? and how?
Sorry, I havent rooted a phone in 7+ years.
Click to expand...
Click to collapse
Look here. https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997

hallo dare said:
Look here. https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
Click to expand...
Click to collapse
That doesn't seem to work for me since I can't see my case, which is the same as @Jarek84
Only the stock boot.img boots for me. magisk_patched.img puts me in a bootloop and I'm stuck at the fastboot logo whenever I try to fastboot boot twrp.img (neither official nor the .65 one here, the modified one).
Any help would be appreciated to get root and twrp back.
Thanks!

hallo dare said:
False, it was possible on android 9 to flash twrp on this device. It worked perfectly. With android 10 that's not possible unfortunately unless you have it already installed on android pie and you are upgrading. Use the unofficial twrp latest build and flash it after you flash the android 10 update in twrp and you are golden.
Click to expand...
Click to collapse
Can you cite anyone who flashed twrp from fastboot in op7p.
---------- Post added at 06:12 PM ---------- Previous post was at 06:09 PM ----------
whisky_ said:
That doesn't seem to work for me since I can't see my case, which is the same as @Jarek84
Only the stock boot.img boots for me. magisk_patched.img puts me in a bootloop and I'm stuck at the fastboot logo whenever I try to fastboot boot twrp.img (neither official nor the .65 one here, the modified one).
Any help would be appreciated to get root and twrp back.
Thanks!
Click to expand...
Click to collapse
. Have you tried patching your own boot.img instead of flashing the one provided on the guide?

Everyone who has ever flashed twrp. But if you want evidence,
https://forum.xda-developers.com/showpost.php?p=79677185&postcount=1

hallo dare said:
Everyone who has ever flashed twrp. But if you want evidence,
https://forum.xda-developers.com/showpost.php?p=79677185&postcount=1
Click to expand...
Click to collapse
If you read a little more carefully you will see that the thread you're linking to says exactly what redpoint73 wrote. I.e. in order to flash TWRP one must first fastboot boot the TWRP-image, and then flash the TWRP-zip from within TWRP.
No one said it's not possible to flash TWRP. What was said was that it's not possible to do it from fastboot.
Cheers.

branko.s67 said:
If you read a little more carefully you will see that the thread you're linking to says exactly what redpoint73 wrote. I.e. in order to flash TWRP one must first fastboot boot the TWRP-image, and then flash the TWRP-zip from within TWRP.
No one said it's not possible to flash TWRP. What was said was that it's not possible to do it from fastboot.
Cheers.
Click to expand...
Click to collapse
Obviously you cannot flash from fastboot, but what I'm referencing to is that it was said "twrp cannot be flashed from fastboot" , but that it can be achieved by the method i pointed out to get to recovery to flash. It's not just a case of saying it cannot be flashed and covered the method in one sweeping statement. There is a method, but as we all know, this is not possible currently with Android 10

hallo dare said:
Obviously you cannot flash from fastboot, but what I'm referencing to is that it was said "twrp cannot be flashed from fastboot" , but that it can be achieved by the method i pointed out to get to recovery to flash.
Click to expand...
Click to collapse
Once you have booted recovery, you are no longer in fastboot.
Just try a fastboot command while in TWRP, and see how that works for you.

redpoint73 said:
Once you have booted recovery, you are no longer in fastboot. Duh!!!!
Click to expand...
Click to collapse
Hold on a sec. If you are going to act in a childish manner how are we to discuss this properly.
To even get to twrp you have to use the .img file in fastboot. So "fastboot flash recovery filename.img"
So you are flashing in fastboot to get to twrp recovery.
Your comment said that you couldn't flash twrp via fastboot and never could with this phone. That's half correct. What I'm saying is you can flash the .img file to access twrp before flashing the zip file on Android pie. Unfortunately that's not the case with Android 10.

hallo dare said:
To even get to twrp you have to use the .img file in fastboot. So "fastboot flash recovery filename.img"
So you are flashing in fastboot to get to twrp recovery.
Click to expand...
Click to collapse
Wrong. Your command is incorrect.
The correct command is: fastboot boot twrp.img
Once you are booted to TWRP, you can than flash TWRP installer zip (not the TWRP img).
Just look at the post you quoted above in response #14.
This phone does not even have a recovery partition. Recovery resides on boot.img for this device due to A/B partition scheme.
My original statements hold as correct.

redpoint73 said:
Wrong. Your command is incorrect.
The correct command is: fastboot boot twrp.img
Just look at the post you quoted above in response #14.
This phone does not have a recovery partition. Recovery resides on boot.img for this device.
My original statements hold as correct.
Click to expand...
Click to collapse
O my God, that recognised contributor tag is going to your head.
The command with "boot" boots into TWRP recovery. The command with "flash", flashes the .img file in fastboot mode on Android pie.

Stock rom of Doogee S96 pro

Dear community,
I have a doogee S96 pro, I'm from Italy, and I installed TWRP from the unofficaltwrp guide.
Now I'm no more able to boot, the phones goes directly to the recovery.
Probably magisk was no able to patch the system and to disable the tm verity (avb). I have a super partition, and from what I saw the fstab is inside the vendor partition inside super.
Doogee does not provide stock roms, so I cannot restore the phone as factory settings, that's why I open this thread.
Is someone available to help me booting into Android or available to give me the stock boot/recovery img? It's a fast and safe procedure, I can give more details on how to do.
Thank you!

Dear @giubenez I had a similar problem. But after I got in touch with doogee support they sent me the firmware. I want to share it with you and with any other person that wants to ROOT THE DOOGEE S96 PRO
The following link is the firmware and upgrade tool. Please open and download.
Please note that if your computer system is French you need to change the name of the downloaded file.
Spoiler: Link
ZN129（S96）
Folder
1drv.ms
When upgrading the firmware, please do not select the 'Format All+Download' option
When flashing the phone, please set up the software first, turn off the phone, and then connect the phone to the computer.
Best wishes

Wow! thank you!!!
You saved... us!
Why doogee does not respond to me? why they not post the firmware on the forum? WTF

@giubenez Im very happy to contribute something. IDK why doogee doesnt list this firmware in their website. I was very lucky to receive an answer to my emails.
Also I successfully rooted my S96 PRO, but I learned a few things in the process that might be helpful to you or anyone trying to root this model.
1) After flashing the boot.img (using magisk method). The device went into a boot loop. I could not enter into recovery mode either. I discovered vbmeta was responsible for the boot loop.
Google introduced vbmeta which is also a verity check. An option to bypass this check is to flash an empty vbmeta.img before attempting to flash TWRP recovery.
Click to expand...
Click to collapse
I solved this by flashing an empty vbmeta file.
Code:
fastboot flash vbmeta vbmeta.img
You can download the vbmeta.img file I used HERE
2) After flashing vbmeta, the device finally booted and the root was done. But the first time, I noticed all the internal storage folders and files were encrypted. (I know this is normal when you browse files through TWRP, but it happened to me while using the phone in the first boot)
I solved that by wiping > Format Data in TWRP
3) Here you can find the files I used to install TWRP and remove the orange state notification on boot: LINK "Credits to www.getdroidtips.com"

Ankiseth said:
@giubenez Im very happy to contribute something. IDK why doogee doesnt list this firmware in their website. I was very lucky to receive an answer to my emails.
Also I successfully rooted my S96 PRO, but I learned a few things in the process that might be helpful to you or anyone trying to root this model.
1) After flashing the boot.img (using magisk method). The device went into a boot loop. I could not enter into recovery mode either. I discovered vbmeta was responsible for the boot loop.
I solved this by flashing an empty vbmeta file.
Code:
fastboot flash vbmeta vbmeta.img
You can download the vbmeta.img file I used HERE
2) After flashing vbmeta, the device finally booted and the root was done. But the first time, I noticed all the internal storage folders and files were encrypted. (I know this is normal when you browse files through TWRP, but it happened to me while using the phone in the first boot)
I solved that by wiping > Format Data in TWRP
3) Here you can find the files I used to install TWRP and remove the orange state notification on boot: LINK "Credits to www.getdroidtips.com"
Click to expand...
Click to collapse
GOD BLESS YOU, Ankiseth!
YOU SAVE MY PHONE! SPFLASH AND EVERYTHING WORKS!

Hi guys : I need help. Since the last firmware update (settings/about phone/update) DOOGEE-S96Pro-EEA-Android10.0-20210128, my Ir Camera don't work anymore
Video : https://oracle.tuxme.net/s/Xng63Ej3kJoJhOj
When I used the dial mode *#*#8613#*#* SINGLE TEST
* INFRAED LIGHT : i see the IR light
* Night Vision camera : app crash like the camera when i switch to the night vision mode.
Doggee mail me :
Good day, I would like to ask you to help us. Please use the following link: https://1drv.ms/u/s!AvX9KABcpSV1kTOgCMsUkLyXY-we?e=nMchxl Download the previous version of the S96pro firmware and follow the tutorial to return the phone to OTA The previous version (ver3.02) was upgraded. The tutorial has been included in the firmware compression package. Please test the night vision camera after flashing the camera and let me know if it can be used normally. Thank you very much.
Click to expand...
Click to collapse
But the documentation is .... you know ...
Have you a step by step tutorial or tools to do that ?
Beanpod_ActiveTool is a tool to modified serials, Imei ?
Have i to used SP Flash tool ?
Thanks guys !!
by the way @Ankiseth :
Please note that if your computer system is French you need to change the name of the downloaded file.
Click to expand...
Click to collapse
which file ?

berzerking said:
Hi guys : I need help. Since the last firmware update (settings/about phone/update) DOOGEE-S96Pro-EEA-Android10.0-20210128, my Ir Camera don't work anymore
Video : https://oracle.tuxme.net/s/Xng63Ej3kJoJhOj
When I used the dial mode *#*#8613#*#* SINGLE TEST
* INFRAED LIGHT : i see the IR light
* Night Vision camera : app crash like the camera when i switch to the night vision mode.
Doggee mail me :
But the documentation is .... you know ...
Have you a step by step tutorial or tools to do that ?
Beanpod_ActiveTool is a tool to modified serials, Imei ?
Have i to used SP Flash tool ?
Thanks guys !!
by the way @Ankiseth : which file ?
Click to expand...
Click to collapse
There Is Hope Brother... I Just Downloaded The Files And Used The SCATTER-LOADING FILE From 3.02 on SP-FlashTools 5.2 Switched It To Download Only And Hit Download .. Plugged In My Phone To USB While OFF And aftyer the loading was complete .. Phone Reboot As If NEW. ( HARD RESET) EVERYTHING LOST WARNING.. But IR CAMERA is Working AGAIN!!!!! Now i Just Have To ReLoad All Apps And Accounts .. And Wait For The oukitel WP7 i ordered out of frustration. Will Be Doing A Review Comparison On Both Cameras !!!!! You Can Follow Me Here If Interested https://www.youtube.com/channel/UCYOpd4yooYgKS-0xe63jnCw

Hi all. Thanks for the information. I was in touch with doogee and they say to me that there is an update during this WE (S9S88A7.DGE.DOOGEE.EEA.HB.HJAYYDVFAZ.0128.V3.03820210313-2312.
Nothing change IR camera don't work
I will flash my S96pro during the week with S9S88A7.DGE.DOOGEE.EEA.HB.HJ.AYYDVFAZ.1130.V3.02.zip and I'll post here what happened

HouseOwl said:
) EVERYTHING LOST WARNING.. But IR CAMERA is Working AGAIN!!!!!
Click to expand...
Click to collapse
Yes !!!!! it s alive !!!!
Thank you dude ! my ir works again !!!!!

btw a couple of days after your post, another user posted the same folder on https://4pda.ru/forum/index.php?showtopic=1010578&st=340.
I rooted the phone by using the 4pda method (i.e. flashing super.img, boot.img, vbmeta.img). After that I flashed twrp and it was fine. Everything was working.
After that I downloaded the OTA update and the phone is no more able to boot, simply goes to TWRP. I tried formatting data, dalvik and cache but the situation is always the same: when i try to boot i go to the recovery. Any idea? Thank you

berzerking said:
But the documentation is .... you know ...
Have you a step by step tutorial or tools to do that ?
Beanpod_ActiveTool is a tool to modified serials, Imei ?
Have i to used SP Flash tool ?
Thanks guys !!
by the way @Ankiseth : which file ?
Click to expand...
Click to collapse
Can you write a tutorial? Have you used SP flash tool?
Thank you!

giubenez said:
btw a couple of days after your post, another user posted the same folder on https://4pda.ru/forum/index.php?showtopic=1010578&st=340.
I rooted the phone by using the 4pda method (i.e. flashing super.img, boot.img, vbmeta.img). After that I flashed twrp and it was fine. Everything was working.
After that I downloaded the OTA update and the phone is no more able to boot, simply goes to TWRP. I tried formatting data, dalvik and cache but the situation is always the same: when i try to boot i go to the recovery. Any idea? Thank you
Click to expand...
Click to collapse
I solved in this way:
>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(with the empty vbmeta
>fastboot.exe flash recovery recovery.img
(with the stock recovery)
>fastboot reboot
after that the update attempted to start and failed, the phone then boot to android.
The updates always failes after that, so I disabled them.

this is why the update fails..is it because I used the the Russian super img?
{
"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"
}
#edit: it was because I flashed the wrong recovery. With the correct one, i still have issues with the update: md5 chechsum controll is not passed and the update aborts.
I don't care, I prefer a rooted phone without the updates.

your device has not passed the test and may not work properly - Here is a message on the screen . Constantly overloaded is not included in the recovery. The firmware doesn't help.

Could someone repost the S96Pro stock firmware... I can't find it anywhere online, thanks in advance

I'm uploading them.
https://bit.ly/3en9EZY

Thanks giubenez ,u saved me but now I have the watermark from formatting Google Key State : Fail, I don't see a factory mode file to freeze, tried ADB and couldn't find the build prop values, has anyone else ran into this with a fix?

I can't get what problem are you facing. I unlocked and rooted my s96 pro.
If you describe your issue i can help you solving it.
However, i found very risky to root the phone, if you plan to do the ota updates avoid TWRP since it'll make you bootloop at the moment you try to install the update.
The only way to solve it is to flash the stock recovery through adb.

So.. yeah.
I have recently procured this device and want to install twrp, and stock and/or test a gsi and in what capacity the phone works with one of those.
Enabled both developer mode & the usb debug mode and adb devices lists the device.
N.B; the supplied s96pro cable does not seem to carry data, "presumably" because doogee is cheapskates on cables, as well in the support department. I had to use my sony headphone cable. Go figure, its consequential at least, so there's that.
In any case, read this thread and have downloaded all files, including the apparently new stock rom that is listed since yesterday in the evidently wholesome user Ankiseth's link above.
Questions:
In the 4pda link there are some instructions, specifically the adb command with the boot.img, however.. the links seems to be dead. What to do?
A) Can I first do the vbmeta command and then use our lord and savior Ankiseth's twrp recovery file and follow a generic "Case II: Devices with A/B partition scheme" mentioned in this xda twrp guide?
B) Hope that some other wholesome user share the boot.img file?
(Or, can I use the one in the zip file 'S9S88A7.DGE.DOOGEE.HB.HJ.AYYDVFAZ.1203.V3.04' ?)
-
After twrp is accessible can I use twrp/adb and install either the mentioned shared rom and any gsi for that matter?
I use linux and sure there is spflash, but the adb & twrp combo "subjectively feels" as a more stable way of doing things.

Update 2. Got both twrp and magisk going. Now to figure out if I can install a gsi.
Update, got spflashtool working and used the latest stock rom mentioned in my previous post.
However.
I patched the boot.img from said stock rom in magisk and also flashed twrp-recovery with fastboot.
No luck. Magisk seems not to be installed and the usual twrp gui does not show, seems to be the stock recovery. Got a orange state though.

How To Guide Gaining root access on New Oxygen OS A12 for the op9.

Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
Just sharing what I've learned. Have to patch boot.img and vendor boot.img and flash out of folder in sdk on desktop.Then use vb_meta.img to disable verity flash. Guide above has to be followed to a T. Even though it's for the Chinese version Color os works fine on Oos... Patch boot.img /vendor_boot with magisk 23.0. This way magisk hide and modules work. If you patch with canary version of magisk you loose both. I'm attaching stock boot, vb_meta vendor_boot.img files for the Global unlocked op9. Files are from new A12 os. Btw 23.0 works perfectly on A12. If this helps hit the like button; it's free.
0p9 partitions..A 12 - Google Drive
drive.google.com

This method is overkill for rooting both versions of A12 that were released ,
The best method for a12 with unlocked bootloader is this:
Patch boot.img & copy to adb folder on pc
Reboot to bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot *nameofpatchedbootimagehere.img*
IF YOUR DOING A CLEAN FLASH OF A12 BEFORE SETUP = fastboot-w
fastboot reboot
Worst case scenario you will have to wipe all data for it to register correctly and boot fully.
The vendor_boot does not need to be patched with the A12 update, you have to disable verity and verification instead of just verification for any device running A12.

allenjthomsen said:
This method is overkill for rooting both versions of A12 that were released ,
The best method for a12 with unlocked bootloader is this:
Patch boot.img & copy to adb folder on pc
Reboot to bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot *nameofpatchedbootimagehere.img*
IF YOUR DOING A CLEAN FLASH OF A12 BEFORE SETUP = fastboot-w
fastboot reboot
Worst case scenario you will have to wipe all data for it to register correctly and boot fully.
The vendor_boot does not need to be patched with the A12 update, you have to disable verity and verification instead of just verification for any device running A12.
Click to expand...
Click to collapse
I do know that just patching boot.img and flashing it breaks boot and build. Found that out the hard way. Could only reach fastboot no stock recovery . And couldn't fastboot --set-active=other. Wipe data and boot into old oos on opposite slot. I've had msm tool on my desktop and have heard horror stories of people using and it throwing errors and failing. Plugged mine right in booted edl from adb and 512 sec later had a booting device in oxygen oos

mattie_49 said:
I do know that just patching boot.img and flashing it breaks boot and build. Found that out the hard way. Could only reach fastboot no stock recovery . And couldn't fastboot --set-active=other. Wipe data and boot into old oos on opposite slot. I've had msm tool on my desktop and have heard horror stories of people using and it throwing errors and failing. Plugged mine right in booted edl from adb and 512 sec later had a booting device in oxygen oos
Click to expand...
Click to collapse
I can verify that my method works 100% on build C.36 of A12, because i am currently running it and have redone the steps multiple times to make sure nothing happens that could be bad ,the steps i have listed above in the previous post work perfectly and still let me have root currently, and i have only patched the stock boot.img.
{
"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"
}

If your wondering how i have come to this doing it the way i did it.
I downloaded and copied the update to desktop and extracted the stock boot and patched it in magisk from the device.
I then i extracted the stock vbmeta image and after flashing the full update via local install from system settings i booted to bootloader and disabled verity and verification and then flash the patched boot image.
I then rebooted into full stock C.36 with root.
I can tell you i did this 5 times before i made the reply to you earlier and verified that it booted every time no issue without patching vendor_boot.

allenjthomsen said:
If your wondering how i have come to this doing it the way i did it.
I downloaded and copied the update to desktop and extracted the stock boot and patched it in magisk from the device.
I then i extracted the stock vbmeta image and after flashing the full update via local install from system settings i booted to bootloader and disabled verity and verification and then flash the patched boot image.
I then rebooted into full stock C.36 with root.
I can tell you i did this 5 times before i made the reply to you earlier and verified that it booted every time no issue without patching vendor_boot.
Click to expand...
Click to collapse
How does one undo the disable verity with stock vb_meta after flashing back stock boot.img and vendor boot.img ,I still couldn't take internal Google ota today. Failed after I tried restoring both of those.

Anyone knows if the new oos12 is actually "stable"? Haha

infamousvincci said:
Anyone knows if the new oos12 is actually "stable"? Haha
Click to expand...
Click to collapse
Yes all the small issues I had are corrected in today's am build.

mattie_49 said:
Yes all the small issues I had are corrected in today's am build.
Click to expand...
Click to collapse
I talk to you in TG bro. Its me, the one that has a op9 that doesnt read sim on oos12. Hahaha

mattie_49 said:
I do know that just patching boot.img and flashing it breaks boot and build. Found that out the hard way. Could only reach fastboot no stock recovery . And couldn't fastboot --set-active=other. Wipe data and boot into old oos on opposite slot. I've had msm tool on my desktop and have heard horror stories of people using and it throwing errors and failing. Plugged mine right in booted edl from adb and 512 sec later had a booting device in oxygen oos
Click to expand...
Click to collapse
Oh maan, that was my last night. Lost weeks worth of data with no back up
And I've bricked and recovered before but the way this one acted was scary as hell. A few times it said "die" at the crashdump.

mizarddo said:
Oh maan, that was my last night. Lost weeks worth of data with no back up
And I've bricked and recovered before but the way this one acted was scary as hell. A few times it said "die" at the crashdump.
Click to expand...
Click to collapse
Hello, please can you give me more details about what causes you the loss, how you did it because I'm about to do the same process and I'm afraid to get my onePlus 9 bricked

mooadeer said:
Hello, please can you give me more details about what causes you the loss, how you did it because I'm about to do the same process and I'm afraid to get my onePlus 9 bricked
Click to expand...
Click to collapse
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.

mizarddo said:
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.
Click to expand...
Click to collapse
It helps a lot thank you I just got my oneplus 9 and it's on the latest update C.47 and I don't have too much experience with onePlus or even the new android devices I'm a little bit outdated didn't use root and stuff sins the android 5 that's why I'm a little bit confused I don't want to break it

mizarddo said:
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.
Click to expand...
Click to collapse
Update following your instructions everything is Ok done with rooting thank you
LE2113 on C.47

mizarddo said:
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.
Click to expand...
Click to collapse
from where can I download boot.img for version:
LE2113_11.C.47: LE2113_11.C.47_1470_202203102118
Thanks and best regards

Lol patching the boot image then flashing it with simple "fastboot flash boot patchedboot.img" works for me. It does not require any other images or patches.

_MartyMan_ said:
Lol patching the boot image then flashing it with simple "fastboot flash boot patchedboot.img" works for me. It does not require any other images or patches.
Click to expand...
Click to collapse
you mean boot image from OP? My question is how I get that file

aldoc01 said:
you mean boot image from OP? My question is how I get that file
Click to expand...
Click to collapse
Yep, stock boot images can be extracted from full zips with tools (payload extractor).
Also, i have a collection, check it out.

_MartyMan_ said:
Lol patching the boot image then flashing it with simple "fastboot flash boot patchedboot.img" works for me. It does not require any other images or patches.
Click to expand...
Click to collapse
So you think the same way the 9 Pro does it would work? The guide there says to grab the stock image, install Magisk app on the phone, patch the image with the app, boot (not flash) the image, then have Magisk direct install. I came here and saw all of this other stuff and was like... nahhh...

EtherealRemnant said:
So you think the same way the 9 Pro does it would work? The guide there says to grab the stock image, install Magisk app on the phone, patch the image with the app, boot (not flash) the image, then have Magisk direct install. I came here and saw all of this other stuff and was like... nahhh...
Click to expand...
Click to collapse
If you don't jump magisk across from A11 you have to disable verity with vb_meta partition as well to gain permanent root on A12. This I know it's my post.

TruConnect CloudMobile Stratus C5 Elite Firmware

Hello,
I have been trying to root this device for some time now without success. I know for Magisk to work I need a copy of the boot.img from the stock factory image and I have been unable to find the factory image anywhere. I know there's a way to pull the boot.img from the device itself with TWRP installed but, there's no TWRP image for this device either and I need the recovery.img to port that over. I wonder if there is a way to pull the boot.img and recovery.img from the device without TWRP installed and without root? Perhaps someone knows. I was able to unlock the bootloader in fastboot with: fastboot flashing unlock .
This is a very light device with not a lot of memory or storage and I'd love to be able to tweak it out a bit to remove a lot of clutter and enable it to run smoother and charge faster and hold a charge longer. I removed some bloat through adb. Any help would be greatly appreciated. I will attach screenshots of the system specs below. Thank you for your time.
{
"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"
}

I have that phone at home, I've tried numerous ways to root it with no avail. The ONLY solution I can suggest is finding a program that can extract the entire firmware from the phone and then taking it from there. Plus, with a unlocked bootloader u shouldn't have an issue getting it done. I do remember coming across the topic of firmware extraction online and im pretty sure one of the methods involved ADB, but it's a painstaking process cus u have to extract everything one by one. Search Google about that method. Good luck man.

I am having problems with my lock screen pattern the buttons are not working. What do I do I can't get in my phone

__Pno.0iD said:
I have that phone at home, I've tried numerous ways to root it with no avail. The ONLY solution I can suggest is finding a program that can extract the entire firmware from the phone and then taking it from there. Plus, with a unlocked bootloader u shouldn't have an issue getting it done. I do remember coming across the topic of firmware extraction online and im pretty sure one of the methods involved ADB, but it's a painstaking process cus u have to extract everything one by one. Search Google about that method. Good luck man.
Click to expand...
Click to collapse
Full_Device_Stock_Backup.7z | by kushpr for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I found this. I'm not sure who it is. I have not tested it. But a boot image is present. It maybe for Android 10 or 11 but it holds vbmeta as well. If bootloader is unlocked I would assume patch with magisk and flash via fastboot flash boot. I tried many ways to fastboot boot a image as I don't wish to flash a untested image. It always fails so I'm not entirely sure.
******curiosity ed the cat. These do not boot. FML LOL******.
The boot images do not boot. However if I flash the provided vbmeta as fastboot flash --disable-verification --disable-verity vbmeta /patchedvbmeta.img then the user provided twrp fastboot flash boot /c5twrp.img. I can then fastboot reboot and it will now load twrp with no storage being mounted. I also prior fastboot flashing unlock.
Fastboot flashing unlock_critical
Not sure if that worked for critical or not.

JovialQuestion said:
Full_Device_Stock_Backup.7z | by kushpr for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I found this. I'm not sure who it is. I have not tested it. But a boot image is present. It maybe for Android 10 or 11 but it holds vbmeta as well. If bootloader is unlocked I would assume patch with magisk and flash via fastboot flash boot. I tried many ways to fastboot boot a image as I don't wish to flash a untested image. It always fails so I'm not entirely sure.
Click to expand...
Click to collapse
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Heres the files for the device I found but again I've tested none

Hey, flashed the boot images and now phone won't boot, which was expected honestly, but how do I restore original firmware from the bin files in the backup.7z archive?

Kylethedarkn said:
Hey, flashed the boot images and now phone won't boot, which was expected honestly, but how do I restore original firmware from the bin files in the backup.7z archive?
Click to expand...
Click to collapse
I'm not sure as I did not upload the bin file. However I did find out that boot img and frimware is not for the Android 12 go but 10 go release C5 stratus but the twrp when I flashed to the boot partition would boot it. You can try and see if flashing it will boot the twrp img and ar least your able to use root adb. Otherwise I'm still trying to figure it out. I simply found the files while searching

JovialQuestion said:
Full_Device_Stock_Backup.7z | by kushpr for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I found this. I'm not sure who it is. I have not tested it. But a boot image is present. It maybe for Android 10 or 11 but it holds vbmeta as well. If bootloader is unlocked I would assume patch with magisk and flash via fastboot flash boot. I tried many ways to fastboot boot a image as I don't wish to flash a untested image. It always fails so I'm not entirely sure.
******curiosity ed the cat. These do not boot. FML LOL******.
The boot images do not boot. However if I flash the provided vbmeta as fastboot flash --disable-verification --disable-verity vbmeta /patchedvbmeta.img then the user provided twrp fastboot flash boot /c5twrp.img. I can then fastboot reboot and it will now load twrp with no storage being mounted. I also prior fastboot flashing unlock.
Fastboot flashing unlock_critical
Not sure if that worked for critical or not.
Click to expand...
Click to collapse
I have tested the Full Stock Backup and it's 100√ working..

Kylethedarkn said:
Hey, flashed the boot images and now phone won't boot, which was expected honestly, but how do I restore original firmware from the bin files in the backup.7z archive?
Click to expand...
Click to collapse
What I did was I put the phone on Brom/preloader and flash with Rom2Box version 3.0 , select on Firmware folder .no scatter file

Smil3yWulf said:
What I did was I put the phone on Brom/preloader and flash with Rom2Box version 3.0 , select on Firmware folder .no scatter file
Click to expand...
Click to collapse
Thanks for this

Mtkclient allowed me to root mine

Smil3yWulf said:
I have tested the Full Stock Backup and it's 100√ working..
Click to expand...
Click to collapse
Awesome.. I know the C-5 twrp uploaded by the same person worked when I flashed it to the boot partition after the flashed boot img failed for me. If it has a recovery partition maybe you can flash that and try it out to the recovery partition
Twrp
20.82 MB folder on MEGA
mega.nz

My bootloader is unlocked, twrp flashed to recovery booting fine when selected from the button combo preloader or whatever, but I still have no boot.img. I only have access to computers running linux right now so rom2box is kinda not a reliable option for me. Is there some way of turning boot.bin and/or boot_para.bin into a bootable boot.img? Or is there any way anybody who still has one of these phones could get a working one from their phone by way of twrp or something? Is the c5 treble compatible?

Jason Hugg said:
My bootloader is unlocked, twrp flashed to recovery booting fine when selected from the button combo preloader or whatever, but I still have no boot.img. I only have access to computers running linux right now so rom2box is kinda not a reliable option for me. Is there some way of turning boot.bin and/or boot_para.bin into a bootable boot.img? Or is there any way anybody who still has one of these phones could get a working one from their phone by way of twrp or something? Is the c5 treble compatible?
Click to expand...
Click to collapse
A boot.bin file is a img. .bin .img .fex .iso are all image files. How large is the boot.bin file. 34mb? 64mb and this bootloader doesn't fastboot boot unless it's got dtb and I'm not familiar with it. Flash the boot.bin and try to boot if your boot slot is already messed up should not be a issue to try.

What ended up working for me was to go to the Advance Fastboot tab in the Android part of rom2box and flash each partition, rebooted after and success. So I fastboot flash --disable-verification --disable-verity vbmeta vbmeta.bin, which allowed me to fastboot flash recovery twrp-C5.img and it boots fine from the boot selection screen. After/during initial setup, phone did a mandatory system up[date, but since I knew I could reflash and recover from a screw up, I installed Magisk Manager and used it to patch and flash the boot.bin included in the backup and it worked fine. Just figured I'd post an update in case it might help anyone else

Jason Hugg said:
Sorry my page keeps redirecting and I am posting in the wrong posting
Click to expand...
Click to collapse

I have the boot.img for the cloud stratus C5 elite if you still need it. I have the complete stock firmware for the phone. If you need it just message me

chuck1es909090 said:
I have the boot.img for the cloud stratus C5 elite if you still need it. I have the complete stock firmware for the phone.
Click to expand...
Click to collapse
DO NOT SEND IN EMAILS. This is a forum so people can get assistance with the help of others. You can share the files here but it's not recommended to share your email asking for people to contact you that way. Not to mention everyone can now see your email and your personal data