Develop Bugs

How to Boot Into LG G3 Fastboot Mode

How to Boot Into LG G3 Fastboot 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"
}
​-- What is Fastboot?
Fastboot allows you to re-flash partitions on your Android device. It works through PC command line and connects over a USB connection with your device.
Not every Android device manufacturer allows direct Fastboot access to end-users, and unfortunately LG is one of them. But there’s a workaround for the LG G3..
The LG G3 download mode hides the fastboot mode behind it, so if we remove the download mode (laf) from the device we get direct access to fastboot on G3. Follow the instructions below to get started:
-- STEP 1: Remove LG G3 Download mode (laf)
Important!You’ll need root access to remove (laf), so make sure you’ve rooted your LG G3 before proceeding with the steps below:​
Download ADB files:
Prepare your phone:
Enable developer options: Go to your phone’s Settings » select About phone » Scroll to the bottom and tap on “Build number” seven times to enable developer options
Enable USB Debugging: Open phone’s Settings » select Developer options » Tick the “USB debugging” checkbox (under Debugging section)
Connect your phone to PC with a USB cable and if/when a pop-up screen shows up on Phone asking you to ‘Allow USB debugging?‘ for the computer, make sure you tick the checkbox and tap OK
Navigate to the folder where you have extracted the adb and fastboot recovery files and hold SHIFT key on your keyboard and RIGHT CLICK and select “Open command window here” (as shown in the below image).
Now type/paste the following ADB commands to backup LG Download Mode (laf), so you can restore it later when necessary
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
Now run the following command to remove laf and reboot your phone
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
exit
adb reboot
Your phone will now reboot
How to Boot LG G3 Fastboot Mode:​There are a few ways you can accomplish this, I will go over just a few of them.
adb reboot bootloader:
Code:
adb reboot bootloader
Going into Download Mode:
Disconnect your phone from PC.
Power off your G3 and wait 4-5 seconds after lights go off.
Hold the Volume Up button on phone, and while holding it, connect the phone to PC using a USB cable.
I took this nfo from the original source listed below and made a few changes..
I will update with more nfo as to installing correct drivers for windows and setting up linux
at a later time. For now I only posted because I received a few request to do so.
Original Source: How to Boot Into LG G3 Fastboot Mode

Fastboot mode
fastboot

Could you explain why one would use this?
I HAVE used download mode in the past...
When i soft bricked my phone... I had to use download mode(i think?) to get the stock firmware back in....Would using fastboot(still dono why anyone would use it), take download mode out?
Thanks for upload

yanowman said:
Could you explain why one would use this?
I HAVE used download mode in the past...
When i soft bricked my phone... I had to use download mode(i think?) to get the stock firmware back in....Would using fastboot(still dono why anyone would use it), take download mode out?
Thanks for upload
Click to expand...
Click to collapse
download mode is LGE's version of updating your phone with their software.
as to fastboot gives you more control over what you want to update..
you have like 25 commands you could do in fastboot as to download mode you have no control over..
Download mode is just as it is, turn it on and wait..
as to fastboot, you turn it on type fastboot and see the list of commands.
example:
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
Another Example:
Code:
fastboot getvar version
The results will be the bootloader version, Mine showed up as 0.5 .................
One more thing: If you softbrick your phone and cant get into Recovery, fastboot is pretty much always there. you can fix any one of your partitions or all.
Some may not want it or like it, But anyone who does alot of flashing and experiments would like it as a life jacket just in case.
flashing a full kdz file can be a pain in the butt, while just flashing the partition that you need to get your phone to boot back up is much easier..
I bet you couldnt do all that in Download mode..

solution for fastbooting system.img on G3? always get errors related to file size or header.
everything else has always fastbooted without issue.
fun facts
1. fastboot is broken on D851 20B aboot.img... you can boot into fastboot but no images seem to actually flash or boot from it.
2. verizon has disabled fastboot entirely, trying to boot into it will get you a black screen and disco led.
in both of the above conditions.. if fastboot was your last hope you would be stuck.

Guys . maybe it's stupid question , but i need answer
So , we have unlocked bootloader on T-mobile g3 , we can access fastboot mode . bla bla bla
So long story short , can't we convert t-mobile g3 to international g3 (with 32GB and 3gb ram version) ? why? i just need it
i was doing same on g2 before and it was booting , but mine had problem with flash memory itself (which contains imei ,ect..) ,so i couldn't say anything why it wasn't stable , but it was booting up

autoprime said:
1. fastboot is broken on D851 20B aboot.img... you can boot into fastboot but no images seem to actually flash or boot from it.
Click to expand...
Click to collapse
Sorry for quoting you sir, but I have successfully flashed partitions using fastboot on 20B.

@Eliminater74 thanks for this guide.
Just one question: where is fastboot located? I mean in what img/partition?
aboot.img?

Is it work on a dead boot ? I can't boot to recovery or DL mode but my device shows as normal usb on pc but no display only black screen. I messed up my phone partitions. How to acces fastboot in this case ?

how can i get download mode back as i have the laf file

