Related
I would like to request users to post all there boot images in a single thread for all other users. and i would also request a boot image that is the Gucci and FBI boot image modded for mytouch that is available in the dream forum, i can post them if you can't find coz with those images i can make a perfect boot ROM(special Hero) highly modded and highly cool if anybody can mod the images for my touch or just use the name magic. with that if done i can make a secure and cool hero ROM that will run as fast as cyanogen's and Good boot and graphics
This is updated with the latest tool. (Windows)
I included a zip with all files you may need at the bottom of the post.
1. Turn off your phone
2. Turn on the phone into bootloader (camera+power).
Make sure it say fastboot in the middle if not hit back and it should appear-
3. Make sure your device is found in device manger
If you don't see adb device up top in device manger find the yellow mark devices
Right Click, update driver, and point to the location of the USB Driver
(http://dl.google.com/android/android_usb_windows.zip)
4. Open and extract the below zip to your desktop
You should now have a custom and fastboot folder on your desktop
5. Open up a dos window (start>run>CMD)
6. Type cd desktop then cd fastboot
7. If you would not like to flash the sample images skip to step 9
8. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565
fastboot reboot
Part 2 Making your own images
9. Open up the "create" folder
10. Run CreateG1Splash.exe
11. Open up your image in the program and click convert
12. Go to the folder of your images and their you will find mysplash.rgb565
13. Place the mysplash.rgb565 into the fastboot folder
14. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565 (maybe the mytouch or magic spl does not have splash2 partition. dont panic if it gives any error. it cannot brick the phone)
fastboot reboot
i just copied it from the dream forum so credits to them
Here are the boot images to be edited
I finally found the images on my hard drive, so here they are. Can anybody replace G1 with mytouch
Right, so here's what I boot to =)
Andy and Astroboy my 2 favorite androids!
Nice! How do you change the boot screen?
Using fastboot
We can change the using fastboot and boot images tool, ican upload it if requested
Here's mine. I included the .jpg and the .rgb565 file for easy use, if anyone would want it.
if u can upload that it would be nice. i wanna try to mamke a nice boot screen. if u have some tutorial on how to make the glow also would be nice, sorry im still new to this as mytouch is my first android phone.
Here's one for ya
myBoot.zip has both a jpg and the raw565 file. Enjoy
edit: Also decided to add the original boot image that spawned this - myOriginalBoot.zip
edit: I finally got that peeing Andy working on this thing! framework-res.apk attached. You need to do the following:
Update your 32b phone to Cyanogen 4.1.2.1
Unzip framework-res.apk from the framework-apk.zip attachment
From a shell, run:
adb remount
adb push /path/to/framework-res.apk /system/framework/framework.apk
Now reboot your phone and enjoy your custom boot splash followed by the animation of Andy peeing on an apple that looks suspiciously familiar.
Note - I take no credit for the images you see here. I simply compiled them into boot screens for your enjoyment.
Here is mine... my first try at Adobe CS4 Fireworks... haha
Here is mine (for now)
Can anybody please change the names in these images
Charnsingh - Try these
I put these together in like 5 minutes, so if you want me to change something or if it's not quite perfect, let me know and I'm happy to correct.
Enjoy!
BTW - nice work on the Debian installer, got it running on my myTouch right now and I can't get over having LXDE on my phone
edit - I just noticed the FBI screen had Dream written on it, so you'll notice I made some adjustments to that graphic as well.
For the lxde just install vnc viewer from the market then start debian. After that go to vnc after sometime and input the values given and you Will be running lxde. Have any problem pm me. Thanks for the edit I will throw on a Gucci FBI Rom tomorrow. Just gimme your name and I will make a special one for you (with login and pass)
maybe i may just give the files coz i cant keep on updating each and every hero ROM, and people it will be universal, can be used on any hero ROM. I will create a one click file for windows and mac(you must have adb set up) and one for the phone. Files will be build.conf, the edited system files, the sound files, some image files and sim tracker app from market if you would like that. The editing will not affect the speed, i can also make a speedu script for hero as i have done for my phone which needs to be run every time you flash a hero ROM, just message me
flash troubles...
how long does it take to flash the new splash screen??? my cmd is sitting at sending 'splash1' <300kb>...
and not moving--- anyways i have another question..
there is HBOOT and FASTBOOT...
when im in FASTBOOT it says sending 'splash1' <300kb>... FAILED <remote: not allow>
when im in HBOOT it just sits at sending 'splash1' <300kb>...until i close or do something else to stop it... i let it sit for 20 min--- no way in hell should it take that long
It never takes more than a second for me...
ok so im not sure why i keep getting remote: not allow any help out there?
What SPL are you using? Search the forum for how to root your myTouch.
I have tried over and over to install the USB driver and it will not install. Im running Win7. Is this my issue and how can I get the driver to work so I can run FastBoot?
11ryan11 said:
ok so im not sure why i keep getting remote: not allow any help out there?
Click to expand...
Click to collapse
iWantDonut said:
What SPL are you using? Search the forum for how to root your myTouch.
Click to expand...
Click to collapse
+1 you need to root.
I updated my phone's SPL to "Danger SPL" and now my phone wont turn back on! I press power and the black Android screen with the little green android next to it comes up but wont boot my phone! The only thing I can do is get the white screen with the 3 android's skateboarding by pressing camera + power.
Ontop of that, I had tried to update my phone's recovery image too, and I erased the old one and now it would let me upload the NEW one! So not only do I have NO PHONE but NO RECOVERY either!
What do I do!? HELP!
can you get into fastboot? (back+power)
if you can, get adb running and flash your recovery image with fastboot
you are gonna have to fast boot in the screen with the three androids on it, either a rom or a recovery
guess you betta learn how to use adb
Yea I can get into fastboot, thats the ONLY thing I can get into. How do I flash my recovery image?
http://forum.xda-developers.com/showthread.php?t=566669
boot your phone into fastboot. plug in your usb cable to your pc. this should change the fastboot icon on the screen to fastboot usb. from there, load up adb on your pc and make sure you have the fastboot option available by typing fastboot devices. it should list your phone. once that is good, type:
fastboot flash recovery and the correct name of your recovery file.
for example:
fastboot flash recovery recovery-RA-dream-v1.2.3.img
**also note...put the recovery image in your android sdk\tools folder**
this should give you a recovery to boot into.
if you dont have adb on your pc, read this and follow the instructions
http://forum.xda-developers.com/showthread.php?t=532719
I did that already, it wont work.
C:\Android>fastboot flash recovery recovery123.img
error: cannot load 'recovery123.img'
i am gonna be the one to ask this question but did you put .s between 123 like 1.2.3.
you need to be in the tools directory, not the android directory.
c:\Android\tools>fastboot flash recovery recovery-RA-dream-v1.2.3.img
and you need the recovery file IN your tools folder for it to be found as well.
No I didn't put .'s between each number I renamed my file recovery123.img so thats the way I put it in.
ok, so go to the correct directory and input what you had the first time, WITH the file IN that same folder. and then report back.
i justed rename my recovery the shortest way i can like for amon ra"s i just put amon, less typing is always better
It says C:\Android\tools is not recognized as an internal or external command, operable program or batch file.
from your c:\> prompt type this:
cd c:\android\tools
(this is assuming you have the android sdk in the c:\android folder on your pc)
if it is saying its not a folder, then that is not where you installed the android sdk.
knowfear said:
and you need the recovery file IN your tools folder for it to be found as well.
Click to expand...
Click to collapse
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
If you use the above SPL you will need new drivers for Windows. They are located here.
Click to expand...
Click to collapse
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).
what he said.
Binary100100 said:
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).
Click to expand...
Click to collapse
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.
innerspace said:
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.
Click to expand...
Click to collapse
No problem. I just hate it when something this simple drags onto multple pages. Call it a peev. So many people get intimidated by the "Danger SPL" because they don't want to risk bricking their phones. The odds of bricking your phone are extremely small if you follow directions and read everything. And sure the possibility of accomplishing this by different means exists. But when you try to tell someone to put this file in that folder and type in the full names of the files to include all the dots and dashes, it's going to get confusing and intimidating and thus these posts keep popping up.
If someone follows those very short and simple directions they shouldn't have any problems. Granted that "**** happens" and things don't always go as they should. So in that case, search for your answer. If you've searched on XDA then search Google. Out of the MILLIONS of G1's that have been sold, I am fairly certain that someone out there has had a similar problem. If not then you and your phone are literally "1 in a million" (technically it was 1 in 1.5 million a year ago so you can bet that it's well over 2 if not 3 million by now). And if you really fall into that catagory then please post a new thread (in the appropriate catagory of course) .
well the good news is u didnt brick ur phone but try a enter adb and do a nadroid back up if u hav 1 that will bring u back 2 the way u want it
either flash a nadroid or flash dreaming.nbh....i had the same problem and a nadroid worked just fine
well i happened to have some problems with a theme i was using that made the icons appear themed even in cyanogens roms , and i was told that i needed to flash the htc adp image to fix that
the problem comes here i flashed the htc adp image but i forgot to read what cyanogen said that i had to flash his rom before rebooting
so i just found that cyanogen gives us something to follow just in case it happens what happened to me here http://wiki.cyanogenmod.com/index.php/RE-recovery-img
i went to ''if you currently have an engineering or a Hard SPL'' and followed all the procedures until i got to number 4 where it asks me to Change directory to where you have saved your recovery image..i've tried lots of paths but none seems to work...ADB NOOB HERE so please help
when you didnt follow the process, you lost root.
you have to start from scratch.
.............................................................................
i typed
cd C:\recovery-RA-dream-v1.5.2.img
and it tells me the directory name is invalid what am i doing wrong?
recovery image is not a directory, it'a file. What are you trying to do?
borodin1 said:
recovery image is not a directory, it'a file. What are you trying to do?
Click to expand...
Click to collapse
im trying to flash amon ra recovery via fastboot
Easier to do it from adb
Code:
adb remount
adb shell flash_image recovery C:\recovery-RA-dream-v1.5.2.img
reboot
Just a tip: I usually rename files into something easier to type, like ra152.img. Up to you though.
You can also do it from terminal (place file on the root of sdcard)
Code:
su
flash_image recovery /sdcard/filename.img
reboot
If you must do it via fastboot
Start your phone in fastboot mode (camera/power)
Code:
fastboot flash recovery recovery-RA-dream-v1.5.2.img
fastboot reboot
borodin1 said:
Easier to do it from adb
Code:
adb remount
adb shell flash_image recovery C:\recovery-RA-dream-v1.5.2.img
reboot
Just a tip: I usually rename files into something easier to type, like ra152.img. Up to you though.
You can also do it from terminal (place file on the root of sdcard)
Code:
su
flash_image recovery /sdcard/filename.img
reboot
If you must do it via fastboot
Start your phone in fastboot mode (camera/power)
Code:
fastboot flash recovery recovery-RA-dream-v1.5.2.img
fastboot reboot
Click to expand...
Click to collapse
i would do this..but i cant since i messed up when flashing the htc adp image im following cyanogens tutorial http://wiki.cyanogenmod.com/index.php/RE-recovery-img and it says that i have to flash the new recovery through fastboot , and the part im stuck at is step 4 where he says that i need to Change directory to where you have saved your recovery image
if you can get into the main phone operating system via a boot up then use linda file manager to move them
when i type this
fastboot recovery recovery-RA-dream-v1.5.2.img
i get this message "error: cannot load 'recovery-RA-dream-v1.5.2.img
then i changed the directory to where the recovery image was and when i tried to flash i got this message
'fastboot' is not recognized as an internal or external command, operable program or batch file
Not sure, I'm not anywhere near my computer. Try putting your recovery image into different locations (i always put it on desktop) and rename it to something simpler, without any punctuation or special characters (i suggest rec.img). Also... make absolutely sure that you're NOT naming it rec.img.img . Make sure that your PC is not hiding your extensions.
Then, connect your phone to the computer, start your phone in fastboot mode (not Hboot or serial, if you see serial or Hboot on your screen then tap return button)
In command line type
Code:
fastboot devices
to make sure that you're connected
then type
Code:
cd desktop
your directory should change to something like C:\user\desktop (make SURE there are no spaces anywhere in user name, fastboot has problem with that. I had to rename my account to "EugeneAndLiz"a from "Eugene and Liza" because of that)
then type
Code:
fastboot recovery rec.img
fastboot reboot
and let us know how did it go for you. I'l be lurking around here for a while, hopefully we can resolve this.
Good luck
borodin1 said:
Not sure, I'm not anywhere near my computer. Try putting your recovery image into different locations (i always put it on desktop) and rename it to something simpler, without any punctuation or special characters (i suggest rec.img). Also... make absolutely sure that you're NOT naming it rec.img.img . Make sure that your PC is not hiding your extensions.
Then, connect your phone to the computer, start your phone in fastboot mode (not Hboot or serial, if you see serial or Hboot on your screen then tap return button)
In command line type
Code:
fastboot devices
to make sure that you're connected
then type
Code:
cd desktop
your directory should change to something like C:\user\desktop (make SURE there are no spaces anywhere in user name, fastboot has problem with that. I had to rename my account to "EugeneAndLiz"a from "Eugene and Liza" because of that)
then type
Code:
fastboot recovery rec.img
fastboot reboot
and let us know how did it go for you. I'l be lurking around here for a while, hopefully we can resolve this.
Good luck
Click to expand...
Click to collapse
im going to tell you step by step what i do
turn the phone off
hold power and back
i see the androids on skateboards and it says fastboot in red letters
i connect my phone via usb then the name changes to fastboot usb
run the cmd
once there i type where adb is located which is cd C:\android-sdk-windows\tools
then when i type fastboot devices
i see the serial number of my phone
now when i type cd desktop i get this message "the system cannot find the path specified"
and if i ignore that and try to flash
fastboot flash recovery rec.img (yes i did rename the recovery image)
it says that it cant load 'rec.img'
Got it! Put your image file into the "tools' folder and once you see your device in the fastboot just flash it from there
Code:
cmd
cd C:\android-sdk-windows\tools
fastboot devices
fastboot flash recovery rec.img
fastboot reboot
Sorry about all this complication... the main idea is that your recovery needs to be in the same directory as you're when you're flashing. So if earlier you went to tools folder then your file needs to be there as well.
Try it out.
it worked...it said sending 'recovery' <4456 KB>... okay
writting 'recovery'...okay
fastboot reboot
then when i go to the system recovery..its the same htc adp one
i tried to flash amon ra's recovery and cyanogens
oh nevermind..instead of rebooting the phone i just unpluged the device and wnet directly into the system recovery and YES i have cyanogens recovery thank you so much borodin1
hmmmm that's weird because you got confirmation....
1. Did you download right recovery? You had to becaue you tried 2 of them and you can only make the same mistake once lol
2. AmonRA's recovery has the same image in the background as HTCs, are you sure that it's still HTC's recovery?
Other then that... I'm clueless
Can you get su in the adb shell? Try flashing it from adb....
You got me stomped on this.... Anyone else wants to take a shot at this????
i dont know what happened but when i flashed the recovery image on fastboot and then rebooted the phone...then turn off the phone and went to the system recovery and the htc adp recovery appeared...blue letters and the scrolling options..but when i did not reboot the phone after flashing the image and went directly to the system recovery i had the recovery i flashed...then i applyed the updateand everything is good now
weird uh?
will that new recovery stick?... I'm starting to remember something but it's vague... give me few minutes Reboot couple of times into recovery and back for now and see what happens...
it did stick..i just rebooted into recovery and i have the new recovery..haha
Great! Happy modding!
Well, long story short my friend royally screwed up his phone.
He screwed up the kernel and even the Recovery. Don't ask how.
We even connected the phone and ADB didn't work on bootloader. But after we went into fastboot and tried a restart it worked. So.. we used fastboot to restore the phone.
Notes before you start: Use command prompt and cd to the directory for your sdk tools. In my case, I simply used the 'data' folder for the Toolkit that was released here that had the sdk tools like adb.exe and fastboot.exe . MAKE SURE you copy the associated recovery zips and ROM zips to the very same folder to prevent complications and for the commands to work like a charm. Finally, uninstall the drivers for your phone and reinstall them (if you need to only, as we had connection issues.. yep he royally screwed up).
Boot into bootloader then select fastboot and hit the power button. Keep it on the fastboot screen. Now you can proceed.
Here is what I did:
fastboot erase cache
fastboot flash recovery recovery.zip *rename your recovery zip to 'recovery.zip' and make sure it's in the same folder as the sdk tools*
You can now then boot into recovery and write the ROM or even use fastboot to write it with the following:
fastboot flash zip rom.zip *once again, rename your ROM zip to rom.zip*
I only put this out there to help those who screwed up their recovery and can't even get the Toolkit to execute commands using ADB.
Good luck!
Yeah, fastboot on pc then in command you clear cache and install recovery. I got into a boot cycle and this fixed it.
lopuandroid said:
Yeah, fastboot on pc then in command you clear cache and install recovery. I got into a boot cycle and this fixed it.
Click to expand...
Click to collapse
Glad it worked. Yeah, for some reason my friend's computer was being really fussy. It wouldn't detect the phone or anything, and ADB was rendered useless. We reinstalled the drivers so many times.. And used 2 different laptops.. Thank God fastboot worked. Hopefully this helps anyone else in the same **** zone. I know the heart sinking feel when your Recovery won't work and you only get the bootloader to work..
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.