Database Info

[Q] LG Thrill 4G new ROM Help

I have a LG Thrill 4G. I rooted the phone using superonelick, root checker says it is rooted. Downloaded ROM Manger and flashed clockworkmod. I cannot click boot into recovery, it just restarts the phone. I have tried to reboot into recovery by pressing 3d button, down volume, and power and it boots me into the android recovery but not clockworkmod, so I can not find anyway in to download the new rom from the zip file. Has had any other people had trouble with this? I have spent over 2 days searching the internet but I cannot find any similar problems, is there anyway to get into the recovery mode to install the new ROM without it just restarting the phone?

LG Thrill 4G ClockworkMod Installation (correct method)
1) You need to have ROOT access at the least (see link below)
It will also be good to have ADB (and hence LG Thrill drivers) installed properly
http://forum.pandaapp.com/thread/2/11/20110919/4e77f603d22632913-1.html
2) Get the recovery image from here and keep it on your PC in a folder accessible by ADB.
OR (if no ADB then) directly put it on your LG Thrill SDCard root
http://forum.xda-developers.com/showthread.php?t=1257588
4) If you have ADB then follow the instructions in the first link above to push the recovery image to your phone.
OR
if no ADB then open Terminal Emulator (install it from Market) and type su and click allow if the prompt comes up
5) Now you can follow instructions in the first link (far above) again, starting from the 'dd if=...' step. But instead of rebooting you could just power off
6) Clockwork recovery should now be flashed. To enter recovery, keep the 3D button, Vol-down and Power button pressed until you see the LG logo

Thank you for getting back with me. I tried to follow these steps and when I am in the Terminal Emulator and type adb push recovery.img /data it comes back with adb: not found. I have redownloaded the recovery file that you have attached to the SD card, same error, and then I tried to copy to the phone itself and same error. I can do any of the other prompts for the emulator but nothing that has to do with the recovery file it will not work. I am guessing maybe this is the problem because if it cannot find the recovery file, I cant do much of anything else. Do you have any suggestions of why the file still cannot be found on my phone?

connect adb through tcp
Try this:
1. If you are using terminal emulator to access adb then try downloading the app called remote adb. This tool will allow you to connect your device via tcp. Take note of the ip adress and port number. Usually the default port is fine.
2. Now open sshdroid, connectbot, terminal emulator and start an ssh session with the adb shell. You must have the correct public ip and port entered in to access the adb via tcp.
3. Once you have made the ssh connection between what ever emulator you are using and remote adb, start a shell as su.
4. Type the commands mentioned earlier.
This should let you run the whole thing from within your phone.
Alternatively...
1. start remote adb on your device.
2. start a terminal or cmd prompt on your cpu.
3. cd to androidSDK\platform-tools
4. type ---> adb start-server
The server then sets up connections to all running emulator/device instances. It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585, the range used by emulators/devices. Where the server finds an adb daemon, it sets up a connection to that port.
Note that each emulator/device instance acquires a pair of sequential ports — an even-numbered port for console connections and an odd-numbered port for adb connections. For example:
Emulator 1, console: 5554
Emulator 1, adb: 5555
Emulator 2, console: 5556
Emulator 2, adb: 5557 ...
As shown, the emulator instance connected to adb on port 5555 is the same as the instance whose console listens on port 5554.
Once the server has set up connections to all emulator instances, you can use adb commands to control and access those instances. Because the server manages connections to emulator/device instances and handles commands from multiple adb clients, you can control any emulator/device instance from any client (or from a script).
5. type --> adb forward tcp:5554 tcp:5555
5. type ---> adb devices. In response, adb prints this status information for your device. If there is no emulator/device running, adb returns no device, and you have not made a tcp connection.
6. Take note of the serial number listed. You will use it later to direct commands to device.
7. Type --> adb shell
8. Type --> su
9. Use commands from other post to achieve whatever you need.
10. once finished with shell, type --> exit twice to leave the shell
11. Finally, type --> adb server-kill
Hope that helps. Seems like you were having issues making the connection from device to adb, so that is what I focused on. If I can help anymore, just ask. We are all continually learning and the only stupid question is the one never asked.
B^)

sensation stuck on bootloop

