Database Users

[Q] Cant enter factory reset mode (devide turned off)

Got an LG G2 D802 which recently was stuck in fastboot only,no download mode not anything at all,
after many tries and errors i managed to boot to download mode and flash an apropriate version.
The thing is from that moment i cant seem to get in factory reset screen through Power Down + Power button as it used on the beginning i press the is im supposed and the phone just normaly boots,never get on factory reset or recovery,I can only enter the recovery via application from playstore called Reboot Recovery.
I can still factory reset from settings but i want to know why i cant enter with the other way and i think it a necessary function to have just in case.
How can i fix this in order to get in factory reset when the device is turned off?
How can i install twrp without autorec because this was the problem which bricked my phone?(download zip and install from current recovery?)which twrp do i need for the following device?
Any info on dorimanx kernel?
Android version 4.4.2
Build Number KOT49I.D80220h
kernel version 3.4.0
Model LG G2 D802

Did you use a kdz file or tot file?

scuzzo500 said:
Did you use a kdz file or tot file?
Click to expand...
Click to collapse
kdz file was it,should i reflash with a .tot file?
also my device was locked to tmobile uk and the got unlock via pin from the carrier,if i reflash it will need again to be unlocked?

watanabe32 said:
How can i fix this in order to get in factory reset when the device is turned off?
Click to expand...
Click to collapse
You're running 4.4.2 which is KitKat. KitKat Recovery is accessed by holding PWR + VOL DWN, then when the LG logo appears, switching to VOL DWN + VOL UP. You are trying the old method for Jellybean Recovery.
watanabe32 said:
How can I install TWRP without AutoRec?
Click to expand...
Click to collapse
BEFORE FOLLOWING THIS MAKE SURE YOU HAVE WORKING ADB DRIVERS INSTALLED AND CAN CONFIRM COMMUNICATION WITH YOUR PHONE VIA ADB COMMANDS!
You can install TWRP without autorec, which will result in keeping your KitKat bootloader. This method is also called BUMP. Follow my steps:
1. Download your KDZ from here. If you are already running Stock KitKat, no need.. just continue to step 2. I like to do everything from a clean/fresh installation that's all.
2. Root your stock KK with StumpROOT.
3. Download Bumped TWRP from here.
Extract the recovery.img file from the downloaded TWRP .rar archive.
4. Next we need your boot.img file currently on your phone. We can extract your boot.img to your sdcard by running the following command:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
Once your boot.img is on your sdcard, move it to your computer via usb or adb, your choice.
5. Download Windows BUMP Tool.
6. Bump your boot.img file with the Windows BUMP Tool. This will result in a newly created bumped.img file. Delete your original boot.img and rename bumped.img to boot.img
7. Next we need to force your phone into fastboot mode (as much as that might scare you!), we can do that by running the following command via adb/shell.
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/boot
8. BEFORE WE GO ANY FURTHER, You should have 2 files on your computer: recovery.img, and your newly renamed boot.img (bumped with the Windows BUMP Tool). Next we need to reboot the phone in order to get into fastboot mode. So, REBOOT.
9. When your device reboots it will boot into fastboot as we nullified the boot partition. We now need to connect our device via adb and run the following commands,
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
These commands require your recovery.img and boot.img to be in the same folder as your fastboot.exe file.
(See the image below for an example)
{
"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"
}
Once successfully flashing your bumped recovery and bumped boot.img, run the following command:
Code:
fastboot reboot
.
That's it! You now installed TWRP without AutoRec, and kept your KitKat bootloader.
watanabe32 said:
Which TWRP do I need?
Click to expand...
Click to collapse
ALWAYS A BUMPED TWRP RECOVERY FROM HERE.
watanabe32 said:
Any info on dorimanx kernel?
Click to expand...
Click to collapse
Dorimanx Kernel works great with a KK Bootloader, BUT YOU NEED TO HAVE A BUMPED VERSION OF THE DORIMANX KERNEL. All versions of Dorimanx above 9.1 are BUMPED.

