Related
Hi
Unprovoked (latest version) tried on the MAC and PC does not root my HTC Desire running Android 2.1. I have tried everything possible and it just does not grant me root access to the phone.
What are my options, what other software can I try, to root the phone, preferably PC based.
Thanks
Thread moved to Q&A.
dazdaz said:
Hi
Unprovoked (latest version) tried on the MAC and PC does not root my HTC Desire running Android 2.1. I have tried everything possible and it just does not grant me root access to the phone.
What are my options, what other software can I try, to root the phone, preferably PC based.
Thanks
Click to expand...
Click to collapse
#snark
Good Lord, of course it doesn't. There is no rooting tool known as unprovoked.
#endsnark
Please, describe the problem that you are facing, what steps you have taken, etc.
Don't ask stupid questions (or ask questions stupidly) and expect anyone to be able to have a vision of your problem, diagnose it correctly AND help you solve it.
lol a classic typo, I was provoked using unrevoked hehe I wish I could change the subject title now, and of course meant unrevoked (sorry was too tired after trying it for many many hours) ... i know that many people have had success rooting their phones with this tool.
My phone got stuck in a reboot cycle after using unrevoked on 2.2, so I downgraded to 2.1-update1 and tried unrevoked again but the same problem happened and no root access. Then I took the battery out for a few minutes, powered it back on, and so far it's been stable, i.e. no reboots. This morning I also powered off and back on again and the phone has not rebooted. I just can't understand it.
Moving forward, is there another option, a different tool which I could use which can root Android 2.1.
Did you enable usb debugging?
Sent from my HTC Desire using XDA App
TheGhost1233 said:
Did you enable usb debugging?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Yes and selected default connection type to charge only.
Have you installed HtC Sync then removed it? Making sure the drivers are left on?
I tried on both the PC and MAC. The MAC does'nt require messing around with USB drivers.
On the PC, HTC sync was uninstalled with the drivers left installed ( unrevoked modified USB driver ) and then ran unrevoked.
So I now have HBOOT 0.83.0001 and Android 2.1.
I tried unprovoked once more today, and the phone is stuck in a reboot loop.
1.
I take out the battery, and the phone boots and then reboots once i see the multi-coloured HTC background and then goes into that infinite reboot cycle before I can make any changes.
2.
HBOOT is trying to find an image with a name similar to : PB99IMG.ZIP which it can't find so reboots in a loop until the battery in taken out and then returns to 1.
Hello,
i've got a problem like the title says. Everytime i connect my phone to the computer via usb, i get the message the device wasnt recognized by the computer. i tried everything i know, another usbport. etc. i want to install a new radio, but without connecting to the computer it isnt possible, because i dont have the usb debugging active.
i hope someone has an idea what i can do. i have rcmix 6.1.0.1 installed.
Are you using Windoze?
If you are unfortunate enough to be doing so then you might need to reinstall HTC Sync program (sometimes it works better if you completely uninstall it first including manually removing any left over folders and files in the application data folder.
thanks for the quick answer.
i tried it, but it didnt help. where is this application data folder? do you mean on the computer? i found after uninstalling no more folders from htc.
and yes i use windows home premium 64bit.
got another idea? now it says also the device does not function properly. i hope that nothing on the device is broken.
schorschl said:
thanks for the quick answer.
i tried it, but it didnt help. where is this application data folder? do you mean on the computer? i found after uninstalling no more folders from htc.
and yes i use windows home premium 64bit.
got another idea? now it says also the device does not function properly. i hope that nothing on the device is broken.
Click to expand...
Click to collapse
yes he is talking about your computer... if in the "program files" you hasn´t anythink about HTC SYNC,, ALL IS OK...
but enssure that in the configuration panel-system-dispositive administrator you hasn´t any drive installed for your android device... if you have installed it, erase or uninstall it before re-install htc sync or the htc drivers....then you can re-install and reboot windoux...
and hey buddy!I recommend to you to consider to pass to linux, you will not have this type of mistakes... LOL
UBUNTU is great!
I'm afraid I don't know much about Windoze but memory serving appication data is a hidden folder so you will need to change it to view them and is in the Documents and Settings / [Your username] directory.
Device not function is just a default Windoze error when it can't install something, ignore it, your phone is fine.
If you have reinstalled HTC Sync, try a USB port on the opposite side of the PC. So if you trying ones next to each other on the front, try ones on the back (they use different headers on the motherboard).
If that doesn't work then I'm afraid I probably won't be of much more use, sorry.
SERGI.3210 said:
and hey buddy!I recommend to you to consider to pass to linux, you will not have this type of mistakes... LOL
UBUNTU is great!
Click to expand...
Click to collapse
Best advice ever. Ubuntu user here too (thus for me everything just works ).
Mr_JMM said:
Best advice ever. Ubuntu user here too (thus for me everything just works ).
Click to expand...
Click to collapse
The use of linux is good to understand better android OS you don´t believe?
you said it.... EVERYTHING WORKS
thanks guys for your help, but although i followed your advices, except the one to switch to linux ;-), it hasnt got better yet. the problem is still exsisting and i dont know what else i can do.
anyone got an idea how to install radio without having usb debugging and the drivers from the computer?
Hi!
I've got the same problem with 2 different PCs, one with Win7 64-bit, the other with Win XP PRO.
Other devices work fine with the same USB ports, so i doubt it's windows or the PC...
schorschl said:
thanks guys for your help, but although i followed your advices, except the one to switch to linux ;-), it hasnt got better yet. the problem is still exsisting and i dont know what else i can do.
anyone got an idea how to install radio without having usb debugging and the drivers from the computer?
Click to expand...
Click to collapse
you can´t flash any radio if your phone is not recognized
well.. Let's continue with the problem in question...
1.At some time could you have connected it?with the stock rom maybe?
2.have you tried to swich on mass storage usb mode?what´s the result?
3.when you tries to swich the phone for flash some radio you enables "usb debug"
and "only chargue"?
its a weird problem
Hey man, I've had the same problem with my old Desire (normal). Which was actually broken.. Went back to the store twice and it was sent to htc twice. But that one wasn't rooted tho. But in the end, the sensors were broken & something inside the phone that didn't recon the pc. But also try a full wipe, which helped temporarily for me.
1. yes i functioned, not only with stock rom, but also with the next few custom roms. but then 2 weeks ago the problem occured and i dont know why. before i used custom roms for months.
2. it also doesnt recognize the mass storage anymore, i dont see the memorycard as a storage device in explorer.
3. yes i turned usb debugging on and connected charging only, i flashed radios before. but the problem with the actual is, that my signalstrength is weak and so i wanted to flash the recommended for this rom, and so i recognized there is something wrong, cause my problem here occured.
normally i sync with myphoneexplorer so i didnt realize that mass storage didnt function anymore.
and because earlier i got no problems, i think more and more, that something on the phone went wrong.
maybe it helps if i go back to stockrom and undo all changes i made, to start all over again?
again thanks mate for your effort to help me out
maikel16 said:
Hey man, I've had the same problem with my old Desire (normal). Which was actually broken.. Went back to the store twice and it was sent to htc twice. But that one wasn't rooted tho. But in the end, the sensors were broken & something inside the phone that didn't recon the pc. But also try a full wipe, which helped temporarily for me.
Click to expand...
Click to collapse
maybe this is his problem...
schorschl said:
1. yes i functioned, not only with stock rom, but also with the next few custom roms. but then 2 weeks ago the problem occured and i dont know why. before i used custom roms for months.
2. it also doesnt recognize the mass storage anymore, i dont see the memorycard as a storage device in explorer.
3. yes i turned usb debugging on and connected charging only, i flashed radios before. but the problem with the actual is, that my signalstrength is weak and so i wanted to flash the recommended for this rom, and so i recognized there is something wrong, cause my problem here occured.
normally i sync with myphoneexplorer so i didnt realize that mass storage didnt function anymore.
and because earlier i got no problems, i think more and more, that something on the phone went wrong.
maybe it helps if i go back to stockrom and undo all changes i made, to start all over again?
again thanks mate for your effort to help me out
Click to expand...
Click to collapse
you´re welcome companion
i reded in a spanish forum ( www.htcmania.es ) about your problem and there´s people that had the same problem with a S.GALAXY S & desire HD...
someone was solved it fullwiping and formating (in the paragraph of mounts & storage into CWM) and flashing another ROM... then they formatted their sd card with a card reader OF THE PC... later they was formatted the sd card from the pc and the problem was disapeared successfully...
BUT if it persists i think that you should (mi suggestion) send your machine to the thecnical service....
ok, will try this today evening when i'm home. if this doesnt work i will reset it in the orginial state and send it to the technical support. i will leave a comment if i was successful, perhaps this will help others with the same problem.
schorschl said:
ok, will try this today evening when i'm home. if this doesnt work i will reset it in the orginial state and send it to the technical support. i will leave a comment if i was successful, perhaps this will help others with the same problem.
Click to expand...
Click to collapse
good idea mate
see you soon
finally after long hours of work, i have to state, that nothing changed.
i tried everything, but its still the same.
so i think i will send it in to the technical service.
does anyone of you know if they will say something about the software i changed? because i now i cant go back to stock radio.
thanks for your help.
finally after long hours of work, i have to state, that nothing changed.
i tried everything, but its still the same.
so i think i will send it in to the technical service.
does anyone of you know if they will say something about the software i changed? because i now i cant go back to stock radio.
thanks for your help.
Click to expand...
Click to collapse
oops!!don't say anything LOL! you lose warranty...unroot and disable custom recovery...of your phone flashing an official ruu and then do S-OFF... ITS sufficient..
edit: sorry FOR your DHD
Sent from my Nokia 3210 running the worst symbian using the XDA app powered by LOL
hi mate, i also had the same problem, i connected my dhd to the back usb port of my pc and it was ok. and i also got this problem when i was using a non genuine htc usb cable.
weird!!! can it be possible?
EDIT:I´M using a NOKIA N97 genuine cable and works perfect... LOL
Ok I'm a HTC noob so please bear with me. I setup adb-sdk environment and windows environment variable. After that I obtained Alpharevx and ran it. Everything went fine and I entered the beta key. But then after
'Beta key accepted - thank you for participating!'
, nothing happens. It just stops. Any idea how to get this thing going?
Did you run AlphaRevx as an administrator ... given you're on Vista or Windows7?
Is the phone in USB debugging mode?
Is the Android software on your phone 2.2.1? If it's 2.3 then the AlphaRevX will not work :/
JWhetstone02 said:
Did you run AlphaRevx as an administrator ... given you're on Vista or Windows7?
Is the phone in USB debugging mode?
Is the Android software on your phone 2.2.1? If it's 2.3 then the AlphaRevX will not work :/
Click to expand...
Click to collapse
Thanks
Yes my phone is frogyo.
Yes it's in USB debugging mode.
Yes ran as an admin because I disabled the protection so basically all apps as admin on my windows 7.
I've read in the AlphaRevX thread where some people have had to do it multiple times before it Roots their phone. Maybe try that?
Thank you. I will try more :O I hope this won't brick my phone. I heard HTC devices can't recover from brick. With SGS you could just odin back from whatever mess you are in.
Is the phone set to charge only? Also is htc sync uninstalled?
Sent from my Incredible 2 using Tapatalk
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
4GivenByChrist said:
Is the phone set to charge only? Also is htc sync uninstalled?
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Yes, set to charge only mode.
Yes, removed everything and used the drivers from alpharevx's site.
JWhetstone02 said:
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
Click to expand...
Click to collapse
Yea, I just got mine as a replacement after a year of use. So far I'm happy because the screen is up to par with SAmoled. People always hype up SAmoled but imho, SLCD on Dinc2 is not far behind.
Hey, so I am new to this board. I myself have a Dinc2 arriving soon. My brother just got his. We are both former fascinate owners. After researching and following some how to's, my brother was rooting his phone and he got stuck while attempting to get recovery after S-off. He cannot post, but here is what stated happened:
Hey I'm having a problem with my incredible 2.
Before activating the phone (avoiding the 2.3 update) I tried rooting my phone.
1) I downloaded alpharedex and generated the code
2) downloaded the recovery mode application onto the phone
3) and placed the SU zip folder onto my phone
I was stopped at step 3 because the volume down power button procedure was not working. Instead the phone powered on normally. I attempted it many more times and it would not work.
After spending some time on it, I said screw it, I just want to use the phone. So i activated it and OK'd the 2.3 update. It shut down my phone and began to download the file but it was stopped with a exclamation point in a red triangle. I tried doing a hard reset (volume up and power button) but that did not work. So i was forced to take out the battery. When I powered up the phone again, it continued the download: the phone shut down, it began to download and froze up like last time.
Click to expand...
Click to collapse
Okay, so yes I know he shouldn't have done this. After consulting with me, I was able to get him into recovery by attempting the volume down + power procedure about a dozen more times.
Should he install the super user package and reboot? Or should he do something now to fix the OTA auto reboot problem while he still has recovery?
Edit: Because he is in recovery, could he just factory reset and flash a new rom? Apparently, when he boots the phone normally it gets to the home screen and then instantaneously reboots and attempts to install the OTA. That is where it locks up.
If he installs a rom it should block the update. Any custom rom will have superuser built in, and I know at least CM7 has OTA blocking built in as well.
Oh, and it sounds like his trouble booting into hboot with power and volume down is because fastboot is enabled. It can be turned off in settings»power.
k_nivesout said:
If he installs a rom it should block the update. Any custom rom will have superuser built in, and I know at least CM7 has OTA blocking built in as well.
Oh, and it sounds like his trouble booting into hboot with power and volume down is because fastboot is enabled. It can be turned off in settings»power.
Click to expand...
Click to collapse
But the problem is that now he can't get into settings.... damn.maybe a factory reset is best if that's possible.
Sent from my Incredible 2 using Tapatalk
deaffob said:
Yes, set to charge only mode.
Yes, removed everything and used the drivers from alpharevx's site.
Yea, I just got mine as a replacement after a year of use. So far I'm happy because the screen is up to par with SAmoled. People always hype up SAmoled but imho, SLCD on Dinc2 is not far behind.
Click to expand...
Click to collapse
You have it working yet? If not I would uninstall the drivers you got and then download and install HTC sync. Then uninstall just htc sync leaving your drivers. Then try again. That wokred for me when I was unlocking a friends phone.
Sent from my Incredible 2 using Tapatalk
deaffob, you seem to be pretty computer literate, if it keeps giving you issues, boot ubuntu from a flash drive and do it that way. I messed with windows for a couple hours, and it took me all of 20 minutes to install ubuntu to my flash drive, boot into it and root.
bik2101 said:
But the problem is that now he can't get into settings.... damn.maybe a factory reset is best if that's possible.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
That is what I was hoping for, but I don't think there is a factory reset option in Recovery that doesn't wipe the current rom he is on.
I was pretty sure flashing a rom with superuser in it would solve it, and it sounds like that might be the answer.
Only problem now is somehow getting the rom on to the SD card. I might have to have him swap SD cards in my phone, add the rom to the SD card, and then swap back.
I fixed it by going to alpharev IRC and got a great help from attn1! He was very helpful late at night.
To those of who'd like to know, this was my situation:
-Windows 7 64bit with admin control turned off=everything has admin rights.
-Fastboot off(tried on too)
-installed HTC Sync's driver.
-tried HTC driver that's posted on AlpharevX's website.
-HTC Sync was uninstalled.
-It was froyo
-Correct HBOOT(obvious because the whole point of getting the beta key was to prevent someone using the hack with the wrong version of HBOOT)
-Tried 3 different USB ports.
-ADB SDK was installed
-JDK was installed
-environment variable path for ADB SDK was set.
-tried reinstalling the HTC Driver twice, each time uninstalling with Revo Uninstaller to clean up registry.
So even after all these, the hack still did not work. So attn1 suggested that I should try it different computer or download the flash version of Ubuntu and try it in there. I tried it on my old lap with Windows 7 64 installed. I haven't used the laptop that much so the Windows was pretty clean and new.
It worked on that laptop. The lesson is, no matter how much you take care of your windows system, I practically baby my computer and do everything to keep the optimum performance, it will get screwed up after some time. I would've never thought that it'd be my desktop Windows that was the problem.
So if you are having a problem, please try Ubuntu as that's probably the best bet.
PeterGunz said:
That is what I was hoping for, but I don't think there is a factory reset option in Recovery that doesn't wipe the current rom he is on.
I was pretty sure flashing a rom with superuser in it would solve it, and it sounds like that might be the answer.
Only problem now is somehow getting the rom on to the SD card. I might have to have him swap SD cards in my phone, add the rom to the SD card, and then swap back.
Click to expand...
Click to collapse
but there's still the problem of not being able to turn fast boot off, which i think is needed to be able to get into recovery..
get into recovery
To get into Recovery EVERY time, simply do a battery
pull beforehand. That does it.
JWhetstone02 said:
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
Click to expand...
Click to collapse
+1
Yep! And I'm happy I made the switch, the SLCD screen is not bad and has more accurate color reproduction and plus who uses the SAMOLED at 100% brightness anyways..-nobody really lol.
Also HTC sense imho is waay more useable with good functionalities like the ever so good integration of Facebook compared to TW. I still can't get over that since I was conned into thinking that the Fascinate had in-app pictures but atlas it was a link to the website.. whereas HTC has that and more plus notifications!
Sorry I'm just thoroughly impressed especially since this is my first HTC Device. ^__^
Plus the rotating capacitive buttons is just super cool... :3 Now to make it work when using the camera app... >.> Anybody know if this mod exists yet?
Sent from my ADR6350 using XDA App-Dinc2 switched from a Fascinate.. :3
michaelbsheldon said:
To get into Recovery EVERY time, simply do a battery
pull beforehand. That does it.
Click to expand...
Click to collapse
You can download a program from the Market called quickboot It allows you to reboot into recovery without doing a battery pull. this is what I use right now in replace of the 4-in-1 reboot menu
I just got su on mine. I am an Android beginner so my experience may help. My system is a laptop running Win 7. I had installed synch and then following advice removed it with all drivers. I installed the htc USB drivers, and plugged in the phone in the proper mode. AlphaRevX will not work. So (this may be vital) reinstalled synch with drivers. Then removed synch. Got AlphaRevX to do its thing at once. So the other drivers must be there!
I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer
Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.
I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app
Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little
Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT
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.