Database Develop

Root without custom recovery?

Can you root the One without installing a custom recovery? I want to root my buddies phone, but I don't want to put a custom recovery on because I want him to be able to take OTA updates. I know this is possible on some Samsung phones, but I'm not sure it can be done on HTC phones?

You can s-off and after it gets root and you have s-off, (after you run revone -s 0) then:
Code:
adb remount
adb push su /system/xbin/su
adb shell chmod 04755 /system/xbin/su
Then you just simply install the SuperUser app from the playstore.

Root simply means that you have access to superuser privileges, aka, power to change anything in the "root".
It had nothing to do with custom recovery, although it is common to see both together.
This is also possible on practically any phone, it's not brand-specific.
Note that there are easier ways for people to take OTAs though. As it can fail even if you still have stock recovery installed.
Someone usually posts the stock rooted update within a day or two of its release, and that's the easiest way of updating IMO. Taking the OTA while rooted will either fail, flash and remove root, or just flash normally.

Indirect said:
You can s-off and after it gets root and you have s-off, (after you run revone -s 0) then:
Code:
adb remount
adb push su /system/xbin/su
adb shell chmod 04755 /system/xbin/su
Then you just simply install the SuperUser app from the playstore.
Click to expand...
Click to collapse
Wouldn't we have to download the SU.apk before pushing to the phone?

toomuchespresso said:
Wouldn't we have to download the SU.apk before pushing to the phone?
Click to expand...
Click to collapse
That was implied...

Thanks. I just want to clarify because I'm tired this morning, su is the same as SuperUser or SuperSU? Or is it a different apk?
EDIT: Nevermind. Forgot it's the binary.

Could anyone be more specific as to the steps necessary? Sorry, I am a bit of a noob. I already have S-OFF with revone.

leo.sutton said:
Could anyone be more specific as to the steps necessary? Sorry, I am a bit of a noob. I already have S-OFF with revone.
Click to expand...
Click to collapse
i would also appreciate some more details if possible?

revone failed (error code = -6)! ( [S-OFF] revone)

Hello, i tried a million times to solve this issue
i used those commands:
Code:
adb push revone /data/local/tmp
adb shell
cd /data/local/tmp
su
chmod 755 revone
./revone -P
doesn't work...
i also added those commands:
Code:
chown root:root revone
ls
nothing happend
can anybody help me please?
my htc one is T-mobile branded, android: 4.1.2, HBOOT: 1.44

me_rashad said:
Hello, i tried a million times to solve this issue
i used those commands:
Code:
adb push revone /data/local/tmp
adb shell
cd /data/local/tmp
su
chmod 755 revone
./revone -P
doesn't work...
i also added those commands:
Code:
chown root:root revone
ls
nothing happend
can anybody help me please?
my htc one is T-mobile branded, android: 4.1.2
Click to expand...
Click to collapse
Make sure your on a rooted rom, then run it. I would also make sure your run revone as su when you start your adb shell

Mikee4fun said:
Make sure your on a rooted rom, then run it. I would also make sure your run revone as su when you start your adb shell
Click to expand...
Click to collapse
my device is rooted
and i run revone as su.

Are you running the latest android sdk?
Sent from my HTC One using Tapatalk 2

me_rashad said:
Hello, i tried a million times to solve this issue
i used those commands:
Code:
adb push revone /data/local/tmp
adb shell
cd /data/local/tmp
su
chmod 755 revone
./revone -P
doesn't work...
i also added those commands:
Code:
chown root:root revone
ls
nothing happend
can anybody help me please?
my htc one is T-mobile branded, android: 4.1.2
Click to expand...
Click to collapse
If you put on the latest OTA then sorry you are out of luck revone will not work.

Mikee4fun said:
Are you running the latest android sdk?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
yes i just checked it.
daleski75 said:
If you put on the latest OTA then sorry you are out of luck revone will not work.
Click to expand...
Click to collapse
my software number: 1.27.531.11, android 4.1.2

Are you on 1.54 bootloader?
Sent from my HTC One using xda premium

try running revone via the computer in an adb session instead of through your terminal emulator.

