Database Info

[RECOVERY] [UNOFFICIAL] [Phobos] TWRP 3.0.0-0 for the HP Slate 21

TWRP for the HP Slate 21 (phobos)
Code:
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* A lot.
*
TeamWin Recovery project (or TWRP for short) ported for the HP Slate 21 (s100 & k100).
Here are some 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"
}
Download
https://www.androidfilehost.com/?fid=24399994186369430
Install/Flashing Instructions:
1. You will need the following things in order to install TWRP on the Slate 21: 1 USB male to USB male connector, a computer with ADB and fastboot installed, common sense.
2. Turn off device and boot into fastboot mode (Volume Down + Power)
3. Connect your device to your computer by plugging one end of the USB cord into the lone USB port on the left-hand side of the device and the other end on any USB port on your computer.
4. Run the command “fastboot oem unlock” (no quotes)
5. Select yes on your Slate 21, after this step you will lose all your data. Vol Up to move Up, Vol Down to move Down, Brightness Up to select.
6. After fastboot has been unlocked, you’ll need to flash TWRP to your recovery. Do do this run the following command:
fastboot flash recovery /path/to/downloaded/TWRP.img
Replace /path/to/downloaded/TWRP.img with where you downloaded TWRP provided by me (Quaesar). You can drag and drop the IMG into Terminal/CMD to do this easily.
7. Use the buttons on the side of the device to select “Recovery”
8. Profit! You now have the latest TWRP on your device!
Cyanogenmod 12.1:
http://forum.xda-developers.com/general/general/rom-cyanogenmod-12-1-hp-slate-21-t3201416
Donations:
You can donate to me for my hard work through PayPal. My donation email is [email protected]. Any and all donations are welcome regardless of amount. Thanks for supporting me!
Direct link: https://www.paypal.me/Quaesar
Credits
Building this was a collaborative effort. The following developers/beta testers helped me provide you with this:
Quaesar (me): Main person, started project, etc etc.
UnjustifiedDev: Device tree, initial setup
SLATE21&MOTOG: Beta testing
Vocoderism: Beta testing
JonasFi: Beta testing
Seanichigo: k100 testing
If you have any comments or questions, reply to this thread and I'll get to you whenever I can
PLEASE HIT THAT THANKS BUTTON!!! IT REALLY SHOWS YOU APPRECIATE MY WORK!!!!!
Peace,
Quaesar

Changelog:
Public Release 1:
- First public release of recovery. Nothing major to see here
Known Issues/Bugs:
- CPU temperature will show up as 0 sometimes (it's usually 40-50*C if you're wondering)

FAQs:
Q: Bruhhhh, hook me up with dem sources
A: Dem sources can be found at teh GitHubs: (Link)
Q: Should I backup my stuff?
A: Do I need to answer that?
Q: What is this fastboot your speak of and how can I get it?
A: This video explains everything nicely: https://www.youtube.com/watch?v=maLWScgXflk
Q: On a scale of one to ten, how cool are you?
A: 11

Version 3 works very well. I also resolves an issue with using the swipe control from the previous version. Thanks Q!

device not found

Desparragosa said:
device not found
Click to expand...
Click to collapse
Check your connection (wire, computer, Slate). Make sure you have the correct fastboot drivers installed. I've seen an issue with the Windows 10 where Windows doesn't want to recognize or flash to the device. If you're comfortable, you may want to try using Ubuntu (I use 14.04). If you want, you can always contact me over Hangouts at [email protected]
Peace,
Quaesar

Quaesar said:
Check your connection (wire, computer, Slate). Make sure you have the correct fastboot drivers installed. I've seen an issue with the Windows 10 where Windows doesn't want to recognize or flash to the device. If you're comfortable, you may want to try using Ubuntu (I use 14.04). If you want, you can always contact me over Hangouts at [email protected]
Peace,
Quaesar
Click to expand...
Click to collapse
Hi. I can't do the unlock. Started with windows 10, and now with windows 8. Get the same message FAILED (command write failed (Unknown error))
don't know what else to try. Can you provide the fastboot drivers you used?
EDIT: Found the problem. Had to disable MTP!

