Hello everyone,
I have a weird problem with my HTC One (Japanese version HTL22). The Hboot is 1.57, android version 4.4.2. I basically triedever method, even the one specific for this HTL22 but I encounter a weird issue:
On adb, I am able to push the revone into the temp dir; chmod 755 but when I want to prepare the S-OFF with revone-P I always got the same error message:
Gaining root access (thanks to Dan's motochopper)...[-] Failed to open framebuffer device.
[-] Failed to open framebuffer device.
[-] Failed to open framebuffer device.
[-] Failed to open framebuffer device.
[-] Failed to open framebuffer device.
[-] Failed to open framebuffer device.
[-] Failed to open framebuffer device.
...
I also tried with the run_root_shell made for htl22, to use before revone but error came out:
Device detected: ()
Try to find address in memory...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80608000 form iomem
Attempt fb_mem exploit...
Detected kernel physical address at 0x80608000 form iomem
Failed to open /dev/graphics/fb0 due to Permission denied
You need to manage to get remap_pfn_range addresses.
Failed to get prepare_kernel_cred addresses.
Failed to get commit_creds addresses.
Failed to get ptmx_fops addresses.
() is not supported.
Failed to setup variables.
The first line is odd to me, it slike it don t fin my phone: Device detected: (). I tried to type adb devices and it find my phone, but if i enter the shell, then type adb shell, the list is empty i don t know if it is normal or not.
And yes the debug option is on !
Any advice for my case ? thank you very much in advance !
erannou said:
Hello everyone,
I have a weird problem with my HTC One (Japanese version HTL22). The Hboot is 1.57, android version 4.4.2. I basically triedever method, even the one specific for this HTL22 but I encounter a weird issue:
On adb, I am able to push the revone into the temp dir; chmod 755 but when I want to prepare the S-OFF with revone-P I always got the same error message:
Click to expand...
Click to collapse
Revone? As far as I'm concerned it doesn't work with HBOOT 1.57
erannou said:
Hello everyone,
I have a weird problem with my HTC One (Japanese version HTL22). The Hboot is 1.57, android version 4.4.2. I basically triedever method, even the one specific for this HTL22 but I encounter a weird issue:
On adb, I am able to push the revone into the temp dir; chmod 755 but when I want to prepare the S-OFF with revone-P I always got the same error message:
Gaining root access (thanks to Dan's motochopper)...[-] Failed to open framebuffer device.
[-] Failed to open framebuffer device.
[-] Failed to open framebuffer device.
[-] Failed to open framebuffer device.
[-] Failed to open framebuffer device.
[-] Failed to open framebuffer device.
[-] Failed to open framebuffer device.
...
I also tried with the run_root_shell made for htl22, to use before revone but error came out:
Device detected: ()
Try to find address in memory...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80608000 form iomem
Attempt fb_mem exploit...
Detected kernel physical address at 0x80608000 form iomem
Failed to open /dev/graphics/fb0 due to Permission denied
You need to manage to get remap_pfn_range addresses.
Failed to get prepare_kernel_cred addresses.
Failed to get commit_creds addresses.
Failed to get ptmx_fops addresses.
() is not supported.
Failed to setup variables.
The first line is odd to me, it slike it don t fin my phone: Device detected: (). I tried to type adb devices and it find my phone, but if i enter the shell, then type adb shell, the list is empty i don t know if it is normal or not.
And yes the debug option is on !
Any advice for my case ? thank you very much in advance !
Click to expand...
Click to collapse
Are you using windows or linux? Try this ADB and fastboot I attached to the post. Also have you unlocked the bootloader yet through HTCdev?
johnwayne007 said:
Are you using windows or linux? Try this ADB and fastboot I attached to the post. Also have you unlocked the bootloader yet through HTCdev?
Click to expand...
Click to collapse
Thank you for your answer.
I am using Windows 7, i tried on 8 and it is the same result.
HTCdev don t work for me as my carrier is not allowing it ...
I tried your files but the result is the same.
Is there any method for hboot 1.57 ? I will maybe try sunshine but as it is not free, i am afraid it won t work with my phone, as my final goal is to get rid of the sim lock !
erannou said:
Thank you for your answer.
I am using Windows 7, i tried on 8 and it is the same result.
HTCdev don t work for me as my carrier is not allowing it ...
I tried your files but the result is the same.
Is there any method for hboot 1.57 ? I will maybe try sunshine but as it is not free, i am afraid it won t work with my phone, as my final goal is to get rid of the sim lock !
Click to expand...
Click to collapse
Only Sunshine method to s-off hboot 1.57
MaratabHashmi said:
Only Sunshine method to s-off hboot 1.57
Click to expand...
Click to collapse
Thank you for your answer. I guess i have no choice then.
With sunshine I should be able to unable the sim lock right? Or the hboot 1.57 will prevent me to do it ?
Thank you in advance !
erannou said:
Thank you for your answer. I guess i have no choice then.
With sunshine I should be able to unable the sim lock right? Or the hboot 1.57 will prevent me to do it ?
Thank you in advance !
Click to expand...
Click to collapse
sim unlock is not achieved with s-off its 2 different thing. You need to purchase a sim unlock code.
Related
I've tried all the s-off guides tu unlock my incredible s, but every time, when i try to flash the RUU, it dosen't work Someone to help me
What hboot u on?
more info u give the help u will get in return
Sent from my HTC Incredible S using xda premium
jules290496 said:
I've tried all the s-off guides tu unlock my incredible s, but every time, when i try to flash the RUU, it dosen't work Someone to help me
Click to expand...
Click to collapse
sharkman3d said:
What hboot u on?
more info u give the help u will get in return
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^ What he said!!!!!!!! ^^^^^^^^^^^^^^^^
More information please.
Sorry I'm on 2.01.0001
What error did you get?
jules290496 said:
I've tried all the s-off guides tu unlock my incredible s, but every time, when i try to flash the RUU, it dosen't work Someone to help me
Click to expand...
Click to collapse
Even i have this problem with the new version of HBOOT. Did you try the tool given by Nonverbose?? And are you having any radio issues?
I got this in my terminal:
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Is the device rooted?
y OR n:n
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Pushing tacoroot
adb server is out of date. killing...
* daemon started successfully *
351 KB/s (14475 bytes in 0.040s)
Correcting permissions
adb server is out of date. killing...
* daemon started successfully *
tacoroot rebooting phone to recovery
adb server is out of date. killing...
* daemon started successfully *
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
link failed No such file or directory
Waiting for device to connect
Device found
tacoroot starting adbD as root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
cannot create /data/local.prop: permission denied
Waiting for device to connect
Device found
Pushing misc_version
1006 KB/s (367096 bytes in 0.356s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Do you need to create a goldcard?
y OR n:n
Undoing tacoroot (if applied)
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
rm failed for /data/local.prop, No such file or directory
Root removed, rebooting
Waiting for device to connect
error: protocol fault (no status)
Device found
Cleaning temp files
* daemon not running. starting it now *
* daemon started successfully *
Checking version-main
< waiting for device >
version-main: 3.11.405.2
finished. total time: 0.002s
If the version-main returns 2.00.000.0 you should be
able to run the RUU downgrade. If it does not, answer n to the
unlocked bootloader prompt no matter what.
Do you have an unlocked bootloader from htcdev.com?
y OR n:y
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.297s
Note: run the RUU in fastboot mode
If all steps were completed without error,
you should be ready to run the RUU downgrade
Appuyez sur une touche pour continuer...
And when i try to flash the RUU for downgrad, it say : The update utility can't update the android phone.
Try to obtain the correct rom update utility and try again ( it's translated from french)
InsertDumbNick said:
Even i have this problem with the new version of HBOOT. Did you try the tool given by Nonverbose?? And are you having any radio issues?
Click to expand...
Click to collapse
Yes, it was the first i tried...
Is the RUU you have the correct one for your region? The fact you are choosing not to make a goldcard could be having an effect.
Type this command into cmd while your phone is in fastboot mode 'fastboot oem lock'. I did that before I run the process.
Sent from my HTC Incredible S using xda premium
jules290496 said:
I got this in my terminal:
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Is the device rooted?
y OR n:n
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Pushing tacoroot
adb server is out of date. killing...
* daemon started successfully *
351 KB/s (14475 bytes in 0.040s)
Correcting permissions
adb server is out of date. killing...
* daemon started successfully *
tacoroot rebooting phone to recovery
adb server is out of date. killing...
* daemon started successfully *
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
link failed No such file or directory
Waiting for device to connect
Device found
tacoroot starting adbD as root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
cannot create /data/local.prop: permission denied
Waiting for device to connect
Device found
Pushing misc_version
1006 KB/s (367096 bytes in 0.356s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Do you need to create a goldcard?
y OR n:n
Undoing tacoroot (if applied)
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
rm failed for /data/local.prop, No such file or directory
Root removed, rebooting
Waiting for device to connect
error: protocol fault (no status)
Device found
Cleaning temp files
* daemon not running. starting it now *
* daemon started successfully *
Checking version-main
< waiting for device >
version-main: 3.11.405.2
finished. total time: 0.002s
If the version-main returns 2.00.000.0 you should be
able to run the RUU downgrade. If it does not, answer n to the
unlocked bootloader prompt no matter what.
Do you have an unlocked bootloader from htcdev.com?
y OR n:y
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.297s
Note: run the RUU in fastboot mode
If all steps were completed without error,
you should be ready to run the RUU downgrade
Appuyez sur une touche pour continuer...
And when i try to flash the RUU for downgrad, it say : The update utility can't update the android phone.
Try to obtain the correct rom update utility and try again ( it's translated from french)
Click to expand...
Click to collapse
OK, during the running of this script, when tacoroot says starting adb as root, do you see a # prompt?
From the messages, it looks like tacoroot is not getting temproot in order to update the mainver value to 2.00.0000. At the end of the script your mainver is still 3.11.405.2.
tpbklake said:
OK, during the running of this script, when tacoroot says starting adb as root, do you see a # prompt?
From the messages, it looks like tacoroot is not getting temproot in order to update the mainver value to 2.00.0000. At the end of the script your mainver is still 3.11.405.2.
Click to expand...
Click to collapse
No, i don't see any # and i tried whith and without goldcard
jules290496 said:
No, i don't see any # and i tried whith and without goldcard
Click to expand...
Click to collapse
Yeah, the whole key to the script is getting temp root access so that the mainver can be modified to 2.00.0000.
If that doesn't work, the whole goldcard and RUU thing will not work.
The best thing you could try is to open a command window and try manually typing the commands in and post the command window to help isolate the issue.
I think i will give up, thanks anyway
jules290496 said:
I think i will give up, thanks anyway
Click to expand...
Click to collapse
You have a custom recovery installed?
No, i don't now how to do it without revolutionary...
jules290496 said:
No, i don't now how to do it without revolutionary...
Click to expand...
Click to collapse
So the phone is completely stock, just unlocked bootloader?
Yes it's completely stock
jules290496 said:
Yes it's completely stock
Click to expand...
Click to collapse
Try locking the bootloader and doing a factory reset. Boot into recovery once, turn fastboot off and USB debugging on and run the newest version (3.2) of the script again.
Ok, i will try
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
I am new to writing anything here. But, these forums have helped me countless times and I thank you all for that.
I have a T-mobile HTC One and I have tried for 2 days now to get to S-Off but I keep getting error codes using both revone and moonshine.
With Moonshine I get all the way down to Moonshining <10> and then it says error: Dont Drink and Shine. I have run it about 10 times and keep getting the same think.
With Revone I get this error code:
2|[email protected]:/data/local/tmp #
C:\sdk-tools>adb shell
[email protected]:/ # su
su
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 revone.dna-0.2.1
chmod 755 revone.dna-0.2.1
[email protected]:/data/local/tmp # ./revone.dna-0.2.1 -P
./revone.dna-0.2.1 -P
revone v0.2.1
revone failed (error code = 2)
2|[email protected]:/data/local/tmp #
I have tried doing a FULL power off/factory reset/reboot bootloader. Nothing...
Also after all of this my Wifi will not connect anymore. It now stays on connecting and then after a while it says ERROR.
Any help on fixing any of these would be greatly appriciated. If you need any more information please let me know.
Dud you get any help this this ?
Sent from my HTC One using xda premium
What version is your hboot? If its greater than 1.44 you can't s off.
AT&T HTC One
GPe 4.3
CoryTallman said:
What version is your hboot? If its greater than 1.44 you can't s off.
AT&T HTC One
GPe 4.3
Click to expand...
Click to collapse
My hboot is 1.44. No help yet unfortunately.
joemc1470 said:
My hboot is 1.44. No help yet unfortunately.
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).
puargs said:
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).
Click to expand...
Click to collapse
I did not apply the patch but I did just get the phone. I guess it came with that patch because it did start making everything screwy (Didnt recognize my sdcard and would not let wifi turn on) I flashed a stock rom and all is good for now. I will wait for an update to moonshine.
Thanks
joemc1470 said:
I am new to writing anything here. But, these forums have helped me countless times and I thank you all for that.
I have a T-mobile HTC One and I have tried for 2 days now to get to S-Off but I keep getting error codes using both revone and moonshine.
With Moonshine I get all the way down to Moonshining <10> and then it says error: Dont Drink and Shine. I have run it about 10 times and keep getting the same think.
With Revone I get this error code:
2|[email protected]:/data/local/tmp #
C:\sdk-tools>adb shell
[email protected]:/ # su
su
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 revone.dna-0.2.1
chmod 755 revone.dna-0.2.1
[email protected]:/data/local/tmp # ./revone.dna-0.2.1 -P
./revone.dna-0.2.1 -P
revone v0.2.1
revone failed (error code = 2)
2|[email protected]:/data/local/tmp #
I have tried doing a FULL power off/factory reset/reboot bootloader. Nothing...
Also after all of this my Wifi will not connect anymore. It now stays on connecting and then after a while it says ERROR.
Any help on fixing any of these would be greatly appriciated. If you need any more information please let me know.
Click to expand...
Click to collapse
Have you fixed it? i have the same problem
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
I rooted this device successfully but then my bro try'd installing a busybox and it broke the root so I did a factory reset then try'd to root again and all I got was this
2510 KB/s (89968 bytes in 0.035s)
Changing permissions...
Executing Exploit (could take some minutes, be patient!)
Hit ENTER to continue
Drücken Sie eine beliebige Taste . . .
Device detected: KFSOWI (JDQ39)
Attempt acdb exploit...
KFSOWI (JDQ39) is not supported.
Attempt fj_hdcp exploit...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt put_user exploit...
ioctl: Bad address
Attempt fb_mem exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt perf_swevent exploit...
Drücken Sie eine beliebige Taste . . .
I have try 'd the manual way and uninstalled driver's then reinstalled them I downloaded the root and nothing seems to work...I need someone's help
Thanks
Performing a factory rest does not completely remove root access since the binaries are still left. That's most likely why you cannot gain root access.Try following the advice given in post 15 from this link.
http://forum.xda-developers.com/showthread.php?t=1923612&page=2
elua35 said:
Performing a factory rest does not completely remove root access since the binaries are still left. That's most likely why you cannot gain root access.Try following the advice given in post 15 from this link.
http://forum.xda-developers.com/showthread.php?t=1923612&page=2
Click to expand...
Click to collapse
i have try'd unrooting and had no sucess i just get permission deined at
mount -o remount,rw /system
so i get rm failed here
rm /system/xbin/su
because i dont have permission...i try'd rooting again after this and no luck still no luck but thank for the advice
EDIT:in the beginning when i type
adb shell
su
after i type su i get
su: must be suid to work properly
EDIT:I was looking throughout the files and found in /system/xbin a superuser file I try 'd opening it and reading it but it was encrypted like it's expected to be but then I try 'd deleting it but then again no root so no permissions
I think you and I are in the same boat. I had root, something went wrong, factory reset the device, now can't get root back, and no solutions I've found on here have worked.