[Tool] NoKDZ extensible flash tool for LG devices (and possibly others) - Android Software/Hacking General [Developers Only]

I thought I would post this here as I thought that several LG devices do not have .kdz files available, making it very problematic to restore the firmware to a stock state.
I originally encountered this problem with the LG Aristo 2 plus, a mid-range T-Mobile phone.
Apparently, T-Mobile does not want any .kdz files available, so I designed a flash utility capable of flashing an image just like LGUP does. Originally, I was writing multiple custom scripts to do different things to the phone.
Then I decided, why not write one script and have it interpret different "flash profiles" to do just about anything you might want to do to the phone. What I arrived at seems generic enough that I am sure it could be used on any LG phone and probably even non-LG phones.
My utility does require root to be able to flash partitions, but fortunately LG has enabled bootloader unlocking on the cv1 series of devices (Aristo 2, Aristo 2 plus, K8+), so root is easily obtainable.
The source images for the stock device can be easily obtained in either of 2 ways:
1. Running a firmware backup using the NoKDZ utility itself.
or
2. Running LGUP in developer mode and selecting the DUMP option. This will provide images of any partition even w/o root.
Details on installing LGUP developer mode are here:
Install LGUP Dual Mode(Dev/User) on your Windows PC
Here are some example "flash profiles":
Code:
@ Aristo 2 plus root suite
% Flashes Magisk patched boot image and TWRP recovery all other partitions are stock Aristo 2 plus
M LG
$ Aristo 2 plus
# LM-X212TA
* cv1
< boot recovery
+ TWRP.img recovery
+ RB_M17.1_EVD_A2P.img boot
+ miscnull.img misc
+ fotanull.img fota
> modem aboot abootbak tz tzbak sbl1 sbl1bak rpm rpmbak devcfg devcfgbak cmnlib cmnlibbak cmnlib64 cmnlib64bak keymaster keymasterbak dsp sec rct apdp msadp laf lafbak recoverybak factory raw_resources raw_resourcesbak persist system OP
= This utility will flash your phone to stock except for boot and recovery
= This is firmware version X212TA-10j, Android 7.1.2, the current release as I type this (10/27/2018).
= A backup of your current boot and recovery will be saved prior to any partitions being flashed
= TWRP will then be flashed to recovery and a patched boot image will be flashed to boot.
= The boot image is patched for systemless root by Magisk. It has also been patched to
= disable encryption and verity and to remove/disable the LG root checking tool
= The firmware images included with this install package are for the LG Aristo 2 plus device
= and should only be used on an Aristo 2 plus or a variant using identical hardware such as the Aristo 2 or K8 plus.
= Note that using this utility on an Aristo 2 or K8 plus will effectively change the device into an Aristo 2 plus
= By typing a y at the next prompt, you accept full responsibility for anything that may happen to your device.
? Press Y to accept and flash or any other key to abort.
Code:
@ cv1 wipe misc and fota
% Nulls out misc and fota partitions possibly fixing TWRP boot loop
M LG
$ Any cv1 device
# Various
* cv1
+ miscnull.img misc
+ fotanull.img fota
= This utility will zero out your misc and fota partitions
= If your phone boots only into TWRP, this may remedy the problem.
= By typing a y at the next prompt, you accept full responsibility for anything that may happen to your device.
? Press Y to accept and flash or any other key to abort.
As you can see, the flash profiles are relatively short and powerful and do not require any real coding skill.
I will post more details soon, in the mean time you can see some practical application of NoKDZ here:
Restore some or all of your rooted LG Aristo 2 plus partitions to stock 10j firmware w/o LGUP

Related

[Q] What is LG G Pro 2 bootloader chain?

