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

[RECOVERY][K920] Unofficial TWRP 3.2.1 (2018/02/24)

{
"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"
}
Team Win Recovery Project
for Lenovo Vibe Z2 Pro
The only true recovery built straight from 8.1 source code.​
Key features:
Based on android-8.1 TWRP sources and LineageOS 15.1
"eng" build (no adb authorization required, ro.secure=0)
Full /data HW decryption support (PIN/password/pattern)
Full adb support - sideload, etc...
Full SELinux support
OTA updates support
MTP & USB-OTG support
F2FS support
List of partitions:
System - /system
Data - /data
Persist - /persist
Preload - /preload
Firmware - /modem
Bootloader - /aboot
Boot (kernel) - /boot
Recovery - /recovery
Splash - /splash
Misc - /misc
FS Golden - /fsg
ESF (NV Data) - /modemst1 & /modemst2
MRD Data - /mrd
How to enter recovery?
Hold the POWER button and BOTH VOLUME buttons simultaneously until you see the TWRP logo.​
Downloads
TWRP_3.2.1-0_K920.img (2018/02/24) [15.5 MB] | Google Drive Mirror
TWRP_3.1.1-0_K920.img (2017/10/15) [12.7 MB]
TWRP_3.1.0-0_K920.img (2017/03/21) [12.7 MB]
TWRP_3.0.3-0_K920.img (2017/01/24) [14.7 MB]
TWRP_3.0.2-2_K920.img (2016/11/26) [13.3 MB]
TWRP_3.0.2-1_K920.img (2016/10/08) [10.7 MB]
TWRP_3.0.2-0_K920.img (2016/09/04) [10.7 MB]​
I am not responsible for anything that happens to your phone or computer. You have to understand what you are doing.​
Sources
Manifest: https://github.com/K920/android/tree/master/twrp
Device tree: https://github.com/K920/android_device_lenovo_kingdom/tree/twrp​
Dev Info
To build with 15.1 sources requires:
export ALLOW_MISSING_DEPENDENCIES=true
repopick -t oreo-lineage-build (omnirom)
Manual removal of "vendor" under out/.../recovery/root/​
Screenshots​

FAQ:
How do I flash this TWRP .img? (with PC)
If you haven't already, install ADB+Fastboot with drivers (I recommend this installer)
Enable ADB debugging on your phone (in Settings->Developer Options)
After connecting the phone to the PC, pop up may appear, tick Always allow from this computer and click OK
Extract downloaded recovery zip and copy .img file to C:/adb
Now open cmd line (press Start+R, type "cmd", press OK) and go to C:/adb (type "cd C:/adb" and hit Enter)
Reboot into bootloader (fastboot mode) (type "adb reboot-bootloader")
Your phone should now reboot into the bootloader (Little green android logo in the middle of the screen)
Flash the recovery.img (type "fastboot flash recovery recovery.img")
Finally, reboot!
Done!
Do I have to have unlocked bootloader?
Yes!​Whenever I try to flash something, I'm getting ERROR 7. Help!
Reboot->Recovery, also make sure that your flashable zip isn't corrupted.​I have formatted encrypted /data partition, now I can't mount it.
Reboot->Recovery​Wrong password?!?
Reboot->Recovery​Does this work on CN variants?
Yes!​I can't flash my favorite ROM/.zip/we, this is not a kingdom_row device! (3.0.3+)
Yes, that's right. For the sake of using the same device tree as official Lineage OS, we're using common 'kingdom' device name. Many flashable .zips include safety mechanism to prevent them being flashed on unsupported device. If this is the case, ask the creator of your .zip to assert also on 'kingdom' device name. (e.g. by using TARGET_OTA_ASSERT_DEVICE), or edit the updater-script by yourself.​

Electry said:
reserved
Click to expand...
Click to collapse
Installation error - android\google\update-binary
CM13 (03092016)

Alexander_Gostev said:
Installation error - android\google\update-binary
CM13 (03092016)
Click to expand...
Click to collapse
It is not a flashable zip... If you want to install this TWRP, you'll have to extract the .zip and flash the .img through fastboot (fastboot flash recovery recovery.img).

Electry said:
It is not a flashable zip... If you want to install this TWRP, you'll have to extract the .zip and flash the .img through fastboot (fastboot flash recovery recovery.img).
Click to expand...
Click to collapse
Thanks, I understood and flashed through recoveri.
How do the two systems?

Updated to 3.0.2-1
/persist is now mounted RW

