I've tried all the s-off guides tu unlock my incredible s, but every time, when i try to flash the RUU, it dosen't work Someone to help me
What hboot u on?
more info u give the help u will get in return
Sent from my HTC Incredible S using xda premium
jules290496 said:
I've tried all the s-off guides tu unlock my incredible s, but every time, when i try to flash the RUU, it dosen't work Someone to help me
Click to expand...
Click to collapse
sharkman3d said:
What hboot u on?
more info u give the help u will get in return
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^ What he said!!!!!!!! ^^^^^^^^^^^^^^^^
More information please.
Sorry I'm on 2.01.0001
What error did you get?
jules290496 said:
I've tried all the s-off guides tu unlock my incredible s, but every time, when i try to flash the RUU, it dosen't work Someone to help me
Click to expand...
Click to collapse
Even i have this problem with the new version of HBOOT. Did you try the tool given by Nonverbose?? And are you having any radio issues?
I got this in my terminal:
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Is the device rooted?
y OR n:n
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Pushing tacoroot
adb server is out of date. killing...
* daemon started successfully *
351 KB/s (14475 bytes in 0.040s)
Correcting permissions
adb server is out of date. killing...
* daemon started successfully *
tacoroot rebooting phone to recovery
adb server is out of date. killing...
* daemon started successfully *
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
link failed No such file or directory
Waiting for device to connect
Device found
tacoroot starting adbD as root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
cannot create /data/local.prop: permission denied
Waiting for device to connect
Device found
Pushing misc_version
1006 KB/s (367096 bytes in 0.356s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Do you need to create a goldcard?
y OR n:n
Undoing tacoroot (if applied)
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
rm failed for /data/local.prop, No such file or directory
Root removed, rebooting
Waiting for device to connect
error: protocol fault (no status)
Device found
Cleaning temp files
* daemon not running. starting it now *
* daemon started successfully *
Checking version-main
< waiting for device >
version-main: 3.11.405.2
finished. total time: 0.002s
If the version-main returns 2.00.000.0 you should be
able to run the RUU downgrade. If it does not, answer n to the
unlocked bootloader prompt no matter what.
Do you have an unlocked bootloader from htcdev.com?
y OR n:y
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.297s
Note: run the RUU in fastboot mode
If all steps were completed without error,
you should be ready to run the RUU downgrade
Appuyez sur une touche pour continuer...
And when i try to flash the RUU for downgrad, it say : The update utility can't update the android phone.
Try to obtain the correct rom update utility and try again ( it's translated from french)
InsertDumbNick said:
Even i have this problem with the new version of HBOOT. Did you try the tool given by Nonverbose?? And are you having any radio issues?
Click to expand...
Click to collapse
Yes, it was the first i tried...
Is the RUU you have the correct one for your region? The fact you are choosing not to make a goldcard could be having an effect.
Type this command into cmd while your phone is in fastboot mode 'fastboot oem lock'. I did that before I run the process.
Sent from my HTC Incredible S using xda premium
jules290496 said:
I got this in my terminal:
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Is the device rooted?
y OR n:n
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Pushing tacoroot
adb server is out of date. killing...
* daemon started successfully *
351 KB/s (14475 bytes in 0.040s)
Correcting permissions
adb server is out of date. killing...
* daemon started successfully *
tacoroot rebooting phone to recovery
adb server is out of date. killing...
* daemon started successfully *
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
link failed No such file or directory
Waiting for device to connect
Device found
tacoroot starting adbD as root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
cannot create /data/local.prop: permission denied
Waiting for device to connect
Device found
Pushing misc_version
1006 KB/s (367096 bytes in 0.356s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Do you need to create a goldcard?
y OR n:n
Undoing tacoroot (if applied)
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
rm failed for /data/local.prop, No such file or directory
Root removed, rebooting
Waiting for device to connect
error: protocol fault (no status)
Device found
Cleaning temp files
* daemon not running. starting it now *
* daemon started successfully *
Checking version-main
< waiting for device >
version-main: 3.11.405.2
finished. total time: 0.002s
If the version-main returns 2.00.000.0 you should be
able to run the RUU downgrade. If it does not, answer n to the
unlocked bootloader prompt no matter what.
Do you have an unlocked bootloader from htcdev.com?
y OR n:y
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.297s
Note: run the RUU in fastboot mode
If all steps were completed without error,
you should be ready to run the RUU downgrade
Appuyez sur une touche pour continuer...
And when i try to flash the RUU for downgrad, it say : The update utility can't update the android phone.
Try to obtain the correct rom update utility and try again ( it's translated from french)
Click to expand...
Click to collapse
OK, during the running of this script, when tacoroot says starting adb as root, do you see a # prompt?
From the messages, it looks like tacoroot is not getting temproot in order to update the mainver value to 2.00.0000. At the end of the script your mainver is still 3.11.405.2.
tpbklake said:
OK, during the running of this script, when tacoroot says starting adb as root, do you see a # prompt?
From the messages, it looks like tacoroot is not getting temproot in order to update the mainver value to 2.00.0000. At the end of the script your mainver is still 3.11.405.2.
Click to expand...
Click to collapse
No, i don't see any # and i tried whith and without goldcard
jules290496 said:
No, i don't see any # and i tried whith and without goldcard
Click to expand...
Click to collapse
Yeah, the whole key to the script is getting temp root access so that the mainver can be modified to 2.00.0000.
If that doesn't work, the whole goldcard and RUU thing will not work.
The best thing you could try is to open a command window and try manually typing the commands in and post the command window to help isolate the issue.
I think i will give up, thanks anyway
jules290496 said:
I think i will give up, thanks anyway
Click to expand...
Click to collapse
You have a custom recovery installed?
No, i don't now how to do it without revolutionary...
jules290496 said:
No, i don't now how to do it without revolutionary...
Click to expand...
Click to collapse
So the phone is completely stock, just unlocked bootloader?
Yes it's completely stock
jules290496 said:
Yes it's completely stock
Click to expand...
Click to collapse
Try locking the bootloader and doing a factory reset. Boot into recovery once, turn fastboot off and USB debugging on and run the newest version (3.2) of the script again.
Ok, i will try
Related
Well, I see lot's of questions about rooting. Here's a small guide on how to do that. At first make sure that you have KIES installed. The drivers for your phone come with it, without drivers there will be no root!
1. Download the attached file. (Super One Click Root.rar)
2. Unpack the .rar.
3. Connect your phone through USB to the computer.
4. Make sure USB debugging is checked on. (Settings > Applications > Development > USB debugging)
5. Launch SuperOneClick.exe
6. Press the 'Root' button.
7. Wait for the program to finish.
P.S. I'm not able to make screenshots. But, it's not that hard.
Just added:
before run SuperOneClick, install your phone driver (you can install KIES). Thanks
dhendriyanto said:
Just added:
before run SuperOneClick, install your phone driver (you can install KIES). Thanks
Click to expand...
Click to collapse
Added it to the first post.
hey i hav tried but it stuck here
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 0.05s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.14s
Waiting for device...
OK 0.06s
2.2.1
Getting manufacturer...
Samsung
OK 0.03s
Getting model...
GT-S5570
OK 0.03s
Getting version...
JPKA3
OK 0.03s
Checking if rooted...
False
OK 0.06s
Installing BusyBox (temporary)... - Step #1
2027 KB/s (1062992 bytes in 0.512s)
OK 0.56s
Installing BusyBox (temporary)... - Step #2
OK 0.03s
Rooting device... - Step #1
cannot stat 'C:\Users\myacirkhan\Downloads\Compressed\Super_One_Click_Root\Super One Click Root\Exploits\psneuter': No such file or directory
OK 0.05s
Rooting device... - Step #2
Unable to chmod /data/local/tmp/psneuter: No such file or directory
OK 0.03s
Rooting device... - Step #3
OK 0.01s
Rooting device... - Step #4
./psneuter: not found
FAILED
handsumdevil said:
hey i hav tried but it stuck here
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 0.05s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.14s
Waiting for device...
OK 0.06s
2.2.1
Getting manufacturer...
Samsung
OK 0.03s
Getting model...
GT-S5570
OK 0.03s
Getting version...
JPKA3
OK 0.03s
Checking if rooted...
False
OK 0.06s
Installing BusyBox (temporary)... - Step #1
2027 KB/s (1062992 bytes in 0.512s)
OK 0.56s
Installing BusyBox (temporary)... - Step #2
OK 0.03s
Rooting device... - Step #1
cannot stat 'C:\Users\myacirkhan\Downloads\Compressed\Super_One_Click_Root\Super One Click Root\Exploits\psneuter': No such file or directory
OK 0.05s
Rooting device... - Step #2
Unable to chmod /data/local/tmp/psneuter: No such file or directory
OK 0.03s
Rooting device... - Step #3
OK 0.01s
Rooting device... - Step #4
./psneuter: not found
FAILED
Click to expand...
Click to collapse
go this post both the soc and update.zip methods are explained also an update.zip to root get s5570i
http://forum.xda-developers.com/showpost.php?p=20253964&postcount=6
I used revolutionary to get S-OFF on my Incredible S. I'm trying to install blackrose. It gives the following "permission denied" error.
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1765 KB/s (1048576 bytes in 0.580s)
/dev/block/mmcblk0p18: cannot open for write: Permission denied
< waiting for device >
erasing 'cache'...
OKAY [ 0.217s]
finished. total time: 0.218s
Any help would be appreciated.
quark020 said:
I used revolutionary to get S-OFF on my Incredible S. I'm trying to install blackrose. It gives the following "permission denied" error.
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1765 KB/s (1048576 bytes in 0.580s)
/dev/block/mmcblk0p18: cannot open for write: Permission denied
< waiting for device >
erasing 'cache'...
OKAY [ 0.217s]
finished. total time: 0.218s
Any help would be appreciated.
Click to expand...
Click to collapse
Are you rooted?
Sorry.. it was not. my bad.
Hey folks, sorry to dig up an old post, but I'm running into the same issue.
I've got hboot 6.13.1002 s-off with radio 3805.04.03.27_M. Using Revolutionary.
I've got CWM and superuser on, used Titanium backup, and installed busybox.
Doesn't this mean I'm rooted? Or am I missing some pretty obvious things here...
TheMegosh said:
Hey folks, sorry to dig up an old post, but I'm running into the same issue.
I've got hboot 6.13.1002 s-off with radio 3805.04.03.27_M. Using Revolutionary.
I've got CWM and superuser on, used Titanium backup, and installed busybox.
Doesn't this mean I'm rooted? Or am I missing some pretty obvious things here...
Click to expand...
Click to collapse
of course you are rooted and you are not missing anything.
but try root check app from play store
TheMegosh said:
Hey folks, sorry to dig up an old post, but I'm running into the same issue.
I've got hboot 6.13.1002 s-off with radio 3805.04.03.27_M. Using Revolutionary.
I've got CWM and superuser on, used Titanium backup, and installed busybox.
Doesn't this mean I'm rooted? Or am I missing some pretty obvious things here...
Click to expand...
Click to collapse
Theoretically yes, practically maybe.
Run this app https://play.google.com/store/apps/details?id=eu.thedarken.rootvalidator and all your question will be answered...
Surajkumar said:
of course you are rooted and you are not missing anything.
Click to expand...
Click to collapse
Using Root Validator, everything is green, "Your device is successfully rooted".
Well... I was getting permission errors, opened recovery, reformatted the phone, cleared cache, restarted. Then blackrose installer worked!
The installer seemed to have worked, though I got an error at the end. Restarting my phone, reformatting, formatting cache, shows the phone is still on hboot 6.13 and not blackrose...?
-------------------------------
| Incredible S BlackRose 120602 |
| Made by Lecahel(XDA-dla5244) |
| Dok-Do belongs to KOREA |
-------------------------------
Do at your own risk
Your INS(USB Debugging ON) should be connected to PC
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* Waiting for device... *
* Installing BlackRose *
2645 KB/s (1116332 bytes in 0.412s)
2515 KB/s (1048576 bytes in 0.407s)
586 KB/s (2402 bytes in 0.004s)
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.212922 seconds, 4.7MB/s
* Failed to verify blackrose image *
0 KB/s (2 bytes in 0.005s)
Click to expand...
Click to collapse
EDIT: Installed cyanogen 7.1, Blackrose install worked flawlessly. I guess it was the stock GB rom that was causing issues. Flashing ICS now.
I'm trying to root a new Droid 4 for a friend. I rooted one a month or so ago using Motofail without any trouble. But it's not working for me this time.
I'm running Windows 7 x64.
I installed the latest Motorola drivers.
I connected the phone to USB cable and let it install all the drivers with USB Debugging enabled and with it disabled. I did both in Charge only and Mass Storage.
One thing that is unusual in this situation is that the phone hasn't been activated with Verizon. I'm doing this so my friend can keep using his old phone until I have this one set up. I've done this in the past with several Droid Razrs but the other Droid 4 I rooted was already activated. If you think this is causing the trouble, let me know.
Model Number: DROID4
System Version: 6.13.215.XT894
Android Version: 2.3.6
Build Number: 6.5.1_167_DR4-1_M-215
I get the following in command prompt when attempting to root:
[*]
[*] Motofail: Universal Motorola Android Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
682 KB/s (501292 bytes in 0.717s)
[*] Owning phone...
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.
[*] Rebooting device...
[*] Waiting for phone to reboot.
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
[*] Attemping persistence...
adb server is out of date. killing...
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
[*] Cleaning up...
error: device not found
error: device not found
[*] Rebooting...
error: device not found
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
Can anyone help me? I know you can...
Sounds like your Motorola USB drivers are nonexistent or outdated. I would download the latest USB drivers and try it again. You cannot just go by the drivers Windows 7 downloads, you need to download them from the Motorola website.
---------- Post added at 09:45 PM ---------- Previous post was at 09:43 PM ----------
Here's that link:
http://www.motorola.com/Support/US-EN/Support-Homepage/Software_and_Drivers/USB-and-PC-Charging-Drivers
Thanks for the reply. I downloaded the latest drivers and restarted the computer and now I get this...
[*]
[*] Motofail: Universal Motorola Android Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
adb server is out of date. killing...
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
550 KB/s (501292 bytes in 0.889s)
[*] Owning phone...
adb server is out of date. killing...
* daemon started successfully *
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.
[*] Rebooting device...
adb server is out of date. killing...
* daemon started successfully *
[*] Waiting for phone to reboot.
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (no status)
[*] Attemping persistence...
adb server is out of date. killing...
* daemon started successfully *
error: device not found
failed to copy 'su' to '/system/bin/su': Read-only file system
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/bin/su: No such file or directory
adb server is out of date. killing...
* daemon started successfully *
link failed Read-only file system
* daemon not running. starting it now *
* daemon started successfully *
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Cleaning up...
adb server is out of date. killing...
* daemon started successfully *
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.
[*] Rebooting...
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
It seems to me to go okay until the phone reboots... at that point the phone trys to activate and I wonder if that's messing up the system. Unless someone has a better solution, I'm going to activate the phone and then try it to see if it will make a difference.
Are you giving the program admin rights?
Sent from my DROID4 using Tapatalk 2
I give admin rights by right-clicking on run.bat and selecting Run as administrator? If yes, I've tried that. The problem isn't specific to Droid 4 as I just now tried rooting a Razr with the same results. It's telling me my "adb server is out of date" and then "device not found".
Can any of you guys tell me how to figure out where the problem is and fix it? It's weird because I've rooted 8 Razrs and 1 D4 before without a problem...
Unroot and reroot.
Sent from my DROID4 using Tapatalk 2
I was never rooted so how can I unroot?
Also make sure your phone is in charge only mode, and the screen is unlocked and on when the process begins.
Yes my phone was in Charge only with screen unlocked.
Thanks to all who are responding!
Try using the Droid 4 utility instead of just Motofail.
Then, like papi was saying, try running the unroot process to get rid of any trace of the exploit. You may want to boot into fastboot and run a data/cache wipe at this point. Then, run the root option again.
I got it guys!!! I copied five files from the Motofail folder: busybox, motofail, run.bat, su and Superuser.apk to my Android-sdk\platform-tools\ folder. I then ran run.bat as an Adminstrator and everything went off without a hitch. Yay!!!
But please, can someone tell me why it worked. I would really like to use this as a learning experience because I just spent a frustrating 8 hours or so fussing with this.
Thanks guys!
mrbuilder
It could have been that somehow the program couldnt find those files in the previous directory
Sent from my DROID4 using Tapatalk 2
Quick noob question everyone, if I have an unlocked bootloader and custom recovery, am I rooted? Because busybox and superuser still aren't giving me command prompts. I'm on stock ics
Sent from my HTC PH39100 using XDA
Long story short no your not rooted but you did the hard part already just follow this guide you'll be rooted in under 2 minutes http://forum.xda-developers.com/showthread.php?t=1498003
THANKS!
Sent from my HTC PH39100 using XDA
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.
I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.
I've been up and down the Android and Vivid forums on different websites, but can't find the answer.
I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.
Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.
FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
MMVXIII said:
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.
I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.
I've been up and down the Android and Vivid forums on different websites, but can't find the answer.
I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.
Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.
FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Adb isn't set up properly or may need to ne run as administrator
Sent from my HTC PH39100 using xda premium
MMVXIII said:
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.
I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.
I've been up and down the Android and Vivid forums on different websites, but can't find the answer.
I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.
Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.
FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
Click to expand...
Click to collapse
When using the all in one tool did you boot into bootloader when trying to perm root if it didn't automatically do it for you.
If you could get back to stick gb, Google zergrush root. Its a tempt root for users who still have their boot loader locked. But in your case, it should be locked.
Sent from my HTC PH39100 using XDA
jigajay said:
When using the all in one tool did you boot into bootloader when trying to perm root if it didn't automatically do it for you.
Click to expand...
Click to collapse
All In One automatically reboots into recovery, runs the batch then responds with "device not found" after each command.
I did try what you said. I booted into bootloader, then ran the perm root from AIO, but got the same "device not found" result.
---------- Post added at 05:46 PM ---------- Previous post was at 05:10 PM ----------
After much reading, booting and rebooting, I managed to get this response from All In One:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
* server not running *
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
349 KB/s (22364 bytes in 0.062s)
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
4800 KB/s (843503 bytes in 0.171s)
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
However, no still no root. I've kept up to date with the AIO forum. Read the "under construction SuperGuide cover to cover. I have done exactly what many others have, except no joy for me. It appears I may have the only AT&T Vivid in the world that will not root.
http://forum.xda-developers.com/showthread.php?t=1529669
Flash that in boot loader. If it says update presses yes then you're back to gingerbread.
Sent from my HTC PH39100 using XDA
http://forum.xda-developers.com/showthread.php?t=1341162
Use that to root your phone. Follow instructions carefully.
Sent from my HTC PH39100 using XDA
I try revone to get s-off and every command comes successful, but when I go to bootloader still s-on
first step :
HTML:
C:\ADB + Fastboot + Drivers>adb reboot
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\ADB + Fastboot + Drivers>adb reboot
adb server is out of date. killing...
* daemon started successfully *
C:\ADB + Fastboot + Drivers>adb push revone /data/local/tmp/
adb server is out of date. killing...
* daemon started successfully *
2434 KB/s (648208 bytes in 0.259s)
C:\ADB + Fastboot + Drivers>adb shell
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 revone
chmod 755 revone
[email protected]:/data/local/tmp # su
su
[email protected]:/data/local/tmp # ./revone -P
./revone -P
revone v0.2.1
revone failed (error code = 1)
1|[email protected]:/data/local/tmp # ./revone -p
./revone -p
./revone: invalid option -- 'p'
revone v0.2.1
revone successful.
[email protected]:/data/local/tmp #
C:\ADB + Fastboot + Drivers>
second step :
HTML:
C:\ADB + Fastboot + Drivers>adb shell
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1
revone successful.
[email protected]:/data/local/tmp # adb reboot bootloader
adb reboot bootloader
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/data/local/tmp # exit
exit
C:\ADB + Fastboot + Drivers>adb reboot bootloader
C:\ADB + Fastboot + Drivers>
1- I try in win 8.1 and win 7 64bit same successful and in bootloader still s-on
2- I try in ubuntu 32bit same successful and in bootloader still s-on
and I try with stock ROM 4.4.3 non rooted and rooted, and ARHD 31.6 ROM
also I was try firewater I get syntax error.
and also I was try runrummer and get fail.
about my phone:
Hboot 1.56
unlocked by htcDev s-on
recovery twrp-2.8.4.0-m7
last thing: when I want to install any ROM I don't need to flash Boot.img from fastboot
I hoop some one help me
azoz123456 said:
I try revone to get s-off and every command comes successful, but when I go to bootloader still s-on
first step :
HTML:
C:\ADB + Fastboot + Drivers>adb reboot
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\ADB + Fastboot + Drivers>adb reboot
adb server is out of date. killing...
* daemon started successfully *
C:\ADB + Fastboot + Drivers>adb push revone /data/local/tmp/
adb server is out of date. killing...
* daemon started successfully *
2434 KB/s (648208 bytes in 0.259s)
C:\ADB + Fastboot + Drivers>adb shell
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 revone
chmod 755 revone
[email protected]:/data/local/tmp # su
su
[email protected]:/data/local/tmp # ./revone -P
./revone -P
revone v0.2.1
revone failed (error code = 1)
1|[email protected]:/data/local/tmp # ./revone -p
./revone -p
./revone: invalid option -- 'p'
revone v0.2.1
revone successful.
[email protected]:/data/local/tmp #
C:\ADB + Fastboot + Drivers>
second step :
HTML:
C:\ADB + Fastboot + Drivers>adb shell
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1
revone successful.
[email protected]:/data/local/tmp # adb reboot bootloader
adb reboot bootloader
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/data/local/tmp # exit
exit
C:\ADB + Fastboot + Drivers>adb reboot bootloader
C:\ADB + Fastboot + Drivers>
1- I try in win 8.1 and win 7 64bit same successful and in bootloader still s-on
2- I try in ubuntu 32bit same successful and in bootloader still s-on
and I try with stock ROM 4.4.3 non rooted and rooted, and ARHD 31.6 ROM
also I was try firewater I get syntax error.
and also I was try runrummer and get fail.
about my phone:
Hboot 1.56
unlocked by htcDev s-on
recovery twrp-2.8.4.0-m7
last thing: when I want to install any ROM I don't need to flash Boot.img from fastboot
I hoop some one help me
Click to expand...
Click to collapse
HBOOT 1.56 and above requires Sunshine to s-off for which you will have to pay $25 http://theroot.ninja/
However if you are just looking to flash custom rom's, you can do this s-on, no need to flash the boot.img separately, this is all done during the flash, you just cant use GPe rom's whilst s-on.
Seanie280672 said:
HBOOT 1.56 and above requires Sunshine to s-off for which you will have to pay $25 http://theroot.ninja/
However if you are just looking to flash custom rom's, you can do this s-on, no need to flash the boot.img separately, this is all done during the flash, you just cant use GPe rom's whilst s-on.
Click to expand...
Click to collapse
thanks for replay
1- is there any way to downgrade Hboot to 1.54 ? and is it possible to do s-off when Hboot version is 1.54 ?
2- about GPE I can flash it without problem
3- the problem is I need to upgrade firmware
so is there any way to do S-off without pay ? because I don't have any credit card or something like this
thank you again
azoz123456 said:
thanks for replay
1- is there any way to downgrade Hboot to 1.54 ? and is it possible to do s-off when Hboot version is 1.54 ?
Click to expand...
Click to collapse
You can't downgrade hboot to achieve s-off because s-off is required to downgrade hboot.
---------- Post added at 12:41 AM ---------- Previous post was at 12:39 AM ----------
azoz123456 said:
2- about GPE I can flash it without problem
Click to expand...
Click to collapse
Some GPE roms require s-off (e.g arhd 6.1)
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
azoz123456 said:
3- the problem is I need to upgrade firmware
Click to expand...
Click to collapse
Why do you need to upgrade your firmware?
so is there any way to do S-off without pay ?
Click to expand...
Click to collapse
Not on your hboot version.
azoz123456 said:
thanks for replay
1- is there any way to downgrade Hboot to 1.54 ? and is it possible to do s-off when Hboot version is 1.54 ?
2- about GPE I can flash it without problem
3- the problem is I need to upgrade firmware
so is there any way to do S-off without pay ? because I don't have any credit card or something like this
thank you again
Click to expand...
Click to collapse
However you can upgrade your firmware as long as it matches exactly your current firmware or the next one up.
Which rom do you want to flash
alray said:
You can't downgrade hboot to achieve s-off because s-off is required to downgrade hboot.
---------- Post added at 12:41 AM ---------- Previous post was at 12:39 AM ----------
Some GPE roms require s-off (e.g arhd 6.1)
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Why do you need to upgrade your firmware?
Not on your hboot version.
Click to expand...
Click to collapse
thanks for replay..
I need to upgrade my firmware to achieve all recommended in MaximusHD ROM, and I can use it without any problem but I want to achieve all recommended by developer
Why? I don't know
but I think it will give me more stability.
If I upgrade Hboot to 1.57 it can be s-off?
Seanie280672 said:
However you can upgrade your firmware as long as it matches exactly your current firmware or the next one up.
Which rom do you want to flash
Click to expand...
Click to collapse
this ROM [ROM] MaximusHD | 50.0.0 | Android 5.0.2 | Sense 6.0 | EYE |OTA | 7.15.401.1
thanks for replay
azoz123456 said:
If I upgrade Hboot to 1.57 it can be s-off?
Click to expand...
Click to collapse
Seanie already told you (post #2) hboot 1.56 and above can be s-off'ed using sunshine only.
alray said:
Seanie already told you (post #2) hboot 1.56 and above can be s-off'ed using sunshine only.
Click to expand...
Click to collapse
ok thanks brother. I will try to find a way to bay 25$
and what about upgrade firmware to ( 7.15.401.1 ), It will give me more stability?