Related
Just saw this on Twitter https://twitter.com/topjohnwu/status/1053488124389720064?s=20 any guides out yet ? Not sure where to get started other than having a unlocked bootloader. Had a pixel 2xl not sure if same steps as in booting into twrp and then flashing twrp etc etc
just give it some time.
plus, there is a section for q&a and I think you are asking a question.
I'm pretty sure it'll be just like the pixel 2 XL the tools just needed to be updated for the new device
Sent from my Pixel 2 XL using Tapatalk
Magisk 17.3-e1a65276 failed fastboot P3XL; error booting boot.img
Huge thanks for topJohnWu for his amazingly prompt Magisk update! I'm hopeful we'll see a working version of this quickly enter the Beta or Stable channels.
I've set my Magisk update channel to Custom, and successfully upgraded my P2XL to Magisk 17.3-e1a65276, but this is NOT yet working for my P3XL.
Canary Channel "How to"; (circa 2018-Oct)
Open Magisk Settings : UpdateChannel : Custom
paste the url (after removing spaces) ;
https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/canary.json
https :// raw.githubusercontent.com /topjohnwu /magisk_files /master /canary_builds /canary.json
Patched File sizes:
When patching "boot.img", I'm not seeing major discrepancy between input and output file sizes ; P2XL compared with P3XL. Both patched_boot.img file sizes are significantly smaller than original.
P2XL (2018.10.ppr2)
boot.img; 40 MB (41,943,040 bytes)
17.3 patched_boot.img; 24 MB (25,321,472 bytes)
P3XL (2018.07.pd1a)
boot.img; 64 MB (67,108,864 bytes)
17.3 patched_boot.img; 30 MB (30,953,472 bytes)
Failed ">fastboot flash boot patched_boot.img":
When attempting to reboot, following successful "flashboot boot patched_boot.img" command, the P3XL fails to load the patched_boot.img file, citing cause as "error booting boot.img" (See attached)
Recovery:
Issuing "fastboot flash boot boot.img", using the originally extracted factory boot.img file, restores expected boot behaviour, albeit without root.
mzterina said:
Huge thanks for topJohnWu for his amazingly prompt Magisk update! I'm hopeful we'll see a working version of this quickly enter the Beta or Stable channels.
I've set my Magisk update channel to Custom, and successfully upgraded my P2XL to Magisk 17.3-e1a65276, but this is NOT yet working for my P3XL.
Canary Channel "How to"; (circa 2018-Oct)
Open Magisk Settings : UpdateChannel : Custom
paste the url (after removing spaces) ;
https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/canary.json
https :// raw.githubusercontent.com /topjohnwu /magisk_files /master /canary_builds /canary.json
Patched File sizes:
When patching "boot.img", I'm not seeing major discrepancy between input and output file sizes ; P2XL compared with P3XL. Both patched_boot.img file sizes are significantly smaller than original.
P2XL (2018.10.ppr2)
boot.img; 40 MB (41,943,040 bytes)
17.3 patched_boot.img; 24 MB (25,321,472 bytes)
P3XL (2018.07.pd1a)
boot.img; 64 MB (67,108,864 bytes)
17.3 patched_boot.img; 30 MB (30,953,472 bytes)
Failed ">fastboot flash boot patched_boot.img":
When attempting to reboot, following successful "flashboot boot patched_boot.img" command, the P3XL fails to load the patched_boot.img file, citing cause as "error booting boot.img" (See attached)
Recovery:
Issuing "fastboot flash boot boot.img", using the originally extracted factory boot.img file, restores expected boot behaviour, albeit without root.
Click to expand...
Click to collapse
I don't know if this will work. Did you try renaming the patched boot image to just boot.img and then fastboot it.
---------- Post added at 10:23 PM ---------- Previous post was at 10:16 PM ----------
I don't think topjohn pushed the changes to git yet? Does anyone know?
@mzterina what url did you use for custom update channel?
lollyjay said:
@mzterina what url did you use for custom update channel?
Click to expand...
Click to collapse
It's in his post. Just remove the spaces. I got the same error as he did.
So it's not ready?
TheUndertaker21 said:
So it's not ready?
Click to expand...
Click to collapse
Not yet.
Edit: Log shows install Magisk Manager using MagiskBoot v17.3-e8e39e0f(17203) (by topjohnwu) - Boot Image Modification Tool instead of e1a65276(17204) like the downloaded zip.
Coming soon. Yummy ?
For those having trouble setting their Update Channel to Canary:
Canary Channel "How to"; (circa 2018-Oct)
Open Magisk Settings : UpdateChannel : Custom
paste the url (after removing spaces) ;
https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/canary.json
https :// raw.githubusercontent.com /topjohnwu /magisk_files /master /canary_builds /canary.json
maybe the attached images can overcome whatever wrinkles are happening with copy/paste?
As regards file names:
You can name your patched boot.img file whatever you like on your local PC file system. Syntax suggested by Magisk itself is "patched_boot.img" but you can clip that to just "boot.img" or rename the file to include the build and Magisk version, such as "20180720pda1_17.3_patched_boot.img". The local filename simply identifies the data source, to be transferred by fastboot, to the boot_a (or boot_b) partition.
I found it interesting that screenshots from the P3XL show little notchyness! They simply don't show status bar info where the notch is. Compare the two Magisk screenshots; P2XL with 17.3 installed, and P3XL without. The only hint of nachos is the absence of status stuff.
mzterina said:
For those having trouble setting their Update Channel to Canary:
Canary Channel "How to"; (circa 2018-Oct)
Open Magisk Settings : UpdateChannel : Custom
paste the url (after removing spaces) ;
https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/canary.json
https :// raw.githubusercontent.com /topjohnwu /magisk_files /master /canary_builds /canary.json
maybe the attached images can overcome whatever wrinkles are happening with copy/paste?
As regards file names:
You can name your patched boot.img file whatever you like on your local PC file system. Syntax suggested by Magisk itself is "patched_boot.img" but you can clip that to just "boot.img" or rename the file to include the build and Magisk version, such as "20180720pda1_17.3_patched_boot.img". The local filename simply identifies the data source, to be transferred by fastboot, to the boot_a (or boot_b) partition.
I found it interesting that screenshots from the P3XL show little notchyness! They simply don't show status bar info where the notch is. Compare the two Magisk screenshots; P2XL with 17.3 installed, and P3XL without. The only hint of nachos is the absence of status stuff.
Click to expand...
Click to collapse
I'm old, your thorough juniorness is very welcome. Thanks. ?
This truncated address is what you use for canary,
https://bit.ly/2MPKGY5
mzterina said:
For those having trouble setting their Update Channel to Canary:
Canary Channel "How to"; (circa 2018-Oct)
Open Magisk Settings : UpdateChannel : Custom
paste the url (after removing spaces) ;
https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/canary.json
https :// raw.githubusercontent.com /topjohnwu /magisk_files /master /canary_builds /canary.json
maybe the attached images can overcome whatever wrinkles are happening with copy/paste?
As regards file names:
You can name your patched boot.img file whatever you like on your local PC file system. Syntax suggested by Magisk itself is "patched_boot.img" but you can clip that to just "boot.img" or rename the file to include the build and Magisk version, such as "20180720pda1_17.3_patched_boot.img". The local filename simply identifies the data source, to be transferred by fastboot, to the boot_a (or boot_b) partition.
I found it interesting that screenshots from the P3XL show little notchyness! They simply don't show status bar info where the notch is. Compare the two Magisk screenshots; P2XL with 17.3 installed, and P3XL without. The only hint of nachos is the absence of status stuff.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
are we going to have a direct post from him? @topjohnwu
dnsmo said:
are we going to have a direct post from him? @topjohnwu
Click to expand...
Click to collapse
Yes. It's released! Go check magisk beta thread
---------- Post added at 04:45 AM ---------- Previous post was at 04:44 AM ----------
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page5
Time for everyone to reward Top John!
https://www.patreon.com/topjohnwu
https://www.paypal.me/topjohnwu
https://github.com/topjohnwu/Magisk/releases
I am ****ed now, after I install the patch_boot.img, the wifi and sim is not working help, do you need to unlock the bootloader? which I did.
guys, I don't think it's working for me, at least the unlock version is not working. I had to re-lock the bootloader in order for the phone to function. I can't install magdisk, after I apply the patch_boot.img its not working.
radionerd said:
Time for everyone to reward Top John!
https://www.patreon.com/topjohnwu
https://www.paypal.me/topjohnwu
https://github.com/topjohnwu/Magisk/releases
View attachment 4623609
Click to expand...
Click to collapse
hmm says remote partition not found when i try to flash the patched boot img.....
dnsmo said:
I am ****ed now, after I install the patch_boot.img, the wifi and sim is not working help, do you need to unlock the bootloader? which I did.
guys, I don't think it's working for me, at least the unlock version is not working. I had to re-lock the bootloader in order for the phone to function. I can't install magdisk, after I apply the patch_boot.img its not working.
Click to expand...
Click to collapse
elreydenj said:
hmm says remote partition not found when i try to flash the patched boot img.....
Click to expand...
Click to collapse
Both of you; if you want help, you're going to have to supply more information. What did you do? What files did you use? What were your exact steps?
Sent from my crosshatch using XDA Labs
ridobe said:
Both of you; if you want help, you're going to have to supply more information. What did you do? What files did you use? What were your exact steps?
Click to expand...
Click to collapse
I utilized the command fastboot flash boot patched_boot.IMG. instead I changed it to flash boot_a and also flashed it to boot_b and now all is well .
This is a stop-gap solution until we get a fully working TWRP with data decryption on the OnePlus 7T Pro 5G McLaren.
Tutorial video here (up to 4K; fullscreen recommended): https://youtu.be/rNwyb_gaByE
requirements:
*OnePlus 7T Pro 5G McLaren (HD1925)
*bootloader unlocked
*USB connected to PC with adb/fastboot
installation:
fastboot getvar all
(look for the (bootloader) current-slot text)
fastboot flash recovery_a recovery_11.0.1.4_adb_nosec.img
or
fastboot flash recovery_b recovery_11.0.1.4_adb_nosec.img
usage:
adb shell
removal:
fastboot getvar all
(look for the (bootloader) current-slot text)
fastboot flash recovery_a recovery_11.0.1.4.img
or
fastboot flash recovery_b recovery_11.0.1.4.img
recovery_11.0.1.4_adb_nosec.img.zip
https://drive.google.com/file/d/1iq-LyWItf1P_0LdoGs5WKaH79TX849G6/view?usp=sharing
recovery_11.0.1.4.img.zip
https://drive.google.com/file/d/1NhVeCjunEJ2X4cdyPuHbxTISu91uTR6H/view?usp=sharing
OLD
recovery_11.0.1.3_adb_nosec.img.zip
https://drive.google.com/file/d/1sxZGQpXG_Fk-yK4NZmB6Im8wSxlcbSPZ/view?usp=sharing
recovery_11.0.1.3.img.zip
https://drive.google.com/file/d/1LDydnV4fdTFbzPD2orZycaYUeSeYYnT-/view?usp=sharing
recovery_11.0.1.2_adb_nosec.img.zip
https://drive.google.com/file/d/1J0jQXJhKmEiH9sLExUPb1arehXeMQGWn/view?usp=sharing
recovery_11.0.1.2.img.zip
https://drive.google.com/file/d/1Avb2y9bc0oZGVMBS40BXQ-_-efzWNJyj/view?usp=sharing
recovery_10.0.43_adb_nosec.img.zip
https://drive.google.com/file/d/1GD1QWWN_q5Lq5-O_w0OgN2jE3dG2_-M0/view?usp=sharing
recovery_10.0.43.img.zip
https://drive.google.com/file/d/1OL1oy9yb3dFE5gsWdrUQVZd5PcHi9ap-/view?usp=sharing
recovery_10.0.42_adb_nosec.img.zip
https://drive.google.com/file/d/1n7tQWR1nRp2vDwejE2dKCjHONwm32ZTs/view?usp=sharing
recovery_10.0.42.img.zip
https://drive.google.com/file/d/1IdMuwj-onVeUYGe0u0XjlIbU0E4mnz0-/view?usp=sharing
recovery_10.0.41_adb_nosec.img.zip
https://drive.google.com/file/d/1zRBMHHIDmTCtReTUCorhNDknzwU4Z5Jf/view?usp=sharing
recovery_10.0.41.img.zip
https://drive.google.com/file/d/1jPC9R5ZY8obIXfOH9k7ghnm3oCsBfTCs/view?usp=sharing
recovery_10.0.40_adb_nosec.img.zip
https://drive.google.com/file/d/1k_GSg4EBf8ejhA2Yk6JInnd8oQTz4WPE/view?usp=sharing
recovery_10.0.40.img.zip
https://drive.google.com/file/d/12YSaIiQhroRXehGR3xi4nzBUx7oeNiNL/view?usp=sharing
recovery_10.0.39_adb_nosec.img.zip
https://drive.google.com/file/d/1eqPCZ9ExaEDpNt3huTmU07z2WVKR-i72/view?usp=sharing
recovery_10.0.39.img.zip
https://drive.google.com/file/d/1Elpc8jv1kYeNAMWyU1nJyjkzG0rd6zTg/view?usp=sharing
recovery_10.0.37_adb_nosec.img.zip
https://drive.google.com/file/d/1CUplbaMHpSV49siLzK3tSN-tmtfYJ2jd/view?usp=sharing
recovery_10.0.37.img.zip
https://drive.google.com/file/d/1z7uG-F7SedzAJwBHn6pY81Nqa44vkUcz/view?usp=sharing
recovery_10.0.36_adb_nosec.img.zip
https://drive.google.com/file/d/1AHy863Z_CFBHfRNSAhYN7E0UFCzU-YHs/view?usp=sharing
recovery_10.0.36.img.zip
https://drive.google.com/file/d/1AIk09glW0ZVLDWastbQVEXGxxJLZ6sqp/view?usp=sharing
recovery_10.0.35_adb_nosec.img.zip
https://drive.google.com/file/d/1UxRvakxsKHZ-pEaZQcGy6YiL_23jLscK/view?usp=sharing
recovery_10.0.35.img.zip
https://drive.google.com/file/d/1Ut-JqzAJKz7jNvb6bp14zO-L0haVjz57/view?usp=sharing
recovery_10.0.34_adb_nosec.img.zip
https://drive.google.com/open?id=16S3eJS3WrKIekJAijFtIgP4a34sMJE78
recovery_10.0.34.img.zip
https://drive.google.com/open?id=1yCvTsT-2NKzToGUn_-1FtiMbNur6Livw
recovery_10.0.31_adb_nosec.img.zip
https://drive.google.com/open?id=1-H92H_TIQUJjQbIElQLsryRq0299lM1k
recovery_10.0.31.img.zip
https://drive.google.com/open?id=1Lp4wuql8j0FwD1I1OPj1r4ebi1Ti3XTg
recovery_10.0.27_adb_nosec.img.zip
https://drive.google.com/open?id=13sp8k6Vk6n6v8SpnjvO9sIFr_5mJ6UYV
recovery_10.0.27.img.zip
https://drive.google.com/open?id=13uRw5yfsBiWJ_nviiXB3Qk3yLl7IPxQG
recovery_10.0.25_adb_nosec.img.zip
https://drive.google.com/open?id=1CapeyuagSK0XxKbI-OuRSXjyKf9ylstV
recovery_10.0.25.img.zip
https://drive.google.com/open?id=1CaNNsZ4q3QVKrzzJ8S7LW5r8TUPuW7OC
recovery_10.0.19_adb_nosec.img.zip
https://drive.google.com/open?id=1-gfQlKcHkIoTzWgHaGenyda6AU614dct
recovery_10.0.19.img.zip
https://drive.google.com/open?id=10Nal33Bw5q_dpBQSbdjKpizGghAV4Wda
Android SDK Platform-Tools
https://developer.android.com/studio/releases/platform-tools
-----------------------------------------------------------------
Special thanks to @aer0zer0 for his input
and to @osm0sis for his: [TOOL] Android Image Kitchen - Unpack/Repack Kernel Ramdisk [Win/Android/Linux/Mac]
https://forum.xda-developers.com/showthread.php?t=2073775
Forgive the noob question but Are we able to use this recovery to flash kernels etc?
lendawg said:
Forgive the noon question but Are we able to use this recovery to flash kernels etc?
Click to expand...
Click to collapse
If you just wanted to flash kernels, if already rooted you could could just use an app like Franco Kernel Manager, etc., to flash kernels. A main purpose of this adb enabled stock recovery is to allow decrypted filesystem access in case you could not successfully boot into OS normally. For example, I know of someone who used it to delete a particular file that was causing boot loop after they rebooted right after installing Viper. When we get a fully functioning TWRP for the 5G McLaren, this recovery will be unnecessary.
Can this be used to update our Android version since unlocking the bootloader has messed up receiving OTAs?
Bildo41383 said:
Can this be used to update our Android version since unlocking the bootloader has messed up receiving OTAs?
Click to expand...
Click to collapse
@ntzrmtthihu777 came up with an OTA fixer, which is currently located at https://forum.xda-developers.com/7t-pro-mclaren/how-to/hd1925-10-0-19-fastboot-rom-ota-fixer-t4040629 . Also, you would want to flash back the stock recovery (i.e, without adb enabled), and fully unroot, etc., before OTA as well. If you still couldn't OTA update at that point, then you'd want to backup important files to external storage and flash our device's latest MSM image.
Does anyone here know a good Post on how to unroot my device so I can go ahead and do the update for my phone?
I have a McLaren 5G T-Mobile. I'm currently on version 0.19 and I just received the OTA this morning to update to version 0.25.
I'm new to all of this rooting world. Any help is appreciated.
Thank you.
lramos_90 said:
Does anyone here know a good Post on how to unroot my device so I can go ahead and do the update for my phone?
I have a McLaren 5G T-Mobile. I'm currently on version 0.19 and I just received the OTA this morning to update to version 0.25.
I'm new to all of this rooting world. Any help is appreciated.
Thank you.
Click to expand...
Click to collapse
You could try the OTA fixer linked in the post above your post, and this restores the reserve.img file in /data/reserve/ . After restoring reserve.img, you could open Magisk Manager and choose full unroot. Then, after rebooting, OTA might be able to install; if not, a surefire option is to flash the latest MSM image. The MSM flash in our device forum should be a last resort, because you would probably want to back up important files to external storage and almost everything is replaced starting from scratch.
jhofseth said:
You could try the OTA fixer linked in the post above your post, and this restores the reserve.img file in /data/reserve/ . After restoring reserve.img, you could open Magisk Manager and choose full unroot. Then, after rebooting, OTA might be able to install; if not, a surefire option is to flash the latest MSM image. The MSM flash in our device forum should be a last resort, because you would probably want to back up important files to external storage and almost everything is replaced starting from scratch.
Click to expand...
Click to collapse
I bricked my phone but I was able to use the MSM tool and fresh install everything. Thank you very much for the recommendation..
Thank you for the update version.
im not getting any updates for my phone I am still stuck on 19 can I use this to update to 31 I am waiting for my unlock code for the bootloader should i wait to root before I update or update first
cgrimm9 said:
im not getting any updates for my phone I am still stuck on 19 can I use this to update to 31 I am waiting for my unlock code for the bootloader should i wait to root before I update or update first
Click to expand...
Click to collapse
No, you'd need to use latest MSM tool if you were stuck on 19, but you may want to backup any important files to external storage first. https://forum.xda-developers.com/7t-pro-mclaren/how-to/op7tpro-tmo-5g-unbrick-tool-to-restore-t4043925
jhofseth said:
No, you'd need to use latest MSM tool if you were stuck on 19, but you may want to backup any important files to external storage first. https://forum.xda-developers.com/7t-pro-mclaren/how-to/op7tpro-tmo-5g-unbrick-tool-to-restore-t4043925
Click to expand...
Click to collapse
I figured it out after messing around. I meant to come back and edit my post. I saw the msm post and thats the only reason I messed around with this phone. I just wish there was a working twrp for this phone so some roms come over. but that may never happen.
seems like the 31 recovery is wrong - cannot install OTA without it = = FIXED!!!! HAD TO APPLY ORIGINAL 2X for some reason" literally used the same download to apply again... I dont get this phone
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553051:ERROR:delta_performer.cc(522)] Unable to open ECC source partition recovery on slot B, file /dev/block/bootdevice/by-name/recovery_b: Invalid argument (22)
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553106:ERROR:delta_performer.cc(1230)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553148:ERROR:delta_performer.cc(1235)] Expected: sha256|hex = 001B4315FE31C5A4F1C23D1B16A2C64F137950FF2C28CBC7A7 BD85F3FCB6C987
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553187:ERROR:delta_performer.cc(1238)] Calculated: sha256|hex = 9FF662AA7D1616A5CAB2E532839F6D41429D4214CF38012A49 96D6228A806AF7
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553228:ERROR:delta_performer.cc(1249)] Operation source (offset:size) in blocks: 0:1,15252:1
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553274:ERROR:delta_performer.cc(1530)] source_fd != nullptr failed.
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553323:ERROR:delta_performer.cc(305)] Failed to perform BROTLI_BSDIFF operation 848, which is the operation 0 in partition "recovery"
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553367:ERROR:download_action.cc(336)] Error ErrorCode::kDownloadSta
I moved from TMO to Google Fi about a month ago and I haven't had any issues since moving over, other than this weird call terminating thing that I fixed with a new SIM card. However, I would like to get rid of the TMO ROM that is on here. Does anyone have any advice on what to go with? Just stock OxygenOS rom? I found it at the oneplus.in/support/softwareupgrade forums. However, I can't follow the instructions at the bottom because my "System Update" page does not have a settings button in the top right hand corner (I assume bc of TMO build). Also, the build number appears to be different. 10.3.3.HD01AA vs. 10.0.9 that I have seen elsewhere, but similar dates on them.
Do I need to unlock my bootloader and completely flash a new ROM? Sorry for being such a noob about this.
cregets said:
I moved from TMO to Google Fi about a month ago and I haven't had any issues since moving over, other than this weird call terminating thing that I fixed with a new SIM card. However, I would like to get rid of the TMO ROM that is on here. Does anyone have any advice on what to go with? Just stock OxygenOS rom? I found it at the oneplus.in/support/softwareupgrade forums. However, I can't follow the instructions at the bottom because my "System Update" page does not have a settings button in the top right hand corner (I assume bc of TMO build). Also, the build number appears to be different. 10.3.3.HD01AA vs. 10.0.9 that I have seen elsewhere, but similar dates on them.
Do I need to unlock my bootloader and completely flash a new ROM? Sorry for being such a noob about this.
Click to expand...
Click to collapse
If you're on the TMO 5G variant, I would get the bootloader unlocked and then flash AOSiP. You can definitely use stock ROM, but are limited to TMO's update schedule which differs from OnePlus devices sold directly. With a custom ROM, you get flexibility. Just know you won't have a fingerprint scanner for the time being, but the software advantages and flexibility and battery life increase are worth it in my opinion!
10.0.37.HD61CB is out now, anyone know how to download recovery and add adb?
t436h05t said:
10.0.37.HD61CB is out now, anyone know how to download recovery and add adb?
Click to expand...
Click to collapse
37 is now added to the OP
39 is now added to the OP
anyway to remove a magisk module this way - data is empty?
recovery_10.0.37_adb_nosec.img works and askes for decrypt 39 broken
7T Pro McLaren HD1913 Official Build
Hello, can someone please provide the links to the official builds for the 7T Pro McLaren Edition HD1913. I would really appreciate it.
Edit 25/10/2020: OK its been a while guys, if you want to try a ROM I'd highly recommend following LineageOS's wiki for instructions. Then if u want to try other ROMs keep an eye out in these forums, ill have a build up every now and then. See ya around guys
==========================================================================================
Rather than having random comments in random parts of the forum here is a thread for everything 64 bit on G7 Play.
CURRENT STATUS
WE DID IT!!!! CHECK SyberHexen's ANDROIDFILEHOST FOR DOWNLOAD!
OLD POST ARCHIVED BELOW
And here is what is available so far:
A nice selection of ROMs for the other G7's, but they dont actually boot on the Play, although should do something in theory
postmarketOS is aarch64, but that is mobile linux, and no phone interface works (x.org doesnt work with the current drivers)
Here is what I've tried:
crDroid from ocean:
I got it to install by: repartitioning device using ocean gpt.bin
Then flashing stock rom from channel
Booting TWRP
Flashing ROM, with modified zip accepting channel
Doesnt boot
Also tried a flash using ocean firmware completely, doesn't boot, but got the logos and bootloader works lol
If anyone has any tips or progress drop it here, eta kids go away. Read the status above if you want the up-to-date answer
00p513 said:
Rather than having random comments in random parts of the forum here is a thread for everything 64 bit on G7 Play.
CURRENT STATUS
NO 64-BIT ANDROID ROM AVAILABLE
And here is what is available so far:
A nice selection of ROMs for the other G7's, but they dont actually boot on the Play, although should do something in theory
postmarketOS is aarch64, but that is mobile linux, and no phone interface works (x.org doesnt work with the current drivers)
Here is what I've tried:
crDroid from ocean:
I got it to install by: repartitioning device using ocean gpt.bin
Then flashing stock rom from channel
Booting TWRP
Flashing ROM, with modified zip accepting channel
Doesnt boot
Also tried a flash using ocean firmware completely, doesn't boot, but got the logos and bootloader works lol
If anyone has any tips or progress drop it here, eta kids go away. Read the status above if you want the up-to-date answer
Click to expand...
Click to collapse
You have to compile the kernel from source and use a 64bit gsi and flash a 64 bit vendor partition I'm pretty sure everythi
---------- Post added at 04:44 AM ---------- Previous post was at 04:42 AM ----------
00p513 said:
Rather than having random comments in random parts of the forum here is a thread for everything 64 bit on G7 Play.
CURRENT STATUS
NO 64-BIT ANDROID ROM AVAILABLE
And here is what is available so far:
A nice selection of ROMs for the other G7's, but they dont actually boot on the Play, although should do something in theory
postmarketOS is aarch64, but that is mobile linux, and no phone interface works (x.org doesnt work with the current drivers)
Here is what I've tried:
crDroid from ocean:
I got it to install by: repartitioning device using ocean gpt.bin
Then flashing stock rom from channel
Booting TWRP
Flashing ROM, with modified zip accepting channel
Doesnt boot
Also tried a flash using ocean firmware completely, doesn't boot, but got the logos and bootloader works lol
If anyone has any tips or progress drop it here, eta kids go away. Read the status above if you want the up-to-date answer
Click to expand...
Click to collapse
You have to compile the kernel from source and use a 64bit gsi and flash a 64 bit vendor partition I'm pretty sure everything else will work fine. I'm working on getting a new dev environment set up I'll give it a shot... This phone is reeeeealy under developed. Proly cause the g6 play is a way better phone and much cheaper to boot
mrsurge said:
You have to compile the kernel from source and use a 64bit gsi and flash a 64 bit vendor partition I'm pretty sure everythi
---------- Post added at 04:44 AM ---------- Previous post was at 04:42 AM ----------
You have to compile the kernel from source and use a 64bit gsi and flash a 64 bit vendor partition I'm pretty sure everything else will work fine. I'm working on getting a new dev environment set up I'll give it a shot... This phone is reeeeealy under developed. Proly cause the g6 play is a way better phone and much cheaper to boot
Click to expand...
Click to collapse
We have a 64-bit kernel and 64-bit Lineage OS testing builds but porting 64-bit vendor partition for it to flash in g7 play hasn't been achieved yet.
kD said:
We have a 64-bit kernel and 64-bit Lineage OS testing builds but porting 64-bit vendor partition for it to flash in g7 play hasn't been achieved yet.
Click to expand...
Click to collapse
I think maybe you can just pick out driver binaries from 64 bit /vendor and use all the configs scripts and frameworks from the original vendor
Try backing up/vendor pieceing the drivers from another device of the same model but diff carrier and a combo as such would work. If not mistaken the. Vendor from the Verizon g6 play worked for sprint except data and wifi or radio in general didn't work.. that's a start right there
I think the modem is going to be the same architecture no matter what so you wouldn't have to worry to much about that
64bit Test
Okay so this sh*t probably totally won't boot up at all, but if someone is feeling brave, you can test this out.
1. From your active slot, with root access, you'll need to dd these images to the correct partitions. It's easiest to do this from the internal sdcard using termux. Use the following as a template. These commands assume you're installing it to slot b.
Code:
su
dd if=/sdcard/boot64.img of=/dev/block/by-name/boot_b
dd if=/sdcard/dtbo64.img of=/dev/block/by-name/dtbo_b
dd if=/sdcard/vendor64.img of=/dev/block/by-name/vendor_b
dd if=/sdcard/oem64.img of=/dev/block/by-name/oem_b
2. Reboot into fastboot, swap active slots, and wipe userdata + DDR. Then flash an arm64 AB GSI. I'd recommend trying Phh's AOSP Vanilla to maximize the chances of success.
To swap slots and wipe user data...
Code:
fastboot --set-active=_b
fastboot erase userdata
fastboot erase DDR
3. Reboot system, and tell me what happens.
**Do NOT attempt to use TWRP with this. You'll probably have to reflash stock firmware to the slot you tampered with to get everything back to normal afterwards.**
Link: 64bit Folder
This is not source built, and it's very much a hack job, so I'm really not expecting anything to work. I did get Ubuntu installed this morning, so I will attempt to build from source in the near future.
Please don't use this if you don't know what a "brick" is or how to recover from one
PS: it probably wont work cause vendor is twice the size xD
The G7 play is coming so far little by little it was like yesterday we never thought we would have twrp and magisk and now in fact we do on a GSI
([emoji88]Havoc GSI[emoji88])
00p513 said:
PS: it probably wont work cause vendor is twice the size xD
Click to expand...
Click to collapse
You are correct. She's way too hefty. It's ~164mb too large. I tried resizing last night, but I can only shrink it to 433mb. I can probably remove the modem files and replace them with the ones from stock. I think it's where most of the extra weight is from. The 64bit libs are about 1.5x bigger, but I don't think that accounts for all of it. The Muppets have a tree for sdm632, so all I need to do is look at it, and delete everything in vendor that's not in there. It should help but I'm not sure if it'll be enough. I could repartition it, but I'm not a fan of resizing partitions because I'm very fearful of bricks.
Spaceminer said:
You are correct. She's way too hefty. It's ~164mb too large. I tried resizing last night, but I can only shrink it to 433mb. I can probably remove the modem files and replace them with the ones from stock. I think it's where most of the extra weight is from. The 64bit libs are about 1.5x bigger, but I don't think that accounts for all of it. The Muppets have a tree for sdm632, so all I need to do is look at it, and delete everything in vendor that's not in there. It should help but I'm not sure if it'll be enough. I could repartition it, but I'm not a fan of resizing partitions because I'm very fearful of bricks.
Click to expand...
Click to collapse
I can get a bit more space with an ocean gpt.bin btw. i suppose we could see how those files work i guess and make a bigger vendor?
00p513 said:
I can get a bit more space with an ocean gpt.bin btw. i suppose we could see how those files work i guess and make a bigger vendor?
Click to expand...
Click to collapse
Have you flashed the gpt.bin from ocean before? If so I'll definitely try using that with the slightly smaller vendor I made. I'm thinking most things from Ocean should work natively. The only difference is screen size by a few pixels, ram, and battery capacity. Otherwise they're essentially the same.
Spaceminer said:
Have you flashed the gpt.bin from ocean before? If so I'll definitely try using that with the slightly smaller vendor I made. I'm thinking most things from Ocean should work natively. The only difference is screen size by a few pixels, ram, and battery capacity. Otherwise they're essentially the same.
Click to expand...
Click to collapse
yeah i use channel firmware extracted, then i use motoflash2sh to generate a bashscript from the flashfile. I then replace gpt .bin and remove it from the md5 checks at the beginning of the script. run the script and im repartitioned!
00p513 said:
yeah i use channel firmware extracted, then i use motoflash2sh to generate a bashscript from the flashfile. I then replace gpt .bin and remove it from the md5 checks at the beginning of the script. run the script and im repartitioned!
Click to expand...
Click to collapse
That's awesome! I'll try working with this.
Spaceminer said:
That's awesome! I'll try working with this.
Click to expand...
Click to collapse
ill send a repartition kit later. just unzip and run the script
00p513 said:
ill send a repartition kit later. just unzip and run the script
Click to expand...
Click to collapse
I already found it. So I'd just remove 61863ba7dac0c512d610ffa6406a50f8 and it'll flash correct?
Code:
md5sum --check <<EOF || exit 1
[B]61863ba7dac0c512d610ffa6406a50f8[/B] *gpt.bin
Spaceminer said:
I already found it. So I'd just remove 61863ba7dac0c512d610ffa6406a50f8 and it'll flash correct?
Code:
md5sum --check <<EOF || exit 1
[B]61863ba7dac0c512d610ffa6406a50f8[/B] *gpt.bin
Click to expand...
Click to collapse
that whole line needs deleting. That is just to stop it failing on md5 verification ,as it is a dfiferent file
Spaceminer said:
I already found it. So I'd just remove 61863ba7dac0c512d610ffa6406a50f8 and it'll flash correct?
Code:
md5sum --check <<EOF || exit 1
[B]61863ba7dac0c512d610ffa6406a50f8[/B] *gpt.bin
Click to expand...
Click to collapse
Did it work? Any update on the vendor image?
00p513 said:
Did it work? Any update on the vendor image?
Click to expand...
Click to collapse
I haven't tried it yet. I got side tracked compiling twrp. I'm 3 errors away from success. Something about unknown compiler flags.
As an FYI, I'm out of a computer for the next several months, possibly up to a year. I'm going through a nasty divorce at the moment, and that's all I'm going to say about that. I'll get back into the game as soon as I can, but for now, you should not expect me to put out anything new for quite awhile. I can and will help people as much as possible during this time. But my ability to do so is going to be hindered without an PC.
I'm sorry to hear that. My divorce lasts since two years.
However, that's not why I registered. I received a Moto G7 Play for app security testing just a few days ago and found this forum when trying to install GSI to the phone. Everything works fine, but I'm interested to upgrade the OS to 64bit. Therefore, I'd like to try out the work already present in this thread. Unfortunately, I have neither found the repartition kit nor gained enough information about gpt.bin file format yet in order to repartition the flash memory of the G7 Play.
I'd really appreciate if anybody could either post or send me the repartition kit or supply information about the partition table format, because I failed to google for that kind of information.
[edit] Ok, I found out how to change partition size to the size of ocean. I flashed the following images:
* Partition table from ocean
* Everything else except system_a from channel
* system_a from phh (binder64)
Everything worked just fine.
Then I proceeded to flash the files posted in this thread earlier. The vendor64.img fits into the new partition layout just fine. After flashing all 4 files, I proceeded to flash phh 64bit version. Then I rebooted, but the boot failed:
First, the device showed up some very long hexadecimal number (maybe some UUID?) on a black screen, where it had shown "bad key" before when everything went right.
Afterwards, it ran into fastboot:
Start Up Failed:
Your device didn't start up successfully.
Use Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Failed to verify hab image boot_a
Error: failed to load kernel!
No bootable A/B slot
Failed to boot Linux,falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
Click to expand...
Click to collapse
So, I'm back on binder64 again.
Please, could you provide any help for fixing the images, or at least the information how you have built the 64bit 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"
}
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.
IntroductionROG 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 installWe 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
CreditsRocky7842xspx for testing the device with meNumerous 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.
Any custom roms like lineage for this device? This is not kiev.
Well, the phone barely launched. It does not have even a year. Since the phone is in order to get another 1 -2 updates, wait for those. Moto can develop faster than any individual dev. If you want lineage or other custom rom, wait a couple more months
Fytdyh said:
Well, the phone barely launched. It does not have even a year. Since the phone is in order to get another 1 -2 updates, wait for those. Moto can develop faster than any individual dev. If you want lineage or other custom rom, wait a couple more months
Click to expand...
Click to collapse
I tried using a stock firmware and patched magisk but when I booted up the phone I got this
gr3uh said:
I tried using a stock firmware and patched magisk but when I booted up the phone I got this
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You cannot bypass that. That carrier lock is in place to ensure you won't sell the device as something else. You would need to talk to your carrier and pay to get it unlocked.
Fytdyh said:
You cannot bypass that. That carrier lock is in place to ensure you won't sell the device as something else. You would need to talk to your carrier and pay to get it unlocked. .
Click to expand...
Click to collapse
I think I used the wrong firmware possibly
Fytdyh said:
You cannot bypass that. That carrier lock is in place to ensure you won't sell the device as something else. You would need to talk to your carrier and pay to get it unlocked.
Click to expand...
Click to collapse
Makes no sense since I was perfectly able to unlock the bootloader using Motorola's official guide.
I recommend posting your questions here :
https://forum.xda-developers.com/t/...noob-friendly.2257421/page-2453#post-87357675
Do say what you did, what you flashed. Everyone can help you faster if you are concise and say what did you flash or did to that device. Whenever you try something, write it down.
mine did that too and i just kept trying different sim cards untill i found one that worked and it unlocked it
Hi all, I have a couple questions about this:
My ultimate goal is to get a custom firmware on this (Lineage). I have seen a few threads floating around here, recommending an alternate method for rooting the device, and offering a link to the stock firmware.
However, even if this is successful, I will end up with a rooted, stock-Android phone at the end of it, and since there's still no Lineage release for this phone (or any other alternate firmare, from what I can tell), this effort is not going to get me any closer to a custom ROM. Am I understanding this correctly?
If I'm understanding point 1 correctly, then I need to decide whether to keep this phone, or return it. If a custom OS never becomes available, I don't want the phone. Even in github, there's no indication I could see that Austin is even under development.
However, if this phone is likely to end up with a LineageOS version, I'll just wait a few months. For those of you who spend more time on XDA than I do, how likely is it that this will get a release candidate?
Thanks for your help!
3×5 said:
Hi all, I have a couple questions about this:
My ultimate goal is to get a custom firmware on this (Lineage). I have seen a few threads floating around here, recommending an alternate method for rooting the device, and offering a link to the stock firmware.
However, even if this is successful, I will end up with a rooted, stock-Android phone at the end of it, and since there's still no Lineage release for this phone (or any other alternate firmare, from what I can tell), this effort is not going to get me any closer to a custom ROM. Am I understanding this correctly?
If I'm understanding point 1 correctly, then I need to decide whether to keep this phone, or return it. If a custom OS never becomes available, I don't want the phone. Even in github, there's no indication I could see that Austin is even under development.
However, if this phone is likely to end up with a LineageOS version, I'll just wait a few months. For those of you who spend more time on XDA than I do, how likely is it that this will get a release candidate?
Thanks for your help!
Click to expand...
Click to collapse
I've been told there will never be any progress on custom roms and firmware for this device since it is mediatek and mediatek is locked down their binaries making it hard for people to make custom rom. That being said you can try porting your own twrp or flashing a GSI.
KParsons0697 said:
mine did that too and i just kept trying different sim cards untill i found one that worked and it unlocked it
Click to expand...
Click to collapse
My phone I bought it from a carrier and it was locked until payed off, paid it and waited a few days and it worked. Rooting this device was easy, just wish rom development would come sometime. I hear android 13 should be coming to this device around the beginning of Q2 of 2023
@gr3uh, thanks for the reply. I could try a GSI, but really my goal is to have an open-as-possible, de-Googled phone. I don't even really care about MicroG, or any of this. Even with no services at all, I can use Google Maps in a browser.
I assume if I install the stock firmware from lolinet, it'll have all the Google Play services. Will the phone also be rooter at that point? Or do I have to also root the phone, and then manually remove all the play services?
The big picture question is this: what's the simplest route to me De-Googling this phone?
Bonus question: why is the stock firmware hosted on a site called 'lolinet'? Maybe I don't want to know...
Alright, here's an update on my progress:
I downloaded a Lineage GSI image from Andy Yan. His site said to install an app called 'Treble Info' to get device information. I did this and got the version that matched this device: lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
(b means "AB", i.e. system-as-root. VNDKLITE = Read/Write Super partition. Treble info said VNDKLITE was enabled on this device).
I restarted in fastboot mode and ran
Code:
fastboot erase system
and got:
Code:
erasing 'system_b'...
OKAY [ 0.054s]
Then I ran:
Code:
fastboot -u flash system lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
and got:
Code:
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 164341876 is not a multiple of the block size 4096
sending sparse 'system_b' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
OKAY [ 9.599s]
writing 'system_b' 1/3...
FAILED (status read failed (No such device))
So then I downloaded an empty vbmeta.img file, and flashed that:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
That appeared to work, because I thought my issue might be that dm-verity was enabled. However, I think the real issue is that I flashed this wrong, because I was looking at a tutorial that didn't apply to a system with a super partition. So my hope is that I can still flash my GSI image to the super partition, but I'm not totally sure how to do this. It might be as simple as
Code:
fastboot flash super lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
But I don't want to make things worse. At this point, my system partition is corrupted. The first time I tried to flash system I got "no such device", and the second time I got
Code:
(bootloader) Invalid partition name system
Anyway, I can only boot into fastboot mode. I do have that stock ROM from lolinet, so I could try flashing the super partition, chunk by chunk. There are 26 sparsechunks. Maybe this would get me back to square 1, but I'd rather press forward at this point, if possible, and try to get this GSI image flashed.
I should also point out that when I boot into fastbootd on the phone, it says 'Secure boot - yes' even though I flashed that empty vbmeta image and got:
Code:
target reported max download size of 268435456 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.000s]
writing 'vbmeta_b'...
OKAY [ 0.073s]
finished. total time: 0.074s
3×5 said:
Alright, here's an update on my progress:
I downloaded a Lineage GSI image from Andy Yan. His site said to install an app called 'Treble Info' to get device information. I did this and got the version that matched this device: lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
(b means "AB", i.e. system-as-root. VNDKLITE = Read/Write Super partition. Treble info said VNDKLITE was enabled on this device).
I restarted in fastboot mode and ran
Code:
fastboot erase system
and got:
Code:
erasing 'system_b'...
OKAY [ 0.054s]
Then I ran:
Code:
fastboot -u flash system lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
and got:
Code:
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 164341876 is not a multiple of the block size 4096
sending sparse 'system_b' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
OKAY [ 9.599s]
writing 'system_b' 1/3...
FAILED (status read failed (No such device))
So then I downloaded an empty vbmeta.img file, and flashed that:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
That appeared to work, because I thought my issue might be that dm-verity was enabled. However, I think the real issue is that I flashed this wrong, because I was looking at a tutorial that didn't apply to a system with a super partition. So my hope is that I can still flash my GSI image to the super partition, but I'm not totally sure how to do this. It might be as simple as
Code:
fastboot flash super lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
But I don't want to make things worse. At this point, my system partition is corrupted. The first time I tried to flash system I got "no such device", and the second time I got
Code:
(bootloader) Invalid partition name system
Anyway, I can only boot into fastboot mode. I do have that stock ROM from lolinet, so I could try flashing the super partition, chunk by chunk. There are 26 sparsechunks. Maybe this would get me back to square 1, but I'd rather press forward at this point, if possible, and try to get this GSI image flashed.
Click to expand...
Click to collapse
There should be a batch file in the zip you can use to flash the dynamic partition covers everything just edit it to fit your need. And run as betch
Thanks for the reply, but the link in my post is just to a .img.xz file. It doesn't have any zip and no "batch/betch" file (I assume you meant bash?)
3×5 said:
Thanks for the reply, but the link in my post is just to a .img.xz file. It doesn't have any zip and no "batch/betch" file (I assume you meant bash?)
Click to expand...
Click to collapse
.bat or batch is a file that contains a compiled list or a batch of commands that can run the commands in chronological order so you don't have any error and it makes the installation data redundant. It's really a helpful tool that automates workflow.
radosomalo said:
.bat or batch is a file that contains a compiled list or a batch of commands that can run the commands in chronological order so you don't have any error and it makes the installation data redundant. It's really a helpful tool that automates workflow.
Click to expand...
Click to collapse
Thanks for the clarification. Unfortunately, my image is just an img.xz file. There's no .bat script and no zip.
I ran fastboot getvar current-slot and it says 'current-slot: b'. Then I ran fastboot flash system_b imagefile.img.xz and I got:
Code:
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 433714276 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 165282916 is not a multiple of the block size 4096
sending sparse 'system_b' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 433714276 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 433714276 is not a multiple of the block size 4096
OKAY [ 9.401s]
writing 'system_b' 1/3...
FAILED (status read failed (No such device))
finished. total time: 14.558s
So basically the same problem as before. I tried running 'fastboot delete-logical-partition product_b' and got:
Code:
fastboot: usage: unknown command delete-logical-partition
I could try 'fastboot flash super imagefile.img.xz' but I don't know if I'm supposed to delete super first, and I don't want to make things worse. So any advice would be appreciated.
radosomalo said:
.bat or batch is a file that contains a compiled list or a batch of commands that can run the commands in chronological order so you don't have any error and it makes the installation data redundant. It's really a helpful tool that automates workflow.
Click to expand...
Click to collapse
Alright, I was able to flash the GSI ROM, but it didn't work. My phone thinks the OS is corrupted. I think my only choice now is to go back to my stock ROM. I tried to flash the super partition but running
Code:
./fastboot flash super ../super.img_sparsechunk.0
and it did this through sparsechunk 26. Then I rebooted and I still have no OS.
Now this stock ROM does not have a .bat file, but it does have flashfile.xml. Is there any way I can use this to automate the flashing process? At this point, I'm thinking I'm going to have to flash every partition.
Related question: In the flashfile, it specifies partitions as logo_a, vbmeta_system_a, etc. But when I run '
fastboot getvar current-slot' it says my current slot is 'b'. So should I replace every instance of _a with _b?