thx, good work

Hello
After last update of CM 14.1 via OTA (20161104) I cannot re-flash TWRP when I trying to do that via TWRP i see error http://i.imgur.com/tJ4IZXf.png. Is it a problem with permissions or with something else ? Thx

yes it's not working. you can use "fastboot flash recovery recovery.img"
Sent from my K920 using Tapatalk

Hello friends,
I try to flash it but got this:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 1610612736 bytes
sending 'recovery' (17332 KB)...
OKAY [ 0.547s]
writing 'recovery'...
FAILED (remote: invalid data)
finished. total time: 0.758s
My phone is lenovo K920
Android version 5.0.2
Anyone can help me?
Thank you.

Do first unlock bootloader
Wysłane z mojego K920 przy użyciu Tapatalka

Electry said:
Updated to 3.0.2-1
/persist is now mounted RW
Click to expand...
Click to collapse
https://mega.nz/#!YIRiFZra!a3fVWBylwMDRghq3Aa15Q3R4WrSIFFMZLvHQa_HMLn4
не рабочая ссылка!
broken links!

Alexander_Gostev said:
https://mega.nz/#!YIRiFZra!a3fVWBylwMDRghq3Aa15Q3R4WrSIFFMZLvHQa_HMLn4
?? ??????? ??????!
broken links!
Click to expand...
Click to collapse
wtf? they're not broken

Electry said:
wtf? they're not broken
Click to expand...
Click to collapse
link does not boot at all, you can move?
ссылка не грузиться вобще, можете перезалить?

Hi all,
As I got instruction few posts before I tried to copy last version of twrp via ADB but it does not work. Installed TWRP 3.0.2-1 ,
When i try to push it via ADB I see an error -------------------------------------Ä»αÑñѽѡ¿Ñ ΓѽÑΣ«¡á
List of devices attached
89355fd4 recovery
-------------------------------------ÅÑαѺáúαπº¬á ó bootloader
-------------------------------------çá»π߬ root-shell
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.458s]
booting...
OKAY [ 0.019s]
finished. total time: 0.477s
-------------------------------------Åα«Φ¿ó¬á recovery
failed to copy 'fw\twrp.img' to '/sdcard/twrp.img': Read-only file system
CANNOT LINK EXECUTABLE "/system/bin/sh": library "libNimsWrap.so" not found
-------------------------------------ÅÑαѺáúαπº¬á ó recovery
-------------------------------------çáóÑαΦÑ¡«
-------------------------------------ì᪼¿ΓÑ ½εíπε ¬½áó¿Φπ.
internal mem is Read only mode ????
ROOT for ADB , USB enabled.
As I mentioned before flashing via TWRP dow not work too.
Any suggestions?
Thx

seekator said:
Hi all,
...
As I mentioned before flashing via TWRP dow not work too.
Any suggestions?
Thx
Click to expand...
Click to collapse
no, I won't provide support for any 3rd party batch scripts (or w/e is that log from). If you can't figure out how to flash single .img, you shouldn't be messing with this stuff.
ps: I'm uploading 3.0.3-0 with F2FS support.

Electry possible to make re-initialization of the system partition? To release the space not used by the system. She's stock was designed for Roma. A cm (lineage) is much easier.
And what topics can be done f2fs?
Отправлено с моего K920 (ROW) через Tapatalk
Sorry my google English)

Electry said:
no, I won't provide support for any 3rd party batch scripts (or w/e is that log from). If you can't figure out how to flash single .img, you shouldn't be messing with this stuff.
ps: I'm uploading 3.0.3-0 with F2FS support.
Click to expand...
Click to collapse
OK Thanks . When you mentioned about unsupported script I have taken a look on it and .... Yep I used wrong zip with adb . When I tried right one I had another output . Strange, I had TWRP, ROOT but locked bootloader.
Then QPST to version 143 ,update to lollipop, bootloader , root, yours TWRP and I have last recovery, LineageOS :good:
UPDATE
Something wrong is with last TWRP 3.0.3-0. Because I started fresh installation lastest TWRP and CM I had to install everything from the scratch and ..... I was not able to install GAPPS, error 64 and something about architecture, yep I was trying to install 32 bit gapps so it was ok, when I pressed reboot it came back to TWRP, reboot to system the same, Bootloader too. When I switched back to previous version TWRP_3.0.2-2_K920.img I was able to install gapps and reboot menu was operating as it should.
On TWRP_3.0.2-2_K920.img is ok .