rgomesf said:
Hi. I can't do the unlock. Started with windows 10, and now with windows 8. Get the same message FAILED (command write failed (Unknown error))
don't know what else to try. Can you provide the fastboot drivers you used?
EDIT: Found the problem. Had to disable MTP!
Click to expand...
Click to collapse
Nice! I use Ubuntu anyway so I would know about drivers haha

Hi there
Is there any other way of installing TWRP onto the HP Slate s/k100 21 without using a male to female usb connector?
Like rooting the Slate then flashing using something like the app Flashify? Booting off the SD card?
Thanks in advance

Hey there! I tried to install your recovery on my HP Slate 21, but although the fastboot output looks good to me:
seems I have already unlocked previously:
Code:
$ sudo fastboot oem unlock
...
(bootloader) Bootloader is already unlocked.
OKAY [ 0.025s]
finished. total time: 0.025s
And flashing the recovery also seems like it works fine:
Code:
$ sudo fastboot flash recovery TWRP_3.0.0-0_phobos_Quaesar.img
target reported max download size of 641728512 bytes
sending 'recovery' (9256 KB)...
OKAY [ 0.329s]
writing 'recovery'...
OKAY [ 0.562s]
finished. total time: 0.892s
But when I boot into recovery afterwards I get not TWRP but a stock recovery that will not flash your cyanogenmod because it cannot verify it.

Apad121 said:
Hi there
Is there any other way of installing TWRP onto the HP Slate s/k100 21 without using a male to female usb connector?
Like rooting the Slate then flashing using something like the app Flashify? Booting off the SD card?
Thanks in advance
Click to expand...
Click to collapse
If you can get root then yeah it's good. However finding a way to root without a wire to connect to the computer is kinda hard. My suggestion is to skip that and just twist two male usb cables together
@kaefert, try locking and unclocking the bootloader. If that doesn't work wipe the recovery partition then flash it

Quaesar said:
If you can get root then yeah it's good. However finding a way to root without a wire to connect to the computer is kinda hard. My suggestion is to skip that and just twist two male usb cables together
@kaefert, try locking and unclocking the bootloader. If that doesn't work wipe the recovery partition then flash it
Click to expand...
Click to collapse
Thanks but I have already bought the cable and flagged TWRP on. I have also tried out your cm ROM.

I could use some advice. I enabled the USB developer option, when the cable is connected to my booted HP slate the ADB command window on my laptop works. I was able to send command adb reboot bootloader to reboot the Slate into the bootloader but once I get there, the cable disconnects from the Slate so I can't do the fastbook unlock command. Any tips ?

when I run the fastboot flash recovery /path/to/downloaded/TWRP.img command
error appears: can not open '/path/to/downloaded/TWRP.img'

im having issues installing TWRP on Slate21
hi, its been a while since I touched anything android, so its probably no surprise im having problems here! lol, anyhow, ive got a Slate 21 stuck on the 'HP Slate Android' boot screen and wanted to reflash it, so I follow the instructions here, and I get as far as the point where you flash TWRP and I get a problem and it doesn't flash?
this is what it says when I try>>>>>
Target reported Max download size of 641728512 bytes
error: cannot load 'c:\TWRP.img' : No error
obviously ive placed the TWRP.img on the root drive, am I doing something wrong here? have I got the wrong ADB driver? any help will be greatly appreciated. thanks Dee

HP Slate 21-s100
Turn off device and boot into fastboot mode - OK
Connect your device to your computer by plugging USB male to USB male connector - OK
Run the command “fastboot oem unlock” - OK
fastboot oem unlock
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 19.503s]
Finished. Total time: 19.504s
fastboot flash recovery /path/to/downloaded/TWRP.img - OK
Use the buttons on the side of the device to select “Recovery” - OK
Profit! You now have the latest TWRP on your device! - NOPE! :crying: I see the original hp Android System Recovery :crying: WHY?
I was worng, Where am I doing wrong?

I did it the way you say here.
then i wanted to change the software.
i got this error.
I did something wrong.
I am installing twrp but it won't open.
Pressing volume + volume - power keys comes here.
I would be glad if you could help.
Thanks

[Guide] Fix and Re-Locking Bootloader From Fake UBL

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

Converted J9110 to J8170 - VoLTE working on tmobile (US)

I got the J9110 from WondaMobile (hk) a couple weeks ago. Finally saw that the J8170's US firmware is out on Xperifirm, so I downloaded and flashed it. VoLTE works on Tmobile! Only downside is that 2nd sim isn't in the settings option, and unsure if it works. I use 1 sim + microsd card anyway.
Photos here: https://imgur.com/7LjnwCC

