Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot
parakleet said:
Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot
Click to expand...
Click to collapse
No offence but i am lost by what you said, I am trying to get back to completely stock. Is part of my issue the fact that command prompt didn't detect my device? or no?
I'm not exactly sure what to do with the information you shared, sorry
I the tutorial i found it says to make sure the command prompt sees your device but doesnt say what to do when it doesnt see it.
Also, I downloaded the may factory image, i believe it was version O
Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble
jreink01 said:
Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble
Click to expand...
Click to collapse
If you did not get your phone from Verizon use this
7.1.2 (N2G47O, May 2017)
Download the zip
unpack all the zip files some are nested so unzipping one creates more keep unzipping until there are no more then gather the following img files
bootloader.img
radio.img
boot.img
system.img
system_other.img
vendor.img
modem.img
Some of those names are cut down as i hate typing long strings, jsut rename them as such.
Create a folder on root of c:\_PIXEL_XL_
put all the files there.
You will use way less files than you unpacked
once you have done that run the following commands
copy and paste
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
After last reboot just wait and you will be back at stock
if that doesnt work
Download latest version of TWRP place it in C:\_PIXEL_XL_
rename it twrp.img, again i hate typing long strings
from bootloader run
fastboot boot c:\_PIXEL_XL_\twrp.img
This will take you into twrp
you might need to wipe system and cache and data,
From memory the fourth entry at bottom is internal memory or user data, in any event if you do not check that your data stays on the phone.
Once you have wiped the other 3 rerun the fastboot commands and you will be back at stock
add the twrp and supersu commands from earlier to add root.
dont forget the signatureverify.img if you are doing that.
good luck.
you arent bricked
you just need to find the correct combination of steps to get your phone where you want it to be
Thanks for the response. I am having a hard time with this, the zip file i downloaded from the google website, when i open it, there are only 6 files, 1 of which is a zip file (marlin). When I open marlin it shows a bunch of files, none of which you mentioned. I am confused, was wondering if you would be nice enough to walk me through this over the phone, i would be really grateful.
Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!
jreink01 said:
Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!
Click to expand...
Click to collapse
Yes, i sent you a PM.
HALV0RS3N said:
Yes, i sent you a PM.
Click to expand...
Click to collapse
thanks, sent you my #
Okay so I had the exact problem yesterday. To to the Google developers site and download the official Google pixel or xl 7.1.2 nougut ota update. Once that's downloaded, go to your phone, I had all the exact same screens on my phone so it should work. Hold down the power button until it completely shuts down. Then hold the power and volume down to go to recovery mode, if it goes back to the ext 4 screen, try it again until it goes to recovery mode, then on command prompt type, fastboot boot twrp.img then once it's in twrp, go to advanced-then adb sideload and click both boxed and then swipe to enter sideload. Then on your computer, type adb sideload "file name for Google update" and hit enter. That should do the trick. Like I said, I had the exact same problem yesterday
---------- Post added at 06:56 PM ---------- Previous post was at 06:50 PM ----------
Also, I forgot to mention, download the twrp image file from the Internet. Shouldn't be hard to find just make sure it's the latest. Put that file in the adb file on your computer same with the Google update for your phone. Do not unzip either file. That's very important. DO NOT UNZIP THE UPDATE File. When you type in the twrp.img make sure you type img. And when you flash the update, make sure at the end of the file name you put
.zip ex( marlinpixelxl7.1.2.zip)
jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
Looking at your screen shot you didn't let the file finish flashing. It sticks at the "does not contain" for a bit before it continues.
You were doing it right. You just didn't wait.
If it wasn't going to work it would eventually give you a failure and jump to the command prompt.
jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.
RedBlueGreen said:
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.
Click to expand...
Click to collapse
OP was flashing to stock. Didn't let it finish though.
Related
Guys let me put this disclaimer out there, this is not my first Android device and neither my first time tinkering or modding it. I've rooted three android devices prior to this.
I upgraded from a Droid Incredible this weekend to Galaxy Nexus on Verizon and finally thought of rooting and flashing a kernel to the phone today since battery life is horrendous. I download the Rootkit that is on the forums here and went through the procedure as laid out in the thread. After unlocking the bootloader and flashing root, the phone hangs on google boot screen. I am fearing that i have bricked the phone. Does anybody else have suggestions on what should i do here? I've never had a problem with rooting a device before.
This is why I always do mines manually. It's better to do it that way and not take the faster route because you get a idea what's going on.
Is your bootloader unlocked? did that successfully work? When you turn your phone on on the bottom center.. is there a lock there?
It's not bricked. Put the phone in fastboot and flash the galaxy nexus image files to it. No big deal.
mysterioustko said:
It's not bricked. Put the phone in fastboot and flash the galaxy nexus image files to it. No big deal.
Click to expand...
Click to collapse
Exactly what I was going to say. +1
fastboot oem lock
fastboot oem unlock
Bricking this phone is nearly impossible, we have fastboot, and even Odin for when things really go to hell.
Restore to stock and start again! You should always keep these images around anyway in case you get stuck at any stage.
1) Grab the latest image for your type of phone from google:
http://code.google.com/android/nexus/images.html
2) Unzip the file and its contents into your SDK/Tools folder (wherever your adb.exe and fastboot.exe files are).
3) From within your Tools folder, open a command prompt (SHIFT + right click – “open command prompt here”) / OR open a command prompt and CD to the folder.
4) Type the following commands, allowing each to finish before moving onto the next:
adb reboot bootloader
fastboot flash bootloader bootloader-<varies>.img
fastboot reboot-bootloader
fastboot flash radio radio-<varies>.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-<varies>.img
fastboot reboot-bootloader
fastboot -w update image-<varies>.zip
fastboot reboot-bootloader
Remember the exact image name will vary depending on which version you use. Also if you have the GSM version you won't have radio-cdma etc.
There's other guide that are specific to GSM or CDMA/LTE version if you need exact filenames.
You guys are awesome! I was able to get it back to Stock Google. Thanks a lot fellas .
what would the command prompts be for a mac user?
silverado9502 said:
what would the command prompts be for a mac user?
Click to expand...
Click to collapse
where ever you see:
fastboot ...
do
./fastboot ...
ok so im on a mac and really not too familiar with the locations for things so im tryng to figure out what to, i can get to fastboot and recovery, somehow i lost my backup and the rom that i have isnt installing, i already wiped all data and now it only reboots to the google splash screen with the lock pad unlocked. what do i need to do exactly i may need a walk through unless what is on previous posts is what i need to do?
I am not a noob when it comes to android dev, but this has stomped me and I am asking for expert's help. I have a GSM version SGN that I flashed the official yakju ICL53F on it via fastboot. It has been working great for a month now. Suddenly today I felt it was vibrating in my pocket, took it out and discover it was stuck in boot loop--the google sign with the unlocked icon. I waited til I get home to put clockworkmod on it, but when I try to nandroid it first it gave me an error. Then I figure I would just fastboot the stock rom on it again, using fastboot mode like I did before. I even flashed the bootloader, radio, and system image. Still stuck on google icon with screen went blank, vibrate and repeat. Is there anything else I should try? odin mode is also available, but I am not seeing any instructions on it at the developer section so I am reluctuant to try it. I can still adb and fastboot to access my phone...help please?
well I am no noob but I am no expert either. Apparently you cannot
fastboot flash system XXXXstock_image.img, you have to use
fastboot update -w XXXstock_image.img instead.
still I am baffled by why this happened in the first place. I was ready to lock the bootloader back up and send it in for warranty...glad I didn't have to resort to that.
lettcco said:
well I am no noob but I am no expert either. Apparently you cannot
fastboot flash system XXXXstock_image.img, you have to use
fastboot update -w XXXstock_image.img instead.
still I am baffled by why this happened in the first place. I was ready to lock the bootloader back up and send it in for warranty...glad I didn't have to resort to that.
Click to expand...
Click to collapse
I think you are mixing some things up.
The "update" parameter of fastboot is used to flash a group of images inside a zip file to you device.
The "flash" parameter is used to flash a single image to your device.
The following two groups of commands do the same thing:
fastboot update -w image-yakju-icl513f.zip
or
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot erase cache
I have a GSM Galaxy nexus that boots into fastboot and odin but when ever i flash stock or go into recovery it gets stuck on that dreaded google bootlogo . I have literaly tried everything and that google logo is not leaving !!
Try reverting everything back to stock using [GNex TOOLKIT V6.1]
http://forum.xda-developers.com/showthread.php?t=1392310
eliasgkphoto said:
Try reverting everything back to stock using [GNex TOOLKIT V6.1]
http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
I've already tries reverting back to stock and after its done it just immediately goes to the google screen and stays that way
You should try to flash the stock images manually in fastboot if you haven't done so already. I'm not a fan of Toolkits.
Download the stock files: https://developers.google.com/android/nexus/images#yakju
You must extract the .tgz file first and then extract the .tar file inside.
Navigate the folder until you see the radio bootloader and factory image.
Put those three files in the folder on your computer where you have fastboot.exe
Boot into the bootloader.
Type fastboot devices - to make sure your phone is connected.
Then these commands.
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot bootloader
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot bootloader
fastboot -w update image-yakju-imm76i.zip
Hopefully it will boot
Still nothing
El Daddy said:
You should try to flash the stock images manually in fastboot if you haven't done so already. I'm not a fan of Toolkits.
Download the stock files: https://developers.google.com/android/nexus/images#yakju
You must extract the .tgz file first and then extract the .tar file inside.
Navigate the folder until you see the radio bootloader and factory image.
Put those three files in the folder on your computer where you have fastboot.exe
Boot into the bootloader.
Type fastboot devices - to make sure your phone is connected.
Then these commands.
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot bootloader
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot bootloader
fastboot -w update image-yakju-imm76i.zip
Hopefully it will boot
Click to expand...
Click to collapse
I tried it and it didn't work. I also noticed that on the bottom of the gnex it says "fastboot command read error -2147483647" any ideas? I am officially clueless. I am offering 20 dollars to anyone who can fix this
i have found ABSOLUTELY NOTHING regarding this "FASTBOOT COMMAND READ ERROR -2147483647" that can actually fix it. everything from flashing stock via odin, uninstall and reinstall sdk, differnt usb cables, ubuntu 12.04 and win7. seems to no fix...please help. this started after flashing koush JB update via rom manager
Same thing for me but its stuck at the boot animation and it just started
Have completed rumrunner root for htc one.
Have installed twrp through adb using command prompt.
Then when trying to reboot system it boots up in recovery.
Need help to find out how to get back on my phone.
Have found similar sites with information but not clear enough for me to understand
I'm able to access twrp so i would assume it's a mount of the sd card but i am not seeing that option anywhere
twrp v 2.6.3.0
I know it's late guys thanks for your help!
if you ever get this issue please understand that there are websites out there that are making you use "fastboot flash boot blah.img" which is making you flash recovery on top of your boot img. please understand that you have overwritten something that is necessary for your phone to work so just open a rom you are preparing to flash and unzip. Copy the boot.img from the unzipped folder and move it to your fastboot folder where your going to open command prompt.
after you open command prompt in the same folder as your adb/fastboot/ and such using shift right click
you then type in the command prompt "fastboot flash boot boot.img" that should flash the boot image back and you should be able to turn on your phone.... wow that took a lot of stress but figured it out in the end. JUST HAD TO GET A GRIP! now happy flashing thanks!
kiit408 said:
if you ever get this issue please understand that there are websites out there that are making you use "fastboot flash boot blah.img" which is making you flash recovery on top of your boot img.
Click to expand...
Click to collapse
Either the tutorial was completely written wrong, or you read them wrong. There's no way of telling which happened, but the point is to be very careful with fastboot.
The command "fastboot flash boot file.img" doesn't flash recovery in your boot partition unless you mis-labeled your .img file and flashed the wrong file in the wrong place.
Most people modding their phones are going to be using fasboot to flash to boot, recovery, system, or bootloader. It's important to understand all of the places that fastboot can flash before you start pushing in .img files. Understanding fastboot commands can also help you possibly identify if someone made a typo in their guides.
Want to put in recovery? "fastboot flash recovery recovery.img". Want to put in a new kernel? "fastboot flash boot boot.img", and so on. Ensure that you've got files that are properly named and you won't ever have to worry about flashing the wrong thing in the wrong place.
kiit408 said:
if you ever get this issue please understand that there are websites out there that are making you use "fastboot flash boot blah.img" which is making you flash recovery on top of your boot img. please understand that you have overwritten something that is necessary for your phone to work so just open a rom you are preparing to flash and unzip. Copy the boot.img from the unzipped folder and move it to your fastboot folder where your going to open command prompt.
after you open command prompt in the same folder as your adb/fastboot/ and such using shift right click
you then type in the command prompt "fastboot flash boot boot.img" that should flash the boot image back and you should be able to turn on your phone.... wow that took a lot of stress but figured it out in the end. JUST HAD TO GET A GRIP! now happy flashing thanks!
Click to expand...
Click to collapse
Jjust understand what you're flashing, you can't 100% trust a tutorial..
If you do the command, fastboot flash boot boot.img, you BEST DAMN be sure that is a kernel/boot.img you are flashing and make sure your working is right, if you fastboot flash a boot.img to say recovery.img, you are screwed.
make sure the file is right my MD5, also make sure the tutorial is good, messing with ANYTHING in fastboot is dangerous.
This is for the people [myself earlier] who cannot boot into Android (bootloop or worse), have no download mode, no recovery and can only boot into Fastboot. Download the file below, I have included fastboot (for windows) and the appropriate files to flash, all you have to do is run the commands in order below, then boot into download mode.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
It is best to use the CMD.exe file in the folder provided so you will already be running the commands from that folder without having to change directories. If you're on Linux then make sure you have Fastboot installed then run Terminal from the folder and run the same commands. This will restore the STOCK download mode and recovery partitions not TWRP or CWM.
Download Here
Artifesto said:
This is for the people [myself earlier] who cannot boot into Android (bootloop or worse), have no download mode, no recovery and can only boot into Fastboot. Download the file below, I have included fastboot (for windows) and the appropriate files to flash, all you have to do is run the commands in order below, then boot into download mode.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
It is best to use the CMD.exe file in the folder provided so you will already be running the commands from that folder without having to change directories. If you're on Linux then make sure you have Fastboot installed then run Terminal from the folder and run the same commands. This will restore the STOCK download mode and recovery partitions not TWRP or CWM.
Download Here
Click to expand...
Click to collapse
How would one go about repairing a broken download mode when all I can do is boot into a broken recovery? I cannot issue any fastboot commands as the device is only recognized as an ADB Bridge device. Are there ADB equivalent commands to accomplish the same things as you have detailed here?
SPRINT LS980 (was on Rooted Stock C and borked phone with D OTA) and a broken TWRP 2.7.1.0 Recovery
natefuhr said:
How would one go about repairing a broken download mode when all I can do is boot into a broken recovery? I cannot issue any fastboot commands as the device is only recognized as an ADB Bridge device. Are there ADB equivalent commands to accomplish the same things as you have detailed here?
SPRINT LS980 (was on Rooted Stock C and borked phone with D OTA) and a broken TWRP 2.7.1.0 Recovery
Click to expand...
Click to collapse
well you should never install any OTA with a custom recovery install. you should always keep at least one backup on your phone to restore to in these events. but i would try downloading a rom and installing via sideload before nuking any partitions. which is easy with TWRP. the sideload menu should be in Advanced then ADB Sideload and the command is adb sideload filename.zip and it will take awhile depending on the file size. make sure the file name is simple and it is placed in the folder you are running the sideload from.
Artifesto said:
well you should never install any OTA with a custom recovery install. you should always keep at least one backup on your phone to restore to in these events. but i would try downloading a rom and installing via sideload before nuking any partitions. which is easy with TWRP. the sideload menu should be in Advanced then ADB Sideload and the command is adb sideload filename.zip and it will take awhile depending on the file size. make sure the file name is simple and it is placed in the folder you are running the sideload from.
Click to expand...
Click to collapse
Yes yes I know... it was a moment of weakness late at night and I didn't think before telling the girl to go ahead and upgrade. That being said... Part of the problem now is that the one backup she made just up and disappeared. The ADB sideload option just hangs and never actually does anything. The original Stock Rooted file I had still on the sd partition doesn't fix the issue when I flash it... it looks like it flashes ok but on the next boot it just drops me back into TWRP right where I began. And download mode is still borked.
So let's talk thermonuclear resolution on this motherlover.... where do I begin?
Sent from my SM-N900P using Tapatalk
natefuhr said:
Yes yes I know... it was a moment of weakness late at night and I didn't think before telling the girl to go ahead and upgrade. That being said... Part of the problem now is that the one backup she made just up and disappeared. The ADB sideload option just hangs and never actually does anything. The original Stock Rooted file I had still on the sd partition doesn't fix the issue when I flash it... it looks like it flashes ok but on the next boot it just drops me back into TWRP right where I began. And download mode is still borked.
So let's talk thermonuclear resolution on this motherlover.... where do I begin?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
hmmmmm.... I've been able to get my G2 into fastboot by holding Volume + and Pwr after it setting for awhile turned off.. may be stupid but have you tried that button combo or Volume + and Volume - with Pwr
Could u tell me the command cause i went adb sideload filename.zip and it comes up file not found and i put it in my platform-tools folder any ideas i have adb version 1.30...it was above the version that they said you need on the twrp site
whatsamatta u alumni 1990-2011
Fastboot???
Artifesto said:
This is for the people [myself earlier] who cannot boot into Android (bootloop or worse), have no download mode, no recovery and can only boot into Fastboot. Download the file below, I have included fastboot (for windows) and the appropriate files to flash, all you have to do is run the commands in order below, then boot into download mode.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
It is best to use the CMD.exe file in the folder provided so you will already be running the commands from that folder without having to change directories. If you're on Linux then make sure you have Fastboot installed then run Terminal from the folder and run the same commands. This will restore the STOCK download mode and recovery partitions not TWRP or CWM.
Download Here
Click to expand...
Click to collapse
How do I get to fastboot. I can get to recovery but that's it. Download is not working. The Vol+/- and Power just gets me to key controls.
deathsquad737 said:
Could u tell me the command cause i went adb sideload filename.zip and it comes up file not found and i put it in my platform-tools folder any ideas i have adb version 1.30...it was above the version that they said you need on the twrp site
whatsamatta u alumni 1990-2011
Click to expand...
Click to collapse
i would try to rename your rom to something simple, like rom.zip. there cannot be any spaces in the name and it does need to be in the same folder you run the command from like you seem to be doing.
gelito81 said:
How do I get to fastboot. I can get to recovery but that's it. Download is not working. The Vol+/- and Power just gets me to key controls.
Click to expand...
Click to collapse
did you try vol+ and power together? When a functioning rom is installed it asks to do a factory reset but it may get into fastboot if you nuked that partition. i haven't tried this yet but if you're in adb sideload in twrp maybe the command
Code:
adb reboot fastboot
might help
Artifesto said:
i would try to rename your rom to something simple, like rom.zip. there cannot be any spaces in the name and it does need to be in the same folder you run the command from like you seem to be doing.
did you try vol+ and power together? When a functioning rom is installed it asks to do a factory reset but it may get into fastboot if you nuked that partition. i haven't tried this yet but if you're in adb sideload in twrp maybe the command
Code:
adb reboot fastboot
might help
Click to expand...
Click to collapse
Tried all of the above.... they all just send me into recovery or broken download mode
damn
I'm screwed. I gave this a try and now all I get is a black screen. The phone will connect to my computer but I can't send any commands to it through the command prompt. When it connects to the computer it opens a bunch of different drives and says I need to format them. I can't get into download mode and when I try to send a command in the prompt it just says waiting for device. Any ideas?
Edit: It shows up in device manager like this: http://i.imgur.com/NXGxpcX.png
http://forum.xda-developers.com/showthread.php?t=2582142 try that
Sent from my VS980 4G using XDA Free mobile app
how i can enter in FASTBOOT mode ?
I'm not sure if you can help me here. I have a Verizon G2 and am trying to reset to factory for a repair. I am trying to get into download mode, but only get fastboot when pressing volume up while powered off and plugging in my USB cord. Any help would be greatly appreciated.
razer_ins said:
how i can enter in FASTBOOT mode ?
Click to expand...
Click to collapse
Flash xdabbbeb 24a bootstack zip
WHATSAMATTA U ALUMNI
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
Crossxcalibur said:
I'm not sure if you can help me here. I have a Verizon G2 and am trying to reset to factory for a repair. I am trying to get into download mode, but only get fastboot when pressing volume up while powered off and plugging in my USB cord. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Read 2 post above yours i answered your ?
WHATSAMATTA U ALUMNI
For everyone who is having issues with drivers see the video below to get fastboot to work:
https://www.youtube.com/watch?v=NaK5OxUeDKM