I'll try your steps when i go home,
i've got installed the minimal adb driver which i found in my search for fixi g the fastboot problem of g2 i think this will be enough right?
for the twrp recovery cant i install it via sideload?from the recovery that it has now which is not twrp/cwm,its something else i dont know what but it has wipe cache install from cache install fro sideload

watanabe32 said:
I'll try your steps when i go home,
i've got installed the minimal adb driver which i found in my search for fixi g the fastboot problem of g2 i think this will be enough right?
Click to expand...
Click to collapse
That should be okay. As long as you can use the fastboot command and fastboot.exe is present.
watanabe32 said:
for the twrp recovery cant i install it via sideload?from the recovery that it has now which is not twrp/cwm,its something else i dont know what but it has wipe cache install from cache install fro sideload
Click to expand...
Click to collapse
I have no idea, I've never used sideload before. I'm just giving you my solution to installing TWRP without AutoRec from the facts stated in your original post. We both have the D802 model and my methods above have worked flawlessly for me multiple times after reflashing a compatible KDZ. Good luck and take it slow.

ZUK Z1 Entered an endless restart loop

Hey guys,
I was hoping you might help me as I was struggling to find an answer through google search.
After using the ZUK Z1 (Cyanogen OS 12.1 with the latest update), a few days ago the phone suddenly restarted and entered an endless restart loop
I've tried wiping the data, the cache and the user files.
I've tried applying the latest CyanogenOS zip for the Z1 either through sideload or locally from the device.
Nothing worked and I'm becoming very frustrated
I thought that maybe if I could wipe the system partition and then apply the COS zip than maybe it would work.
Does anybody have any ideas?
Thanks in advance,
Yoav.

Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-z1/development/win-zuk-z1-toolkit-0-1-alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too too.

Can you tell me what exactly did you do?
As far as I can see nothing works for me with the toolkit...
Did you use a mac or windows?
I checked that the driver is recognized (ShenQI), also tried manually using fastboot commands to unlock the bootloader and flashing images, but since my device is bricked I am unable to allow OEM unlock from inside Android
Update:
So I came across a discussion in this forum about bringing a bricked ZUK back to life
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
Done that, seem to be successful, however the phone won't turn on and the QPST Configuration tool shows that the device is stuck in download mode.
{
"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"
}
Does anyone has any idea what that means? Does that mean that it is a hardware failure?

yoavk said:
Can you tell me what exactly did you do?
As far as I can see nothing works for me with the toolkit...
Did you use a mac or windows?
I checked that the driver is recognized (ShenQI), also tried manually using fastboot commands to unlock the bootloader and flashing images, but since my device is bricked I am unable to allow OEM unlock from inside Android
Update:
So I came across a discussion in this forum about bringing a bricked ZUK back to life
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
Done that, seem to be successful, however the phone won't turn on and the QPST Configuration tool shows that the device is stuck in download mode.
Does anyone has any idea what that means? Does that mean that it is a hardware failure?
Click to expand...
Click to collapse
Ok, so first, don t panic. If you re able to acces recovery and fastboot mode, there is a strong hope. I have Windows 7 on my PC, btw.
I tried the qpst tool to flash the stock, but i couldn t. That is why i turned to the Zuk Tool Kit, which did the trick for me.
To use this tool, FIRST OF ALL YOU MUST INSTALL ADB AND FASTBOOT. you can find varius tutorials about this on te interent. I provide you some, too:
http://forum.xda-developers.com/showthread.php?t=2588979
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
It was hard for me too to understand what is going on at first, but i did some research on the topic, and i got it.
After you installed adb, you can check if it is instaled by running the command "adb version" in CMD:
You should recieve something like this if it is installed.
After you installed fastboot and adb, install the Zuk Toolkit following the steps provided in the thread of Lenvo Zuk toolkit. Download cygwin, open cygwin terminal and drag start.sh from zuk toolkit folder into terminal window, press Enter, and you will have the menu open like this:
Here, just naviagte by writing the number corresponding to the menu you want to access and hitting enter.
Under "6. Do some basic ADB and Fastboot commands.
" coomands, you will have this menu:
Do note that [fASTBOOT] marked commands will work only when your phone is in fastboot mode. To acces your fast boot mode of your phone, just select "reboot to bootloader" option from recovery menu.
Once you managed to reach this state, you can put your phone in fastboot mode, and try the command "10. [Fastboot] Reflash to stock using a manually downloaded factory image."....
IF this doesn t work, try to flash the stock rom via sideload option from recovery menu of your phone. To do this, you must chose the sideload option from recovery menu. Download the stock signed rom from here https://cyngn.com/support(NOT THE FASTBOOT ONE, JUST THE SIGNED ONE.) Rename your stock rom zip file you just downloaded "sideload" and place it on desktop. Then use THE command "4. [ADB] Sideload a zip file.
" from zuk toolkit to flash the rom. Also you must have the phone connected to pc with the USB-c cable during the whole process, of course. If it works, your phone will show the animation of flashing procees on its screen. Wait until the phone stops, chose wipe dalvik and reboot.
Use the snipping tool or PrtSc to take screen images from where you are stuck or you don t know what to do, and post them here.