iArvee said:
I got the J9110 from WondaMobile (hk) a couple weeks ago. Finally saw that the J8170's US firmware is out on XDA, so I downloaded and flashed it. VoLTE works on Tmobile! Only downside is that 2nd sim isn't in the settings option, and unsure if it works. I use 1 sim + microsd card anyway.
Click to expand...
Click to collapse
Would you please share the download link of the J8170 firmware?

oh damn !!! nice ! how u flashed it
?

EmrickX51 said:
Would you please share the download link of the J8170 firmware?
Click to expand...
Click to collapse
On xda search for Xperifirm app. This can download Sony fw
avetny said:
oh damn !!! nice ! how u flashed it
?
Click to expand...
Click to collapse
On xda search for newflasher app

Thank you !!! Gonna do it tonight
---------- Post added at 11:10 AM ---------- Previous post was at 10:57 AM ----------
VeixES said:
On xda search for newflasher app
Click to expand...
Click to collapse
Friend one more question, did u flashed all frimware folder ? Or you move something out of folder ? (Im also on tmobile lmao)
Regards
Avi

avetny said:
Thank you !!! Gonna do it tonight
---------- Post added at 11:10 AM ---------- Previous post was at 10:57 AM ----------
Friend one more question, did u flashed all frimware folder ? Or you move something out of folder ? (Im also on tmobile lmao)
Regards
Avi
Click to expand...
Click to collapse
You can take userdata.sin file out. keep everything else

VeixES said:
You can take userdata.sin file out. keep everything else
Click to expand...
Click to collapse
Thank u friend!!!!

avetny said:
Thank you !!! Gonna do it tonight
---------- Post added at 11:10 AM ---------- Previous post was at 10:57 AM ----------
Friend one more question, did u flashed all frimware folder ? Or you move something out of folder ? (Im also on tmobile lmao)
Regards
Avi
Click to expand...
Click to collapse
It'd be best if you also flash the userdata.sin file. Since we're flashing a different variant, it'd be best to wipe everything clean. Taking out userdata will keep data intact.

iArvee said:
It'd be best if you also flash the userdata.sin file. Since we're flashing a different variant, it'd be best to wipe everything clean. Taking out userdata will keep data intact.
Click to expand...
Click to collapse
Oh im that kind of guy who factory reset (with full wipe/format) every time after frimware update via network lol !
Thank you I'll definitely flash data and on top I'll factory reset manually from the settings one more time lmao

damn guys hate to be a noob but im getting error in my newflasher.exe window.
--------------------------------------------------------
newflasher.exe v17 by Munjeni @ 2017/2019
--------------------------------------------------------
Determining available free space by GetDiskFreeSpaceEx:
Available space to caller = 822419 MB
Total space on current drive = 953766 MB
Free space on drive = 822419 MB
Optional step! Type 'y' and press ENTER if you need GordonGate flash driver, or
type 'n' to skip.
This creates GordonGate.7z archive in the same dir with newflasher.exe!
n
Device path: \\?\usb#vid_0fce&pid_b00b#5&29cad4f4&0&1#{a5dcbf10-6530-11d2-901f-0
0c04fb951ed}
Class Description: Android Device
Device Instance Id: USB\VID_0FCE&PID_B00B\5&29CAD4F4&0&1
Optional step! Type 'y' and press ENTER if you want dump trim area, or type 'n'
and press ENTER to skip.
Do in mind this doesn't dump drm key since sake authentifiction is need for that
!
n
ERROR: GetOverLapped_out_Result: failed with error code 1 as follows:
Incorrect function.
- Error write! Need nBytes: 0x18 but done: 0x0
nBytes[0x0]:
- Error writing command getvar:max-download-size!
End. You can disconnect your device when you close newflasher.exe
Press any key to continue . . .
1) installed drivers via Xperia Companion. (make sure they all installed everywhere)
2) downloaded J8170_Customized US_1318-8742_55.0.A.2.278_R13A
3)Placed newflasher_v17 files in to J8170_Customized US_1318-8742_55.0.A.2.278_R13A
4) Run as administrator and getting that error. (adb devices showing my phone, is mean drivers installed !)
Damn !