i rooted my phone and followed the guide in
http://www.androidauthority.com/how-to-root-htc-sensation-21697/
which worked great and had my phone rooted with S-OFF and full control
then i went to this page and wanted to install a rom and chose
http://forum.xda-developers.com/showthread.php?t=1468683
which i downloaded, after trying to follow the instructions the firmware would install and gave installation aborted so i installed the rom anyways
now the phone boots into the rom but freezes before the loading the phone and restarts.
i am stuck in boot-loop and when trying to recover using the backup it still boot-loops
i think the boot files are corrupt, and i have also tried super-wipe, (super-wipe V2 would load)
even after this i tried installing the custom rom and the backup version and still not working
the firmware still does work and i have tried loading the backup 6 times now using as many different methods such as clearing cache..etc
i even found programs uses to 4EXT_Recovery_Touch_v1.0.0.4_RC3_flashing_tool
and ADB_Fastboot_Windows
but those wont work unless the phone is started and in htc sync/usb mode.
any help would be grateful, i am really getting stressed out for not being able to use my phone

1)You know how to boot into HBOOT, or the bootloader? Do just that.
2) Connect your phone to your computer. You must have all the ADB and SDK drivers installed.
3)Navigate to "Fastboot" using your phones Volume UP and DOWN keys until you reach fastboot. Select using the power button.
4) Go into cmd in Windows.
5)Type the following:
cd C:\Program Files\Android\android-sdk\platform-tools
6)Type the following:
adb getvar cid
7) Remember what the previous command just told you. It could be HTC_001 for example.
8)Thanks to this dev, go to this thread. Find this in the first post:
Firmware from 3.32.401.x & 3.32.401.10x RUU
9)See if your CID is listed. If it is not, DO NOT TRY FLASHING THIS. If it is, download the file and flash in HBOOT using the PG58IMG.zip method. Make sure it isn't called PG58IMG.zip.zip.
10) If it isn't listed, use STEP 4 in this post, then flash it.
RE-POST THIS!!! Save devs time to building ROMs and save hassle.

i have followed your steps to number 3, now it says "fastboot ac" on phone
with step 5 i found the folder in this directory
C:\Program Files (x86)\Android\android-sdk
after typing in the command after navigating there i get this
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Owner>cd C:\Program Files (x86)\Android\android-sdk\platform-tools
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb getvar cid
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
and now im stuck as to where to find htc_001
sorry for sounding noobish as im new to this but can you please tell me what i have done wrong to where to go from here ??

Once in that directory type fastboot getvar cid
Then write down the CID that shows up.
If it doesn't match one in the list of compatible firmware then you'll have to super CID to 11111111.
Edited because I wasn't thinking.

You have to use fastboot, not adb
Sent from my HTC Sensation with Beats Audio using xda premium

ok i have tried that now it is saying "waiting for device"
the phone is still not being picked up by the computer either by htc sync or by the program through command prompt.
fastboot changes to fastboot ac, not sure if that means its just on charge only and not any other mode

Unplug the phone and pull the battery. Then boot the phone back into the initial recovery screen (vol down + power on)
Connect phone to computer. In a cmd prompt navigate to cd C:\Program Files\Android\android-sdk\platform-tools
Type adb devices (Should come back with serial number)
Type fastboot getvar cid
Hopefully that pulls the CID. Let us know.

i have tried this over several times , it still does not pick up the device.
any other ways to get this to work ??

Have you just installed the SDK? Open the SDK, and a pop-up should come up. Select Android USB drivers or something similar to it. Check it and install. Try again after this.
Sent from my Wildfire using Tapatalk 2 Beta-5

You also need to have your fast boot drivers in the directory that you cd to to issue your fastboot commands.
sent from HTC Pyramid using Tapatalk

usaff22 said:
Have you just installed the SDK? Open the SDK, and a pop-up should come up. Select Android USB drivers or something similar to it. Check it and install. Try again after this.
Sent from my Wildfire using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
stringer7 said:
You also need to have your fast boot drivers in the directory that you cd to to issue your fastboot commands.
sent from HTC Pyramid using Tapatalk
Click to expand...
Click to collapse
i have made sure that the usb drivers have been installed infact i uninstalled htc sync and android sdk and reinstalled them both and made sure the drivers are installed.
on there is doesnt say anything like android usb drivers but Google usb drivers is the closest, basically the default settings installed.
for the drivers htc sync has been installed it is also failing to detect my phone.
stringer7, i have made sure i am in the directory and it checks for devices, but it fails to find my htc sensation.
Ive had this phone for 2 months now of a 24 month contract.
now i just want to reformat it all and install the stock version over, and see if i can get my backup back as it has all my contacts and messages on it which i thought were on the sim.