seekator said:
UPDATE
Something wrong is with last TWRP 3.0.3-0. Because I started fresh installation lastest TWRP and CM I had to install everything from the scratch and ..... I was not able to install GAPPS, error 64 and something about architecture, yep I was trying to install 32 bit gapps so it was ok, when I pressed reboot it came back to TWRP, reboot to system the same, Bootloader too. When I switched back to previous version TWRP_3.0.2-2_K920.img I was able to install gapps and reboot menu was operating as it should.
On TWRP_3.0.2-2_K920.img is ok .
Click to expand...
Click to collapse
That's an issue with gapps. TWRP 3.0.3-0 uses toybox instead of busybox and the 'unzip' executable/link is missing. Check my 2nd post (FAQ) there is a way around it, but you can just use 3.0.2-2 if that's easier.
EDIT: I've rebuild 3.0.3-0 with busybox included, so this shouldn't be an issue anymore.

whats new in TWRP 3.2.0-0? when the official release of twrp for our k920?

[ROM][10][UNOFFICIAL] OmniROM

{
"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"
}
Download :
GApps : https://dl.omnirom.org/tmp/def/
microG : https://dl.omnirom.org/def/
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it).
Get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
You should see a recovery like screen with a red "fastbood" message
Extract payload.bin using payload dumper (google it for tutorials)
fastboot -w (warning : this will wipe all your data)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
UPDATE
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram group for One Hyper : https://t.me/MotoOneHyper
XDA:DevDB Information
OmniROM, ROM for the Motorola One Hyper
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-02-02
Created 2020-02-02
Last Updated 2020-08-15

I unlocked my bootloader of my Motorola One Hyper and tried to install this rom.
The flashing is ok untill the flashing of the system. When I run :
fastboot flash system system.img
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
I get an error as response. Any clue ?

orimigato said:
I unlocked my bootloader of my Motorola One Hyper and tried to install this rom.
The flashing is ok untill the flashing of the system. When I run :
fastboot flash system system.img
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
I get an error as response. Any clue ?
Click to expand...
Click to collapse
I don't get why it's trying to flash on slot b, did you get an OTA since you got the phone ?

vache said:
I don't get why it's trying to flash on slot b, did you get an OTA since you got the phone ?
Click to expand...
Click to collapse
Yes I got an OTA when I got my phone today.

orimigato said:
Yes I got an OTA when I got my phone today.
Click to expand...
Click to collapse
Download stock ROM that match your current version from https://mirrors.lolinet.com/firmware/moto/def/official/
Then flash super image and try to flash ROM again.
Code:
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7

vache said:
Download stock ROM that match your current version from ...
Then flash super image and try to flash ROM again.
Code:
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
Click to expand...
Click to collapse
I have downloaded the official firmware (RETEU) which matches my device and carried out the flashing steps as you described. After that I tried to reflash your your rom and now got the following error :
fastboot flash system system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed

orimigato said:
I have downloaded the official firmware (RETEU) which matches my device and carried out the flashing steps as you described. After that I tried to reflash your your rom and now got the following error :
fastboot flash system system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Weird.
1. Are you sure that you're in fastbootd and not bootloader mode ?
2. Make sure to run the latest version of fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip

vache said:
Weird.
1. Are you sure that you're in fastbootd and not bootloader mode ?
2. Make sure to run the latest version of fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
That was the problem. When I did a fastboot reboot fastboot and retried the install. It succeeded.
Rom is now succesfully installed. First impression : its really fast compared to stock !
Thanks for your kind and quick help !!!

orimigato said:
That was the problem. When I did a fastboot reboot fastboot and retried the install. It succeeded.
Rom is now succesfully installed. First impression : its really fast compared to stock !
Thanks for your kind and quick help !!!
Click to expand...
Click to collapse
Wew cool it worked, i was running out of ideas xD

First impression after a few days of running this rom :
-Stable
-Uptime good
-Fast
-Clean
A few things that are not working/not present :
-I have 3 bluetooth devices. 2 headsets, and one car (profile audio & telephone). The 2 headsets will connect fine, but no audio is send trough the bluetooth connection. Audio is still output to the internal speaker. The car is connecting to telephone bluetooth profile but will refuse to connect to bluetooth audio profile.
-The camera does not include support for the wideangle (0,5x zoom) camera (or I cant find it...)
-The interal SIP client is not working. It says it is connected and accepting calls but no calls are received. I used the same SIP account with exactly the same settings on my other phone running Lineage with the same internal SIP client, and this one is running fine and receiving calls.
One note : I turned off all google apps including Play services and Google partner setup. However when switching these on, I got the same issues as described above.
Very happy with this ROM so far, keep up the good work !

