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.
Related
"warning this will wipe your data"
"warning make sure that the tablet matches the firmware TB_X605F_USR_S200065_1905280020_Q00332_ROW
1. download adb setup https://forum.xda-developers.com/showthread.php?t=2588979
and install it
2. download the TB-X605F firmware http://www.mediafire.com/file/1uo5eu6iuzx39cd/TB_X605F_USR_S200065_1905280020_Q00332_ROW.zip/file
3. on the tablet go to settings and enable developer options
4. enable oem unlock and usb debugging
5. plug the tablet into the computer with usb cable and check the box on the tablet that allows usb debugging
6. reboot into fastboot using "adb reboot bootloader"
7. once fastboot has loaded type "fastboot oem unlock-go" to unlock the bootloader
8. then on computer extract the zip file and look for boot image "boot.img"
"make sure you have usb debugging enabled in developer options"
9. once your tablet is set up, on the android system prompt click "Charging this device via usb"
then click "Media device MTP" to access tablet storage on computer
10. download the magisk.apk file http://www.mediafire.com/file/vinf7xswbir90yi/magisk.apk/file
11. once downloaded drag the "boot.img" in firmware folder to internal storage
12. open command prompt and type adb install "the directory of the magisk apk file"
13. once magisk is installed launch the app and go to install / install / Select and Patch a File and look for the location of the boot.img
14. magisk will patch the boot image and put it in the download directory
15. go into download directory and you will see magisk_patched.img
16. on computer drag the magisk_patched.img on tablet storage to the directory where you want it to be
17. open cmd on computer type adb reboot bootloader
18. type fastboot flash boot "the directory of the magisk_patched.img"
19. once flashed type fastboot reboot
20. once booted go into magisk if it asks to update manager then update it, once the updated magisk manager is installed go to install / install / Direct Install to update root
Hi,
great job!
Do you know if it is possible to flash a recovery?
Thanks
Bootloop when trying magisk root
Hello,
I've tried your method, but since I've done "fastboot flash boot magisk_patched.img" my tablet entered in bootloop.
Impossible to flash original firmware with QFIL: I've "Switch to EDL download fail" error...
{
"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 also tried Lenovo Moto Smart Assistant, but it fail too.
Many thanks for your help to rescue my tab...
justalone said:
Hello,
I've tried your method, but since I've done "fastboot flash boot magisk_patched.img" my tablet entered in bootloop.
Impossible to flash original firmware with QFIL: I've "Switch to EDL download fail" error...
I also tried Lenovo Moto Smart Assistant, but it fail too.
Many thanks for your help to rescue my tab...
Click to expand...
Click to collapse
What error did LMSA give you? The vol-up + USB-in combo is really touchy. Maybe give it a few more tries with LMSA.
Someone else had probs like this, but was able to boot into recovery using Pwr+VolUp+VolDown combo. If that works, see if you can factory reset.
justalone said:
Hello,
I've tried your method, but since I've done "fastboot flash boot magisk_patched.img" my tablet entered in bootloop.
Impossible to flash original firmware with QFIL: I've "Switch to EDL download fail" error...
I also tried Lenovo Moto Smart Assistant, but it fail too.
Many thanks for your help to rescue my tab...
Click to expand...
Click to collapse
Did you try power+vol up+vol down, 10 seconds long? It reinitialize the tab.
Good luck, neighbour
Hello,
thanks a lot for you help, LMSA stuck a 67% with error "fail to rescue".
The good solution was from my french neighbour with "power+vol up+vol down" for more than 10s. I then got acces to recovery and go to fasboot mode to flash original boot.img.
I've been then able to use LMSA to rescue my TAB and it's back to life !
I just wonder why magisk's boot generated was wrong... I'll make some other try in the weekend to root my tab.
Thanks a lot.
Merci du Var !
justalone said:
Thanks a lot.
Merci du Var !
Click to expand...
Click to collapse
De rien / you're welcome.
I had the same issue at 67% with LSMA.
Before I rooted the Tab, I upgraded it to Android 9 in Settings/System. Then everything worked fine.
I hope your house is safe despite this crazy rain.
This didnt work for me but maybe because the firmware that was on the tablet was 3 updates newer than the OP firmware.
It was stuck at the LENOVO boot image sadly
It took a long time but I got the tablet back trough a rescue.
The firmware was and again is: TB-X605F_S210126_191029_ROW
And I wonder if it will work if I get a boot.img from this firmware and patch it.
KrazyKlutt said:
This didnt work for me but maybe because the firmware that was on the tablet was 3 updates newer than the OP firmware.
It was stuck at the LENOVO boot image sadly
It took a long time but I got the tablet back trough a rescue.
The firmware was and again is: TB-X605F_S210126_191029_ROW
And I wonder if it will work if I get a boot.img from this firmware and patch it.
Click to expand...
Click to collapse
There's a magisk_patched.img for that build over on this thread.
Yahoo Mike said:
There's a magisk_patched.img for that build over on this thread.
Click to expand...
Click to collapse
Thanks a million Mike! You’re the best ?
XDA can be a jungle sometimes, I though I did research but I missed both the root thread and the TWRP thread for 605F.
That would have saved my lots of time a headache haha , but I didn’t get a heart attack so it’s all good.
Anyway, the patched Magisk worked perfectly, and all is good , finally a working YouTube Vanced since my previous Xperia 2 tablet.
The only weird thing was the link issue from Lenovo’s recovery for the latest firmware, the full one, not the ota updates.
???
twrp has problems, with screen bootlooping in twrp when trying to install zip files, the recovery is faulty and we probably need a new tree for the fix, which i was trying to look for an official tree, but i mean we already have one and when you compile it, it produced a faulty recovery image and lenovo hasn't released a kernel source or device tree yet, but i hope i can get a fully working one
turboperson123 said:
twrp has problems, with screen bootlooping in twrp when trying to install zip files, the recovery is faulty and we probably need a new tree for the fix...
Click to expand...
Click to collapse
Try this TWRP for X605F. I've been using the "update" function with no problems.
turboperson123 said:
... lenovo hasn't released a kernel source or device tree yet...
Click to expand...
Click to collapse
Have a look at this post.
There are so many hardware variants of the M10 now, it's probably impossible for Lenovo to release reliable kernel source. There's now even an M10 that uses SDM429 (rather than SDM450). ...and the second gen M10 FHD Plus (X606F) will use the MediaTek Helio P22T.
hello i have a problem i do the adb install command but it say "Missing APK file" plz help me
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~)
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel!
Click to expand...
Click to collapse
Images
Prerequisites
Unlocked Bootloader
Click to expand...
Click to collapse
Installation instructions
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
Code:
fastboot reboot
Alternate Installation Method (requires prior TWRP installation):
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed. NOTE: This will only flash TWRP to the active slot!
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Click to expand...
Click to collapse
Device Changelog
Current version: 3.6.0_11-0:
Initial version
Click to expand...
Click to collapse
Older Device-specific versions:
N/A
Click to expand...
Click to collapse
Click to expand...
Click to collapse
TWRP Official Change Log
Frequently Asked Questions (FAQ)
Downloads
Download
Latest Official versions
Sources
TWRP
Device tree
Common tree
Kernel source
Click to expand...
Click to collapse
Known Issues
Device-specific
N/A
TWRP Upstream
N/A
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"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 issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Click to expand...
Click to collapse
Additional Help/Support
Live support is available on Zulip.
Click to expand...
Click to collapse
Frequently Asked Questions (FAQ)
How do I install an OTA while rooted and keep TWRP/root?
Full Firmware zip - in Android
Prerequisites:
Full Firmware zip for new software
TWRP zip from twrp.me
Magisk app
Steps:
Put Full Firmware zip on root of internal storage
Reboot the device so that the update is detected
Install the update
After install completes BUT BEFORE REBOOTING, install TWRP zip in Magisk app
Install Magisk "to Inactive Slot (After OTA)" in Magisk app
Reboot and you're updated with TWRP and root retained
Full Firmware zip - Through TWRP
Prerequisites:
Full Firmware zip for new software
TWRP image or TWRP zip from twrp.me
Magisk apk (optional)
Steps:
Reboot into TWRP
Navigate to Full Firmware zip and install, or sideload zip over adb
Install TWRP image using "Install Image" (check "Flash to both slots" option), or flash TWRP zip to retain TWRP.
(Optional) Reboot into TWRP and flash Magisk for root.
Incremental OTA package - Through TWRP ONLY
Prerequisites (for stock images, see attachments to post #3):
Current software stock boot.img
Current software stock recovery.img
Current software stock dtbo.img (only if modified by Magisk or custom ROM)
Incremental OTA zip for current software to new software
TWRP image or TWRP zip from twrp.me
Magisk apk (optional)
Steps:
Ensure you have the latest version of TWRP installed. If you don't, follow the instructions in the OP to flash it.
Boot into TWRP.
Use the "Install Image" feature to flash the stock boot and recovery (and dtbo) images.
Flash the incremental OTA zip. Make a note of the slot to which the zip is installing (you will need this after the next step).
Install TWRP image using "Install Image" (check "Flash to both slots" option), or flash TWRP zip to retain TWRP.
Open the Reboot menu in TWRP and switch to the slot to which the zip installed from step 4. Reboot to system now, or go to the next step.
(Optional) Reboot into TWRP and flash Magisk for root.
The key here is making sure the current slot is fully stock (including boot and recovery images) in order for the incremental OTA zip to install successfully.
What's the deal with these dynamic partitions?
Here's Google's explanation.
Why can't I write to system?
Dynamic partitions (see link above). See @topjohnwu's detailed explanation here.
How do I make modifications to system?
On the stock ROM, you don't. However, you can modify system "systemlessly" with Magisk.
Can I boot the recovery image without flashing it?
No. Fastboot boot isn't possible on this device, but since there's a separate recovery partition (two in fact), and ASUS provides full stock firmware, this isn't a big concern.
What is fastbootd?
Here's Google's explanation.
Can I back up the system/vendor partition separately?
No. Because dynamic partitions. The Super partition is backed up and restored in its entirety. If you need to flash the individual images, use fastbootd.
Why can't I restore X partition (read-only error)?
Some of the partitions that can be backed up in TWRP include sensitive device data which, if corrupted, backed up, and then restored, can irreparably damage the device. Therefore, while these partitions can be backed up in TWRP, only experienced users should restore them, which can be done manually via the dd command.
(I will not provide any additional details on this procedure)
Click to expand...
Click to collapse
Stock Boot/DTBO/Recovery Images
Keep up the good work m8 @Captain_Throwback :highfive:
Great job!
Reserved
sup guys. been a long time that i havent installed twrp.
jiz wanna ask if i have twrp if OTA is still possible?
Woohoo! Excellent!
Sent from my ASUS_I003D using Tapatalk
about twrp
hey guys, i have tried to install the twrp but after installing using the powershell whenever I try to restart to recovery it just shows the twrp loading screen and restarts back to the phone, so basically I dont have any recovery anymore
Monsibd said:
hey guys, i have tried to install the twrp but after installing using the powershell whenever I try to restart to recovery it just shows the twrp loading screen and restarts back to the phone, so basically I dont have any recovery anymore
Click to expand...
Click to collapse
This happened to me before when my device data partition got corrupted. You'll have to do a RAW flash that uses fastboot -w to clean up the corrupted data. Then TWRP should work. Unfortunately that is unrelated to TWRP.
chacho_2me said:
sup guys. been a long time that i havent installed twrp.
jiz wanna ask if i have twrp if OTA is still possible?
Click to expand...
Click to collapse
Well, unlocking the bootloader means you won't get an OTA from ASUS anymore, but that has nothing to do with TWRP. When a new OTA becomes available, you will be able to flash the full firmware file in TWRP, if that's what you're asking.
EDIT: Installing TWRP won't prevent you from being able to place a firmware file on the root of your storage so that the system updater will detect and install it, either. That process happens outside of recovery so flashing TWRP is unrelated to it. However note that after flashing an OTA update, TWRP will need to be flashed again, as the OTA will write stock recovery to the slot where the OTA is installed.
Captain_Throwback said:
This happened to me before when my device data partition got corrupted. You'll have to do a RAW flash that uses fastboot -w to clean up the corrupted data. Then TWRP should work. Unfortunately that is unrelated to TWRP.
Click to expand...
Click to collapse
hey there, thank you so much my man you fixed my mobile! you rock!! <3
however now theres a new problem after doing the Fastboot -w, i installed the twrp but i cant mount the data partition because it asks for password (which there shouldnt be cause i just reset the phone) and after restarting into the system and setting it up, I get the same results as before (the twrp loading screen shows and reboots back to system).... so yea kind of lost now
Monsibd said:
hey there, thank you so much my man you fixed my mobile! you rock!! <3
however now theres a new problem after doing the Fastboot -w, i installed the twrp but i cant mount the data partition because it asks for password (which there shouldnt be cause i just reset the phone) and after restarting into the system and setting it up, I get the same results as before (the twrp loading screen shows and reboots back to system).... so yea kind of lost now
Click to expand...
Click to collapse
Where is the recovery log from the TWRP boot where it was prompting for password? The OP clearly states that a log should be included with any issues. Do me a favor and try flashing the TWRP attached and let me know if it boots.
https://drive.google.com/file/d/1-2qBUqYv0AWnvqDmxIY2DqRqwG5dSwHg/view?usp=drivesdk
If it does, I can adjust the TWRP image linked in the OP. If it doesn't, I'll definitely need a log to understand the issue, and your device details.
So I did some testing, and it appears that if you're not on the latest .58 firmware, then TWRP may not boot successfully. Can anyone that has had an issue with booting TWRP please report their device variant and firmware version? If you're not on the latest, please update and then try TWRP.
WW 2007.58 Full Firmware: https://dlcdnets.asus.com/pub/ASUS/...US_I003_1-ASUS-17.0823.2007.58-1.1.9-user.zip
CN 2007.58 Full Firmware: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS661KS/UL-ASUS_I003_1-CN-17.0823.2007.58-1.1.45-user.zip
If that doesn't work, let me know.
EDIT: Actually I need to check again. I think I broke my TWRP tree so it may not be the kernel at all :/
Hey sorry for taking such a long time to reply, life happened to me.
I am on the latest firmware (cn_17.0823.2007.58)
I am sorry as I didn't send the recovery log, I will be testing the latest twrp you attached for me with the Google drive and let you know the results shortly :good:
Edit: the same happens with this twrp file too, it just shows the loading screen and boots to system directly, would you want me to clean flash and then do the recovery all over again with the logs?
Edit 2: by any chance would be able to get hold of the stock_recovery.img or do you know any way to flash the stock rom without recovery? FYI my version is cn_17.0823.2007.58 ,will recovery from any version work though?
Captain_Throwback said:
Well, unlocking the bootloader means you won't get an OTA from ASUS anymore, but that has nothing to do with TWRP. When a new OTA becomes available, you will be able to flash the full firmware file in TWRP, if that's what you're asking.
EDIT: Installing TWRP won't prevent you from being able to place a firmware file on the root of your storage so that the system updater will detect and install it, either. That process happens outside of recovery so flashing TWRP is unrelated to it. However note that after flashing an OTA update, TWRP will need to be flashed again, as the OTA will write stock recovery to the slot where the OTA is installed.
Click to expand...
Click to collapse
so basically installing twrp can still be overwritten when flashing original firmware from asus
.thanx sir
Monsibd said:
Hey sorry for taking such a long time to reply, life happened to me.
I am on the latest firmware (cn_17.0823.2007.58)
I am sorry as I didn't send the recovery log, I will be testing the latest twrp you attached for me with the Google drive and let you know the results shortly :good:
Edit: the same happens with this twrp file too, it just shows the loading screen and boots to system directly, would you want me to clean flash and then do the recovery all over again with the logs?
Edit 2: by any chance would be able to get hold of the stock_recovery.img or do you know any way to flash the stock rom without recovery? FYI my version is cn_17.0823.2007.58 ,will recovery from any version work though?
Click to expand...
Click to collapse
So maybe there is some difference with the CN device that's causing this issue. Everyone it's working for is running WW firmware. Not sure what's different with the CN firmware, but that's unsettling.
Since the full firmware file is available, you can just use payload dumper to get the stock recovery image.
And yes, a clean flash with logs would be great, thanks!
Monsibd said:
hey guys, i have tried to install the twrp but after installing using the powershell whenever I try to restart to recovery it just shows the twrp loading screen and restarts back to the phone, so basically I dont have any recovery anymore
Click to expand...
Click to collapse
same as you im on the latest ww firmware tencent games variant and rooted
bouyhy01 said:
same as you im on the latest ww firmware tencent games variant and rooted
Click to expand...
Click to collapse
So yours is Tencent converted to WW? I'm going to build a TWRP with the CN kernel and if that makes any difference. There must be something different with the Tencent variant that's causing the kernel panic.
Captain_Throwback said:
So yours is Tencent converted to WW? I'm going to build a TWRP with the CN kernel and if that makes any difference. There must be something different with the Tencent variant that's causing the kernel panic.
Click to expand...
Click to collapse
thank you very much captain i'll be waiting for it to test
Global/US OnePlus 9 Unbricking Guide
Tested and used on a LE2115 variant device.
YOU SHOULDN'T USE THIS GUIDE UNLESS YOU ARE ABSOLUTELY SURE YOUR PHONE IS BRICKED. PLEASE TRY POWER COMBOS FIRST! THERE ARE NO GUARANTEES, AND THIS SHOULD BE A LAST DITCH ATTEMPT BEFORE SENDING IT TO ONEPLUS (THEY WILL FIX IT FOR YOU, UNLOCKED BOOTLOADER OR NOT)
Step 1: Boot your device into EDL mode. (If it's not already), then plug it in.
If it isn't, and you're in fastboot, you can boot into it via fastboot oem edl (correct me if I'm wrong here)
Step 2: Download the MSM tool.
The proper MSM tool can be found here.
I'd recommend using Internet Download Manager to speed it up.
Unzip it using something like 7-zip into the root folder of any drive (the root folder meaning the topmost, any subdirectories may have issues).
Some AVs may flag MSM, so please make an exception (it's safe, you can ask basically anyone)
Step 3: Install the right drivers. (If they aren't installed)
The proper drivers can be found here.
Use the readme.txt file in the driver zip, it'll explain how to do everything.
Step 4: Run the "MsmDownloadTool V4.0.exe"
Set the dropdown to "Others" and click next.
{
"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"
}
Check the "Use Lite Firehose" box, and uncheck the "Sha256 check" box.
Click on "Start" once your phone is detected.
Step 5: Let it run for around 300-350 seconds (that's how long it took mine). Once it says "Completed" (if it errors, see below), congrats! You've unbricked your OnePlus 9!
Errors
If an error occurs, don't worry! See here for the potential errors and how to solve them.
Sahara Communication Failed
When this happens, try using a different cable (one included in box is best), and try a different port. If both fail, try on another computer.
Device not match image!
Okay, this one WILL take much longer than the previous one, but this is still fixable.
Download this MSM tool instead following the same guidelines as above. (I am aware it is the wrong version, however this is the only working fix to the extent of my knowledge.)
Close the old one.
Flash using the above guidelines aswell.
Once finished (you have to wait the 300 seconds), hope that it works lol.
If it does, it'll reboot into OxygenOS. Go through setup as normal (the cursed camera cutout is also normal), finish it, and then you will have to:
Set up Magisk (too many guides for it, not going to explain it here.
Flash magisk by booting into TWRP using fastboot (fastboot boot twrp-3.6.0_11-0-lemonadep.img) (install menu, then find magisk's file), then copy TWRP's image to the device and install the ramdisk via the image (should be in advanced).
Install this app.
When setting up, grant it root access, and make sure to select the Stable (Full) channel, and set your device to OnePlus 9. (NOT THE INDIA VERSION, NO MATTER WHAT IT SAYS.
Go into settings, and enable Advanced Mode (this is req'd)
Go to the main page, and click download update.
When it finishes, let it do automatic install (UNCHECK ALL BOXES OR IT WILL ERROR!)
Congrats! You fixed it!
If it doesn't work, you may have to send it off to OnePlus. They will still do repairs even on unlocked bootloaders assuming that you're in warranty.
Nice guide ! Just one question, the TWRP link is for OnePlus 9 pro, it is normal?
Other point, to be complete, you should specify how to boot in EDL mode and add fastboot commands for every operations, like flashing twrp
akboy7015 said:
Nice guide ! Just one question, the TWRP link is for OnePlus 9 pro, it is normal?
Other point, to be complete, you should specify how to boot in EDL mode and add fastboot commands for every operations, like flashing twrp
Click to expand...
Click to collapse
Yup, it's normal. I use that specific TWRP on my LE2115. I'll make the edits right away! Thanks for the suggestion!
I have a CN variant of OnePlus 9 (LE2110) running the Global version of Oxygen OS 11.2.10.10LE25AA.
I installed the latest TWRP (3.6.0_11-0-lemonade) from the TWRP website and then I rooted the phone via TWRP with Magisk v23 and everything was fine.
Today I installed a new version of the launcher which was probably buggy, and it made the phone act funny even when I rebooted the device, so I booted the phone into TWRP recovery and dirty flashed the ROM and then reflashed Magisk for root. This is how I used to do it with my 5T.
Obviously, I have done sth wrong, and now the phone boots only in fastboot mode. When I try to boot into recovery, TWRP loads with the lockscreen but it doesn’t work, you cannot do anything, whatever you press it doesn’t react.
To my understanding, I have soft-bricked the phone and need to follow your guide to unbrick it?
panoramixmeister said:
I have a CN variant of OnePlus 9 (LE2110) running the Global version of Oxygen OS 11.2.10.10LE25AA.
I installed the latest TWRP (3.6.0_11-0-lemonade) from the TWRP website and then I rooted the phone via TWRP with Magisk v23 and everything was fine.
Today I installed a new version of the launcher which was probably buggy, and it made the phone act funny even when I rebooted the device, so I booted the phone into TWRP recovery and dirty flashed the ROM and then reflashed Magisk for root. This is how I used to do it with my 5T.
Obviously, I have done sth wrong, and now the phone boots only in fastboot mode. When I try to boot into recovery, TWRP loads with the lockscreen but it doesn’t work, you cannot do anything, whatever you press it doesn’t react.
To my understanding, I have soft-bricked the phone and need to follow your guide to unbrick it?
Click to expand...
Click to collapse
This guide is for phones stuck in edl mode. This won't work on CN phones to the extent of my knowledge. If you can get into fastboot, you can try and recover via a tool. I'm not sure why twrp is doing that, but can you try booting the twrp image instead of booting the flashed one? Sorry about the late response, by the way
@winterfoxx,
thanks for this very useful guide, a curiosity, when you use the zip file linked from "OnePlus_9_Pro_India_OxygenOS_11.2.4.4", you flash the file inside the zip, "lemonadep_22_I.07_210412" which is for the Pro model? right? thanks
winterfoxx said:
This guide is for phones stuck in edl mode. This won't work on CN phones to the extent of my knowledge. If you can get into fastboot, you can try and recover via a tool. I'm not sure why twrp is doing that, but can you try booting the twrp image instead of booting the flashed one? Sorry about the late response, by the way
Click to expand...
Click to collapse
It worked perfectly for the CN variant (LE2110) that I have. The CN variant is running the Global version of OxygenOs (AA) so the only difference was that I had all three options checked (Sha256 check, Auto reboot and Use Lite Firehose).
The first few times I got the Sahara Communication Failed message but I followed your suggestion and changed USB port and cable and it worked flawlessly.
Thank you for the very helpful guide!
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
So sad , I am in the same situation!
Did you figured it out ??
from oxygen updater, I also tried to flesh the Open beta 1, but same result, the touchscreen does not respond, strange but with the rom for the pro version the touchscreen works fine, I'm looking for a way to solve but still nothing new....
iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
i had to do this with the latest a12 update broke the screen like your saying and this is the steps i had to take to fix it
Device not match image!
Okay, this one WILL take much longer than the previous one, but this is still fixable.
Download this MSM tool instead following the same guidelines as above. (I am aware it is the wrong version, however this is the only working fix to the extent of my knowledge.)
Close the old one.
Flash using the above guidelines aswell.
Once finished (you have to wait the 300 seconds), hope that it works lol.
If it does, it'll reboot into OxygenOS. Go through setup as normal (the cursed camera cutout is also normal), finish it, and then you will have to:
Set up Magisk (too many guides for it, not going to explain it here.
Boot into TWRP using fastboot (fastboot boot twrp-3.6.0_11-0-lemonadep.img
Flash 11.2.10.10 ota zip in twrp via adb sideload and reboot and you will have working screen and everything else.
at this point do not update to A12 update aka the c36 ota in settings or you will face the same issue and have to redo this process
Congrats! You fixed it!
panoramixmeister said:
It worked perfectly for the CN variant (LE2110) that I have. The CN variant is running the Global version of OxygenOs (AA) so the only difference was that I had all three options checked (Sha256 check, Auto reboot and Use Lite Firehose).
The first few times I got the Sahara Communication Failed message but I followed your suggestion and changed USB port and cable and it worked flawlessly.
Thank you for the very helpful guide!
Click to expand...
Click to collapse
Congrats! I'm glad I was able to help
iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
Erm, try factory resetting it in twrp
winterfoxx said:
Erm, try factory resetting it in twrp
Click to expand...
Click to collapse
even with twrp flashed the device is frozen in recovery same as on the main screen even for me i had todo it the way i listed above to be able to even do anything on the phone and it was the only way for it to work correctly for me
the one downside to this method that ive found is i am still unable to flash stock OP9 msm even after fixing i still get the device not match image error even after using the param from my stock msm backup files and flashing it directly to my device.
i verified before i even had this issue that my device was in fact a le2115 and backed up all partitions using msm.
i figured out the best way to flash stock global to device and not have a frozen screen if you update to a12
i can verify that you can shorten this down by a few steps also and it will still work .
At step 4 just flash global msm with step 2 options unchecked and device set as o2 and start
Although i would advise against taking the a12 update for multiple reasons
papad13 said:
So sad , I am in the same situation!
Did you figured it out ??
Click to expand...
Click to collapse
now i try to: at the step where you installed twrp, now i try to flash (adb sideload...) indian fw to downgrade from openbeta, stay tuned!!
allenjthomsen said:
i figured out the best way to flash stock global to device and not have a frozen screen if you update to a12
i can verify that you can shorten this down by a few steps also and it will still work .
At step 4 just flash global msm with step 2 options unchecked and device set as o2 and start
Although i would advise against taking the a12 update for multiple reasons
Click to expand...
Click to collapse
"a12" you talked aboit open beta? or we have official oxygen android 12? thx
iaio72 said:
now i try to: at the step where you installed twrp, now i try to flash (adb sideload...) indian fw to downgrade from openbeta, stay tuned!!
Click to expand...
Click to collapse
Can you help finding the “param bin file global”
Please ?
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