balakay4312 said:
how can i get download mode back as i have the laf file
Click to expand...
Click to collapse
you need a working phone to do that.
But the way was the reverse:
Code:
adb shell
su
dd if=/file/you/have/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
if your phone is not working, you need to use boarddiag

Thanks but i just flashed it in fastboot using fastboot flash laf laf.img

Eliminater74 said:
flashing a full kdz file can be a pain in the butt, while just flashing the partition that you need to get your phone to boot back up is much easier..
Click to expand...
Click to collapse
How can I flash a kdz file through fastboot? I know it's hard but I really want to try.

pelelademadera said:
you need a working phone to do that.
But the way was the reverse:
Code:
adb shell
su
dd if=/file/you/have/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
if your phone is not working, you need to use boarddiag
Click to expand...
Click to collapse
How can I use BoardDiag in order to get back download mode?

BarCouSeH said:
How can I use BoardDiag in order to get back download mode?
Click to expand...
Click to collapse
You need to get the phone in qualcomm 9008 mode... Or breaking the partition table, or forcing it... I dont know how, but if you google it... You must find the way
Enviado desde mi LG-D851 mediante Tapatalk

Impossible...
BarCouSeH said:
How can I flash a kdz file through fastboot? I know it's hard but I really want to try.
Click to expand...
Click to collapse
KDZ's are only for use on LAF mode, Bootloader use Fastboot to flash .img's to specific partitions...
2 Options: Restore the LAF mode on Fastboot to use KDZ or manualy search the Codefire Directory to Flash .img
Remember: LAF on LG's react the same as Samsung Download Mode, as well as their .KDZ/.TAR File Extentions.
Greetings!!!!:good:

pelelademadera said:
you need a working phone to do that.
But the way was the reverse:
Code:
adb shell
su
dd if=/file/you/have/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
if your phone is not working, you need to use boarddiag
Click to expand...
Click to collapse
where does the laf.img file have to be? my fastboot doesn't work for some reason and i'm trying to get back to download mode -- phone & recovery working.

stej16 said:
where does the laf.img file have to be? my fastboot doesn't work for some reason and i'm trying to get back to download mode -- phone & recovery working.
Click to expand...
Click to collapse
/dev/block/platform/msm_sdcc.1/by-name/laf
Enviado desde mi ZTE A2017G mediante Tapatalk

pelelademadera said:
/dev/block/platform/msm_sdcc.1/by-name/laf
Enviado desde mi ZTE A2017G mediante Tapatalk
Click to expand...
Click to collapse
not working. when i look in the root browser , there's no Block folder, just a file. the ADB command line to pull the laf.img sent it to my SDcard directory.. Can i command line from there? if possible , can i have that command line? sorry i am not good with commands.

stej16 said:
not working. when i look in the root browser , there's no Block folder, just a file. the ADB command line to pull the laf.img sent it to my SDcard directory.. Can i command line from there? if possible , can i have that command line? sorry i am not good with commands.
Click to expand...
Click to collapse
You must get there with root permissions, and to dump it, it must be done from terminal, or adb...
Enviado desde mi ZTE A2017G mediante Tapatalk

Unlock Bootloader on Android 5.1.1 A5CN701?

I've been trying to unlock the bootloader since the A5CN701 update. Here's how i've tried:
1. Go to developer options -> Tick OEM Unlocking
2. Use the launcher.bat from IntelAndroid-FBRL-05-16-2015.7z from this topic http://forum.xda-developers.com/nokia-n1/general/play-store-howto-t3118965
3. Use the T4 option and the tablet ends up like this (because the bootloader is locked):
{
"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"
}
4. Use fastboot and enter this code:
Code:
fastboot oem unlock
Then the cmd console and the tablet should look like this:
5. Select ''Yes: change device state'' using the UI on the N1 but here's all i've received:
The result is :''Fail: couldn't change state''
So that's pretty much about how i've tried to unlock the bootloader. I don't know why i couldn't change the device state! Is there anyone that can help me?
I posted this topic so that everyone can join and make suggestions & solutions to rooting the A5CN701 firmware!
Any help would be much appreciated!
P/s: sorry for the sloppy photos, i didn't have time to crop and edit them

it's no use,I use the same way and i get my device state-unlocked.
C：\Dociments and Settings\fldministrator>cd C:\platform-tools
C：\platform-tools>adb reboot bootloader
C：\platform-tools>fastboot oen unlock
<bootloader) Please confirm the device state action using the UI-<bootloader) Userdata erase required, this can take a while ---
OKAV [ 5.844s]
finished- total time： 5.844s
C：\platform-tools>
and then I use the old way to root the device,only end like this.
copy needed files to our deuice
target reported nax download size of 536870912 bytes
sending ^/tmp/recouery.zip^ <3477 KB> • • •
OKAV [ 0.297s]
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.516s
target reported max download size of 536870912 bytes
sending ^/tmp/recouerv. launcher^ <400 KB> • • •
OKAV [ 0.203s]
writing '/tmp/recouerv. launcher' • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
we need to stop logcat before replacing it
<bootloader> Start partitioning
OKAY [ 0.406s]
finished, total tine： 0.406s
target reported max download size of 536870912 bytes
sending ^/system/bin/logcat'<178KB
OKAY 【0.219s】
writing '/systen/bin/logcat^•••
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
issue fastboot oem ''stop.partitioning command to start cwn recouerv：
<bootloader> Stop partitioning
OKAY 【0.391s】
finished, total tine： 0.391s
sorry，can't upload img
PS:if you unlock,the device only stay in bootloader,if you want to open and normal use device,you must lock it.