oOzzy` said:
Are you on 1.54 bootloader?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
No, HBOOT: 1.44

Donjuanal said:
try running revone via the computer in an adb session instead of through your terminal emulator.
Click to expand...
Click to collapse
not working as well.

me_rashad said:
not working as well.
Click to expand...
Click to collapse
did you get help?
i have and error code 2

broffy said:
did you get help?
i have and error code 2
Click to expand...
Click to collapse
Not yet dude. still waiting to find solution

me_rashad said:
Not yet dude. still waiting to find solution
Click to expand...
Click to collapse
So it took me many times to get this to work correctly. Mostly because I was not reading the doc carefully enough. I was trying to run "revone -s 0" right away and was missing the "revone -P" step first. What I found was that it appears that if you run any revone command and it fails, your best bet is to reboot the phone to try again. I was able to finally get "revone -P" to work but only after rebooting the phone and running that as the first command. Note that I did not use su or anything else, I just ran "revone -P" in the adb shell. I was on a T-Mobile One which I successfully converted to GE. Hope this helps.
Code:
$ adb shell
[email protected]:/ $ cd /data/local/tmp
[email protected]:/data/local/tmp $ ./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful - please reboot to continue.

First off, you can try this at your own risk. I did it last night and it worked. I was on the at&t update version 1.26.502.15 which generated the same error code. INeFFeCTiVE gets all the credit on this one for getting me S-OFF after the update. Basic idea was to put a nandroid on your phone of 2 versions ago (1.26.502.10) and then lock the bootloader and run the RUU of the version just before the one that broke the exploits (1.26.502.12). Then I was able to run the All In One toolkit and obtain S-OFF. I am not sure the same will work for you, but that was my solution. I know the people with hboot 1.54 have to wait, but mine was still on 1.44 and I was getting that error code. Here is the link to the thread I followed. Again, all credit to INeFFeCTiVE.
http://forum.xda-developers.com/showthread.php?t=2394155#post44384465

me_rashad said:
Not yet dude. still waiting to find solution
Click to expand...
Click to collapse
pm me your google plus

If you are on T-Mobile, you may have accidentally applied an OTA which leaves your HBOOT at 1.44 but patches the exploit revone and moonshine use to set S-OFF.
Again, ONLY on T-Mobile, it is possible to be on HBOOT 1.44 with a patched version that will NOT allow revone or moonshine to work. Hopefully they update these tools to get around this patch. They probably will, it's likely a short matter of time.
(If you suspect you're in this situation, don't even try to apply moonshine unless you know how to restore a stock boot image. Moonshine will quit after 10 tries with an error without restoring your boot!! Moonshine *does* back up your original boot in the folder it was run from, though).

There's a previous thread like this. Error code -6 is a known bug and there is no known solutions to this.
EDIT: Here. http://forum.xda-developers.com/showthread.php?t=2395756

me_rashad said:
yes i just checked it.
my software number: 1.27.531.11, android 4.1.2
Click to expand...
Click to collapse
If you're on that software number, you're in luck! http://rootzwiki.com/topic/96098-s-offdowngrade-12753111-to-1275318/

Similar problem
I have done substantial searching on the question of overcoming revone failed error code -6 and have tried most of the troubleshooting steps (not all) without success.
However, a consistent trend I saw was the need to provide details about my specific situation, so I wanted to give that a shot before continuing to flail.
Below you'll find my Phone Details, Steps Taken, Steps Not Taken, and Known Potential Issues
Phone Details
If I provided more information than is needed, please forgive the over-thoroughness. If I'm missing something, please let me know.
Carrier: T-Mobile
Build number: 2.24.401.8 CL235216 release-keys
Baseband version: 4A.17.3250.20_10.40.1150.04L
Kernel Version: 3.4.10-g28df0d6 [email protected] #1 SMP PREEMPT
Android Version: 4.2.2
HTC SDK API Level: 5.34
Software Number: MaximusHD 11.0.0
Statuses: Tampered, Unlocked, S-ON (M7_UL_PVT SHIP S-ON RH, Fastboot
HBOOT: 1.44.0000 June 21 2013, 20:19:45:-1
OpenDSP: v31.120.274.0617
Recovery: TWRP 2.5.0.0
IMAGE CRC Output:
Rpm: 0x78B119F1
Sb11: 0x65B5FF28
Sb12: 0xEF6D89
Sb13: 0xBD185F39
Tz: 0x5B8AB6C5
Radio: 0x13BCF252
Hboot: 0x7B12BD3D
Boot: 0x95994696
Recovery:0x4D812542
System: 0x124B8D8A
Steps Taken
HTC One Toolkit (-6 occurs at 4. Prepare Revone)
CMD Entry via standard approach (adb shell, cd, chmod 755, etc.). This fails at ./revone -P
Attempted chown root: root revone (I'm writing that from memory, I apologize if its is slightly wrong)
Reverted from 4.3 to 4.2.2 via MaximusHD 11.0.0
Drivers updated via HTC One Toolkit
Yes, USB Debugging enabled, fast boot disabled
Removed HTC Sync from computer about 20 minutes ago I just discovered I'm now getting Device Not Found errors in CMD after removing Sync. I thought I'd licked this problem, but apparently my success was tied to HTC Sync. However, everything written already was when device was found.
Steps Not Yet Taken
Downgraded to 1.24.*.10 and then upgraded to 1.24.*.12 - I'm not entirely clear how to do this.
Attempted Rumrunner despite being 1.44 - I read a post where someone had been successful despite their HBOOT, but haven't done it yet.
[Edit] Have downloaded M7 TWRP Nandroid Backup CID CWS__001 1.26.502.10.zip but not yet flashed. Assuming I even have that concept right, that you install this by flashing like I did the MaximusHD 11.0.0 ROM
Known Potential Issues
Some people have alluded that an OTA HBOOT release of T-Mobile contained an impenetrable block for revone
Others have said error code -6 is just a known bug. I'm assuming that would mean I'm **** outta luck?
In CMD, I've seen others with "[email protected]", but I was getting "[email protected]"
I attempted to run as su, but wasn't entirely clear on how to do that. I didn't get any error messages, so I'm assuming I did it correctly. I believe I performed it as "adb shell su" or perhaps I just did "su" after getting into the shell.

you already have been answered, easy on the double posting
http://forum.xda-developers.com/showthread.php?t=2647168

[ROOT][10-29-13]How to Manually Root the Nvidia Shield

Introduction
The following procedure will walk you through the step-by-step process for gaining root access on the Nvidia Shield.
Note: You must have an unlocked bootloader before you can proceed with this tutorial!
A tutorial on how to unlock your Shield's bootloader can be found here.
This tutorial also assumes how have the correct ADB and Fastboot drivers installed for your device, for a tutorial on how to install the ADB and Fastboot drivers for the Shield please look here.
Due to the nature of modifying devices system files the standard XDA disclaimer applies: I take no responsibility for bricked devices due to the following rooting procedure, no warranty express or implied is given, I will not be held responsible if you mess up your device by following this procedure!
Procedure
Before you begin please make sure to read and re-read the whole procedure, making sure you understand the directions.
1. Download the "Superuser-su.zip" file and the "roth-insecure-boot-63.img" file that are attached to this post. After you have downloaded the files, extract the contents of the "Superuser-su.zip" file which contains Superuser.apk and the su binary, and move them to your ADB and Fastboot folder on your computer. Also transfer the "roth-insecure-boot-63.img" to your computer's ADB and Fastboot folder.
MD5 Checksum for "roth-insecure-boot-63.img": F8BA5C48D0323D99E2A748C77BF647F6
2. Connect your Shield to your computer using your USB cable. For maximum reliability please connect the USB cable to a USB 2.0 port directly connected to the motherboard as USB ports on the front of a case panel or USB 3.0 ports can sometimes be unreliable.
3. Now that your Shield is connected to your computer make sure that "USB debugging" is enabled under the Developer Options section in the system settings menu (If the Developer Options section is hidden, go to the About Phone/About Tablet section of the system settings and then tap on the item that lists the Build number 7 times or until it says "You are now a developer" and the Developer Options section becomes visible in the system settings).
4. Open a command prompt window (cmd) in your ADB and Fastboot folder on your computer and issue the following commands (If you are new to using ADB and Fastboot I would recommend checking out this excellent guide to get you up and running):
Code:
adb reboot bootloader
Now that you are in fastboot mode let's make sure that the computer see's our device:
Code:
fastboot devices
If the computer see's our device then we can proceed, if it doesn't see your device make sure you are in fastboot mode and have the correct ADB and Fastboot drivers installed for the Shield.
Now we will be booting an insecure boot.img (ro.secure = 0) to our device to allow us to gain root acess:
Code:
fastboot boot roth-insecure-boot-63.img
After the insecure boot.img finishes flashing the device will automatically boot up using the insecure boot.img.
5.First we need to mount the /system partition as read/write so we can modify it:
Code:
adb shell
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
exit
6. Now we need to run the following commands to push the Superuser.apk and su binary to there correct positions and set the proper file permissions:
Code:
adb push su /system/xbin
adb push Superuser.apk /system/app
adb shell
chmod 6755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
sync
reboot
7. After the device reboots and power on into the Android Operating System you should see Koush's Superuser app in your app-drawer and you should be rooted. If you would like to verify root access you can download and run Root Checker Basic from the Play Store here. Enjoy!
Credits: Koush for his open source Superuser.apk and the su binary (https://github.com/koush/Superuser)
If users would like me to create a 1-click root process of this please let me know and I will do so .
If you are stuck with the rooting procedures I would recommend checking out this great video tutorial by wwjoshdew.

Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root

Gnurou said:
Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root
Click to expand...
Click to collapse
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.

wwjoshdew said:
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.
Click to expand...
Click to collapse
I did my RMA and nvidia sent me a new 1. So you should get your new shield b4 you send it back if you happen to root it and the screen dies.

This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.

dark42 said:
This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.
Click to expand...
Click to collapse
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium

shimp208 said:
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
This method is actually nearly the same. It's a bootable self-contained image (like recovery is) that mounts the correct partitions, installs the necessary bits, and is done.

I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris

i00 said:
I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris
Click to expand...
Click to collapse
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.

shimp208 said:
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.
Click to expand...
Click to collapse
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris

i00 said:
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris
Click to expand...
Click to collapse
The original factory restore image that you can be flashed to your shield to return it to stock can be downloaded from here, along with the factory image extraction instructions (Under the open source resources section), as well as the factory image flashing instructions.

Does anyone if the root stop you from updating the device like GS4?

Simply rooting does not. I was rooted and updated. You lose root but can just reroot it like the first time. I am not sure if you have a custom recovery installed though. I haven't used one on the shield.

I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2

wrc1010 said:
I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2
Click to expand...
Click to collapse
When you mean you can't get the command prompt to directly open what do you mean by that? Does command prompt not open or run at all when you open it? Do you have ADB and Fastboot installed and the files listed for this procedure in your ADB and Fastboot directory? The Shield I rooted was my friends and he's on vacation right now so I unfortunately can't make a video right now , but I'll still be happy to try and help you through the procedure.

Finally success root my shield

oh god
wrc1010 said:
Finally success root my shield
Click to expand...
Click to collapse
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc

gogul1 said:
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc
Click to expand...
Click to collapse
What drivers are you trying to install and which version of Windows are you running?

Drivers
shimp208 said:
What drivers are you trying to install and which version of Windows are you running?
Click to expand...
Click to collapse
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.

gogul1 said:
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.
Click to expand...
Click to collapse
Did you try and install these drivers? Make sure to uninstall your old driver installation first.

Anyway to reverse Kit-Kat update?

So I updated my HTC One to Kit Kat about a week ago thinking that it would make some improvement to my user experience, but so far I don't like it. Things seem a bit glitchy now when they weren't before, especially with things like the GUI. I also don't like some of the changes they made, such as how texts show up on the lockscreen now and the grey battery indicator...and I don't really care much for some of the minor new features.
So I was wondering whether it's at all possible to "reverse" the update to the version just before they released and pushed out the Kit Kat update... I realize that I'll probably have to re-flash the stock rom in order to do so, but I'm willing to do it if at all possible. The phone is completely stock, no root and no modifications whatsoever.

If you root, s-off, and flash an aftermarket recovery you can flash the stock Rom. If you're going to go thru all the trouble to do this I personally would NOT run an ota to become stock again. You can achieve that by flashing a Rom and be 80% or more stock. To get back fully stock you need to find the original ota and run it after doing the other things I listed above. Search here and you'll find out how to do all of these steps.
Sent from my HTC0P3P7 using Tapatalk

Greetings,
I moved your thread to Q&A.
Please note all questions should be in Q&A.
Thank You, BD619

Any way to downgrade kitkat to 4.3?
is there any how to's to downgrade sprint htc one kitkat to jellybean 4.3,thnx.

EVANS AMOAH said:
is there any how to's to downgrade sprint htc one kitkat to jellybean 4.3,thnx.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2634256

Decifra said:
http://forum.xda-developers.com/showthread.php?t=2634256
Click to expand...
Click to collapse
Thanks for your reply but these steps require you to be s-off and temp root,I have a completely stock 4.4.2 rom with locked bootloader and hboot 1.56.0000.Now I need to temp root,s-off so I can downgrade the rom to an unlockable rom(sim unlock).
I understand it's possible to sim unlock the sprint htc one.
Question is,how can I gain temp root and s-off so I can downgrade to 4.3 and sim unlock the phone,thnx.

EVANS AMOAH said:
Thanks for your reply but these steps require you to be s-off and temp root,I have a completely stock 4.4.2 rom with locked bootloader and hboot 1.56.0000.Now I need to temp root,s-off so I can downgrade the rom to an unlockable rom(sim unlock).
I understand it's possible to sim unlock the sprint htc one.
Question is,how can I gain temp root and s-off so I can downgrade to 4.3 and sim unlock the phone,thnx.
Click to expand...
Click to collapse
... your best bet is to use feirewater s-off method which also has temp root. get s-off, downgrade and then go for sim unlock :victory: ...

Devilish_Angel said:
... your best bet is to use feirewater s-off method which also has temp root. get s-off, downgrade and then go for sim unlock :victory: ...
Click to expand...
Click to collapse
oh ok,I will give it a shot and post back my experince,thnx for your reply.

EVANS AMOAH said:
oh ok,I will give it a shot and post back my experince,thnx for your reply.
Click to expand...
Click to collapse
well I did try firewater but I always get this "error, run firewater as root. su or FU", after running the last command which is /data/local/tmp/firewater.
Am I doing anything wrong?
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\evans>cd c:/android-sdk/android-sdk-windows/platform-tools
c:\android-sdk\android-sdk-windows\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
FA3A3S907109 device
c:\android-sdk\android-sdk-windows\platform-tools>adb reboot
c:\android-sdk\android-sdk-windows\platform-tools>adb wait-for-device push firew
ater /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
2818 KB/s (4519496 bytes in 1.566s)
c:\android-sdk\android-sdk-windows\platform-tools>adb wait-for-device push firew
ater /data/local/tmp
3056 KB/s (4519496 bytes in 1.444s)
c:\android-sdk\android-sdk-windows\platform-tools>adb push temproot /data/local/
tmp/
2678 KB/s (68576 bytes in 0.025s)
c:\android-sdk\android-sdk-windows\platform-tools>adb shell
[email protected]:/ $ chmod 755 /data/local/tmp/temproot
chmod 755 /data/local/tmp/temproot
[email protected]:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ $ /data/local/tmp/temproot
/data/local/tmp/temproot
run_root_shell, thanks fi01 - https://github.com/android-rooting-tools/android_r
un_root_shell
[*] Attempting to acquire root. This will take 5-10 minutes, be patient
error in setsockopt().
Failed to get prepare_kernel_cred address.
Failed to get commit_creds address.
Failed to get ptmx_fops address.
Failed to setup variables.
1|[email protected]:/ $
it stops there nothing happens again.

EVANS AMOAH said:
well I did try firewater but I always get this "error, run firewater as root. su or FU", after running the last command which is /data/local/tmp/firewater.
Am I doing anything wrong?
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\evans>cd c:/android-sdk/android-sdk-windows/platform-tools
c:\android-sdk\android-sdk-windows\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
FA3A3S907109 device
c:\android-sdk\android-sdk-windows\platform-tools>adb reboot
c:\android-sdk\android-sdk-windows\platform-tools>adb wait-for-device push firew
ater /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
2818 KB/s (4519496 bytes in 1.566s)
c:\android-sdk\android-sdk-windows\platform-tools>adb wait-for-device push firew
ater /data/local/tmp
3056 KB/s (4519496 bytes in 1.444s)
c:\android-sdk\android-sdk-windows\platform-tools>adb push temproot /data/local/
tmp/
2678 KB/s (68576 bytes in 0.025s)
c:\android-sdk\android-sdk-windows\platform-tools>adb shell
[email protected]:/ $ chmod 755 /data/local/tmp/temproot
chmod 755 /data/local/tmp/temproot
[email protected]:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ $ /data/local/tmp/temproot
/data/local/tmp/temproot
run_root_shell, thanks fi01 - https://github.com/android-rooting-tools/android_r
un_root_shell
[*] Attempting to acquire root. This will take 5-10 minutes, be patient
error in setsockopt().
Failed to get prepare_kernel_cred address.
Failed to get commit_creds address.
Failed to get ptmx_fops address.
Failed to setup variables.
1|[email protected]:/ $
it stops there nothing happens again.
Click to expand...
Click to collapse
... It seems firewater is not getting root permissions. When you run firewater again, never let the screen sleep and grant permission whenever it asks (not sure but can ask multiple times) ...
Sent from my HTCONE using XDA Premium 4 mobile app

I'm pretty sure the temp root method does not work on Sprint devices.

I guess the only option for me now is to wait untill a proper root exploit is found.
thank you guys for your support

EVANS AMOAH said:
I guess the only option for me now is to wait untill a proper root exploit is found.
thank you guys for your support
Click to expand...
Click to collapse
There has only been 1 exploit in recent years that did not require your bootloader to be unlocked beforehand...so your "proper root exploit" most likely won't happen.

EVANS AMOAH said:
I guess the only option for me now is to wait untill a proper root exploit is found.
thank you guys for your support
Click to expand...
Click to collapse
... i insist you to try firewater and dont loose hope if it fails 1st time. you may have to try 4-5 times, eventually it will work hopefully ...

smsmart said:
So I updated my HTC One to Kit Kat about a week ago thinking that it would make some improvement to my user experience, but so far I don't like it. Things seem a bit glitchy now when they weren't before, especially with things like the GUI. I also don't like some of the changes they made, such as how texts show up on the lockscreen now and the grey battery indicator...and I don't really care much for some of the minor new features.
So I was wondering whether it's at all possible to "reverse" the update to the version just before they released and pushed out the Kit Kat update... I realize that I'll probably have to re-flash the stock rom in order to do so, but I'm willing to do it if at all possible. The phone is completely stock, no root and no modifications whatsoever.
Click to expand...
Click to collapse
The only way to downgrade is to go through the process of unlocking bootloader, root, s-off, you can do whatever you want from there...

Devilish_Angel said:
... i insist you to try firewater and dont loose hope if it fails 1st time. you may have to try 4-5 times, eventually it will work hopefully ...
Click to expand...
Click to collapse
ok,I will keep on trying and see what happens,by the way,have you tried firewater's temp root and s-off on sprint htc one 4.4.2 before,if yes how did it go?

EVANS AMOAH said:
ok,I will keep on trying and see what happens,by the way,have you tried firewater's temp root and s-off on sprint htc one 4.4.2 before,if yes how did it go?
Click to expand...
Click to collapse
... i think temroot does not work on 4.4.2. as you been suggested before, unlock bootloader, custom recovery, root and then get s-off ...

BD619 said:
There has only been 1 exploit in recent years that did not require your bootloader to be unlocked beforehand...so your "proper root exploit" most likely won't happen.
Click to expand...
Click to collapse
Any suggestions as to what next,because I really need to sim unlock this phone.
thnx.

EVANS AMOAH said:
Any suggestions as to what next,because I really need to sim unlock this phone.
thnx.
Click to expand...
Click to collapse
... Brother either we are not able to make you understand or you are not willing to grasp it. The only way to sim unlock is to downgrade, to downgrade you need s-off, for s-off you need root, for root you need custom recovery, for custom recovery you need unlocked bootloader, and all starts from here. I hope this helps you clear any doubts if you still have them ...

Devilish_Angel said:
... Brother either we are not able to make you understand or you are not willing to grasp it. The only way to sim unlock is to downgrade, to downgrade you need s-off, for s-off you need root, for root you need custom recovery, for custom recovery you need unlocked bootloader, and all starts from here. I hope this helps you clear any doubts if you still have them ...
Click to expand...
Click to collapse
I must say a big thank you to you and everyone for your time,patience and understanding,I guess my only option for now is to wait,since none of these things mentioned above is currently available for my device.
Forgive me if I'm being unreasonable,thank you.
DEVICE DETAILS:
SPRINT HTC ONE
ANDROID KITKAT 4.4.2
OS VERSION 4.06.651.4
HBOOT - 1.56.0000
RADIO -1.00.20.1108
BOOTLOADER - LOCKED
Fingers crossed.

[root][confirmed][5.1.1]

CONFIRMED
I've looked a bit arround how we could achieve root on the fire without TWRP.
I don't have 5.1.1 installed, but I'm hoping the following is still possible.
(I tested it on a brand-new fire, that never came in touch with TWRP or a custom rom)
If someone could test this please:
Confirmed, working:
- Enable ADB-Debugging in Developer Settings, then:
Code:
adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb wait-for-device && adb shell
You should now hopefully have a shell with root-priviledges:
Code:
[email protected]:/ #
Please test and report back.
To Flash SuperSU and make root persistent (thx @pappasmurfsharem):
https://www.androidfilehost.com/?w=files&flid=42700
If you are still inside "adb shell" from the last command above type "exit" first.
Or just skip the "adb shell" command above.
Code:
adb remount
adb push files\libsupol.so /data/local/tmp/
adb push files\root_fire.sh /data/local/tmp/
adb push files\su /data/local/tmp/
adb push files\Superuser.apk /data/local/tmp/
adb push files\supolicy /data/local/tmp/
adb shell chmod 777 /data/local/tmp/root_fire.sh
adb shell /data/local/tmp/root_fire.sh
# This Part reopened fastboot and I just re-ran the cmds from the first post in this thread #
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb wait-for-device && adb remount
adb shell /system/xbin/su --install
adb reboot

It works, in fact I've used it to remove a couple of apks from Amazon on 5.1.1 but... I can't see firelauncher, for example.

Huge thanks k4y0z!
I have another Fire due to arrive tomorrow, will definitely try it if I get 5.1.1.
Could you give the commands for restoring the old bootloader? Or would we use FlashFire? I presume there is a risk of hard brick. Flashing the bootloader would include the preloader & amazon recovery? I see there is a Boot & a Recovery partition.

Confirmed. This works on 5.1.1

Thanks, it is working on my fire 5.1.1.
now just need to figure out how load TWRP on here

I'll do it... I only have one, but I bought it for $30, so I don't mind helping here!

cococo42 said:
It works, in fact I've used it to remove a couple of apks from Amazon on 5.1.1 but... I can't see firelauncher, for example.
Click to expand...
Click to collapse
Thanks for the feedback
blueberry.sky said:
Huge thanks k4y0z!
I have another Fire due to arrive tomorrow, will definitely try it if I get 5.1.1.
Could you give the commands for restoring the old bootloader? Or would we use FlashFire? I presume there is a risk of hard brick. Flashing the bootloader would include the preloader & amazon recovery? I see there is a Boot & a Recovery partition.
Click to expand...
Click to collapse
I have never used FlashFire.
I believe it should be enough to flash the old fastboot, though I'm unsure about the preloader.
You are correct, the following could potentially WILL brick your Fire, do at your own risk!
Code:
adb push lk.bin /data/local/tmp/
adb push preloader_prod.img /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb shell "dd if=/data/local/tmp/preloader_prod.img of=/dev/block/platform/mtk-msdc.0/mmcblk0boot0"
adb reboot-bootloader
Now fastboot boot should hopefully work again.
Please test and report back!

Total noob question, I know... I haven't used Android Studio before, but am definitely a computer guy... Very simply, can you show me how to just run a straight up terminal to type these commands without creating a new "app"...
I just have a lack of android coding experience, but if you tell me, I'll understand very quickly...

jbraney said:
Total noob question, I know... I haven't used Android Studio before, but am definitely a computer guy... Very simply, can you show me how to just run a straight up terminal to type these commands without creating a new "app"...
I just have a lack of android coding experience, but if you tell me, I'll understand very quickly...
Click to expand...
Click to collapse
You don't need android studio to do any of this. Do you have ADB and fastboot installed? If you need help PM me.

jbraney said:
Total noob question, I know... I haven't used Android Studio before, but am definitely a computer guy... Very simply, can you show me how to just run a straight up terminal to type these commands without creating a new "app"...
I just have a lack of android coding experience, but if you tell me, I'll understand very quickly...
Click to expand...
Click to collapse
You don't need Android Studio, you just need adb and fastboot, your best bet is to search this forum for these two.

Well this is exciting!

Alright guys... this looks promising!

I'll go ahead and try the bootloader downgrade trick in a few hours, assuming nobody else has done it by that time .

Installed supersu on 5.1.1 ... works perfect ! THX VERY MUCH!!

lordpit said:
Installed supersu on 5.1.1 ... works perfect ! THX VERY MUCH!!
Click to expand...
Click to collapse
Does this mean that the bootloader is unlocked? With root we can now flash CM12.1 and GAPPS?

jbraney said:
Does this mean that the bootloader is unlocked? With root we can now flash CM12.1 and GAPPS?
Click to expand...
Click to collapse
The 5.1.1 bootloader still prevents TWRP recovery/others from being installed. According to post #7, we might be able to downgrade bootloaders.

k4y0z said:
Thanks for the feedback
I have never used FlashFire.
I believe it should be enough to flash the old fastboot, though I'm unsure about the preloader.
You are correct, the following could potentially brick your Fire, do at your own risk!
I have the old fastboot attatched to this post to flash it:
Code:
adb push lk.bin /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb reboot-bootloader
Now fastboot boot should hopefully work again.
Please test and report back!
Click to expand...
Click to collapse
This bricked my fire on 5.1.1 ... do not do this! Here is what I did to brick it:
Code:
adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb push lk.bin /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb reboot-bootloader

maratd said:
This bricked my fire on 5.1.1 ... do not do this! Here is what I did to brick it:
Code:
adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb push lk.bin /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb reboot-bootloader
Click to expand...
Click to collapse
Damn can you still get into fastboot with VOL-DOWN + Power?
Maybe we also have to flash the older preloader

jbraney said:
Does this mean that the bootloader is unlocked? With root we can now flash CM12.1 and GAPPS?
Click to expand...
Click to collapse
Bootloader is still locked. But if we can downgrade to the 5.0.1 fastboot bootloader then we can return to flashing CM12.1, SlimLP, gapps as we did before (temporarily loading twrp into memory then flashing rom).

k4y0z said:
CONFIRMED
I've looked a bit arround how we could achieve root on the fire without TWRP.
I don't have 5.1.1 installed, but I'm hoping the following is still possible.
(I tested it on a brand-new fire, that never came in touch with TWRP or a custom rom)
If someone could test this please:
- Enable ADB-Debugging in Developer Settings, then:
Code:
adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb wait-for-device && adb shell
You should now hopefully have a shell with root-priviledges:
Code:
[email protected]:/ #
Please test and report back.
If it works we can probably restore the old bootloader with "fastboot boot" support.
Click to expand...
Click to collapse
Is this all I habe to do, getting into the root shell or are there any more things to do for a root in my 5.1.1?
Thanks