Develop Bugs

CUBOT S550 5,5 HD MT6735 1,3Ghz 2gb/16gb fingerprint 3000mAh

Tomorrow i will receive this new Cubot series with fingerprint and good specs.
{
"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"
}
Official Page:
http://www.cubot.net/Index.php/mobile/view/id/263.html

Reserved for review and modding

Cubot claim that it has a 3000mAh battery.
Battery mAh measured to 2795 here http://peecee.dk/uploads/012016/20160123_204834.jpg
Geekbench 3 battery test: http://browser.primatelabs.com/battery3/197467 (09:35:40 / 3589)

thanks S7yler , not bad, also battery test seems to be very good!
I wait if from EFOX, and i hope to have mine today or tomorrow!

Just Arrived.. .white color in my sample!
first challenge was to create TWRP .. successfull!
http://www.needrom.com/download/twrp-2-8-7-3-material-play-megthebest/
Archive contain Boot Unlocked and TWRP Material Play ported by me!
Tested successfully with V06 January 2016 rom.
1- Download and Install correctly Mediatek Preloader drivers
( Take care on Windows 8.1/10 drivers, you need to disable driver signature before install
https://www.youtube.com/watch?v=50pD0mONm44
http://laurentiumihet.ro/technology...-for-32-64-bit-drivers-installation-tutorial/
https://thebroodle.com/microsoft/windows/install-mediatek-mt65xx-usb-vcom-drivers-windows-8-8-1/
2- enter Engineering Mode MTK with Dialer code *#*#3646633#*#*, go into log and debugging, tap on user2root and tap on ROOT, shut down smartphone.
3- With flashtool load MT6735_Android_Scatter-Play.txt
4- Select download and connect smartphone to pc (smartphone must be powered off)… in few seconds will start the process and the new TWRP will be flashed.
3.1- To restore original stock recovery, you need load ad point 3 the file MT6735_Android_Scatter.txt
P.P.S to enter in the recovery, power off the smartphone, push VOL + and Power at the same time, you will see three words with VOL + you move selection, with VOL – you must select Recovery
To have root flash with TWRP the archive supersu.zip found here: https://download.chainfire.eu/696/supersu/

Unboxing & Review (Italian language) :

any custom roms for that phone ?

megthebest said:
Just Arrived.. .white color in my sample!
first challenge was to create TWRP .. successfull!
Archive contain Boot Unlocked and TWRP Material Play ported by me!
Tested successfully with V06 January 2016 rom.
Click to expand...
Click to collapse
This is great work. Have you got a version of this that works with the latest firmware? I upgraded my firmware to the June v10 firmware and when I put this version on it just boot loops the phone.
Thanks.

So no chance of an updated TWRP then megthebest?

I updated the TWRP myself and put it on needrom, for anyone who wants to use TWRP with the latest official ROM. I tested it on my phone and it works I used it to root the phone and install xposed framework.
All credit to megthebest, it is his work.
http://www.needrom.com/download/twrp-2-8-7-3-material-play-megthebest-3/

Thanks Famineuk! Can I update to the new version directly from twrp recovery or do I have to use the flashtool again?

I did it using the flash tool. I never tried it directly through TWRP. I think you could try it then if it didn't work you would still be able to flash it through the flash tool.

Famineuk said:
This is great work. Have you got a version of this that works with the latest firmware? I upgraded my firmware to the June v10 firmware and when I put this version on it just boot loops the phone.
Thanks.
Click to expand...
Click to collapse
Where did you get the v10 ?
i got v9 OTA, but no v10
have you used the one from needrom ? i see no other source.

Root is possible with KingoRoot (NOT Kingroot)

johnfdoe said:
Where did you get the v10 ?
i got v9 OTA, but no v10
have you used the one from needrom ? i see no other source.
Click to expand...
Click to collapse
This is a link to version 10
http://www.needrom.com/download/cubot-s550/

Will an update using the flash tool erase the internal memory of my phone(titanium backup, photos, etc)? Can I update to V10 using TWRP recovery or do I have to use the flash tool again?

baggos12 said:
Will an update using the flash tool erase the internal memory of my phone(titanium backup, photos, etc)? Can I update to V10 using TWRP recovery or do I have to use the flash tool again?
Click to expand...
Click to collapse
Only Flashtool to upgrade.
You may try to maintain Data if in flashtool you will deselect Userdata partition before start flashing (and Recovery partition if you want to maintain TWRP).
You loose root and it will be not guaranteed that with new v10 rom TWRP will work again (possible change in kernel)

megthebest said:
Only Flashtool to upgrade.
You may try to maintain Data if in flashtool you will deselect Userdata partition before start flashing (and Recovery partition if you want to maintain TWRP).
You loose root and it will be not guaranteed that with new v10 rom TWRP will work again (possible change in kernel)
Click to expand...
Click to collapse
you have twrp for s550

[TWRP][3.1.1][UNOFFICIAL]Moto G4/G4 Plus[Athene]

TWRP 3.1.1 Moto G4/G4 Plus (athene)​
{
"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"
}
TWRP changelog : Here
Working/Bugs : Lemme knoe if anything broken
Please do read the installation guide note !
IMPORTANT NOTE :
1. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
2. Encryption is enabled by default
3. If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide :
1. Make sure you have unlocked bootloader
2. Reboot to bootloader
3. fastboot flash recovery twrp-xxxx.img (if you want permanent flash) or
fastboot boot twrp-xxxx.img (if you want temporary boot)
Download Link :twrp-3.1.1-0-O1-athene
Tree : Here
XDA:DevDB Information
twrp-athene, Tool/Utility for the Moto G4 Plus
Contributors
rahulsnair
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2017-10-07
Last Updated 2017-10-06

is this the recommended twrp for flashing O builds?

blowingoff said:
is this the recommended twrp for flashing O builds?
Click to expand...
Click to collapse
You can use it for N or O. No issues.

It says encryption is enabled!
Does that mean the problem where in the custom recovery couldn't mount anything when the device was encrypted, is solved with this??
Earlier I did need to do a factory reset from the stock recovery and then do anything on TWRP.

abhi212b said:
It says encryption is enabled!
Does that mean the problem where in the custom recovery couldn't mount anything when the device was encrypted, is solved with this??
Earlier I did need to do a factory reset from the stock recovery and then do anything on TWRP.
Click to expand...
Click to collapse
Oreo roms always says Encrypted but I've never noticed true encryption.

HueyT said:
Oreo roms always says Encrypted but I've never noticed true encryption.
Click to expand...
Click to collapse
No not this one! I am talking about the situation when i encrypt the phone! Once the phone is encrypted the custom recovery fails to read /data.. which leads to no flashing or anything else, until i factory reset the device via stock recovery!
I will try it out anyway!

Thanks brother! I can confirm it works perfectly on device protected with encryption !!

Sorry i couldn't understand the first important note. Will i lose data if i allow system modifications? As far as i remembered this option also shows on previous versions and ive always given permission to modify. Is this the same?

u_knw_who said:
Sorry i couldn't understand the first important note. Will i lose data if i allow system modifications? As far as i remembered this option also shows on previous versions and ive always given permission to modify. Is this the same?
Click to expand...
Click to collapse
Unless you do anything to system (for eg :wipe) allowing system modifications will not harm.

abhi212b said:
It says encryption is enabled!
Does that mean the problem where in the custom recovery couldn't mount anything when the device was encrypted, is solved with this??
Earlier I did need to do a factory reset from the stock recovery and then do anything on TWRP.
Click to expand...
Click to collapse
Yes.

rahulsnair said:
Yes.
Click to expand...
Click to collapse
Got it! Tried it yesterday! Thanks!

No offense, but there's already an official 3.1.1 version of TWRP out there... https://dl.twrp.me/athene

Shahbaz_23 said:
No offense, but there's already an official 3.1.1 version of TWRP out there... https://dl.twrp.me/athene
Click to expand...
Click to collapse
The official version can't use some Motorola configurations because their politics. TWRP unofficial can use that configurations, allowing to decrypt and encrypt /data. In summary, unofficial is better.

I think I can't format /data with F2FS. The option doesn't appear in TWRP.

Magisk v22

So I have installed new magisk app and I cannot install magisk via recovery. I read magisk installation guide as far as I understand I should patch my recovery image. The problem is my custom rom doesn't have recovery image in it can I use my stock rom's image?
Edit:
Finally solved. Just renamed magisk.apk to zip and flashed it with good old recovery method.

Did you read the guide properly?
Patch the boot image file using the app and then flash the magisk patched boot image using fastboot.
Good luck

VD171 said:
Did you read the guide properly?
Patch the boot image file using the app and then flash the magisk patched boot image using fastboot.
Good luck
Click to expand...
Click to collapse
Yes I read it properly I don't have ramdisk so I should flash recovery correct me if I am mistaken

KenanT. said:
Yes I read it properly I don't have ramdisk so I should flash recovery correct me if I am mistaken
Click to expand...
Click to collapse
Why do you not have ramdisk?

VD171 said:
Why do you not have ramdisk?
Click to expand...
Click to collapse
Ummm, I don't know is there a way to activate it or install?

What is your device?

VD171 said:
What is your device?
Click to expand...
Click to collapse
İt is redmi note 8

Redmi note 8 has ramdisk.

VD171 said:
Redmi note 8 has ramdisk.
Click to expand...
Click to collapse
{
"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"
}

Magisk app says I don't have Ramdisk.
Installing Magisk 22 from recovery (OrangeFox 11.0.1) via the rename/flash method results in a bootloop to recovery.
Even when I uninstall Magisk (by renaming the zip to uninstall.zip) I can't boot anymore and I have to reflash rom.
I'm on Redmi Note 8T (willow) with official MIUI global 12.0.2.

MichaelMay said:
Magisk app recognises that you don't need a ramdisk patch and doesn't employ it.
What ROM and what build are you using? Also, what build of the recovery.
Click to expand...
Click to collapse
Both are latest stable versions for my device (Redmi 8T/Willow):
ROM: miui_WILLOWEEAGlobal_V12.0.2.0.QCXEUXM
OrangeFox: 11.0_1

mrror said:
Magisk app says I don't have Ramdisk.
Installing Magisk 22 from recovery (OrangeFox 11.0.1) via the rename/flash method results in a bootloop to recovery.
Even when I uninstall Magisk (by renaming the zip to uninstall.zip) I can't boot anymore and I have to reflash rom.
I'm on Redmi Note 8T (willow) with official MIUI global 12.0.2.
Click to expand...
Click to collapse
Try flashing older Magisk v21.4 first via recovery, that worked for me. Then update it to latest version via the Manager app. For some reason, Magisk v22 is failing on a lot of devices running MIUI 12.
Also, with the manual method, you should patch boot.img not recovery.img. Xiaomi is an exception to NO ramdisk installation method.

I had to tinker a bit more (first time it would still boot to recovery, I had to reflash rom) but I ended up having Magisk 22 installed. Thanks for pointing me to the right direction!

KenanT. said:
So I have installed new magisk app and I cannot install magisk via recovery. I read magisk installation guide as far as I understand I should patch my recovery image. The problem is my custom rom doesn't have recovery image in it can I use my stock rom's image?
Edit:
Finally solved. Just renamed magisk.apk to zip and flashed it with good old recovery method.
Click to expand...
Click to collapse
try format data when you get bootloop

Question Lost root after system update

Hi. So I rooted my OnePlus9 Pro after I bought it. But few days ago I updated it to Oxygen OS 11,2,3,3,LE15BA
And now I lost my root.
Can someone please tell me what I need to do to regain root access?

You need to install latest Magisk app, get a copy of the latest stock boot.img for your build, patch it and then flash in fastboot. See the Magisk General forum with any questions. https://forum.xda-developers.com/posts/84854149

So I went to this topic https://forum.xda-developers.com/t/magisk-patched-boot-images-for-all-builds.4262015/
Downloaded this
192 MB folder on MEGA
4 files
mega.nz
Which one of those 4 files I need to patch via Magisk and which one do I need to flash via Fastboot?

Tokic said:
So I went to this topic https://forum.xda-developers.com/t/magisk-patched-boot-images-for-all-builds.4262015/
Downloaded this
192 MB folder on MEGA
4 files
mega.nz
Which one of those 4 files I need to patch via Magisk and which one do I need to flash via Fastboot?
Click to expand...
Click to collapse
The first boot.img is stock, the second one is "patched" with Magisk, the last 2 are just hash values used to compare what the value is supposed to compared to what you download to ensure the integrity of the download. So the short answer is if you want root, the second one, "patched" img

Tokic said:
So I went to this topic https://forum.xda-developers.com/t/magisk-patched-boot-images-for-all-builds.4262015/
Downloaded this
192 MB folder on MEGA
4 files
mega.nz
Which one of those 4 files I need to patch via Magisk and which one do I need to flash via Fastboot?
Click to expand...
Click to collapse
The second one that has patched in the filename. You will...
Fastboot boot magisk_patched.img and after boot open magisk and direct install.

If you already rooted, it will be the same process.

First, you need to read a bit more before doing stuff like Rooting, updating when rooted,...
Everything is explained here. Just need to to do a bit of digging so you can confidently do stuff. And when in doubt, ask before doing.
The first sticky thread has all the info you need.
To update when rooted, do THIS. Works perfect.

Tokic said:
Hi. So I rooted my OnePlus9 Pro after I bought it. But few days ago I updated it to Oxygen OS 11,2,3,3,LE15BA
And now I lost my root.
Can someone please tell me what I need to do to regain root access?
Click to expand...
Click to collapse
Follow the directions above, the next time you update the rom, ensure you install the update but do not reboot the phone, then go into Magisk and choose "Install to Inactive Slot (After OTA)", that way your newly updated rom should boot with root already applied. Magisk will then ask to reboot and should do so into the new version.

Thx everyone for the help, managed to do it

Have another problem. Lost my root after I restarted my mobile phone. Anyone knows why?

So I flashed magisk pacthed img in bootloader. After that I need to open Magisk and direct install that same magisk patched img?

Have you read the link I provided?
If yes, and you've done exactly like described, then impossible to loose root.
So, question: what steps have you done?

Tokic said:
So I flashed magisk pacthed img in bootloader. After that I need to open Magisk and direct install that same magisk patched img?
Click to expand...
Click to collapse
I hope you "fastboot boot magisk_patched.img" then once booted open Magisk and "Direct Install". You will now be rooted again.

Bunecarera said:
Have you read the link I provided?
If yes, and you've done exactly like described, then impossible to loose root.
So, question: what steps have you done?
Click to expand...
Click to collapse
Except it is guaranteed to root lose with the last few updates in Magisk. There is no "Install to inactive slot(After OTA). Lol

schmeggy929 said:
Except it is guaranteed to root lose with the last few updates in Magisk. There is no "Install to inactive slot(After OTA). Lol
Click to expand...
Click to collapse
Strange...
I'm on v22.1 and still have the option...

Which version are you using?
I use 22.1 and the option is still there...
{
"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"
}

Latest Canary Build. Also tried stable and beta. It is weird some people still have that option and some don't.

V350AWM30e ATT_US stock & rooted partitions

V350AWM30e.zip (3.7GB)
I pulled the stock unmodified slot partitions from a fully updated AT&T V35.
I modified them with Magisk and TWRP, and disabled Dm-Verity and ForceEncrypt
I flashed them to another V35AWM that had previously been crossflashed with V350ULM 20f.
Now I stock rooted Android 10 working nicely on my main driver.
I can think of several ways to flash the partitions:
• Using ADB in TWRP (what I did)
• Using ADP from a running rooted system
• One by one with QFIL
The archive includes the unmodified partions, the modified partitions, the packages that I used to modify the partions, some notes, and a script that I used to flash them in TWRP.
If I were doing it again from the start, I would not cross flash, because there are differences in the partition tables. Despite what the guides say, I think that the bootloader can be unlocked from Android 9 or 10, using QFIL. I think that this would work: enable bootloader unlock in developer settings,, flash the engineering bootloader with QFIL, wipe laf, unlock with fastboot, flash the modified boot.img with QFIL, boot into recovery, flash the other partitions from there.
These files are for developers only. You can easily brick your phone and I won't help.

Thank you for this!

amazing
let's hope something useful comes to the end user

Thanks so much for putting this together. Should I anticipate any issues doing TWRP ADB sideload coming from a Korean rom?

Hi! Yesterday I tried to download from the link, but the following error popped up on Mac OS. On Windows, the link just doesn't open. In short, it just can't download...
{
"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"
}

smir_ant said:
Hi! Yesterday I tried to download from the link, but the following error popped up on Mac OS. On Windows, the link just doesn't open. In short, it just can't download...
Click to expand...
Click to collapse
I can download it on windows, it's just extremely slow at 0.5 Mb/s

ghylander said:
I can download it on windows, it's just extremely slow at 0.5 Mb/s
Click to expand...
Click to collapse
yeap, from sative safari (without addblock and another addons) i download too, slow, but success,
thanks for reply

jacob019 said:
V350AWM30e.zip (3.7GB)
I pulled the stock unmodified slot partitions from a fully updated AT&T V35.
I modified them with Magisk and TWRP, and disabled Dm-Verity and ForceEncrypt
I flashed them to another V35AWM that had previously been crossflashed with V350ULM 20f.
Now I stock rooted Android 10 working nicely on my main driver.
I can think of several ways to flash the partitions:
• Using ADB in TWRP (what I did)
• Using ADP from a running rooted system
• One by one with QFIL
The archive includes the unmodified partions, the modified partitions, the packages that I used to modify the partions, some notes, and a script that I used to flash them in TWRP.
If I were doing it again from the start, I would not cross flash, because there are differences in the partition tables. Despite what the guides say, I think that the bootloader can be unlocked from Android 9 or 10, using QFIL. I think that this would work: enable bootloader unlock in developer settings,, flash the engineering bootloader with QFIL, wipe laf, unlock with fastboot, flash the modified boot.img with QFIL, boot into recovery, flash the other partitions from there.
These files are for developers only. You can easily brick your phone and I won't help.
Click to expand...
Click to collapse
Could you reporst the download? I just installed windows 11, so maybe that's the issue, but I keep getting "v350awm30e.zip cannot be downloaded securely." and it refuses to even start the download. Any help would be appreciated.

Working fine for me. Try using https instead of http:
https://jacobstoner.com/V350AWM30e.zip

jacob019 said:
Working fine for me. Try using https instead of http:
https://jacobstoner.com/V350AWM30e.zip
Click to expand...
Click to collapse
Thanks for the fast reply here and in a DM. For anyone new to windows 11 like me, if you try to download from any website that doesn't have that S in it (http vs https), it will not let you download. After a quick google, you can still download from places like this by right-clicking on the download and selecting "keep this".
You can also click on the lock icon in the url bar and then going to permissions and selecting the option to download unsecure content from this website.
Cheers.

Hi everyone. Do you know where can I download a stock ATT firmware for lg v35? Mine is network locked and I have the code to unlock it but I have to be on original firmware. Please help me if you can. Thanks