Well, the QPST method seemed to have worked (as indicated by the QFIN tool).
However, it seems that the bootloop is back, when I am only able to boot into the ZUI recovery without any option of fastboot.
Edit:
Here is a pic of the Recovery (there is no option of adb sideload)
http: //s10.postimg. org/flaa11g3d/IMG_20160120_121012.jpg
Here is the fastboot
http: //s22.postimg. org/rgz4rt3a9/IMG_20160120_122555.jpg
And this is what i get when I try to use fastboot commands
C:\ WINDOWS\ system32> fastboot -i 0x2b4c oem device-info
< waiting for device >
Click to expand...
Click to collapse
All devices are discovered correctly in device manager
http: //s30.postimg. org/g8m1taywx/Capture.jpg

yoavk said:
Well, the QPST method seemed to have worked (as indicated by the QFIN tool).
However, it seems that the bootloop is back, when I am only able to boot into the ZUI recovery without any option of fastboot.
Edit:
Here is a pic of the Recovery (there is no option of adb sideload)
http: //s10.postimg. org/flaa11g3d/IMG_20160120_121012.jpg
Here is the fastboot
http: //s22.postimg. org/rgz4rt3a9/IMG_20160120_122555.jpg
And this is what i get when I try to use fastboot commands
All devices are discovered correctly in device manager
http: //s30.postimg. org/g8m1taywx/Capture.jpg
Click to expand...
Click to collapse
You have the ZUI version?? Because this does not seem to be the stock recovery of cyanogen. At least, i have the option to sideload in my recovery.
When you chose the install Update pacakge option, what options are displayed on your phone?
Also, if u installed qpst, you shoudl have in your PC a program callled QFIL, which is the flasher tool for all lenovos including ZUK. You must flash the zui stock rom using qfil. Read this thread for more info and downloads: http://forum.xda-developers.com/zuk...ui-version-t3265741/post64865607#post64865607
Also, here is a thread of a guy who had pretty much the same problem as you and managed to flash the stoc using QFIL : http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257

Extentho said:
You have the ZUI version?? Because this does not seem to be the stock recovery of cyanogen. At least, i have the option to sideload in my recovery.
Click to expand...
Click to collapse
Yeah, it was cyanogen and with QFIN I flashed stock ZUI in hopes that it will the bootloop.
I contacted coolicool, which is from where I bought the device.
I will send the device to them. I hope that they'll be able to find the problem.

yoavk said:
Yeah, it was cyanogen and with QFIN I flashed stock ZUI in hopes that it will the bootloop.
I contacted coolicool, which is from where I bought the device.
I will send the device to them. I hope that they'll be able to find the problem.
Click to expand...
Click to collapse
I think you could try un-bricking it by yourself. It is not that hard. But if those guys from coolicool will change your phone, that s ok too. Blease be advised that rooting voids warranty...soo

