Related
Let me start by saying yes i'm fully rooted, ok now with that outta the way, im trying to a load new splash screen as explained here http://forum.xda-developers.com/showthread.php?t=722717, but the issue i'm having is where he say "Boot your phone into fastboot (hold vol up key while powering phone on, select fastboot)", shouldn't it be power and volume down, also when i go to cmd to type" fastboot devices" to see if the computer is recognizing my phone my first command line that comes up says C:\Documnents and Setting\Tom Harman>, i have a filling that should not be there, but either way it's not showing it's connected, should i have the phone set to charge only, or disk drive or what am i not doing right.
39 views, come one some has got to have something, searching has turned up no good results.
You check with this line.. adb devices. Will have a bunch of numbers and if it does your all good.
Sent from my PC36100 using XDA App
see i can't even get there since my first cmd line is C:\Documnents and Setting\Tom Harman>, i put in fastboot device, and it says not a internal or external command.
Boot the phone with volume up and it should bring you to a white screen with info about your phone. Select fastboot from the menu. When it talks about cmd, use windows explorer to navigate to the Android SDK folder on your computer. Find the tools folder and highlight the folder name and hold shift then right click and select open new command window here. Then type fastboot devices in the cmd window.
nukedukem said:
Boot the phone with volume up and it should bring you to a white screen with info about your phone. Select fastboot from the menu. When it talks about cmd, use windows explorer to navigate to the Android SDK folder on your computer. Find the tools folder and highlight the folder name and hold shift then right click and select open new command window here. Then type fastboot devices in the cmd window.
Click to expand...
Click to collapse
when i try this way of holding power and vol up, it buzz's 3 times and does nothing, then i have to pull battery just to start over, but if i hold power and vol down i can select fastboot, and it takes me to the red highlighted fastboot usb, but nothing about cmd.
You must navigate to the android-sdk-windows\tools folder. The path can be different for everyone. The location is where you extracted the android sdk to. Mine is at the root of the C drive.
Make sure USB debugging in Settings/Applications/Development is turned on and reboot into the bootloader (power+vol down)
Type this:
cd C:\android-sdk-windows\tools press enter
(The path you just typed should be displayed here)
Now type: fastboot devices
This should display something like HTxxxxxxxxxxxxxx
If it does, it worked. Just type your commands to flash the splash image.
Hope this helps
That's strange, did you flash an eng hboot? How did you root?
tomh1979 said:
when i try this way of holding power and vol up, it buzz's 3 times and does nothing, then i have to pull battery just to start over, but if i hold power and vol down i can select fastboot, and it takes me to the red highlighted fastboot usb, but nothing about cmd.
Click to expand...
Click to collapse
Thats referring to the command prompt terminal on your computer
dglowe343 said:
You must navigate to the android-sdk-windows\tools folder. The path can be different for everyone. The location is where you extracted the android sdk to. Mine is at the root of the C drive.
Make sure USB debugging in Settings/Applications/Development is turned on and reboot into the bootloader (power+vol down)
Type this:
cd C:\android-sdk-windows\tools press enter
(The path you just typed should be displayed here)
Now type: fastboot devices
This should display something like HTxxxxxxxxxxxxxx
If it does, it worked. Just type your commands to flash the splash image.
Hope this helps
Click to expand...
Click to collapse
that's the first time it confirmed my device, but it failed to flash, says remote not allowed.
nukedukem said:
Boot the phone with volume up and it should bring you to a white screen with info about your phone. Select fastboot from the menu. When it talks about cmd, use windows explorer to navigate to the Android SDK folder on your computer. Find the tools folder and highlight the folder name and hold shift then right click and select open new command window here. Then type fastboot devices in the cmd window.
Click to expand...
Click to collapse
i just followed what you said and held the UP VOLUME KEY and the power button at the same time, my phone vibrated 3 times, n now wont charge, or turn on, or work with volume down n power button... thanks a lot for the misleading info
nukedukem said:
That's strange, did you flash an eng hboot? How did you root?
Click to expand...
Click to collapse
the only way you could root the ota 2.2, which i have been able to do everything else from change roms, load boot animations, just can't do this, lol.
vikramjatt11 said:
i just followed what you said and held the UP VOLUME KEY and the power button at the same time, my phone vibrated 3 times, n now wont charge, or turn on, or work with volume down n power button... thanks a lot for the misleading info
Click to expand...
Click to collapse
just pull the battery, it'll be ok, i did that a few times too, lol.
If you power up the phone with the volume up held it should boot into fastboot. I was wrong about selecting fastboot earlier, I thought you had to select it, but it will boot directly into fastboot.
IDK how the 2.2 root is done, it sounds like you don't have an eng bootloader.
http://forum.xda-developers.com/showthread.php?t=752832&highlight=engineering+hboot
found the problem, it lies in the hboot, should be .76, but is .79, time to revert.
I have been searching and reading, but I still am unsure of which rooting method I should use. I just got my "new" EVO on Friday. Here are my specs:
HBoot 2.2
Hardware 0003
Baseband 2.15.00.09.01
Kernal [email protected]#17
Software 3.30.651.3
Any and all help would be greatly appreciated.
You have two choices:
option 1. Follow the directions and root your phone using these instructions that I copied from the thread below and use the following link to download the correct files: (http://forum.xda-developers.com/showthread.php?t=829045)
option 1 is not recommended for a noob...
option 2. Wait for unrevoked to come out with their update to unrevoked 3. If you wait, almost all of the root process will be automated. Unrevoked should be releasing this update in the next couple of weeks or so. They have been tweeting about it.
Directions from option 1 copied from thread link above:
1. Make sure that you downloaded and installed HTC Sync from HTC website.
2. Unzip hboot202-s_off-V71.zip to a folder in your C: drive. I used C:\hroot
3. This hroot folder should have a folder inside it called root. If you have a folder called hboot202-s_off-V71 then you need to move all the files from that subfolder to c:\hroot.
4. In Vista/7 slick on the start button and type in cmd. You will see in the program list the command prompt. Right click and open as Administrator.
5. In the command prompt type cd c:\hroot
6. On phone goto-> Setting>Applications>Debugging make sure usb debugging is on.
7. Connect the usb cable to your computer and phone. The phone should change it's screen to ask you what type of connection mode you want. Make sure that it is on charge only. Do not mount.
8. Type into the command prompt: adb push root/unrevoked-forever.zip /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
9. Type into the command prompt: adb push root/mtd-eng.img /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
10. Type into the command prompt: adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
11. Type into the command prompt: adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
12. Type into the command prompt: adb push root/flash_image /data/local/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
13. Type into the command prompt: adb push root/rageagainstthecage /data/local/tmp After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
14. Type into the command prompt:adb shell You should see a $, this means that you are "in" the phone.
15. Type into the command prompt:chmod 0755 /data/local/tmp/rageagainstthecage You should see this echoed on your screen. This is normal. You should still have $ on your cmd line.
16. Type into the command prompt: chmod 0755 /data/local/flash_image You should see this echoed on your screen. This is normal. You should still have a $ on your cmd line.
17. Type into the command prompt:./data/local/tmp/rageagainstthecage A message will pop up on the screen. It will take a few seconds, and your will be kicked "out" of the phone. The $ should now be gone.
18. Type into the command prompt: adb shell You should have a # on your command line instead of a $. # means you have temporary root in your phone. If you do not have #, then start over.
19. Type into the command prompt that has #: ./data/local/flash_image misc /sdcard/mtd-eng.img
20. Type into the command prompt that has #: sync
21. Type into the command prompt that has #: reboot bootloader
22. Your phone will be rebooting now. Eventually your phone will be at the bootloader menu. On your phone use volume up/down to highlight bootloader and press the power button once. It will start loading the PC36img.zip file.
23.After it loads, it will ask if you want to flash. Press Volume UP to say yes. It will now flash, which can take some time. You may see some red fail messages. This is normal.
24.When it is done flashing it will ask you if you want to reboot. Press Volume Down to say now to reboot.
25. Use volume up/down to highlight recovery. Press the power button once. This will try to boot into recovery mode but fail and load a screen with a red triangle. This is normal because you have not installed recovery yet.
26. Go back to your computer screen and your command prompt. You should not have a #
27. Type into the command prompt: adb push recovery /
28. Type into the command prompt: adb shell busybox --install /sbin
29. Type into the command prompt: adb shell nohup /sbin/recovery &
30. After a pause you should see a new screen on your phone. It should be green text with your recovery options.
31. Highlight backup/restore. Press the power button. Highlight backup nand and press the power button. Press the power button again to confirm the action. Your phone is now doing a nandroid backup. This will backup your wimax keys amongst other things.
32. It will take a little time to do the backup. After it is done press the power button once to return to the recovery menu.
33. Highlight enable USB-MS and press the power button.
34. On your computer, you should see a new drive in my computer or a pop up asking you for an action. Click on Explore, or open the drive in my computer, to access your phone like you would a thumb drive.
35. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip
36. On your phone, press the power button to disable USB-MS mode. You should be back at the recovery menu.
37. Highlight the option to flash image from zip. Press the power button.
38. Highlight unrevoked-forever.zip and press the power button. Press the power button again to confirm if told to do so.
39. When it completes flashing the image, select reboot from the menu.
40. When it reboots a few things could happen. If you think your phone is frozen, you are okay because that is a normal occurrence on this step.
----->Your phone gets "stuck" on a white screen with the word HTC on it for more than a minute. You need to take the back case off your phone and pull your battery out. Put the battery back in and put the back case on again. Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->You phone started up and fully booted. You need to completely power off.Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->The phone returns to the boot loader.
41. No matter which of the 3 scenarios occurred to you in the last step, you are now in the boot loader. Obviously the 3rd scenario is the best, but all are OKAY.
42. The phone should find PC36img.zip. It then loads this file and asks if you want to flash. Use volume up for yes. When it asks to reboot press volume up for yes.
43. When it is done booting, return to your computer screen and type adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip into the command prompt.
44. Type into the command prompt: adb reboot recovery
45. Highlight backup/restore in recovery and then press power. Highlight backup nand and press power. Press power again to confirm. Wait for the backup to complete.
46. Press power to return to recovery menu. Highlight reboot phone and press power.
47. Your phone is now rooted, S-OFF, and booted into stock 3.30.651.2.
-------------------------------------------------------------------------
After Root:
1. Run through setup and get to the actual phone screens.
2. Try to turn on 4G/wifi/etc and see if it all works. It may not and this does not mean disaster.
For me, I had to flash Stock RUU root 3.30.651.3 to get 4G to work. Here is what I did next:
1. Download stock RUU root 3.30.651.3(I opted for Odexed version) from http://forum.xda-developers.com/showthread.php?t=836728
2. Reboot phone into recovery by completely powering off. Hold down volume down and press power. When you get into the boot loader it will try to find PC36img.zip and fail (we renamed that file remember?) and that is normal. Use volume up/down to highlight recovery and press the power button.
3. In recovery highlight USB-MS and press power to enable.
4. Your phone should be mounted as a drive in your computer again like before. Copy the whole zip file that you downloaded for RUU 3.30.651.3 rooted odexed to your phone. Wait for it to finish the transfer.
5. On your phone press power to turn off USB-MS mode.
6. On the recovery menu highlight wipe and press power.
7. Highlight the first wipe option which is something like wipe cache/factory reset. Press power. Press power again to confirm if needed.
8. Hightlight the second wipe option which is wipe cache. Press power and then press power again if needed.
9. Highlight the third wipe option which is wipe dalvik-cache. Press power and then press power again if needed.
10. Return recovery menu.
11. Hightlight flash image from zip and press power.
12. Highlight the file that you just transfered over that is for RUU 3.30.651.3 and press power. Press power again to confirm if asked. It will start flashing the image to your phone, but you will not see progress bars. It will take a few minutes.
13. When it is complete select the option to reboot the phone.
14. The phone should fully boot up into the stock rooted 3.30.651.3 rom.
15. Now try to turn 4G/wifi/etc on and make sure it works. It did for me.
16. Assuming that everything is working fine, fully power off, boot into recovery, and do another backup. This newest backup is your holy grail backup. It is stock rooted S-OFF and 4G working backup.
Note: these last 15 steps can be used to flash any custom rom too. Just make sure that you get your "holy grail" backup first before you experiment.
GOOD LUCK!
Thank you very much. I had been looking at the three different methods, I just wasn't sure which one to go with. I'm downloading the files now, but won't be able to do the thing until i get home. I had a Hero for the longest, and rooting that was pretty simple, but when I got the EVO and looked at the forum; I knew it wouldn't be quite as easy. I just wanted to be certain before I bricked my phone trying to fly blind. I'll let you know how it turns out. Thanks again, I really appreciate it.
You are welcome! I am sure you know this, but make sure you read through the thread first so you can see other hangups other people are having before you start the rooting process. If you have rooted a phone before, I am sure you can root the evo. Good luck!
Worked like a charm. 30 minutes, and I'm rooted. That went easier than I expected. Thanks again!
you are welcome...good luck with choosing a rom kernel combination. I dont flash a new rom or kernel very often (once a month) but right now i have myn 2.2 for a rom and baked battery #5 for a kernel with some setcpu profiles and it works great! I can get a full day of 10 hours of heavy usage (connected to exchange all the time) and lots of texts, web browsing etc and still have 20% battery left
I rooted my evo yesterday. I have super user and titanium backup but it still shows s-on. How do i change this. I used unrevoked.
what version is your hboot?
jay-are said:
I rooted my evo yesterday. I have super user and titanium backup but it still shows s-on. How do i change this. I used unrevoked.
Click to expand...
Click to collapse
if you still got s-on then you might need to run unrevoked forever. just go to this site.http://unrevoked.com/rootwiki/doku.php/public/forever and run the correct update.zip like you would another rom or kernel
weaselp1 said:
what version is your hboot?
Click to expand...
Click to collapse
i dunno about him. (y must i assume its a dude n not a female on these boards... tsk tsk) but i have hboot 0.97.000
I feel as if i missed my window of rooting my fone when i should of.. now theres a 1000 and 1 threads on the newer versions for newer fones.. and yes i've 'been' reading most of them.. and its all starting to stick. **and whats this i hear about the newer evo screens being more brilliant? anyways, can i follow those same directions u posted? 30 mins doesnt sound bad. even tho 30 seconds with unrevoked is pretty enticing. thanks for your time and effort. might even give u an actuall "thanks" above ur name. just seen those recently and been wanting to give em a try.
the reason i asked what version your hboot is: if you have hboot 2.02 or 2.10 you cannot use unrevoked at this current time; you must use the above method. I just wanted to make sure you had the correct hboot to use unrevoked. I have had a friend who made this mistake, and it broke his 4g and he had to get a replacement.
as far as using th above method, unless you have hboot 2.02 or 2.10, I would advise agianst it.
Sent from my PC36100 using XDA App
Some people are having trouble using unrevoked-forever on hboot 2.10 saying that their radio is not supported. Some people have not had trouble and the root worked fine. So, make sure you root before updating to the latest build.
weaselp1 said:
the reason i asked what version your hboot is: if you have hboot 2.02 or 2.10 you cannot use unrevoked at this current time; you must use the above method. I just wanted to make sure you had the correct hboot to use unrevoked. I have had a friend who made this mistake, and it broke his 4g and he had to get a replacement.
as far as using th above method, unless you have hboot 2.02 or 2.10, I would advise agianst it.
Click to expand...
Click to collapse
So with me having such an older hoot - 0.97.000, u would recommend what...?? Unrevoked? Thanks for ur time.
Yes, use the unrevoked method because of the version of hboot you have
Sent from my PC36100 using XDA App
Hi!
Is it normal to lose the ability to get into fastboot via software commands after installing CM10.1? I've tried SU and reboot bootloader - just reboots and stops at the blue KindleFire logo of TWRP. I've tried the fastboot command with the Kindle Fire turned off and disconnected and then plugging it in, and I think that still hangs at the TWRP logo (if I remember correctly). I've tried setting bootmode to 4009 using IDME, that doesn't seem to do anything.
I won't be back from military deployment for a few days, so I don't have my new factory cable to try yet. Just wondering if this is normal, and if not what can I do to fix it?
Thank you in advance,
John
NavyLCDR said:
Hi!
Is it normal to lose the ability to get into fastboot via software commands after installing CM10.1? I've tried SU and reboot bootloader - just reboots and stops at the blue KindleFire logo of TWRP. I've tried the fastboot command with the Kindle Fire turned off and disconnected and then plugging it in, and I think that still hangs at the TWRP logo (if I remember correctly). I've tried setting bootmode to 4009 using IDME, that doesn't seem to do anything.
I won't be back from military deployment for a few days, so I don't have my new factory cable to try yet. Just wondering if this is normal, and if not what can I do to fix it?
Thank you in advance,
John
Click to expand...
Click to collapse
Can it boot into TWRP?
If it can
Code:
adb reboot bootloader
This should get you into fastboot
EDIT:
I so misread the question...so you are stuck at the blue KindFire boot screen and not the TWRP boot screen right?
Thank you for your reply! Now that I have my Kindle in front of me this time:
1st: I have CM 10.2-20131015.UNOFFICIAL-otter2 loaded. Kernel is 3.0.72+. Everything works normal, and I love it, except can't get into fastboot.
Using Terminal Emulator I type in su and get the "[email protected]:/ #" prompt, so I know I have root.
I type reboot bootloader and something appears quickly in response in the terminal window that I can't read because the Kindle reboots immediately. I captured the text to a txt file and what appears is:
Reading idme data ...
Setting bootmode to 7
Writing new vars to temp area
It shows the white and orange KindleFire logo for a brief moment and then black screen. The Kindle appears to turn itself off after the brief appearance of the KindleFire white and orange logo.
The same thing happens if I do reboot bootloader using adb shell.
I can get into TWRP the normal way by pressing the power button at boot time.
I won't have access to my factory cable for a few more days, so so don't know if that works or not.
NavyLCDR said:
Thank you for your reply! Now that I have my Kindle in front of me this time:
1st: I have CM 10.2-20131015.UNOFFICIAL-otter2 loaded. Kernel is 3.0.72+. Everything works normal, and I love it, except can't get into fastboot.
Using Terminal Emulator I type in su and get the "[email protected]:/ #" prompt, so I know I have root.
I type reboot bootloader and something appears quickly in response in the terminal window that I can't read because the Kindle reboots immediately. I captured the text to a txt file and what appears is:
Reading idme data ...
Setting bootmode to 7
Writing new vars to temp area
It shows the white and orange KindleFire logo for a brief moment and then black screen. The Kindle appears to turn itself off after the brief appearance of the KindleFire white and orange logo.
The same thing happens if I do reboot bootloader using adb shell.
I can get into TWRP the normal way by pressing the power button at boot time.
I won't have access to my factory cable for a few more days, so so don't know if that works or not.
Click to expand...
Click to collapse
Make sure to turn ADB on and enable developer options by tapping "build" six times. Now plug your kF2 into a USB port and open a command prompt and type "adb reboot bootloader" with no quotes. You should enter fastboot mode. You should be able to just open a command prompt and type "fastboot" (no tablet plugged in) and see some lines of data which lets you know the path is set right.
LinearEquation said:
Make sure to turn ADB on and enable developer options by tapping "build" six times. Now plug your kF2 into a USB port and open a command prompt and type "adb reboot bootloader" with no quotes. You should enter fastboot mode. You should be able to just open a command prompt and type "fastboot" (no tablet plugged in) and see some lines of data which lets you know the path is set right.
Click to expand...
Click to collapse
adb reboot bootloader and adb reboot recovery both do the same thing - the Kindle reboots, I get the white and orange KindleFire logo for a second and it turns itself off. Press the power button and all is normal. I can get into TWRP by pressing the power key when the blue and white Kindle Fire logo is up.
NavyLCDR said:
adb reboot bootloader and adb reboot recovery both do the same thing - the Kindle reboots, I get the white and orange KindleFire logo for a second and it turns itself off. Press the power button and all is normal. I can get into TWRP by pressing the power key when the blue and white Kindle Fire logo is up.
Click to expand...
Click to collapse
No, they are not the same thing. One reboots into the bootloader and the other reboots into recovery. My comment had nothing to do with testing a reboot and everything to see if you can enter fastboot mode.
Since you have now stated you can enter TWRP, use this tutorial to push a ROM onto TWRP and then just flash it from there. http://forum.xda-developers.com/showthread.php?t=2459498
LinearEquation,
I know that adb reboot bootloader and adb reboot recovery are not the same commands and I know that they are not SUPPOSED to do the same thing. HOWEVER, on MY Kindle both commands ARE doing the same thing. And that is why I know something is wrong. Both commands on MY Kindle ARE having the same result: the Kindle reboots, I get the white and orange KindleFire logo for a second and it turns off.
Why would I want to reinstall a ROM from TWRP when I have a ROM installed? Once I press the power button, if I let it go it boots into CM 10.2 just fine or I can boot into TWRP by pressing the power button at the right time. I cannot reboot in TWRP or fastboot using software commands, and I don't even know if it is supposed to be that way, or if it is a problem.
I did not (and still don't) know if it is normal for the only way to get into fastboot is with a cable after CM 10.2 is installed (and I don't know if I can get into fastboot that way for a few more days), or if I need to reflash a bootloader file or which bootloader file I need to reflash.
I hope that clarified what my problem is.
i was trying to flash the 2.0 update to my watch. i was in command prompt and was typing in the codes then my watch rebooted into recovery i was able to get my watch back into fastboot mode but now adb isnt recognizing my device and the watch doesnt have any software on it what do i do ?!
Same for me what do I do ? Now when I turn on recovery appears for 2 sec then black screen and over and over again looks like I don't have software installed what do I do ?
I also got the same issue I clicked on recover in the bootloader as everytime I tried to run the following step: Execute the flash-all script by typing flash-all.sh or, in the case of Windows, flash-all.bat.
Set up the watch and begin testing it would just say adb does not recognise this command.
I am now stuck in a cycle of not being access the device in ADB to flash say TWRP or get it to even boot, the only thing I can do is get it back to the boot loader.
OK, so the good news is we didn't brick out watches
First thing is first you will need to get back into the watches boot-loader to do this follow the steps below:
1. Hold the power button down until the Huawei logo show's up
2.As soon as the watch vibrates let go of the power button and do one quick short press of the power button again
3. If you did this right the boot-loader should appear if not you will feel another vibration and will have to start over
Now that you are back in the Boot-loader put the watch back on the dock and plug it into your pc. Fire up ADB and fastboot minimal (Get it here: http://forum.xda-developers.com/showthread.php?t=2317790). Install this and drag the contents of the Sturgeon-nvd file you downloaded from the android site (this is the Android Wear 2.0 preview image) into the same folder that the minimal ADB is installed in like so:
http://i.imgur.com/Vw8sUo1.png
Now double click the Flash-all.bat file in the folder and you should see it processing on the ADB window.
Did you unzip the folder and placed it in the ad folder location?
Just an FYI: ADB is not what is used to flash .img files. Its fastboot. When you are in bootloader mode are you in fastboot mode and would use fastboot commands. Its normal for ADB not to see a device in fastboot mode.
Hi people,
I unlocked, rooted, and flashed Liquid on my XL tonight. Everything seemed to be going fine when I rebooted again and got a bootloop. TWRP is not loading, what I am getting is the Android on it's back menu and here's where I'm lost. I'm getting the error in the screenshots when I try to sideload the factory image from ADB. My cords are good, drivers are updated, and I have ADB and Fastboot set to Large Address Aware. I don't want to admit that I have a paperweight now. Any ideas? Thanks in Advance
elektrosoundwave said:
Hi people,
I unlocked, rooted, and flashed Liquid on my XL tonight. Everything seemed to be going fine when I rebooted again and got a bootloop. TWRP is not loading, what I am getting is the Android on it's back menu and here's where I'm lost. I'm getting the error in the screenshots when I try to sideload the factory image from ADB. My cords are good, drivers are updated, and I have ADB and Fastboot set to Large Address Aware. I don't want to admit that I have a paperweight now. Any ideas? Thanks in Advance
Click to expand...
Click to collapse
Can you reboot to download mode (fastboot)? Hold the power button and vol down buttons together.
If you can get into the bootloader, use fastboot to flash the factory image instead of using adb. Or try issuing 'adb reboot-bootloader' command to reboot to bootloader
koivth said:
Can you reboot to download mode (fastboot)? Hold the power button and vol down buttons together.
If you can get into the bootloader, use fastboot to flash the factory image instead of using adb. Or try issuing 'adb reboot-bootloader' command to reboot to bootloader
Click to expand...
Click to collapse
Both volume buttons? I've only done the power and down volume. I will try both of these when I get home tonight, or when I wake up. I stayed up until 6am working on this and did not get much sleep. I'm also going to uninstall and reinstall the Pixel driver. I don't remember off the top of my head if I installed it before or after I upgraded my laptop to Windows 10.
elektrosoundwave said:
Both volume buttons? I've only done the power and down volume. I will try both of these when I get home tonight, or when I wake up. I stayed up until 6am working on this and did not get much sleep. I'm also going to uninstall and reinstall the Pixel driver. I don't remember off the top of my head if I installed it before or after I upgraded my laptop to Windows 10.
Click to expand...
Click to collapse
Sorry for being unclear. To get into the bootloader (where you can use the fastboot command to re-flash the factory image), you hold the Power Button and Volume Down buttons together (not volume up button). This is what your screen should look like if you successfully get to the bootloader: https://www.xda-developers.com/files/2016/10/CvqcEDHUsAA_EY4.jpg
If you see that screen, you're sitting good. Download the latest factory image (https://developers.google.com/android/images#marlin) and run the flash-all.bat (for windows) script to reflash your phone. You will have to have fastboot drivers installed on your computer for that to work.
If your device is recognized by adb (if you type 'adb devices' and it shows your device as the output) but you are having trouble getting to the bootloader, you can type in 'adb reboot-bootloader' to reboot your device into fastboot mode where you can flash the factory image. Hopefully that helps push you in the right direction. Your phone isn't bricked/lost forever if adb or fastboot recognizes your device and you can save it!
koivth said:
Sorry for being unclear. To get into the bootloader (where you can use the fastboot command to re-flash the factory image), you hold the Power Button and Volume Down buttons together (not volume up button). This is what your screen should look like if you successfully get to the bootloader: https://www.xda-developers.com/files/2016/10/CvqcEDHUsAA_EY4.jpg
If you see that screen, you're sitting good. Download the latest factory image (https://developers.google.com/android/images#marlin) and run the flash-all.bat (for windows) script to reflash your phone. You will have to have fastboot drivers installed on your computer for that to work.
If your device is recognized by adb (if you type 'adb devices' and it shows your device as the output) but you are having trouble getting to the bootloader, you can type in 'adb reboot-bootloader' to reboot your device into fastboot mode where you can flash the factory image. Hopefully that helps push you in the right direction. Your phone isn't bricked/lost forever if adb or fastboot recognizes your device and you can save it!
Click to expand...
Click to collapse
That's where that first screenshot came from. I will try the reboot bootloader tonight. They sort of recognize my phone, but I can't get them to flash anything. This isn't my first rodeo with borked phones, but I don't think I've had this much trouble since I placed the wrong boot animation on my Droid 4 many years ago.
:victory: :highfive: It's flashing right now. You don't know how much I appreciate it.
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
obsidianlycanthrope said:
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
Click to expand...
Click to collapse
Is your bootloader unlocked?
obsidianlycanthrope said:
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
Click to expand...
Click to collapse
Before you can flash the factory image, you have to unlock the bootloader by issuing this command first: 'fastboot flashing unlock'