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

[Guide] Persist error fix in YUREKA / PLUS [21-Apr-2016]

PERISIST ERROR IN TWRP WHILE FLASHING ANY ZIP.....? THEN HERE IS THE GUIDE
{
"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 am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
What is the persist partition?
Persist is partition mounted at /persist. It has ext4 file system. DRM releated files, sensor reg file (sns.reg), wifi and bluetooth mac addresses are stored there.
If you experience the following issues:
1. You get "e: cannot mount /persist" in recovery
2. Can't access to internal storage.
3. Boot loop on Lollipop 5.0 and above
4. IMEI number is lost even after formating cache and fastboot flash cache.img
5. No signal even after formating cache and fastboot flash cache.img
Then your persist partition have to be fixed​
Follow instructions carefully to solve this issue
NOTE : UNLOCK your device bootloader first before doing this
1. Download this " persist file & ADB+&+Fastboot of yureka " provided by @Annabathina
2. extract them in PC
3. open ADB+&+Fastboot of yureka
4. place presist.img file which you have extracted in ADB+&+Fastboot folder
5. Hold shift key and right click on mouse and select Open command window here
6. Connect your device to pc..... and make sure that drivers are installed properly..... ( VERY VERY IMPORTANT )
a. Type : adb devices
If your device is connected you will get it in connected devices list
b. Type : adb reboot-bootloader
Your phone will restart into bootloader.
c. Type : fastboot -i 0x1ebf flash persist persist.img
7. Disconnect your device from PC and REBOOT​
ADB+&+Fastboot : link
persist : link
Useful links
ADB for pc : link
YU usb drivers : link
PdaNet drivers : link
@Annabathina............................for Guide
Ricks ............... for Presist file
YU YUREKA
YU YUREKA PLUS​
XDA:DevDB Information
[Guide] Persist error fix in YUREKA / PLUS [21-Apr-2016], Tool/Utility for the YU Yureka
Contributors
Annabathina
Version Information
Status: Stable
Stable Release Date: 2016-04-21
Created 2016-04-21
Last Updated 2016-04-23

Reserved

Reserved

I dont get a multirom function in the advanced settings menu. Is it because im using twrp 3.0.... Or is it bcoz of persist partition ?
Sent from my AO5510 using XDA-Developers mobile app

After booting into fastboot mode .. i put the commands and then it just says "waiting for device"..

Bazilbycom said:
After booting into fastboot mode .. i put the commands and then it just says "waiting for device"..
Click to expand...
Click to collapse
Have you solved it?

saurav007 said:
Have you solved it?
Click to expand...
Click to collapse
Yes! .. All you have to do is install proper drivers for your device .
Use PDAnet and Google Usb Drivers

Hi,
For me the message is : is not possible to erase this partition
Thanks a lot for your help

still same error.....what to do now..??

Bazilbycom said:
Yes! .. All you have to do is install proper drivers for your device .
Use PDAnet and Google Usb Drivers
Click to expand...
Click to collapse
Earlier i was getting error even after installing all the drivers, all i needed was to update PDAnet on phone as well & it does everything.
Thank you it worked well!

still stucking
i was suffering of problem error persist but using this method it solved the error is gone but not still my device stuck on boot i tried many custom roms stock rom formats and all but still it stuck after 2 of android logo. in twrp recovery in mount option the system, persist, firmware are uncheck .i think it means they are not mount right??? i click many time to check and reboot but still logo stuck problem please give me solution!!!!!!!
Thank You

Can I flash this zip by twrp
Sent from my YU5510 using Tapatalk

vijaysingh1996 said:
Can I flash this zip by twrp
Sent from my YU5510 using Tapatalk
Click to expand...
Click to collapse
This isn't TWRP flashable zip. You have to flash via fastboot (see OP) after extracting the img from downloaded zip file.

Failing on my Pantech Sky Vega Iron 2 IM-A910S (codename: ef63) and bootloader unlocked.
In Fedora Linux the command continues to display "waiting for device" message even though the device is detected by "fastboot devices" command, although its serial number is not displayed and ???????? is display in that place.
While in Windows 7 (64-bit), the following error message is displayed after execution of the command "fastboot -i 0x1ebf flash persist persist.img":
target reported max download size of 1610612736 bytes
sending 'persist' (4324 KB)...
OKAY [ 0.165s]
writing 'persist'...
FAILED (remote: It is not surpport in user build.)
finished. total time: 0.186s
Any one please help...

In my device it showing can't load persist
After typing last line

shekarsahani said:
In my device it showing can't load persist
After typing last line
Click to expand...
Click to collapse
Can you post CMD screenshot?
Make sure the file name is same as in CMD.

Unfortunately I can't is send cmd screenshot it is not uploading..
When I type fastboot -i 0x1ebf flash persist persist.img then it shows error cannot load 'persist.img'

Unable to update AT&T XT1789-04 using Moto Smart Assistant

Hi Everyone,
I recently purchased an AT&T branded Z2 force. I SIM unlocked the device through the AT&T unlock portal, and subsequently OTA updated the phone to 7.1.1 (Ver. NCXS26.122-59-8-6, security level Sept. 1 2017). The phone thinks it is up to date but we all know Android 8 is available for this device.
I downloaded the latest update zip from android file host (NASH_ATT_OCXS27.109-47-14_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip).
I tried installing it in recovery mode but both ADB sideload and local installation types fail.
I tried Moto Smart Assistant but it says my device is unsupported. Screenshots:
{
"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"
}
Even the flashall.bat from the Return to stock thread didn't work. The fastboot commands simply hang when trying to transfer files to the phone (which is in bootloader mode).
The phone seems to be recognized correctly in the Windows Device Manager, and I already installed the Motorola Device Manager drivers.
I am stumped. I've rooted/installed custom roms on several android devices in the past, but I've never encountered one as stubborn as this.
Any input would be greatly appreciated. Thank you

Make sure you have the utilities.zip from the 'How to Return to Stock' thread unzipped in your firmware folder, which should be unzipped too. Might seem trivial, but for all intent they're known good and have worked 100s of times. Unplug your phone, close all prompts and the smart tool. Make sure you're using a 2.0 usb port directly from the mobo, not a 3.0 port or a hub port. Typically not an issue, but can be for some. Replug your phone and reboot to bootloader, verify connection with 'fastboot devices', and if all is set then run the flashall.bat
Feel free to post screenshot of your command prompt, and you can also post the output from the command 'fastboot getvar all' if it still doesn't succeed.

The update ZIP file from Android Host is for the Moto Z2 Play (not Force)

HKSpeed said:
The update ZIP file from Android Host is for the Moto Z2 Play (not Force)
Click to expand...
Click to collapse
Incorrect. Nash refers to the Z2 Force. It just happens to share a folder with the Z2 Play. You'd need to contact the folder's owner for a separate one to be made, but that's not necessary.
More importantly, attempts to flash these on the Play will likely result in bricks.

Smart Assistant didn't recognize that file I downloaded form Android Host. Instead Smart Assistant downloaded a different file and flashed it.
Android Host file: OCXS27.109-47-14
Smart Assistant (build # on my Z2 Force): OCXS27.109-47-17 (Nov 1, 2018 patch level date)

I have one as well and I just used the flshall but that did not work, it soft bricked. So then I used LSMA restore and now I have oreo.

41rw4lk said:
Make sure you have the utilities.zip from the 'How to Return to Stock' thread unzipped in your firmware folder, which should be unzipped too. Might seem trivial, but for all intent they're known good and have worked 100s of times. Unplug your phone, close all prompts and the smart tool. Make sure you're using a 2.0 usb port directly from the mobo, not a 3.0 port or a hub port. Typically not an issue, but can be for some. Replug your phone and reboot to bootloader, verify connection with 'fastboot devices', and if all is set then run the flashall.bat
Feel free to post screenshot of your command prompt, and you can also post the output from the command 'fastboot getvar all' if it still doesn't succeed.
Click to expand...
Click to collapse
Thanks for your help. I am not allowed to post screenshots as a new user. Here's a copy-paste of my command prompt (serial redacted):
Code:
Microsoft Windows [Version 10.0.17134.523]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Temp\FlashAllUtils>fastboot devices
ZY224BCXXX fastboot
C:\Temp\FlashAllUtils>flashall.bat
C:\Temp\FlashAllUtils>fastboot oem fb_mode_set
...
FAILED (remote: unknown command)
finished. total time: 0.002s
C:\Temp\FlashAllUtils>fastboot getvar max-sparse-size
getvar:max-sparse-size FAILED (remote: unknown command)
finished. total time: 0.004s
C:\Temp\FlashAllUtils>fastboot flash partition gpt.bin
(bootloader) slot-cou: not found
(bootloader) slot-suffi: not found
(bootloader) max-downlo: not found
target didn't report max-download-size
sending 'partition' (206 KB)...
FAILED (remote: unknown command)
finished. total time: 0.003s
C:\Temp\FlashAllUtils>fastboot flash bootloader bootloader.img
(bootloader) current-slott: not found
error: Failed to identify current slot
C:\Temp\FlashAllUtils>fastboot flash modem NON-HLOS.bin
(bootloader) slot-countott: not found
(bootloader) partition-: not found
target didn't report max-download-size
sending 'modem' (97411 KB)...
"Sending Modem" hangs indefinitely. Doesn't seem like anything is actually being sent to the device.

Your firmware.zip and utilities.zip should both be unzipped into one folder, see attached. The only thing that might be causing a problem, maybe not though, is the fact that everything is coming out of a Temp folder in your root directory. Whether that is an actual temp folder or just a folder you made called temp it's not a good choice to work out of. Certain namespaces and paths are subject to environmental variables and permissions; a folder named Temp in your root directory would definitely qualify. Try renaming the folder and make sure everything is unzipped in there.

Just a quick update: it looks like there was a hardware issue with the device; no laptop I tried (of 3) could properly communicate with the phone in both adb and fastboot modes.
I received my replacement from Motorola, and it was immediately identified by Lenovo Moto Smart Assistant

Lenovo P2 stuck in "Fast boot" menu. Bricked?

I have a Lenovo P2, unrooted, on stock Android, with a 256mb micro SD card. It hasn't been unlocked/flashed/rooted in any way apart from Developer Options to allow ADB.
A couple of days ago the phone started to lag and lock up, and then rebooted into "AP Fastboot Flash Mode (Secure)" menu. The only options are Start/Barcodes/Power Off.
The Start and Power Off/On options simply reboot back to the same screen after a couple of seconds. It won't boot back into Android with any combination of volume up/down/power buttons, or offer me any other options such as recovery or clear cache etc.
I've tried rebooting with/without the SD card - it makes no difference.
The phone still appears to be recognised by ADB when I connect it to a laptop - it appears in 'fastboot devices' - but I still can't get it to exit fastboot and boot back into Android with any ADB command.
I've tried downloading Reiboot and "15 second adb" toolkits which claim to exit fastboot mode, but without success.
I'm assuming the bootloader is corrupted.
Can anyone please point me towards any possible action for fixing it, or is it bricked?
Many thanks.
{
"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"
}

The thing you are on now is the bootloader...
What you did is probably soft bricked the phone.
What did you perform with adb?

If your rom is not booting you might need to reinstall it.

Keno_I said:
The thing you are on now is the bootloader...
What you did is probably soft bricked the phone.
What did you perform with adb?
Click to expand...
Click to collapse
Here's what I've tried with ADB - the phone seems to be connected as evidenced by "fastboot devices", but I don't know what to do now. "Fastboot reboot" just brings me back to the same Fastboot screen in my original post, as does holding down vol+/vol-/power for several seconds.
I successfully unlocked/flashed a ZTE San Francisco Blade back in the day, so I don't mind trying to flash this P2 if that's the answer and you can point me towards a noob-friendly guide, please.

Reinstall the stock rom from fastboot

@Kenora_I
To try and reinstall stock, I'm following the instructions here --> https://forum.xda-developers.com/t/lenovo-p2-fastboot-files-of-every-stock-firmware.3649914/
and have downloaded all the firmware files linked on that page, ie https://www.androidfilehost.com/?w=files&flid=205781
Do I need to unlock the bootloader first?
Well, when I tried to "fastboot oem unlock", I got
fastboot oem unlock
...
FAILED (remote: oem unlock error: partition tampered
I then tried the Flash commands given, and got this error;
Fastboot flash system systemchunk0.img
target reported max download size of 536870912 bytes
sending 'system' (260121 KB)...
OKAY [ 9.303s]
writing 'system'...
FAILED (remote: Not official valid sparse image)
finished. total time: 9.379s
I got this with every set of firmware files on the download link. Am I trying to use the wrong firmware images?
Thanks for any tips and suggestions.

bigajm said:
@Kenora_I
To try and reinstall stock, I'm following the instructions here --> https://forum.xda-developers.com/t/lenovo-p2-fastboot-files-of-every-stock-firmware.3649914/
and have downloaded all the firmware files linked on that page, ie https://www.androidfilehost.com/?w=files&flid=205781
Do I need to unlock the bootloader first?
Well, when I tried to "fastboot oem unlock", I got
fastboot oem unlock
...
FAILED (remote: oem unlock error: partition tampered
I then tried the Flash commands given, and got this error;
Fastboot flash system systemchunk0.img
target reported max download size of 536870912 bytes
sending 'system' (260121 KB)...
OKAY [ 9.303s]
writing 'system'...
FAILED (remote: Not official valid sparse image)
finished. total time: 9.379s
I got this with every set of firmware files on the download link. Am I trying to use the wrong firmware images?
Thanks for any tips and suggestions.
Click to expand...
Click to collapse
You have to find and flash a valid flash image, try with the same version you were installed on

Can someone provide me with a twrp restore file? I tried to flash the stock rom but the bat file that came with it tampered with some files and I can't even boot into the stock rom

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