乄Rain丶Man said:
it's no use,I use the same way and i get my device state-unlocked.
C：\Dociments and Settings\fldministrator>cd C:\platform-tools
C：\platform-tools>adb reboot bootloader
C：\platform-tools>fastboot oen unlock
<bootloader) Please confirm the device state action using the UI-<bootloader) Userdata erase required, this can take a while ---
OKAV [ 5.844s]
finished- total time： 5.844s
C：\platform-tools>
and then I use the old way to root the device,only end like this.
copy needed files to our deuice
target reported nax download size of 536870912 bytes
sending ^/tmp/recouery.zip^ <3477 KB> • • •
OKAV [ 0.297s]
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.516s
target reported max download size of 536870912 bytes
sending ^/tmp/recouerv. launcher^ <400 KB> • • •
OKAV [ 0.203s]
writing '/tmp/recouerv. launcher' • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
we need to stop logcat before replacing it
<bootloader> Start partitioning
OKAY [ 0.406s]
finished, total tine： 0.406s
target reported max download size of 536870912 bytes
sending ^/system/bin/logcat'<178KB
OKAY 【0.219s】
writing '/systen/bin/logcat^•••
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
issue fastboot oem ''stop.partitioning command to start cwn recouerv：
<bootloader> Stop partitioning
OKAY 【0.391s】
finished, total tine： 0.391s
sorry，can't upload img
PS:if you unlock,the device only stay in bootloader,if you want to open and normal use device,you must lock it.
Click to expand...
Click to collapse
If you have got your device unlocked, can you boot into the recovery menu where the option ''Install update from ADB'' is? I can't seem to boot into the recovery menu on the A5CN701? If we can get there, I'm sure we'll figure it out

When running "fastboot flash fastboot droidboot.img" and "fastboot flash boot boot.img" with the files from A5CN507_update.zip i get the IntelAndroid-FBRL-07-24-2015 to run TWRP or CWM.

Drivknuten said:
When running "fastboot flash fastboot droidboot.img" and "fastboot flash boot boot.img" with the files from A5CN507_update.zip i get the IntelAndroid-FBRL-07-24-2015 to run TWRP or CWM.
Click to expand...
Click to collapse
you reboot into the Temporary CWM success?

Xkernels said:
you reboot into the Temporary CWM success?
Click to expand...
Click to collapse
Yes

Drivknuten said:
Yes
Click to expand...
Click to collapse
please, you could post your image?

colorado48 said:
If you have got your device unlocked, can you boot into the recovery menu where the option ''Install update from ADB'' is? I can't seem to boot into the recovery menu on the A5CN701? If we can get there, I'm sure we'll figure it out
Click to expand...
Click to collapse
No,if you unlock device,only stay in bootloader,no matter what your choice，reboot to recovery or power off or anything else. yesterday，i see Root Dell Venue 8 7840 on Android 5.1 Lollipop, which also intel device and run android 5.1.1, it must Flashing Old Firmware and Droidboot,then use the old way to root it, just like the #4 said, but i don't have the N1's old Firmware and Droidboot, so i can't try. now,we just wait #4 upload the img and do what need to do.
---------- Post added at 04:30 AM ---------- Previous post was at 04:25 AM ----------
Drivknuten said:
When running "fastboot flash fastboot droidboot.img" and "fastboot flash boot boot.img" with the files from A5CN507_update.zip i get the IntelAndroid-FBRL-07-24-2015 to run TWRP or CWM.
Click to expand...
Click to collapse
I have the A5CN507_update.zip,could you please tell me how to flash the old droidboot.img and boot.img,
Thx~ plaese
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
p233 said:
please, you could post your image?
Click to expand...
Click to collapse
do you mean you need A5CN507_update.zip?
I have it, it's in a Chinese cloud drive，if you want it ,i can give you the url.

乄Rain丶Man said:
No,if you unlock device,only stay in bootloader,no matter what your choice，reboot to recovery or power off or anything else. yesterday，i see Root Dell Venue 8 7840 on Android 5.1 Lollipop, which also intel device and run android 5.1.1, it must Flashing Old Firmware and Droidboot,then use the old way to root it, just like the #4 said, but i don't have the N1's old Firmware and Droidboot, so i can't try. now,we just wait #4 upload the img and do what need to do.
---------- Post added at 04:30 AM ---------- Previous post was at 04:25 AM ----------
I have the A5CN507_update.zip,could you please tell me how to flash the old droidboot.img and boot.img,
Thx~ plaese
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
do you mean you need A5CN507_update.zip?
I have it, it's in a Chinese cloud drive，if you want it ,i can give you the url.
Click to expand...
Click to collapse
Here is the original old version download link
http://forum.xda-developers.com/nokia-n1/general/nokia-n1-chinese-version-5-1-1-update-t3183529 #3

