Hi,
So long i've dont active my account on XDA Developers because my studies. Finally i've found to update Oukitel K9 by using Treble 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"
}
Video Review : https://youtu.be/EMbBpCc0R-Y
Please make sure you have download Generic GSI from Google and already unlocked bootloader.
Here the link ( Download Generic GSI )
Choose ARM64+GMS / ARM64, if you want to flash android Q treble rom, just download Android Q only.
Let's start it.
1. Flash to stock firmware using MTK Tools
2. Extract vbmeta.img from Generic GSI.
3. Connect to usb to device (enter fastboot mode) hold volume up and power button, choose fastboot mode.
4. Type this and make sure using generic vbmeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. Next erase file system
Code:
fastboot erase system
6. a) Flash file system
Code:
fastboot flash system ######.img
# = your file system name
or
6. b) Using TWRP > Flash> Click image> find img to flash> Select system>then swipe to flash
7.
Code:
fastboot -w
8.
Code:
fastboot reboot
PLEASE TAKE NOTE OUKITEL K9 IS A/B DEVICES
Test
Working GSI:
system-quack-arm64-ab-gapps.img.xz
Evolution X , Lineage 17.1 - All Working
Havoc 3.3 - RIL bugs, no simcard detect
All GSI Rom list you can find here : Phhusson GSI
Thanks @Levered
I've flashed stock Android 9 using SP Flash Tool, is that what you're talking about when you say 'MTK Tools'?
Step #3 - My PC doesn't recognize my device. (see #2 below)
A few other questions:
1) What build number are you coming from? I'm on OUKITEL_K9_V21_20190524
From what I've read there was some sort of 'lock' put in place at around that time so that only certain firmware could be flashed.
2) Fastboot? on a MTK device? I thought that was impossible too, even though it canbe put in to Fastboot mode by holding Vol+&PWR. I'm new to MTK devices so am very much a newb.
3) The link you provided correct? It takes me to the page for Android 11 GSI's, but the video shows Android 10
4) At bottom you have generic GSI linked—which one to flash, the one linked at top or bottom?
Also, perhaps worth mentioning, I've successfully temporary-rooted using this method from @diplomatic
https://forum.xda-developers.com/an...ing-temp-root-mediatek-armv8-t3922213/page101
Thanks again
TiTiB said:
Thanks @Levered
I've flashed stock Android 9 using SP Flash Tool, is that what you're talking about when you say 'MTK Tools'?
Step #3 - My PC doesn't recognize my device. (see #2 below)
A few other questions:
1) What build number are you coming from? I'm on OUKITEL_K9_V21_20190524
From what I've read there was some sort of 'lock' put in place at around that time so that only certain firmware could be flashed.
2) Fastboot? on a MTK device? I thought that was impossible too, even though it canbe put in to Fastboot mode by holding Vol+&PWR. I'm new to MTK devices so am very much a newb.
3) The link you provided correct? It takes me to the page for Android 11 GSI's, but the video shows Android 10
4) At bottom you have generic GSI linked—which one to flash, the one linked at top or bottom?
Also, perhaps worth mentioning, I've successfully temporary-rooted using this method from @diplomatic
https://forum.xda-developers.com/an...ing-temp-root-mediatek-armv8-t3922213/page101
Thanks again
Click to expand...
Click to collapse
Sorry for this.
Use fastboot mode on windows. You can find this on others thread using cmd.
I suggest you flash img using twrp for more faster.
3) Yes, i will check later.
4) All linked has work on our devices. I will update what rom has worked.
thanks
Levered said:
Sorry for this.
Use fastboot mode on windows. You can find this on others thread using cmd.
I suggest you flash img using twrp for more faster.
3) Yes, i will check later.
4) All linked has work on our devices. I will update what rom has worked.
thanks
Click to expand...
Click to collapse
Thanks for the reply, but the question remains,
Which firmware version did you start with?
I believe the bootloader is locked on my device, no fastboot.
TiTiB said:
Thanks for the reply, but the question remains,
Which firmware version did you start with?
I believe the bootloader is locked on my device, no fastboot.
Click to expand...
Click to collapse
Pixel experience, havoc 3.3, lineage 17.1 and EvolutionX
Please unlocked your bootloader, if that. Your device will get brick.
Levered said:
Pixel experience, havoc 3.3, lineage 17.1 and EvolutionX
Please unlocked your bootloader, if that. Your device will get brick.
Click to expand...
Click to collapse
nvm, you are obviously not going to share useful information
1) build# you were able to root
2) what you mean by 'MTK Tools'
3) and other important stuff
Additional information I have discovered
The vbmeta generic file is needed http://www.mediafire.com/file/lpdpocvn76n7cyo/vbmeta.img/file
The rom is https://www.mediafire.com/file/i9jo...20200413-UNOFFICIAL-treble_arm64_bvN.img/file
The Trebel test app stated the my Oukitel k9 was A only I found out it is A/B this rom works.
Also after flashing Lineage 17 there is not enough space for Gapps. Solution after flash reboot recovery again go to wipe select system select repair then adjust size of partition. Then reboot to recovery again then flash Gapps. I have successfully flashed Gapps stock and works great. Note I flashed Magisk last. So far this GSI works great, better than the phones original. Xposed works! Gravity box beta 6 works. Apps now auto start properly.
Thank you.
Thanks
hello, my name is bausette i'm italian, i'm sorry for my bad English i hope you cand understand me. First of all
thanks for your work, that's amazing my Oukitel k9 has new life :fingers-crossed::victory:, that's amazing Everything work better, than Stock Rom.
Can i Ask you some question please? i had Flash Vmeda generic files, Open Gapp, Orange State fix message, Lineage Rom project Treble, TWRP recovery, but i think i forgot something, because after install Magisk it say that the device is not Rooted, please can you tell my step by step Guide to Root the phone? thanks so much
Levered said:
PLEASE TAKE NOTE OUKITEL K9 IS A/B DEVICES
Click to expand...
Click to collapse
My Oukitel K9 is A-Only partition when I use Treble checker. Every guide seems to reference A/B for the Oukitel K9. Mine is not or at least it is being reported incorrectly.
How do I update to a custom rom when I have only A-Partition? The stock image is so buggy it's almost unusable.
Thanks!
Lannie
lschafroth2 said:
My Oukitel K9 is A-Only partition when I use Treble checker. Every guide seems to reference A/B for the Oukitel K9. Mine is not or at least it is being reported incorrectly.
How do I update to a custom rom when I have only A-Partition? The stock image is so buggy it's almost unusable.
Thanks!
Lannie
Click to expand...
Click to collapse
You can try A partition images.
Levered said:
You can try A partition images.
Click to expand...
Click to collapse
Is the process any different? I found the following list of files:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
It shows Treble A only image as an option. Mine supports Treble but not seamless updates due to the A-only partition.
Will the image listed above work with the normal guides? Do I need the vbmeta.img for the Oukitel K9?
I'm very new to this so I'm afraid to mess it up.
Lannie
lschafroth2 said:
Is the process any different? I found the following list of files:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
It shows Treble A only image as an option. Mine supports Treble but not seamless updates due to the A-only partition.
Will the image listed above work with the normal guides? Do I need the vbmeta.img for the Oukitel K9?
I'm very new to this so I'm afraid to mess it up.
Lannie
Click to expand...
Click to collapse
you can try both, but i think our k9 is A/B partition.
yes you need vbmeta.img
follow this guide:
https://forum.xda-developers.com/mi-9-se/how-to/guide-how-to-flash-twrp-gsi-roms-mi-9-se-t3939254
Levered said:
you can try both, but i think our k9 is A/B partition.
yes you need vbmeta.img
follow this guide:
https://forum.xda-developers.com/mi-9-se/how-to/guide-how-to-flash-twrp-gsi-roms-mi-9-se-t3939254
Click to expand...
Click to collapse
I have tried 4 different Treble checking apps and they all say Treble supported but seamless updates not supported because A-only partition exists.
This is a Oukitel K9 OUKITEL_K9_V21_20190524
Wonder why everyone else seems to have A/B and I only have A.
Lannie
---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------
nation888888 said:
The vbmeta generic file is needed http://www.mediafire.com/file/lpdpocvn76n7cyo/vbmeta.img/file
The rom is https://www.mediafire.com/file/i9jo...20200413-UNOFFICIAL-treble_arm64_bvN.img/file
The Trebel test app stated the my Oukitel k9 was A only I found out it is A/B this rom works.
Also after flashing Lineage 17 there is not enough space for Gapps. Solution after flash reboot recovery again go to wipe select system select repair then adjust size of partition. Then reboot to recovery again then flash Gapps. I have successfully flashed Gapps stock and works great. Note I flashed Magisk last. So far this GSI works great, better than the phones original. Xposed works! Gravity box beta 6 works. Apps now auto start properly.
Thank you.
Click to expand...
Click to collapse
How do you verify you are A/B? Mine says A only on 4 different treble apps. Is there a way to verify for sure? I have a Oukitel K9.
Lannie
lschafroth2 said:
I have tried 4 different Treble checking apps and they all say Treble supported but seamless updates not supported because A-only partition exists.
This is a Oukitel K9 OUKITEL_K9_V21_20190524
Wonder why everyone else seems to have A/B and I only have A.
Lannie
Click to expand...
Click to collapse
You can try it first both partition. If not boot, try another partition. :fingers-crossed:
Everything seems to work except hotspot
The no verity, Lineage rom a/b, vbmeta, resizing system partition size, installing stock gapps all works making this one of the nicest roms I have worked with. The only issue I find so far I cannot get the mobile Hotspot to stay on. Mobile Hotspot works in safe mode. I did a fresh install and does the same. Modded buildprop, no results. Installed module tether enabler, no results.
Mobile Hotspot switches off right away. Any ideas?
---------- Post added at 06:01 AM ---------- Previous post was at 05:57 AM ----------
It is this one a/b I have not seen any other variants. Both Global and Chinese have same partition setup. Yes I have tried a only and doesn't boot.
How do I check? I've tried the ADB SHELL commands and it returns an empty line. The article said it would show TRUE if it did. All it returns is an empty line. I have yet to find any app that shows my Oukitel K9 is A/B. All of them say it is not.
lschafroth2 said:
How do I check? I've tried the ADB SHELL commands and it returns an empty line. The article said it would show TRUE if it did. All it returns is an empty line. I have yet to find any app that shows my Oukitel K9 is A/B. All of them say it is not.
Click to expand...
Click to collapse
If recovering to stock is easy, I guess I can dive in and try the A/B image and see if it works.
Lannie
use the lineage ab... it is ab. Make sure to do the no verity first with vbmeta line. Then flash lineage ab the file is not clear it states b. I tried them all see my post for direct download.
Same result
lschafroth2 said:
How do I check? I've tried the ADB SHELL commands and it returns an empty line. The article said it would show TRUE if it did. All it returns is an empty line. I have yet to find any app that shows my Oukitel K9 is A/B. All of them say it is not.
Click to expand...
Click to collapse
I have same firmware, K9 OUKITEL_K9_V21_20190524, and same results for Treble check (see screenshots for info).
Also, device not recognized using fastboot.
Code:
adb devices
OUKITELK90007961
Code:
adb reboot bootloader
success; 'FASTBOOT mode. . .' on phone
Code:
fastboot devices
blank line
From what I understand, this is because our devices' bootloaders are locked; and there is nothing we can do to change that, period. So, no flashing anything but stock. I hope I'm wrong, and someone more knowledgeable corrects me, but I'm pretty sure this is correct.
For now I'm just stuck, and using temporary root as mentioned in previous post.
Related
DISCLAIMER: all operations descripted here should be done *only* by trained & expert guys... as every "hacking" operations, they involve the risk of soft/hard bricking your device making it unusable temporary or permanently. I will not be responsable in any way for it. So, pay attention and, if not sure, simply don't do it.
WARNING #1: this is a fast guide describing needed steps and providing needed files only for expert guys. It is *not*suitable* for newbies who need detailed instructions on how to install drivers, programs, flash partitions, etc...
WARNING #2: on this phone there are (strangely...) close ties between boot.img and recovery.img content. This involves that changing contents of recovery.img can produce bootloop and changing contents of boot.img can prevent to access recovery too, creating a soft brick condition. I don't know exactly why, BUT you are warned.
WARNING #3: the procedure and files provided are *only* for ROM1 firmware version 14 of 13 Aug 2016. It is indicated as OUKITEL_C4_V14.0_20160813 in "About phone" and as t637d-oq-s08-fdd3m-hd-64g8g-sd internally. If you are on a differently indicated version and/or release date, *don't*even*think* about trying to apply the provided files: bootloops and (at least) soft bricks are easy coming, expecially because of warning #2...
WARNING #4: all provided files are in .zip format only due to forum rules and limitations. They *all* need to be *unpacked* before use them.
CREDITS: this TWRP recovery has been compiled by Jemmini on 4PDA forum. Since of the Russian only language of that forum and the very hard way to subscribe on it for not Russians (needed to download files too...), I'm reporting it here with more explanations and my hints & experiences too...
Said that... Let's start! :highfive:
IF (and *only* if...) your firmware version is reported as OUKITEL_C4_V14.0_20160813 in your phone, these are the steps to follow:
- unlock your bootloader (no special code needed, just enable the apposite option slider in Developers section of Settings and unlock it by the standard fastboot command in fastload mode... you need adb, fastboot and adb/fastboot drivers installed in your pc obviously )
Please remember that, as ever, unlocking your bootloader will factory reset your phone (and void your warranty...), so take it in proper account....
- using SP Flash Tool (recent versions since of the new MT6737 used in C4... tested one is the v.5.1644, just Google for it) just flash the provided twrp-c4.img (by Jemmini on 4PDA) selecting "Download only" on top, using the provided scatter file and selecting only the recovery row (browsing to twrp-c4.img file). Then press Download button and connect your phone in OFF status. If all was OK and you have MTK drivers properly installed (Google for them... search for MT6737 drivers. To test them just try to connect your phone to PC as storage to check if it is properly seen...), you should see a green checking sign "v" on top of SP Flash tool.
If nothing happens, try to reinstall drivers and/or doublecheck your phone is in OFF status when connected.
- don't try to boot to system now. It simply doesn't anyway.
For some unknown reason connected to warning #2, flashing twrp introduces a bootloop (soft brick...) on this phone.
Nothing to be worried of anyway: systemless rooting will fix it!
To root simply flash by TWRP (yes, you need to enable /system modification on first twrp boot...) SuperSU v.2.78 "standard" version in zip format (just Google for it...).
For standard is intended the released one, not SRx or "forced to system" one... (tested version is SuperSU-v2.78-201609011115.zip) .
Just remember that, since of unability to boot system before flashing SuperSU, its zip have to be already on your device before flashing TWRP. Otherwise you can use a microSD card to flash from it...
If you do all fine you now have your rooted & TWRP 3.0.2-x provided Oukitel C4!!! :highfive:
If you are in a bootloop condition you aren't able to fix, just turn off your phone and, ever using SP Flash Tool in the same way, simply reflashing stock boot.img and recovery.img (both provided as zipped-to-to-be-unzipped attachment for... emergency reasons ).
After, if you want, you can install Xposed (in system mode) or busybox by app (it will be automatically installed in systemless mode since of supersu installation method...).
Don't even try to install Magisk v.9 instead: it will not work and will produce a soft brick (with no recovery access too...) that will requires a boot.img and recovery.img reflashing to be solved (with all this procedure to be redone one more time...).
This said... if you have questions... I'm here to answer them. Otherwise... have a nice time with your TWRP provided and systemless Rooted Oukitel C4!!! :fingers-crossed:
Reserved. :silly:
Can you please provide the 4PDA forum link of TWRP for this phone? Thanks for your post anyways
[email protected] said:
Can you please provide the 4PDA forum link of TWRP for this phone? Thanks for your post anyways
Click to expand...
Click to collapse
Added in OP. Don't expect to find more anyway...
I can confirm that this TWRP build also works fine with the newest OUKITEL_C4_V17.0_20161124 Firmware. Important: before flashing TWRP disable your boot lock code, otherwise you will softbrick your device.
Entec do you have an 4pda Account? If yes it would be really awesome if you could add the second TWRP recovery image for oukitel phones with the Rxx_xxxx ROM to OP.
EDIT:
I successfully installed XPOSED on my C4! This rocks the **** out of an 50 EUR budget phone!
Hello thank you for your information, could you provide us also TWRP for 32bits version (R06), I have tried to download from de forum but file is not avalaible.
regards
salvarez01 said:
Hello thank you for your information, could you provide us also TWRP for 32bits version (R06), I have tried to download from de forum but file is not avalaible.
regards
Click to expand...
Click to collapse
We need someone with 4PDA Account....
However, have you tried to install the 64Bit rom? You can get the Stock 64 Bit Rom from needrom.com. I advise you to do the software update before flashing TWRP linked in this thread.
[email protected] said:
We need someone with 4PDA Account....
However, have you tried to install the 64Bit rom? You can get the Stock 64 Bit Rom from needrom.com. I advise you to do the software update before flashing TWRP linked in this thread.
Click to expand...
Click to collapse
Hello thank you I have flashed 64 bits Rom and updated to V17, now all OK with TWRP and SuperSU.
Seam 64 bits version more slow than R06, but OK.
Thanks.
Hello I have tried to use native sip editing the files in /system/etc/permissions but the option is not available in phone menu. Someone know how to activate?
Enviado desde mi Redmi Note 4 mediante Tapatalk
[email protected] said:
Entec do you have an 4pda Account? If yes it would be really awesome if you could add the second TWRP recovery image for oukitel phones with the Rxx_xxxx ROM to OP.
Click to expand...
Click to collapse
[email protected] said:
We need someone with 4PDA Account....
However, have you tried to install the 64Bit rom? You can get the Stock 64 Bit Rom from needrom.com. I advise you to do the software update before flashing TWRP linked in this thread.
Click to expand...
Click to collapse
I managed to create an account on 4pda.ru and downloaded twrp for all firmware versions!
Files are attached!
Use twrp_recovery_C4_V.zip if your phone uses the OUKITEL_C4_VXX.X_XXXXXXXX firmware (Tested with OUKITEL_C4_V17.0_20161124)
Use twrp_recovery_R0x.zip if your phone uses the R0X_XXXXXX firmware. (Tested with R06_102033)
Where is OUKITEL_C4_V17.0_20161124 firm now?
I can't find it at needrom.com.
pop003 said:
Where is OUKITEL_C4_V17.0_20161124 firm now?
I can't find it at needrom.com.
Click to expand...
Click to collapse
Which rom do you have on your device?
Now I have R06_102033 on my C4
pop003 said:
Now I have R06_102033 on my C4
Click to expand...
Click to collapse
No problem, just use the twrp_recovery_R0x.zip from my previous post.
https://forum.xda-developers.com/showpost.php?p=71584701&postcount=10
[email protected] said:
No problem, just use the twrp_recovery_R0x.zip from my previous post.
https://forum.xda-developers.com/showpost.php?p=71584701&postcount=10
(do not forget to give it a like)
Click to expand...
Click to collapse
Thank you. twrp_recovery_R0x installed successfully.
However, in my environment, I needed the latest version of SP_Flash_Tool_v 5.1712_Win.
With other versions of sp_flash_tool, I did not succeed any number of times.
pop003 said:
Thank you. twrp_recovery_R0x installed successfully.
However, in my environment, I needed the latest version of SP_Flash_Tool_v 5.1712_Win.
With other versions of sp_flash_tool, I did not succeed any number of times.
Click to expand...
Click to collapse
Glad to hear it worked!
salvarez01 said:
Hello I have tried to use native sip editing the files in /system/etc/permissions but the option is not available in phone menu. Someone know how to activate?
Enviado desde mi Redmi Note 4 mediante Tapatalk
Click to expand...
Click to collapse
You can configure SIP by using an App called Activity Launcher.
Download and Install Activity Launcher
Start Activity Launcher
Choose 'All Activities'
Search for 'Phone'
Open 'Phone'
Search and Click 'Sip Settings', 'com.android.phone.services.telephony.sip.SipSettings'
{
"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"
}
Hello, yes I know this app to find secret menu. With this you can configure sip settings but when you try to make a call the dialer not offer choice to select calls with sip account
Enviado desde mi Redmi Note 4 mediante Tapatalk
salvarez01 said:
Hello, yes I know this app to find secret menu. With this you can configure sip settings but when you try to make a call the dialer not offer choice to select calls with sip account
Enviado desde mi Redmi Note 4 mediante Tapatalk
Click to expand...
Click to collapse
After you added an Sip account you can choose you default dailing method as follows: Dailer -> Settings -> Accounts -> Dail With
You also see your SIP account as "additional SIM Card" when Opening the dailer!
Thank you!
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
New twrp 331-test 1 for this device is builded!
Now need period of tests...
http://www.mediafire.com/file/cnqw8d2qkjqtp6k/Twrp_331_test1_Umi_Power.rar/file
reserved 1
Reserved 2
TWRP Not Working for Me
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
I confirm the first part of this, same issue here... i'd like to flash a twrp for gsi purposes, but for now no luck
SeekerofLight.iz said:
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Root UMIDIGI Power with Magisk
mr A V said:
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Click to expand...
Click to collapse
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
Step 0 - Download the Attached Zip File Below
Google Drive Mirror
Mediafire Mirror
MEGA Mirror
Step 1 - Drivers
Install the MediaTek drivers by running "DriverInstaller.exe". These are the drivers that worked for me. But if you have issues with them in Step 5, Google "Mediatek MT65xx USB VCOM Drivers" (or some variation of that) and try some others you can find.
-----------------------------------
Step 2 - Install ADB Interface
Install the Android SDK (ADB Interface). To do this drop the platform-tools folder (from the Step 2 folder) into your C:\ directory. Press the windows start button and search for "Environment Variables" and click on "Edit environment variables" from the results. Under SYSTEM VARIABLES on the bottom (not User variables above it) click on the "Path" variable, and click edit. In the new window that appears, hit "Browse..." and click on the "platform-tools" folder that you placed in your C:\ directory.
All this does is allows you to easily input adb commands into command prompt with no issues. This will be used to verify that the device is appearing properly and issue commands in case of emergency.
{
"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"
}
-----------------------------------
Step 3 - Install Magisk
Copy the Magisk.apk to your phone and install it.
(This is where you can then copy the boot.img to your device and patch it via the Magisk app to create the "magisk_patched_boot.img" file, however I have included the already patched file in Step 6 for the UMIDIGI Power so you don't need to.)
Also, this is the Magisk v19.3 Beta, but you can install another version.
-----------------------------------
Step 4 - OEM Unlocking/USB Debugging Mode
On your phone, go to Settings >> System >> Developer Options. (If you haven't activated Developer Options yet, do that by going to About Phone >> Build number, and tap it a bunch of times, but I'm sure you already know this lol)
In Developer Options, turn on "OEM Unlocking" to unlock the bootloader, and USB Debugging.
-----------------------------------
Step 5 - Verify That Your Phone is Detected with ADB
Connect your phone to your PC. Make sure you click "Allow USB debugging" on your phone. Then open up Command Prompt. (Protip: Type "color a" and press Enter if you want to feel like a REAL HACKERMAN.) Now, type in "adb devices" and verify that your phone is detected by your computer. If it's detected, then that's perfect you can move on to Step 6. If not, then uh... you may have to try and find some other MediaTek drivers mentioned in Step 1.
-----------------------------------
Step 6 - Set up SP Flash Tool
Open up SP Flash Tool on your computer by running "flash_tool.exe" in the SP Flash Tool Folder. (If at any time it shows a "Processing" window for some reason, just close and reopen the program if it doesn't go away on its own.)
On the first line choose "MTK_AllInOne_DA.bin". And the third line "Authentication File" can be left blank.
On the second line where it shows "Scatter-loading File", hit "choose" and find the "MT6765_Android_scatter.txt" file in the Step 6 folder. It'll load up and show a bunch of green/white rows in the space below.
Now this looked intimidating to me at first, but it's actually quite simple. As far as I understand (and I could be wrong but), the scatter file just tells the program where to place certain files, like a map for the program to follow. The scatter file I provided is for the UMIDIGI Power. The only thing we'll worry about for now is the boot.img file (but in the future, this is where you could also install a TWRP recovery once we get one that is confirmed to work.)
So in the white/green list, scroll down to where it says "boot" in the "Name" column, and click on the blank area in the "Location" column. It will bring up a window where you can browse to the "magisk_patched_boot.img" that I provided.
-----------------------------------
Step 7 - The Big Huzzah (Rooting)
Power off your phone and make sure it's UNPLUGGED. On SP Flash Tool, click "Download". This prepares the program to begin flashing your phone as soon as it is connected. Grab your phone with one hand, and with your other hand plug in the USB cable (if you only have one hand, use your mouth I guess). Your screen should not turn on at all throughout this process, but if it's successful, you should see that the program begins to flash your device after a second or two. Now just wait until it reaches 100% and says "Download Ok" with a green checkmark. And you're pretty much done!
You can then boot up your phone and check the Magisk app, as well as download a root checker from the Play Store to confirm that your phone has root access! Have fun!
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
mr A V said:
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
Click to expand...
Click to collapse
No problem! Unfortunately I don't see many custom ROMs coming to this phone, considering it's not a very popular device. I'd guess our best bet is to hope that the UMIDIGI F1 gets some support, and that anything on there can hopefully be ported over to this phone, but even that device isn't very popular either. For me though, that's not a huge issue because I'm actually quite satisfied with the stock firmware it has on board. It's basically stock Android Pie, and I've been able to add all the extra goodies I want into the phone through Magisk Manager and EdXposed with very minor issues. Most notably Viper4Android to fix the slightly tinny speakers and pump up the overall headphone experience too, and Gravity Box for some extra minor software customization.
Overall, I'd say the biggest downside to this device is the limited camera capabilities, and its somewhat limited performance for heavier tasks like 3D games / game streaming. But other than that, this feels like a very premium device. :good:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
mr A V said:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
Click to expand...
Click to collapse
I definitely consider myself to be a major noob with the more advanced Android development stuff. I only know enough to find my way around the internet and flash compatible software, haha. I've never looked into creating ports myself, but it's certainly something I think might be worth learning, especially with the limited device support on these phones.
And yeah, in terms of performance I don't expect much out of a phone at this price point, but for all the essentials - music, 1080p YouTube, web browsing, and mid to light gaming, it's surprisingly great considering the price. I haven't had any issues with the memory as of yet, so I wouldn't be too concerned, although you're definitely right in that they probably source some pretty cheap parts for these kind of phones.
SeekerofLight.iz said:
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
"stubbed guide"
Click to expand...
Click to collapse
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
---------- Post added at 09:30 AM ---------- Previous post was at 09:29 AM ----------
ghost45 said:
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
Click to expand...
Click to collapse
Can i ask you a guide on how were you able to boot it? i'm only getting a bootloop after flashing that from SPFlash
I will build one other version of recovery soon...
mg95tux said:
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
Click to expand...
Click to collapse
Glad to hear it worked for you!
Still nothing. Unfortunately I haven't had any luck with booting into TWRP since I last tried it. Hoping ghost45 will be able to help us out with that when he gets the chance.
Bootloop - Secureboot
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Andre_Filho said:
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Click to expand...
Click to collapse
remember to allow oem unlock from developer settings in stock rom, otherwise it will fail!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Andre_Filho said:
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Click to expand...
Click to collapse
The trick to getting Viper4Android to work is to make sure you have SELinux set to "PERMISSIVE" rather than "ENFORCING" on your phone. Here's a handy little app designed to automatically set it to permissive on boot!
https://forum.xda-developers.com/devdb/project/?id=1561#downloads
And for BusyBox, I was having issues too at first because I think with systemless root, BusyBox can only be installed in /sbin, which gets wiped after each boot. So I searched for "BusyBox" in the Magisk app and found a module called "BusyBox for Android NDK" which has worked perfectly for me.
One thing to note...
Sometimes SELinux doesn't always get changed automatically everytime you boot up. It's pretty consistent, but every once in awhile you may need to manually set it to permissive mode again if things don't seem to be working. But it's literally just pressing a single button, so not a big deal.
The other thing is with Viper itself- At times when I launch the app, the driver status says "abnormal" even after I've toggled SELinux to permissive. If you go into settings and toggle "compatibility mode" or "attach audio effects" on and then off that seems to refresh the driver status. Not sure why, but it works.
Let me know if you have any issues.
TWRP for UMIDIGI POWER
I ask for help in creating TWRP for UMIDIGI POWER firmaware ROM v1.5
Please make for this model TWRP
I am very grateful to you - I unlocked the phone and got the rights Root rights.
It remains only to create a TWRP for UMIDIGI POWER
At this forum, competent specialists and for other models everything is already done.
Maybe there is a website where you can make an order to create a TWRP?
Unfortunately, I do not know English and I do not know how to apply.
I would be very grateful and ready to test your work.
Introduction
This is the LineageOS 17.0 (non-GSI) port for K-touch i9 a.k.a Anica i9. Due to the lack of kernel source code, this port comes with a prebuilt kernel image, but the ramdisk has been updated to support a proper System-as-Root system partition as is required by Android 10.
This is ONLY compatible with the MT6739 variant of this phone.
About the phone
The K-touch i9 is an ultra-mini phone produced by K-touch (Ktouch / Anica) based on the MT6739 SoC. I got the phone purely due to its interesting size (similar to the Palm phone) and the desire to port real custom ROMs to it to see if they can work well. I mainly use it as a backup phone, so this port might not be thoroughly tested enough for daily drive.
Known Issues
- Some particular animation / gifs will skip frames or repeat incorrectly
Images
{
"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"
}
Flashing instructions
1. Unlock the phone (reboot to bootloader by holding volume up on boot, run `fastboot flashing unlock` and confirm)
2. Flash TWRP image from here
3. Reboot to recovery (hold volume up and choose Recovery accordingly)
4. Backup all stock partitions whatever way you like (especially boot / vendor)
5. Flash this LOS 17 port image and format data
6. Reboot and enjoy
Please note that after flashing this LOS 17 image, you have to restore the stock boot.img before being able to install A-only Android 10 GSIs again. Although you MIGHT be able to boot phh A/B GSI 10 on the boot.img of this LOS 17 port, please note that this is not tested and you still need to shrink the image size before phh GSIs can work -- the same as the A-only situation.
Why not GSI
There is no reason why not to use a phh GSI on this phone, given that phh GSIs work pretty well and I have actually fixed a few bugs for it too and I absolutely love it. However we can't play with some certain things, for example, transitioning to System-as-Root, in a GSI, and that's why I started this port just for fun. Also this device has such a small system partition that GSIs won't work out-of-the-box and require some manual adjustments just for the device, which kind of defeats the purpose. Nevertheless, I will contribute my fixes to GSIs so that things will work as well on GSIs as on my device-specific ROM ports.
Downloads
20191025: https://www.androidfilehost.com/?fid=4349826312261605900
Alternatively, you may check the latest updates to both the TWRP and the LOS 17 port on my GitHub
Source code
https://github.com/PeterCxy/android_device_ktouch_i9
There is no kernel source code available for this device, unfortunately.
Credits
all the people that have worked on MTK devices before me.
twrp link does not work
theleftykid said:
twrp link does not work
Click to expand...
Click to collapse
It works here. It links to a GitHub release page where you can download recovery.img for TWRP
Hi,
I bought this phone, but with different CPU- MT6580, 5MP camera at the back, would this ROM be compatible with it well?
I've tried to flash the TWRP recovery, but it failed - "FAILED (remote: size too large)" so it mean the recovery image not compatible with my phone?
This device is really nice, but huge let down by the operation sys. The battery drain really fast, always "phone idle" take place at the top of battery consuming chart.
Thank you!
hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.
theleftykid said:
hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.
Click to expand...
Click to collapse
Based on the previous comment before you, you seem to have the MT6580 version of the phone. This means you have a different and smaller gpt than the one from the OP that uses MT6739. You can't flash this ROM or any recovery from the MT6739 since they have different hardware and different partition layout. If you flash something, it will end with a nice brick
Cheers!
Rortiz2 said:
Based on the previous comment before you, you seem to have the MT6580 version of the phone. This means you have a different and smaller gpt than the one from the OP that uses MT6739. You can't flash this ROM or any recovery from the MT6739 since they have different hardware and different partition layout. If you flash something, it will end with a nice brick
Cheers!
Click to expand...
Click to collapse
Well, I’m sending myne back to get the mt3739 so I could mount 128gb sd card and to try this buil. It look promissing.
theleftykid said:
hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.
Click to expand...
Click to collapse
You boot into the original OS and the recovery will be back.
Thank you for this ROM.
I used it on my K-touch i10. Its the same as the i9 but the shape is slightly different.
I have the 3gb - 64gb version and it seems OK.
I had to use BiTGApps-Q for Playstore to appear.
I also had to go into the USB developer options to set up file transfer from a PC.
And no wallpaper app from holding on home screen.
I hope you keep this up to date else I might have to try and work out how to apply security patches.
Thanks again
EDIT. Oh so are you saying I could just try and install the GSI?
Edit. OK so Wellbeing and problems with Gapps is to do with Android 10 and gapps.
I also found twrp hard to control. The swipe action and pressing near the edge was difficult.
I don't have face recognition to unlock, not sure if that's because lineage os doesn't have it or the i9 doesn't, but certainly possible on my i10.
The swipe action in lineage is also difficult.
Thanks again. Just want to let you know.
Edit. Also a problem for me is when it's charging, touch screen gives the odd ghost press when used.
Ive found forcedoze useful with this phone.
Works with K-Touch M16?
Theoretically speaking this Rom should work in the K-Touch M16 as it has the exact same specs, processors, etc. Being the only difference is that it has a fingerprint sensor.
So I was wondering does anyone know if this custom ROM and TWRP works on the K-Touch M16.?
how do i download this rom. there are no active links available!
PeterCxy said:
Downloads
20191025: https://www.androidfilehost.com/?fid=4349826312261605900
Alternatively, you may check the latest updates to both the TWRP and the LOS 17 port on my GitHub
Source code
https://github.com/PeterCxy/android_device_ktouch_i9
There is no kernel source code available for this device, unfortunately.
.
Click to expand...
Click to collapse
From the first post
m16 tried
I have tried this with my M16, which is very similar to i9, same cpu same spec, got fingerprint though... no luck, unable to boot into recovery, anyone successfully done?
It worked with my K-touch i10.
I guess you should start looking at TWRP. If you have the same processor you should be able to get TWRP going.
Sorry no help here, maybe try a TWRP forum or something.
chinese bootloader
hi, i just got the phone so i wanted to flash this rom. but my bootloader is in chinese and i don't speak/read chinese.
can anyone here please help me get trough the bootloader so i do all the steps correctly.
i attached the picture from bootloader and also what google translate offers for translation.
does volume up and down works correctly on your devices? on my it just jumps one step down and up on ether up key or down key when i press and hold the key ti gradually turns volume up on ether up or down key.
I have an i10 and am no expert.
When I reboot and hold up-volune I get 3 options. Recovery, Fastboot and Normal in that order.
Are you sure your phone is the mt3769. As I had an i10 which was was MT6580 and I got those options. I did have Fastboot though. Sorry don't still have it for reference.
I just found out on youtube this menu should pop up when you press volume down + power on. But on my phone it also boots to this menu when i press volume up + power on. Guess i received defective volume buttons on my phone. Too bad as it is such a nice little phone.
Are you able to use the volume keys to move up and down the menu you took a picture of? Moving in this menu and selecting should be the up and down volume keys. Guess then you could see for sure if you have a key problem.
I did manage to take my phone apart as when I dropped it I managed to disconnect the screen cable inside but was lucky to be able to fix it.
---------- Post added at 12:23 PM ---------- Previous post was at 11:44 AM ----------
PeterCxy said:
...you still need to shrink the image size before phh GSIs can work...
...
Also, this device has such a small system partition that GSIs won't work out-of-the-box and require some manual adjustments just for the device, which kind of defeats the purpose. Nevertheless, I will contribute my fixes to GSIs so that things will work as well on GSIs as on my device-specific ROM ports.
Click to expand...
Click to collapse
Hello I'd like to update this for myself. I thought I'd use the GSI image but you say it needs resizing before use. Can you give me any pointers as to how you do this?
free30 said:
Are you able to use the volume keys to move up and down the menu you took a picture of? Moving in this menu and selecting should be the up and down volume keys. Guess then you could see for sure if you have a key problem.
I did manage to take my phone apart as when I dropped it I managed to disconnect the screen cable inside but was lucky to be able to fix it.
Click to expand...
Click to collapse
i am unable to enter the correct bootloader that gives you three options you mentioned before. i already contacted the seller to see what we can do cause i just received the phone. on this chinese menu i can navigate only down (pressing volume up or down moves the selection down) and i can select the item via power button.
I finally got my cubot pocket. I like my devices without GAPPS so I unlocked the bootloader and finally managed to flash a GSI.
This post contains: observations and general hints for this level of development, a guide to unlock the bootloader and what I did so far to flash a GSI.
Unlocking the bootloaderThis works similar to other Spreadtrum/Unisoc-based devices.
The crucial thing is to issue get_identifier_token from fastboot -> reboot to bootloader. If you issue it in adb reboot fastboot, it will say OKAY and may also print a four character string, but this is not the token you're looking for.
Also, when you flash the unlock_bootloader signature.bin, it will prompt you on the phone, but you have to react differently than described on the phone - see below.
enable Android developer mode (Settings -> About Phone -> tap "build number" >= 7x)
enable OEM unlocking (Settings -> System -> Developer Options -> OEM unlocking)
enable ADB (Settings -> System -> Developer Options -> USB debugging)
adb reboot fastboot
choose "reboot to bootloader"
Code:
$ fastboot oem get_identifier_token
proceed as described here
finally:
Code:
$ fastboot flashing unlock_bootloader signature.bin
this prompts you to press volume up to cancel, volume down to confirm.
But volume down and power don't have any effect, instead volume up starts wiping user.
wiping takes a bit longer than I'd expect, for me 433 s.
Congratulations, you now own your phone a bit more than before!
Flashing GSIs (probably applies to ROMs in general)It's a Treble-enabled arm64 A/B device. Flashing GSIs should be possible.
It looks to me like the A/B is crippled as all the _b partitions are 0-sized, probably to save space.
get and unpack necessary files as necessary: boot.img, vbmeta-sign.img, a ROM that you want, p.ex. AndyYan's Lineage GSI
fastboot resize-logical-partition product_a 38000
fastboot flash system [unpacked ROM file]
I also factory reset it afterwards
General/random notes
there are two different things reachable as "bootloader":
in fastboot switch to bootloader. The device displays the Cubot splash and from the display it looks stuck, but it exposes a fastboot interface -> useful
$ adb|fastboot reboot bootloader
shows the droid with open service door, saying "no command". It also exposes adb, but I don't see a way how to authorise it. Maybe via the debug UART? I didn't yet read the UART when I stumbled upon this. Currently it seems useless to me.
there are test points for the debug UART easily reachable once you disassemble it.
I didn't see anything with a 3.3V USB UART adapter, but a logic analyser with 1.4 V threshold works -> it probably uses 1.8 V logic level. UART-wise it's 115200 8n1.
I think I don't have anything to hook up to the TX currently.
UART log of boot
it's easy to softbrick this device, and I haven't found a nice way out of softbricked yet. Two not-so-nice-ways
- drain the battery, which obviously requires lots of patience
- disassemble the device and disconnect the battery
then flash the original ROM from the cubot site following the instructions there.
Once it bootloops, I didn't manage to power it off or get into fastboot / recovery using the device's keys.
the device reconfigures it's USB during boot and there's a limited time for the SPDFlashTool's mode that flashes complete firmwares. That means that it's not really feasible to run SPDFlashTool inside a VM.
the phone actually does something with the battery detached but USB power attached. For example, it's possible to flash it with the SPDFlashTool. However, it doesn't boot the linux kernel / Android, this seems to be inhibited.
This is in contrast to many other devices that are not laptops for which the PMIC does not provide power to the system when the battery is disconnected.
Old notes / how not to do it: Flashing GSIs (probably applies to ROMs in general)
it's a Treble-enabled arm64 A/B device. Flashing GSIs should be possible.
It looks to me like the A/B is crippled as all the _b partitions are 0-sized, probably to save space.
system_a is a bit below 1 GB ( 0x3CF5D000 B) which is likely smaller than any interesting GSI.
attempting to flash yields
Code:
Resizing 'system' FAILED (remote: 'Not enough space to resize partition')
There's the general hint to delete the product partition by running
fastboot delete-logical-partition product
then it's actually possible to flash a GSI, however:
the device bootloops -> log
From the log I realised I need to modify vbmeta, so:
it does android verified boot / AVB which from my understanding the easiest way forward is to disable it by:
creating a vbmeta.img with
Code:
$ avbtool make_vbmeta_image --flags 2 --padding_size 4096 --output vbmeta_disabled.img
the padding necessary might be 16384 instead, according to the hovatek thread below.
it might be necessary to pad it additionally. There's a tutorial and a script here
when I flash both the hovatek-unpadded avbtool-4096-padded and hovatek-padded avbtool-16384-padded vbmeta, the device bootloops -> log
I guess the next step would be to unpack the vendor PAC ROM and check how the vbmeta image looks there.
Since with the original vbmeta it looks like it's restarting when it's already running linux / android, another way to go at this might be to change the kernel cmdline: instruct it to not do verity - Does anyone know how this is possible?
reserved for future use
dead ends (so far...)
didn't manage to find what image header magic number was wrong with the vbmeta.img (was already in the starting post)
the vbmeta actually doesn't chain to system, but there's a vbmeta_system partition (and vbmeta_vendor.img, vbmeta_system_ext.img, vbmeta_product.img) - I flashed the empty vbmeta disabling checking to vbmeta_system... and it bootloops again
this time the error is:
Code:
sprd_get_all_imgversion: ab_slot_flag is 0
read successed
sprd_get_all_imgversion: rpmb read blk 16382 successful
invalid sprd imgversion magic 0 exp a50000a5
uboot_vboot_verify_img() return error:param->a0=3
could be that it's just necessary to write the magic number to the correct offset, but I coulnd't figure out where this offset is - the images in the PAC don't have this number, so I guess it's embedded on-the-fly while flashing.
searching for imgversion+spreadtrum gets 0 relevant results - I guess it's very unusual that people hook up to the debug uart
I didn't manage to disassemble uboot.img - At least the disassemble doesn't look like a bootloader to me. Not an expert with disassemblies though!
modifying boot.img with magisk also results in invalid sprd imgversion, so no root or disabled verity through this route
I didn't manage to read back from flash through SPD ResearchDownload, I get the error "incompatible partition" for userdata - and I can't deselect it :/
(I thought it might be possible to get the sprd imgversion magic throught this route
Partial successI managed to boot a GSI by signed by google through Dynamic System Updates (DSU).
It kind of looks like it's running in emulation though: settings say "About emulated device" and it gets an own userdata.img
the DSU page also says it will only run GSIs signed by google or the vendor (not sure which key that would be, but I doubt there are any) - I haven't tried flashing anything this route
Open Ends:reverse engineering the imgversion thingIt should be possible to figure out how this imgversion business works, ultimatively from the u-boot.img / PAC content. Anyone has any idea how to proceed there? I tried:
binwalk: doesn't look useful to me, nothing got extracted -> here
arm-none-eabi-objdump -b binary -D u-boot-sign.bin -m armv8-a -Mforce-thumb
(also without -Mforce-thumb and with -m armv7)
I'm pretty sure it's actually U-boot: there is the U-boot version string matching the one printed to uart and also the printf-string for the imgversion
requested U-boot source code from CubotI requested source for all GPL'ed parts of the Pocket from Cubot, but especially U-Boot and the kernel. I'd be a pleasantly surprised if something comes out of this though
reading back the flashDoes anyone have an idea how to do that? without root no access to /dev/block/mmcblk* and I didn't get SPD ResearchDownload to read it.
It's nice that you could unlock the bootloader! I'll try to do it soon (maybe in some months, but ok lol)
Anyway, which GSI did you try? And about the vbmeta, I think it should be enough to flash the blank vbmeta.img from google. Maybe we could use the original vbmeta.img from stock ROM with the --disable-xxxxx flags.
This is the tutorial from phhusson's group (the man behind the treble project):
0. Get an up-to-date fastboot on your computer (fastboot —version should give version >= 29)
1. Get vbmeta.img from https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
2. Get A/B GSI (I'm guessing you need ARM64), don't forget to uncompress it
3. From running Android, do adb reboot bootloader
4. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. fastboot reboot fastboot
6. fastboot flash system system-xxxx.img
6bis. If fastboot tells you there isn't enough place, do fastboot delete-logical-partition product, fastboot delete-logical-partition product_a, fastboot delete-logical-partition product_b and run the fastboot flash command again
7. On your phone, the screen should have a button "go back to recovery", select it, then select "factory reset / wipe data"
8. Reboot and enjoy
Thanks for your work. I got my Cubot Pocket unlocked too. I have booted LineageOS 19 via DSU Sideloader. It runs like a charm but there is no way to flash the GSI permanent.
@changer86 with the DSU I have the navigation bar not showing, back-gesture not functioning and no automatic display brightness - do these work for you?
wori said:
@changer86 with the DSU I have the navigation bar not showing, back-gesture not functioning and no automatic display brightness - do these work for you?
Click to expand...
Click to collapse
I tried it. My Navigation Bar is showing and working normal.
Automatic Display Brightness is working too.
I dont use gestures, but if you tell me how to do it, i will check that too.
Image: lineage-19.1-20220719-UNOFFICIAL-arm64_bvS.img.xz
and DSU-Sideloader 1.03 from Github. Default Settings
thanks for trying!
You can change it in Settings->System->Navigation->System Navigation->check Gesture Navigation
So: interesting that you got a lineage build working, maybe that's the important difference! From google's doc I understand that there's some verifcation, but looks like it's not. Since I actually don't want the google build, I'll try with lineage next. Did you also try with the built-in DSU way, like described in googles doc?
wori said:
Did you also try with the built-in DSU way, like described in googles doc?
Click to expand...
Click to collapse
As I understood, the app is doing exactly the same like the Google Doc say. It seems like unlocking the Bootloader is enough to boot a custom-DSU.I have read something about signed Images that will boot without unlocking the Bootloader, but i didnt try it. I just want to get rid of all the Google-Stuff before using the Pocket Hope we can get it working.
btw: Gestures seem to work. swipe from right to middle closes Apps. from middle to up opens Menue
After a Weekend of fails i flashed Lineage 19 to my old KingKong mini and its working on the first try. Problem seems to be the Unisoc T310. The success-rate of flashing GSI to T310 seems to be really low. Does anybody know another Android 11 Device with Unisoc T310 that is working with GSI-Roms?
changer86 said:
Does anybody know another Android 11 Device with Unisoc T310 that is working with GSI-Roms?
Click to expand...
Click to collapse
GSI on Unisoc device
My tablet is unisoc t310 T803 with oem android 11 here is were im stuck I reflashed oem super.img and the system booted fine so i can start fresh i erased product and system, and flashed lineage 17.1
www.hovatek.com
seems this guy has succeeded and his device looks pretty similar to pocket in treble info
im unisoc tablet has oem stock A11 and no GSI A10 was to boot. my oem system is system as root AB arm64. so I have no choice but to use Arm64 AB GSI A11 because A10 will not boot
Click to expand...
Click to collapse
Hi, can you help me with this situation? I can't unlock bootloader on cubot pocket.
I tried to unlock on my ubuntu and windows devices.
FAILEN ( Flashing Lock Flag is locked. Please unlock it first)
I don't know that I will do for this problem
Spoiler: image
{
"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"
}
@raary did you enable OEM unlocking in the Android settings?
wori said:
@raary did you enable OEM unlocking in the Android settings?
Click to expand...
Click to collapse
Yes of course
raary said:
Yes of course
Click to expand...
Click to collapse
Did you use the modified fastboot ? Under Ubuntu start a Terminal from the extracted Folder and use ./fastboot instead of fastboot. Ensure that fastboot in the folder is executable. Check this guide: How to unlock Unisoc
Be warned: Unlocking the Bootloader ist working but flashing vbmeta like you tried leads to bootloop. I think the cubot pocket needs signed Images for flashing. there is a guide for custom signed Images but i did not get it to work for now.
changer86 said:
Did you use the modified fastboot ? Under Ubuntu start a Terminal from the extracted Folder and use ./fastboot instead of fastboot. Ensure that fastboot in the folder is executable. Check this guide: How to unlock Unisoc
Be warned: Unlocking the Bootloader ist working but flashing vbmeta like you tried leads to bootloop. I think the cubot pocket needs signed Images for flashing. there is a guide for custom signed Images but i did not get it to work for now.
Click to expand...
Click to collapse
Thank you, I will be try to unlock
@wori any updates on flashing gsi?
@badcodelab not from my side. I got frustrated and also had some other things to do. Hopefully find some time + energy to continue working on this.
I can't stay in stock OS, my GSI on cubot pocket have only 16 Gb via DSU sideload less for me, correct custom not exist for this, sad
@wori, @changer86 i didn't get clear from your posts if you tried to use signed vbmeta from the stock rom
also i haven't manage to make research tool to unpack boot.img nor super.img
by some reasons they stay listed as zero-sized .flag files in the target folder
{
"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"
}
This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 6a devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.
This seems interesting. I was just looking into options to disable verity and or verification, root, and flash a custom kernel. It seems this application is an all in one. If all goes as planned, will my data and apps remain? Or am I basically starting all over. My bootloader is already unlocked. Thanks for sharing.
chopt51 said:
This seems interesting. I was just looking into options to disable verity and or verification, root, and flash a custom kernel. It seems this application is an all in one. If all goes as planned, will my data and apps remain? Or am I basically starting all over. My bootloader is already unlocked. Thanks for sharing.
Click to expand...
Click to collapse
If you don't choose wipe data, or force in flash options, then you should keep your data.
I have my 6a connected with usb. I chose where my platform tools are in a directory but it doesnt find a device via adb. Yet cmd shows an adb connection.
USB debugging turned on?
tlxxxsracer said:
Yet cmd shows an adb connection.
Click to expand...
Click to collapse
Explain what you mean by that?
badabing2003 said:
Explain what you mean by that?
Click to expand...
Click to collapse
usb debugging was on. when I run an adb/fastboot in cmd within the same directory my device is recognized
tlxxxsracer said:
usb debugging was on. when I run an adb/fastboot in cmd within the same directory my device is recognized
Click to expand...
Click to collapse
Please be clear and explicit, exactly what you ran and what response you got, please also generate support.zip file from the help menu of PixelFlasher and post it here.
There is no reason for it not to be detected if you're command detects it.
New Release:
Aug 24, 2022 v3.6.0 release
When a device is selected, the Bootloader version is displayed. (Useful for Pixel 6* devices with ARB). Works in adb and fastboot modes.
Added a button to dump full device info (useful for troubleshooting). Works in adb and fastboot modes.
Improved tooltips.
Hello,
I have a pixel 6a on A12 rooted with Magisk.
I tried to upgrade to A13 with PixelFlasher (v3.6.0) with the option to flash all the slots and now I'm stuck in loop.
I tried to use fastboot command to flash again with A13 with no result. I also tried to change the current slot.
The weird thing is that I still have the message that said the bootloader is unlocked...
Any ideas?
jpdurand31 said:
Hello,
I have a pixel 6a on A12 rooted with Magisk.
I tried to upgrade to A13 with PixelFlasher (v3.6.0) with the option to flash all the slots and now I'm stuck in loop.
I tried to use fastboot command to flash again with A13 with no result. I also tried to change the current slot.
The weird thing is that I still have the message that said the bootloader is unlocked...
Any ideas?
Click to expand...
Click to collapse
If you can post support.zip file from help menu I can take a look.
If you want more info, i'm 100% available!
jpdurand31 said:
If you want more info, i'm 100% available!
Click to expand...
Click to collapse
Hmmm ...
I don't see any flashing logs in PixelFlasher, are you sure you flashed in PixelFlasher?
I see you started with PixelFlasher 3.4.0 and upgraded to 3.6.0; good
I see at first you did not have Android Platform Tools installed, and then had version 28.0.2-debian; bad, this is an old version, you should click on the blue link next to the Android Platform Tools and download the latest (don't install from package manager, those are usually old, just download the latest and unpack wherever you want, and point to it in PixelFlasher)
You started in adb mode (good), processed the firmware in PixelFlasher, but that is where you stopped, you did not attempt flashing in PixelFlasher (not sure what you did, but it would help to know)
On next attempt (one hour later) your device was in bootloader mode.
Then you tried disabling magisk, which didn't work because that feature requires adb mode, and your phone is stuck in fastboot mode.
You cannot create a patch file in fastboot mode, it needs to be in adb mode.
And please please don't dare to lock your bootloader, I see you attempted and then cancelled,
Code:
2022-09-02 18:25:29 Lock Bootloader
WARNING!!! WARNING!!! WARNING!!!
NEVER, EVER LOCK THE BOOTLOADER WITHOUT REVERTING
TO STOCK FIRMWARE OR YOUR PHONE WILL BE BRICKED!!!
Do you want to continue to Lock the device bootloader?
Press OK to continue or CANCEL to abort.
2022-09-02 18:25:42 User Pressed Cancel.
Aborting ...
If you lock your bootloader before fixing your device, you will be locked out forever (bricked)
So at this point what are your choice and how can you fix this?
1- get the latest Android Platform Tools
2- If PixelFlasher detects your device, check if it is in fastboot mode (f.b) or adb mode.
Select the firmware, process it, this will show the boot.img file
Select the boot.img file and choose keep data and hit Flash.
Yes I know, you will lose root because you're not flashing a patched boot.img, but you can always re-root if you recover your device.
Alternately, what happens if you select in PixelFlasher to reboot the device into System.
Does it reboot? and if it does, does it end up in adb mode of fastboot mode?
One other option you have is to flash OTA in sideload mode.
Report back, and make sure you capture all the manual steps you perform outside of PixelFlasher.
PixelFlasher logs would tell me everything you do in PixelFlasher, you can submit a new one after your operations.
Good luck
Thanks for your response and the detailed process.
I was fooled by the version of the package that was in 33...
By upgrading the Android Platform Tools to the latest version, I could update to Android 13.
Thanks a lot for the help and the reactivity!
New Release:
Sep 04, 2022 v3.7.0 release
New Feature: Install Magisk into the phone, PixelFlasher displays information about the latest available Magisk versions (stable, beta, canary, debug) and offers the choice to install a selection.
New Feature: Install compatible apk file onto the device from PixelFlasher menu.
Check Android Platform Tools version and warn if it is old.
Block flashing when stock flash_all.bat file is tampered with.
Don't bother with flashing if bootloader is locked.
More validations and exceptions handling.
Improved logging.
3.7.0 does not start for me on Windows 10. It never appears in my task list as running. 3.6.0 is working fine.
JudasD said:
3.7.0 does not start for me on Windows 10. It never appears in my task list as running. 3.6.0 is working fine.
Click to expand...
Click to collapse
Thanks for reporting and sorry for your troubles.
Can you please open a command prompt, navigate to PixelFlasher 3.7.0 and run it from command prompt (just type PixelFlasher.exe), see if it displays an error in the console.
Can you also please generate a support.zip file using PixelFlasher 3.6.0 ?
It should capture the error PixelFlasher 3.7.0 encountered.
Thank you for the help. The issue has now been resolved after reboot.
Launching 3.7.0 via cli displayed no error message. I went to create support.zip with 3.6.0 and my computer BSODed. After reboot, 3.7.0 runs just fine. Apologies for the false alarm.
JudasD said:
Thank you for the help. The issue has now been resolved after reboot.
Launching 3.7.0 via cli displayed no error message. I went to create support.zip with 3.6.0 and my computer BSODed. After reboot, 3.7.0 runs just fine. Apologies for the false alarm.
Click to expand...
Click to collapse
No need for apology, happy to hear that the issue now resolved.
Not sure if this should be of concern, but upgrading to today's Android release, I got this (very early on, while selecting the device and firmware):
Code:
2022-09-12 18:44:06 ERROR: Exception during Magisk modules processing
Exception: not enough values to unpack (expected 2, got 1)
Everything seemed to work fine, though.