Lucky me I didn't have the chance to do it
I didn't even have the chance to unlock the bootloader
Does anyone here have any experience with the guys over at coolicool?

i flashed coldbird's zip for capacitive touch on the fingerprint sensor. got into an endless restart loop after that. to every option, the toolkit replies command not found.
eg: ./xposeduninstallbootloop.sh: line 128: adb: command not found
followed by whatever option was ordered, that has been done successfully but can see no change.

Try this
https://forum.xda-developers.com/zuk-z1/help/boot-loop-cyanogen-logo-t3666056

Easy bro easy, the steps that you are following are a bit confusing, aren't they?
Please tell me the current status of your phone. I might be able to help.

Device is not detected when trying to flash TWRP

okay hello people.
here is my situation.
i was about to revert back to kitkat from ED300 CM12.1, and i suddenly wipe off and formatted my internal storage.
and now ofcourse i cant boot in and what i did was trying to reinstall TWRP through fastboot and minimal adb from PC.
*i tried to flash Lenovo_A6000_TWRP-3.0.2-0_x64-L_by_SevenMaxs
*i cant go into download mode (vol+,vol-,power) button.
so i went to fastboot mode (vol-,power) button until the 'powerkey long press can reboot phone' appear , and i plug in my phone to pc and when i type in command for -adb devices, no device appear.
figure out it was okay, i go ahead and proceed with - fastboot boot recovery.img command.
then it shows
FAILED (remote: dtb not found)
and im stuck there. idk what else to do, which guide to follow to bring my phone back to life.
i have did hours of searching but nothing works. really need a magic here.
thanks guys for ur time

rizarulaltiz said:
okay hello people.
here is my situation.
i was about to revert back to kitkat from ED300 CM12.1, and i suddenly wipe off and formatted my internal storage.
and now ofcourse i cant boot in and what i did was trying to reinstall TWRP through fastboot and minimal adb from PC.
*i tried to flash Lenovo_A6000_TWRP-3.0.2-0_x64-L_by_SevenMaxs
*i cant go into download mode (vol+,vol-,power) button.
so i went to fastboot mode (vol-,power) button until the 'powerkey long press can reboot phone' appear , and i plug in my phone to pc and when i type in command for -adb devices, no device appear.
figure out it was okay, i go ahead and proceed with - fastboot boot recovery.img command.
then it shows
FAILED (remote: dtb not found)
and im stuck there. idk what else to do, which guide to follow to bring my phone back to life.
i have did hours of searching but nothing works. really need a magic here.
thanks guys for ur time
Click to expand...
Click to collapse
BTW if "fastboot devices" not showing any devices then try to properly install fastboot on computer."fastboot boot twrp.img" is command for boot the twrp without flashing.
try "fastboot flash recovery twrp.img" .
p.s:-Try to flash different recovery file.It may be corrupted.

i-AM-BoReD said:
BTW if "fastboot devices" not showing any devices then try to properly install fastboot on computer."fastboot boot twrp.img" is command for boot the twrp without flashing.
try "fastboot flash recovery twrp.img" .
p.s:-Try to flash different recovery file.It may be corrupted.
Click to expand...
Click to collapse
did it as your advice,
{
"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"
}
then i reboot the phone, still cant manage to go into recovey. it stuck there at lenovo logo.
tried with different recovery image, still the same

rizarulaltiz said:
did it as your advice,
then i reboot the phone, still cant manage to go into recovey. it stuck there at lenovo logo.
tried with different recovery image, still the same
Click to expand...
Click to collapse
As i can see that it is saying device not found but flshing is succeeded.
Editlz try to install fastboot properly.Look here

i-AM-BoReD said:
As i can see that flashing is successful.For entering to recovery r u using button combo or command?
Click to expand...
Click to collapse
i use button combo.
vol+, vol-, power button

