Related
I have adb and fastboot installed, and using rumrunner, I am trying to s-off/root my HTC One M7. Is anyone else having issues with it getting stuck on the first pouring <1>... message? Mine has been sitting here for about an hour with no change. I made sure to go in an disable 'verify apps by adb' in the phone's settings, and started again, and yet it still gets stuck on this first pour.
Any ideas?
MReprogle said:
I have adb and fastboot installed, and using rumrunner, I am trying to s-off/root my HTC One M7. Is anyone else having issues with it getting stuck on the first pouring <1>... message? Mine has been sitting here for about an hour with no change. I made sure to go in an disable 'verify apps by adb' in the phone's settings, and started again, and yet it still gets stuck on this first pour.
Any ideas?
Click to expand...
Click to collapse
I had lots of issues what I did by the book is the following...
Flashed stock deodex vzw rom
Flashed stock boot img
Flashed stock recovery
Made sure usb debugging was on
Made sure verifying apps was off
Made sure fastboot was off
Made sure no lock screen was selected
And boom it finally worked. Windows 8 64bit.
Okay so my first question: Is it a VERIZON One?
Second question: Did you properly install the drivers for fastboot on the phone?
1st suggestion: Add an exception in your firewall for soju.exe
2nd suggestion: open a command window in your platform tools folder of your adb installation and type adb devices to see if it comes up
Sent from my One using XDA Premium 4 mobile app
cstrife999 said:
I had lots of issues what I did by the book is the following...
Flashed stock deodex vzw rom
Flashed stock boot img
Flashed stock recovery
Made sure usb debugging was on
Made sure verifying apps was off
Made sure fastboot was off
Made sure no lock screen was selected
And boom it finally worked. Windows 8 64bit.
Click to expand...
Click to collapse
Ok maybe I missed that, where is verifying apps off?
Never mind, found it under developer options.
sanjeeva7 said:
Ok maybe I missed that, where is verifying apps off?
Never mind, found it under developer options.
Click to expand...
Click to collapse
Under security. It's a 4.2 and up thing to prevent malware from being installed on the phone.
Ok still not working.
I am on VZW with stock. Zero mods made to the phone. I just got it a few days ago. I am on the .10 version.
adb works:
C:\miniadb_m7>adb reboot bootloader
C:\miniadb_m7>fastboot devices
FA37K------- fastboot
C:\miniadb_m7>fastboot reboot
rebooting...
finished. total time: 0.044s
C:\miniadb_m7>adb devices
List of devices attached
FA37K------- device
C:\miniadb_m7>
Loaded the HTC only drivers for Windows 7. Run as admin directly from the program, and in DOS which was run as admin. At first I was getting the "WTF" error. I have disabled my antivirus and added the "soju.exe" to allow in my firewall settings. So then I rebooted. I am using the OEM cable and usb 2.0 port.
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (34/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (36/120)
Waiting for device
Waiting for device
pouring (1)...........
.................................
Waiting for device
pouring (2)...........
.................................
Waiting for device
pouring (3)...........
.................................
Waiting for device
pouring (4)...........
................................
Waiting for device
pouring (5)...........
................................
Waiting for device
pouring (6)...........
................................
Waiting for device
pouring (7)...........
................................
Waiting for device
pouring (8)...........
.................................
Waiting for device
pouring (9)...........
.................................
Waiting for device
pouring (10).....
...
If you're getting the pouring (10) error, run the .08 software. that fixed it for me.
What worked for me was to right click soju.exe and run as administrator. After that it worked like a charm.
Sent from my HTC6500LVW using Tapatalk 4
Wow, 10 pours? With all these random numbers of pours I'm reading (mine was 3), I'm thinking this exploit keeps trying until it works and I imagine theres a bit of timing or trial and error involved?
skiman10 said:
What worked for me was to right click soju.exe and run as administrator. After that it worked like a charm.
Sent from my HTC6500LVW using Tapatalk 4
Click to expand...
Click to collapse
Make sure debugging is check marked every time the phone reboots during the process.
I had to manually mark it the first few times.
Sent from my HTC6500LVW using Tapatalk 2
My suggestion is to use Linux to do the process , I did it first attempt . Just make sure you sudo get adb and fastboot and you are good to go . If you don't have linux I suggest dual booting it will get the job done .
Sent from my HTC6500LVW using Tapatalk now Free
kookahdoo said:
Make sure debugging is check marked every time the phone reboots during the process.
I had to manually mark it the first few times.
Sent from my HTC6500LVW using Tapatalk 2
Click to expand...
Click to collapse
It seems when you turn that fast boot option OFF it kept USB debugging on. At least it did for me.
I'm not sure why it would make any difference, but I wiped adb and fastboot from Windows, then reinstalled both of them. After that, everything went perfectly fine, and now I just have to figure out what ROM to put on this thing.
Any suggestions for the Verizon version?
USB ports
I was having the exact same problem, dumping out to a WTF error on Pouring 1. I tried everything on the planet, but what eventually fixed it for me was switching USB ports.
Ironically, it was a USB 3.0 port that worked for me. But my tower has, easily 10 USB ports on the backside. Try different ports. That's the only change I made, and it went from that exact failure to a first try success.
MReprogle said:
I'm not sure why it would make any difference, but I wiped adb and fastboot from Windows, then reinstalled both of them. After that, everything went perfectly fine, and now I just have to figure out what ROM to put on this thing.
Any suggestions for the Verizon version?
Click to expand...
Click to collapse
I am running VANIR and liking it so far. I'm sure I'll try them all eventually. Never had much luck with PAC on any of my previous devices and Liquid was always good but lacked some features I wanted. CM is always another option as well. Whatever you pick now, you will probably change as now that we have a simple S-Off my guess is we will have a LOT more choices soon. What I'd really love to see is a Team Sourcery ROM but doubt it will happen.
I really like Blinkfeed, so I went with BoneStock.
cstrife999 said:
I had lots of issues what I did by the book is the following...
Flashed stock deodex vzw rom
Flashed stock boot img
Flashed stock recovery
Made sure usb debugging was on
Made sure verifying apps was off
Made sure fastboot was off
Made sure no lock screen was selected
And boom it finally worked. Windows 8 64bit.
Click to expand...
Click to collapse
Where did you get the stock recovery to flash?
Verizon HTC One software version & rumrunner
Prior to implementing any Rumrunner S-OFF mod, I notice that Verizon pushed a "minor" OTA upgrade last week. It might have been .8 prior to the OTA and is now showing a long string for the ID; both revs are being shown.
When I query my software on the phone now, I see: "...1.10.605.10-1.10.605.8_R2". I'm not sure what it showed prior to receiving the OTA push...
Question, which version of the software should be downloaded, at least initially? The .10 or the .8? I assume the .8_R2 implies the tweak to .8 and the .10 means the push is applied... Any recommendations?
Thanks, bj
clivusmul said:
Prior to implementing any Rumrunner S-OFF mod, I notice that Verizon pushed a "minor" OTA upgrade last week. It might have been .8 prior to the OTA and is now showing a long string for the ID; both revs are being shown.
When I query my software on the phone now, I see: "...1.10.605.10-1.10.605.8_R2". I'm not sure what it showed prior to receiving the OTA push...
Question, which version of the software should be downloaded, at least initially? The .10 or the .8? I assume the .8_R2 implies the tweak to .8 and the .10 means the push is applied... Any recommendations?
Thanks, bj
Click to expand...
Click to collapse
if i were you, i'd try .8
Aggies1288 said:
Where did you get the stock recovery to flash?
Click to expand...
Click to collapse
I provided a .zip somewhere
let me find it
http://d-h.st/sdg
use fastboot.
Hi I'm trying to sideload the 5.0 lollipop update to my 2013 N7 using adb. I've downloaded the correct file. I have the correct drivers installed, and adb recognizes my N7 just fine. I am able to use the commands to get into the recovery. When I type in "adb sideload <filename.zip>" I keep getting the following message "the syntax of the command is incorrect" Any help would be great. My N7 is unrooted, stock recovery.
Thanks.
evltwn72 said:
Hi I'm trying to sideload the 5.0 lollipop update to my 2013 N7 using adb. I've downloaded the correct file. I have the correct drivers installed, and adb recognizes my N7 just fine. I am able to use the commands to get into the recovery. When I type in "adb sideload <filename.zip>" I keep getting the following message "the syntax of the command is incorrect" Any help would be great. My N7 is unrooted, stock recovery.
Thanks.
Click to expand...
Click to collapse
I didn't get that particular error last night when I tried, but I wa going from 5.0 to 5.0.1 and the sideload first told me the ADB version was too old (I was on 1.0.31 and needed 1.0.32 or something), then it told me that the file check failed (rooted, and non-stock recovery will do that).
I ended up using the factory image instead, which worked great.
Download the factory image, unzip it in your ADB folder and edit the flash-all.bat file. Remove the -w flag near the end of the file. This flag tells the script to wipe your user data, so removing it keeps your data. I did this for both 5.0 and 5.0.1 and all my data/apps/etc were fine.
Once you edit it, save it and double click it with the phone in the bootloader. Took about 2 minutes to flash mine, then about 10-15 minutes to optimize apps. I then ran Chainfire Auto Root and I was back in business. Whole process took about 20 minutes (optimizing apps being nearly all of that).
fury683 said:
I didn't get that particular error last night when I tried, but I wa going from 5.0 to 5.0.1 and the sideload first told me the ADB version was too old (I was on 1.0.31 and needed 1.0.32 or something), then it told me that the file check failed (rooted, and non-stock recovery will do that).
I ended up using the factory image instead, which worked great.
Download the factory image, unzip it in your ADB folder and edit the flash-all.bat file. Remove the -w flag near the end of the file. This flag tells the script to wipe your user data, so removing it keeps your data. I did this for both 5.0 and 5.0.1 and all my data/apps/etc were fine.
Once you edit it, save it and double click it with the phone in the bootloader. Took about 2 minutes to flash mine, then about 10-15 minutes to optimize apps. I then ran Chainfire Auto Root and I was back in business. Whole process took about 20 minutes (optimizing apps being nearly all of that).
Click to expand...
Click to collapse
Well I'm still having no luck. I already had the factory image, I tried what you recommended, and still no luck. Thanks for your help. :highfive: I guess I'll wait until Google decides to push it out. I did call them prior to my 1st post on here, and of course, they were not much help.
evltwn72 said:
Well I'm still having no luck. I already had the factory image, I tried what you recommended, and still no luck. Thanks for your help. :highfive: I guess I'll wait until Google decides to push it out. I did call them prior to my 1st post on here, and of course, they were not much help.
Click to expand...
Click to collapse
I followed this guide which worked great : http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
If you still get the error, maybe deinstall adb, drivers etc and try again
Sent from my Nexus 5 using XDA Free mobile app
chrismast said:
I followed this guide which worked great : http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
If you still get the error, maybe deinstall adb, drivers etc and try again
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That was my next suggestion. If sideload and factory images aren't working, seems like it's a PC issue. Worth a shot.
My drivers are working just fine. I made sure they were update. I'm just gonna wait until I get the OTA update. Thanks for your help guys.
Sent from my HTC One M8 using XDA app
Well Google just pushed 5.0.1 to my N7. Happy days.
Sent from my Nexus 7 using XDA app
All I want to do is flash back to stock, I feel like I am gonna lose my my mind or go buy a new phone. I have mostly spent a solid 10 hours of time trying to get it to work.
I have been endlessly looking, searching, trying all these different methods to get my ls980 to connect to my pc. So basically everytime I have hooked it up it comes up as unreconized or unknown device doesn't connect.
List of things: Latest LG mobile drivers I have installed them through there exe and tried to install them manually when the ! comes up on the device. I have tried my laptop and my desktop every usb in all of them. I have tried the stock cable, and about 8 other different cables. I have tried it in debugging mode with mtp and without debugging. I tried the support tool as well. Tried composite usb setting.
I guess I am at a loss at this point to what even to try besides sending it to be repaired. Which I don't feel like it's a phone problem and I am just missing something I can't find, I say this because the phone charges perfectly fine and no damage to the usb port at all. If anyone has good information or just a direction I can go will be greatly appericated.
Dirty Grimace said:
All I want to do is flash back to stock, I feel like I am gonna lose my my mind or go buy a new phone. I have mostly spent a solid 10 hours of time trying to get it to work.
I have been endlessly looking, searching, trying all these different methods to get my ls980 to connect to my pc. So basically everytime I have hooked it up it comes up as unreconized or unknown device doesn't connect.
List of things: Latest LG mobile drivers I have installed them through there exe and tried to install them manually when the ! comes up on the device. I have tried my laptop and my desktop every usb in all of them. I have tried the stock cable, and about 8 other different cables. I have tried it in debugging mode with mtp and without debugging. I tried the support tool as well. Tried composite usb setting.
I guess I am at a loss at this point to what even to try besides sending it to be repaired. Which I don't feel like it's a phone problem and I am just missing something I can't find, I say this because the phone charges perfectly fine and no damage to the usb port at all. If anyone has good information or just a direction I can go will be greatly appericated.
Click to expand...
Click to collapse
Is your device functioning normally, besides from this? Also, did you use the T-mobile drivers?
tabp0le said:
Is your device functioning normally, besides from this? Also, did you use the T-mobile drivers?
Click to expand...
Click to collapse
It works just fine, only notable thing that I never figured out was why OTA updates don't ever take, it's still on ZVC. I tried the T-mobile d802 drivers as it was suggested by another post I saw on here.
And you've removed all drivers to android and lg for it.
secret.animal said:
And you've removed all drivers to android and lg for it.
Click to expand...
Click to collapse
Correct, I uninstalled them, tried new ones a couple different ways from other posts, and removed them and tried again. Right now I just have them all uninstalled. Trying to figure out if it's something that's stopping it. In error I did forget that a couple times it reconized it but would :fail to start code 10.
Which version of windows are you running? On both desktop and laptop???
secret.animal said:
Which version of windows are you running? On both desktop and laptop???
Click to expand...
Click to collapse
Windows 7 64-bit home premium on both.
Dirty Grimace said:
Windows 7 64-bit home premium on both.
Click to expand...
Click to collapse
OK, that shouldn't be the problem. Zvc yet updates do not take.
Is it rooted?
And it is running on sprint network?
secret.animal said:
OK, that shouldn't be the problem. Zvc yet updates do not take.
Is it rooted?
And it is running on sprint network?
Click to expand...
Click to collapse
Long story short, it's on ZVC, even with other updates that came up it would never update past it. I took it into sprint several times they didn't know why, I did root it as one guy said that was an option, I used stump root, but then I unrooted as I felt I was getting into something too complicated. It is on the sprint network, about 90% of the time and all the times I tried to update previous to the root/unroot. But I am not trying to update it since the root, mostly trying to restore to stock and start overish.
I'm thinking maybe a virtual machine with Linux might find it. If it can then there is something. And maybe we can redo the partitions and such.
secret.animal said:
I'm thinking maybe a virtual machine with Linux might find it. If it can then there is something. And maybe we can redo the partitions and such.
Click to expand...
Click to collapse
I will check with a couple guys see if I can find someone with a machine with Linux this weekend. Thanks a lot for you on going help.
I have this phone at least for another year. So at least someone out here is still willing to help.
secret.animal said:
I have this phone at least for another year. So at least someone out here is still willing to help.
Click to expand...
Click to collapse
I was unable to find anyone outside local computer store that I know. Kind of problem finding that in rural midwest. I also tried installing drivers in vista compatability as that was suggested no luck..
Dirty Grimace said:
I was unable to find anyone outside local computer store that I know. Kind of problem finding that in rural midwest. I also tried installing drivers in vista compatability as that was suggested no luck..
Click to expand...
Click to collapse
As for driver removal, one thing I remember with the nexus devices. There is wugfresh nrt, nexus root toolkit. Let me see which application or program they loaded for removal before reinstall of drivers. I know they have 2 places you check into.
Dang, I'll have to try to load them via a windows emulator. I'm running Linux right now.
secret.animal said:
As for driver removal, one thing I remember with the nexus devices. There is wugfresh nrt, nexus root toolkit. Let me see which application or program they loaded for removal before reinstall of drivers. I know they have 2 places you check into.
Dang, I'll have to try to load them via a windows emulator. I'm running Linux right now.
Click to expand...
Click to collapse
Let me know.. I am kinda at the point where I might try to find someone to flash it back to stock, and just activated my old phone til it gets back.. like I am past the point of frustration and no legit just don't get why, since all my other devices have zero issues connecting.
Updated to Android 10. Build number QP1A.191005.007.A1. Ever since updating to Android 10, my phone won't connect to my computer. It'll charge via USB, but that's about it. I can't access any USB options, they are greyed out. ADB will not attempt to authorize my computer, so I can't root it. I can't use data transfer, so if I have to resolve to a factory reset, I have no way to back up data. My phone won't authorize an app to send data over wifi, so that's out. It's been a while, so I figured (hoped) someone would have an idea what to do. Oh and connecting to a Windows machine has always been a hassle for me, so I use a Linux machine to connect to my phone. That worked smoothly up until this update. So, anyone know what's going on?
google usb drivers
sudoxd said:
google usb drivers
Click to expand...
Click to collapse
Uninstalled and reinstalled the drivers. Did not help. In the end I just did a factory reset and flashed a clean factory image. It was not what I wanted to do, but it fixed the problem.
valkiron said:
Updated to Android 10. Build number QP1A.191005.007.A1. Ever since updating to Android 10, my phone won't connect to my computer. It'll charge via USB, but that's about it. I can't access any USB options, they are greyed out. ADB will not attempt to authorize my computer, so I can't root it. I can't use data transfer, so if I have to resolve to a factory reset, I have no way to back up data. My phone won't authorize an app to send data over wifi, so that's out. It's been a while, so I figured (hoped) someone would have an idea what to do. Oh and connecting to a Windows machine has always been a hassle for me, so I use a Linux machine to connect to my phone. That worked smoothly up until this update. So, anyone know what's going on?
Click to expand...
Click to collapse
SDK Platform-tools r29.0.5
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-10-0-q-t3964112
Homeboy76 said:
SDK Platform-tools r29.0.5
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-10-0-q-t3964112
Click to expand...
Click to collapse
Thanks, but updating platform-tools did not help. Funnily enough, using the guide this time around turned a 30 minute fix into a 3 hour fix and for a while there I was worried that I had bricked my phone beyond recovery, but that's a story for another post. Thanks for replying though.
valkiron said:
Thanks, but updating platform-tools did not help. Funnily enough, using the guide this time around turned a 30 minute fix into a 3 hour fix and for a while there I was worried that I had bricked my phone beyond recovery, but that's a story for another post. Thanks for replying though.
Click to expand...
Click to collapse
What was the solution to your problem?
Homeboy76 said:
What was the solution to your problem?
Click to expand...
Click to collapse
Yea, I couldn't figure it out. In the end I had to factory reset and sideload the ota. Cleared the memory, but the usb is working when I plug it into my computer.
Trying to sideload the June drop. I have done it many times before with no issues. But this time it keeps hanging. Usually at 1 percent but I made it to 6 percent on one try.
Multiple trys with different USB cords and computers. One of which I have used many times in the past.
Any ideas?
TonikJDK said:
Trying to sideload the June drop. I have done it many times before with no issues. But this time it keeps hanging. Usually at 1 percent but I made it to 6 percent on one try.
Multiple trys with different USB cords and computers. One of which I have used many times in the past.
Any ideas?
Click to expand...
Click to collapse
OTA or Full image? I just use the android flash tool and flash full image without wiping data or locking bootloader. There are threads with pics on how to use android flash tool.
jcp2 said:
OTA or Full image? I just use the android flash tool and flash full image without wiping data or locking bootloader. There are threads with pics on how to use android flash tool.
Click to expand...
Click to collapse
OTA sideload. I am not bootloader unlocked, doing so now would require a wipe. The flash tool can be used while locked?
TonikJDK said:
Trying to sideload the June drop. I have done it many times before with no issues. But this time it keeps hanging. Usually at 1 percent but I made it to 6 percent on one try.
Multiple trys with different USB cords and computers. One of which I have used many times in the past.
Any ideas?
Click to expand...
Click to collapse
Knowing you you have the latest tools. Are you rooted? OTA or full image? You'll get it, you're missing a simple thing.
TonikJDK said:
OTA sideload. I am not bootloader unlocked, doing so now would require a wipe. The flash tool can be used while locked?
Click to expand...
Click to collapse
No, must be unlocked.
bobby janow said:
you're missing a simple thing.
Click to expand...
Click to collapse
Lol. Between my look at last check for update and trying the sideload it had downloaded the OTA.
TonikJDK said:
Lol. Between my look at last check for update and trying the sideload it had downloaded the OTA.
Click to expand...
Click to collapse
I knew it. Lol
i am trying to side load the andriod 13 update to my p6 pro and it is stuck at 10%, what should I do?
dnsmo said:
i am trying to side load the andriod 13 update to my p6 pro and it is stuck at 10%, what should I do?
Click to expand...
Click to collapse
Try USB 2.0. I had 9 different random percentage stops over two different PCs and my phone was soft bricked. I grabbed an adapter that downed my USB 3 to 2 and ran again. First shot on a USB 2.0 the OTA went through and brought my phone back to how it was.
Similar to @roughriduz's advice, I switched both which USB 3.0 port and which USB-C cable I was using, and that did the trick for me, although in my case it was the full factory image.
I used PixelFlasher since I am rooted with Magisk. Didn't have any issues using my USB 3.0 port and updated my Pixel 6 Pro to Android 13 in about 15 minutes. No problems.
Switching to a USB 2.0 port fixed it for me also. Thanks everyone.
Long press Power & volumn UP button for 10 second should solve it.