Database Users

Trying to flash stock on nexus 6p command prompt not recognizing commands

I'm trying to flash stock android from pure nexus, im in bootloader and have opened command prompt from the folder my images are in, I'm trying to use these commands i found on xda forum's guide to flash to stock
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
but im getting the error - 'fastboot' is not recognized as an internal or external command, operable program or batch file.
please help, how do i get through this :/

kalendaan said:
I'm trying to flash stock android from pure nexus, im in bootloader and have opened command prompt from the folder my images are in, I'm trying to use these commands i found on xda forum's guide to flash to stock
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
but im getting the error - 'fastboot' is not recognized as an internal or external command, operable program or batch file.
please help, how do i get through this :/
Click to expand...
Click to collapse
1) Is this on Windows, Linux, or Mac?
2) Were you able to unlock the bootloader on this same computer with no issues?
3) Are you getting this error after each fastboot command or just for "fastboot flash vendor"? If this is an error for any command, you should first update your platform-tools and fastboot.

kalendaan said:
I'm trying to flash stock android from pure nexus, im in bootloader and have opened command prompt from the folder my images are in, I'm trying to use these commands i found on xda forum's guide to flash to stock
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
but im getting the error - 'fastboot' is not recognized as an internal or external command, operable program or batch file.
please help, how do i get through this :/
Click to expand...
Click to collapse
Do you have the correct drivers and sdk files installed on your pc listed here? http://developer.android.com/sdk/index.html#download

kalendaan said:
I'm trying to flash stock android from pure nexus, im in bootloader and have opened command prompt from the folder my images are in, I'm trying to use these commands i found on xda forum's guide to flash to stock
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
but im getting the error - 'fastboot' is not recognized as an internal or external command, operable program or batch file.
please help, how do i get through this :/
Click to expand...
Click to collapse
You need to setup Android SDK tools on your PC. The generic process is by downloading, installing, and setting up the Android SDK. Once that is done, you should be good to go.

after updating to nougat space dissapeer

hello
i update to nougat by using these commands
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
Fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
and now instead of 64GB i see only 24..where is the rest?
i have root and twrp
thanks

Only those with the 32gb model need to flash user data
So just format your device and start over and you should have 64gb again.

ok so i just to skip the
fastboot flash userdata userdata.img
but it stays as before 24.1GB
and what is - Fastboot flash vendor vendor.img
thank you

Note: You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have. If you wish to wipe your internal storage you'd use the following command instead:
Code:
fastboot format userdata
and i did fastboot flash userdata userdata.img
so to fix these i did the flash all.bat
just left to know what is the Fastboot flash vendor vendor.img
thanks

Format data
See guide here : http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

vendor formats data???

flashing the vendor will not cause a wipe of data.
firstly fastboot format userdata
then follow the guide by Heisenberg that is stickied.
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img

what does the vendor command?

I7210I said:
what does the vendor command?
Click to expand...
Click to collapse
It will flash the vendor.img

so if the device doesn't know that he is from huawei so these will remind him?
Sent from my Nexus 6P using Tapatalk

Need help... Bricked my phone...

Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.

try http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
then flash android 6.0 maybe trupure 2.9 and then get the modem from trupure and flash it

goldentequila said:
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
Click to expand...
Click to collapse
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
---------- Post added at 04:06 PM ---------- Previous post was at 04:00 PM ----------
goldentequila said:
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
Click to expand...
Click to collapse
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
Check all the files that u have flashed

goldentequila said:
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
Click to expand...
Click to collapse
Find 18-4 firmware, it's newer anyway... the sparse chunk size error is the problem, the system.img file in that firmware file is too large for the phone to flash via fastboot (thus, it probably isn't an official image, or it's an image for the engineering flash tool, not fastboot). The proper image file with have 6-11 sparce chunks you need to flash individually.

acejavelin said:
Find 18-4 firmware, it's newer anyway... the sparse chunk size error is the problem, the system.img file in that firmware file is too large for the phone to flash via fastboot (thus, it probably isn't an official image, or it's an image for the engineering flash tool, not fastboot). The proper image file with have 6-11 sparce chunks you need to flash individually.
Click to expand...
Click to collapse
I think i made it worse lol... Because I was getting many errors (random reboots), I decided to do a full wipe to install a ROM fresh. When wiping in TWRP, I accidentally wiped "internal" too. I'm guessing that I need to do something to correct this before I can flash 18-4 firmware. Please let me know if you know what I need to do. Thank you.