rizarulaltiz said:
i use button combo.
vol+, vol-, power button
Click to expand...
Click to collapse
Here is the possibilities:-
1)May be fastboot is not properly installed .I gave a link in the previous post for that. "device not found" that shouldn't be appear.
2)Try vol+ +power button
3)Try if stock recovery can be flashed by fastboot.Link.if can be then let me know.
4)If not then run this command in adb
Code:
adb shell
ls -al /dev/block/platform/dw_mmc/by-name
and give a screen shot.

Did you flash kitkat ROM after this or before this fuss?
If Yes, then you need to flash TWRP for kitkat firmware.

https://drive.google.com/file/d/0B8_p5nNeW71VRFZnc3cwb2hLR28/view?usp=sharing
download the above recovery and download flashify from playstore . Flash the recovery that you downloaded from above link with flashify and reboot and in the next step you will be in the recovery

Try this
http://forum.xda-developers.com/len...lenovo-a6000-plus-stuck-booting-logo-t3437378
LP/MM TWRP 2.8.7.7 https://drive.google.com/file/d/0B3yAzE4FH2e7RkNQbUk2b0g1T0E/view?usp=drivesdk
KK TWRP 2.8.6.1 https://drive.google.com/file/d/0B3yAzE4FH2e7RU5helVWd0dBUGM/view?usp=drivesdk

i-AM-BoReD said:
Here is the possibilities:-
1)May be fastboot is not properly installed .I gave a link in the previous post for that. "device not found" that shouldn't be appear.
2)Try vol+ +power button
3)Try if stock recovery can be flashed by fastboot.Link.if can be then let me know.
4)If not then run this command in adb
Code:
adb shell
ls -al /dev/block/platform/dw_mmc/by-name
and give a screen shot.
Click to expand...
Click to collapse
1.fastboot is properly installed
2.still nothing
3. tried this and it worked. i can boot into recovery now.
now i should flash the stock rom right?

rizarulaltiz said:
1.fastboot is properly installed
2.still nothing
3. tried this and it worked. i can boot into recovery now.
now i should flash the stock rom right?
Click to expand...
Click to collapse
Then ur device is good to go.I found a recovery flashble stock rom in help or guide thread few days ago.Search it.
Also if there is recovey flashable T.W.R.P available somewhere u can flash it also.
Edit:-Here is a zip file of T.W.R.P.But version is 3.0.0.1.Don know if it can be flaahed by Stock recovery or not.Give it a try.If succeeded then no need to flash whole stock rom.You know that already.

i-AM-BoReD said:
Then ur device is good to go.I found a recovery flashble stock rom in help or guide thread few days ago.Search it.
Also if there is recovey flashable T.W.R.P available somewhere u can flash it also.
Edit:-Here is a zip file of T.W.R.P.But version is 3.0.0.1.Don know if it can be flaahed by Stock recovery or not.Give it a try.If succeeded then no need to flash whole stock rom.You know that already.
Click to expand...
Click to collapse
after i manage to flash stock recovery, i flash TWRP-2.8.6.1_A6000. then i boot into TWRP and format my internal storage, then continue flashing back ED 300's CM12.1.
and my device is back onlinee! Thanks brother for the help!!!

rizarulaltiz said:
1.fastboot is properly installed
2.still nothing
3. tried this and it worked. i can boot into recovery now.
now i should flash the stock rom right?
Click to expand...
Click to collapse
I am facing the same problem of adb device not listed , please share how it worked for you

LineageOS starts booting, but then phone goes to Qualcomm Crash Dump Mode

