ULTIMATE GUIDE TO FIX ROM FROM FAKE UNLOCK BOOTLOADER
Device: Redmi Note 5/Pro (Whyred)
Anti: 3 (required)
Initial Rom: Global/China with ARB v3
Method: Test Point
As we know that buying whyred from a distributor with a red box has a strange rom and also mi account that can't be binded. this is very troublesome when we want to unlock the bootloader..
This method is to really lock the Bootloader again, can bind Mi account and can be used for Unlock bootloader officially.
And finally, this method doesn't need to edit the script anymore, I upload patch scripts and loaders specifically for ROM 9.5.17 below.
It has been tested and the results are successful.
Let's start and DWYOR!
Step:
1. Download ROM 1 and ROM 2 below then extract.
2. Download the Patch then copy and replace it in ROM 1 which has been extracted (in the images folder).
3. Open back cover of the phone carefully and connect to the PC via Test Point (HS-USB QDLoader 9008)
4. Flash ROM 1 that has been patched with MiFlash (I use MiFlash 2017.4.25.0 and PC 64bit during flashing).
5. After success, close the miflash, unplug the cable, and turn it on. Wait a few moments until stuck in recovery mode (pict 1)
6. Connect Whyred to PC again via Test Point and Flash ROM 2 with MiFlash.
7. Wait for the first boot, after entering the system, check unlock status in developer mode and tadaaaa.. it's completely locked now... (pict 2)
8. Bind Mi account, continued unlock bootloader officially.
9. Done! ready to go to custom ROM
Note:
1. Patch is only used for ROM 1 (Global 9.5.17).
2. ROM 2 can use all China ROMs as long as still ARB v3.
Picture:
Pict 1
{
"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"
}
Pict 2
War Equipment:
ROM 1. (Global 9.5.17): LINK
ROM 2. (China 9.5.21): LINK
Patch: LINK
Just Hit THANKS Button for Supporting me..
Any chance this guide can be updated for ARB4? At least the patch file?
Edit:
Nevermind, I see it cannot be done.
poncespr said:
Any chance this guide can be updated for ARB4? At least the patch file?
Edit:
Nevermind, I see it cannot be done.
Click to expand...
Click to collapse
The same mistake is also available
poncespr said:
Any chance this guide can be updated for ARB4? At least the patch file?
Edit:
Nevermind, I see it cannot be done.
Click to expand...
Click to collapse
UtkuAblak said:
The same mistake is also available
Click to expand...
Click to collapse
sorry bro, currently only available for arb 3. refers to the difficulty of flashing if it has arb 4. coz the test point method in arb 4 must use an authorized account.
there is a guide to bypass this authorized account, but there are some reports that still fail.
this weirdness has been made xiaomi itself..
octodellin said:
sorry bro, currently only available for arb 3. refers to the difficulty of flashing if it has arb 4. coz the test point method in arb 4 must use an authorized account.
there is a guide to bypass this authorized account, but there are some reports that still fail.
this weirdness has been made xiaomi itself..
Click to expand...
Click to collapse
Stupid me that updated my RMN5Pro before reading these guides. Still is a great phone. Just wanted a taste of pie.
Mi phone deat
Sir, my nead mi authorized account please help me this my id 1813003637
---------- Post added at 05:50 PM ---------- Previous post was at 05:39 PM ----------
Sir my need mi authorized account please help me
This is my id 1813003637 sorry for my bad english
I have ARB3 device with fake ubl. I want to try this method, but I can not fully understand what we do with battery while short circuit the test points(5th step).
After writing 1st ROM, we connect the battery, then open device and stuck with recovery. After this (6th step), will I disconnect the battery again, while test point?
And another question;
while writing 1st or 2nd ROM which option we select with MiFlash Tool? "Clean_all" or "Clean_all and Lock" ?
How can I check for Fake UBL to be sure for 100% that I need this ?
netlogger said:
I have ARB3 device with fake ubl. I want to try this method, but I can not fully understand what we do with battery while short circuit the test points(5th step).
After writing 1st ROM, we connect the battery, then open device and stuck with recovery. After this (6th step), will I disconnect the battery again, while test point?
Click to expand...
Click to collapse
yes, like the first..
netlogger said:
And another question;
while writing 1st or 2nd ROM which option we select with MiFlash Tool? "Clean_all" or "Clean_all and Lock" ?
Click to expand...
Click to collapse
both can be used, coz basically our whyred is in locked bootloader.
but for sure, you can choose Clean_all and Lock
The4anoni said:
How can I check for Fake UBL to be sure for 100% that I need this ?
Click to expand...
Click to collapse
go to fastboot mode and run fastboot command:
Code:
fastboot getvar anti
if the displayed output is 3, is good. that means you can use this method.
if the displayed output is 4, you can not use this method.
octodellin said:
go to fastboot mode and run fastboot command:
Code:
fastboot getvar anti
if the displayed output is 3, is good. that means you can use this method.
if the displayed output is 4, you can not use this method.
Click to expand...
Click to collapse
I know how to check anti rollback... I want to check does my bootloader is fake unlocked or not
I copied the patch files to the ROM1 images folder.
I open miflash, selected the ROM1 folder.
I made the testpoint method, and I see driver 9008.
then clicked the refresh button then Flash button on miflash program. It writes "flashing".
Flashing process starts, but after that, it stucks while writing keymaster.mbn file. I waited over 20 minutes but nothing happened.
I tried another miflash from may 2018, but same situation.
I tried other USB ports, nothing changed.
I checked the log file. At begining it seems everything normal, but when it came to write keymaster.mbn file(this is the first file to flash)
The log file looks like this:
...
: Write file C:\RN5... ....\images\keymaster.mbn to partition[keymaster] sector 65536
: write file legnth 357392 to partition 65536
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
...
And gooes on like this for over 80000 lines. I closed the miflash.
I checked the phone, nothing happened, It opens normally, old rom still there...
what can be the situation?
The4anoni said:
I know how to check anti rollback... I want to check does my bootloader is fake unlocked or not
Click to expand...
Click to collapse
1. check in mi unlock status from developer mode
2. check from fastboot command: fastboot oem device-info
3. test to unlock bootloader
if you face unlocked in mi unlock status but in fastboot showing "Device unlocked: false" even more you can't bind account, thats mean you unlocked is fake.
netlogger said:
I copied the patch files to the ROM1 images folder.
I open miflash, selected the ROM1 folder.
I made the testpoint method, and I see driver 9008.
then clicked the refresh button then Flash button on miflash program. It writes "flashing".
Flashing process starts, but after that, it stucks while writing keymaster.mbn file. I waited over 20 minutes but nothing happened.
I tried another miflash from may 2018, but same situation.
I tried other USB ports, nothing changed.
I checked the log file. At begining it seems everything normal, but when it came to write keymaster.mbn file(this is the first file to flash)
The log file looks like this:
...
: Write file C:\RN5... ....\images\keymaster.mbn to partition[keymaster] sector 65536
: write file legnth 357392 to partition 65536
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
...
And gooes on like this for over 80000 lines. I closed the miflash.
I checked the phone, nothing happened, It opens normally, old rom still there...
what can be the situation?
Click to expand...
Click to collapse
1. make sure that you have extracted the patch. there are 3 files that must be replaced to the images folder in ROM 1 (Global 9.5.17)
2. use the miflash that I use
3. try to change clean all or clean all and lock, with flash_all.bat
hope it works for you ..
I allready tried that all of you wrote. But in windows command prompt mode, I tried to execute flash_all.bat with admin rights. It didn't work.
---------- Post added at 10:45 AM ---------- Previous post was at 10:42 AM ----------
I allready tried all. Nothing changes.
I tried to run flash_all.bat from command prompt with admin rights, but that does not work.
Bruh. Thanks a lot. This is the ONLY guide that has helped me fix my Note 5 Pro.
I was on global rom from the seller... I'm flashing a bunch of ARB 3 or lower MIUI roms... I accidently flashed with lock the bootloader...
That bricked my phone. No other roms would work. No china ones, no global. Tried so many patches until this guide which worked for me.
Thanks
Related
Hello everyone.
I know many Nokia 8 users experience some issues with both Oreo and Pie (it can be battery, freeze, etc..). Bear in mind that Nougat is totally adapted to Nokia 8 performances as it has been sold along with it.
Anyway, this guide is mainly for TA-1012 model, but I guess it can work with other models as well.
I. The Downgrade part
1. Unlock your bootloader (critical)
Before anything, you must unlock your bootloader critically.
As far as i'm concerned, I did the official method, that is described here : https://forum.xda-developers.com/nokia-8/development/official-nokia-8-bootloader-unlock-t3848051/
But there is a lot of topics on here on how to unlock (+critical)
2. Flash Nougat firmware with NOST
I used the first released Nougat firmware, namely NB1-0-303A-00WW-B01.nb0.
You can find it here : https://fih-firmware.hikaricalyx.com/hmd_en.html
Or on my MEGA : https://mega.nz/#!lodxDaAR!u5ZJLv8LHKL0U3irqTlRMdZoz1adzni1oN87KC2D-Fg
2.1 Download NOST
NOST (Nokia Service Tool), is a modded version of OST, easy to use. A huge thank to the developer.
I've had issues with NOST 0.5, so please download 0.6 (last version when I write those lines) :
Github link: https://github.com/StollD/NOST/releases/download/v0.6/NOST-v0.6.exe
Mirror link : https://mega.nz/#!E9kERajA!KnELFSHV9ekHhJFnWu4lL0PbkIbLT5qHCvupr8Kawk0
2.2 Download ADB and Fastboot drivers
Here is an easy guide : https://www.xda-developers.com/install-adb-windows-macos-linux/
ADB Windows mirror link : https://mega.nz/#!AhsBSYgJ!R_s2pE6fvFXNKsATSGffdjNGoPJy57HkgQeg9XNID6M
2.3 Reboot into Bootloader (aka Download Mode)
You can boot into Download Mode with VOL DOWN and POWER key, or with this method :
- First, turn on USB Debugging on your phone, and plug in into your computer
- Then, extract the content of the previous downloaded ADB/Fastboot driver
- Next, go to the root of the extracted folder, hold SHIFT and do a Right click on that same folder, and open a command prompt here
- On the commande box, just type :
Code:
adb reboot bootlader
2.4 Install NOST and flash nb0 file
Your phone is now into Download Mode, plugged into you PC.
Open NOST, load your nb0 file, and make sure that you check Erase User Data (an Normal Download, but it's already checked)
{
"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"
}
Just press next, and your firmware is now flashing.
Wait until your phone reboot.
Congratulations you are now on Nougat 7.1.1 !
II. The Root part
I don't used the TWRP flashing wat to root my phone, since I never suceeded to boot it, idk why.
So we'll use the magisk boot image flashing here.
1. Download Magisk Manager APK
Github link : https://github.com/topjohnwu/Magisk/releases/
Mirror link (7.1.1 version) : https://mega.nz/#!Zk8ESAQA!n3JLUC-nU4xBKB7E3J0aTsvAzp9WlAHM5_VbgXob6c0
Then install the APK on your phone, open the app, and make sure everything is up to date inside.
2. Patch stock boot image from extracted nb0
The normal way to do it is to extract your nb0 file with this software :
- XDA link : https://forum.xda-developers.com/attachment.php?attachmentid=4468396&d=1523018789
- Mirror link : https://mega.nz/#!AksQDSyb!zTt_L4x-DgP6aQG83D0DF4m34v78gFjA855JzSN-yBY
BUT, the software needs a lot of RAM to end the process, and I got an OutfMemory error. I had to use a powerful computer to extract the file.
So to make the task more easy for you, here is the stock boot image from the extracted nb0 :
- Mega link (Stock boot image) : https://mega.nz/#!khUFVArZ!KJ7ezdXKzisVtFgiGiTL1WiEnxBoTYJdhs9rI5CrI0w
If you want to patch it yourself with Magisk, you can, but again, I give you my patched boot image (so just ignore the above link) :
- Mega Link (Patched boot image) : https://mega.nz/#!sok2kS6B!WRUJK_B2vsFIMA8VJpyCCw98xVOgEWLQIjHj6zxq-lI
3. Flash patched boot image
Go into the ADB extracted folder (the one with fastboot.exe).
Copy the downloaded NB1-0-303A-00WW-boot-patched_boot.img into this folder.
Then open the command windows with SHIFT + Right Click.
Plug your phone into your computer, and reboot into bootloader, as always with :
Code:
adb reboot bootloader
Once into Download Mode, flash the patched boot image with :
Code:
fastboot flash boot_a NB1-0-303A-00WW-boot-patched_boot.img
(be sure that your main partition is a. Otherwise you'll have to do boot_b)
(you can rename the .img file to make the command line more easy, e.g. boot.img, then type fastboot flash boot boot.img)
Now reboot your phone and go to Magisk Manager. Check that everything is updated, and on the left panel, go to Super User. You are now rooted !
Has anyone else apart from the author tested this method and can confirm that it works perfectly? No issues with rolling back or after rolling back? Everything works, even Google pay? Battery life significantly improved?
For battery life I dont think its that significant
I'm on stock Android 9 and consistently get not less than 6 hours SOT - how much do you have on nougat?
Saloon-Baloon said:
I'm on stock Android 9 and consistently get not less than 6 hours SOT - how much do you have on nougat?
Click to expand...
Click to collapse
With 50% brightness :
On SOT standby it last 12h
On SOT internet (browsing, YouTube) it last 6h
And in general, when I'm outside an entire day, it's at 50% battery when I come back at home on evening (with music, internet browsing...).
yozil said:
With 50% brightness :
On SOT standby it last 12h
On SOT internet (browsing, YouTube) it last 6h
And in general, when I'm outside an entire day, it's at 50% battery when I come back at home on evening (with music, internet browsing...).
Click to expand...
Click to collapse
Well I get better results on Pie on a single charge. Discharged from 85% to 16% over 35hours
MDV106 said:
Well I get better results on Pie on a single charge. Discharged from 85% to 16% over 35hours
Click to expand...
Click to collapse
It depends, what did you do in those 35 hours ?
If I lock my phone for 10h, I also can have 30 hours battery
yozil said:
It depends, what did you do in those 35 hours ?
If I lock my phone for 10h, I also can have 30 hours battery
Click to expand...
Click to collapse
I use Whatsapp, telegram, instagram, twitter via twidere, OSMand for navigation daily, Musicolet for music (at least 6 hours of music), i browse plenty on Kiwi browser. I also check Reddit and XDA every few hours. Not only that but listed apps usually end up with me opening youtube links and watch videos on it. Point is, Pie is not as bad as most of you claim. I get 8+ hours of SOT over 24h+ on a single charge from 90% to 20% almost everytime.
hi, I m using TA-1004 and back to Nougat successfully after flash NB1-0-303A-00WW-B01.nb0, I can boot up my phone and with out root, but when I start up my phone in first initial screen , after select language, it should be at select SIM/select wifi screen, I connect my wifi it's force update my phone to android pie, I havn't see "skip" button, dose anyone know how can I skip this update?
I need my Nougat....thanks all
kelvin31 said:
hi, I m using TA-1004 and back to Nougat successfully after flash NB1-0-303A-00WW-B01.nb0, I can boot up my phone and with out root, but when I start up my phone in first initial screen , after select language, it should be at select SIM/select wifi screen, I connect my wifi it's force update my phone to android pie, I havn't see "skip" button, dose anyone know how can I skip this update?
I need my Nougat....thanks all
Click to expand...
Click to collapse
Its been said multiple time...DO NOT ACTIVATE WIFI WHEN BOOTING UP THE OS
MDV106 said:
Its been said multiple time...DO NOT ACTIVATE WIFI WHEN BOOTING UP THE OS
Click to expand...
Click to collapse
Thx for reply first.
No WiFi button found, my situation is first initial setup
1. Select language
2. Insert SIM card screen
3. Copy your data, from iPhone Android or cloud / set up as new
4. Get connected( select WiFi then)
Where can I turn off the WiFi ?
Thanks
kelvin31 said:
Thx for reply first.
No WiFi button found, my situation is first initial setup
1. Select language
2. Insert SIM card screen
3. Copy your data, from iPhone Android or cloud / set up as new
4. Get connected( select WiFi then)
Where can I turn off the WiFi ?
Thanks
Click to expand...
Click to collapse
Do not copy your data because it likely contains all your saved wifi passwords. Just skip everything you can. Dont select the wifi network when asked either.
"Don't activate WiFi" is not the solution here. Android will force you to select a WiFi. This is called factory reset protection - to prevent an attacker from downgrading your phone to a vulnerable android version. What you have to do is reinstall Pie, set up the phone, and then before you downgrade, remove the google account from the device. That disables FRP and you can setup Nougat just fine.
I have select erase userdata in NOST
---------- Post added at 07:37 AM ---------- Previous post was at 07:33 AM ----------
THMSP said:
"Don't activate WiFi" is not the solution here. Android will force you to select a WiFi. This is called factory reset protection - to prevent an attacker from downgrading your phone to a vulnerable android version. What you have to do is reinstall Pie, set up the phone, and then before you downgrade, remove the google account from the device. That disables FRP and you can setup Nougat just fine.
Click to expand...
Click to collapse
Thank you!
Let me try and study how to remove FRP first
Thanks
THMSP said:
"Don't activate WiFi" is not the solution here. Android will force you to select a WiFi. This is called factory reset protection - to prevent an attacker from downgrading your phone to a vulnerable android version. What you have to do is reinstall Pie, set up the phone, and then before you downgrade, remove the google account from the device. That disables FRP and you can setup Nougat just fine.
Click to expand...
Click to collapse
Explains why I never had these wifi issues in the first place when I downgraded to unlock the bootloader. Its cause I never signed in on google on this phone. Even now on Pie, I uninstalled all google apps and only kept Play Services (which ive kept disabled).everything still works and I get my notifications from apps with no hiccups. Most of all the battery life is exellent (i only need to charge once every 2 day window)
kelvin31 said:
Thx for reply first.
No WiFi button found, my situation is first initial setup
1. Select language
2. Insert SIM card screen
3. Copy your data, from iPhone Android or cloud / set up as new
4. Get connected( select WiFi then)
Where can I turn off the WiFi ?
Thanks
Click to expand...
Click to collapse
He mean to not connect on any wifi network.
Послато са TA-1012 уз помоћ Тапатока
Allek84 said:
He mean to not connect on any wifi network.
Послато са TA-1012 уз помоћ Тапатока
Click to expand...
Click to collapse
I can't bypass the wifi selection stop, no skip button
kelvin31 said:
I can't bypass the wifi selection stop, no skip button
Click to expand...
Click to collapse
Before downgrading, while you on Pie,delete google account from settings and then do downgrade and you will have options to skip.
Nice
Fully working TA-1012
And i think battery time so good
In pie pubg run only 3/4 hour and in Nougat 5+ hour
This seems obsolete by now, gives me a func not ready error in nost. To mention that I first installed tvirus, and then reverted it.
Not only that but it broke something and the device isn't recognized in downloader mode by fastboot, and NOST either hangs or throws errors while flashing so I'm stuck in unrooted android 9 until I somehow fix it, nice. And then I hard bricked trying to solve this.
Ok, managed to fix everything. It seems windows nokia drivers and fastboot simply **** their pants at some point and lose access to phone even when it's detected in device manager. Flashed FWUL to a USB, booted to linux from the USB, and from there flashed T-Virus, no problem. Now I could revert to get back to stock android 9 if I want to using T-virus revert. Lessons of the story: 1) don't use OST or NOST. 2) Get bootable linux on a usb for all android needs 3) Maybe I could've solved the issue in windows if I didn't try using OST again, after it screwed the phone first time, to try and flash stock nokia 8 oreo rom in emergency download, it blocked fastboot command from powershell to enter edl mode after OST shat its pants again during flashing. Maybe qualcomm apps could'be been used to flash stock rom in windows from EDL mode, instead of the crappy nokia OST.
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.
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.
NEW: Install official Global ROM on Chinese TB132FU running ZUI 14 or Fake globalDISCLAMER: Flashing on TB132FU is pretty much safe and a hard brick has not occured yet, but do it at your own risk. If anything goes wrong you can return to ZUI 14 using one of the restoration methods listed on the FAQ thread. ALL YOUR FILES WILL BE DELETED. Make a backup of your personal files before proceeding.
Did my work help you? Be free to buy me a coffee. PayPal me at @alsbvg
Current version: TB132FU_S000094_221117_ROW
To see what works and what doesn't check below.
To flash this version you will need:
1 - A computer running Windows
2 - Flashtool (attached to the thread)
3 - ADB drivers or UsbDk drives & MTK drivers
4 - ZUI 14 installed on your TB132FU. If you have fake global you can flash as well, but having ZUI is recommended.
5 - Firmware file
6 - Attention to the really detailed tutorial below.
How to flash
Preparation:
1 - Download and install the drivers provided above. If you already have them installed skip this step.
2 - On your computer create a folder on your Desktop. Name it LENOVO.
3 - Download the firmware file (download link provided above) and un-zip it inside the LENOVO folder on your desktop. So inside your LENOVO folder now you should have a folder called TB132FU_S000094 Global.
4 - Download the attached flash tool and un-zip it inside the LENOVO folder on your desktop. Now you have a folder called TB132FU_S000094 Global and a folder called MTK_Flashtool.
5 - Power off your TB132FU and disconnect it from your computer in case you have it connected.
Flashing:
1 - Go to the LENOVO folder, and open the folder MTK-Flashtool. Inside this folder find flash_tool and double-click to open it.
2 - Once it opens click the TAB download. Do not click the green arrow.
3 - For the Download agent click Choose. Navigate to your Desktop > Lenovo > MT_Flashtool and select the file MTK_AllInOne_DA_onyx_signed
4- For Scatter-loading file click Choose. Navigate to your Desktop > Lenovo > TB132FU_S000094 Global and select MT6893_Android_scatter.txt. You will see two files with the same name. Click the one with the paper with lines icon. Wait for it to load.
5 - For Authentication File click Choose. Navigate to your Desktop > Lenovo > MT_Flashtool and select the file auth_sv5
6 - You will see white and green lines below. Scroll down and find the line that starts with lk_a and UNMARK it. All the other options should be marked, only lk_a should be unmarked.
Ex:
{
"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"
}
7 - Click the green arrow DOWNLOAD and plug in your tablet. Wait until it completes flashing the firmware.
And done. Once it is finished you can unplug your tablet and turn it on. You now should be running the latest global rom on your TB132FU;
What works:
Google Sync
HDR with true black
Productivity mode (PC mode)
And almost everything else. I'm still testing it.
What doesn't work:
OTA - once a new update is available it will be needed to be flashed manually losing all data. OTA did not work on a previous version.
Ultra-fast charging. It has Rapid charge but not the super fast charging available on ZUI
Some users reported L1 when flashing this global.
For users who lost L1 status, no solution to get it back from L3 yet. :/
"Scroll to the left" on the home screen to access the media center will not turn off even if you try manually setting it as off.
Time-zone issue: Factory reset it after the first boot to get it fixed.
You tell me what else is not working.
Thanks for the detailed explanation.
Some cuestions that you may have an answer for:
1. Has the bootloader to be unlock? What happens if I have the bootloader lock? (I lock mine with zui 14 in order to get L1)
2. Is there a way to change region code like in others lenovo models? Will it have any impact on OTAs?
3. Can you rollback to zui 14?
Thanks in advance. I think that will be able to have a full working rom with OTAs and L1 eventually. This is a huge step forward
als_bvg said:
What doesn't work:
Ultra fast charging. It has Rapidy charge but not the super fast charging available on ZUI
Click to expand...
Click to collapse
Out of curiosity, does the Chinese model have an Ultra fast charging?
My Global P11 Pro gen 2 does Rapid charge and my cable display caps out at 10w which I wouldn't say is rapid...
Same cable and charger gives me much faster speeds on my Galaxy S22U.
Pawnty said:
Out of curiosity, does the Chinese model have an Ultra fast charging?
My Global P11 Pro gen 2 does Rapid charge and my cable display caps out at 10w which I wouldn't say is rapid...
Same cable and charger gives me much faster speeds on my Galaxy S22U.
Click to expand...
Click to collapse
It does. The Chinese running ZUI has Ultra-fast charging with the original cable and charger.
tylerdanarg said:
Thanks for the detailed explanation.
Some cuestions that you may have an answer for:
1. Has the bootloader to be unlock? What happens if I have the bootloader lock? (I lock mine with zui 14 in order to get L1)
2. Is there a way to change region code like in others lenovo models? Will it have any impact on OTAs?
3. Can you rollback to zui 14?
Thanks in advance. I think that will be able to have a full working rom with OTAs and L1 eventually. This is a huge step forward
Click to expand...
Click to collapse
1 - You don't need the bootloader to be unlocked to flash this global version. I had Zui 14 with a locked bootloader and OEM locked, and the flashing worked. The OEM toggle will not be available once you use this version. It says you need to connect to the internet or contact your carrier.
2 - No way to change the region code so far. OTA will not work as described. It was tested on an older version. It will download and try to install but will fail. This is the latest rom so no OTA updates so far, we will have to wait to see if it will be the same.
3 - Yes, you can roll back to Zui 14. I did that quite a few times during my tests. Bricked the device more than 20 times and was always able to roll back to ZUI.
Thank you so much!
Generating User Accounts is working too? Wanted to use the tablet for the family, but ZUI doesn't offer accounts and Google Family doesn't work.
Hi. Thank you very much for the excellent work! Testing, so far so good. Do I have an L1 or am I misunderstanding something? Screenshot attached.
Thanks for the great work you do.
We have successfully implemented the global implementation.
My tablet is formatted with the SP Flash Tool. The serial number was lost at that time. (When I looked in the settings, the serial number was 0123456789ABCDEF.)
The serial number itself was recovered by rewriting the proinfo.bin. I think this formatting probably caused the Widevine-related settings to disappear and become L3.
I ask other L3 users, did you format with SP Flash Tool or python?
Flash mine today from ZUI 14 with bootloader lock, L1 and Google Play Certified to Global ROM and I kept L1, Google Certified Device and everything Is working. Even fast charging.
Thanks a lot! Let's see what happens when an OTA Will be available.
Hanswurstistda said:
Thank you so much!
Generating User Accounts is working too? Wanted to use the tablet for the family, but ZUI doesn't offer accounts and Google Family doesn't work.
Click to expand...
Click to collapse
I bought it for my daughter to use and have Family link for her Google Account and its all kinds of wonky (it shows my daughters account under Accounts then it vanishes. the only way I can add it back in is by signing into the Play store but then after an hour or so it goes. Works fine with my google account. Damn Family Link!)
(its on 14.0.413, and has an update pending for 14.0.640 ST). Not a clue how to check if its a modified ROM or what, but was going to try the above and see how it gets on.
Just to clarify fast charging Is shown on the screen but I don't if it's 10w ir 30w. I Will do some measures today and keep you posted
tylerdanarg said:
Just to clarify fast charging Is shown on the screen but I don't if it's 10w ir 30w. I Will do some measures today and keep you posted
Click to expand...
Click to collapse
Try the AccuBattery app, it may not be accurate, but it shows the charging current. I don't want to charge it yet. I will first discharge it and then install this app and start charging. It's convenient because it shows time to charge up to 100%.
daybreak7456 said:
Thanks for the great work you do.
We have successfully implemented the global implementation.
My tablet is formatted with the SP Flash Tool. The serial number was lost at that time. (When I looked in the settings, the serial number was 0123456789ABCDEF.)
The serial number itself was recovered by rewriting the proinfo.bin. I think this formatting probably caused the Widevine-related settings to disappear and become L3.
I ask other L3 users, did you format with SP Flash Tool or python?
Click to expand...
Click to collapse
Thanks for your input. I formated it before using the option "format + download" and serial number is now 012345678ABCDEF. I can try doing what you did with the file proinfo.bin. Any specific tutorial you used?
GeesRiK said:
I bought it for my daughter to use and have Family link for her Google Account and its all kinds of wonky (it shows my daughters account under Accounts then it vanishes. the only way I can add it back in is by signing into the Play store but then after an hour or so it goes. Works fine with my google account. Damn Family Link!)
(its on 14.0.413, and has an update pending for 14.0.640 ST). Not a clue how to check if its a modified ROM or what, but was going to try the above and see how it gets on.
Click to expand...
Click to collapse
Go to your settings menu. If you see the word ZUI anywhere, it's the Chinese model and you can flash the global if you want.
als_bvg said:
Go to your settings menu. If you see the word ZUI anywhere, it's the Chinese model and you can flash the global if you want.
Click to expand...
Click to collapse
Thanks! Yep, I have ZUI! I think its the family link attached to my daughters Google account that makes it annoying, but can't see any down sides in going to the Global to be honest. Can't get any worse... can it?!
GeesRiK said:
Thanks! Yep, I have ZUI! I think its the family link attached to my daughters Google account that makes it annoying, but can't see any down sides in going to the Global to be honest. Can't get any worse... can it?!
Click to expand...
Click to collapse
It shouldn't get any worse lol, but if your daughter is a kid you might benefit of a global rom, it has Kids space and the possibility of creating multiple users.
Awesome! Big thanks.
als_bvg said:
Thanks for your input. I formated it before using the option "format + download" and serial number is now 012345678ABCDEF. I can try doing what you did with the file proinfo.bin. Any specific tutorial you used?
Click to expand...
Click to collapse
What I did.
Install Python and mtkclient on a windows 10 computer.
python mtk rl --skip userdata "Destination path"
Backup everything but the user data with the above command
Open the backed up proinfo.bin with HxD and rewrite the serial number at the beginning.
python mtk wl "Destination path"
Flash the rewritten proinfo.bin with the above command.
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
Please check the commands and other information on the website.
I used to be able to do this, but I just tried it with a globalised tablet and it didn't work: the BROM mode (press power and volume plus simultaneously to connect the cable) is difficult to connect and even if it does, an error message appears and the process stops. When I get more time, I will switch back to zui14 and give it a try.
daybreak7456 said:
What I did.
Install Python and mtkclient on a windows 10 computer.
python mtk rl --skip userdata "Destination path"
Backup everything but the user data with the above command
Open the backed up proinfo.bin with HxD and rewrite the serial number at the beginning.
python mtk wl "Destination path"
Flash the rewritten proinfo.bin with the above command.
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
Please check the commands and other information on the website.
I used to be able to do this, but I just tried it with a globalised tablet and it didn't work: the BROM mode (press power and volume plus simultaneously to connect the cable) is difficult to connect and even if it does, an error message appears and the process stops. When I get more time, I will switch back to zui14 and give it a try.
Click to expand...
Click to collapse
Nice one! I can test it tomorrow. It's actually easier to pull the proinfo.bin file using MTK META Utility by using option Dump NV region. I was able to get and edit the file. Not sure how to flash it again on ZUI with a unlocked bootloader. But that's a start. I managed to get another Serial number by flashing another user's backup, but I still have L3, so might not be connected. I'll keep trying.
als_bvg said:
Nice one! I can test it tomorrow. It's actually easier to pull the proinfo.bin file using MTK META Utility by using option Dump NV region. I was able to get and edit the file. Not sure how to flash it again on ZUI with a unlocked bootloader. But that's a start. I managed to get another Serial number by flashing another user's backup, but I still have L3, so might not be connected. I'll keep trying.
Click to expand...
Click to collapse
I actually managed to get it back by flashing the edited proinfo.bin file using this command on ZUI with unlocked bootloader and OEM unlocked: fastboot flash proinfo proinfo.bin
Now let's see if it impacts or not L3. Testing...