Does anyone know the exact bootloader chain for LG phones? There are several partition images in the firmware such as sbl1, dbi, aboot, rpm, boot, tz, persist, recovery, laf etc.
I guess the normal boot chain should be:
sbl1 -> [may or may not have others] -> aboot -> boot
And boot to recovery might be:
sbl1 -> [may or may not have others] -> aboot -> recovery
What is the intermediate stage? And the most important things that I want to know, what is the exact boot chain for download mode? While using LGFlashTool, some communication session display LAF tag. Does this imply laf.bin is the real core of download mode?
pcfree said:
Does anyone know the exact bootloader chain for LG phones? There are several partition images in the firmware such as sbl1, dbi, aboot, rpm, boot, tz, persist, recovery, laf etc.
I guess the normal boot chain should be:
sbl1 -> [may or may not have others] -> aboot -> boot
And boot to recovery might be:
sbl1 -> [may or may not have others] -> aboot -> recovery
What is the intermediate stage? And the most important things that I want to know, what is the exact boot chain for download mode? While using LGFlashTool, some communication session display LAF tag. Does this imply laf.bin is the real core of download mode?
Click to expand...
Click to collapse
I will continue monitoring thi thread for further update. Thank you

Duplicating a tablet with no custom recovery

Hello.
I have a somewhat unique situation.
I have more than one unit of identical, generic (not a standard brand) tablets. They are all rooted, so I do have root access. However, they don't have a custom recovery - there isn't one readily available (I have looked far and wide).
One of the tablets has the OS (with all the Google -and other- apps) I want to replicate on to the others (this is admittedly an oldish Kitkat OS, but while I have one of them running Lollipop successfully, I am unable to get Gapps to run with Lollipop, hence the reversion to Kitkat). I only want to replicate the OS, there are no other complications such as IMEI, etc that I need to replicate.
What do I need to accomplish this? I am comfortable flashing, rooting, etc, but I am by no stretch of imagination an Android developer, so creating a custom recovery is beyond me.
What I have tried so far:
0. The tablets are already rooted. Used Kingo to ensure root access to apps if/when necessary.
1. ADB/Fastboot flashes. This is by far most successful, although I don't have a system.img/recovery.img of the 'good' tablet. The others (including Jellybean, Kitkat and Lollipop) that I do have don't have Gapps on the OS and I am unable to install them through ADB (or native tablet-based installation) with the apks. (Google play services error).
2. dd-ing the images from the 'good' tablet to the bad ones (soft bricked, had to reflash with working images in 1. to get it back up again). (dd if=<> of=<>)
3. Taking Online-Nandroid backups, but unable to flash this image through the Nandroid Manager (and can't do it through recovery since lacking a custom recovery). I can't flash this through ADB since it isn't an system.img/recovery.img type backup.
Given this background, what I need to do is create boot.img, system.img, recovery.img, cache.img, persist.img, userdata.img from the 'good' tablet and flash these to the 'bad' ones. I have searched and searched - both on XDA and over Google at large. But I haven't found an answer to this specific issue of replicating a tablet entirely through ADB. The ones I have found (dd-method) didn't work.
Here's the Flashing batch file I've been using, that I know brings up one of these tablets. I assume I can continue to use the 'modem and bootloaders' that I currently have, although I would prefer to extract them from the 'good' tablet just to be sure.
Any help greatly appreciated.
Code:
adb root
adb wait-for-device reboot bootloader
sleep 5
:: erase all the partitions
fastboot erase modem
fastboot erase boot
fastboot erase system
fastboot -w
:: flash the modem and bootloaders
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
echo Flashed the bootloaders!
:: reboot the target
fastboot reboot
sleep 1
:: flash the linux images
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash persist persist.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
echo Done flashing the images, rebooting the target!
fastboot reboot

Can´t find partition for recovery

My Z3C has root and unlocked bootloader on Android 4.4.4. Trying to get custom recovery nothing works. When I flash recovery with fastboot, sending and writing is okay but booting into recovery only leads to stock recovery. I have tried different custom recoveries using fastboot and TWRP app but the outcome is the same. When flashing still another it failed because ”size too large”. I have tried:
1. Factory reset – no effect.
2. Using Xperia Companion to repair. When I tried to relock the bootloader it didn´t work: after 60 minutes I got ”Too many links”.
3. Flashing 23.0.A.2.93 via FlashTool. ”Preparing files for flashing. ERROR – null. Cannot open bundle. Flash operation canceled”.
4. Getting a new kernel via NUT´s Kernel Builder. ”Unpacking the uploaded kernel… Copying base packages...” After 30 minutes still nothing more.
To solve this problem I am planing to format the partition for recovery but can´t find it.
Adb shell and ls -al /dev/block/platform/msm_sdcc.1/by-name results in:
DDR p17
FOTAKernel p16
LTALabel p18
TA p1
aboot p5
alt_aboot p11
alt_db1 p10
alt_rpm p12
alt_s1sbl p9
alt_sbl1 p8
alt_tz p13
apps_logg p22
boot p14
cache p24
dbi p4
fsg p21
modemst1 p19
modemst2 p20
ramdump p15
rpm p6
s1sbl p3
sbl1 p2
system p23
tz p7
userdata p25
But where is RECOVERY hiding??? Is my idea right or can anyone come up with something better?
Hi,
stigartur said:
My Z3C has root and unlocked bootloader on Android 4.4.4...
Click to expand...
Click to collapse
Wrong place.
Try here.

[Guide] Fix Bricked due to pie kdz w/ unlocked bootloader

Not long ago i flashed stock ulm20e kdz using a guide to have twrp, i made the mistake of trying to keep the v35 bootloader which is the original we use to bootunlock ulm11g firmware. I was bricked with only being able to get to fastboot, but any attempt got me stuck with a red triangle.
SO being the first brick i had on the LG G7 ThinQ i tried every possible way to fix it, LOL even flash system/boot/vendor separately via fastboot.
In this guide i will show you how to fix this brick without octoplus. So we are gonna act like we flash the kdz and now its bootloop to fastboot due to the v35 bootloader because of flash ULM20e.
Download lg firmware extractor (Windows) - https://forum.xda-developers.com/showthread.php?t=2600575
Open lg firmware extractor and load the kdz file (In this case 20e kdz)
Find the dz file and press extract kdz
Now load the dz file that was extracted
Find abl elf (should be 2 different ones) and click the check boxes
Press extract dz
Either should be fine to use, just rename the abl.elf to abl.img
Flash abl.img to both abl_a and abl_b
Now you should be able to access download mode if you have not made any other changes to any of the other partitions. If you did you will need to re-flash the partitions you changed.

[ROM][STOCK][GM1915][FASTBOOT][11] T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)