wbb1 said:
i have made sure that the usb drivers have been installed infact i uninstalled htc sync and android sdk and reinstalled them both and made sure the drivers are installed.
on there is doesnt say anything like android usb drivers but Google usb drivers is the closest, basically the default settings installed.
for the drivers htc sync has been installed it is also failing to detect my phone.
stringer7, i have made sure i am in the directory and it checks for devices, but it fails to find my htc sensation.
Ive had this phone for 2 months now of a 24 month contract.
now i just want to reformat it all and install the stock version over, and see if i can get my backup back as it has all my contacts and messages on it which i thought were on the sim.
Click to expand...
Click to collapse
u mean that you boot into bootloader, u see written HBOOT on the screen, then u connect the usb cable coming from a computer on which both htc sync and ADK/SDK installed (not running, but installed) and HBOOT turns into FASTBOOT USB on the screen but u cant send fastboot commands?

dowanrac said:
u mean that you boot into bootloader, u see written HBOOT on the screen, then u connect the usb cable coming from a computer on which both htc sync and ADK/SDK installed (not running, but installed) and HBOOT turns into FASTBOOT USB on the screen but u cant send fastboot commands?
Click to expand...
Click to collapse
when i connect the phone to my computer i manually go to fastboot option using the power key then from there it will say fastboot ac
or if i connect after in fastboot it will change to "fastboot ac"
now im gonna try reinstall the whole setup on another machine or try dualboot with ubuntu and try the drivers through that,

wbb1 said:
when i connect the phone to my computer i manually go to fastboot option using the power key then from there it will say fastboot ac
or if i connect after in fastboot it will change to "fastboot ac"
now im gonna try reinstall the whole setup on another machine or try dualboot with ubuntu and try the drivers through that,
Click to expand...
Click to collapse
grab a photo of the screen - bootloader screen when u connect. lets see what u got there.
i think its only a communication problem with pc. message on screen should be fastboot USB. not fastboot AC. so it means u simply dont have the proper drivers. if u get a different computer, just install htc sync, reboot computer after that and make sure htc sync program aint running. then connect phone in bootloader. if it says fastboot usb, go to ADK step. if not... weird...

dowanrac said:
grab a photo of the screen - bootloader screen when u connect. lets see what u got there.
i think its only a communication problem with pc. message on screen should be fastboot USB. not fastboot AC. so it means u simply dont have the proper drivers. if u get a different computer, just install htc sync, reboot computer after that and make sure htc sync program aint running. then connect phone in bootloader. if it says fastboot usb, go to ADK step. if not... weird...
Click to expand...
Click to collapse
heres the photo of the bootloader that shows when connecting to pc
{
"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"
}
i also tried this on another computer and it still shows the same message. i would try on linux ubuntu but cant seem to find htc sync for it.
any more ideas ??

Try Google USB Drivers. Install that.
And please DO try and make your pictures a bit smaller

ok i found out my usb cable was the reason and now after getting a new one i get "fastboot usb"
after typing the code on first page i get this, the device is not listed but it shows htc_001 with getvar cid
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar cid
cid: HTC__001
finished. total time: 0.002s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
i am now going to try supercid to see if i can move forward in finally getting my phone working.
EDIT:
it is working now, after 3 long days of no phone,
after installing the rom i used my backup to "advanced backup" to get my data back which gave my old apps and messages along with contacts