orimigato said:
First impression after a few days of running this rom :
-Stable
-Uptime good
-Fast
-Clean
A few things that are not working/not present :
-I have 3 bluetooth devices. 2 headsets, and one car (profile audio & telephone). The 2 headsets will connect fine, but no audio is send trough the bluetooth connection. Audio is still output to the internal speaker. The car is connecting to telephone bluetooth profile but will refuse to connect to bluetooth audio profile.
-The camera does not include support for the wideangle (0,5x zoom) camera (or I cant find it...)
-The interal SIP client is not working. It says it is connected and accepting calls but no calls are received. I used the same SIP account with exactly the same settings on my other phone running Lineage with the same internal SIP client, and this one is running fine and receiving calls.
One note : I turned off all google apps including Play services and Google partner setup. However when switching these on, I got the same issues as described above.
Very happy with this ROM so far, keep up the good work !
Click to expand...
Click to collapse
Thanks for the detailed report.
1. About bluetooth, noticed that later while testing, already fixed.
2. You'd better install back Moto Camera 2 from Play Store if you want to get all stock features.
3. Never used that feature tbh, could you grab some logs ? (i'll make some tests on my side anyway)
I'll try to release the new build later today.
Edit : Created an account here : https://www.linphone.org/freesip/home
Then used https://freephonebox.net/ to call me, and it seems to work. (see attached screenshots)

SIP
Retried the SIP and now it is working. Possible was not working earlier since my old phone was still registered. Thanks for checking:good:

Any idea when you could have a build available? Thanks in advance for your efforts :good:

orimigato said:
Any idea when you could have a build available? Thanks in advance for your efforts :good:
Click to expand...
Click to collapse
Sorry, it was delayed cause i was working on dolby. Ill post it tomorrow.
Edit : New build ->https://www.androidfilehost.com/?fid=4349826312261718849 (check OP for update instruction)
Changelog :
- Fix bluetooth audio playback
- Added Dolby audio (Use QS Tile to open it for now)
- Added Google Feed to launcher
- February security patch
- Fixed tap to wake
- Synced kernel source with CAF
https://gerrit.omnirom.org/q/status:merged
https://github.com/boulzordev/device_motorola_def/commits/android-10
https://github.com/boulzordev/kernel_motorola_sm6150/commits/android-10

Bluetooth works perfectly now. Dolby is also very nice. Many thanks!

Can we install magisk and install root apps
Also what is the camera sensor used in this phone, Sony IMX686 or Samsung GW1?

htcmusic said:
Can we install magisk and install root apps
Also what is the camera sensor used in this phone, Sony IMX686 or Samsung GW1?
Click to expand...
Click to collapse
Yes what's the best root method you guys using?

young-ster said:
Yes what's the best root method you guys using?
Click to expand...
Click to collapse
I will receive this phone next week (US version) and I will use patching boot.img method

mingkee said:
I will receive this phone next week (US version) and I will use patching boot.img method
Click to expand...
Click to collapse
I'm waiting around first to see more updates, also patching boot.img I could not find the same firmware version. mine ends with a 7

young-ster said:
Yes what's the best root method you guys using?
Click to expand...
Click to collapse
young-ster said:
I'm waiting around first to see more updates, also patching boot.img I could not find the same firmware version. mine ends with a 7
Click to expand...
Click to collapse
I see it
https://mirrors.lolinet.com/firmware/moto/def/official/RETUS/

can't unlock bootloader by miflash

i was android 10 custom rom .
i used twrp to wip data .
i used mi flash to flash official android 9 rom to downgrade android 10.
but bymistake i checked flash_all_lock.bat
now the problem is
bootloader is locked + phone start when i choose language and select connection wifi or sim it reboot again
so i'm stuck now ,, no twrp or recovery work ,,
when try flash twrp from fastboot it say FAILED (remote: 'oem unlock is not allowed')
i don't have mi account and i never made one ............
there are the log from mi flash
[5:29:40 AM 2349f23c0005]:info:$fastboot -s 2349f23c0005 flash userdata C:\Users\gowan\OneDrive\Desktop\daisy_global_images_V9.6.11.0.ODLMIFF_8.1\\images\userdata.img ||
[5:29:45 AM 2349f23c0005]:err:Sending 'userdata' (181024 KB) OKAY [ 4.049s]
[5:29:45 AM 2349f23c0005]:err:Writing 'userdata' OKAY [ 1.264s]
[5:29:45 AM 2349f23c0005]:err:Finished. Total time: 5.813s
[5:29:45 AM 2349f23c0005]:info:$fastboot -s 2349f23c0005 set_active a
[5:29:45 AM 2349f23c0005]:err:Setting current slot to 'a' OKAY [ 0.020s]
[5:29:45 AM 2349f23c0005]:err:Finished. Total time: 0.023s
[5:29:45 AM 2349f23c0005]:info:$fastboot -s 2349f23c0005 oem lock 2>&1 | findstr /r "locked!" 2>&1 && fastboot -s 2349f23c0005 reboot
[5:29:46 AM 2349f23c0005]:flash done
[5:29:46 AM 2349f23c0005]rocess exit.
[5:29:46 AM 2349f23c0005]:flashSuccess True
[5:29:46 AM 2349f23c0005]:isFactory False CheckCPUID False
[5:29:46 AM 2349f23c0005]:before:flashSuccess is True set IsUpdate:True set IsDone True
[5:29:46 AM 2349f23c0005]:after:flashSuccess is True set IsUpdate:false set IsDone true
Click to expand...
Click to collapse
{
"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"
}
after this by 3 sec it reboot again

any way or go to shops ?

Are you able to enter in fastboot with keys combo?
If so you might try the following tool
Read carefully the file readme.md before starting
https://github.com/Szaki/XiaomiADBFastbootTools

You can boot twrp in fastboot mode and make a format data ( fastboot boot twrpname.img), use official twrp, try to Finish setup, enable developers options, enable usb debugging oem unlocking options, then go back to fastboot mode and type fastboot oem unlock

Os_Herdz said:
You can boot twrp in fastboot mode and make a format data ( fastboot boot twrpname.img), use official twrp, try to Finish setup, enable developers options, enable usb debugging oem unlocking options, then go back to fastboot mode and type fastboot oem unlock
Click to expand...
Click to collapse
I CAN go to fastboot but same error when flash any thing twrp
twrp is broken no recovery

srepole said:
Are you able to enter in fastboot with keys combo?
If so you might try the following tool
Read carefully the file readme.md before starting
https://github.com/Szaki/XiaomiADBFastbootTools
Click to expand...
Click to collapse
FAILED (remote: 'oem unlock is not allowed')
fastboot: error: Command failed

Maybe this helps
https://androidfilehost.com/?a=show&w=files&flid=38683
Download this Tool and Install, connect your Phone, then use on the right Side Flash factory, choose your original image and install.
Then finish the Phone Setup, activate Developer Options, activate OEM unlock and USB Debugging and retry to unlock and install twrp.

Big-Schrotty said:
Maybe this helps
https://androidfilehost.com/?a=show&w=files&flid=38683
Download this Tool and Install, connect your Phone, then use on the right Side Flash factory, choose your original image and install.
Then finish the Phone Setup, activate Developer Options, activate OEM unlock and USB Debugging and retry to unlock and install twrp.
Click to expand...
Click to collapse
it say can't modify system ..... - now way to install factory rom from fastboot
alltoolbox use fastboot

Well i think the last resource is trying to unbrick your device with EDL mode
But you'll have to physically open your phone
Once connected test-point and phone with usb cable you'll be able to see in device manager a new device
Use some metal tool like tweezers to connect the test points together
While holding test-points together connect your device to pc
After new device appeared in device manager you can release the test-points and continue
Press “refresh” in MiFlash tool
A new device should also appear
This means that everything is good and you've entered EDL mode
Then you'll have to flash phone
Here an example/tutorial
https://www.youtube.com/watch?v=BrEyAEXid_o

srepole said:
Well i think the last resource is trying to unbrick your device with EDL mode
But you'll have to physically open your phone
Once connected test-point and phone with usb cable you'll be able to see in device manager a new device
Use some metal tool like tweezers to connect the test points together
While holding test-points together connect your device to pc
After new device appeared in device manager you can release the test-points and continue
Press “refresh” in MiFlash tool
A new device should also appear
This means that everything is good and you've entered EDL mode
Then you'll have to flash phone
Here an example/tutorial
https://www.youtube.com/watch?v=BrEyAEXid_o
Click to expand...
Click to collapse
thx it worked <3

no recovery mode!!!!!!

my phone only restarting with message ΄΄this phone is unlocked will continue to boot in 5 seconds''''...But i type fast the command (fastboot reboot bootloader) so i get into download mode...now i am trying to flash twrp but nothing happening....i use cmd from this folder...the phone is stucked..cant start..i dont know what happened...i just tryed to put new twrp because i want install new rom....thanks all guys.....
{
"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"
}

'No such partition' means there exist no such partition 'recovery'!!!!!!
don't use exclamation marks!!!!!!
RTFM!!!!!!

what i must do bro

I recommend to read the instructions.
first, set your windows explorer view so you can see file name suffix. unbelievable you didn't do this yet. you can't even differ .img from .zip
this is just common instructions for devices with recovery ramdisk in boot partition. (no guarantee it is suitable for your device)
Code:
fastboot boot twrp.img
adb push twrp-installer.zip /tmp
adb shell twrp install /tmp/twrp-installer.zip

i need to join in powershell for the adb commands ?

cmd.exe is prefered.

what i do wrong...can we just make a reset the phone and start from the begine?
https://github.com/TeamWin/android_device_razer_cheryl about this ? can we make something ?

you are typing invalid commands without any sense.
the first command flashed twrp into boot partition (boot_b) successfully.
now set slot B active slot and reboot. this will bring you in TWRP recovery.
Code:
fastboot --set-active=b
fastboot reboot
once you are in TWRP restore the boot partition from adb shell. do not type commands you don't fully understand!
Code:
adb devices
adb shell
# dd if=/dev/block/bootdevice/by-name/boot_a of=/dev/block/bootdevice/by-name/boot_b
# exit
you have now repaired your boot partition.
now in TWRP proceed with installing TWRP. this will install TWRP into both slots.
Code:
adb push twrp-installer-3.6.0_9-0-cheryl.zip /tmp
adb shell twrp install /tmp/twrp-installer-3.6.0_9-0-cheryl.zip

Τhe device still does not enter into twrp and restarting all the time.this is the all problem,i cant untarstand why the factory twrp disappeared

you probably did not check current slot beforehand, maybe flashed TWRP into wrong slot.
get stock boot.img according to the current ROM and flash into both slots. if phone is working, start from scratch.

what must type to check if this happened ? btw thanks so much for your help.

according to instructions one must boot up android and from adb shell getprop ro.boot.slot_suffix - but it's too late now. you can try these commands from fastboot
Code:
fastboot getvar current-slot
fastboot getvar slot-bootable
fastboot getvar slot-successful
do you have boot.img?

C:\Users\Main User\Desktop\mobrom\platform-tools>adb shell getprop ro.boot.slot_suffix
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb.exe: no devices/emulators found
i dont have boot.img

as stated adb works only in fully booted android (with usb-debugging enabled) or in TWRP recovery.
if you don't have any boot.img congratulations to your first brick.
search in the thread if someone has shared.
TWRP for Razer Phone
https://dl.twrp.me/cheryl Razer Phone Install Instructions Read these instructions and follow them carefully. Failure to do so may result in not being able to update the device in the future and there are no factory images available. The Razer...
forum.xda-developers.com

the phone is unlocked,usb debugging enabled and cant join in TWRP mode or start normally.i can join only into fastboot mode by comand fastboot reboot-bootloader

yes, I know. that's why I said you need to unbrick first. find the proper stock boot.img

(deleted)

i need download the stock boot.img from internet or set with command ?

you need matching boot.img according to the current ROM. you can check ROM buildno from fastboot.
Code:
fastboot getvar ro.build.fingerprint
you can search for ROM on mirrors.lolinet.com and extract zip file.
edit: no Motorola device sorry
Razer Phone Factory Images - Razer Developer Portal
This page contains instructions that allow you to restore your Razer Phone's original factory firmware.
developer.razer.com
found some threads offering boot.img but links are dead
https://forum.xda-developers.com/t/guide-system-restore-using-twrp.3727777
https://forum.xda-developers.com/t/razer-phone-android-9-0-pie-cheryl-p-magisk-twrp-boot.3974325

working link for Oreo
https://forum.xda-developers.com/t/...ll-9-0-gsi-on-razer-phone-on-both-a-b.3883586
there is also LineageOS available
https://forum.xda-developers.com/t/official-lineageos-19-1-for-the-razer-phone.4436937