goldentequila said:
I think i made it worse lol... Because I was getting many errors (random reboots), I decided to do a full wipe to install a ROM fresh. When wiping in TWRP, I accidentally wiped "internal" too. I'm guessing that I need to do something to correct this before I can flash 18-4 firmware. Please let me know if you know what I need to do. Thank you.
Click to expand...
Click to collapse
TWRP shouldn't be a part of this, nor should it matter whats on your internal storage, this is all done with fastboot.
Factory reset in stock recovery, reboot to bootloader, then flash the complete image with fastboot.

Sagar_1401 said:
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
---------- Post added at 04:06 PM ---------- Previous post was at 04:00 PM ----------
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
Check all the files that u have flashed
Click to expand...
Click to collapse
The instruction in that post said to not worry about the sparse error message, so I went with it. This is what the post said.
"You may notice a "sparse header error" when flashing at the beginning. Don't worry about it, all is well. The current AutoFlashFirmware.bat file doesn't work with this Firmware file. Flash the files manually!"
Also, i posted above too, but I just accidentally wiped internal via TWRP too. Do you know what I need to do now in order to get my phone back? I've found solutions for other phones regarding this situation, but I haven't come across one for Moto X Pure. This is what happens when you work on your phone all day long and some more into late night lol...

acejavelin said:
TWRP shouldn't be a part of this, nor should it matter whats on your internal storage, this is all done with fastboot.
Factory reset in stock recovery, reboot to bootloader, then flash the complete image with fastboot.
Click to expand...
Click to collapse
Thank you for your ongoing support. I just want to make sure I'm doing this right. I found this firmware: http://forum.xda-developers.com/showpost.php?p=69103575&postcount=243
Could you please tell me if you think that's what I should flash?
Also, if you don't mind, will you please share exact fastboot commands/process? I just don't want to make any more mistakes and make things worse. I apologize for being needy.

goldentequila said:
Thank you for your ongoing support. I just want to make sure I'm doing this right. I found this firmware: http://forum.xda-developers.com/showpost.php?p=69103575&postcount=243
Could you please tell me if you think that's what I should flash?
Also, if you don't mind, will you please share exact fastboot commands/process? I just don't want to make any more mistakes and make things worse. I apologize for being needy.
Click to expand...
Click to collapse
Yes, look in my signature and use the non-relock option: http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot

acejavelin said:
Yes, look in my signature and use the non-relock option: http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thank you very much for that. You mentioned that I would need to factory reset in stock recovery first. Do I just fastboot flash a stock recovery from the firmware zip file from 18-4, boot into its recovery, reset, and then follow the instruction above?

goldentequila said:
Thank you very much for that. You mentioned that I would need to factory reset in stock recovery first. Do I just fastboot flash a stock recovery from the firmware zip file from 18-4, boot into its recovery, reset, and then follow the instruction above?
Click to expand...
Click to collapse
Boot, flash, whatever... It is best to do a factory reset in the default recovery first, but it isn't essential.

acejavelin said:
Boot, flash, whatever... It is best to do a factory reset in the default recovery first, but it isn't essential.
Click to expand...
Click to collapse
Oh ok. Thanks again. I'll report back if I succeed (or not) later today. I appreciate your help.

acejavelin said:
Boot, flash, whatever... It is best to do a factory reset in the default recovery first, but it isn't essential.
Click to expand...
Click to collapse
Thank you so much for your help. It worked perfectly. Now I have my phone back :victory:

goldentequila said:
Thank you so much for your help. It worked perfectly. Now I have my phone back :victory:
Click to expand...
Click to collapse
Glad I could help. You're welcome.

Lol it was sparsechunk i just got confused with it and said spunk??

Bricked - Don't know what to do