p233 said:
please, you could post your image?
Click to expand...
Click to collapse
Right now my device is in a bootloop and i have too much work to get anything done with the device right now. So no pic right now.
乄Rain丶Man said:
I have the A5CN507_update.zip,could you please tell me how to flash the old droidboot.img and boot.img,
Thx~ plaese
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
Click to expand...
Click to collapse
1. extract the droidboot.img & boot.img from the A5CN507_update.zip.
2. adb reboot recovery
3. fastboot oem unlock
4. fastboot flash boot boot.img
5. fastboot flash boot boot.img
6. download "IntelAndroid-FBRL-07-24-2015" unzip, run launcher.bat type "ACCEPT" select number 4 or 5 (i have only tested those two). Then option T4 if i remember correctly.
7. Now the device should start receiving the files and start in TWRP or CWM depending on the choices you have made.

Drivknuten said:
Right now my device is in a bootloop and i have too much work to get anything done with the device right now. So no pic right now.
1. extract the droidboot.img & boot.img from the A5CN507_update.zip.
2. adb reboot recovery
3. fastboot oem unlock
4. fastboot flash boot boot.img
5. fastboot flash boot boot.img
6. download "IntelAndroid-FBRL-07-24-2015" unzip, run launcher.bat type "ACCEPT" select number 4 or 5 (i have only tested those two). Then option T4 if i remember correctly.
7. Now the device should start receiving the files and start in TWRP or CWM depending on the choices you have made.
Click to expand...
Click to collapse
2.adb reboot bootloader?
can you provide some pic?

Xkernels said:
2.adb reboot bootloader?
can you provide some pic?
Click to expand...
Click to collapse
Yes that should be adb reboot bootloader.
NO pics possible, my device is in a bootloop and i dont have the time to fix the device until the weekend.

Hi, i seem to have the same problem. ie, N1 stuck in fastboot mode. i have folowed the instructions above, ie;
- successfully unlocked it (fastboot mode reports DEVICE STATE - unlocked)
- extracted boot.img and flashed using fastoboot flash boot boot.img (successful) twice
however, when i run the FBRL script, using option T4 the same problem remains as per the earlier post, ie, it fails at the following point;
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
the script then fails in the same way for recovery.launcher and logcat.
any ideas?
my device now stays in fastboot mode, whether i try chose recovery mode, normal boot etc nothing chances and each time i power cycle it comes back to fastboot mode.
please help. thanks

pdt100 said:
Hi, i seem to have the same problem. ie, N1 stuck in fastboot mode. i have folowed the instructions above, ie;
- successfully unlocked it (fastboot mode reports DEVICE STATE - unlocked)
- extracted boot.img and flashed using fastoboot flash boot boot.img (successful) twice
however, when i run the FBRL script, using option T4 the same problem remains as per the earlier post, ie, it fails at the following point;
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
the script then fails in the same way for recovery.launcher and logcat.
any ideas?
my device now stays in fastboot mode, whether i try chose recovery mode, normal boot etc nothing chances and each time i power cycle it comes back to fastboot mode.
please help. thanks
Click to expand...
Click to collapse
Try "fastboot flash fastboot droidboot.img" with the droidboot.img from the A5CN507_update

Drivknuten said:
Try "fastboot flash fastboot droidboot.img" with the droidboot.img from the A5CN507_update
Click to expand...
Click to collapse
Hi, i was able to submit the command successfully however no change unfortunately. any other ideas? thanks

Drivknuten said:
Right now my device is in a bootloop and i have too much work to get anything done with the device right now. So no pic right now.
1. extract the droidboot.img & boot.img from the A5CN507_update.zip.
2. adb reboot recovery
3. fastboot oem unlock
4. fastboot flash boot boot.img
5. fastboot flash boot boot.img
6. download "IntelAndroid-FBRL-07-24-2015" unzip, run launcher.bat type "ACCEPT" select number 4 or 5 (i have only tested those two). Then option T4 if i remember correctly.
7. Now the device should start receiving the files and start in TWRP or CWM depending on the choices you have made.
Click to expand...
Click to collapse
Then did you root your device successfully？or did you rollback to old version？

乄Rain丶Man said:
Then did you root your device successfully？or did you rollback to old version？
Click to expand...
Click to collapse
Nah i bricked it,

the same thing to me, after i relock bootloader, it jump into a big problem: bootloop, whenever i turn on devices, it just show "android" screen

It's been a while now, can anybody confirm that a root for A5CN701 is on the way?

Drivknuten said:
Nah i bricked it,
Click to expand...
Click to collapse
Oflyt...

The System has been destroyed - only fastboot possible

