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
Related
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?
Hi,
So I got a HTC One today, and I'm lovin it so far!
However, I want to have 4.2 ROM on my HTC One, but it's Three (3) Carrier branded!
I bought a code so I could use my own SIM from Tele2....However, when I boot op my HTC, I still get the Three Carrier Bootanimation.
But what I think is the worst, I can't get the 4.2 ROM on my HTC!
Is there any possibility that I can magicly get the official 4.2 ROM on my Three branded HTC One?
Do I need to unlock the bootloader or something?
PLEASE HELP!:crying:
yeah unlock your bootloader, flash a custom recovery and install the odexed ROM from here: http://forum.xda-developers.com/showthread.php?t=2224752
OR
you can check the dev forums, S-OFF the device and change your CID to a Debranded one and flash a worldwide RUU
youll never get updates on Three
IINexusII said:
yeah unlock your bootloader, flash a custom recovery and install the odexed ROM from here: http://forum.xda-developers.com/showthread.php?t=2224752
OR
you can check the dev forums, S-OFF the device and change your CID to a Debranded one and flash a worldwide RUU
youll never get updates on Three
Click to expand...
Click to collapse
Thank you a 100 times! When I unlock my bootloader, I will lose my data. So how do I S-OFF and change my CID?
pottemans said:
Thank you a 100 times! When I unlock my bootloader, I will lose my data. So how do I S-OFF and change my CID?
Click to expand...
Click to collapse
If you would like to skip unlocking the bootloader do revone s off.it is in the original development section
a box of kittens said:
If you would like to skip unlocking the bootloader do revone s off.it is in the original development section
Click to expand...
Click to collapse
But Revone needs Root and for Root you need to unlock your bootloader, right?
PLEASE HELP!! I WANT 4.2 ON MY HTC ONE
it could work without root, just follow the instructions http://forum.xda-developers.com/showthread.php?t=2314582
IINexusII said:
it could work without root, just follow the instructions http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
I Don't understand any of that! I'm new to this kind of stuff so please help me! I'm coming from a SGS3 so i know how Odin, SuperSU, and Clockworkmodrecovery works, but don't know anything about S-OFF, Unlocking bootloader, and what the heck is a Adb Shell??
Please help me from scratch!
The only thing I want is Android 4.2 with Sense so I can get battery percentage and make my home button act like a menu button so the irritating black menu bar on the bottom goes away....
pottemans said:
I Don't understand any of that! I'm new to this kind of stuff so please help me! I'm coming from a SGS3 so i know how Odin, SuperSU, and Clockworkmodrecovery works, but don't know anything about S-OFF, Unlocking bootloader, and what the heck is a Adb Shell??
Please help me from scratch!
The only thing I want is Android 4.2 with Sense so I can get battery percentage and make my home button act like a menu button so the irritating black menu bar on the bottom goes away....
Click to expand...
Click to collapse
1. Install adb and get it to work http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/, Youtube http://www.youtube.com/watch?v=Yc4z-KYypgY.
2. Disable fastboot in settings/energ at the bottom and close HTC Sync Manager if its running.
3. Download and copy revone 0.2.1 to your phone and follow the instructions in the revone OP.
http://forum.xda-developers.com/showthread.php?t=2182792
and use the ODEXED rom from here: http://forum.xda-developers.com/showthread.php?t=2224752
gee2012 said:
1. Install adb and get it to work http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/, Youtube http://www.youtube.com/watch?v=Yc4z-KYypgY.
2. Disable fastboot in settings/energ at the bottom and close HTC Sync Manager if its running.
3. Download and copy revone 0.2.1 to your phone and follow the instructions in the revone OP.
Click to expand...
Click to collapse
Okay so i got adb running in my c:/adroidadb and in downloaded revone, but i can´t push it to my devices data/local/tmp!
How to fix this>
pottemans said:
Okay so i got adb running in my c:/adroidadb and in downloaded revone, but i can´t push it to my devices data/local/tmp!
How to fix this>
Click to expand...
Click to collapse
Type: adb devices in cmd. Do you see a serial number?
If so type the right name, so adb push revone-0.2.1 /data/local/tmp/
IINexusII said:
http://forum.xda-developers.com/showthread.php?t=2182792
and use the ODEXED rom from here: http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
okay so I unlocked my bootloader and installed cwm recovery. Do i only need to download the ROM zip, or also the recovery.img.... ps im not rooted!
pottemans said:
okay so I unlocked my bootloader and installed cwm recovery. Do i only need to download the ROM zip, or also the recovery.img.... ps im not rooted!
Click to expand...
Click to collapse
First i suggest you get S-Off with revone.
adb shell ; cd /data/local/tmp ; ./revone -s 0 -t
Reboot in bootlader mode: adb reboot bootloader, then you type fastboot oem writecid 11111111
Now you can flash anu RUU or rom you want
Then copy superSU zip to the phone and flash in recovery http://download.chainfire.eu/339/SuperSU/UPDATE-SuperSU-v1.41.zip.
Then make a backup in CWM recovery before you flash any custom rom.
Don`t forget to hit thanks button
gee2012 said:
First i suggest you get S-Off with revone.
adb shell ; cd /data/local/tmp ; ./revone -s 0 -t
Then copy superSU zip to the phone and flash in recovery http://download.chainfire.eu/339/SuperSU/UPDATE-SuperSU-v1.41.zip.
Then make a backup in CWM recovery before you flash any custom rom.
Don`t forget to hit thanks button
Click to expand...
Click to collapse
no, sorry i dont want to have SOFF... but can you look at this ROM! How to install this
http://forum.xda-developers.com/showthread.php?t=2224752
pottemans said:
no, sorry i dont want to have SOFF... but can you look at this ROM! How to install this
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
I`am running that one too, an excellent rom which is fast and stable.
I urge you to get S-Off, you`ll regret it later if you don`t do it now on Hboot 1.44.000. You cannot downgrade the bootloader so you cannot install a RUU later if you should have to turn it in for repair.
gee2012 said:
I`am running that one too, an excellent rom which is fast and stable.
I urge you to get S-Off, you`ll regret it later if you don`t do it now on Hboot 1.44.000. You cannot downgrade the bootloader so you cannot install a RUU later if you should have to turn it in for repair.
Click to expand...
Click to collapse
okay so i pushed revone to my Phone, what now! when i type in chmod 755 it says that chmod is not a command or something!
pottemans said:
okay so i pushed revone to my Phone, what now! when i type in chmod 755 it says that chmod is not a command or something!
Click to expand...
Click to collapse
Use any operating system you like, you only need adb.
1. Download revone (above) and push it to your device: adb push revone /data/local/tmp/
2. Open an adb shell and:
* cd /data/local/tmp
* chmod 755 revone-0.2.1
3. (optional) If your device is unlocked and rooted please switch to root using su.
4. Prepare to gain S-OFF by running the command: ./revone -P
4a. If revone reports success reboot the device and proceed to step 5)
4b. If revone reboots the device (we'll pretend this isn't an undiagnosed random crash) please wait 2 minutes then try again from step 2.
4c. If revone reports that you need to reboot and try again please reboot and try again from step 2.
5. Now that revone has successfully prepared your device for S-OFF please open another adb shell (as per step 2) and change to
the /data/local/tmp directory.
6. Instruct revone to grant you S-OFF and unlock status by running the command: ./revone-0.2.1 -s 0 -t
6a. Other optional command arguments:-
* -u - Unlock the device
* -l - Lock the device (as if it was never unlocked)
* -r - Relock the device (mark the device as relocked)
* -t - Reset the device's tamper flag.
7. Presuming revone reported success please reboot the device again, this time to the bootloader (adb reboot bootloader)
8. You should now observe your device is S-OFF (and the lock status changed if you invoked that option).
9. (optional) Re-run revone to remove TAMPERED from your HBOOT screen: ./revone -t
Type the red text in cmd.
gee2012 said:
Use any operating system you like, you only need adb.
1. Download revone (above) and push it to your device: adb push revone /data/local/tmp/
2. Open an adb shell and:
* cd /data/local/tmp
* chmod 755 revone-0.2.1
3. (optional) If your device is unlocked and rooted please switch to root using su.
4. Prepare to gain S-OFF by running the command: ./revone -P
4a. If revone reports success reboot the device and proceed to step 5)
4b. If revone reboots the device (we'll pretend this isn't an undiagnosed random crash) please wait 2 minutes then try again from step 2.
4c. If revone reports that you need to reboot and try again please reboot and try again from step 2.
5. Now that revone has successfully prepared your device for S-OFF please open another adb shell (as per step 2) and change to
the /data/local/tmp directory.
6. Instruct revone to grant you S-OFF and unlock status by running the command: ./revone -s 0 -t
6a. Other optional command arguments:-
* -u - Unlock the device
* -l - Lock the device (as if it was never unlocked)
* -r - Relock the device (mark the device as relocked)
* -t - Reset the device's tamper flag.
7. Presuming revone reported success please reboot the device again, this time to the bootloader (adb reboot bootloader)
8. You should now observe your device is S-OFF (and the lock status changed if you invoked that option).
9. (optional) Re-run revone to remove TAMPERED from your HBOOT screen: ./revone -t
Type the red text in cmd.
Click to expand...
Click to collapse
this is what i get
C:\Users\lorenzo>adb shell
[email protected]:/ $ cd/data/local/tmp
cd/data/local/tmp
/system/bin/sh: cd/data/local/tmp: not found
127|[email protected]:/ $
pottemans said:
this is what i get
C:\Users\lorenzo>adb shell
[email protected]:/ $ cd/data/local/tmp
cd/data/local/tmp
/system/bin/sh: cd/data/local/tmp: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
You have no root sign which is # instead of $.
Do You have adb installed correct, is you serialnumber visible if you type adb devices.
Command: cd /data/local/tmp , don`t forget the space after cd.
Is usb debugging enabled in developer options on the phone?
Do you have fastboot in settings/energy disabled?
gee2012 said:
You have no root sign which is # instead of $.
Do You have adb installed correct, is you serialnumber visible if you type adb devices.
Command: cd /data/local/tmp , don`t forget the space after cd.
Is usb debugging enabled in developer options on the phone?
Do you have fastboot in settings/energy diasabled?
Click to expand...
Click to collapse
yes, when I type in adb devices my serial number show up.
when I type in that command, it says there´s no path (sorry if im translating it wrong, i´m dutch)
usb debugging is enabled and fastboot is disabled...
I rooted my sprint HTC One and when i was going to flash a rom i accidentaly wiped the phone completely. I can go into TWRP but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a USB otg cable but the phone didnt seem to recognize it. please help. I've been stuck without a phone for about a week now
You try adb sideload(adb push (drag rom here) /sdcard / (hit enter)
From My TweakedOut ONE
Maybe
dased14 said:
You try adb sideload(adb push (drag rom here) /sdcard / (hit enter)
From My TweakedOut ONE
Click to expand...
Click to collapse
i tried to do something with the windows command line but i dont know if i did it right. im a noob with complicated stuff like this. i dont know if i had to download anything to make the adb work.
IVcruz said:
i tried to do something with the windows command line but i dont know if i did it right. im a noob with complicated stuff like this. i dont know if i had to download anything to make the adb work.
Click to expand...
Click to collapse
If your having trouble with ADB just grab this tool http://forum.xda-developers.com/showthread.php?t=2236814 and download the rom you want and within the tool click Sideload Rom and then select the rom. And you should be all set.
This might help you in the future so you dont wipe your data again http://forum.xda-developers.com/showthread.php?t=2237021
I tried
Konfuzion said:
If your having trouble with ADB just grab this tool http://forum.xda-developers.com/showthread.php?t=2236814 and download the rom you want and within the tool click Sideload Rom and then select the rom. And you should be all set.
This might help you in the future so you dont wipe your data again http://forum.xda-developers.com/showthread.php?t=2237021
Click to expand...
Click to collapse
I gave it a shot but when i tried to sideload the rom it says device not found. i got the same thing when i tried to adb push the rom onto my sdcard. i get an error saying device not found i also tried running the RUU but apparently i need a newer version of the RUU that is not out yet so i think im stuck and just have to wait and hope that the RUU i need comes out soon.
IVcruz said:
I rooted my sprint HTC One and when i was going to flash a rom i accidentaly wiped the phone completely. I can go into TWRP but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a USB otg cable but the phone didnt seem to recognize it. please help. I've been stuck without a phone for about a week now
Click to expand...
Click to collapse
What os are you using?
When you plug the phone in and your computer makes the ding what shows up in device manager?
Having same issue...
Flashed Android Revolution HD...probably hosed my partitions
I can access FastBoot, but no ADB access from newly formated Windows 7 PC...
...I can't sideload via ANY recovery...
and I can't OTG with USB flash drive via ANY recovery too
Looking for latest RUU but no luck.
I tried to S-Off so I can RUU with 1.29 but no luck with RevOne since I can't ADB for some reason.
Thoughts? Suggestions? Thanks for looking
IVcruz said:
I gave it a shot but when i tried to sideload the rom it says device not found. i got the same thing when i tried to adb push the rom onto my sdcard. i get an error saying device not found i also tried running the RUU but apparently i need a newer version of the RUU that is not out yet so i think im stuck and just have to wait and hope that the RUU i need comes out soon.
Click to expand...
Click to collapse
You don't need to RUU. From that tool click install HTC drivers. And see if that works if not unusual the HTC drivers and install universal naked htc one drivers (Google it you will find it).
Sent from my HTCONE using xda app-developers app
---------- Post added at 06:00 PM ---------- Previous post was at 05:55 PM ----------
rvelajr said:
Having same issue...
Flashed Android Revolution HD...probably hosed my partitions
I can access FastBoot, but no ADB access from newly formated Windows 7 PC...
...I can't sideload via ANY recovery...
and I can't OTG with USB flash drive via ANY recovery too
Looking for latest RUU but no luck.
I tried to S-Off so I can RUU with 1.29 but no luck with RevOne since I can't ADB for some reason.
Thoughts? Suggestions? Thanks for looking
Click to expand...
Click to collapse
You flashed a GSM Rom on your Sprint CDMA device.
Now to fix it follow this guide
http://forum.xda-developers.com/showthread.php?p=44243635
To make your life easy you will need drivers for your phone the best are the universal naked drivers for HTC One
http://forum.xda-developers.com/showthread.php?t=2263822
If installed, uninstall HTC sync, and disable any anti virus or firewalls including Windows firewall. You will also need to download ADB if you don't have it minimal ADB is great
http://forum.xda-developers.com/showthread.php?p=42407269
Next time read before you flash!
Sent from my HTCONE using xda app-developers app
Still battling with ADB...no devices detected...I'm stumped
Universal Driver installed without a hitch...
No firewall
No anti-virus
No HTC Sync
Fastboot works...no adb...daemon starts on port 5037..but no luck
Thoughts?
rvelajr said:
Still battling with ADB...no devices detected...I'm stumped
Universal Driver installed without a hitch...
No firewall
No anti-virus
No HTC Sync
Fastboot works...no adb...daemon starts on port 5037..but no luck
Thoughts?
Click to expand...
Click to collapse
Are you doing this from recovery?
Sent from my HTCONE using xda app-developers app
Got device recognized in recovery...
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files\Minimal ADB and Fastboot>adb devices
List of devices attached
FA35GS910838 recovery
Typed "adb shell"
Then copied/paste echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
with following result...
Sorry for Noob experience here...
C:\Program Files\Minimal ADB and Fastboot>adb shell
~ # ←[6necho "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
warning: seek lseek64 failed
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.006990 seconds, 1.7KB/s
~ # ←[6n
Am I missing something?
rvelajr said:
Got device recognized in recovery...
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files\Minimal ADB and Fastboot>adb devices
List of devices attached
FA35GS910838 recovery
Typed "adb shell"
Then copied/paste echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
with following result...
Sorry for Noob experience here...
C:\Program Files\Minimal ADB and Fastboot>adb shell
~ # ←[6necho "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
warning: seek lseek64 failed
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.006990 seconds, 1.7KB/s
~ # ←[6n
Am I missing something?
Click to expand...
Click to collapse
Nope now flash the RUU.
Need anything PM me
SOLVED!
Is is worth to S-Off with revone at this point?
I've installed ViperOne rom (my fav) and all looks well.
Since, I'm back to 1.29...what is best way to get back to 1.31.651.2?
budeone said:
What os are you using?
When you plug the phone in and your computer makes the ding what shows up in device manager?
Click to expand...
Click to collapse
Im using windows 8 and when i plug in my phoen it actually does show up under devices under a "unspecified" category where it says that drivers are unavailable. I have tried installing the drivers though and it still wont work.
rvelajr said:
SOLVED!
Is is worth to S-Off with revone at this point?
I've installed ViperOne rom (my fav) and all looks well.
Since, I'm back to 1.29...what is best way to get back to 1.31.651.2?
Click to expand...
Click to collapse
S-off will help you if you need to RUU again if your on 1.31
Sent from my HTCONE using xda app-developers app
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.
Hi, followed the instruction from this link http://sakitechonline.com/how-to-get-s-off-on-your-htc-one-m8-all-models/
and I’m stuck on the FINAL STEP: Run firewater tool to Gain S-OFF on your HTC One M8
When I enter the below command, it doesn’t do anything. Any idea what the problem might be?
adb wait-for-device push firewater /data/local/tmp
HTC One M8 - TWRP recovery - Rooted - Windows 7 64 - stock usb cable that came with the phone -
Tone527 said:
Hi, followed the instruction from this link http://sakitechonline.com/how-to-get-s-off-on-your-htc-one-m8-all-models/
and I’m stuck on the FINAL STEP: Run firewater tool to Gain S-OFF on your HTC One M8
When I enter the below command, it doesn’t do anything. Any idea what the problem might be?
adb wait-for-device push firewater /data/local/tmp
HTC One M8 - TWRP recovery - Rooted - Windows 7 64 - stock usb cable that came with the phone -
Click to expand...
Click to collapse
You have to let the program know where firewater is. If the file is located at the base of the C drive then it would look like this
adb wait-for-device push c:\firewater /data/local/tmp
Then you will see a message that it was pushed.
feizy said:
You have to let the program know where firewater is. If the file is located at the base of the C drive then it would look like this
adb wait-for-device push c:\firewater /data/local/tmp
Then you will see a message that it was pushed.
Click to expand...
Click to collapse
I just got my m8 today and firewater doesnt seem to be working anymore...
ooxteme said:
I just got my m8 today and firewater doesnt seem to be working anymore...
Click to expand...
Click to collapse
Did you get a "Whelp" message? If so, certain M8s cannot s-off with firewater. The issue seems to be random.
If you did get the whelp message and feel like paying $25 you can use this method:
http://forum.xda-developers.com/showthread.php?t=2792487
feizy said:
You have to let the program know where firewater is. If the file is located at the base of the C drive then it would look like this
adb wait-for-device push c:\firewater /data/local/tmp
Then you will see a message that it was pushed.
Click to expand...
Click to collapse
Thanks Feizy. I will give it try tonight.
feizy said:
Did you get a "Whelp" message? If so, certain M8s cannot s-off with firewater. The issue seems to be random.
If you did get the whelp message and feel like paying $25 you can use this method:
http://forum.xda-developers.com/showthread.php?t=2792487
Click to expand...
Click to collapse
BAM S OFF thanks well worth the 25 bucks!!!!! ESP when you read their site and see all the testing that was involved!:good:
ooxteme said:
I just got my m8 today and firewater doesnt seem to be working anymore...
Click to expand...
Click to collapse
feizy said:
You have to let the program know where firewater is. If the file is located at the base of the C drive then it would look like this
adb wait-for-device push c:\firewater /data/local/tmp
Then you will see a message that it was pushed.
Click to expand...
Click to collapse
Damn that command doesn't work either and it's driving me crazy lol
where is firewater saved on your computer? you should probably do some more homework first.
{ParanoiA} said:
where is firewater saved on your computer? you should probably do some more homework first.
Click to expand...
Click to collapse
It would appear that the Firewater file is in the same directory as his SDK, according to his screenshot in his first post.
Sent from my HTC device