Not able to download firmware from link provided.
usaff22 said:
1)You know how to boot into HBOOT, or the bootloader? Do just that.
2) Connect your phone to your computer. You must have all the ADB and SDK drivers installed.
3)Navigate to "Fastboot" using your phones Volume UP and DOWN keys until you reach fastboot. Select using the power button.
4) Go into cmd in Windows.
5)Type the following:
cd C:\Program Files\Android\android-sdk\platform-tools
6)Type the following:
adb getvar cid
7) Remember what the previous command just told you. It could be HTC_001 for example.
8)Thanks to this dev, go to this thread. Find this in the first post:
Firmware from 3.32.401.x & 3.32.401.10x RUU
9)See if your CID is listed. If it is not, DO NOT TRY FLASHING THIS. If it is, download the file and flash in HBOOT using the PG58IMG.zip method. Make sure it isn't called PG58IMG.zip.zip.
10) If it isn't listed, use STEP 4 in this post, then flash it.
RE-POST THIS!!! Save devs time to building ROMs and save hassle.
Click to expand...
Click to collapse
Hello,
Im in the same situation and I know how to boot load the firmware. My problem is that when I go to the link provided to download Firmware 3.32.401.x & 3.32.401.10x RUU, it sends me to another website that is down. is there somewhere ales I can find this file? I have been trying for days and I always get the following message.
Not Found
The requested URL /db_mirror/ROMs/HTC Sensation/Firmware/3.32.401.x/PG58IMG.zip was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2 Server at xda3.androidrevolution.nl Port 80

[GUIDE]List all installed apps that don't allow adb backup

Some apps can't be backed up using adb backup. It is mainly because on its AndroidManifest.xml the flag android:allowBackup is either not set or set to "false". This tutorial will get you a list of apps that are currently installed on your device but will not be backed up, either using the official adb backup, LG Backup, Sony Backup and Restore, etc. (because they all use adb backup internally). So you can be cautious on advance and you are aware that the backup methods used officially have its flaws.
1) REQUIREMENTS
I will make the list of apps using a computer, so you need several things set up on the computer and the android phone.
1.1) SMARTPHONE REQUIREMENTS
-> USB Debugging enabled: How to enable USB Debugging on Android [Youtube]
1.2) COMPUTER REQUIREMENTS
-> aapt.exe and adb.exe installed. I recommend to install the Android Studio Bundle. The binaries will be installed in a path similar to this:
Code:
C:\Users\YourUser\AppData\Local\Android\sdk\build-tools\24.0.3\aapt.exe
Code:
C:\Users\YourUser\AppData\Local\Android\sdk\platform-tools\adb.exe
-> Add the paths of aapt.exe and adb.exe to your current PATH in Windows: How to Edit Your System PATH for Easy Command Line Access in Windows
-> Cygwin is mandatory to run bash commands on Windows. The x86 version is recommended because it has more commands than the 64bit version. This is where you will actually type the commands.
-> adb drivers for your smartphone. Windows 10 usually will install them flawlessly.
2) GETTING THE LIST OF APPS THAT DON'T ALLOW ADB BACKUP
2.2) CHECKING FOR SOFTWARE AND SMARTPHONE
Go into cygwin to a working directory to store there your temporary files:
Code:
cd /cygdrive/c/Temp/
Check with Cygwin that you PATH is currently set and that adb.exe and aapt.exe are usable:
Code:
which adb
/cygdrive/c/Users/Admin/AppData/Local/Android/sdk/platform-tools/adb
which aapt
/cygdrive/c/Users/Admin/AppData/Local/Android/sdk/build-tools/24.0.3/aapt
Now connect your android smartphone to the computer with the screen unlocked, accept any data connection (use MTP method if asked or from notifications panel), authorize the computer and run on Cygwin:
Code:
adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
LGH815b4b2c42e unauthorized
adb devices
List of devices attached
LGH815b4b2c42e device
2.3) GETTING THE LIST OF ALL APPS ON THE DEVICE
On this step, a list of all apps on the smartphone, will be saved to a file called all_packages.txt in the format of package name. That string that appears at the end of the url when you browse an app on the Play Store.
Code:
adb shell pm list packages | grep -v '^$' > all_packages.txt
UNDER CONSTRUCTION. WILL REPLY WHEN FINISHED. SUBSCRIBE IF YOU ARE INSTERESTED

It looks like somebody released an application for that and works great:
No ADB backup app lister

Disable Heads Up/Peek Notifications For Android Nougat 7.0 with ADB

Hello guys just want to share it.
If you want to disable the annoying Heads Up/Peek Notifications fellow these steps.
First install this: Mega Link to ADB Just click on it type 3 times [Y]
1.) Open a command prompt and check if the device is connected using the following command:
adb devices
2.) You should see your phone on the list that appears. Now use the following command:
adb shell settings put global heads_up_notifications_enabled 0
3.) Reboot your phone and you are done!

