Related
hello i have htc one
i did s-off and super cid 11111111
i tried to flash firmware - 2.24.401.1
but i have this error cannot load 'C:\adb\firmware.zip' although after i download the file i rename it to firmware.zip and move to adb file
whats the problem
thanks in advance
C:\adb>fastboot reboot-bootloader
* * *rebooting into bootloader... OKAY [ *0.037s]
finished. total time: 0.037s
C:\adb>fastboot oem rebootRUU
... INFOStart Verify: 0
OKAY [ 0.044s]
finished. total time: 0.044s
C:\adb>fastboot flash zip C:\adb\firmware.zip
error: cannot load 'C:\adb\firmware.zip'
C:\adb>fastboot flash zip C:\adb\firmware.zip
error: cannot load 'C:\adb\firmware.zip'
C:\adb>fastboot flash zip C:\adb\firmware.zip
error: cannot load 'C:\adb\firmware.zip'
You are not putting in the commands correctly it's fastboot flash firmware.zip
Sent from inside the T.A.R.D.I.S
joselv456 said:
You are not putting in the commands correctly it's fastboot flash firmware.zip
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
Absolutely correct. As long as the firmware file is in your ADB/fastboot folder, command is just fastboot flash zip firmware.zip, after rebooting to RUU mode of course. Make sure you do the firmware flash 2 times
hanks i tried this but the same problem
C:\adb>fastboot flash zip firmware.zip
error: cannot load 'firmware.zip'
C:\adb>fastboot flash zip firmware.zip
error: cannot load 'firmware.zip'
It's not 'fastboot flash zip firmware.zip' it's 'fastboot flash firmware.zip'
EddyOS said:
It's not 'fastboot flash zip firmware.zip' it's 'fastboot flash firmware.zip'
Click to expand...
Click to collapse
i got this error message
C:\adb>fastboot flash firmware.zip
unknown partition 'firmware.zip'
error: cannot determine image filename for 'firmware.zip'
Sorry, got it wrong. Start again doing this in fastboot:
1. Type: fastboot oem lock (if your device is not relocked yet)
2. Type: fastboot oem rebootRUU and wait for device to reboot
3. Type: fastboot flash zip firmware.zip and wait for process to complete
4. Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
5. Type: fastboot flash zip firmware.zip and wait for process to complete
6. Type: fastboot reboot
EddyOS said:
Sorry, got it wrong. Start again doing this in fastboot:
1. Type: fastboot oem lock (if your device is not relocked yet)
2. Type: fastboot oem rebootRUU and wait for device to reboot
3. Type: fastboot flash zip firmware.zip and wait for process to complete
4. Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
5. Type: fastboot flash zip firmware.zip and wait for process to complete
6. Type: fastboot reboot
Click to expand...
Click to collapse
i did relock
but still got the error
check upper and lowercase lettering, also cd to c:\
cd c:\adb
Click to expand...
Click to collapse
then
fastboot flash firmware.zip
Click to expand...
Click to collapse
then run the commands you want
onejay09 said:
check upper and lowercase lettering, also cd to c:\
then
then run the commands you want[/QUOTE
C:\Users\aws>cd c:/
c:\>cd adb
c:\adb>adb reboot bootloader
c:\adb>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.045s]
finished. total time: 0.045s
c:\adb>fastboot oem rebootRUU
... INFOStart Verify: 0
OKAY [ 0.050s]
finished. total time: 0.050s
c:\adb>fastboot flash zip C:\adb\firmware.zip
error: cannot load 'C:\adb\firmware.zip'
Click to expand...
Click to collapse
so the command your typing into command prompt is
c:\adb>fastboot flash zip C:\adb\firmware.zip
or is your prompt in c:\adb ?
---------- Post added at 11:14 PM ---------- Previous post was at 11:10 PM ----------
so open command prompt
type
cd ..
cd ..
cd c:\adb
fastboot flash zip firmware.zip
awshazim said:
onejay09 said:
check upper and lowercase lettering, also cd to c:\
then
then run the commands you want[/QUOTE
C:\Users\aws>cd c:/
c:\>cd adb
c:\adb>adb reboot bootloader
c:\adb>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.045s]
finished. total time: 0.045s
c:\adb>fastboot oem rebootRUU
... INFOStart Verify: 0
OKAY [ 0.050s]
finished. total time: 0.050s
c:\adb>fastboot flash zip C:\adb\firmware.zip
error: cannot load 'C:\adb\firmware.zip'
Click to expand...
Click to collapse
You keep on typing C:\adb\firmware.zip
Start command prompt from fastboot folder then type commands until you get to flashing step the command is fastboot flash firmware.zip not c:\adb>fastboot flash zip C:\adb\firmware.zip
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
onejay09 said:
so the command your typing into command prompt is
c:\adb>fastboot flash zip C:\adb\firmware.zip
or is your prompt in c:\adb ?
---------- Post added at 11:14 PM ---------- Previous post was at 11:10 PM ----------
so open command prompt
type
cd ..
cd ..
cd c:\adb
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
I tried all the ways by cd and by right click with shift to open command prompt
joselv456 said:
awshazim said:
You keep on typing C:\adb\firmware.zip
Start command prompt from fastboot folder then type commands until you get to flashing step the command is fastboot flash firmware.zip not c:\adb>fastboot flash zip C:\adb\firmware.zip
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
the command is fastboot flash zip firmware.zip and has to be done once in fastboot rebootRUU mode. It seems to me like the firmware file is corrupt.
Click to expand...
Click to collapse
joselv456 said:
awshazim said:
You keep on typing C:\adb\firmware.zip
Start command prompt from fastboot folder then type commands until you get to flashing step the command is fastboot flash firmware.zip not c:\adb>fastboot flash zip C:\adb\firmware.zip
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
i tried fastboot flash firmware.zip that earlier go back up in the forum another error occur
Click to expand...
Click to collapse
awshazim said:
joselv456 said:
i tried fastboot flash firmware.zip that earlier go back up in the forum another error occur
Click to expand...
Click to collapse
what is the size of the firmware.zip file you're trying to flash?
Click to expand...
Click to collapse
open cmd
1.
cd ..
Click to expand...
Click to collapse
2.
cd ..
Click to expand...
Click to collapse
3.
cd c:\adb
Click to expand...
Click to collapse
4. Type:
fastboot oem lock
Click to expand...
Click to collapse
(if your device is not relocked yet)
5. Type:
fastboot oem rebootRUU
Click to expand...
Click to collapse
and wait for device to reboot
6. Type:
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
7. Type:
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
and wait for process to complete
8. Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
9. Type: fastboot flash zip firmware.zip and wait for process to complete
10. Type: fastboot reboot
all quoted text should just be copied
Donjuanal said:
joselv456 said:
the command is fastboot flash zip firmware.zip and has to be done once in fastboot rebootRUU mode. It seems to me like the firmware file is corrupt.
Click to expand...
Click to collapse
can i try 2.24.401.8 because i read this::::Note: Do not skip flashing firmware 2.24.401.1 if you are on anything older than that right now. This firmware included much improved touch drivers which should be updated. Alternatively, you can download the touch panel driver img provided below and include it in your latest firmware zip archive.
Click to expand...
Click to collapse
For what step 3-4-5 i am already in cmd fastboot folder
eliminating issues, im not a mind reader and i cant see your screen... if you cant be bothered to do it correctly then why bother? do it correctly and you cant fail
hello, i have try everything but cant flash boot image, maybe someone know what i'm doing wrong.
my device:
xperia z c6603
bootloader unlocked
no root
developer options on (adb)
to get kernel.sin i use original firmware from sony emma tool than i use 7zip to extract the kernel.sin,
i also use the androxyde flashtool Tools->Bundles->FILESETdecrypt then extract from .ftf file.
kernel.elf i get with flashtool->tools->sin editor->extract data
kernel.img i get thru rename .elf to .img like here http://forum.xda-developers.com/showthread.php?t=2699858
then i use fastboot devices in cmd.exe (admin) with "fastboot flash boot kernel.elf" also "fastboot flash boot kernel.img"
HTML:
C:\platform-tools>fastboot flash boot kernel.elf
sending 'boot' (9000 KB)...
OKAY [ 0.288s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.295s
HTML:
C:\platform-tools>fastboot flash boot kernel.img
sending 'boot' (9000 KB)...
OKAY [ 0.288s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.296s
i also use flashtool for this get same error (see picture)
first i use drivers from sony and xperia companion everything is fine in device manager, i also can erase system, boot and userdata thru fastboot so the drivers are fine.
but for testing i install the driver from androxyde flashtool and done all from begin, same problem here with FAILED (remote: image is not a boot image)
i use win 8.1 64bit as administrator
for install drivers i deactivated the driver signature
can use adb thru cmd.exe (device is correctly shown)
can use fastboot for "fastboot erase boot" for example (device is correctly shown)
i unlocked the bootloader with sony unlock code, no problems
pls help, dont know what i can do else.
now i root my phone and try to extract the boot.img from my android phone (see on picture).
the boot.img was successfully copy to my sdcard, then i reboot into fastboot and try to flash.
no success same error again: FAILED (remote: image is not a boot image)
slowly i get desperate
i try to flash newest twrp,
fastboot flash boot twrp.img
this works without problems, so driver and usb cable is fine.
Do you got a solution?
Michael
Well I have tried to install MIUI ROM 6.5.26 after not processing updates for months (since november).
So I downloaded latest ROM and put it to the top of the partitions and then I wiped everything and that's where i might have done a mistake: I wiped internal storage (inside TWRP 2.8.7 i found there http://forum.xda-developers.com/mi-...timizing-leo-miui-advanced-tweaks-to-t3286972) then I might have might done a second mistake: I have done the command fastboot 'flash boot boot.img' as I read on an old HTC forum.
Then I pushed the latest ROM to the phone (as it was not there after the wipes) and when I tried installing it, it gave E: unable to mount 'cache' .
Now it seems i cannot enter TWRP, only Fastboot or I am stuck with MI logo.
I just want to install latest ROM, as I have done Titanium Backup before all the mess.
I don't know where i should start.
I am on mac so cannot use Mi Flash
EMJI79 said:
Well I have tried to install MIUI ROM 6.5.26 after not processing updates for months (since november).
So I downloaded latest ROM and put it to the top of the partitions and then I wiped everything and that's where i might have done a mistake: I wiped internal storage (inside TWRP 2.8.7 i found there http://forum.xda-developers.com/mi-...timizing-leo-miui-advanced-tweaks-to-t3286972) then I might have might done a second mistake: I have done the command fastboot 'flash boot boot.img' as I read on an old HTC forum.
Then I pushed the latest ROM to the phone (as it was not there after the wipes) and when I tried installing it, it gave E: unable to mount 'cache' .
Now it seems i cannot enter TWRP, only Fastboot or I am stuck with MI logo.
I just want to install latest ROM, as I have done Titanium Backup before all the mess.
I don't know where i should start.
Click to expand...
Click to collapse
you wiped internal sd so you have nothing the only way to solve is
Download the fastboot ROM https://www.dropbox.com/s/dg198q49dctzfgr/leo_images_5.11.26_20151104.0000.4_5.1_cn.tar.gz?dl=0 (recomend this others from this year locked bootloader)
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
10. Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash tz tz.mbn
C:\Fastboot>fastboot flash dbi sdi.mbn
C:\Fastboot>fastboot flash sbl1 sbl1.mbn
C:\Fastboot>fastboot flash rpm rpm.mbn
C:\Fastboot>fastboot flash aboot emmc_appsboot.mbn
C:\Fastboot>fastboot erase boot
C:\Fastboot>fastboot flash misc misc.img
C:\Fastboot>fastboot flash modem NON-HLOS.bin
C:\Fastboot>fastboot flash system system.img
C:\Fastboot>fastboot flash cache cache.img
C:\Fastboot>fastboot flash userdata userdata.img
C:\Fastboot>fastboot flash recovery recovery.img
C:\Fastboot>fastboot flash boot boot.img
C:\Fastboot>fastboot reboot
Now you're all set and should be able to boot normally.
after you can install recovery
to install recoverytwrp https://www.dropbox.com/s/hkuwc6d881im2hy/TWRP_leo.zip?dl=0
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash recovery TWRP.img
C:\Fastboot>fastboot reboot
done now you can install latest rom from xiaomi.eu Does not locked bootloader
helderfp said:
you wiped internal sd so you have nothing the only way to solve is
Download the fastboot ROM https://www.dropbox.com/s/dg198q49dctzfgr/leo_images_5.11.26_20151104.0000.4_5.1_cn.tar.gz?dl=0 (recomend this others from this year locked bootloader)
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
10. Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash tz tz.mbn
C:\Fastboot>fastboot flash dbi sdi.mbn
C:\Fastboot>fastboot flash sbl1 sbl1.mbn
C:\Fastboot>fastboot flash rpm rpm.mbn
C:\Fastboot>fastboot flash aboot emmc_appsboot.mbn
C:\Fastboot>fastboot erase boot
C:\Fastboot>fastboot flash misc misc.img
C:\Fastboot>fastboot flash modem NON-HLOS.bin
C:\Fastboot>fastboot flash system system.img
C:\Fastboot>fastboot flash cache cache.img
C:\Fastboot>fastboot flash userdata userdata.img
C:\Fastboot>fastboot flash recovery recovery.img
C:\Fastboot>fastboot flash boot boot.img
C:\Fastboot>fastboot reboot
Now you're all set and should be able to boot normally.
after you can install recovery
to install recoverytwrp https://www.dropbox.com/s/hkuwc6d881im2hy/TWRP_leo.zip?dl=0
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash recovery TWRP.img
C:\Fastboot>fastboot reboot
done now you can install latest rom from xiaomi.eu Does not locked bootloader
Click to expand...
Click to collapse
OK thanks a lot. :good:
I will try that tonight or tomorrow (already downloading from your dropbox, thanks again).
I'll let you know.
Only i dont understand: (recomend this others from this year locked boot loader) ?
EMJI79 said:
Only i dont understand: (recomend this others from this year locked boot loader) ?
Click to expand...
Click to collapse
It broke halfway, so I am trying again. Thank you for your patience.
Well, I downloaded it entirely and tried "fastboot the tz", then I get -> "device is locked. Cannot flash images"...
So I guess I locked my bootloader already, somehow... :crying:
EMJI79 said:
Well, I downloaded it entirely and tried "fastboot the tz", then I get -> "device is locked. Cannot flash images"...
So I guess I locked my bootloader already, somehow... :crying:
Click to expand...
Click to collapse
ok
so you have to do this
Download Xiaomi MiFlash Tool and install it to your PC https://www.dropbox.com/s/1qntzckybxg3rr4/MiSetup3.2.1.3111_2717.zip?dl=0
Download Qualcomm Driver 32-bit https://www.dropbox.com/s/klnn6h9z7038u80/QDLoader HS-USB Driver_32bit_Setup.zip?dl=0 OR Qualcomm Driver 64-bit https://www.dropbox.com/s/gvizx1ja1vmihox/QDLoader HS-USB Driver_64bit_Setup.zip?dl=0 install it to your PC
Enter your phone in fastboot mode
in command promt wrtite:
cmd
cd C:\fastboot
fastboot devices
fastboot oem edl
After the last command Your Note pro detected as a new device
Launch MiFlash and flash Note pro not locked ROM if you get one error at the midle (not at the beginnig) of flashing dont worry, you have unlocked bootloader, and you can folow the previous steps you already tried
The latest roms from xiaomi (since January 2016) lockes bootloader that is why i recomend that on the link.
Thanks
But I am on Mac, no MiFlash, only ADB, fastboot...
EMJI79 said:
Thanks
But I am on Mac, no MiFlash, only ADB, fastboot...
Click to expand...
Click to collapse
to work on mac
Download the fastboot ROM for your Mi phone and place it on your desktop. Double-click on it and Archive Utility will extract the file on the desktop, so you'll get a folder,
now go to terminal an type
cd C:\fastboot
fastboot devices
fastboot oem edl
In order to use the fastboot scripts, you should go to the folder. For that purpose, execute the following command (the folder name may be different in your case, the example below is for cancro):
cd ~/Desktop/cancro_global_images_V7.0.5.0.KXDMICI_20151016.0000.3_4.4_global
Copy the Code
Quick tip: you don't need to write the whole folder name, just type cd ~/Desktop/cancro, then press the Tab key and Terminal will append the folder name automatically.
Once inside, you need to make the scripts (all the files with .sh extension) executable. Execute the following command:
chmod +x ./*.sh
Now, the scripts are ready to use. In order to start the process, issue one of the following commands:
./flash_all.sh
or
./flash_all_except_storage.sh
or
./flash_all_except_data_storage.sh
When you start any of the scripts, you'll see the fastboot messages, flowing through the Terminal window. Once the script has done its work, the phone will restart itself automatically.
When I change directory for the fastboot ROM directory, the fastboot screen on my phone disappears. I have done the steps after that but i see no message on the terminal or the phone screen. My phone screen is black.
Edit: In fact the fastboot screen on my phone disappears when I type fastboot oem edl in my terminal although i get the message OKAY in my terminal.
EMJI79 said:
When I change directory for the fastboot ROM directory, the fastboot screen on my phone disappears. I have done the steps after that but i see no message on the terminal or the phone screen. My phone screen is black.
Edit: In fact the fastboot screen on my phone disappears when I type fastboot oem edl in my terminal although i get the message OKAY in my terminal.
Click to expand...
Click to collapse
so don't change the directory put the rom in the fastboot folder and do the next step
if you are not able to flash in your mac try in another pc (windows)
Don't you think I just locked my bootloader and I need to do the apply stuff for getting my phone unlocked?
EMJI79 said:
Don't you think I just locked my bootloader and I need to do the apply stuff for getting my phone unlocked?
Click to expand...
Click to collapse
you dont need
just try
put rom in fastboot folder and
cd C:\fastboot
fastboot devices
fastboot oem edl
chmod +x ./*.sh
./flash_all.sh
to unlock bootloader the previous steps (not this) work fine on windows
http://en.miui.com/thread-237832-1-1.html
https://xiaomi.eu/community/threads/mi-note-pro-complete-beginners-guide.30817/
every time I type:
fastboot oem edl
the screen of the smartphone goes off
Maybe I will buy Windows to make it work in VM...
Only can you interpretate why fastboot oem edl makes the screen go off?
EMJI79 said:
Maybe I will buy Windows to make it work in VM...
Only can you interpretate why fastboot oem edl makes the screen go off?
Click to expand...
Click to collapse
do you have qualcom drivers instaled?
No
Will try tomorrow.
Thanks again.
The link to your dropbox for Qualcomm drivers is for Windows, i found that:https://developer.qualcomm.com/download/software
and Snapdragon SDK but I have to register.
Is Snapdragon SDK actually Qualcomm drivers?
helderfp said:
do you have qualcom drivers instaled?
Click to expand...
Click to collapse
Hello,
OK, no Qualcomm drivers for Mac it seems... I have searched thoroughly and haven't found. I have asked a en.miui dev and waiting for the response.. Don't have them?
So I have an LG D415 and I don't know if it's bricked, softbricked, hardbricked or whatever, i'm really a noob and would really appreciate some help, I've included a picture, that shows what pops up when I try entering "Download mode" but I've already tried flashing the KDZ files, I've tried factory resetting the phone, nothing seems to work, phone always shows 0% battery even after charging for over an hour, and so I tried getting into the fastboot commands and stuff, I extracted the laf dz from the kdz files, renamed it to laf.img, put it in the same folder as my fastboot drivers (not even sure if I have the correct drivers) I open up command prompt inside the folder, type in "Fastboot flash laf laf.img" and the following appears in cmd:
target reported max download size of 536870912 bytes
sending 'laf' (13312 KB)...
OKAY [ 0.586s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.739s
I feel like I am missing something or missing some steps, I've got the laf partition, the fastboot drivers(I think) phones in fastboot mode even though at the top it says download mode, no idea as to what to do or try next, if anybody could help it would be very much appreciated...
https://drive.google.com/file/d/0B0shRlbnxbQpTFhYTnpnX3RhVUE/view?usp=sharing
SMOKYxPANDA said:
So I have an LG D415 and I don't know if it's bricked, softbricked, hardbricked or whatever, i'm really a noob and would really appreciate some help, I've included a picture, that shows what pops up when I try entering "Download mode" but I've already tried flashing the KDZ files, I've tried factory resetting the phone, nothing seems to work, phone always shows 0% battery even after charging for over an hour, and so I tried getting into the fastboot commands and stuff, I extracted the laf dz from the kdz files, renamed it to laf.img, put it in the same folder as my fastboot drivers (not even sure if I have the correct drivers) I open up command prompt inside the folder, type in "Fastboot flash laf laf.img" and the following appears in cmd:
target reported max download size of 536870912 bytes
sending 'laf' (13312 KB)...
OKAY [ 0.586s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.739s
I feel like I am missing something or missing some steps, I've got the laf partition, the fastboot drivers(I think) phones in fastboot mode even though at the top it says download mode, no idea as to what to do or try next, if anybody could help it would be very much appreciated...
https://drive.google.com/file/d/0B0shRlbnxbQpTFhYTnpnX3RhVUE/view?usp=sharing
Click to expand...
Click to collapse
What ROM are you using? I think you should try flashing the bootstack with recovery from here >> https://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632. When you flash the bootstack, recovery gets rewritten with an old version of twrp so you probably want to have an IMG of twrp to update to the latest version.
0000.0000.00 said:
What ROM are you using? I think you should try flashing the bootstack with recovery from here >> https://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632. When you flash the bootstack, recovery gets rewritten with an old version of twrp so you probably want to have an IMG of twrp to update to the latest version.
Click to expand...
Click to collapse
I'm not aware of what ROM the phone is using, and I don't even know if the bootloader is unlocked, or if the phone has TWRP or root, and I don't want to mess the phone up even more (if that's even possible) phone was a friends and he gave it to me, said I could keep it if I could fix it, and i don't currently have a working phone, so it would be really nice to fix this one, i'm really a noob when it comes to this stuff, but I'm willing to learn if that's what it takes to fix the phone, I also included a link that shows a picture of the information that appears when i type in "fastboot getvar all" in command, not sure if that could help you
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view?usp=sharing
SMOKYxPANDA said:
I'm not aware of what ROM the phone is using, and I don't even know if the bootloader is unlocked, or if the phone has TWRP or root, and I don't want to mess the phone up even more (if that's even possible) phone was a friends and he gave it to me, said I could keep it if I could fix it, and i don't currently have a working phone, so it would be really nice to fix this one, i'm really a noob when it comes to this stuff, but I'm willing to learn if that's what it takes to fix the phone, I also included a link that shows a picture of the information that appears when i type in "fastboot getvar all" in command, not sure if that could help you
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view?usp=sharing
Click to expand...
Click to collapse
So the first to do is run the command fastboot oem unlock with the phone connected to your computer with fastboot. Then download the latest twrp from https://dl.twrp.me/w7/twrp-3.1.1-0-w7.img and flash it with fastboot flash recovery twrp-3.1.1-0-w7.img making sure that you move the twrp IMG to the directory where fastboot is unless fastboot is on your path where you can just flash it from cmd in the downloads folder. After that, try to factory reset the phone and it should boot into twrp where I would flash the lollipop bootstack linked above with adb sideload "zip name here" where you put the full filename of the zip in zip name here and remove the quotes, boot into the download mode thing which is fastboot and reflash recovery with the instructions above.
---------- Post added at 11:07 AM ---------- Previous post was at 11:02 AM ----------
Also, are you trying to save any data?
0000.0000.00 said:
So the first to do is run the command fastboot oem unlock with the phone connected to your computer with fastboot. Then download the latest twrp from https://dl.twrp.me/w7/twrp-3.1.1-0-w7.img and flash it with fastboot flash recovery twrp-3.1.1-0-w7.img making sure that you move the twrp IMG to the directory where fastboot is unless fastboot is on your path where you can just flash it from cmd in the downloads folder. After that, try to factory reset the phone and it should boot into twrp where I would flash the lollipop bootstack linked above with adb sideload "zip name here" where you put the full filename of the zip in zip name here and remove the quotes, boot into the download mode thing which is fastboot and reflash recovery with the instructions above.
---------- Post added at 11:07 AM ---------- Previous post was at 11:02 AM ----------
Also, are you trying to save any data?
Click to expand...
Click to collapse
No, i'm not trying to save any data, I want a fresh start, the problem when trying the "fastboot oem unlock" command is that it gives me an error, again i put a link below to show you what appears when trying that command..
https://drive.google.com/file/d/0B0shRlbnxbQpeFlxcWxjS0l1eE0/view?usp=sharing
This is what appears on the phone, yet nothing happens
https://drive.google.com/file/d/0B0shRlbnxbQpQzVXMjZ4d3E5S3M/view?usp=sharing
SMOKYxPANDA said:
This is what appears on the phone, yet nothing happens
https://drive.google.com/file/d/0B0shRlbnxbQpQzVXMjZ4d3E5S3M/view?usp=sharing
Click to expand...
Click to collapse
Something probably happened..
Can you please send the results of fastboot getvar all so I can check.
I had already sent it, but here it is again:
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view
SMOKYxPANDA said:
I had already sent it, but here it is again:
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view
Click to expand...
Click to collapse
Could you please run fastboot oem device-info and send me an image of the result. I am just checking if the bootloader got unlocked.
0000.0000.00 said:
Could you please run fastboot oem device-info and send me an image of the result. I am just checking if the bootloader got unlocked.
Click to expand...
Click to collapse
This is the only response I get:
...
FAILED (remote: unkown command)
finished. total time: 0.002s
SMOKYxPANDA said:
This is the only response I get:
...
FAILED (remote: unkown command)
finished. total time: 0.002s
Click to expand...
Click to collapse
Then try flashing twrp and the bootstack and Tell me how it goes from there.
0000.0000.00 said:
Could you please run fastboot oem device-info and send me an image of the result. I am just checking if the bootloader got unlocked.
Click to expand...
Click to collapse
0000.0000.00 said:
Then try flashing twrp and the bootstack and Tell me how it goes from there.
Click to expand...
Click to collapse
How can I flash TWRP?
I've got a TWRP file named "TWRP_2.8.0.0_26.09.14_L90.img"
Tell me where to go from there, and also, the phone isn't even detected using the command "adb devices" it says list of devices and does'nt ever show anything...
SMOKYxPANDA said:
How can I flash TWRP?
I've got a TWRP file named "TWRP_2.8.0.0_26.09.14_L90.img" Tell me where to go from there, and also, the phone isn't even detected using the command "adb devices" it says list of devices and does'nt ever show anything...
Click to expand...
Click to collapse
Flash twrp by first moving the twrp IMG to where fastboot is and running fastboot flash recovery TWRP_2.8.0.0_26.09.14_L90.img with the phone in the download mode thing and connected to the computer.
Also, could you please re-run fastboot getvar all even if you have already run it because its output probably changed and send me an image of what it shows.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
0000.0000.00 said:
Flash twrp by first moving the twrp IMG to where fastboot is and running fastboot flash recovery TWRP_2.8.0.0_26.09.14_L90.img with the phone in the download mode thing and connected to the computer.
Also, could you please re-run fastboot getvar all even if you have already run it because its output probably changed and send me an image of what it shows.
Click to expand...
Click to collapse
After that, run fastboot reboot recovery to reboot into recovery. Press the advanced button and then press the button that says adb sideload with the touchscreen and start it. Then to install the zip run adb sideload zipname where zipname is the name of the zip you want to flash.
After that boot back into the download mode thing to reflash recovery and then reboot into recovery with fastboot reboot recovery. After that I would flash the zips for a ROM and optionally gapps with adb sideload.
This is what I get:
https://drive.google.com/file/d/0B0shRlbnxbQpN3ZrendPbkI4R1k/view?usp=sharing
SMOKYxPANDA said:
This is what I get:
https://drive.google.com/file/d/0B0shRlbnxbQpN3ZrendPbkI4R1k/view?usp=sharing
Click to expand...
Click to collapse
Were you able to flash recovery and boot into it?
0000.0000.00 said:
Were you able to flash recovery and boot into it?
Click to expand...
Click to collapse
No, you can observe in the picture where it gives me the same error message, unknown command
SMOKYxPANDA said:
No, you can observe in the picture where it gives me the same error message, unknown command
Click to expand...
Click to collapse
Could you please send me a picture of the output of fastboot devices.
---------- Post added at 08:52 PM ---------- Previous post was at 08:48 PM ----------
I think the fastboot on the phone has issues because it seems to not flash anything. I think you should try this >>> https://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429
guys, i am in the exact same situation..phone stuck on lg logo, no recovery possible, no download mode available, only fastboot
i have downloaded and extracted the img files from the original firmware, but i cannot do anything with flashboot commands..pls see below
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
c369bc71 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 5.029s]
finished. total time: 5.029s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 536870912 bytes
sending 'laf' (15872 KB)...
OKAY [ 0.501s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.531s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (13824 KB)...
OKAY [ 0.437s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.469s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
all:
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>
asahi7 said:
guys, i am in the exact same situation..phone stuck on lg logo, no recovery possible, no download mode available, only fastboot
i have downloaded and extracted the img files from the original firmware, but i cannot do anything with flashboot commands..pls see below
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
c369bc71 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 5.029s]
finished. total time: 5.029s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 536870912 bytes
sending 'laf' (15872 KB)...
OKAY [ 0.501s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.531s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (13824 KB)...
OKAY [ 0.437s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.469s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
all:
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Try https://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429
thanks, already did, unfortunately seems like there is a problem with the rom. i flash each file but when i test again i always get slb1 corrupt. no recovery, no download mode. it was worth the try
Got my bootloader unlocked, but when trying to flash or unlock critical I get an error and it goes to a screen with the razer logo, "powered by android" at the bottom, and super small text in the upper left "press any key to shutdown"
and shows this in the cmd window:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock_critical
< waiting for any device >
...
FAILED (command write failed (No error))
finished. total time: 0.027s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a arter97-kernel-r9-20190607.img
< waiting for any device >
target didn't report max-download-size
sending 'boot_a' (30140 KB)...
FAILED (command write failed (No error))
finished. total time: 0.011s
I do have the full sdk package and used android studios sdk manager to get the latest google usb driver.
HTML:
EDIT: Also I'm on a global version (bought it on razer's website)
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
blackknightavalon said:
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
Click to expand...
Click to collapse
Running the flash_all script just throws it into that shutdowns again and keeps going into it anytime I go back into fastboot mode.
also gives me this
Code:
C:\Users\zacha\Desktop\platform-tools>fastboot devices
my S/N fastboot
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed.
or is just sits there likes this:
Code:
C:\Users\zacha\Desktop\platform-tools>adb reboot bootloader
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
blackknightavalon said:
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
Click to expand...
Click to collapse
Just does the exact same thing.
Cyclo_sarin said:
Just does the exact same thing.
Click to expand...
Click to collapse
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
Click to expand...
Click to collapse
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
BeardKing said:
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Have ya'll tried using this tool?? It works I'm telling you it'll solve any issues you have with ADB and or FASTBOOT period....
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445