Hello,
I am new to phone rooting/modding, this is my first time trying to install a custom ROM (lineageOS) to my OnePlus 8 Pro.
First, I followed this guide for rooting, installing TWRP and then Magisk. The only different thing that I did was, when flashing TWRP, not usingfastboot flash recovery twrp-image-filename.img, but fastboot flash recovery_a/b twrp-image-filename.img, because I read that the former may lead to a boot loop.
Everything worked. Then I proceeded to Install LineageOS on instantnoodlep, where it said I needed to upgrade my stock OS to Oxygen 11/Android 11 first (it came with O10/A10). I did that successfully.
However, it turned out that O11/A11 had overwritten TWRP with the stock recovery. So I flashed TWRP again. This too was successful.
I decided not to install the LineageOS with the LineageOS recovery, as in the official guide, but through TWRP. I copied the LineageOS image to phone memory, booted to TWRP, selected Wipe and did a Factory Reset - Wipes Data, Cache and Dalvik (DID NOT choose Advanced Wipe, probably this was the problem?)
After the reset, I selected the LineageOS ZIP file and installed it.
After booting to system, LineageOS starts loading, but after 4-5 mins I see
QUALCOMM CrashDump Mode
--------------------------------------------------
Panic requested on external modem boot failure
mdm_force_reset
Any help for getting out of this?
It will be MUCH appreciated.

Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.

Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.

MaybeDontAsk said:
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
Click to expand...
Click to collapse
The unlock command would be:
Code:
fastboot flashing unlock

Thanks for the suggestions, I will try them when I get to my home PC, I'm at work now.
In the meantime: can someone explain to me what is the exact procedure for installing LineageOS with the latest TWRP image? More specifically, which options in "Advanced Wipe" should be checked, because in all the tutorials I found they were using old versions of TWRP which did not include the "system" option. Mine had it, so I decided not to use Advanced Wipe at all and use the default wipe options (this is also what they did in one of the tutorials). Could this be the cause for the crash dump error?
Also, I am kind of reluctant to re-lock the bootloader and go back to stock OxygenOS. I still have access to the (LineageOS) recovery mode (it overwrote TWRP). Can I try doing something from there, like maybe overwriting it with TWRP again, then wiping everything (the right way) and installing LineageOS again?

Well when ever I get a Qualcomm crash dump error I always like to go back to stock and re do everything fresh just in case something else goes wrong but if you just don't wanna go back to stock you can do this:
If you wanna overwrite lineage os recovery you can reboot into the bootloader, and just do fastboot flash recovery (drag and drop twrp image here)
So it will be something like:
Code:
fastboot flash recovery C:\Users\YourUsername\Desktop\(recovery name).img
Or if you have the twrp image in the same place at platform-tools you can do:
Code:
fastboot flash recovery (recovery.img)
Or a one time twrp boot:
Code:
fastboot boot C:\Users\YourUsername\Desktop\(recovery name).img
Or:
Code:
fastboot boot (recovery name).img
But like I said it's probably better to re-lock the bootloader to start fresh then you can unlock it again and do anything else. Good Luck.
Anyways in TWRP Navigate To:
Wipe>Advanced Wipe> Dalvik/Cache>Data>swipe to wipe
Go back to TWRP home
Advanced>Adb Sideload
Now in PC cmd do:
Code:
adb sideload (drag and drop lineage os zip here)
Hit Enter And Wait Until It Finishes Flashing
Now For The Google Apps (GAPPS):
Download Nik GAPP From:
NikGApps - Custom Google Apps Package!
NikGapps Website
nikgapps.com
Select "Download"
Then look through all packages and read what each one contains, I would go with either core or basic. But you may need another apps so just read and choose.
Once you choose, click "download now"
Navigate To Folder
Releases>NikGAPPS R if lineage is 18.1(Android 11)>Latest Version>then choose from here and download.
Back to TWRP
If the download for gapps Finished:
Navigate to:
Advanced>adb sideload
Back On CMD:
Flash Gapps:
Code:
adb sideload (drag and drop NikGAPPS zip)
once it finishes:
On TWRP go back to home menu and navigate to:
Wipe>Format Data>Type "yes">Hit Enter>Go Back To TWRP Menu>Reboot>System if it says "no rom is installed" just swipe to confirm reboot, Lineage OS Is Actually Already Flashed. Good Luck!
I know this is long but it's really not lol.

@MaybeDontAsk
Thanks a lot! I will try again via TWRP first. I don't want to re-lock the bootloader just yet, because I fear something may go wrong in the process and I may end up with a bricked phone AND a locked bootloader, and that will really be the worst scenario, from what I've read in forums.
As for the GAPPS part - I don't plan to install them. Just a LineageOS image will be fine.