Good luck!

[Guide] Android 11 on PH-1 - what worked for me

[Disclaimer: Should anyone decide to follow these instructions, they will be doing so at their own risk. Bad Things™ could happen, and you, and you alone, my fellow traveler, are responsible for your choice to follow this path, and for understanding and accepting full consequences of flashing non-OEM phone firmware. I, myself, do not have enough know-how to help you should things turn not as expected, as all the heavy lifting has been done by others, and I thank them all. Support those that support us!]
Some background; after the post [https://forum.xda-developers.com/t/gsi-rom-aosp-android-gsi-support-for-essential-phone.4326297/] that introduced me to using GSI (Generic System Image) builds as daily drivers, I’ve tried a handful of them (as collected on P.H. Husson’s treble_experimentations page) with a varying degree of success. The build that has delivered the smoothest experience out-of-the-box for me has been the Octavi GSI [https://octavi-os.com/].
-- What’s needed --
- From this page download - Essential PH1 window drivers and The latest official ROM
- Download Android build tools, AOSP.zip given in this post, and this OctaviOS GSI build for full Google experience [some other builds are on this page. NOTE: PH-1 takes ARM64, ab (system-as-root), and project Treble (the vndk part) compatible variant.
-- The work –
- Preparations: (Refer to this page for the excellent overview on working with ROM images done by Vigasaurus, especially the section How to Flash (for Fastboot only)).
On the desktop:
- Install Essential drivers
- Create a work folder, let’s say A11, and unzip the platform tools files (from the ‘platform_tools’ subfolder) there. This folder will then have ‘adb’, and ‘fastboot’ executables.
- Unzip the content of PH1-Images-QQ1A.200105.032.zip to A11
- Unzip the content of AOSP.zip to A11 overwriting all (3) files.
- Unzip OctaviOS firmware to A11 folder
- Open command line and go to A11 folder
- connect the phone to your computer
Then type:
Code:
adb devices
(the response should be a string of numbers (the phone's serial number) followed by the word ‘device’
On the phone (if not done already):
- Tap Settings, then tap System > About phone and scroll to the bottom of the page, then
- Tap Build number multiple times until you see the pop-up message “You are now a developer”
- Go back one screen to System, then tap Developer options and enable OEM Unlocking and USB debugging.
Back on the desktop type:
Code:
adb reboot bootloader
and if not done already, type:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
then:
Code:
fastboot set_active a
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot format userdata
fastboot reboot
After phone reboots type:
Code:
adb root
adb disable-verity
adb reboot bootloader
Now, edit flashall.bat to replace ‘system.img’ with OctaviOS image. In my case those two lines look like this:
Code:
fastboot flash system_a OctaviOS-v2.9-arm64_bgN-vndklite-20210918-Official.img
fastboot flash system_b OctaviOS-v2.9-arm64_bgN-vndklite-20210918-Official.img
- Save and run flashall.bat
At this point your device will boot the new firmware. If how you use your phone does not require rooting, you are done. Go through the initial setup steps and profit!
For those who need root:
- Download Magisk Manager and put, and install it on your phone.
- Enable Developer (as above) and USB debugging
On command line in A11 folder push the Magisk app and boot.img to the phone:
Code:
adb push boot.img /sdcard/Download
adb push Magisk-v23-0.apk /sdcard/Download
On the phone, install the Magisk app and start it up.
then
Tap Install, tap Method, then select file, and choose the boot.img from Download folder
Back on command line:
Code:
adb shell ls /sdcard/Download
adb pull /sdcard/Download/[name-of-magisk-patched-image]
adb reboot bootloader
fastboot flash boot_a [name-of-magisk-patched-image]
fastboot flash boot_b [name-of-magisk-patched-image]
fastboot reboot
Then, back on the phone:
- Start Magisk app
- Tap settings icon (upper right) and activate MagiskHide
- Exit and tap Check SafetyNet to make sure it’s all good.
Now, profit!
[Final advice: I've turned off any AOD, Daydream, and PocketDetection settings, as they severly impact battery use. After that, it's been smooth sailing]