Hello,
I bricked my Redmi Note 8T and I have no idea how to save my phone!
What did I do?
I unlocked my phone with XiaomiTool V2 and added Magisk, installed TWRP and trieed to add LineageOS.
So I tried to restart but the system stocked in a "boot - shutdown - boot - shutdown..."
I read in a description, that I have to delete in TWRP-mode some folders in WIPE so I deleted "System", "Data", "Cache", and maybe some other folders! I'm so stupid!
So there is only "The System has been destroyed", after around 30 seconds the system starts again and the bad massage comes again...
It is just possible to start the fastboot mode!
So I tried again to flash and boot TWRP:
sudo fastboot flash recovery twrp.img
target reported max download size of 804274176 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.617s]
writing 'recovery'...
OKAY [ 0.349s]
finished. total time: 1.967s
sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.615s]
booting...
FAILED (status read failed (No such device))
finished. total time: 37.120s
Afterwards the system says again "The System has been destroyed".
So now I don't have any idea to save my phone!
Please help me! I trust in you!
My OS on the PC is Ubuntu for your information...
Best wishes
De Blasmuskant

Blasmuskant said:
Hello,
I bricked my Redmi Note 8T and I have no idea how to save my phone!
What did I do?
I unlocked my phone with XiaomiTool V2 and added Magisk, installed TWRP and trieed to add LineageOS.
So I tried to restart but the system stocked in a "boot - shutdown - boot - shutdown..."
I read in a description, that I have to delete in TWRP-mode some folders in WIPE so I deleted "System", "Data", "Cache", and maybe some other folders! I'm so stupid!
So there is only "The System has been destroyed", after around 30 seconds the system starts again and the bad massage comes again...
It is just possible to start the fastboot mode!
So I tried again to flash and boot TWRP:
sudo fastboot flash recovery twrp.img
target reported max download size of 804274176 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.617s]
writing 'recovery'...
OKAY [ 0.349s]
finished. total time: 1.967s
sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.615s]
booting...
FAILED (status read failed (No such device))
finished. total time: 37.120s
Afterwards the system says again "The System has been destroyed".
So now I don't have any idea to save my phone!
Please help me! I trust in you!
My OS on the PC is Ubuntu for your information...
Best wishes
De Blasmuskant
Click to expand...
Click to collapse
Doesn't sound so bad. And of you had searched the forum before panic posting, you would have easily found at least 3 similar threads already started.
Not knowing what you had wiped from twrp before, leaves the best option for you is to flash the factory fastboot ROM, and then start over.
There is a thread here about fastboot ROM i beleive.

just miflash

Blasmuskant said:
Afterwards the system says again "The System has been destroyed".
So now I don't have any idea to save my phone!
Please help me! I trust in you!
My OS on the PC is Ubuntu for your information...
Best wishes
De Blasmuskant
Click to expand...
Click to collapse
in fastboot rom there must be a file vbmeta.img....if you don't want to download the fastboot rom then download vbmeta.img from here or here..
then download latest platform tools.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd/terminal in this folder path and flash vbmeta with phone in fastboot mode by this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.

Thank you for your fast answers! I tried already the search function but it seemed to me beeing different problems!
wsdyleon said:
just miflash
Click to expand...
Click to collapse
How can I do it in fastboot mode with Linux?
the_weird_aquarian said:
in fastboot rom there must be a file vbmeta.img....if you don't want to download the fastboot rom then download vbmeta.img from ...
then download ...
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd/terminal in this folder path and flash vbmeta with phone in fastboot mode by this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Click to expand...
Click to collapse
I tried it with the vbmeta.img from the fastboot Redmi Note 8 – Global Stable ROM (V11.0.9.0.PCOMIXM | MIUI 11 | Android 9.0) and the platform-tools for linux from xiaomifirmware.com.
sudo fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
< waiting for any device >
On the phone then is "Press any key to shutdown"
After trying again I got:
target didn't report max-download-size
sending 'vbmeta' (4 KB)...
But then nothing happens...
What is wrong?

Blasmuskant said:
I tried it with the vbmeta.img from the fastboot Redmi Note 8 – Global Stable ROM (V11.0.9.0.PCOMIXM | MIUI 11 | Android 9.0) and the platform-tools for linux from xiaomifirmware.com.
sudo fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
< waiting for any device >
On the phone then is "Press any key to shutdown"
After trying again I got:
target didn't report max-download-size
sending 'vbmeta' (4 KB)...
But then nothing happens...
What is wrong?
Click to expand...
Click to collapse
Was your phone connected in fastboot?

the_weird_aquarian said:
Was your phone connected in fastboot?
Click to expand...
Click to collapse
Yes, it has been connected in fastboot mode... I pressed "Power-On" and "Volume-Down" before and on screen it says FASTBOOT...

Blasmuskant said:
Yes, it has been connected in fastboot mode... I pressed "Power-On" and "Volume-Down" before and on screen it says FASTBOOT...
Click to expand...
Click to collapse
Is it working now? Why don't you try flashing the stock firmware again?

Blasmuskant said:
Yes, it has been connected in fastboot mode... I pressed "Power-On" and "Volume-Down" before and on screen it says FASTBOOT...
Click to expand...
Click to collapse
Download the latest platform tools and try again once