I accidentally disconnected my OnePlus 8 Pro while running the MSM Tool to restore back to oxygenos from lineage. Now it is stuck in a loop where it says:
<Error!>
Upgrade download failed!
This is caused by download interruption. Recommend you use download tool try again.
You need to confirm if there is failure message on download tool or not when you see this error.
also please check if you disconnect usb or click stop button when the download is not finished yet.
You can press any key exit this message
I can boot into fastboot from this state, but I am unable to flash a recovery or use a fastboot rom.
The recovery just doesn't work when I try to boot into it, and the fastboot rom gets stuck at
"Flashing is not allowed for critical partitions"
and when I try running
fastboot flashing unlock_critical
it says something along the lines of 'device already unlocked'
I cannot boot into EDL mode either, and trying to do so doesn't work.
I feel as if I am out of options, and am very worried about my phone.
Please help!!!

I was able to successfully follow all the steps for a fastboot rom, but it still didn't work. This was through using fastboot boot on the lineageos recovery.

Dapherino said:
I was able to successfully follow all the steps for a fastboot rom, but it still didn't work. This was through using fastboot boot on the lineageos recovery.
Click to expand...
Click to collapse
Use MSM Tool. Hold all buttons very until your device appears in msm tool. YOu can start before you connect it and it should work.

xtcislove said:
Use MSM Tool. Hold all buttons very until your device appears in msm tool. YOu can start before you connect it and it should work.
Click to expand...
Click to collapse
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.

Dapherino said:
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Click to expand...
Click to collapse
Try to press start while the device is connected and then restart it. MSM tools trys to hook in first.

Dapherino said:
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Click to expand...
Click to collapse
Turn phone completely off. On msm tool, hit start so its waiting for device. Hold down ONLY the volume up and volume down buttons, plug in USB cable and you're good to go

jamescable said:
Turn phone completely off. On msm tool, hit start so its waiting for device. Hold down ONLY the volume up and volume down buttons, plug in USB cable and you're good to go
Click to expand...
Click to collapse
Thank you for the advice. I've tried this and it doesn't do anything, since I can't get to EDL mode.

xtcislove said:
Try to press start while the device is connected and then restart it. MSM tools trys to hook in first.
Click to expand...
Click to collapse
Thanks, I've tried this as well. It didn't work, since I cannot enter EDL mode.

Dapherino said:
Thank you for the advice. I've tried this and it doesn't do anything, since I can't get to EDL mode.
Click to expand...
Click to collapse
Your phone is in EDL mode when its powered off and holding ONLY both volume bottons

jamescable said:
Your phone is in EDL mode when its powered off and holding ONLY both volume bottons
Click to expand...
Click to collapse
I understand that. When I do so, it just boots into fastboot. And when I tried to enter EDL through using 'fastboot boot' with a custom recovery, it did the same thing. Now I can't even use 'fastboot boot' anymore for some reason though.

Dapherino said:
I understand that. When I do so, it just boots into fastboot. And when I tried to enter EDL through using 'fastboot boot' with a custom recovery, it did the same thing. Now I can't even use 'fastboot boot' anymore for some reason though.
Click to expand...
Click to collapse
So you tried fastboot boot recovery?
Fastboot boot will never work to boot edl

jamescable said:
So you tried fastboot boot recovery?
Fastboot boot will never work to boot edl
Click to expand...
Click to collapse
Yes. Even from a temporary custom recovery, I cannot enter edl from there.

Dapherino said:
Yes. Even from a temporary custom recovery, I cannot enter edl from there.
Click to expand...
Click to collapse
Do this. Install a custom ROM using fastboot

Download any ROM you want. Extract the payload and put it in the payload input folder.

jamescable said:
Download any ROM you want. Extract the payload and put it in the payload input folder.
Click to expand...
Click to collapse
I've tried this with 4 different roms [stock oneplus one, lineageos, pixel experience, and evolutionx]. Even though they flash successfully, I still encounter the exact same error when trying to boot into it, and I still cannot enter recovery or EDL.

Dapherino said:
I've tried this with 4 different roms [stock oneplus one, lineageos, pixel experience, and evolutionx]. Even though they flash successfully, I still encounter the exact same error when trying to boot into it, and I still cannot enter recovery or EDL.
Click to expand...
Click to collapse
This wont work and idk why. If i try a custom rom i always have to use msm tool to go back to oos.
I flash every partition with fastboot but i end in a boot loop if i where on a custom rom before.

