I have a v6 stock phone, no root, no cwm. Thought I would run through the ADB manual method of root to see what happens. I get to this point...
Code:
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
When I try to do the SU because I get the $ I get Permissions denied.
I know that this method does not work but I wanted to see where it fails. It appears that they may have fixed the glitch that allowed the rage exploit to work.
I also tried cubes other way and it failed as well.
Code:
Open ADB shell
Your command prompt should be "$"
Run
kill `busybox pidof adbd`
Re-run ADB shell, your command prompt should change to "#"
Just thought I would toss this out there in case someone wanted to know...
Thanks for the heads up on this good info to know when I get my rev on Saturday
Sent from my SHIFTAO5P using XDA Premium App
Haxcid said:
I have a v6 stock phone, no root, no cwm. Thought I would run through the ADB manual method of root to see what happens. I get to this point...
Just thought I would toss this out there in case someone wanted to know...
Click to expand...
Click to collapse
Mm, I went through that last night, then downgraded to the V4 software as shown by the other post - still, none of it worked for me.
Pull your SDcard out when trying to root after the downgrade. Or format the SD card. It should work then.
Guys, I have a problem with my HTC One M7. I am trying to unlock the bootloader using the HTCDev guide (available at htcdev site).
But suddenly I am not able to complete Step 8 (running command "fastboot oem get_identifier_token").
Command "fastboot devices" shows my phone in a fastboot mode:
\> fastboot devices
mt6589_phone_720pv2 fastboot
But none of fastboot oem commands executes successfully (including "get_identifier_token").
Instead I get only three dots ("...") and nothing changes after that:
\> fastboot oem get_identifier_token
...
Other commands (like fastboot reboot) function, but not "fastboot oem get_identifier_token". I can't unlock my bootloader, could you please help!
andrey o said:
Guys, I have a problem with my HTC One M7. I am trying to unlock the bootloader using the HTCDev guide (available at htcdev site).
But suddenly I am not able to complete Step 8 (running command "fastboot oem get_identifier_token").
Command "fastboot devices" shows my phone in a fastboot mode:
\> fastboot devices
mt6589_phone_720pv2 fastboot
But none of fastboot oem commands executes successfully (including "get_identifier_token").
Instead I get only three dots ("...") and nothing changes after that:
\> fastboot oem get_identifier_token
...
Other commands (like fastboot reboot) function, but not "fastboot oem get_identifier_token". I can't unlock my bootloader, could you please help!
Click to expand...
Click to collapse
Never seen that before but since we have S-off now you can unlock the bootloader without HTCDev
check out the revone thread in the Original Development section.
If you're using Windows 8, I would use the following link that I've seen floating around here"
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
I had issues getting the token for mine until I used that guide to convert my Microsoft USB 3.0 drivers into Intel drivers.
gunnyman said:
Never seen that before but since we have S-off now you can unlock the bootloader without HTCDev
check out the revone thread in the Original Development section.
Click to expand...
Click to collapse
Thanks for this advice, I am now trying to do it with revone.
I have successfully pushed the file to the phone, but when executing adb shell commands I get a error:
"- exec '/system/bin/sh' failed: No such file or directory"
How to fix it?
andrey o said:
Thanks for this advice, I am now trying to do it with revone.
I have successfully pushed the file to the phone, but when executing adb shell commands I get a error:
"- exec '/system/bin/sh' failed: No such file or directory"
How to fix it?
Click to expand...
Click to collapse
Not sure, but the folks in that thread are super helpful
you're in an ADB shell when you execute the command?
gunnyman said:
Not sure, but the folks in that thread are super helpful
you're in an ADB shell when you execute the command?
Click to expand...
Click to collapse
Yes, I am now reading that thread to find the answer.
Here's what i do and what I get:
> adb devices
List of devices attached
0123456789ABCDEF recovery
> adb push revone /data/local/tmp/
4584 KB/s (648208 bytes in 0.138s)
>adb shell cd /data/local/tmp
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -
Start the shell. Then do the cd command separately
gunnyman said:
Start the shell. Then do the cd command separately
Click to expand...
Click to collapse
same result
> adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -
Is the phone in recovery or booted up? Needs to be booted
gunnyman said:
Is the phone in recovery or booted up? Needs to be booted
Click to expand...
Click to collapse
It was in recovery mode - my mistake, thank you for pointing.
I have booted it and executed the needed commands, but still another mistake:
>sudo adb shell
[email protected]:/ # cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 revone
[email protected]:/data/local/tmp # ./revone -P
revone v0.2.1
revone failed (error code = 1)
1|[email protected]:/data/local/tmp #
Step by step I am coming closer to the result, thanks so much for your help
[Q] change "relocked" to "locked" when putting phone back to stock?
I followed this thread but mine says "relocked" and it still says S-OFF. is it possible to get it to say "locked" without going through the whole process of unlocking, rooting, and using revone again?
I'm sending my phone back to get the screen replaced which isn't under warranty, so does it even matter that it says "relocked?"
mcarswell said:
I followed this thread but mine says "relocked" and it still says S-OFF. is it possible to get it to say "locked" without going through the whole process of unlocking, rooting, and using revone again?
I'm sending my phone back to get the screen replaced which isn't under warranty, so does it even matter that it says "relocked?"
Click to expand...
Click to collapse
Use revone -l to change back to "locked"
There is not a way without rerooting for Tue device to day say locked and not relocked BUT you can easily get rid of S-Off. It doesn't take long either...
1.) Reroot.
2.) Download revone to computer.
3.) Navigate Using Command Prompt to where revone file is located on computer and move the Downloaded file to /data/local/tmp using the command "adb push revone /data/local/tmp" without quotations while phone is booted into OS and connected to computer.
3.) Use Command Prompt with phone connected to computer to run these commands or you can use Terminal Emulator app without a computer but will need a computer later on to run RUU again...
3A.) adb shell
3B.) su(SU Will Now Request SU Access For ADB Shell, Grant It)
3C.) cd /data/local/tmp
3D.) chmod 755 revone
4.) Reboot device
5.) Once device is fully booted back up run these commands again while connected to computer
5A.) adb shell
5B.) su(Will Not Need To Request Access Again)
5C.) cd /data/local/tmp
5D.) ./revone -P(If It Tells You "No Need To Reboot" Then Move On To Step 7 And If It Tells You To "Reboot To Continue" Move On To Step 6).
6.) Reboot
7.) Once fully booted back into OS open another command prompt and run these commands with Command Prompt while connected to computer.
7A.) adb shell
7B.) su
7C.) cd /data/local/tmp
7D.) ./revone -s 0 -u(To Be Safe).
7E.) Reboot
8.) Once again open another command prompt window and run these commands
8A.) adb shell
8B.) su
8C.) cd /data/local/tmp
8D.) ./revone -t -l
9.) Reboot
10.) Run RUU And Allow It To Successfully Complete.
11.) Once booted back into OS open command prompt and type in the final two commands
11A.) adb reboot bootloader
12.) Once it boots into bootloader and recognizes device type in this command
12A.) fastboot oem writesecureflag e
Sent from my HTCONE using Tapatalk 4
Hello,
I have rooted my phone with custom ROM, I am selling my phone back to the provder and need to unroot and back to standard ROM.
How do i do this?? Also how do i do the counter back to 0 so they know it hasn't been rooted??
Thank you
coolfreebies
coolfreebies said:
Hello,
I have rooted my phone with custom ROM, I am selling my phone back to the provder and need to unroot and back to standard ROM.
How do i do this?? Also how do i do the counter back to 0 so they know it hasn't been rooted??
Thank you
coolfreebies
Click to expand...
Click to collapse
First thing, are you S-Off?
If not you will only be able to get RELOCKED, not LOCKED. So that's a dead giveaway.
nkk71 said:
First thing, are you S-Off?
If not you will only be able to get RELOCKED, not LOCKED. So that's a dead giveaway.
Click to expand...
Click to collapse
Its says S-ON What does that mean??
Thank you
coolfreebies
coolfreebies said:
Its says S-ON What does that mean??
Thank you
coolfreebies
Click to expand...
Click to collapse
It means you're phone is Security On. Since you've unlocked the bootloader it probably says "UNLOCKED" and "TAMPERED", even if you go back to stock rom and stock recovery and lock your phone, it will show as "RELOCKED" (not sure if TAMPERED will go away, as there are conflicting reports about that).
The only way to really get your phone not to show any evidence of being unlocked, you would need to use revone to get it to show "LOCKED". In order to use revone, you would need to be on hboot 1.44 as hboot 1.54+ have been patched so that revone no longer works.
nkk71 said:
It means you're phone is Security On. Since you've unlocked the bootloader it probably says "UNLOCKED" and "TAMPERED", even if you go back to stock rom and stock recovery and lock your phone, it will show as "RELOCKED" (not sure if TAMPERED will go away, as there are conflicting reports about that).
The only way to really get your phone not to show any evidence of being unlocked, you would need to use revone to get it to show "LOCKED". In order to use revone, you would need to be on hboot 1.44 as hboot 1.54+ have been patched so that revone no longer works.
Click to expand...
Click to collapse
I am on HB 1.44.0000
Thank you for your advice
coolfreebies
coolfreebies said:
I am on HB 1.44.0000
Thank you for your advice
coolfreebies
Click to expand...
Click to collapse
Do some reading of the guides including revone's s-off, vomer's guide to s-off, etc.
Once you are comfortable with the procedure go ahead and S-Off. Then you'll be able to fully restore your device.
A note of advise (at your discretion of course) keep S-Off even after you fully go back to stock, as some phones do actually ship with S-Off.
Hit thanks of i helped
Have read very carefully but can't get past this part:
./revone -s 0 -u
Any suggestions
Thank you
coolfreebies
coolfreebies said:
Have read very carefully but can't get past this part:
./revone -s 0 -u
Any suggestions
Thank you
coolfreebies
Click to expand...
Click to collapse
Have you read this: http://forum.xda-developers.com/showthread.php?t=2431515
What's the error message you are receiving? Give us detailed output from the beginning of your adb shell.
EDIT: what custom ROM are you using, if it's 4.3 based it's a no go. download one that is either 4.1.2 (better) or 4.2.2 (should work also)
nkk71 said:
Have you read this: http://forum.xda-developers.com/showthread.php?t=2431515
What's the error message you are receiving? Give us detailed output from the beginning of your adb shell.
EDIT: what custom ROM are you using, if it's 4.3 based it's a no go. download one that is either 4.1.2 (better) or 4.2.2 (should work also)
Click to expand...
Click to collapse
Phone is 4.1.2
Sense 5.0
Mac/Linux: adb push /Users/vomer/Desktop/revone /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 revone
./revone -P (Revone successful) Asks for a reboot
adb shell
cd /data/local/tmp
./revone -P (Waiting for a reboot of phone)
adb shell
cd /data/local/tmp
./revone -s 0 -u - revone failed (error code = -1) This is where i get stuck
Thank you
coolfreebies
coolfreebies said:
Phone is 4.1.2
Sense 5.0
Mac/Linux: adb push /Users/vomer/Desktop/revone /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 revone
./revone -P (Revone successful) Asks for a reboot
adb shell
cd /data/local/tmp
./revone -P (Waiting for a reboot of phone)
adb shell
cd /data/local/tmp
./revone -s 0 -u - revone failed (error code = -1) This is where i get stuck
Thank you
coolfreebies
Click to expand...
Click to collapse
Not on my pc right now, I'll try to come back later. But -1 doesn't sound like too big of a problem, keep trying, it took some people up to 50 retries before it actually worked.
Head over to the s-off thread where u can see some other experiences.
Sent from my HTC One using xda app-developers app
coolfreebies said:
Phone is 4.1.2
Sense 5.0
Mac/Linux: adb push /Users/vomer/Desktop/revone /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 revone
./revone -P (Revone successful) Asks for a reboot
adb shell
cd /data/local/tmp
./revone -P (Waiting for a reboot of phone)
adb shell
cd /data/local/tmp
./revone -s 0 -u - revone failed (error code = -1) This is where i get stuck
Thank you
coolfreebies
Click to expand...
Click to collapse
Just gotta keep doing it, it will eventually work (took me about 20 minutes to do it with my phone). You just have to keep running the S-OFF command again, not the whole process
coolfreebies said:
Phone is 4.1.2
Sense 5.0
Mac/Linux: adb push /Users/vomer/Desktop/revone /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 revone
./revone -P (Revone successful) Asks for a reboot
adb shell
cd /data/local/tmp
./revone -P (Waiting for a reboot of phone)
adb shell
cd /data/local/tmp
./revone -s 0 -u - revone failed (error code = -1) This is where i get stuck
Thank you
coolfreebies
Click to expand...
Click to collapse
+1 what EddyOS said
Once you "./revone -P", and it gives you success, reboot the phone and start running " ./revone -s 0 -u" until it succeeds.
nkk71 said:
+1 what EddyOS said
Once you "./revone -P", and it gives you success, reboot the phone and start running " ./revone -s 0 -u" until it succeeds.
Click to expand...
Click to collapse
Thank you... I have been trying to do this for an hour now and no luck... I have gone from Erro 1 to Erro 2 now.
Any suggestion??
Thank you for your help...
coolfreebies
coolfreebies said:
Thank you... I have been trying to do this for an hour now and no luck... I have gone from Erro 1 to Erro 2 now.
Any suggestion??
Thank you for your help...
coolfreebies
Click to expand...
Click to collapse
From what I've read, but remember each user experience is different, try some of the following: (I know it's tedious, but if/when you get S-Off it's well worth it):
1- Try a different Sense 5 ROM 4.1.2 and/or try 4.2.2; I've even seen someone use a GPe 4.2.2 ROM and it worked
2- are you rooted? could improve chances, using "su" in the shell
3- try running the commands using terminal emulator directly on the phone; for some that worked, whereas adb didnt
So far error -1 and error -2 aren't a failure; from @The War Horse:
Code:
Error Code -1 = Potentially you need to try a different ROM or it could just be random and after a few tries and reboots it might work. A few people have reported that rebooting and using -p rather than -P has worked but I'm not convinced as -p isn't built as a command but you're free to try whatever you wish.
Error Code -2 = I've seen people report this but revone has actually worked so should you see this try and reboot and carry on, if not then try changing ROMs and try again.
Reboot, factory reset, start from the beginning again, etc etc you should get it working PLEASE :fingers-crossed:
I know it's a hassle, for some it works from the first time, for others it takes 50 times and many reboots.
PERSONALLY, I achieved S-Off while being unlocked, rooted, and on ARHD 8.x or 9.x (can't remember )
Keep going, you'll get there :fingers-crossed:
nkk71 said:
From what I've read, but remember each user experience is different, try some of the following: (I know it's tedious, but if/when you get S-Off it's well worth it):
1- Try a different Sense 5 ROM 4.1.2 and/or try 4.2.2; I've even seen someone use a GPe 4.2.2 ROM and it worked
2- are you rooted? could improve chances, using "su" in the shell
3- try running the commands using terminal emulator directly on the phone; for some that worked, whereas adb didnt
So far error -1 and error -2 aren't a failure; from @The War Horse:
Code:
Error Code -1 = Potentially you need to try a different ROM or it could just be random and after a few tries and reboots it might work. A few people have reported that rebooting and using -p rather than -P has worked but I'm not convinced as -p isn't built as a command but you're free to try whatever you wish.
Error Code -2 = I've seen people report this but revone has actually worked so should you see this try and reboot and carry on, if not then try changing ROMs and try again.
Reboot, factory reset, start from the beginning again, etc etc you should get it working PLEASE :fingers-crossed:
I know it's a hassle, for some it works from the first time, for others it takes 50 times and many reboots.
PERSONALLY, I achieved S-Off while being unlocked, rooted, and on ARHD 8.x or 9.x (can't remember )
Keep going, you'll get there :fingers-crossed:
Click to expand...
Click to collapse
Thank you for all that info... Will read though it now... But now my phone is stuck on the boot up screen, shall i try a factory reset bootlocker?
Thank you
coolfreebies
coolfreebies said:
Thank you for all that info... Will read though it now... But now my phone is stuck on the boot up screen, shall i try a factory reset bootlocker?
Thank you
coolfreebies
Click to expand...
Click to collapse
Stuck on bootloader? did u try "fastboot erase cache"
my laptop battery going dead... sorry ... c u tomorrow, hopefully with s-off
Hey,
Thank you so much for all your help it is much appreciated...
I tried using "su" in the shell but it kept aking me for a password and i am not sure what it could be...
Thank you
coolfreebies
coolfreebies said:
Hey,
Thank you so much for all your help it is much appreciated...
I tried using "su" in the shell but it kept aking me for a password and i am not sure what it could be...
Thank you
coolfreebies
Click to expand...
Click to collapse
Hi coolfreebies, did you get it working? Just curious
nkk71 said:
Hi coolfreebies, did you get it working? Just curious
Click to expand...
Click to collapse
Morning nkk71,
Nope didn't get it to work. I was trying for about 3 hours and i just gave up as it was getting to frustrating.
Gonna give it another go now.
Cheers
coolfreebies
Hey,
I managed to get ./revone -s 0 -u DONE... Yippy
Now i am stuck on ./revone -t fingers crossed it will work soon...
Thank you
coolfreebies
Hello forum. First experience with this device.
Software Version 7.4.8
ADB drivers working, finds device.
No factory Cable.
"adb shell reboot bootloader" returns /system/bin/sh: su Reboot-bootloader: Not found
"adb shell" returns prompt with "$"
"su" command returns "Operation not permitted"
Do I need to be root before I can get into fastboot?
I want to use fastboot to downgrade to version 7.2.3 in order to properly flash the second bootloader.
Thanks for your feedback.
FillTheVoid said:
Hello forum. First experience with this device.
Software Version 7.4.8
ADB drivers working, finds device.
No factory Cable.
"adb shell reboot bootloader" returns /system/bin/sh: su Reboot-bootloader: Not found
"adb shell" returns prompt with "$"
"su" command returns "Operation not permitted"
Do I need to be root before I can get into fastboot?
I want to use fastboot to downgrade to version 7.2.3 in order to properly flash the second bootloader.
Thanks for your feedback.
Click to expand...
Click to collapse
Nope, type "adb reboot bootloader"
FillTheVoid said:
Hello forum. First experience with this device.
Software Version 7.4.8
ADB drivers working, finds device.
No factory Cable.
"adb shell reboot bootloader" returns /system/bin/sh: su Reboot-bootloader: Not found
"adb shell" returns prompt with "$"
"su" command returns "Operation not permitted"
Do I need to be root before I can get into fastboot?
I want to use fastboot to downgrade to version 7.2.3 in order to properly flash the second bootloader.
Thanks for your feedback.
Click to expand...
Click to collapse
You need to be rooted, have the SDK package downloaded and the environment set up (set paths) and then CD from the tools folder and issue the command "adb shell su -c reboot bootloader"
Edit: Do I all in one line with no quotations. This is the way to access the bootloader on a Kindle with no factory cord.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
---------- Post added at 09:15 PM ---------- Previous post was at 09:04 PM ----------
stunts513 said:
Nope, type "adb reboot bootloader"
Click to expand...
Click to collapse
You need to be rooted, have the SDK package downloaded and the environment set up (set paths) and then CD from the tools folder and issue the command "adb shell su -c reboot bootloader" Probably don't have too set paths when CD but it's a good thing to do.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app