It works!
[email protected] said:
Is it working now? Why don't you try flashing the stock firmware again?
Click to expand...
Click to collapse
It worked, I installed the Stock recovery and then TWRP (all with fastboot) and so it was possible for me to install LineageOS!
Thank you very much for your support!

How To Guide custom rom xperia 10 iii unofficial pixel experiene android 12

first step you can unlock bootloader https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader
step 2 download treble gsi on https://github.com/ponces/treble_build_pe/releases/tag/v400.a after download extrak with winrar
step 3 download google usb driver from https://developer.android.com/studio/run/win-usb.html and android sdk from https://developer.android.com/studio/releases/platform-tools.html and vbmeta image from attach file
step 4 move file image vbmeta and pixel exp android 12 to folder platform-tools
rename file image pixel exp as system
step 5 enter cmd on folder platform-tool type cmd on up folder platform-tool
step 6 after unlock bootloader enable usb debug on phone
type command on terminal command
adb devices press enter
adb reboot fastboot press enter for mode fastbootd
follow step to flash android 12 on cmd
fastboot getvar is-userspace
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot -w
fastboot reboot
hardware isu and bugs you can setting on phh setting after booting

Just bought one of these, looking for root to run Snoopsnitch and and afwall+ as first steps. But this is excellent, if we can mooch of a pixel life could be good indeed.

[email protected] said:
first step you can unlock bootloader https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader
step 2 download treble gsi on https://github.com/ponces/treble_build_pe/releases/tag/v400.a after download extrak with winrar
step 3 download google usb driver from https://developer.android.com/studio/run/win-usb.html and android sdk from https://developer.android.com/studio/releases/platform-tools.html and vbmeta image from attach file
step 4 move file image vbmeta and pixel exp android 12 to folder platform-tools
rename file image pixel exp as system
step 5 enter cmd on folder platform-tool type cmd on up folder platform-tool
step 6 after unlock bootloader enable usb debug on phone
type command on terminal command
adb devices press enter
adb reboot fastboot press enter for mode fastbootd
follow step to flash android 12 on cmd
fastboot getvar is-userspace
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot -w
fastboot reboot
hardware isu and bugs you can setting on phh setting after booting
Click to expand...
Click to collapse
does it really work? and does fingerprint work?

How To Guide Convert ColorOS to OxygenOS (OFP & OTA | Bootloader reLock & PIN working)

