Related
Here is the story in a nutshell I flashed xdabbeb's bootstack, then his rom. Then I did something stupid such as wipe everything folks, I mean everything. So my phone then restarted and I am able to get into recovery twrp 2.7.
I have tried in twrp to sideload, mount neither which work.
I have my drivers installed it says in device manager when I plug the phone up for download mode
android- galaxy nexus adb
and under ports it says LGE AndroidNet for VZW ADB Interface com41
I tried lg flash tool, tried with old vs98010b rom
pid:
imei:
model:
dll: vs980
bin: vs98010b_13.tot
swv:
swov:
model information check fail!
00000000
I really need help guys, are there any adb commands I can type or are there any drivers I need to install
Ok when i hold the up and plug in it takes me to fastboot
[500] fastboot mode started
[550] udc_start()
[720] reset
[730] portcharge
[740] reset
[750] portcharge
and the device only registers as android under other on my computer
i've installed lg drivers
How can you fastboot flash? When I hold up and plug in for fastboot my computer wont register a driver just shows android what are the commands and how do I use fastboot
timenewton said:
How can you fastboot flash? When I hold up and plug in for fastboot my computer wont register a driver just shows android what are the commands and how do I use fastboot
Click to expand...
Click to collapse
Download mode is not going to work because the laf partition (this allows for download mode to work) is wiped when you flash xdabbeb's bootstack in favor of fastboot mode.
I suggest you pm xdabbeb; he will guide you on the steps to using the necessary fastboot commands to get your phone working again. He's already helped a few people that were in the same situation as you are in right now.
Fastboot is good because you can write certain partitons at a time without having to .tot and wipe your whole phone.
You could also flash his xdabbeb_vs98024a_laf.zip http://www.androidfilehost.com/?fid=23329332407586639 file in TWRP 2.7 to restore download mode, but you will end up wiping your whole phone by using the LG Flash Tool, even your sd card when you restore your phone.
You said you "wiped everything", I'm not sure if that means your sd card too, if so, then that might be the easiest thing to do since you still have access to recovery. You will need an otg cable and a flash drive to mount the flash drive in TWRP 2.7 and flash the file, unless you can side load the file with adb.
Either way, like I mentioned earlier, it might be a good idea to pm xdabbeb first.
Hey my phone is already wiped even sdcard, but the thing is i cant flash that file because I can not get it on my phone. So ill ask xdabbeb the fastboot commands. Yeah and I read about the otg cable, ordered one of those babies should be here this saturday and hopefully it will mount my flash drive in that case id be golden untill then ill see what mr xdabbeb has to say.
cant sideload
everytime i try to sideload the file it just says cant read file or something like that
And I really appreciate you responding. Always nice to get support from somebody when your just sitting here and your phone seems like it hasnt been working for an eternity. Almost depressing not hearing from anyhbody and just seeing all the views but no replys. Thank you
Hey there...Fastboot is about as basic/simple/reliable as it comes. If you have adb/fastboot set up properly then command is:
fastboot flash <partition> <filename>
for example:
fastboot flash recovery recovery.img
In your case, you claim to have a working recovery (twrp 2.7), but are unable to copy files from your computer to your phone. It sounds like you don't have the proper drivers installed so that you can use adb from recovery. This is a common/known issue with windows and I believe I replied to you in the rom thread already about this, but you need to install/use Koush's universal adb driver and simply copy the rom file over to your phone using the following command:
adb push <filename> /sdcard/
After you have the file there you can flash it as normal in recovery.
If you want to use a kdz/tot method to restore your phone, just download the laf zip file from my thread, extract the laf.img file from the zip, and use the following command to put it in place:
fastboot flash laf laf.img
Then you can go about the tot restore method described in the thread here. You don't need to put the tot file itself on your phone. It just needs to be on your computer.
I get to sdk and open cmd
type adb devices it says
List of devices attached
0215817d960ce580 sideload
Then I type adb push rom.zip /sdcard/
error: closed
When phone is plugged in for adb device manager says under android device- Google galaxy Nexus ADB Interface
I have universal drivers installed and I goto device manger to update drivers where clockworkmod is installed and it doesnt do anything
Fastboot it says in other devices in device manager
Android
PCI Data Acquisition and Signal Processing Controller
I type fastboot flash recovery laf.img
<waiting for device>
timenewton said:
I get to sdk and open cmd
type adb devices it says
List of devices attached
0215817d960ce580 sideload
Then I type adb push rom.zip /sdcard/
error: closed
When phone is plugged in for adb device manager says under android device- Google galaxy Nexus ADB Interface
I have universal drivers installed and I goto device manger to update drivers where clockworkmod is installed and it doesnt do anything
Fastboot it says in other devices in device manager
Android
PCI Data Acquisition and Signal Processing Controller
I type fastboot flash recovery laf.img
<waiting for device>
Click to expand...
Click to collapse
Wait, I'm confused here a little bit. Are you trying to do sideload mode in TWRP or are you using fastboot mode?
And the command you typed is not correct fastboot flash recovery laf.img...you don't want to do that...this would flash the laf.img in your recovery partition.
xdabbeb referenced two methods to you...one was pushing a Rom to your sdcard and then flashing that Rom in TWRP to get your phone booting...the other was to flash the laf.img file and do a .tot if that's what you prefer.
It seems like you want to do a .tot restore, so do the second method xdabbeb suggested.
Get into fastboot mode and type fastboot flash laf laf.img
Make sure you use the correct laf.img...you can extract it from the zip in my previous post/link.
After this your download mode should be working again.
I was trying either one
For fastboot I downloaded xdabbebs laf
the image file in his file is laf.img, if thats not the right file then where is the recovery.img
So the recovery.img would have been one that i made?
and laf is so I can us lg tool to tot flash?
Even when i try to flash the laf it keeps saying waiting for device. I have the drivers koushu installed and lg
timenewton said:
I was trying either one
For fastboot I downloaded xdabbebs laf
the image file in his file is laf.img, if thats not the right file then where is the recovery.img
So the recovery.img would have been one that i made?
and laf is so I can us lg tool to tot flash?
Click to expand...
Click to collapse
Yes, download xdabbeb's laf.img, it's the link I gave you originally. You will have to take out the laf.img file from the zip file that is called xdabbeb_vs98024a_laf.zip
The recovery command he gave was just an example, there was no need for you to use it.
Yes, flashing the laf.img will fix your download mode and you will be able to do the .tot method.
What am I suppose to do about it saying wiating for device, its not detecting it
timenewton said:
What am I suppose to do about it saying wiating for device, its not detecting it
Click to expand...
Click to collapse
That sounds like a driver issue. Reboot your computer and turn off the phone and start again. See if that helps. You can also remove the drivers and re-install...I suggest you reboot your computer every time you install new drivers.
EDIT:
Are you using a newer adb.exe from your android sdk? If you have ioroot25 installed on your computer I suggest you use the folder/files from there. It has a newer adb.exe in there; put your laf.img file in that folder too if you do use that instead, and run the command prompt from within that folder.
Ok when my phone is plugged into my comp, im on win 7 it shows up as android under other devices when started in fastboot mode. When I browse to the driver location to load for the android it says no driver found for it.
Yes i just installed the sdk like 2 days ago so I know its current.
As far as the driver situation, why would I need to uninstall if it isnt even installing a driver.
This is terrible
timenewton said:
Ok when my phone is plugged into my comp, im on win 7 it shows up as android under other devices when started in fastboot mode. When I browse to the driver location to load for the android it says no driver found for it.
Click to expand...
Click to collapse
timenewton said:
Yes i just installed the sdk like 2 days ago so I know its current.
As far as the driver situation, why would I need to uninstall if it isnt even installing a driver.
This is terrible
Click to expand...
Click to collapse
For me it shows up under "ADB Interface", but I don't have the universal driver installed.
I didn't realize it wasn't installing the driver for you.
You have to get that driver going or you won't be able to get your phone fixed. Maybe try a different usb port or a different computer.
Man yeah mine doesnt look at all like that. Im uninstalling lg driver and universal one and clearing temp folder. Then restart and reinstall maybe that will work. So its just the koushu driver that works for fastboot and adb right?
timenewton said:
Man yeah mine doesnt look at all like that. Im uninstalling lg driver and universal one and clearing temp folder. Then restart and reinstall maybe that will work. So its just the koushu driver that works for fastboot and adb right?
Click to expand...
Click to collapse
Yeah, it should work. I've read posts by others stating that it works.
Yep just reinstalled the universal drivers, plug phone up into fastboot and still get the same result
Can you perhaps send me that driver you have? Because I know if you have that one and it works for you it SHOULD work for me. Murphs law is killing me. I can pm you my email address
last day i accidentally delete the os of my honor 4x..does somebody know how to install new os and where to download a new one?
jdaryl04E19 said:
last day i accidentally delete the os of my honor 4x..does somebody know how to install new os and where to download a new one?
Click to expand...
Click to collapse
hmm...model code?
and your device is unlocked bootloader?
Giannhs Togias said:
hmm...model code?
and your device is unlocked bootloader?
Click to expand...
Click to collapse
Che2-L11....yes it is unlocked, it was accidentally deleted using TWRP.
is it still possible to make it work again?
thank you in advance.
jdaryl04E19 said:
Che2-L11....yes it is unlocked, it was accidentally deleted using TWRP.
is it still possible to make it work again?
thank you in advance.
Click to expand...
Click to collapse
Step1: Download the ROM Package from the link
http://consumer.huawei.com/jo/support/downloads/detail/index.htm?id=87523
Step2: Extract using Winrar. (Inside dload folder you will find Update.app file)
Step3: Download Huawei Update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
Step4:: Now Run the huawei update extractor and point to the update.app file.
Now the contents of the update.app file will be displayed.
Select the Boot.img,recovery.img and System.img alone and select extract by rightclicking it.
Step5: You need the adb tool kit.
https://drive.google.com/file/d/0B8C...R3c/view?pli=1
Step6: Install and configure the Adb (yes all)
Step7: Copy the extracted recovery.img,system.img and boot.img to the adb root folder which should be in c:\adb\.
Step8: Open fastboot (connect the device to usb and press vol down) + open adb (shift+right click and select to open cmd here)
And now type in cmd:
1. "fastboot devices" -Displays some id of your device which makes sure your device is connected.
2. "fastboot flash recovery recovery.img" - Flashes stock recovery
3. "fastboot flash system system.img" - Replaces your custom rom with stock rom
4. "fastboot flash boot boot.img" - Flashes boot partition which is need to boot stock rom.
5. "fastboot reboot"
Step9: End restart your phone,open recovery and select "Wipe data/factory reset :laugh:
Giannhs Togias said:
Step1: Download the ROM Package from the link
http://consumer.huawei.com/jo/support/downloads/detail/index.htm?id=87523
Step2: Extract using Winrar. (Inside dload folder you will find Update.app file)
Step3: Download Huawei Update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
Step4:: Now Run the huawei update extractor and point to the update.app file.
Now the contents of the update.app file will be displayed.
Select the Boot.img,recovery.img and System.img alone and select extract by rightclicking it.
Step5: You need the adb tool kit.
https://drive.google.com/file/d/0B8C...R3c/view?pli=1
Step6: Install and configure the Adb (yes all)
Step7: Copy the extracted recovery.img,system.img and boot.img to the adb root folder which should be in c:\adb\.
Step8: Open fastboot (connect the device to usb and press vol down) + open adb (shift+right click and select to open cmd here)
And now type in cmd:
1. "fastboot devices" -Displays some id of your device which makes sure your device is connected.
2. "fastboot flash recovery recovery.img" - Flashes stock recovery
3. "fastboot flash system system.img" - Replaces your custom rom with stock rom
4. "fastboot flash boot boot.img" - Flashes boot partition which is need to boot stock rom.
5. "fastboot reboot"
Step9: End restart your phone,open recovery and select "Wipe data/factory reset :laugh:
Click to expand...
Click to collapse
i was in the cmd and started to type the commands but it say that the "fastboot" is not recognized as an external or internal command, operable or batch file...
my phone is open in fastboot and rescue mode and "unlocked"
jdaryl04E19 said:
i was in the cmd and started to type the commands but it say that the "fastboot" is not recognized as an external or internal command, operable or batch file...
my phone is open in fastboot and rescue mode and "unlocked"
Click to expand...
Click to collapse
you need to download minimal adb and fastboot, and run the commands from it. or, you can do it the easy way. just put your update.app file inside /dload/ folder, and do the forced upgrade. if its not working, then fallback to fastboot method.
jdaryl04E19 said:
last day i accidentally delete the os of my honor 4x..does somebody know how to install new os and where to download a new one?
Click to expand...
Click to collapse
This method is propably easiest https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702 It also has link to site that has firmwares.
keikari said:
This method is propably easiest https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702 It also has link to site that has firmwares.
Click to expand...
Click to collapse
Thank you
I easily flash any roms via twrp, but recently some rom come with payload.bin inside the zip. I cant manage to flash it via twrp, it ends up with error with zip format?
I saw a thread that mentions to unpack the payload.bin and put all unpacked files into fastboot folder, then fastboot these files separately.
Is there any way to make it as easy as it used to.
stevedat said:
I easily flash any roms via twrp, but recently some rom come with payload.bin inside the zip. I cant manage to flash it via twrp, it ends up with error with zip format?
I saw a thread that mentions to unpack the payload.bin and put all unpacked files into fastboot folder, then fastboot these files separately.
Is there any way to make it as easy as it used to.
Click to expand...
Click to collapse
Actually. Its not that hard the using the fastboot version. You will just extract the file then run the batch file. Then wait to finish. Better than ota. Retain my data.
Identity77 said:
Actually. Its not that hard the using the fastboot version. You will just extract the file then run the batch file. Then wait to finish. Better than ota. Retain my data.
Click to expand...
Click to collapse
You mean that if I come from other Rom, just wipe all in twro, then flash it by using batch file and just connected the phone to pc as fastboot mode.
stevedat said:
You mean that if I come from other Rom, just wipe all in twro, then flash it by using batch file and just connected the phone to pc as fastboot mode.
Click to expand...
Click to collapse
I Didnt try with other rom. It has the a and b thing. I got problem with ota because im rooted with magisk. Got into bootlloop. This fastboot thing saves me. And i was able to upgrade to latest.
Been getting this error after trying to flash to my k20 pro, removing the checkpoint just makes it instantly flash and nothing changes. Any help?
WaiAi said:
Been getting this error after trying to flash to my k20 pro, removing the checkpoint just makes it instantly flash and nothing changes. Any help?
Click to expand...
Click to collapse
I am facing same problem, but no problem there, phone boot up after flash.
Ignore it. To get it done without this error you have to lock your bootloader...
thiagodark said:
Ignore it. To get it done without this error you have to lock your bootloader...
Click to expand...
Click to collapse
Nothing happens still, just says flash done and phone stays in fastboot loop
I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
SageDroid said:
I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
You have saved my life sir, days of surfing the internet with no solution, you have saved me a new phone.
SageDroid said:
I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
Thank you very very very much. ( I should stop messing with this stuff )
I also had to fiddle around until I figured it out. I don't understand why all instructions are based on the Mi Flash tool. It seems to be just a GUI for fastboot, optimized for Xiaomi devices.
If you download fastboot and set it as a PATH system variable, you can run the scripts from the rom folder with one click. Super easy and you never have to deal with the "Mi Flash tool" again.
SageDroid said:
I also had to fiddle around until I figured it out. I don't understand why all instructions are based on the Mi Flash tool. It seems to be just a GUI for fastboot, optimized for Xiaomi devices.
If you download fastboot and set it as a PATH system variable, you can run the scripts from the rom folder with one click. Super easy and you never have to deal with the "Mi Flash tool" again.
Click to expand...
Click to collapse
I got stuck in a fastboot loop again have ran into a few different issues, first of which, is that I have a mismatching image or device, this doesn't always show at the start, sometimes it stops half way through and when I start it back up again I'm met with that. Other times it starts with that and once I remove that part of the script it does some stuff and stops on deleting boot. I'm pretty sure I've been using the right roms, or I should have at least once by now. Before it got into a fastboot loop I had the xiaomi eu rom and I flashed the vendor that I was told to flash with the rom, does either of those have anything to do with it?
Call the script from the terminal and post what the output is.
You can only execute the script directly if you have defined "fastboot" as a global PATH variable. You can verify this by checking that you can call "fastboot devices" from anywhere without getting an error message.
Niaz
SageDroid said:
I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
thanks a lot brother
SageDroid said:
I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
It works thank you!!! :victory::victory:
Genius thanks!
SageDroid said:
I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
Thank yoou!!!!
SageDroid said:
I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
Thank you so much, you saved me of a lot of stress. It was literally the only thing that worked after searching all over the internet. You literally saved me of hundreds of dollars, money that in this current pandemic situation, I do not have.
Thank you very. very much.
Thank's
Thank you! Very much! After long hours of searching you're solution is the only one that worked.
SageDroid said:
I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
Thanks a lot for this method!!! You saved me from losing all my data by flashing all except storage.
Thank you really
sagedroid said:
i had the same problem. Forget the mi flash tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the mi flash tool and navigate to the subfolder "source/third party/google/android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
you are god, i was really nervius!
This is bound to the latest MiFlash tool. You can skip it by getting into "Configuration" and then erasing that line at "Checkpoint". Hit "OK" and you're good to go.
Try copiying the rom zip (just folder that is 1 level back to images folder) to root of C drive and try installing the rom. It worked for me.. Flashtool doesnt like subfolders..
Sent from my Redmi K20 Pro using Tapatalk
abees said:
Try copiying the rom zip (just folder that is 1 level back to images folder) to root of C drive and try installing the rom. It worked for me.. Flashtool doesnt like subfolders..
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
I am having a hard time using the cmd method with the error "flash_all.bat not recognized"
But i tried your method and it works . Thank you so much
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
Click to expand...
Click to collapse
Go to https://developers.google.com/android/images and flash manually it's work with me
Sent from my BASIC using Tapatalk
When you run the flash all in fastboot, what messages/errors does it show?
I once ran into a similar problem, the fact that you have unlocked the bootloader is good as you can flash the factory image and boot it up.
Usually once in fastboot I check the devices with "fastboot devices", if it shows up, I close the adb window, copy the factory image files to the adb folder, and doublec click the flash all bat. It should do everything by itself and reboot now.
TENN3R said:
When you run the flash all in fastboot, what messages/errors does it show?
I once ran into a similar problem, the fact that you have unlocked the bootloader is good as you can flash the factory image and boot it up.
Usually once in fastboot I check the devices with "fastboot devices", if it shows up, I close the adb window, copy the factory image files to the adb folder, and doublec click the flash all bat. It should do everything by itself and reboot now.
Click to expand...
Click to collapse
Just to add to this, make sure you left the image-coral-[buildnumber].[builddate].zip ZIPPED. Your folder should look something like this one, although you might also have your platform-tools in that same directory, which is perfectly fine, but not necessary if you have them added to your path.
Just try redoing the flash-all.bat again. This time, though, do it from powershell. Here's what to do. Right click in the folder, not on any item, just in the folder, and you should see "open powershell" (or command prompt, if this is the case, then just type powershell into the cmd window), click that. Then, type or copy and paste into the powershell prompt while in that directory:
.\flash-all.bat | Tee xda-flash-attempt.log
and if it still doesn't work and you're stuck in fastboot, just upload that .log file, so we can see what happened. If you're curious, what Tee does is it simultaneously takes standard input (i.e. what you see on the screen, the output of programs) and shows it to you, as well as sends it to a file, in this case, the xda-flash-attempt.log If you really don't want to use powershell, you can accomplish what's needed by typing flash-all.bat > xda-flash-attempt.log, but you will not see any of the output, as it will all be piped into that file. The | key is the one directly below backspace, which is the same key as \, but with shift held down.
Also, if it's not working, it might be worth checking that the checksum of the zip file you downloaded is correct, possibly redownloading it, and also checking what the flash-all.bat contents are. There are two files named flash-all in the folder, one a .sh for *nix systems, and a .bat for windows. While it should automatically assume you meant the .bat, it's best to be explicit. The .sh really wouldn't do anything different, if it worked, so it's a minor issue that really wouldn't make a difference, but still.
Edit: when you do type flash-all, the cmd prompt was in the directory with the flash-all.bat file as well as all of the other necessary files, yes? Seems obvious, perhaps, but just based on the "cd\pp\p" command you ran, which doesn't do anything, you should be changing directory to the directory that holds the flash-all.bat as well as the firmware.
blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today ...
Click to expand...
Click to collapse
Like others have said, you need to extract the Google image which has a nested zip file (which you leave alone unless you need something in there). Since you apparently are stuck and cannot boot, I suggest you extract the boot.img from that nested zip file into your tools folder and fastboot flash the boot.img to be able to boot the phone to system. You may need to do the vol-down button press to enter fastboot mode. Once you have your phone back and running, boot into fastboot mode and run the flash-all again. If you extracted the Google image completely, now the script can finish. Not sure if you want to wipe the phone while doing this, so you can also "dirty flash" . If you would like to retain all your apps and app data, edit the flash-all script with notepad and remove the wipe flag (-w) from the script and SAVE it before running. Best of luck. :good:
blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
Click to expand...
Click to collapse
Put the unzipped factory image files (should be 6 of them) in your platform tools folder and then open up the command prompt in the platform tools folder and execute the flash-all command. Make sure all remnants of previous factory images, etc. are removed from the platform tools folder beforehand as well so you just have the platform tools default files in there as well as the 6 files from the factory image.
The latest version of platform tools is 30.0.4 I believe so make sure you have that version.
I just switched from a Pixel 2 xl and ran into the exact same problem with the no valid slot to boot error yesterday. It turned out I was not using the latest platform tools when flashing the factory image. I upgraded my platform tools to 30.04 and everything flashed and booted as expected.
Make sure you're using an A to C and not the C to C that comes with the phone when flashing. Yes, it matters.
Hi everyone,
Thank you so much guys for your quick responses . Well , I finally resolved my issue by the following commands so I'm just gonna post it for whomever may run into the same problem as I did .
First thing I did, was to download the latest Platform tools as well as USB Drivers and then I executed the following commands :
fastboot --slot=all flash bootloader ( Drag bootloader image ) By dragging I mean , you should unzip the flash factory image into a folder and then drag bootloader image into command prompt .
fastboot reboot bootloader
fastboot --slot=all flash radio ( Drag radio image )
fastboot reboot bootloader
fastboot --skip-reboot --slot=all update ( Drag Image file )
Boommmmm, my phone back on running again with no issue.
blackbomb1991 said:
Hi everyone,
Thank you so much guys for your quick responses . Well , I finally resolved my issue by the following commands so I'm just gonna post it for whomever may run into the same problem as I did .
First thing I did, was to download the latest Platform tools as well as USB Drivers and then I executed the following commands :
fastboot --slot=all flash bootloader ( Drag bootloader image ) By dragging I mean , you should unzip the flash factory image into a folder and then drag bootloader image into command prompt .
fastboot reboot bootloader
fastboot --slot=all flash radio ( Drag radio image )
fastboot reboot bootloader
fastboot --skip-reboot --slot=all update ( Drag Image file )
Boommmmm, my phone back on running again with no issue.
Click to expand...
Click to collapse
Woohoo! This worked perfectly. Thanks for following up with the instructions.