xtcislove said:
This wont work and idk why. If i try a custom rom i always have to use msm tool to go back to oos.
I flash every partition with fastboot but i end in a boot loop if i where on a custom rom before.
Click to expand...
Click to collapse
Yeah, you need to wipe internal storage. In fastboot you can type
fastboot format userdata
fastboot format cache
Also, you can type
Fastboot -w

Dapherino said:
I accidentally disconnected my OnePlus 8 Pro while running the MSM Tool to restore back to oxygenos from lineage. Now it is stuck in a loop where it says:
<Error!>
Upgrade download failed!
This is caused by download interruption. Recommend you use download tool try again.
You need to confirm if there is failure message on download tool or not when you see this error.
also please check if you disconnect usb or click stop button when the download is not finished yet.
You can press any key exit this message
I can boot into fastboot from this state, but I am unable to flash a recovery or use a fastboot rom.
The recovery just doesn't work when I try to boot into it, and the fastboot rom gets stuck at
"Flashing is not allowed for critical partitions"
and when I try running
fastboot flashing unlock_critical
it says something along the lines of 'device already unlocked'
I cannot boot into EDL mode either, and trying to do so doesn't work.
I feel as if I am out of options, and am very worried about my phone.
Please help!!!
Click to expand...
Click to collapse
This happened to me. I tried downloading Qualcomm drivers and reinstalling them and moved my platform tools to root of C:\, among other things. I was using OEM red cable and had been having to flip it a certain way to get WARP charge, so in desperation, I switched to a non-OEM cable, C to C, and that got me back in EDL. Good luck.

jamescable said:
Yeah, you need to wipe internal storage. In fastboot you can type
fastboot format userdata
fastboot format cache
Also, you can type
Fastboot -w
Click to expand...
Click to collapse
thats part of my batch script anyway.
Code:
:choice
set /P c=Do you want to wipe all the data ( Reccomended )[Y/N]?
if /I "%c%" EQU "Y" goto :wipe
if /I "%c%" EQU "N" goto :continue
goto :choice
:wipe
fastboot -w
goto :continue
:continue
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot fastboot
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
fastboot reboot-bootloader
pause

wgs1028 said:
This happened to me. I tried downloading Qualcomm drivers and reinstalling them and moved my platform tools to root of C:\, among other things. I was using OEM red cable and had been having to flip it a certain way to get WARP charge, so in desperation, I switched to a non-OEM cable, C to C, and that got me back in EDL. Good luck.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!!!! Using a different cable worked!!!!!!!!!!!!!!!!!!!!!!!!!!!! I'm so glad my phone is ok. Thank you again, I really appreciate it.

Question Unable to install any updates

Okay so, I did root and downgraded to acquire call recording and root. Then I upgrading using the fastboot method. Locked up the critical partition but left the bootloader unlocked.
There is an update for the 2.5.3 I'm on but I cannot apply it through the official update method or the dialer method !
I've flashed both partitions with the same ROM. It is the global version I have.
What am I missing here ?
Thanks in advance.

Try adb sideload
Try to remove root before update

So like, no one knows ?

xtcislove said:
Try adb sideload
Try to remove root before update
Click to expand...
Click to collapse
I don't have root and all partitions are locked.
I can try adb sideload again but I have my doubts.
I need a way to completely flash and start over I think. This phone is weird.

"I need a way to completely flash and start over I think. This phone is weird."
How to unbrick Nothing Phone 1 fastboot bootloop
Welcome to this unbrick tutorial NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours. I do not suggest following this tutorial if...
forum.xda-developers.com
Follow this guide and in the end relock the bootloader if you like. I did this several times and i get normal otas after this.

Moderator Announcement
Thread sanitized of all "snarky" and disrespectful replies.​
Greetings to all. Just a friendly reminder if I may regarding XDA Rule 2.3 regarding member conduct:
2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
Click to expand...
Click to collapse
Please be polite to each other, and instead of replying to member comments that you may find offensive, please report them instead rather than creating a "flame war" requiring
Moderator interventions such as this. Thank you.
Regards to all: Badger50

xtcislove said:
"I need a way to completely flash and start over I think. This phone is weird."
How to unbrick Nothing Phone 1 fastboot bootloop
Welcome to this unbrick tutorial NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours. I do not suggest following this tutorial if...
forum.xda-developers.com
Follow this guide and in the end relock the bootloader if you like. I did this several times and i get normal otas after this.
Click to expand...
Click to collapse
Thanks. I will try that.