Update: 18th March 2023
**** Give Up ****
I got so fedup and decided to goto HK and get my OnePlus 11, a real CPH2449 GLO. Paid and waiting to collect.
I will not be update and maintaining this post from now on.
Why give up?
Minor issue like auto brightness and things is still something i can live along with.
Some othe rmajor issue are just impossible to make this chiniese converted 1+11 to be my daily driver:
- Auto reboot randomly
- Lagging randomly, screen lag, video recording lag.
- OTA update issue, refreshing/reinstall at every update is just anonying
My advice? just get a proper non chinese version or if you own a Chinese version just stick with colorOS.
**** Flash at your own risk ****
**** Flash at your own risk ****
**** Flash at your own risk ****
*** DO NOT OTA UPDATA Your Phone After Convert. It will brick and only Official MSM Tool can save you ***
A Oneplus user since OnePlus one. Give up Oneplus and swtiched to Nothing phone since Oneplus 10. Decided to try out OnePlus 11 and ColorOS is really pain in the a**
This post tested converting from PHB110 to CPH2447 / CPH2449. I did not test CPH2451.
Model:
CPH2447 - Indian
CPH2449_EEA - EU
CPH2449_GLO - International
CPH2451 - North America
PHB110 - China
Credits：
Thanks for their feedback
[email protected]
wtywtykk
mark332
alexander宇
daxiaamu
Following is the steps to flash the OTA updates:​
Step 1:
Download all the usual tools
Download Fastboot Enhance
Android SDK
Get the firmware from this post
Firmware also availble at https://yun.daxiaamu.com/OnePlus_Roms/一加11/
CPH2449 Global A07: eea73728a1b945ea8e3ff6b628495af5.zip
ColorOS: Abandon_PHB110_V13_202301030.zip (only oplusstanvbk.img needed)
Step 2:
To boot into bootloader from Android
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
Run $ adb reboot-bootloader
After enter into fastboot (The one with Menu and shows SECURE BOOT/DEVICE STATE)
Run $ fastboot flashing unlock
Reboot back into bootloader, as in step 2 item 4.
Step 3:
Download and unzip eea73728a1b945ea8e3ff6b628495af5.zip
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is NO (Phone Screen: The one with Menu and shows SECURE BOOT/DEVICE STATE)
Flash payload.bin
Step 4:
Boot into fastbootd (Phone Screen: The one with language selection)
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is YES
Flash payload.bin
Step 5:
Download and unzip Abandon_PHB110_V13_202301030.zip
Unzip make sure radio/oplusstanvbk.img exits
Boot into fastbootd (Phone Screen: The one with language selection)
Use Fastboot Enhance or command line
fastboot flash --slot=all oplusstanvbk radio/oplusstanvbk.img
Step 6:
Follow step 6 from "flash the OFP/EDL Packages"
Following is the steps to flash the OFP/EDL Packages:​
Step 1:
Download all the usual tools
Android SDK
Get the firmware from this post
Firmware also availble at https://yun.daxiaamu.com/OnePlus_Roms/一加11/
CPH2449GDPR_11_A.06_2023010723370128.zip
Abandon_PHB110_V13_202301030.zip (only oplusstanvbk.img needed)
Step 2:
To boot into bootloader from Android
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
Run $ adb reboot-bootloader
After enter into fastboot (Phone Screen: The one with Menu and shows SECURE BOOT/DEVICE STATE)
Run $ fastboot flashing unlock
Reboot back into bootloader, as in step 2 item 4.
Step 3:
fastboot flash --slot=all modem radio/modem.img
fastboot flash --slot=all boot images/boot.img
fastboot flash vbmeta_system_a images/vbmeta_system.img
fastboot flash vbmeta_system_b images/vbmeta_system.img
fastboot flash vbmeta_a images/vbmeta.img
fastboot flash vbmeta_b images/vbmeta.img
fastboot flash vendor_boot_a images/vendor_boot.img
fastboot flash vendor_boot_b images/vendor_boot.img
fastboot flash vbmeta_vendor_a images/vbmeta_vendor.img
fastboot flash vbmeta_vendor_b images/vbmeta_vendor.img
Step 4:
Go into fastbootd (Phone Screen: The one with language selection)
fastboot reboot fastboot
fastboot flash --slot=all init_boot images/init_boot.img
fastboot flash --slot=all abl radio/abl.img
fastboot flash --slot=all aop radio/aop.img
fastboot flash --slot=all aop_config radio/aop_config.img
fastboot flash --slot=all bluetooth radio/bluetooth.img
fastboot flash --slot=all cpucp radio/cpucp.img
fastboot flash --slot=all devcfg radio/devcfg.img
fastboot flash --slot=all dsp radio/dsp.img
fastboot flash --slot=all dtbo images/dtbo.img
fastboot flash --slot=all engineering_cdt images/engineering_cdt.img
fastboot flash --slot=all featenabler radio/featenabler.img
fastboot flash --slot=all hyp radio/hyp.img
fastboot flash --slot=all imagefv radio/imagefv.img
fastboot flash --slot=all keymaster radio/keymaster.img
fastboot flash --slot=all oplus_sec radio/oplus_sec.img
# Flash the ColorOS version A.08 # fastboot flash --slot=all oplusstanvbk radio/oplusstanvbk.img
fastboot flash --slot=all qupfw radio/qupfw.img
fastboot flash --slot=all recovery images/recovery.img
fastboot flash --slot=all shrm radio/shrm.img
fastboot flash --slot=all splash images/splash.img
fastboot flash --slot=all tz radio/tz.img
fastboot flash --slot=all uefi radio/uefi.img
fastboot flash --slot=all uefisecapp radio/uefisecapp.img
fastboot flash --slot=all xbl radio/xbl.img
fastboot flash --slot=all xbl_ramdump radio/xbl_ramdump.img
fastboot flash --slot=all system images/system.img
fastboot flash --slot=all system_ext images/system_ext.img
fastboot flash --slot=all vendor images/vendor.img
fastboot flash --slot=all product images/product.img
fastboot flash --slot=all my_product images/my_product.img
fastboot flash --slot=all odm images/odm.img
fastboot flash --slot=all my_engineering images/my_engineering.img
fastboot flash --slot=all vendor_dlkm images/vendor_dlkm.img
fastboot flash --slot=all system_dlkm images/system_dlkm.img
fastboot flash --slot=all my_stock images/my_stock.img
fastboot flash --slot=all my_preload images/my_preload.img
fastboot flash --slot=all my_heytap images/my_heytap.img
fastboot flash --slot=all my_carrier images/my_carrier.img
fastboot flash --slot=all my_region images/my_region.img
fastboot flash --slot=all my_bigball images/my_bigball.img
fastboot flash --slot=all my_manifest images/my_manifest.img
Step 5:
From the fastbootd screen (with language selection),
English
Format Data
Step 6:
From daxiaamu blog post,
Go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
Go into bootloader again. follow step 2
Run $ fastboot flashing lock
Again, go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
Once passed the setup screen. Goto settings and set the pin
Additional Tips:
If your phone goes into bootloop with oneplus logo. Most likely its not brick. Just need to do a factory reset in fastboot or QLMFlasher.
As mention by mark332 use the free edition. Goto the fastboot tab and unbrick your phone.
I also paid for the commercial edition. Received username/password which can never login to the commercial editon. Commercial edition allows flash in EDL which i wanted to try.
{
"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"
}

Nice! Would it be possible to write the steps, please?
I believe you had to unlock bootloader? Have you tried locking bootloader after? Thanks.

sth_safal said:
Nice! Would it be possible to write the steps, please?
I believe you had to unlock bootloader? Have you tried locking bootloader after? Thanks.
Click to expand...
Click to collapse
i tried to, after locking the bootloader. the system not able to set the screenlock pattern