Guys hate to be a noob but im getting error in my newflasher.exe window.
ERROR: GetOverLapped_out_Result: failed with error code 1 as follows:
Incorrect function.
- Error write! Need nBytes: 0x18 but done: 0x0
nBytes[0x0]:
- Error writing command getvar:max-download-size!
End. You can disconnect your device when you close newflasher.exe
Press any key to continue . . .
1) installed drivers via Xperia Companion. (make sure they all installed everywhere)
2) downloaded J8170_Customized US_1318-8742_55.0.A.2.278_R13A
3)Placed newflasher_v17 files in to J8170_Customized US_1318-8742_55.0.A.2.278_R13A
4) Run as administrator and getting that error. (adb devices showing my phone too)
Any ideas gentlemens?

avetny said:
damn guys hate to be a noob but im getting error in my newflasher.exe window.
--------------------------------------------------------
newflasher.exe v17 by Munjeni @ 2017/2019
--------------------------------------------------------
Determining available free space by GetDiskFreeSpaceEx:
Available space to caller = 822419 MB
Total space on current drive = 953766 MB
Free space on drive = 822419 MB
Optional step! Type 'y' and press ENTER if you need GordonGate flash driver, or
type 'n' to skip.
This creates GordonGate.7z archive in the same dir with newflasher.exe!
n
Device path: \\?\usb#vid_0fce&pid_b00b#5&29cad4f4&0&1#{a5dcbf10-6530-11d2-901f-0
0c04fb951ed}
Class Description: Android Device
Device Instance Id: USB\VID_0FCE&PID_B00B\5&29CAD4F4&0&1
Optional step! Type 'y' and press ENTER if you want dump trim area, or type 'n'
and press ENTER to skip.
Do in mind this doesn't dump drm key since sake authentifiction is need for that
!
n
ERROR: GetOverLapped_out_Result: failed with error code 1 as follows:
Incorrect function.
- Error write! Need nBytes: 0x18 but done: 0x0
nBytes[0x0]:
- Error writing command getvar:max-download-size!
End. You can disconnect your device when you close newflasher.exe
Press any key to continue . . .
1) installed drivers via Xperia Companion. (make sure they all installed everywhere)
2) downloaded J8170_Customized US_1318-8742_55.0.A.2.278_R13A
3)Placed newflasher_v17 files in to J8170_Customized US_1318-8742_55.0.A.2.278_R13A
4) Run as administrator and getting that error. (adb devices showing my phone, is mean drivers installed !)
Damn !
Click to expand...
Click to collapse
Try using the drivers from flashtool.

iArvee said:
Try using the drivers from flashtool.
Click to expand...
Click to collapse
Oh i didn't tried that way ! Thank u

Thanks.
Flashed J8170 customized us firmware to my J8110 few minutes ago, the t-mobile volte worked.
{
"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"
}

xzent said:
Thanks.
Flashed J8170 customized us firmware to my J8110 few minutes ago, the t-mobile volte worked.
Click to expand...
Click to collapse
Gonna drive to new York help me out to flash it ?

avetny said:
Gonna drive to new York help me out to flash it ?
Click to expand...
Click to collapse
If you need help flashing, feel free to send me a PM.

iArvee said:
If you need help flashing, feel free to send me a PM.
Click to expand...
Click to collapse
oh man, thank you very much for your kind :highfive:
---------- Post added at 12:48 PM ---------- Previous post was at 12:04 PM ----------
iArvee said:
Try using the drivers from flashtool.
Click to expand...
Click to collapse
you was right ! i switched USB ports (choose the new one) , and installed drivers from GordonGate.
it went true ! Thank you friend !

Does anyone know if J8110 and J9110 share the same hardware? Guess I'm asking if it's possible to flash J9110 firmware on J8110 to get dual sim functionality?
Sent from my J8110 using Tapatalk

lepszy said:
Does anyone know if J8110 and J9110 share the same hardware? Guess I'm asking if it's possible to flash J9110 firmware on J8110 to get dual sim functionality?
Sent from my J8110 using Tapatalk
Click to expand...
Click to collapse
They have the same hardware, except for the modem I'm guessing. You only have 1 IMEI number, so you won't be able to use the 2nd sim. You can flash the firmware, but 2nd sim most likely won't work.