Alright well hope everything goes well and yeah I also feared I may end up bricking my device with the msm download tool but I've already done it multiple times.
It has fixed a lot of issues for me wether it is that the device is booting straight into recovery or fastboot or that it's not even booting up!

Just something about TWRP: when I tried just booting to it, the phone froze on the "Fastboot Mode" splash screen and stopped there. So I had to use the flash option.
Also, about flashing: I should use
Code:
fastboot flash recovery (recovery.img)
and not
Code:
fastboot flash recovery_a (recovery.img)
fastboot flash recovery_b (recovery.img)
right?
Just double checking to make sure.

Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
{
"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 forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?

freeride01 said:
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
View attachment 5543241
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
Click to expand...
Click to collapse
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.

MaybeDontAsk said:
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
Click to expand...
Click to collapse
Alright.
I gotta find a Windows PC though, I am on Linux/Fedora.
My OxygenOS before the wipe was 11.0.10.10.IN11BA, I guess from the list I should download "OOS 11.0.4.4", because its the latest.
I'll post again when there is some progress.

MaybeDontAsk said:
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Click to expand...
Click to collapse
OK, I got my hands on a Windows 10 PC. I downloaded and extracted the MSM tool and watched the video you linked.
There is no Win7 version of the .exe file, so I guess I'll use the "normal" one anyway.

Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?

freeride01 said:
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
Click to expand...
Click to collapse
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.

MaybeDontAsk said:
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
Click to expand...
Click to collapse
Hi again,
I did the whole process again and when I did adb sideload I got this:
Code:
[[email protected] phone root]$ adb sideload lineage-18.1-20220214-nightly-instantnoodlep-signed.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Now what? There's a slide in TWRP that says "Swipe to start sideload", should I swipe it?
EDIT: Maybe Ishould use adb install as described here?

No, you need to reinstall the adb interface drivers, search up on how to do it on Linux.
Tht link you put is for installing apk directly from adb and not roms.

But adb seems to work, adb devices returns my phone ID.

It says something like "(Device ID) | Sideload?
If yes then reboot both the laptop/pc and phone.

Code:
[[email protected] phone_root]$ adb devices
List of devices attached
19356f32 recovery
(changed some digits in serial no. for privacy)

Xz2p on gsi 11-12 android

Hello everyone! The camera works on courvus 12L. and cr droid 12L but the battery is big on it. on the courvus 12L the battery is normal.
install twrp and boot into the stock firmware and then boot into twrp again. install the firmware from under twrp as a system image.
enCorvus_vS1.0-Revolt-treble_arm64_ab_vndklite-Gapps-Alpha-0000.img.rar
drive.google.com
this collected all the necessary patches for magisk
patchi.rar
drive.google.com
after installing the firmware, you can flash this recovery.this is recovery-extract the folder from the archive and flash it via fastboot by clicking on the bat file-"1lineage 18.1 recowery.cmd"
lineage 18.1 recowery.rar
drive.google.com
and to run the firmware, be sure to flash it from under recovery
Permissiver_v5.zip
drive.google.com
Sony gallery,fotoredactor sony

Kasper666666 said:
{
"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"
}
Click to expand...
Click to collapse

Hello kasper666666, that`s what I am looking for! It sounds like a fairy tail!
But.....
my knowledge about AOSP and Magisk is poor and even my trial to install magisk for my H8166 was not successfull.
I started from stock rom H8166_Customized DACHBLX_52.1.A.3.49-R6C and Magisk-v24.3 (or alternatively Magisk-v21.4).
Then I flashed system-squeak-arm64-ab-vndklite-gapps.img.
Error: "non supported Magisk-version"
Can you give any advice?
Thanks for your efforts!

I made a mistake. the camera works on firmware courvus 12 v 1.0.magisk does not work because you need to remove system / bin / phh su, and in build.prop in ro.build.fingerprint = you need to insert your own values, the camera also works on cr droid 12 but on it Big battery zhor with gapps.. https://sourceforge.net/projects/tipzbuilds/files/GSIs/CorvusROM/Alpha/20220315/ and be sure to flash it for the sensors to work https://drive.google.com/file/d/1-4cIIg8BNz1o1SlHEqamFKIprYcx9oOX/view?usp=drivesdk

der.lange said:
Can you give any advice?
Thanks for your efforts!
Click to expand...
Click to collapse
if you can’t do this, I will help you, only I will need your build.prop from vendor

Thank you for your quick response and offer!
My last trial was insatalling "magfisk-phh.apk"; but stuck with Sony-logo.

it was not necessary .... I have a ready-made file, now I will upload it to disk and send a link to the finished firmware
put the usual magisk 24.3. install twrp and boot into the stock firmware and then boot into twrp again. install the firmware from under twrp as a system image
then you can put recovery lineage and it will work
lineage-18.1-20220113-recovery-aurora.img
drive.google.com

put all the files in the topic header

sorry, but I can´t see any attachment....
bytheway: will your solution enable the use of the stock xperia camera? As far as I know Bionic does not allow the use of their cameradrivers for the further development.

all attachments open. camera tama 0.3.0 from denny trank works it is in patchi.rar

it´s a hard piece of work for me and an end not to be seen...
1. flash stock with newflasher: ok
2. flash magisk_patched boot.img: ok
3. install twrp
3.1 fastboot boot twrp-kang.img; adb push twrp-kang.img /; install recovery ramdisk; reboot into recovery (with decryption); reboot system doesn´t work, boots into recovery instead!! Flashing system-squeak.img immediately stops with error.
3.2 fastboot boot twrp-aurora.img; boots but no input possible, dead screen
So what I`m doing wrong? Is there another better twrp?

download the archive. extract the twrp-akari.img file, copy it to the memory card. you must have the official firmware, connect the phone to the computer in fastboot and in the folder that you downloaded, click first on 1vbmeta.cmd then on 2twrp.cmd and wait until the phone reboots into twrp. in twrp select advanced then install recowery ramdisk and select the file on the memory card twrp-akari.img and wait for the firmware to finish. then reboot into the system. you can go to twrp and flash the firmware from twrp in system image. flash recovery lineage 18 on fastboot...magisk flash from under recovery lineage 18
xz2p dual TWRP 3.4.0.rar
drive.google.com

sorry, where can I find vbmeta.cmd and twrp.cmd?

xz2p dual TWRP 3.4.0.rar
drive.google.com
sorry

still no end to be seen!
1. install stockrom (newflasher)
2. boot and install ramdisk recovery (twrp-akari.img)
3. flash system.img via recovery or fastboot flash system_a system.img
4. reboot system: SONY-Logo stuck
what´s wrong with me?

2. boot and install ramdisk recovery (twrp-akari.img)!system reboot required!!3. flash system.img via recovery!! no fastboot!!!!4.flash Permissiver_v5.zip..5.reboot system

That´s exactly what I have done. Permissive-zip: too large; aborted....
I think, there´s not enough room for both twrp and permissive in the ramdisk and I dont know howto increase size. If I change the sequence of the installation twrp-img is too large.
"new image larger than boot partition. Aborting"

did you flash it from twrp.? flash recovery lineage 18 and flash permissiver from it

"It′s been a hard day's night
And I′ve been working like a dog" (Beatles)
Finally successfull!
I highly appreciate your work! Thank You!!
My steps installing android 12
1. install stockrom H8166_Customized DACHBLX_52.1.A.3.49-R6C (newflasher)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
2. boot and install ramdisk recovery (twrp-akari.img)
3. reboot recovery ; reboot system ; reboot recovery again
4. push system.img /sdcard and install
5. replace ramdisk recovery with lineage-18.1-20220113-recovery-aurora.img
6. flash Permissiver_v5.zip from it
7. flash Magisk-v24.3.zip
8. reboot system
9. install camera-0.3.0-tama.zip from patchi.rar via magisk
the original SONY Xperia camera is working!!