Badger50 said:
Moderator Announcement
Thread sanitized of all "snarky" and disrespectful replies.​
Greetings to all. Just a friendly reminder if I may regarding XDA Rule 2.3 regarding member conduct:
Please be polite to each other, and instead of replying to member comments that you may find offensive, please report them instead rather than creating a "flame war" requiring
Moderator interventions such as this. Thank you.
Regards to all: Badger50
Click to expand...
Click to collapse
Okay will do. Thanks.

xtcislove said:
"I need a way to completely flash and start over I think. This phone is weird."
How to unbrick Nothing Phone 1 fastboot bootloop
Welcome to this unbrick tutorial NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours. I do not suggest following this tutorial if...
forum.xda-developers.com
Follow this guide and in the end relock the bootloader if you like. I did this several times and i get normal otas after this.
Click to expand...
Click to collapse
But ... none of the files are downloadable.

rogerrulez said:
Okay will do. Thanks.
Click to expand...
Click to collapse
I was reacting to how I was talked to. Simple. And I will do it again to someone who tries to demean or belittle me.

rogerrulez said:
I was reacting to how I was talked to. Simple. And I will do it again to someone who tries to demean or belittle me.
Click to expand...
Click to collapse
Please read my PSA again about "reporting" these matters rather than replying to them.
Thank you.

