This is a temporary solution to a pending pull request. This thread will be deprecated if or when the official release is updated.
I don't have the original signing key, but there is really no reason to attempt reverse engineering an app that's open source. Instead, it is signed with one of my own "Google Play certified" keys. Changes are below for anyone that would rather build and sign the application locally.
The caveat to using a different key is that the unofficial version cannot be installed directly over the official and vice versa.
Pull Request
Do not hardcode su binary path by AbandonedCart · Pull Request #3 · HomerSp/AsusVoLTE
This fixes an issue where rooted devices are not recognized (#2)
github.com
Original Source
GitHub - HomerSp/AsusVoLTE: Enable VoLTE/VoWiFi on the ROG Phone 2
Enable VoLTE/VoWiFi on the ROG Phone 2. Contribute to HomerSp/AsusVoLTE development by creating an account on GitHub.
github.com
Thanks a lot for your update.
I made some progress.
App is working perfectly, triggered the USB PDC mode as well. (Which I couldn't do earlier).
The older versions we used were not detecting the device.
Got the new QPST from here
The latest driver I could find was from here
Still stuck at exactly here;
{
"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"
}
The guide I follow is the one which worked for me on the ROGII - Which is here. Didnt require any MBN flashing, as I have a global device and just needed to use the existing VoWiFI Profile.
Any ideas on how to resolve the connection issue?
Maybe there are newer drivers?
EDIT:
Some information here shows PDC doesnt work anymore.
Thread
JazonX said:
EDIT:
Some information here shows PDC doesnt work anymore.
Thread
Click to expand...
Click to collapse
PDC has been replaced with EfsTool, according to that (and other) threads.
[Guide]Activate VoLTE/VoWiFi OOS 11(OB1&OB2)
Hi everyone. /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following * these directions. YOU are...
forum.xda-developers.com
The thread I referenced in the Australia version of the VoLTE threads covers setup a little better for the specific use. Downloads are available in both.
[Guide] Enabling VoLTE/VoWiFi v2
Preface With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier...
forum.xda-developers.com
twistedumbrella said:
PDC has been replaced with EfsTool, according to that (and other) threads.
[Guide]Activate VoLTE/VoWiFi OOS 11(OB1&OB2)
Hi everyone. /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following * these directions. YOU are...
forum.xda-developers.com
The thread I referenced in the Australia version of the VoLTE threads covers setup a little better for the specific use. Downloads are available in both.
[Guide] Enabling VoLTE/VoWiFi v2
Preface With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks a lot, Made it through to the EFS Tools guide.
Did the mod to the EFSToolsdllconfig, Matched Ports.
Currently stuck here, Will keep you updated of the progress.
EDIT:
Tested with my ROG II and the command is working, So it's unable to read the ROG 5 for some mysterious reason.
I would test, but VoLTE works out of the box for Tencent / T-Mobile. No use trying to break it, especially if it's meant to survive updates / firmware.
At the point of giving up.
Stuck here;
and also I noticed that the Driver detection page keeps refreshing.
So I assume that neither of the tools we use are compatible with the ROG 5 yet, as they all link and work properly with my ROG II.
[Guide] activate Volte on Android 11 (root)
Finally I got it working on ww_30.40.30.96 on German carrier O2. I used most of the Guide from @HomerSp : https://forum.xda-developers.com/t/guide-enabling-volte-vowifi-v2.4028073/ requirements: adb for PC QPST latest EFS Tools from JohnBel...
forum.xda-developers.com
GitHub - JohnBel/EfsTools: Command line tools for Qualcomm EFS file system
Command line tools for Qualcomm EFS file system. Contribute to JohnBel/EfsTools development by creating an account on GitHub.
github.com
Not sure if any of that is a solution, but it seems to be the next suggestions
twistedumbrella said:
[Guide] activate Volte on Android 11 (root)
Finally I got it working on ww_30.40.30.96 on German carrier O2. I used most of the Guide from @HomerSp : https://forum.xda-developers.com/t/guide-enabling-volte-vowifi-v2.4028073/ requirements: adb for PC QPST latest EFS Tools from JohnBel...
forum.xda-developers.com
GitHub - JohnBel/EfsTools: Command line tools for Qualcomm EFS file system
Command line tools for Qualcomm EFS file system. Contribute to JohnBel/EfsTools development by creating an account on GitHub.
github.com
Not sure if any of that is a solution, but it seems to be the next suggestions
Click to expand...
Click to collapse
Thanks a lot for the responses;
(And thank you for your patience)
Here are my findings;
* The new EfsTools app is sorta broken, because it doesnt SIM Slot #2 Changes - Someone already reported it.
* Android 11 seems to block the PDC function, hence no ADB command can trigger it. However somehow your version of the AsusVoLTE app on first post here forcefully enters the Phone to PDC mode. This is a win, however the Device Manager keeps refreshing every second - so no connection can be made. I'm using Qualcomm Driver 1.0061 which seems to be the latest. I have used older .37 / .40 drivers as well, nothing changes the "frequent refresh" behavior.
* Not sure how this guy managed to get the ADB command to work on Android 11 in Zenfone, I tested it with both USB ports, multiple cables.. Nothing seems to trigger anything.
The code he suggested is
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
* OnePlus folks have the same issue and they have managed to enable PDC support by taking the phone to Field Test Mode via "ADB reboot FTM" command. This doesnt work for asus. OnePlus Method.
* I tried putting the phone in EDL mode, however this doesn't enable any Diag or PDC port, it seems its only for flashing. So far I have no clue whether any engineering or FTM mode exists on Asus.
* Many forums have *#*# codes - I think I have tried all of them, none of them seems to make any new option appear in sim menus.
So .. still. No VoLTE, and therefore no 5G either.
If you have any ideas / guides I can try .. Much appreciated!
Enabling Diagnostic Mode
I wanna enable the diagnostic mode and try to see if i can add more LTE bands through QPST. I tried the generic command through adb shell and its not working:( Any suggestions are welcome.
forum.xda-developers.com
Looks like it might be repeat information, though.
twistedumbrella said:
Enabling Diagnostic Mode
I wanna enable the diagnostic mode and try to see if i can add more LTE bands through QPST. I tried the generic command through adb shell and its not working:( Any suggestions are welcome.
forum.xda-developers.com
Looks like it might be repeat information, though.
Click to expand...
Click to collapse
Thanks a lot once again,
Both the suggested codes have no effect. Tried with SU, without SU, without spaces..
Nothing triggers any any new drive installation.
So far, Only your App's (Fixed Asus VoLTE) Enable PDC function can enable this Port. However it doesn't stick, as it keeps refreshing every 2 seconds (probably causing efs tools not to detect the port). QPST can see the port, but doesnt identify what device it is.
I tried a module which allows SeLinux to go permissive, thinking that might help. Almost hard bricked as this has no TWRP. Luckily the combination of Magisk removal code, stock boot image, and safe mode helped me out.
Damn, never thought I'd struggle this much to get 5G working.
Anyone come up with anything recent that works? Struggling with Rog 5 to enter Diag mode and so forth.
Vojtek12 said:
Anyone come up with anything recent that works? Struggling with Rog 5 to enter Diag mode and so forth.
Click to expand...
Click to collapse
You can enter diag mode using this commands
Inline links are only good when they save space for a reference that most readers may not be interested in reading
jbm76 said:
Install these usb drivers - https://gsmusbdriver.com/category/xiaomi/page/3
These are the commands -
Both of these work.
adb shelll,
su
setprop sys.usb.config diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
Either setprop command will work.
setprop sys.usb.config rndis,diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl
In regards to the VOLTE issue still no go on A11 - I have been able to access the EFS partition but the ims_user_agent won't stick even if I write to it with in EFS explorer of EFs tools, it doesn't survive a reboot.
Click to expand...
Click to collapse
JazonX said:
Thanks a lot once again,
Both the suggested codes have no effect. Tried with SU, without SU, without spaces..
Nothing triggers any any new drive installation.
View attachment 5393765
So far, Only your App's (Fixed Asus VoLTE) Enable PDC function can enable this Port. However it doesn't stick, as it keeps refreshing every 2 seconds (probably causing efs tools not to detect the port). QPST can see the port, but doesnt identify what device it is.
I tried a module which allows SeLinux to go permissive, thinking that might help. Almost hard bricked as this has no TWRP. Luckily the combination of Magisk removal code, stock boot image, and safe mode helped me out.
Damn, never thought I'd struggle this much to get 5G working.
Click to expand...
Click to collapse
I'm facing same issue as u now, the driver page keep refreshing every 2 seconds. Can u tell ur solutions pls. Tks mate!
LinhBT said:
I'm facing same issue as u now, the driver page keep refreshing every 2 seconds. Can u tell ur solutions pls. Tks mate!
Click to expand...
Click to collapse
Never found a solution. Tried a lot and asked a lot around here and eventually got rid of the phone.
JazonX said:
Never found a solution. Tried a lot and asked a lot around here and eventually got rid of the phone.
Click to expand...
Click to collapse
My ROG 5S is now in a very weird situation while both SIM is working, baseband is there, but no IMEI ( but still can make and receive phone call, sms....etc ). Also, can't unlock bootloader since it has no IMEI
Related
TWRP
XR6M10
Here
XR6P10
Here
Stock firmware
XR6M10 Version 03.99.01.04 - Marshmallow - Latest
Here
XR6P10 Version 03.02.00.04 - Marshmallow- Latest
Here
How to flash twrp and or stock firmware
Download and install the Qualcomm drivers from here
Download the firmware from above
Extract the firmware to a folder that you can easily access them from like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8936.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram0.xml and then the patch0.xml when prompted.
Plug in your tablet
Run the following adb command "adb reboot edl"
If the text at the top of the QFIL application says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you didn't install the drivers properly.
Click the Download Button to begin flashing your device
Root
Once you flash twrp you can install magisk via the flashable zip
Some info on what i have found about the device
There is really no security on this tablet. The bootloader will always report as bootloader locked, green dm-verity and secure boot being enabled this is because the LK doesn't seem to have ever been completed on it. Because of this everything it reports is static and the fastboot implementation is broken and doesn't work. This means we will need to EDL to flash the device which I provided instructions above on how to do.
Notes
Some XR6P10 may require more work because there is multiple variants of it made by vizio but what i have uploaded works on mine.
Screenshots:
Root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Magisk:
TWRP:
Is it just me not able to boot into EDL through ADB? I have a EDL cable arriving later this month I could use but I figure the device should have it. reboot edl through adb just reboots the device normally which is unfortunate.
XR6P10
Hey. And where to get the driver. And then I have two devices without an Android driver and an ADB Interface hanging in my device manager?
I cannot get anything to work on my XR6P10 either. Every time I try to "download" with the QFIL application it just fails.
@deadman96385
In regards to EDL mode am I missing something obvious. I tried EDL cable that has shorted pins which seems to not work "maybe a bad cable?" and ADB reboot edl seems to not work. I've tried ADB on two different tablets to boot into EDL mode but have yet to see the device pop up in device manager.
*I believe after Dec 2017 security patch ADB reboot EDL was removed, ill check the version on the devices since it should be fairly close to this year.
I'm having the exact same issue. adb reboot edl simply reboots the tablet. It does not enter it into EDL mode. I'm assuming you don't need an EDL cable to do this since we're doing this through the ADB interface. Or did I get that part wrong?
edit: I was able to enter EDL mode on the device itself using the following directions I found from another thread
Here is something to try ...
Enter edl via button combo (volup + voldn + pwr)
You should have a black screen ...
Now plug your phone into the cable on your PC/laptop ..
If your PC / laptop doesn't recognise your phone via Miflash or app you are using ...
Try tapping the power button once ...this seems to open/close the port ...
I noticed this when I was using edl mode to flash a ROM
I hope this helps
edit 2 I'm coming across two errors when downloading the ROM. The first is a Sahara Error which is due from not running QFIL immediately after entering EDL mode. Apparently the full connection does not remain open for that long. The second issue that I'm still dealing with is a Firehose error. I've googled this one and nothing seems to work to get around this.
Any update on this? Can't seem to get my XR6M10 rooted following these directions. Running into the same Firehose error as stefanpolo. Thanks!
stefanopolo said:
I'm having the exact same issue. adb reboot edl simply reboots the tablet. It does not enter it into EDL mode. I'm assuming you don't need an EDL cable to do this since we're doing this through the ADB interface. Or did I get that part wrong?
edit: I was able to enter EDL mode on the device itself using the following directions I found from another thread
Here is something to try ...
Enter edl via button combo (volup + voldn + pwr)
You should have a black screen ...
Now plug your phone into the cable on your PC/laptop ..
If your PC / laptop doesn't recognise your phone via Miflash or app you are using ...
Try tapping the power button once ...this seems to open/close the port ...
I noticed this when I was using edl mode to flash a ROM
I hope this helps
edit 2 I'm coming across two errors when downloading the ROM. The first is a Sahara Error which is due from not running QFIL immediately after entering EDL mode. Apparently the full connection does not remain open for that long. The second issue that I'm still dealing with is a Firehose error. I've googled this one and nothing seems to work to get around this.
Click to expand...
Click to collapse
Its flashed through EDL not ADB and thanks for the tips ill give it a shot. To my knowldege that button combo is just for hard resets on most devices. As of 2017 I believe the security patch removed adb reboot edl as preventive measures to some exploits. I believe that was the last security patch for the device and its dated Jan 1st 2017 for my security patch date. Although I believe it was late 2017 when this was released. Ill give some feed back if I can flash the patched boot file later.
The cable is also just for shorting pins on the USB port which is also a way to trigger EDL most on some devices. I have the cable and it does not work either.
---------- Post added at 03:40 AM ---------- Previous post was at 03:27 AM ----------
Post your log output from QFIL you can hit save log if you right click the Status area.
---------- Post added at 03:45 AM ---------- Previous post was at 03:40 AM ----------
Ah nvm I see what you mean that it just times out on you. I tried flashing TWRP and it just hangs at start download after specifying the working folder
removed
removed
So after restoring to 5.1.1 and fiddling around with QFIL and constructing things from scratch myself the solution is as follows and most likely applies to any variant of these devices. 6.0.1 Is on the device and with TWRP/Root. Next up is a lineage port to the device as 6.0.1 sucks not having OK google working while the device screen is off whereas 5.1.1 did. 6.0.1 and up is the bare minimum for certain apps to install and other various functionality.
1. Hold the volume buttons and PWR buttons until the device vibrates. The screen will be powered on but black instead of off which is in EDL mode. adb reboot edl does not work. I'm not exactly sure how the OP managed to use that unless he had an older build with the functionality or perhaps ADB removed the ability to pass the argument in newer builds past X date and I currently use the latest. Either way this is the only method to get EDL mode without opening the device to my knowledge as EDL cables even did not work for myself.
2. You need to flash within roughly 10 seconds of entering EDL mode. The window is small and you will see a 3 second timer in QFIL if you got it right. If not just reset the device again with step 1. You can have the device plugged in prior to entering EDL mode and QFIL pointing to the proper directory in advance to make things easy.
3. You need to modify the rawprogrammer0.xml that is provided as its making references to files that do not exist. File types that do not exist such as sparse images of which system.img is not a sparse file. I made the mistake here initially by commenting out lines instead of just removing the referenced file which soft bricked the device. I've uploaded the modified file which should work fine for any device and also retain user files. The original worked for the OP due to its his cached files/content/userdata but it will soft brick the device until the cache/data is cleared. I had to do this with TWRP in order to get the device to boot.
Using the provided xml file should be fine for anyone. Try to take a backup of the device in the rare event you play around with things and overwrite your MAC address with another. Its not a huge deal if you do but there is a super slim chance that it would cause problems if another device was on the same network with the same MAC. In short ensure you do not overwrite the persist partition if you do experiment with the firmware.
If anyone else has issues feel free to post here and I can address any questions despite there is probably not much interest in these devices as they were discontinued and I do not even think the new 2020 models are bringing back tablets from vizio. These things make great PDF/screen readers along with being a house hold tablet to control various devices.
I'd be really interested in that Lineage port if it wouldn't take a lot of work. I think these little tablets are a great buy for the price and they look great on the dock. I've already picked up 2 of them.
EDIT: And officially soft bricked one of them... Stuck in a boot loop after attempting to flash TWRP. It fails because it can not find NON-HLOS.bin when flashing TWRP. Obviously the file is not in the directory but I don't understand why it won't skip the file.
EDIT 2: I managed to get it out of the boot loop with a factory reset, but I still can't get the original firmware or TWRP installed on my XR6P10. It always fails because there isn't a file in the folder to flash.
So any Lineage port yet, did anyone verify the original firmware was built from CyanogenMod if so there is a good chance of lineage working. Does this OEM (not Vizio) have other tabs that have been rooted and ported? My P tabs work great as Logitech harmony hub controllers with the harmony app and as small tablets. We will need to get this working soon as developers and the play store end support for Android 6.xx.
Solace50 said:
So after restoring to 5.1.1 and fiddling around with QFIL and constructing things from scratch myself the solution is as follows and most likely applies to any variant of these devices. 6.0.1 Is on the device and with TWRP/Root. Next up is a lineage port to the device as 6.0.1 sucks not having OK google working while the device screen is off whereas 5.1.1 did. 6.0.1 and up is the bare minimum for certain apps to install and other various functionality.
1. Hold the volume buttons and PWR buttons until the device vibrates. The screen will be powered on but black instead of off which is in EDL mode. adb reboot edl does not work. I'm not exactly sure how the OP managed to use that unless he had an older build with the functionality or perhaps ADB removed the ability to pass the argument in newer builds past X date and I currently use the latest. Either way this is the only method to get EDL mode without opening the device to my knowledge as EDL cables even did not work for myself.
2. You need to flash within roughly 10 seconds of entering EDL mode. The window is small and you will see a 3 second timer in QFIL if you got it right. If not just reset the device again with step 1. You can have the device plugged in prior to entering EDL mode and QFIL pointing to the proper directory in advance to make things easy.
3. You need to modify the rawprogrammer0.xml that is provided as its making references to files that do not exist. File types that do not exist such as sparse images of which system.img is not a sparse file. I made the mistake here initially by commenting out lines instead of just removing the referenced file which soft bricked the device. I've uploaded the modified file which should work fine for any device and also retain user files. The original worked for the OP due to its his cached files/content/userdata but it will soft brick the device until the cache/data is cleared. I had to do this with TWRP in order to get the device to boot.
Using the provided xml file should be fine for anyone. Try to take a backup of the device in the rare event you play around with things and overwrite your MAC address with another. Its not a huge deal if you do but there is a super slim chance that it would cause problems if another device was on the same network with the same MAC. In short ensure you do not overwrite the persist partition if you do experiment with the firmware.
If anyone else has issues feel free to post here and I can address any questions despite there is probably not much interest in these devices as they were discontinued and I do not even think the new 2020 models are bringing back tablets from vizio. These things make great PDF/screen readers along with being a house hold tablet to control various devices.
Click to expand...
Click to collapse
Thanks for the write up. Just purchased one for a home automation setup. I am running into so odd issues. I have tried multiple versions of QFIL and finally got a better error with 2.0.0.2. I am having a few errors, downloaded another copy of the firmware and unblocked the files. also grabbed the xml file you uploaded but same issues. Any help would be great as some apps require marshmallow and edl flashing is new to me. Would a full factory reset help from the recovery menu?
FireHose Log: Host's payload to target size is too large
Fail to open image file: C:\test\sec.dat
Error reading the C:\test\rawprogram0.xml
Download Fail:FireHose Fail FireHose Fail:Failed to Upload the emmc images to the phone using Firehose.
Is hope for further updates on this project done?
I found the xml was not right, in addition the max send size needs to be backed down to 4096 in firehose config. I am uploading the files I had working successfully to get TWRP lit up. Hmm doesnt let me post cause I am too new. guess I will code paste the xml I used.
I dont know how far I am going to dive into a device like this, but its nice to be able to do *something* with it now.
this is my contents of rawprogram0.xml
Code:
<?xml version="1.0" ?>
<data>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="recovery.img" label="recovery" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="false" start_byte_hex="0xe38c000" start_sector="466016"/>
</data>
Has anyone managed to get any further with this, i've been using mine as a trusty Sonos controller but been Android 6 it is no longer unsupported.
If not, does anyone know of any other similar device, eg thin, light, no camera, wireless charging with stand?
Yeah. Unfortunately I'm not moving to S2 yet as these are my primary hardware sonos controllers. It's really sad that such a perfect little tablet for this duty is being left by the wayside because there isn't enough of a following for them.
Yeah, wish i'd not upgraded to S2, you're not missing much!
Here is a rooting method for the Plam Phone either the US variant or the Vodafone variant this has not been tested or confirmed working on any other device. This root method may break in the future because it is using a tool that isn't designed for the public i tried getting the firehose packaged with the tool to work in other edl flashing tools but was not able to get it working. So this is all we have for now. There is minimal risk in doing this it just has a lot of steps and it requires a pc running windows.
Note: This will wipe your device so anything stored on it will be lost please backup anything important like photos/contacts/etc
Download and install Sugar QCT from here (Be sure to install the usb drivers as well)
Included in the zip is the username and password that you will need to use to run the program please do not post it here.
Boot the device into recovery by turning the device off and then holding the power button until it restarts 3-4 times and boots to recovery
Select the option to go into emergency download mode
Now plug the device into your computer and open Sugar QCT
From the list select pepito/PVG100 (US) or pepito_vdf (Vodafone)
Now select Upgrade this will download the palms firmware package and flash it to the device
When it finishes do not close sugar
Unplug your device and hold the power button for a few minutes so it will restart out of EDL mode, use a rubber band or something to apply pressure to it so you don't have to hold it
Go to where Sugar QCT is installed (C:\Program Files (x86)\SUGAR QCT_SP_Gotu2\bin\)
In there you should see a folder called PVG100-xxxx (The x's are your serial number)
Copy that to your desktop or anywhere else that you like
In the folder, there should be some random looking mbn files these are actually the firmware files just names are randomized to make using them harder.
There should be a file called B1AMD0D0CV00.mbn if not look for a file that starts with a B it will be the boot.img
You will need to push that to an android device and patch it with magisk manager.
Once that is done replace the B1AMD0D0CV00.mbn in your copy of the firmware with the patched boot.img
Boot it back into emergency download mode as previously stated
Close and reopen sugar
Copy your firmware copy back into C:\Program Files (x86)\SUGAR QCT_SP_Gotu2\bin\ be sure it is the same folder structure
Now select your model again and then press the upgrade button in sugar this will now flash your modified firmware to the device.
Once it finishes hold the power button for a few minutes so it will restart out of EDL mode, use a rubber band or something to apply pressure to it so you don't have to hold it
When it restarts and powers up then go through setting the phone up and install magisk manager and you're rooted.
Thanks to @StormSeeker1 for telling me about holding the power button for a few minutes to get out of EDL previously you had to let the phone die to get out of it which is a pain.
Interesting, shall do it tomorrow.
Curious, this doesn't use the root exploit discussed in other threads? Where is (7) downloading from?
snoopy20 said:
Interesting, shall do it tomorrow.
Curious, this doesn't use the root exploit discussed in other threads? Where is (7) downloading from?
Click to expand...
Click to collapse
It doesn't use any root exploit, it's downloading the firmware directly from TCL servers, the tool used is designed for service centers.
If they are the same hardware, it should be possible to flash Vodaphone over the top?
snoopy20 said:
If they are the same hardware, it should be possible to flash Vodaphone over the top?
Click to expand...
Click to collapse
They are signed with different keys, so it will probably cause the device to boot loop and or not startup. I would not recommend trying it.
Is it possible to dump the radio files from an network unlocked device, and use these files to unlock Verizon network.
Any other ideas to unlock network?
Current findings:
1. Remove the Verizon sim warning.
Simply edit the /vendor/build.prop and modify line "ro.product.vzw=true" to false. However, it has a side effect, causing the contacts in dailer FC while browsering.
2. Enable diag, serial and QMI
One method is dialing "###2324#", another approach is launching "EngineerMode" through apps like quickshortcutmaker, then navigate to Connectivity - DiagProtector.
3. Boot animation path
/Vendor/JRD_custres/media/
4. Most garbage apps path
/Vendor /priv-app/
Every time I try to replace the MBN files after being patched the utility keeps redownloading the originals. Any advice?
xswxm said:
Is it possible to dump the radio files from an network unlocked device, and use these files to unlock Verizon network.
Any other ideas to unlock network?
Current findings:
1. Remove the Verizon sim warning.
Simply edit the /vendor/build.prop and modify line "ro.product.vzw=true" to false. However, it has a side effect, causing the contacts in dailer FC while browsering.
2. Enable diag, serial and QMI
One method is dialing "###2324#", another approach is launching "EngineerMode" through apps like quickshortcutmaker, then navigate to Connectivity - DiagProtector.
3. Boot animation path
/Vendor/JRD_custres/media/
4. Most garbage apps path
/Vendor /priv-app/
Click to expand...
Click to collapse
I put my t-mobile sim into mine and it worked fine no edits needed and mine is officially locked to verizon.
kotaKat said:
Every time I try to replace the MBN files after being patched the utility keeps redownloading the originals. Any advice?
Click to expand...
Click to collapse
Are you postive that the folder structure is the same?
deadman96385 said:
I put my t-mobile sim into mine and it worked fine no edits needed and mine is officially locked to verizon.
Are you postive that the folder structure is the same?
Click to expand...
Click to collapse
I am using another carrier, not USA ones, and it has problems with 4G network.
it works, thanks
Just began mind. So far it's stuck on 2%.
Regarding flashing Vodaphone over Verizon, if the ROM files are signed with different keys then modifying the boot.img will surely break the signage?
snoopy20 said:
Just began mind. So far it's stuck on 2%.
Regarding flashing Vodaphone over Verizon, if the ROM files are signed with different keys then modifying the boot.img will surely break the signage?
Click to expand...
Click to collapse
Are you still stuck at 2%? Of downloading, or of flashing?
deadman96385 said:
I put my t-mobile sim into mine and it worked fine no edits needed and mine is officially locked to verizon.
Are you postive that the folder structure is the same?
Click to expand...
Click to collapse
tapa_t said:
Are you still stuck at 2%? Of downloading, or of flashing?
Click to expand...
Click to collapse
Tried flash pvg100e over pvg100, it will stuck at the beginning and the program won't flash.
xswxm said:
Tried flash pvg100e over pvg100, it will stuck at the beginning and the program won't flash.
Click to expand...
Click to collapse
Doesn't that empirically prove that different versions have different signatures, or at least ROM's are different enough to prevent switching over? Maybe we are just so lucky that boot.img is not checked as rigorously.
Is pvg100e for Vodafone? Where did you get the ROM if your device is pvg100?
Does it finish flashing if you do pvg100 over pvg100?
tapa_t said:
Doesn't that empirically prove that different versions have different signatures, or at least ROM's are different enough to prevent switching over? Maybe we are just so lucky that boot.img is not checked as rigorously.
Is pvg100e for Vodafone? Where did you get the ROM if your device is pvg100?
Does it finish flashing if you do pvg100 over pvg100?
Click to expand...
Click to collapse
The tool deadman provided definitely works if u follow the instruction and choose the right version.
For the signature issue, maybe u can find the answer in another thread about temporary root.
As to the version problems, pvg100 is for Verizon.
To my knowledge, the pvg100e is for many other vendors, such as Vodafone, and the UK version maybe share the same model name. There is another version pvg100eu, for European. U can find more evidence in the temporary root thread.
So far the following:
Windows 10 64 - goes to 2% then after a few seconds a 5002 error.
Windows 7 64 inside Virtualbox - goes to 2% and then doesn't move.
I've tried the drivers and others on the web although the latest is around 2014/15.
xswxm said:
The tool deadman provided definitely works if u follow the instruction and choose the right version.
For the signature issue, maybe u can find the answer in another thread about temporary root.
As to the version problems, pvg100 is for Verizon.
To my knowledge, the pvg100e is for many other vendors, such as Vodafone, and the UK version maybe share the same model name. There is another version pvg100eu, for European. U can find more evidence in the temporary root thread.
Click to expand...
Click to collapse
Checked last night, mine, pvg100, is snapdragon 430, and the China mainland version is pvg100c with snapdragon 435.
deadman96385 said:
It doesn't use any root exploit, it's downloading the firmware directly from TCL servers, the tool used is designed for service centers.
Click to expand...
Click to collapse
I'm not looking to root right now, but if I'm understanding this correctly this should mean that I can use SugarQCT to pull the latest version (1AMD) firmware for my Palm that doesn't show any OTA's available and is still on the original 1AGL firmware. Is that correct?
Thanks for making this happen, deadman96385!
tapa_t said:
Doesn't that empirically prove that different versions have different signatures, or at least ROM's are different enough to prevent switching over? Maybe we are just so lucky that boot.img is not checked as rigorously.
Click to expand...
Click to collapse
No need for empirical proof, I did the analysis here.
The difference is: the early part of boot is Qualcomm code using Qualcomm security. These are the "pbl", "sbl/edl" and "aboot/fastboot" programs (and also "modem", "tz" and other bits). These were the parts that I was looking at in the link above.
When "aboot" completes, it hands over to the late part of boot, which is Android code using Google security. These are the "boot.img/Linux kernel" programs, "recovery", "system", "vendor", "data", etc. They use a different security model. That's what this root method targets. You are correct when you say "Maybe we are just so lucky that boot.img is not checked as rigorously".
It does imply that you can mix the PVG100 Qualcomm partitions for "early boot" with the PVG100E Android partitions for "late boot" and vice-versa. But someone with motivation needs to test this... (No, you can't unlock cellular bands this way; the "modem" partition is from Qualcomm and must match your hardware.)
A good diagram is below; Source (and explanation): https://blog.quarkslab.com/analysis-of-qualcomm-secure-boot-chains.html -- I recommend studying this article.
{
"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"
}
ssuds said:
I'm not looking to root right now, but if I'm understanding this correctly this should mean that I can use SugarQCT to pull the latest version (1AMD) firmware for my Palm that doesn't show any OTA's available and is still on the original 1AGL firmware. Is that correct?
Click to expand...
Click to collapse
This should work. Keep in mind that whilst 1AMD seems to be fine, future versions may (permanently) close the vulnerabilities that allow you to get root, modify system partitions or use the current version of SugarQCT. I don't think this will happen but we should all keep the possibility in mind.
Which Windows version are people using? I've tried W10 and also W7 through a virtualbox but with the above errors.
EDIT: FIXED. I flashed persist.img from version "S250260_210804..." (unzip, flash via `fastboot flash persist persist.img`) https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro/TB-J706F/
Hello dear community,
I am in need of some help. So here is what I did:
* Coming from latest Android 11 ROW, flashed ZUI using QFIL from here: https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro/TB-J706F/
* tried upgrading to ZUI 12.5, 12.6 and 13 but didn't work
* used fastboot to unlock and unlock_critical (i know, i know...)
* used payload_dumper (from some github repo) to extract zui 13 update.zip
* flashed every image I extracted manually using fastboot (I know, I'm stupid)
* Got ZUI 12.0 working, didn't like it and wanted ROW android 11 back
* flashed latest ROW rom using QFIL from lolinet url -> bootloop
* flashed oldest ROW rom using QFIL, updated 3x via OTA to latest version -> few bootloops, then device booted back to android 10 and created notification "failed to install ota"
So I can install any version between TB-J706F_S210002_201015_ROW and TB-J706F_S250260_210804_ROW from lolinet url, but nothing above that. Neither through QFIL, nor using lenovo smart rescue assistent, nor using OTA update from android 10 (which is working fine).
I tried following things to fix this:
* ####6030# -> change to CN and change the NV value to 00
* ####6030# -> change to DE and change the NV value to 02 or 00
* flash latest ROW using QFIL, then change NV value from 02 to 00
nothing of that worked and I'm starting to believe, that I ****ed up some partitions using fastboot. Because I flashed images from ZUI android 11 and I can't install ROW android 11 now.
Could I possibly try restoring a TWRP backup from some other user?
What else could I do to install android 11?
PS: I used QFIL backup and restore tool to change the NV value. Because the nv reader/writer tool didn't seem to work.
It might help, if someone would be kind enough to provide me with the following images (by backing them up with twrp):
* abl
* xbl_a
* xbl_b
Hi there, I also got into this trouble that can't flash any global ROM including TB-J706F_S250260_210804_ROW. What I did is change the NV value to 02 and not 00 using QFIL. After that I was able to update via OTA and currently on the latest global ROM.
Thanks to this thread: https://forum.xda-developers.com/t/check-region-unlock-p11-tb-j606f-l-n.4356451/
MateUserHHTTI have similar problem before, can not flash to Android 11, even ROW or ZUI, bootloop~
please check your J706F screen auto rotate and auto brightness(and pair bluetooth devices) still functional?
If not functional, I'm following below post instruction to flash presist.img, and can upgrade to Android 11, both of ROW & ZUI are available.
<TB-J706F> Auto-rotation & Auto Brightness Broken.But Serial Number shows 123456789ABCDEF, wifi /bluetooth MAC shows 00:00:00... still not solve even functional.
auston said:
But Serial Number shows 123456789ABCDEF, wifi /bluetooth MAC shows 00:00:00... still not solve even functional.
Click to expand...
Click to collapse
I may found a fix for Bluetooth MAC by generating a file for the "NV-items_reader_writer.exe" and wrote it to NV item 447 (some one sait this is BT). Problem was that this item (447) was NOT present at this time inn QCN.
WARNING! May my guess of "Items size" 128 is wrong, I don't know. Use at your own risk and change the file to your MAC.
After that I flashed "persist.img" (matching the actual ROM), some one wrote that this fixed the autorotate. I can confirm this.
But still not found solution for serial, the correct serial is still in NV item 2497.
Okay, Serial number restore can be done the same way.
See here https://forum.xda-developers.com/t/tab-j706f-serial-number.4318901/
Best would be to have the full original QCN file (or an editor for this files)
MateUserHHTT said:
* abl
* xbl_a
* xbl_b
Click to expand...
Click to collapse
abl (_a and _b) = abl.elf
xbl (_a and _b) = xbl.elf
You will find both in the ROM Zip's at lolinet.
Mine updates successfully from 10 to 11 after I have restored BT, Wifi, SN, PN and region lock. And flashed persist.img.
Oh, and you have to set region code in QCN NV 6858, somebody found out that Android 11 checks that value. If it is wrong, device boot loops.
auston said:
please check your J706F screen auto rotate and auto brightness(and pair bluetooth devices) still functional?
Click to expand...
Click to collapse
Firstly, let me thank you for your reply! It's interesting, I indeed noticed just a few days ago, that auto rotation isn't working!
I will follow the guide you linked and update my post accordingly.
Edit: THANK you very much indeed! My problem was solved instantly by this!
Flashed persist.img via fastboot, flashed the latest ROM from lolinet using QFIL and had no issues whatsoever.
Oh, and you have to set region code in QCN NV 6858, somebody found out that Android 11 checks that value. If it is wrong, device boot loops.
Click to expand...
Click to collapse
as I said in my post, I did tried both 00 and 02. I read the thread about the second region code checking.
CryptMan said:
Mine updates successfully from 10 to 11 after I have restored BT, Wifi, SN, PN and region lock. And flashed persist.img.
Click to expand...
Click to collapse
I don't have any problem but just in case...
I guess PN is Product Number where did you change it and where do you get the correct value? I only found a code before the SN that looks unique per tablet but it's not in the box.
MrCrayon said:
I guess PN is Product Number where did you change it and where do you get the correct value?
Click to expand...
Click to collapse
Well I changed the PN in NV item 2497
I found this PN number here: https://forum.xda-developers.com/t/tab-j706f-serial-number.4318901/#post-86315607
My other device, P11 (TB-J606F), has this number: 8SSP69A6PB5XHA6213L0864
Because they look pretty same (length, etc.) I decided to try it.
May somebody would confirm if this PN are the same on all device.
Open settings and type in the search bar "####2222#". That will display PN and SN.
One issue persists though, which is that my widewine level is set to L3.
1. I flashed persist.img from TB-J706F_S250260_210804_ROW
2. I then installed the TB-J706F_S620150_211226_ROW via QFIL and
3. updated to TB-J706F_S630185_220128_ROW via OTA in system settings.
My serial number is also 1-9A-F. My device is locked. I'm unlocking my device and flashing the persist.img of the latest ROM. If that doesn't work, what are my options to restore L1?
CryptMan said:
Well I changed the PN in NV item 2497
I found this PN number here: https://forum.xda-developers.com/t/tab-j706f-serial-number.4318901/#post-86315607
My other device, P11 (TB-J606F), has this number: 8SSP69A6PB5XHA6213L0864
Because they look pretty same (length, etc.) I decided to try it.
May somebody would confirm if this PN are the same on all device.
Open settings and type in the search bar "####2222#". That will display PN and SN.
Click to expand...
Click to collapse
Ah ok, so the number before SN is the PN.
I have two J706F and they have different PN, The last 8-9 digits are different and the other ones are the same.
I could not find that code anywhere else.
MateUserHHTT said:
One issue persists though, which is that my widewine level is set to L3.
Click to expand...
Click to collapse
If you check in play store settings does it say your device is certified?
On my J706F, the one on which I have lost QCN with SN MAC etc. , I have the same problem as MateUserHHTT.
The device lost L1 cert. PlayStore says NOT certified and "DRM Info" app says L3.
I also have a property "sys.lenovo.widevine_security_level" with value "L3".
My guess it that there is a file or partition holding this certifications, but I don' t know which.
And of course I don't have a backup ...
If you check in play store settings does it say your device is certified?
Click to expand...
Click to collapse
It says "Device is not certified"
Now that's curious: my tablet, running the latest Android 11 ROW version, is offering me to upgrade my device to Android Kitkat 4.4. Now that's an offer I can't resist (yes, of course I clicked "update". I want all the new features!)
{
"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"
}
CryptMan said:
The device lost L1 cert. PlayStore says NOT certified and "DRM Info" app says L3.
I also have a property "sys.lenovo.widevine_security_level" with value "L3".
Click to expand...
Click to collapse
Is your bootloader unlocked or did you unlock it previously and relocked?
MateUserHHTT said:
It says "Device is not certified"
Now that's curious: my tablet, running the latest Android 11 ROW version, is offering me to upgrade my device to Android Kitkat 4.4. Now that's an offer I can't resist (yes, of course I clicked "update". I want all the new features!)
Click to expand...
Click to collapse
Maybe the OTA app is getting some wrong data / not set data and that's the result
I tried to decompile that app to get the address called to download updates but my knowledge of android programming is really basic and did not have enough time.
MrCrayon said:
Is your bootloader unlocked or did you unlock it previously and relocked?
Maybe the OTA app is getting some wrong data / not set data and that's the result
I tried to decompile that app to get the address called to download updates but my knowledge of android programming is really basic and did not have enough time.
Click to expand...
Click to collapse
I previousl, unlocked and afterwards relocked it (both flashing lock and flashing lock_critical)
Yes, I once said "erase all before download" and accidentally deleted my original qcn file so some NV fields seem to be missing. Maybe that caused the app to default back to 4.4 it was Lenovo Feature Updater by the way, not the settings - system - update.
If you share your past work in a git repo I will take a look at it. I'm no expert for sure but I'm developing fir android for some years and have stuck my nose a tiny bit under the surface of android rom development (1mm and it was very painful still).
My widewine lvl is L3. Any chance of resetting to L1 myself? I don't know much about how trust attestation works. :/
MateUserHHTT said:
It was Lenovo Feature Updater by the way, not the settings - system - update.
Click to expand...
Click to collapse
I disabled that as soon as I saw it
MateUserHHTT said:
If you share your past work in a git repo I will take a look at it. I'm no expert for sure but I'm developing fir android for some years and have stuck my nose a tiny bit under the surface of android rom development (1mm and it was very painful still).
Click to expand...
Click to collapse
Not much really, I'm not at my desk now but I extracted LenovoOTA from stock ROM and decompiled it with apktools, but even with online tools is probably ok.
Then I see two options:
Recompile that package changing package name and adding a log with full address and parameters or get the code that construct the URL and put it in a new app.
For you probably the last one is easier.
I went for a third I was trying to understand if i could get the data with adb or in files but I did not find documentation.
MateUserHHTT said:
My widewine lvl is L3. Any chance of resetting to L1 myself? I don't know much about how trust attestation works. :/
Click to expand...
Click to collapse
I don't think there is a way to force it, this widevine a thing is a pain.
MrCrayon said:
Is your bootloader unlocked or did you unlock it previously and relocked?
Click to expand...
Click to collapse
Locked, and was never unlocked before.
I tried to unlock now, but does not succeed with flashing sn.img.
Because I'm not interested on Custum ROM, I will leave it locked.
Do you know where the device certification is stored?
I unlocked without flashing sn.img. Does that make a difference?
Did you try monitoring the network traffic with wireshark?
I AM NOT RESPONSABLE IF YOU BREAK YOUR DEVICE OR ANY DAMAGE CAUSED BY NOT FOLLOWING INSTRUCTIONS.
Requirements:
Unlocked Bootloader
Removed Vbmeta verity (Boot Patched with magisk)
ADB and Fastboot: Adb
A GSI Rom: GSI Rom List
ENG ABL (In case you brick the device and you want to go to fastboot)
Enabled USB debugging on developer Options
Developer Options go to Settings => System => About Phone => Software Information and tap Build Number until it either asks you for your password or says you are a developer at the bottom
A Brain
Instructions:
Before doing anything make sure you have a backup of your device partitions.
All your data of the internal memory will delete.
1. Put the GSI you have downloaded from your choise (Make sure you have extracted the File) on the same folder than your Fastboot)
{
"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"
}
2. Open a CMD window on the same folder than Fastboot ( Right click + shift key on the fastboot folder and select open command prompt)
3. Run adb devices and make sure it says Device and not Unauthorized.
4. Write the command Adb reboot fastboot
5. On the Phone You will see a Fastbootd screen ( Image is an example, I dont have a camera with me at the time of doing this Guide)
6. Run Fastboot Devices and make sure your device is showing there
7. write the command fastboot getvar all to check your boot slot
8. Execute fastboot flash system_(Put your slot from previous step) the image name of your gsi.img, and wait until everything download and make sure that every single sparse sent says Okay
8. After Last step just execute fastboot erase userdata
9. just reboot the device and enjoy
Any additional question or issue just let me know and I will help you Gladly as soon as I can
Worked perfectly on my att LG v60. Cheers. it's my backup phone but thanks for giving it new life. LG software sucks. Doing this later on with my second LG v60.
Jaimesco12 said:
Worked perfectly on my att LG v60. Cheers. it's my backup phone but thanks for giving it new life. LG software sucks. Doing this later on with my second LG v60.
Click to expand...
Click to collapse
I agree. Oem software is so loaded with bloatware and bull****. And then of course ALL the carriers pile on their **** and suddenly you have a smartphone that's not really a phone anymore. It's now just a tracking/marketing device that happens to let you make phone calls, send emails. and surf the web so you can provide cookies to be uploaded when you're not looking.
I do give credit to Apple for pulling in the reins on Facebook. Hopefully, Google will be forced to do the same. They're the biggest tracker/marketer of information out there.
Btw, I've been running an a12 gsi rom for several weeks now. First, I tried the Andy Yan LOS19 vndklite secured rom but unfortunately it didn't gapps capability which is sort of a no go for a lot of people. I then switched to Phhusson' vndlite secure with gapps rom and it's been great. So far everything seems to work great except Qdaq.
Damn. Now I may have to build my phone for the second time in a week. One question:
1) How/where do I get the LG apks to properly make use of the phone's hardware? I'm thinking camera, FM Radio and DAC specifically. Plus any others I may be missing. Or is that step not necessary?
[NG]Owner
NGOwner said:
Damn. Now I may have to build my phone for the second time in a week. One question:
1) How/where do I get the LG apks to properly make use of the phone's hardware? I'm thinking camera, FM Radio and DAC specifically. Plus any others I may be missing. Or is that step not necessary?
[NG]Owner
Click to expand...
Click to collapse
I'm already working on porting stock apps to Custom including the Quad-Dac, i dont have an ETA for ir right now but its on the way
Jaimesco12 said:
Worked perfectly on my att LG v60. Cheers. it's my backup phone but thanks for giving it new life. LG software sucks. Doing this later on with my second LG v60.
Click to expand...
Click to collapse
I'm happy to hear that it helped you
Does Android Pay work on this?
Will this process also work for the v40 as well? And if so, can I expect the IMS stack to work on the v40 such that VoLTE and WiFi Calling on Tmo can be enabled?
For that matter do/will VoLTE and WiFi Calling work on TMo using GSI ROMs on a v60?
[NG]Owner
failed, kernel crash, dont't know the reason
update: show no command
I'm assuming that if I install a GSI on the V60, I lose dual-screen usage correct?
jblparisi said:
Does Android Pay work on this?
Click to expand...
Click to collapse
Depends of the GSI you have chosen, some of them comes with Safetynet already approved
peterwode said:
failed, kernel crash, dont't know the reason
Click to expand...
Click to collapse
Make sure alll sparces says OK, also if you are on android 11 you cannot flash a GSI with android 10
Play4Zeta said:
I'm assuming that if I install a GSI on the V60, I lose dual-screen usage correct?
Click to expand...
Click to collapse
I havent tested that, I broke mine a while ago
Kratos574 said:
I havent tested that, I broke mine a while ago
Click to expand...
Click to collapse
Any reason you would think it wouldn't? Mostly just have my V60 for the dual screen.
Jaimesco12 said:
Worked perfectly on my att LG v60. Cheers. it's my backup phone but thanks for giving it new life. LG software sucks. Doing this later on with my second LG v60.
Click to expand...
Click to collapse
Hey mate, you could tell me how you did the prep work to install the GSI room on the ATT variant? Ive been trying to unlock it and installing TWRP but i havent found a reliable way of doing it.
Do you know what rooms work well with the v60? (like having QDAC functionality for instance)
Kratos574 said:
I'm already working on porting stock apps to Custom including the Quad-Dac, i dont have an ETA for ir right now but its on the way
Click to expand...
Click to collapse
wait Quad-Dac
Just wanted to say a big thanks to Kratos for putting this post together. I had some early issues but it turns out that's because I was using 'Minimal ADB and Fastboot'
For whoever comes next here's how I fixed a couple of problems as I went.
ERROR: Failed: remote partition not found - You need to be in fastbootD via ADB REBOOT FASTBOOT, not the fastboot/bootloader via turning off device, holding vol down and plugging in a usb cable.
ERROR: Remote: Operation not permitted. - Minimal ADB and Fastboot is not new enough - download latest SDK platform tools and open an administrator CMD prompt from that directory instead.
Other errors or failure of individual parse files can be fixed by using a better quality cable - you're sending a lot of data via fastbootd. Give yourself the best shot at success.
I installed OctaviOS yesterday and was absolutely blown away - it's extremely fast, the battery life is incredible and the level of deep customisation rivals any rom I've ever used.
Unfortunately, haptic feedback / vibration does not work AT ALL, and nor does the 3.5mm Jack. Also GCAM, nor any other camera app I tried was able to access the wide angle lens so I'll be trying to figure out how to get back to EA firmware today for now.
If someone with the skills could manage a non-gsi port of OctaviOS with cam, haptic and 3.5mm working properly I'd be on it in a heartbeat. THAT is what Android should be. Bloat free but highly customisable.
bandario said:
Just wanted to say a big thanks to Kratos for putting this post together. I had some early issues but it turns out that's because I was using 'Minimal ADB and Fastboot'
For whoever comes next here's how I fixed a couple of problems as I went.
ERROR: Failed: remote partition not found - You need to be in fastbootD via ADB REBOOT FASTBOOT, not the fastboot/bootloader via turning off device, holding vol down and plugging in a usb cable.
ERROR: Remote: Operation not permitted. - Minimal ADB and Fastboot is not new enough - download latest SDK platform tools and open an administrator CMD prompt from that directory instead.
Other errors or failure of individual parse files can be fixed by using a better quality cable - you're sending a lot of data via fastbootd. Give yourself the best shot at success.
I installed OctaviOS yesterday and was absolutely blown away - it's extremely fast, the battery life is incredible and the level of deep customisation rivals any rom I've ever used.
Unfortunately, haptic feedback / vibration does not work AT ALL, and nor does the 3.5mm Jack. Also GCAM, nor any other camera app I tried was able to access the wide angle lens so I'll be trying to figure out how to get back to EA firmware today for now.
If someone with the skills could manage a non-gsi port of OctaviOS with cam, haptic and 3.5mm working properly I'd be on it in a heartbeat. THAT is what Android should be. Bloat free but highly customisable.
Click to expand...
Click to collapse
Just go to Phh Settings and click on Alternate audio policy, That fixes 3.5mm jack
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 6a devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.
This seems interesting. I was just looking into options to disable verity and or verification, root, and flash a custom kernel. It seems this application is an all in one. If all goes as planned, will my data and apps remain? Or am I basically starting all over. My bootloader is already unlocked. Thanks for sharing.
chopt51 said:
This seems interesting. I was just looking into options to disable verity and or verification, root, and flash a custom kernel. It seems this application is an all in one. If all goes as planned, will my data and apps remain? Or am I basically starting all over. My bootloader is already unlocked. Thanks for sharing.
Click to expand...
Click to collapse
If you don't choose wipe data, or force in flash options, then you should keep your data.
I have my 6a connected with usb. I chose where my platform tools are in a directory but it doesnt find a device via adb. Yet cmd shows an adb connection.
USB debugging turned on?
tlxxxsracer said:
Yet cmd shows an adb connection.
Click to expand...
Click to collapse
Explain what you mean by that?
badabing2003 said:
Explain what you mean by that?
Click to expand...
Click to collapse
usb debugging was on. when I run an adb/fastboot in cmd within the same directory my device is recognized
tlxxxsracer said:
usb debugging was on. when I run an adb/fastboot in cmd within the same directory my device is recognized
Click to expand...
Click to collapse
Please be clear and explicit, exactly what you ran and what response you got, please also generate support.zip file from the help menu of PixelFlasher and post it here.
There is no reason for it not to be detected if you're command detects it.
New Release:
Aug 24, 2022 v3.6.0 release
When a device is selected, the Bootloader version is displayed. (Useful for Pixel 6* devices with ARB). Works in adb and fastboot modes.
Added a button to dump full device info (useful for troubleshooting). Works in adb and fastboot modes.
Improved tooltips.
Hello,
I have a pixel 6a on A12 rooted with Magisk.
I tried to upgrade to A13 with PixelFlasher (v3.6.0) with the option to flash all the slots and now I'm stuck in loop.
I tried to use fastboot command to flash again with A13 with no result. I also tried to change the current slot.
The weird thing is that I still have the message that said the bootloader is unlocked...
Any ideas?
jpdurand31 said:
Hello,
I have a pixel 6a on A12 rooted with Magisk.
I tried to upgrade to A13 with PixelFlasher (v3.6.0) with the option to flash all the slots and now I'm stuck in loop.
I tried to use fastboot command to flash again with A13 with no result. I also tried to change the current slot.
The weird thing is that I still have the message that said the bootloader is unlocked...
Any ideas?
Click to expand...
Click to collapse
If you can post support.zip file from help menu I can take a look.
If you want more info, i'm 100% available!
jpdurand31 said:
If you want more info, i'm 100% available!
Click to expand...
Click to collapse
Hmmm ...
I don't see any flashing logs in PixelFlasher, are you sure you flashed in PixelFlasher?
I see you started with PixelFlasher 3.4.0 and upgraded to 3.6.0; good
I see at first you did not have Android Platform Tools installed, and then had version 28.0.2-debian; bad, this is an old version, you should click on the blue link next to the Android Platform Tools and download the latest (don't install from package manager, those are usually old, just download the latest and unpack wherever you want, and point to it in PixelFlasher)
You started in adb mode (good), processed the firmware in PixelFlasher, but that is where you stopped, you did not attempt flashing in PixelFlasher (not sure what you did, but it would help to know)
On next attempt (one hour later) your device was in bootloader mode.
Then you tried disabling magisk, which didn't work because that feature requires adb mode, and your phone is stuck in fastboot mode.
You cannot create a patch file in fastboot mode, it needs to be in adb mode.
And please please don't dare to lock your bootloader, I see you attempted and then cancelled,
Code:
2022-09-02 18:25:29 Lock Bootloader
WARNING!!! WARNING!!! WARNING!!!
NEVER, EVER LOCK THE BOOTLOADER WITHOUT REVERTING
TO STOCK FIRMWARE OR YOUR PHONE WILL BE BRICKED!!!
Do you want to continue to Lock the device bootloader?
Press OK to continue or CANCEL to abort.
2022-09-02 18:25:42 User Pressed Cancel.
Aborting ...
If you lock your bootloader before fixing your device, you will be locked out forever (bricked)
So at this point what are your choice and how can you fix this?
1- get the latest Android Platform Tools
2- If PixelFlasher detects your device, check if it is in fastboot mode (f.b) or adb mode.
Select the firmware, process it, this will show the boot.img file
Select the boot.img file and choose keep data and hit Flash.
Yes I know, you will lose root because you're not flashing a patched boot.img, but you can always re-root if you recover your device.
Alternately, what happens if you select in PixelFlasher to reboot the device into System.
Does it reboot? and if it does, does it end up in adb mode of fastboot mode?
One other option you have is to flash OTA in sideload mode.
Report back, and make sure you capture all the manual steps you perform outside of PixelFlasher.
PixelFlasher logs would tell me everything you do in PixelFlasher, you can submit a new one after your operations.
Good luck
Thanks for your response and the detailed process.
I was fooled by the version of the package that was in 33...
By upgrading the Android Platform Tools to the latest version, I could update to Android 13.
Thanks a lot for the help and the reactivity!
New Release:
Sep 04, 2022 v3.7.0 release
New Feature: Install Magisk into the phone, PixelFlasher displays information about the latest available Magisk versions (stable, beta, canary, debug) and offers the choice to install a selection.
New Feature: Install compatible apk file onto the device from PixelFlasher menu.
Check Android Platform Tools version and warn if it is old.
Block flashing when stock flash_all.bat file is tampered with.
Don't bother with flashing if bootloader is locked.
More validations and exceptions handling.
Improved logging.
3.7.0 does not start for me on Windows 10. It never appears in my task list as running. 3.6.0 is working fine.
JudasD said:
3.7.0 does not start for me on Windows 10. It never appears in my task list as running. 3.6.0 is working fine.
Click to expand...
Click to collapse
Thanks for reporting and sorry for your troubles.
Can you please open a command prompt, navigate to PixelFlasher 3.7.0 and run it from command prompt (just type PixelFlasher.exe), see if it displays an error in the console.
Can you also please generate a support.zip file using PixelFlasher 3.6.0 ?
It should capture the error PixelFlasher 3.7.0 encountered.
Thank you for the help. The issue has now been resolved after reboot.
Launching 3.7.0 via cli displayed no error message. I went to create support.zip with 3.6.0 and my computer BSODed. After reboot, 3.7.0 runs just fine. Apologies for the false alarm.
JudasD said:
Thank you for the help. The issue has now been resolved after reboot.
Launching 3.7.0 via cli displayed no error message. I went to create support.zip with 3.6.0 and my computer BSODed. After reboot, 3.7.0 runs just fine. Apologies for the false alarm.
Click to expand...
Click to collapse
No need for apology, happy to hear that the issue now resolved.
Not sure if this should be of concern, but upgrading to today's Android release, I got this (very early on, while selecting the device and firmware):
Code:
2022-09-12 18:44:06 ERROR: Exception during Magisk modules processing
Exception: not enough values to unpack (expected 2, got 1)
Everything seemed to work fine, though.