kaijern said:
i tried to, after locking the bootloader. the system not able to set the screenlock pattern
Click to expand...
Click to collapse
Ohh, that's odd. Is it just screen lock pattern or also pin locks that had issue? No luck with factory reset either I would imagine..

sth_safal said:
Ohh, that's odd. Is it just screen lock pattern or also pin locks that had issue? No luck with factory reset either I would imagine..
Click to expand...
Click to collapse
Both. I had that problem as well after unlocking the bootloader of my Chinese Onplus 11. According to a Chinese post it's a common issue and you need to keep relocking/unlocking until you are able to set the pin/pattern. Worked for me.

alexander宇 said:
Both. I had that problem as well after unlocking the bootloader of my Chinese Onplus 11. According to a Chinese post it's a common issue and you need to keep relocking/unlocking until you are able to set the pin/pattern. Worked for me.
Click to expand...
Click to collapse
Hmm.. Thanks.
So just unlock again and relock, setup phone and try out if pin works? If it doesn't repeat the post again? Would it be possible to link the Chinese post, please? Couldn't find any info online.. Did you move to Oxygen Os as well?

alexander宇 said:
Both. I had that problem as well after unlocking the bootloader of my Chinese Onplus 11. According to a Chinese post it's a common issue and you need to keep relocking/unlocking until you are able to set the pin/pattern. Worked for me.
Click to expand...
Click to collapse
I am the same.
Can I recover with relock?

sth_safal said:
Hmm.. Thanks.
So just unlock again and relock, setup phone and try out if pin works? If it doesn't repeat the post again? Would it be possible to link the Chinese post, please? Couldn't find any info online.. Did you move to Oxygen Os as well?
Click to expand...
Click to collapse
yep, that's how I resolved the problem. Don't remember where I saw it, probably a Bilibili video comment. Not yet haven't got a chance to switch, been traveling.

alexander宇 said:
yep, that's how I resolved the problem. Don't remember where I saw it, probably a Bilibili video comment. Not yet haven't got a chance to switch, been traveling.
Click to expand...
Click to collapse
Since its worling. I will wait for the international version to be avilable after Feb 7 and try to do a complete flash again. By that time is just all about from Oxygen to Oxygen nothing risky.

alexander宇 said:
yep, that's how I resolved the problem. Don't remember where I saw it, probably a Bilibili video comment. Not yet haven't got a chance to switch, been traveling.
Click to expand...
Click to collapse
I tried to relock it.
fastboot oem lock、fastboot flashing lock、fastboot oem unlock、fastboot flashing unlock
Every command gives me an error.

It seems I brick my phone.
After I typed in "fastboot flash --slot=all abl abl.elf", I got this error:
ERROR: usb_write failed with status e00002ed
fastboot: error: Could not check if partition abl has slot all
In a poor attempt to fix it, I locked BL, and now it stuck in a bootloop to FASTBOOTD
I couldn't get back to FASTBOOT with pressing physical key. Please help!
P.S. I am using mac

if you can give a step by step, or actually a video, that would actually be amazing. i fear for my phone haha

Is this version of package able to receive the OTP update of OOS?

I also bricked my phone last night, got bootloop and only was able to get into bootloader. I unbricked it by fastbootenhanced and flash the F08 payload.bin file

sunxutian said:
I also bricked my phone last night, got bootloop and only was able to get into bootloader. I unbricked it by fastbootenhanced and flash the F08 payload.bin file
Click to expand...
Click to collapse
i bricked mine as well, trying to do the same of reflashing payload.bin, but fastbootenchaned won't flash payload.bin because i can't reboot it into "fastbootd mode". any idea?

oprocks said:
i bricked mine as well, trying to do the same of reflashing payload.bin, but fastbootenchaned won't flash payload.bin because i can't reboot it into "fastbootd mode". any idea?
Click to expand...
Click to collapse
Why can't you boot into fastbood? Did you try fastboot reboot fastboot?

oprocks said:
i bricked mine as well, trying to do the same of reflashing payload.bin, but fastbootenchaned won't flash payload.bin because i can't reboot it into "fastbootd mode". any idea?
Click to expand...
Click to collapse
what you might need to do is to reinstall oneplus driver, I got unknown device when booting into fastbootd and fixed it by reinstalling driver

sunxutian said:
what you might need to do is to reinstall oneplus driver, I got unknown device when booting into fastbootd and fixed it by reinstalling driver
Click to expand...
Click to collapse
"fastboot devices" works.
this is the actual error:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.016s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
any ideas?

oprocks said:
"fastboot devices" works.
this is the actual error:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.016s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
any ideas?
Click to expand...
Click to collapse
Try fastboot -w to clean user data, also you can try flash boot.img or everything which can be flashed from bootloader

sunxutian said:
Try fastboot -w to clean user data, also you can try flash boot.img or everything which can be flashed from bootloader
Click to expand...
Click to collapse
tried that a few times, something about "userdata" not working right..
platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.063s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
any idea if there is a way to get fastboot to get userdata partition to proper state first? maybe?