May anyone confirm if Verizon is working on non-J8170 devices flashed to J8170? I got a J9110 and I'm thinking of flashing it to J8170 for Verizon support, but if it doesn't work for calls and text it will be useless : ( Thanks for any help!

Tutorial flashing GSI image for Oukitel K9

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.

[Guide][GSI][13] GSI Install Guide for ROG Phone zs600kl

{
"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"
}
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Introduction​ROG Phone 1 is no longer receiving any update since android 9 and no custom rom were made, which is sad since s845 is still a well performed CPU even now. However, by the help of Project Treble, we're able to install the latest android 12 (and so on) on this device.
The guide requires some basic knowledges of using SDK Platform Tools and recovery. But feel free to ask if you don't understand anything.
Hardware support​
ComponentCommentCameraWorksSpeaker / MicWorksBluetoothWorks** (Bluetooth in call, all Bluetooth codec supported by the hardware) *(No A2DP)
(Update: All bluetooth functions was now fixed on A13 and above)WiFiWorksSIM / Mobile Data / VoiceWorksVoLTEUnknownFingerprintWorks (see "workarounds and recommendations" to enable fingerprint wakeup)NFCWorksOffline ChargingBroken90Hz Refresh RateWorksAuto-brightnessWorks (May depend on the Rom)Proximity sensorWorksVibrationBrokenRGB backlight on the logoWorks* (Basic functions with an app on google play) *(Will need to set the light again whenever restart the phone)HDR content playbackBroken (Have some wired lines on the screen)
Steps to install​We have 2 ways to install, either through Fastboot or with TWRP. For data safety, I do not recommend break the force encryption whatsoever.
Make sure to Unlock Bootloader before proceeding any further!
A. Install through fastboot:
1. Extract vbmeta.img from the offical rom you're running.​
File attached is from version "WW-16.0420.2009.39", so upgrade to this version if you dont know how to extract vbmeta.img.
2. To disable dm-verity, do "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img".​3. Flash the gsi you choose in fastboot. Do "fastboot flash system (system image name.img)" .​4. Reboot to offical recovery and do a factory reset.​5. You are good to go!​
If you wish to use Magisk (I recommend Lygisk over Magisk since these gsi are force encryped), patch the boot image extract from the offical rom and flash it through Fastboot.
You can also boot to TWRP without flash it onto the device and use adb sideload to install zips, not recommend if you don't know what I'm talking about!
B. Install through TWRP:
1. Extract vbmeta.img from the offical rom you're running.​
File attached is from version "WW-16.0420.2009.39", so upgrade to this version if you dont know how to extract vbmeta.img.
2. To disable dm-verity, do "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img".​3. Flash the TWRP(attached) in fastboot. Do "fastboot flash boot twrp-3.4.0-0-Z01Q-16.0410.2003.24.img" .​4. Reboot to TWRP. Do "fastboot oem reboot-recovery".​5. Format data, cache and system parition in recovery.​6. Flash the gsi you choose in recovery. (flash the "image" into "system partition").​7. Flash any modification zips now.​8. (Optional) Flash "disforsenc_daisy__zero.zip"(attached) in TWRP to disable force encryption.​
It is not recommend to do this step if you really care about your data safety. If someone get your phone, they will be able to access all the files.
9. You are good to go!​
You can still use adb sideload to install zips(and lots of other functions) without disable force encryption. So it's really not recommend to disable it.
Workarounds and Recommendations​
To fix Bluetooth not opening or other Bluetooth related issue, refer to this guide I made. You will need Magisk to enable Aptx. This should NOT be needed anymore, since A13 builds have fix this.
Recommend to use this Gcam. It can utilize all the camera moudules and it's stable.
If you have any problem with mobile network/phone call, try to install and enable the ims apk in "phh/IMS features".
Most builds based on phh's build(which were listed on the wiki page) have a working safetynet, and the Universal Safetynet Fix will work with Magisk installed.
However some of them are still broken. So make sure the safety net is working without Magisk, then install Magisk.
RGB backlight of the ROG logo in the back can be control with this app found in google play. It's not made for this device, but basic functions will work.
My personal recommendation of gsi is crDroid maintain by Nazim. It have working safetynet and lots of customizable features I like. (Especially it can get rid of the search bar and at a glance which I HATE A LOT)
If you do want to enable fingerprint sensor while screen is off, set these two props using adb.
Code:
persist.asus.fp.wakeup=true
If you do want to use bottom usb port rather than the one on the side, set this prop. Also, to go back to the bottom one, set it to a600000.dwc3 .
Code:
persist.vendor.usb.controller.default=a800000.dwc3
If you do want to use double tab to wake, enable related settings in the GSI you use (also settings in "phh treble settings") if needed, and set this prop.
Code:
persist.asus.dclick=1
Credits​Rocky7842​xspx for testing the device with me​Numerous people and threads on the forum for some workaround or inspiration
And all the other devs for creating these wonderful modules/ROMs​

reserved

whats ver. i download from crDroid ??
crDroid-8.8-a64_bgN-slim-Unofficial.img.xz2022-09-03917.6 MB
69crDroid-8.8-a64_bgN-Unofficial.img.xz2022-09-031.1 GB
60crDroid-8.8-a64_bvN-Unofficial.img.xz2022-09-03756.4 MB
45crDroid-8.8-arm64_bgN-slim-Unofficial.img.xz2022-09-031.1 GB
268crDroid-8.8-arm64_bgN-Unofficial.img.xz2022-09-031.3 GB
523crDroid-8.8-arm64_bvN-Unofficial.img.xz2022-09-03944.5 MB
230
a64 or arm64 ?
bgN-slim , bgN or bvN ??

Dj.GriM said:
whats ver. i download from crDroid ??
crDroid-8.8-a64_bgN-slim-Unofficial.img.xz2022-09-03917.6 MB
69crDroid-8.8-a64_bgN-Unofficial.img.xz2022-09-031.1 GB
60crDroid-8.8-a64_bvN-Unofficial.img.xz2022-09-03756.4 MB
45crDroid-8.8-arm64_bgN-slim-Unofficial.img.xz2022-09-031.1 GB
268crDroid-8.8-arm64_bgN-Unofficial.img.xz2022-09-031.3 GB
523crDroid-8.8-arm64_bvN-Unofficial.img.xz2022-09-03944.5 MB
230
a64 or arm64 ?
bgN-slim , bgN or bvN ??
Click to expand...
Click to collapse
arm64 versions are all fine.

I got a rog phone 1 for a little more than a year now or so, its nice to see that we can at least have a update even if its not oficial. Im getting tyred of the same look of the UI and the aod, my god the stock ones are horrible but if i use another app for the aod it just drains the battery so fk quick. I will give a try to the pixel experience gsi

Microsoft Windows [Version 10.0.19044.2006]
(c) Microsoft Corporation. All rights reserved.
C:\platform-tools>fastboot.exe devices
K7AZGV03070237J fastboot
C:\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.030s
C:\platform-tools>fastboot flash system C:\platform-tools\crDroid-8.9-arm64_bgN-Unofficial.img
Sending sparse 'system_b' 1/7 (521508 KB) OKAY [ 12.520s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 2/7 (523009 KB) FAILED (remote: 'Error: Last flash failed : Volume Full')
fastboot: error: Command failed
C:\platform-tools>
i got error !!

Dj.GriM said:
Microsoft Windows [Version 10.0.19044.2006]
(c) Microsoft Corporation. All rights reserved.
C:\platform-tools>fastboot.exe devices
K7AZGV03070237J fastboot
C:\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.030s
C:\platform-tools>fastboot flash system C:\platform-tools\crDroid-8.9-arm64_bgN-Unofficial.img
Sending sparse 'system_b' 1/7 (521508 KB) OKAY [ 12.520s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 2/7 (523009 KB) FAILED (remote: 'Error: Last flash failed : Volume Full')
fastboot: error: Command failed
C:\platform-tools>
i got error !!
Click to expand...
Click to collapse
i fixed now i chaneg the rom to another rom slim and working now
how to patch the boot image for lygisk ?? from offical rom asus rog phone ASUS_Z01QD or from crDroid-8.9-arm64_bgN-slim-Unofficial.img
i want to fix the bluetooth is not working now !
sorry for thats i am noob

Dj.GriM said:
i fixed now i chaneg the rom to another rom slim and working now
how to patch the boot image for lygisk ?? from offical rom asus rog phone ASUS_Z01QD or from crDroid-8.9-arm64_bgN-slim-Unofficial.img
i want to fix the bluetooth is not working now !
sorry for thats i am noob
Click to expand...
Click to collapse
First of all, since the system partition on this phone is designed for android 8/9, it didn't leave much spare space. So a lot of highly modified gsi is too big for the phone. If you wish to flash them, you'll need to follow along this guide to resize partitions (tested and work).
As for the lygisk (magisk) part, take the boot image of the stock ROM you were running (the exact same version is recommended), and use the app to patch the boot.img.
Or if you have installed TWRP, simply flash the zip file through TWRP. If it's encrypted, flash it through adb sideload and it'll be fine too.

does this still apply until date? is it worth it? does upgrading it will make my device performs better? dont get me wrong, i really want to upgrade, but i just need more insights.

edzraaa said:
does this still apply until date? is it worth it? does upgrading it will make my device performs better? dont get me wrong, i really want to upgrade, but i just need more insights.
Click to expand...
Click to collapse
Yes, the guide is still valid for now.
The performance overall is pretty good.
If what I mentioned that's not working is acceptable for you, I would recommend you to try it out. Plus you can always revert it to stock.

Rocky7842 said:
Yes, the guide is still valid for now.
The performance overall is pretty good.
If what I mentioned that's not working is acceptable for you, I would recommend you to try it out. Plus you can always revert it to stock.
Click to expand...
Click to collapse
Which version would you recommend based on the builds now?
I'm using it most for games and daily use. The reason i wanna upgrade is i noticed the game i played started to become laggy and it was not 60fps like it used to after update and update so I dont think it is optimized for the phone? The FPS drops when theres a teamfight. The game run SMOOTHLY on my friends phone which specs is lower than my ROG Phone 1. But his phone run on Android 11 if im not mistaken which i got an idea maybe its the Android version that have something to do with optimization?
I have the latest stock version same as yours stated in the post above. And your guide recommended crDroid which was Android 12 (at that time and it was crDroid 8.8 based on the user above) but that was last year. And by A13 fixed the Bluetooth thingy, by A13 does that mean Android 13? I'm having trouble to choose which ROMs. Or should I just upgrade to Android 12?
Sorry for asking but i just wanna be safe and Thank you for your time. Appreciate it

edzraaa said:
Which version would you recommend based on the builds now?
I'm using it most for games and daily use. The reason i wanna upgrade is i noticed the game i played started to become laggy and it was not 60fps like it used to after update and update so I dont think it is optimized for the phone? The FPS drops when theres a teamfight. The game run SMOOTHLY on my friends phone which specs is lower than my ROG Phone 1. But his phone run on Android 11 if im not mistaken which i got an idea maybe its the Android version that have something to do with optimization?
I have the latest stock version same as yours stated in the post above. And your guide recommended crDroid which was Android 12 (at that time and it was crDroid 8.8 based on the user above) but that was last year. And by A13 fixed the Bluetooth thingy, by A13 does that mean Android 13? I'm having trouble to choose which ROMs. Or should I just upgrade to Android 12?
Sorry for asking but i just wanna be safe and Thank you for your time. Appreciate it
Click to expand...
Click to collapse
There are crDroid 9 A13 builds maintain by Nazim.
I'd recommend you to try different ROMs and versions to see which one serve you the best.

i cant seems to get my wifi to work on crDroid. NEED HELP! Its on the latest crDroid. Or is it just me?

edzraaa said:
i cant seems to get my wifi to work on crDroid. NEED HELP! Its on the latest crDroid. Or is it just me?
Click to expand...
Click to collapse
Welp, i think i F'd it up . Do i need to do the vbmeta.img everytime? And im not sure what to do now. Changing back to partition A stuck on ROG loading. Since i f'd up i might play around and see what i can do.
UPDATE: I got it to work finally. Flashed EVERYTHING back to "WW-16.0420.2009.39" payload.bin incase you got an error and get stucked (bootloop, wont boot). THEN follow the steps above WITH NO MISTAKES!

I need to unlock the bootloader of my rog 1, but do you guys know how? The unlocktool.apk asus has provided is not working anymore

Yusop said:
I need to unlock the bootloader of my rog 1, but do you guys know how? The unlocktool.apk asus has provided is not working anymore
Click to expand...
Click to collapse
That is the only way AFAIK. Try to contact Asus for help.