T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY
WARNING
Proceed at your own risk. I am not responsible for any damage to your device.
Performing the instructed steps below will completely replace the existing firmware on your device, including bluetooth, WiFi and radio firmware.
Do not proceed unless you are absolutely certain your device is the T-Mobile GM1915 Model
Flashing Android 11 will remove TWRP if installed, and custom recovery will no longer be available.​I have temporarily removed instructions for flashing this firmware until I can test it further.
FIRMWARE DETAILS
Version Name: OnePlus7ProTMOOxygen_11_2104261207
Version: OnePlus7ProTMOOxygen_11.O.20_GLO_020_2104261207
Security Patch Level: 2021-04-01
OOS Version: 11.0.1.2.GM31CB
DOWNLOADS
GM1915_11.0.1.2.GM31CB.zip (2.6GB) - md5: 2bb808a07052d5b240e3c8d3dfaf95ac
If you have any problems with the downloads or process, please reply to the thread and tag me. Thanks!
weakNPCdotCom said:
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY
WARNING
Proceed at your own risk. I am not responsible for any damage to your device.
Performing the instructed steps below will completely replace the existing firmware on your device, including bluetooth, WiFi and radio firmware.
Do not proceed unless you are absolutely certain your device is the T-Mobile GM1915 Model
Flashing Android 11 will remove TWRP if installed, and custom recovery will no longer be available.​Now that Oxygen OS 11 has been pushed OTA to devices, some of us trying to revert back to stock TMO firmware may not want to revert to Android 10.
This guide will flash TMO 11.0.1.2 firmware to your device, reverting it to stock and updating it to Android 11
FIRMWARE DETAILS
Version Name: OnePlus7ProTMOOxygen_11_2104261207
Version: OnePlus7ProTMOOxygen_11.O.20_GLO_020_2104261207
Security Patch Level: 2021-04-01
OOS Version: 11.0.1.2.GM31CB
INSTRUCTIONS
If you are going to root: Have a copy of Magisk Manager v23 downloaded to your PC.
Option A: Manual Flash (Recommended)
Download GM1915_11.0.1.2.GM31CB.zip
Extract contents to your fastboot directory or a directory of your choice
For root, replace the extracted boot.img with the boot.img file in the "magisk_patched-OOS-11.0-boot" directory
Execute the following fastboot commands in order. Make sure you specify the path to the extracted images if they were not extracted to your fastboot directory
Code:
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash odm_a odm.img
fastboot flash odm_b odm.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
fastboot erase ddr
If you are converting from a non TMO ROM, this step is required. Otherwise it is optional.
Code:
fastboot erase userdata
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
Option B: Fastboot Update
*I have not tested this method*
Download GM1915_11.0.1.2.GM31CB_UPDATE.zip
Extract contents to your fastboot directory or a directory of your choice
Execute one of the following fastboot commands
Wipe Data (Required if coming from a non TMO ROM):
Code:
fastboot -w update images.zip
Keep Data:
Code:
fastboot update images.zip
OPTIONAL for root, execute the following
Code:
fastboot flash boot_a /magisk-patched-OOS-11.0-boot/boot.img
fastboot flash boot_b /magisk-patched-OOS-11.0-boot/boot.img
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
DOWNLOADS
GM1915_11.0.1.2.GM31CB.zip (2.6GB) - md5: 2bb808a07052d5b240e3c8d3dfaf95ac
GM1915_11.0.1.2.GM31CB_UPDATE.zip (2.6GB) - md5: 12d8a57c1d56e0079bf4375513c1ece6
If you have any problems with the downloads or process, please reply to the thread and tag me. Thanks!
Click to expand...
Click to collapse
Question I owned the T-Mobile variant OnePlus 7 pro which is converted to the international variant running android 11 will this procedure work for me ?
Wouldn't work on my TMobile oneplus 7 pro with bootloader unlocked I get the error sending abl_a okay writing abl_a failed (remote: flashing is not allowed for critical partitions I'm currently on converted international international latest Android 11 update
mjb337 said:
Wouldn't work on my TMobile oneplus 7 pro with bootloader unlocked I get the error sending abl_a okay writing abl_a failed (remote: flashing is not allowed for critical partitions I'm currently on converted international international latest Android 11 update
Click to expand...
Click to collapse
that's strange, I am able to flash abl fine.
I'm also having this issue.
mjb337 said:
Wouldn't work on my TMobile oneplus 7 pro with bootloader unlocked I get the error sending abl_a okay writing abl_a failed (remote: flashing is not allowed for critical partitions I'm currently on converted international international latest Android 11 update
Click to expand...
Click to collapse
And unfortunately there's no way to get TWRP on Android 11 at the moment. Not sure about how else to go about flashing
weakNPCdotCom said:
that's strange, I am able to flash abl fine.
Click to expand...
Click to collapse
Strange it wouldn't work for me my bootloader plus my device have been carrier unlocked for almost two years and I'm converted to the international variant as well I've never had a problem with flashing I guess it's not for me I'll probably convert back to TMobile just to test there update
mjb337 said:
Question I owned the T-Mobile variant OnePlus 7 pro which is converted to the international variant running android 11 will this procedure work for me ?
Click to expand...
Click to collapse
If you have converted to international for all intents and purposes you now have a GSM1917 international. You can install Derpfest and all the other "regular roms". If you do the "manual method" where you flash each partition you should be good to go.
greytheVIIth said:
I'm also having this issue.
And unfortunately there's no way to get TWRP on Android 11 at the moment. Not sure about how else to go about flashing
Click to expand...
Click to collapse
Not true anymore. If this rom uses "fbev2" which apparently most true android 11 rom's do then nebrassy released a version a couple of days back that works just fine with android 11....I linked to it in the derpfest thread and posted install instructions which should work here as well. Even if you get twrp installed you probably still don't want to install the rom's via twrp...just do manual method and then use twrp for backup's etc.
weakNPCdotCom said:
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY
WARNING
Proceed at your own risk. I am not responsible for any damage to your device.
Performing the instructed steps below will completely replace the existing firmware on your device, including bluetooth, WiFi and radio firmware.
Do not proceed unless you are absolutely certain your device is the T-Mobile GM1915 Model
Flashing Android 11 will remove TWRP if installed, and custom recovery will no longer be available.​Now that Oxygen OS 11 has been pushed OTA to devices, some of us trying to revert back to stock TMO firmware may not want to revert to Android 10.
This guide will flash TMO 11.0.1.2 firmware to your device, reverting it to stock and updating it to Android 11
FIRMWARE DETAILS
Version Name: OnePlus7ProTMOOxygen_11_2104261207
Version: OnePlus7ProTMOOxygen_11.O.20_GLO_020_2104261207
Security Patch Level: 2021-04-01
OOS Version: 11.0.1.2.GM31CB
INSTRUCTIONS
If you are going to root: Have a copy of Magisk Manager v23 downloaded to your PC.
Option A: Manual Flash (Recommended)
Download GM1915_11.0.1.2.GM31CB.zip
Extract contents to your fastboot directory or a directory of your choice
For root, replace the extracted boot.img with the boot.img file in the "magisk_patched-OOS-11.0-boot" directory
Execute the following fastboot commands in order. Make sure you specify the path to the extracted images if they were not extracted to your fastboot directory
Code:
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash odm_a odm.img
fastboot flash odm_b odm.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
fastboot erase ddr
If you are converting from a non TMO ROM, this step is required. Otherwise it is optional.
Code:
fastboot erase userdata
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
Option B: Fastboot Update
*I have not tested this method*
Download GM1915_11.0.1.2.GM31CB_UPDATE.zip
Extract contents to your fastboot directory or a directory of your choice
Execute one of the following fastboot commands
Wipe Data (Required if coming from a non TMO ROM):
Code:
fastboot -w update images.zip
Keep Data:
Code:
fastboot update images.zip
OPTIONAL for root, execute the following
Code:
fastboot flash boot_a /magisk-patched-OOS-11.0-boot/boot.img
fastboot flash boot_b /magisk-patched-OOS-11.0-boot/boot.img
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
DOWNLOADS
GM1915_11.0.1.2.GM31CB.zip (2.6GB) - md5: 2bb808a07052d5b240e3c8d3dfaf95ac
GM1915_11.0.1.2.GM31CB_UPDATE.zip (2.6GB) - md5: 12d8a57c1d56e0079bf4375513c1ece6
If you have any problems with the downloads or process, please reply to the thread and tag me. Thanks!
Click to expand...
Click to collapse
Thank you very much!!!
saved my phone <3
Hi. This rom supports dual sim?
kobebryant said:
Hi. This rom supports dual sim?
Click to expand...
Click to collapse
This is a stock firmware package. Also, it is NOT a TRWP flashable zip. I can make one of those if twrp actually works now.
famewolf said:
Not true anymore. If this rom uses "fbev2" which apparently most true android 11 rom's do then nebrassy released a version a couple of days back that works just fine with android 11....I linked to it in the derpfest thread and posted install instructions which should work here as well. Even if you get twrp installed you probably still don't want to install the rom's via twrp...just do manual method and then use twrp for backup's etc.
Click to expand...
Click to collapse
Would it be possible for you to link me to the source of that TWRP build? I would like to get it on my phone.
Also, that would allow me to build a flashable zip of this firmware.
famewolf said:
Not true anymore. If this rom uses "fbev2" which apparently most true android 11 rom's do then nebrassy released a version a couple of days back that works just fine with android 11....I linked to it in the derpfest thread and posted install instructions which should work here as well. Even if you get twrp installed you probably still don't want to install the rom's via twrp...just do manual method and then use twrp for backup's etc.
Click to expand...
Click to collapse
I found nebrassy's twrp image, but it still does not support decryption.
Also, when I booted to it, it messed up my entire system. The phone was no longer able to boot to android and when I reflashed my boot image it started crashing on boot.
I am looking into how to get this working properly.
weakNPCdotCom said:
I found nebrassy's twrp image, but it still does not support decryption.
Also, when I booted to it, it messed up my entire system. The phone was no longer able to boot to android and when I reflashed my boot image it started crashing on boot.
I am looking into how to get this working properly.
Click to expand...
Click to collapse
If you didn't find the post where he specifically says "here is the fbev2 version" then you didn't install the right one. He has SEVERAL versions of twrp.
TWRP-3.5.1-guacamole-FBEv2-Nebrassy-3.img | by Nebrassy for OnePlus 7 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
famewolf said:
If you didn't find the post where he specifically says "here is the fbev2 version" then you didn't install the right one. He has SEVERAL versions of twrp.
Click to expand...
Click to collapse
i assumed that the filename "TWRP-3.5.1-guacamole-FBEv2-Nebrassy" indicated it was FBEv2 xD
weakNPCdotCom said:
i assumed that the filename "TWRP-3.5.1-guacamole-FBEv2-Nebrassy" indicated it was FBEv2 xD
Click to expand...
Click to collapse
See previous file link since the -3 in it means you might have an older version.
*update* Found actual post: https://forum.xda-developers.com/t/...eamwin-recovery-project.4289455/post-85197387
famewolf said:
See previous file link since the -3 in it means you might have an older version.
*update* Found actual post: https://forum.xda-developers.com/t/...eamwin-recovery-project.4289455/post-85197387
Click to expand...
Click to collapse
yeah, that says "only use if you are on a custom rom and other builds dont work for you"
it ended up soft-bricking my phone
weakNPCdotCom said:
yeah, that says "only use if you are on a custom rom and other builds dont work for you"
it ended up soft-bricking my phone
Click to expand...
Click to collapse
Both Derpfest and Yaap work well with fbev2 and are Android 11 based on AOSP. I'm sorry that happened to you. In future you should use "Fastboot BOOT twrp.img" to boot recovery without replacing the existing recovery...then if it didn't work all you'd need to do if force the phone to power off via holding down vol up and power for several seconds. Still not sure how you soft bricked because I tried installing it in recovery on a non compatible rom and all it did was startup and show available storage as 0. It showed no files...once i upgraded the rom then it worked fine.
If you pay attention to with slot you are booting to and flashing to ,it will help out slot. This will always leave you a option to repair. By just switching to the opposite slot to boot to recovery. If you don't know the command then you should really learn fastboot --help. It's all the same as Python.
Hi, do you have the 11.0.1.3 update as well ? I can't install it through OTA, installation keeps failing for whatever reason...
Pluginbaby00 said:
Hi, do you have the 11.0.1.3 update as well ? I can't install it through OTA, installation keeps failing for whatever reason...
Click to expand...
Click to collapse
I have the extracted payload, but im not sure if it's actually usable on the GM1915. I can upload it if you need it, but there are several partitions you cant flash and the system image is not in the proper sparse format.

Categories

Resources