rogerrulez said:
But ... none of the files are downloadable.
Click to expand...
Click to collapse
I checked every link and all are downloadable.
Super.img
Shattered tool (an alternative could be to download from the 1.1.4 fastboot rom from https://reindex-ot.github.io/ and use the cmd commands i posted you a few days ago)
every link is working and you should already setup platform tools.
What you are trying to download what is not working?
Edit: All you need is the 1.1.4 Global super.img and and 1.1.4 fastboot global rom.
You need this code to flash the images, obviously you need to edit the lines to fit your file path. Since you are an experienced user this should not be a problem.
Code:
cd /d F:\Android\NothingPhone1\Other\platform-tools_r33.0.2-windows
fastboot -w
fastboot --set-active=a
fastboot reboot fastboot
fastboot flash super F:\Android\NothingPhone1\Firmware\1.1.3_EEA_super_backup\super.img
fastboot flash abl_a F:\Android\NothingPhone1\Firmware\1.1.3\abl.img
fastboot flash aop_a F:\Android\NothingPhone1\Firmware\1.1.3\aop.img
fastboot flash bluetooth_a F:\Android\NothingPhone1\Firmware\1.1.3\bluetooth.img
fastboot flash boot_a F:\Android\NothingPhone1\Firmware\1.1.3\boot.img
fastboot flash cpucp_a F:\Android\NothingPhone1\Firmware\1.1.3\cpucp.img
fastboot flash devcfg_a F:\Android\NothingPhone1\Firmware\1.1.3\devcfg.img
fastboot flash dsp_a F:\Android\NothingPhone1\Firmware\1.1.3\dsp.img
fastboot flash dtbo_a F:\Android\NothingPhone1\Firmware\1.1.3\dtbo.img
fastboot flash featenabler_a F:\Android\NothingPhone1\Firmware\1.1.3\featenabler.img
fastboot flash hyp_a F:\Android\NothingPhone1\Firmware\1.1.3\hyp.img
fastboot flash imagefv_a F:\Android\NothingPhone1\Firmware\1.1.3\imagefv.img
fastboot flash keymaster_a F:\Android\NothingPhone1\Firmware\1.1.3\keymaster.img
fastboot flash modem_a F:\Android\NothingPhone1\Firmware\1.1.3\modem.img
fastboot flash multiimgoem_a F:\Android\NothingPhone1\Firmware\1.1.3\multiimgoem.img
fastboot flash odm_a F:\Android\NothingPhone1\Firmware\1.1.3\odm.img
fastboot flash product_a F:\Android\NothingPhone1\Firmware\1.1.3\product.img
fastboot flash qupfw_a F:\Android\NothingPhone1\Firmware\1.1.3\qupfw.img
fastboot flash shrm_a F:\Android\NothingPhone1\Firmware\1.1.3\shrm.img
fastboot flash system_a F:\Android\NothingPhone1\Firmware\1.1.3\system.img
fastboot flash system_ext_a F:\Android\NothingPhone1\Firmware\1.1.3\system_ext.img
fastboot flash tz_a F:\Android\NothingPhone1\Firmware\1.1.3\tz.img
fastboot flash uefisecapp_a F:\Android\NothingPhone1\Firmware\1.1.3\uefisecapp.img
fastboot flash vbmeta_a F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta.img
fastboot flash vbmeta_system_a F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta_system.img
fastboot flash vendor_a F:\Android\NothingPhone1\Firmware\1.1.3\vendor.img
fastboot flash vendor_boot_a F:\Android\NothingPhone1\Firmware\1.1.3\vendor_boot.img
fastboot flash xbl_a F:\Android\NothingPhone1\Firmware\1.1.3\xbl.img
fastboot flash xbl_config_a F:\Android\NothingPhone1\Firmware\1.1.3\xbl_config.img
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot fastboot
REM fastboot flash super F:\Android\NothingPhone1\Firmware\1.1.3_EEA_super_backup\super.img
fastboot flash abl_b F:\Android\NothingPhone1\Firmware\1.1.3\abl.img
fastboot flash aop_b F:\Android\NothingPhone1\Firmware\1.1.3\aop.img
fastboot flash bluetooth_b F:\Android\NothingPhone1\Firmware\1.1.3\bluetooth.img
fastboot flash boot_b F:\Android\NothingPhone1\Firmware\1.1.3\boot.img
fastboot flash cpucp_b F:\Android\NothingPhone1\Firmware\1.1.3\cpucp.img
fastboot flash devcfg_b F:\Android\NothingPhone1\Firmware\1.1.3\devcfg.img
fastboot flash dsp_b F:\Android\NothingPhone1\Firmware\1.1.3\dsp.img
fastboot flash dtbo_b F:\Android\NothingPhone1\Firmware\1.1.3\dtbo.img
fastboot flash featenabler_b F:\Android\NothingPhone1\Firmware\1.1.3\featenabler.img
fastboot flash hyp_b F:\Android\NothingPhone1\Firmware\1.1.3\hyp.img
fastboot flash imagefv_b F:\Android\NothingPhone1\Firmware\1.1.3\imagefv.img
fastboot flash keymaster_b F:\Android\NothingPhone1\Firmware\1.1.3\keymaster.img
fastboot flash modem_b F:\Android\NothingPhone1\Firmware\1.1.3\modem.img
fastboot flash multiimgoem_b F:\Android\NothingPhone1\Firmware\1.1.3\multiimgoem.img
fastboot flash odm_b F:\Android\NothingPhone1\Firmware\1.1.3\odm.img
fastboot flash product_b F:\Android\NothingPhone1\Firmware\1.1.3\product.img
fastboot flash qupfw_b F:\Android\NothingPhone1\Firmware\1.1.3\qupfw.img
fastboot flash shrm_b F:\Android\NothingPhone1\Firmware\1.1.3\shrm.img
fastboot flash system_b F:\Android\NothingPhone1\Firmware\1.1.3\system.img
fastboot flash system_ext_b F:\Android\NothingPhone1\Firmware\1.1.3\system_ext.img
fastboot flash tz_b F:\Android\NothingPhone1\Firmware\1.1.3\tz.img
fastboot flash uefisecapp_b F:\Android\NothingPhone1\Firmware\1.1.3\uefisecapp.img
fastboot flash vbmeta_b F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta.img
fastboot flash vbmeta_system_b F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta_system.img
fastboot flash vendor_b F:\Android\NothingPhone1\Firmware\1.1.3\vendor.img
fastboot flash vendor_boot_b F:\Android\NothingPhone1\Firmware\1.1.3\vendor_boot.img
fastboot flash xbl_b F:\Android\NothingPhone1\Firmware\1.1.3\xbl.img
fastboot flash xbl_config_b F:\Android\NothingPhone1\Firmware\1.1.3\xbl_config.img
fastboot reboot bootloader
fastboot --set-active=a
fastboot reboot
pause

xtcislove said:
I checked every link and all are downloadable.
Super.img
Shattered tool (an alternative could be to download from the 1.1.4 fastboot rom from https://reindex-ot.github.io/ and use the cmd commands i posted you a few days ago)
every link is working and you should already setup platform tools.
What you are trying to download what is not working?
Click to expand...
Click to collapse
Thanks. Yeah, I've looked a that. But I compared both files and don't see any differences in the batch files. SO I'm wondering ... how is this better ?

rogerrulez said:
Thanks. Yeah, I've looked a that. But I compared both files and don't see any differences in the batch files. SO I'm wondering ... how is this better ?
Click to expand...
Click to collapse
Which two batch files? They will flash the super.img and ALL other partitions. The code i posted will flash BOTH slots.
You need a way to completely flash and start over. This is the way.

xtcislove said:
Which two batch files? They will flash the super.img and ALL other partitions. The code i posted will flash BOTH slots.
You need a way to completely flash and start over. This is the way.
Click to expand...
Click to collapse
Correct. I need to start over.

rogerrulez said:
Correct. I need to start over.
Click to expand...
Click to collapse
So whats the problem now?
1. Unlock Bootloader
2. Flash super.img
3. Flash fastboot rom to both slots.
4. Relockk bootloader or boot to android.

xtcislove said:
So whats the problem now?
1. Unlock Bootloader
2. Flash super.img
3. Flash fastboot rom to both slots.
4. Relockk bootloader or boot to android.
Click to expand...
Click to collapse
Thanks. Done that. many times actually. lol

rogerrulez said:
Thanks. Done that. many times actually. lol
Click to expand...
Click to collapse
And you installed all updates normaly with system updates or did you install anything manually?

xtcislove said:
I checked every link and all are downloadable.
Super.img
Shattered tool (an alternative could be to download from the 1.1.4 fastboot rom from https://reindex-ot.github.io/ and use the cmd commands i posted you a few days ago)
every link is working and you should already setup platform tools.
What you are trying to download what is not working?
Edit: All you need is the 1.1.4 Global super.img and and 1.1.4 fastboot global rom.
You need this code to flash the images, obviously you need to edit the lines to fit your file path. Since you are an experienced user this should not be a problem.
Code:
cd /d F:\Android\NothingPhone1\Other\platform-tools_r33.0.2-windows
fastboot -w
fastboot --set-active=a
fastboot reboot fastboot
fastboot flash super F:\Android\NothingPhone1\Firmware\1.1.3_EEA_super_backup\super.img
fastboot flash abl_a F:\Android\NothingPhone1\Firmware\1.1.3\abl.img
fastboot flash aop_a F:\Android\NothingPhone1\Firmware\1.1.3\aop.img
fastboot flash bluetooth_a F:\Android\NothingPhone1\Firmware\1.1.3\bluetooth.img
fastboot flash boot_a F:\Android\NothingPhone1\Firmware\1.1.3\boot.img
fastboot flash cpucp_a F:\Android\NothingPhone1\Firmware\1.1.3\cpucp.img
fastboot flash devcfg_a F:\Android\NothingPhone1\Firmware\1.1.3\devcfg.img
fastboot flash dsp_a F:\Android\NothingPhone1\Firmware\1.1.3\dsp.img
fastboot flash dtbo_a F:\Android\NothingPhone1\Firmware\1.1.3\dtbo.img
fastboot flash featenabler_a F:\Android\NothingPhone1\Firmware\1.1.3\featenabler.img
fastboot flash hyp_a F:\Android\NothingPhone1\Firmware\1.1.3\hyp.img
fastboot flash imagefv_a F:\Android\NothingPhone1\Firmware\1.1.3\imagefv.img
fastboot flash keymaster_a F:\Android\NothingPhone1\Firmware\1.1.3\keymaster.img
fastboot flash modem_a F:\Android\NothingPhone1\Firmware\1.1.3\modem.img
fastboot flash multiimgoem_a F:\Android\NothingPhone1\Firmware\1.1.3\multiimgoem.img
fastboot flash odm_a F:\Android\NothingPhone1\Firmware\1.1.3\odm.img
fastboot flash product_a F:\Android\NothingPhone1\Firmware\1.1.3\product.img
fastboot flash qupfw_a F:\Android\NothingPhone1\Firmware\1.1.3\qupfw.img
fastboot flash shrm_a F:\Android\NothingPhone1\Firmware\1.1.3\shrm.img
fastboot flash system_a F:\Android\NothingPhone1\Firmware\1.1.3\system.img
fastboot flash system_ext_a F:\Android\NothingPhone1\Firmware\1.1.3\system_ext.img
fastboot flash tz_a F:\Android\NothingPhone1\Firmware\1.1.3\tz.img
fastboot flash uefisecapp_a F:\Android\NothingPhone1\Firmware\1.1.3\uefisecapp.img
fastboot flash vbmeta_a F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta.img
fastboot flash vbmeta_system_a F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta_system.img
fastboot flash vendor_a F:\Android\NothingPhone1\Firmware\1.1.3\vendor.img
fastboot flash vendor_boot_a F:\Android\NothingPhone1\Firmware\1.1.3\vendor_boot.img
fastboot flash xbl_a F:\Android\NothingPhone1\Firmware\1.1.3\xbl.img
fastboot flash xbl_config_a F:\Android\NothingPhone1\Firmware\1.1.3\xbl_config.img
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot fastboot
REM fastboot flash super F:\Android\NothingPhone1\Firmware\1.1.3_EEA_super_backup\super.img
fastboot flash abl_b F:\Android\NothingPhone1\Firmware\1.1.3\abl.img
fastboot flash aop_b F:\Android\NothingPhone1\Firmware\1.1.3\aop.img
fastboot flash bluetooth_b F:\Android\NothingPhone1\Firmware\1.1.3\bluetooth.img
fastboot flash boot_b F:\Android\NothingPhone1\Firmware\1.1.3\boot.img
fastboot flash cpucp_b F:\Android\NothingPhone1\Firmware\1.1.3\cpucp.img
fastboot flash devcfg_b F:\Android\NothingPhone1\Firmware\1.1.3\devcfg.img
fastboot flash dsp_b F:\Android\NothingPhone1\Firmware\1.1.3\dsp.img
fastboot flash dtbo_b F:\Android\NothingPhone1\Firmware\1.1.3\dtbo.img
fastboot flash featenabler_b F:\Android\NothingPhone1\Firmware\1.1.3\featenabler.img
fastboot flash hyp_b F:\Android\NothingPhone1\Firmware\1.1.3\hyp.img
fastboot flash imagefv_b F:\Android\NothingPhone1\Firmware\1.1.3\imagefv.img
fastboot flash keymaster_b F:\Android\NothingPhone1\Firmware\1.1.3\keymaster.img
fastboot flash modem_b F:\Android\NothingPhone1\Firmware\1.1.3\modem.img
fastboot flash multiimgoem_b F:\Android\NothingPhone1\Firmware\1.1.3\multiimgoem.img
fastboot flash odm_b F:\Android\NothingPhone1\Firmware\1.1.3\odm.img
fastboot flash product_b F:\Android\NothingPhone1\Firmware\1.1.3\product.img
fastboot flash qupfw_b F:\Android\NothingPhone1\Firmware\1.1.3\qupfw.img
fastboot flash shrm_b F:\Android\NothingPhone1\Firmware\1.1.3\shrm.img
fastboot flash system_b F:\Android\NothingPhone1\Firmware\1.1.3\system.img
fastboot flash system_ext_b F:\Android\NothingPhone1\Firmware\1.1.3\system_ext.img
fastboot flash tz_b F:\Android\NothingPhone1\Firmware\1.1.3\tz.img
fastboot flash uefisecapp_b F:\Android\NothingPhone1\Firmware\1.1.3\uefisecapp.img
fastboot flash vbmeta_b F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta.img
fastboot flash vbmeta_system_b F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta_system.img
fastboot flash vendor_b F:\Android\NothingPhone1\Firmware\1.1.3\vendor.img
fastboot flash vendor_boot_b F:\Android\NothingPhone1\Firmware\1.1.3\vendor_boot.img
fastboot flash xbl_b F:\Android\NothingPhone1\Firmware\1.1.3\xbl.img
fastboot flash xbl_config_b F:\Android\NothingPhone1\Firmware\1.1.3\xbl_config.img
fastboot reboot bootloader
fastboot --set-active=a
fastboot reboot
pause
Click to expand...
Click to collapse
Okay. Thanks man.

No ! My phone is turned off. I can't do any updates.