[how to]reset your lock status flag - HTC Jetstream

with the rezound,some folks unknowingly re-unlocked after s off to regain use of fastbooot commands,after running ruus that replaced the patched jpbear hboot. i thot i would bring this here,in case there ever becomes a need.
i happened across this thread inthe gsm evo 3d forum: http://forum.xda-developers.com/showthread.php?t=1970252 and found it to work on the rezound,inc 4g,sensation 4g,cdma evo 3d,jetstream, and prolly several others.
this does NOT mean you can unlock your bootloader without going thru htcdev. all this means,is that if you accidentally unlocked your bootloader after s-off,you can get rid of the relocked watermark and get back to 100% locked prior to s-on for warranty purposes,without having to s-on and re-s off.
ive always been unlocked. for S&Gs,i dumped mmcblk0p3 and found the described "HTCU" at 0x8404. changed it to 0x00000000 and voila! back to locked
afterward,relfashed my origianl mmcblk0p3,wich brought me back to unlocked with no getting or flashing tokens.
this is NOT a patched or hex edited hboot.again,this is ONLY to get back your original ***locked*** status.
*this is for s-off tablets only
2 ways to do it:
1)old school
this assumes you to have drivers,adb/fastboot,a hex editor,a fair understanding about what youre doing,and the ability to follow directions on the linked thread
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:\mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HTxxxxxxxxxx device
c:\mini-adb_vigor>[COLOR="Red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3[/COLOR]
dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 9.519 secs (3481858 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb pull /sdcard2/mmcblk0p3[/COLOR]
2292 KB/s (33143808 bytes in 14.116s)
[COLOR="Blue"]*modify mmcblk0p3 with a hex editor[/COLOR]
c:\mini-adb_vigor>[COLOR="Red"]adb push mmcblk0p3mod /sdcard2/mmcblk0p3mod[/COLOR]
2478 KB/s (33143808 bytes in 13.059s)
c:\mini-adb_vigor>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3[/COLOR]
dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 18.937 secs (1750214 bytes/sec)
[email protected]:/ #[COLOR="red"] exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\mini-adb_vigor>
2)noob friendly
-download the appropriate zips,place on sd card.
-boot to recoverywipe cache/dalvik
-flash in recovery. i recomend to run query first,to make sure its working. tested on my personal rezound,inc 4g,sensation 4g,gsm evo 3d,and jetstream.
query:query_bootloader.zip
query_bootloader.zip f335f78f9f46469c823da0c671026de5
unlock:unlock_bootloader.zip
unlock_bootloader.zip f335f78f9f46469c823da0c671026de5
lock:lock_bootloader.zip
lock_bootloader.zip f335f78f9f46469c823da0c671026de5
a little bit of explanation. yes,the md5s are all the same. its the same file,just named differently. the script behaves based on the name of the zip. i knew if i only included 1 download and instructed folks to change the name there would be confusion,so this is my attempt to keep it simple. feel free to download one file and just change the name to make the other zips.
it also works to make your tablet relocked if for some reason you want it that way(rename relock_bootloader.zip). i didnt include a zip for that because i figued there would be no demand.
before:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after:
sure,i could have easily faked the above photos,but i dint.
again,all credit goes to s trace on the above thread,be sure to click the thanks button on his post. all i did was remove the device check per his instruction. DO NOT flash on other devices without checking for the proper location of the lock flag first.
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
enjoy
special thanks
-brian for unlocking his bootloader,then dumping mmcblock0p3 to make sure it would work for cdma phones too
-brian and donb for fearless testing of the zip files on cdma evo 3d

mine too

mmcblk0p3 does not have HTCU string in it.
PGFS only and some bytes.

maxrfon said:
mmcblk0p3 does not have HTCU string in it.
PGFS only and some bytes.
Click to expand...
Click to collapse
if you do not see HTCU or HTCL at 0x8404.then you are locked
this is from my jetstream:
hope that clears it up

scotty1223 said:
if you do not see HTCU or HTCL at 0x8404.then you are locked
this is from my jetstream:
hope that clears it up
Click to expand...
Click to collapse
Yep that part was not mentioned in the First message
Now i am Unlocked

Related

[THEME] Samsung Galaxy S II [10-02-2012] [62][58][42]

Samsung Galaxy S II theme
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to
AdamTt, for the reboot mod
Ospi, for the reboot and screenshot icon
pvyParts, for help with the notification toggles
Download the full version here​
Hi!
It looks very good , i love the icons on config menu.
But what changes with Conversations, Calendar, SemcPhone, SemcMusic packages?
rafuru said:
Hi!
It looks very good , i love the icons on config menu.
But what changes with Conversations, Calendar, SemcPhone, SemcMusic packages?
Click to expand...
Click to collapse
Glad you like it!
Just some statusbar icons are changed in those apk's
Sent from my iPad using Tapatalk
whoa, nice themes. :-D
Do anyone test it on Neo?
FrozenSE said:
Do anyone test it on Neo?
Click to expand...
Click to collapse
Nope, mind testing it for me? Should work if you're using .145 fw
phone must be rooted to install it ??
philansel7 said:
phone must be rooted to install it ??
Click to expand...
Click to collapse
yes of course.
2 vraagjes: hoe heet de klok widget die je daar hebt, en hoe root ik mn experia arc, ik dacht dat dat nog niet kon??
thomassafca said:
Nope, mind testing it for me? Should work if you're using .145 fw
Click to expand...
Click to collapse
Do you mean that files on Neo and Ark .145 FW is the same (except display drivers)? I will test it on my Neo today and post result.
I try to put files using Root Explorer. Roboot and phone not loading (shows onle splash "Sony Ericsson" on black background.
ragdoll20 said:
2 vraagjes: hoe heet de klok widget die je daar hebt, en hoe root ik mn experia arc, ik dacht dat dat nog niet kon??
Click to expand...
Click to collapse
Clock: http://gu5taf.deviantart.com/art/MIUI-Clock-Calendar-Widgets-214627542
Can you unlock your bootloader? If yes, check this.
If not, check this
@FrozenSE, did you changed the permissions?
Where' the download button on that side?
Can't find it when viewing with my phone.
Sent from my LT15i using XDA Premium App
Start copiyng -> reboot (phone restarts, I dont enter commands) -> not loads.
This is a how-to use adb: http://www.youtube.com/watch?v=Z3SpI7m7mFI
commands:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
00000000000000000000 device
C:\android-sdk-windows\platform-tools>adb push Calendar.apk /sdcard/
229 KB/s (359426 bytes in 1.529s)
C:\android-sdk-windows\platform-tools>adb push Conversations.apk /sdcard/
2806 KB/s (868038 bytes in 0.302s)
C:\android-sdk-windows\platform-tools>adb push framework-res.apk /sdcard/
1732 KB/s (4881322 bytes in 2.751s)
C:\android-sdk-windows\platform-tools>adb push SemcDeskClock.apk /sdcard/
258 KB/s (387747 bytes in 1.464s)
C:\android-sdk-windows\platform-tools>adb push SemcGenericUxpRes.apk /sdcard/
1096 KB/s (1013607 bytes in 0.903s)
C:\android-sdk-windows\platform-tools>adb push SemcMusic.apk /sdcard/
260 KB/s (667725 bytes in 2.501s)
C:\android-sdk-windows\platform-tools>adb push SemcPhone.apk /sdcard/
1200 KB/s (1589678 bytes in 1.293s)
C:\android-sdk-windows\platform-tools>adb push Settings.apk /sdcard/
1314 KB/s (2661869 bytes in 1.978s)
C:\android-sdk-windows\platform-tools>adb push SystemUI.apk /sdcard/
3903 KB/s (159911 bytes in 0.040s)
C:\android-sdk-windows\platform-tools>adb shell
$ su
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
# busybox cp -R /sdcard/Calendar.apk /system/app/
busybox cp -R /sdcard/Calendar.apk /system/app/
# busybox cp -R /sdcard/Conversations.apk /system/app/
busybox cp -R /sdcard/Conversations.apk /system/app/
# busybox cp -R /sdcard/framework-res.apk /system/framework/
busybox cp -R /sdcard/framework-res.apk /system/framework/
# busybox cp -R /sdcard/SemcDeskClock.apk /system/app/
busybox cp -R /sdcard/SemcDeskClock.apk /system/app/
# busybox cp -R /sdcard/SemcGenericUxpRes.apk /system/framework/
busybox cp -R /sdcard/SemcGenericUxpRes.apk /system/framework/
# busybox cp -R /sdcard/SemcMusic.apk /system/app/
busybox cp -R /sdcard/SemcMusic.apk /system/app/
# busybox cp -R /sdcard/SemcPhone.apk /system/app/
busybox cp -R /sdcard/SemcPhone.apk /system/app/
# busybox cp -R /sdcard/Settings.apk /system/app/
busybox cp -R /sdcard/Settings.apk /system/app/
# busybox cp -R /sdcard/SystemUI.apk /system/app/
busybox cp -R /sdcard/SystemUI.apk /system/app/
# sync
sync
# reboot
reboot
C:\android-sdk-windows\platform-tools>
Click to expand...
Click to collapse
enjoy!
same was happening here, but i solved installing busybox.
Also i make a script (for linux) to automate the process and make the changes so fast before the device reboots.
Tunatje said:
This is a how-to use adb: http://www.youtube.com/watch?v=Z3SpI7m7mFI
commands:
enjoy!
Click to expand...
Click to collapse
Okay,this is so confusing.
Is there an easier,noob friendly way to install this theme?
Come on guys, put some bloody effort in. You can install it the same way as any other arc theme.
Use root explorer, change permissions, move, reboot. You can get more detailed instructions from any of the other theme posts.
One word of advice, copy framework file last and reboot straight away.
Also, I get a very long reboot after applying a theme, be patient lol
It won't let me move it,it says it's a read-only file.
Okay,I was able to move it.Rebooted and nothing changed :S

[How to]reset your "lock status" flag

with the rezound,some folks unknowingly re-unlocked after s off to regain use of fastbooot commands,after running ruus that replaced the patched jpbear hboot. i thot i would bring this here,in case there ever becomes a need.
i happened across this thread inthe gsm evo 3d forum: http://forum.xda-developers.com/showthread.php?t=1970252 and found it to work on the rezound,inc 4g,sensation 4g,cdma evo 3d,and prolly several others.
this does NOT mean you can unlock your bootloader without going thru htcdev. all this means,is that if you accidentally unlocked your bootloader after s-off,you can get rid of the relocked watermark and get back to 100% locked prior to s-on for warranty purposes,without having to s-on and re-s off.
ive always been unlocked. for S&Gs,i dumped mmcblk0p3 and found the described "HTCU" at 0x8404. changed it to 0x00000000 and voila! back to locked
afterward,relfashed my origianl mmcblk0p3,wich brought me back to unlocked with no getting or flashing tokens.
this is NOT a patched or hex edited hboot.again,this is ONLY to get back your original ***locked*** status.
2 ways to do it:
1)old school
this assumes you to have drivers,adb/fastboot,a hex editor,a fair understanding about what youre doing,and the ability to follow directions on the linked thread
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:\mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HTxxxxxxxxxx device
c:\mini-adb_vigor>[COLOR="Red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3[/COLOR]
dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 9.519 secs (3481858 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb pull /sdcard2/mmcblk0p3[/COLOR]
2292 KB/s (33143808 bytes in 14.116s)
[COLOR="Blue"]*modify mmcblk0p3 with a hex editor[/COLOR]
c:\mini-adb_vigor>[COLOR="Red"]adb push mmcblk0p3mod /sdcard2/mmcblk0p3mod[/COLOR]
2478 KB/s (33143808 bytes in 13.059s)
c:\mini-adb_vigor>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3[/COLOR]
dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 18.937 secs (1750214 bytes/sec)
[email protected]:/ #[COLOR="red"] exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\mini-adb_vigor>
2)noob friendly
-download the appropriate zips,place on sd card.
-boot to recoverywipe cache/dalvik
-flash in recovery. i recomend to run query first,to make sure its working. tested on my personal rezound,inc 4g,sensation,and gsm evo 3d.
query:http://www.mediafire.com/download.php?jg8v4ady8nyc8bu
query_bootloader.zip f335f78f9f46469c823da0c671026de5
unlock:http://www.mediafire.com/download.php?il51rl2j1m8417b
unlock_bootloader.zip f335f78f9f46469c823da0c671026de5
lock:http://www.mediafire.com/download.php?05ow9uhw540p6jy
lock_bootloader.zip f335f78f9f46469c823da0c671026de5
a little bit of explanation. yes,the md5s are all the same. its the same file,just named differently. the script behaves based on the name of the zip. i knew if i only included 1 download and instructed folks to change the name there would be confusion,so this is my attempt to keep it simple. feel free to download one file and just change the name to make the other zips.
it also works to make your phone relocked if for some reason you want it that way(rename relock_bootloader.zip). i didnt include a zip for that because i figued there would be no demand.
before:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after:
sure,i could have easily faked the above photos,but i dint.
again,all credit goes to s trace on the above thread,be sure to clock the thanks button on his post. all i did was remove the device check per his instruction. DO NOT flash on other devices without checking for the proper location of the lock flag first.
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
enjoy
Might want to change that CID as well
*Madmoose* said:
Might want to change that CID as well
Click to expand...
Click to collapse
CID would obviously need chagned if one were returning to stock. it is easily chagned(when s-off) and not part of the same memory block as the lock flag,and thus not real imortant in the pics,or this thread. superCID is not as big deal when a phone is only used on one region/carrier,so i assume most folks are chanig it back anyway after unlock or s off.
i
I had a speaker bust on my inc4g so I got to test this out and it worked flawlessly
Sent from my ADR6410LVW using xda app-developers app
awsome! glad it was helpful
Beautiful! Thanks a bunch!

[how to]reset your lock status flag

with the rezound,some folks unknowingly re-unlocked after s off to regain use of fastbooot commands,after running ruus that replaced the patched jpbear hboot. i thot i would bring this here,in case there ever becomes a need.
i happened across this thread inthe gsm evo 3d forum: http://forum.xda-developers.com/showthread.php?t=1970252 and found it to work on the rezound,inc 4g,sensation 4g,cdma evo 3d,jetstream,MT4GS,Amaze 4g,evo lte,and prolly several others.
this does NOT mean you can unlock your bootloader without going thru htcdev. all this means,is that if you accidentally unlocked your bootloader after s-off,you can get rid of the relocked watermark and get back to 100% locked prior to s-on for warranty purposes,without having to s-on and re-s off.
ive always been unlocked. for S&Gs,i dumped mmcblk0p3 and found the described "HTCU" at 0x8404. changed it to 0x00000000 and voila! back to locked
afterward,relfashed my origianl mmcblk0p3,wich brought me back to unlocked with no getting or flashing tokens.
this is NOT a patched or hex edited hboot.again,this is ONLY to get back your original ***locked*** status.
*this is for s-off phones only
2 ways to do it:
1)old school
this assumes you to have drivers,adb/fastboot,a hex editor,a fair understanding about what youre doing,and the ability to follow directions on the linked thread
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:\mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HTxxxxxxxxxx device
c:\mini-adb_vigor>[COLOR="Red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3[/COLOR]
dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 9.519 secs (3481858 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb pull /sdcard2/mmcblk0p3[/COLOR]
2292 KB/s (33143808 bytes in 14.116s)
[COLOR="Blue"]*modify mmcblk0p3 with a hex editor[/COLOR]
c:\mini-adb_vigor>[COLOR="Red"]adb push mmcblk0p3mod /sdcard2/mmcblk0p3mod[/COLOR]
2478 KB/s (33143808 bytes in 13.059s)
c:\mini-adb_vigor>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3[/COLOR]
dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 18.937 secs (1750214 bytes/sec)
[email protected]:/ #[COLOR="red"] exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\mini-adb_vigor>
2)noob friendly
-download the appropriate zips,place on sd card.
-boot to recoverywipe cache/dalvik
-flash in recovery. i recomend to run query first,to make sure its working. tested on my personal amaze,jetstream,rezound,inc 4g,sensation,MT4GS,evo lte,and gsm evo 3d.
query:query_bootloader.zip
query_bootloader.zip f335f78f9f46469c823da0c671026de5
unlock:unlock_bootloader.zip
unlock_bootloader.zip f335f78f9f46469c823da0c671026de5
lock:lock_bootloader.zip
lock_bootloader.zip f335f78f9f46469c823da0c671026de5
a little bit of explanation. yes,the md5s are all the same. its the same file,just named differently. the script behaves based on the name of the zip. i knew if i only included 1 download and instructed folks to change the name there would be confusion,so this is my attempt to keep it simple. feel free to download one file and just change the name to make the other zips.
it also works to make your phone relocked if for some reason you want it that way(rename relock_bootloader.zip). i didnt include a zip for that because i figued there would be no demand.
before:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after:
sure,i could have easily faked the above photos,but i dint.
again,all credit goes to s trace on the above thread,be sure to click the thanks button on his post. all i did was remove the device check per his instruction. DO NOT flash on other devices without checking for the proper location of the lock flag first.
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
enjoy
special thanks
-brian for unlocking his bootloader,then dumping mmcblock0p3 to make sure it would work for cdma evo3d phones too
-brian and donb for fearless testing of the zip files on evo3d cdma
Links above seem to be broken...
working fine for me. try a different browser,or disable your antivirus/firewall temporarily

[S-OFF] revone - DEVELOPER EARLY ACCESS PREVIEW EDITION

MOD EDIT: In order to prevent undue questions and excessive off-topic I'm making this edit to the op to inform the users revone does not support HBOOT 1.54.​
What is "EARLY ACCESS PREVIEW"?
We want to give you S-OFF as soon as practically possible so an early access preview release is not a polished product but it does work (mostly). It will:-
* require knowledge of common android tools like adb and/or fastboot
* be a command line tool
* be rough around the edges
* probably crash sometimes
* fail to work everytime or in all cases or on different carrier ROMs - LET US KNOW if you get repeated failure on carrier variants.
* certainly not look pretty.
* despite being "early access" be very unlikely to brick your device (but naturally, this is possible, it's still a hack).
* give you a very good chance of getting S-OFF. Today. Right now.
Status
* revone has been known to grant S-OFF on the latest WWE & EU RUU, T-Mobile and AT&T versions, as well as Sprint HTC One.
* revone might also work on the Droid DNA 2.04 and 2.06. Awaiting (your) feedback.
Download
* Get the Android SDK for ADB. You may need to update to the latest version of the SDK for jellybean devices.
* Download revone: http://revolutionary.io/revone
Instructions
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
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 -u
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
Credits
revone is brought to you by the Revolutionary dev team.
We've been silent, we're back.
Disclaimer
Revolutionary dev team disclaims all responsibility for your use of revone (and any of our tools): If the world ends, it's not our fault. If your device spontaneously ignites, well, that's not our fault either. You make the choice to use our tool, we don't force it upon you.
Support
Please visit #revolutionary on the Freenode IRC network. We will try to support you in the best way possible, but remember, this is early access, and operators might be asleep or not available at the time you join. Just hang around and wait for someone to answer.
ALTERNATE revone binary (v0.2.1-wlj)
Alternate revone binary for the HTC J One (m7_wlj) only, if the main one crashes, reboots or otherwise does not work.
Download: revone-0.2.1-wlj
UPDATED revone binary (v0.2.1)
* Safety update: No longer allows -s 3 since this can lead to bricks with custom HBOOTs, use: fastboot oem writesecureflag 3 (which is safer - and checks such things)
* Fix: delusions of grandeur - revone now no longer reports success when it fails.
* Outside chance some previous failures will now be successful but most likely they will just correctly report failure.
Please note that due to the safety update ALL previous versions have been replaced with v0.2.1 and are hence no longer supported.
YOU WILL NOT RECEIVE SUPPORT FOR A VERSION LESS THAN v0.2.1
Download (and any previous link): revone-0.2.1
UPDATED revone binary (v0.2)
* Remove the random reboot feature.
* Vastly reduce the error -6 probability.
Download: revone-0.2
Use as per OP instructions renaming or name substituting as appropriate.
Reverting to S-ON (updated)
* ./revone -l
* fastboot oem writesecureflag 3
Instructions updated since stating "fastboot oem lock" was a fail - my bad! xD
Stuck with error: -1?
When initiating a reboot after "./revone -P" please press and hold the power button for 15 seconds.
To start the entire process from scratch please power off the device and wait 30 seconds, turn it on and continue to ."/revone -P".
Redistribution/Bundling revone
Permission is not given to redistribute and/or bundle revone into "one click" utilities (or similar). Please only obtain revone directly from us, this allows us to ensure the most up to date version is available in case of any critical issues.
Many thanks for your understanding.
Thanks this made my day
I wanted to update my post (Monday) as I have the priviledge of being on the first page.
I did struggled to get this installed, the first two attempts failed and told me to reboot, the third worked but did not S-Off the device.
Eventually, after multiple combinations of "-P" and "-s 0" (with all reporting successes) and my device was suddenly S-Off.
Then of course, locking and removing the tamper were easily done.
Excellent work everyone involved!
My stock HTC One with HTC_001 (purchased from Phones4U UK) on the EE network is now unlocked!
Electronic Punk said:
I am so in.
First attempt failed, rebooting.
Second attempt failed too.
Error code -6
Click to expand...
Click to collapse
Device mainver? I can check it out if there's a RUU/OTA for it.
squirt
T-Mobile USA, Device doesn't get a error, but doesn't reboot on its own either, tried four times. Tried rebooting manually and continuing, no go. No errors, but no S-OFF either.
Worked without a hitch on my One! Thanks!
itzsnookums said:
T-Mobile USA, Device doesn't get a error, but doesn't reboot on its own either, tried four times. Tried rebooting manually and continuing, no go. No errors, but no S-OFF either.
Click to expand...
Click to collapse
What output do you yet?
very thanks revteam!
I use HTC J butterfly. 1.29.970.1 version (DNA 2.06/2.05 same situation)
root method is temproot
c:\adb\DLX_J>adb push revone /data/local/tmp/
2438 KB/s (646704 bytes in 0.258s)
c:\adb\DLX_J>adb shell chmod 755 /data/local/tmp/revone
c:\adb\DLX_J>adb shell
[email protected]:/ $ /data/local/tmp/run_root_shell
/data/local/tmp/run_root_shell
Attempt perf_swevent exploit...
writing address is 8e55
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # ./revone -P
./revone -P
revone failed (error code = 2
error code 2...?
Please advise me...!
thanks
graffixnyc said:
Worked without a hitch on my One! Thanks!
Click to expand...
Click to collapse
You have really S-OFF now?
Worked here. First couple of times it failed after the entering su part, so tried without su and worked fine. Thanks!
kmdm said:
What output do you yet?
Click to expand...
Click to collapse
You mean this??
I:\One>adb shell
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 revone
chmod 755 revone
[email protected]:/data/local/tmp # su
su
[email protected]:/data/local/tmp # ./revone -P
./revone -P
revone successful - please reboot to continue.
[email protected]:/data/local/tmp #
ATT HTC One, All commands report successful however upon reboot after issuing the S-OFF and Tampered command, nothing gets changed.
Okay, this is a good day!
S-OFF worked on the first try, had to rerun with -t to remove TAMPERED.
Many thanks to the guys who made this possible!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: 1BL09825KR231950Y
:highfive: yeah^^
When I ran it I got S-off but it didn't reset the Tampered. I had to run the -t switch alone a second time for it to reset it
itzsnookums said:
You mean this??
I:\One>adb shell
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 revone
chmod 755 revone
[email protected]:/data/local/tmp # su
su
[email protected]:/data/local/tmp # ./revone -P
./revone -P
revone successful - please reboot to continue.
[email protected]:/data/local/tmp #
Click to expand...
Click to collapse
At that stage you reboot manually and continue to step 6.
i did no change, ill try again, thank you....
graffixnyc said:
When I ran it I got S-off but it didn't reset the Tampered. I had to run the -t switch alone a second time for it to reset it
Click to expand...
Click to collapse
Same. Sprint HTC One. Otherwise it's reporting s-off.

Error "No such file or directory" - dd dump userdata partition

Hi there,
When I tried to restore image file back to the rooted device under adb shell su privilege,
Code:
adb shell
$ su
# dd if=43.img of=/dev/mmcblk0p43
43.img is the image extracted from the userdata partition (mmcblk0p43) and now in the directory of adb (platform-tools) locally.
It returned
Code:
dd: 43.img: No such file or directory
How to fix it?
Thanks in advance.
May you need any additional information, please do not hesitate to ask me.
Regards,
block?
'No such file or directory' means, there exist no such file or directory.
CXZa said:
block?
Click to expand...
Click to collapse
It produced the same result.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need to be in the file's directory for that to work.
That is in external sd card dir or in usb storage dir if using it.
Meant the out file, The block was missing in the path.
# dd if=43.img of=/dev/block/mmcblk0p43
Or use push to write it from the PC...
Wondering how android reacts if you're doing that while the system is running. I.e. not through the TWRP.
dd: 43.img: No such file or directory​ means there is no such file 43.img in
current directory (phones / rootdir)
wenyendev said:
43.img is the image extracted from the userdata partition (mmcblk0p43) and now in the directory of adb (platform-tools) locally.
Click to expand...
Click to collapse
assuming you have TWRP recovery, you can use adb push
Code:
adb shell umount /sdcard
adb shell umount /sdcard
adb shell umount /data
adb push /path/to/43.img /dev/block/mmcblk0p43
Spoiler: hot swap with adb shell su
if you insist in hot swapping during runtime you could use adb exec-in. however it seems broken as it did not work for me.
Beware: this will crash your android session!
Code:
adb shell "su -c 'killall system_server; stop'"
adb shell "while grep -q ' /data/media ' /proc/mounts; do su -c 'umount -l /data/media'; done"
adb shell "while grep -q ' /data ' /proc/mounts; do su -c 'umount -l /data'; done"
adb shell "su -c 'dd bs=1m of=/dev/block/mmcblk0p43'" < /path/to/43.img
adb reboot recovery
CXZa said:
You need to be in the file's directory for that to work.
That is in external sd card dir or in usb storage dir if using it.
Meant the out file, The block was missing in the path.
# dd if=43.img of=/dev/block/mmcblk0p43
Or use push to write it from the PC...
Wondering how android reacts if you're doing that while the system is running. I.e. not through the TWRP.
Click to expand...
Click to collapse
Thanks for your replies @CXZa @aIecxs
Sorry I uploaded the wrong screenshot @CXZa, "block" was actually added in dd if=43.img of=/dev/block/mmcblk0p43, but produced the same error.
Could you please kindly specify in which directory of SD card should 43.img be dropped so that dd if=43.img of=/dev/block/mmcblk0p43 would work?
@Alecxs adb push 43.img /dev/block/mmcblk0p43 pushed 43.img back to mmcblk0p43.
But after the device rebooted into system, the data (photos, apps, etc.) contained in 43.img (that was extracted from the same but rooted device) were not restored, and the device was unrooted, as if the device had undergone a factory reset. Is it normal for such adb push?
Would it be possible that dd if=43.img of=/dev/block/mmcblk0p43, or any other alternatives, restore the data extracted previously back to the device?
Thanks in advance.
sure you did from TWRP recovery mode? in android mode might be it's not possible to restore during runtime. set selinux permissive and rename the file mmcblk0p43 (no suffix) before actually trying to push (just to rule out confusing adb with /dev/block/mmcblk0p43/43.img)
(untested)
Code:
adb shell
$ su
# setenforce 0
# getenforce
# exit
$ exit
adb root
adb push mmcblk0p43 /dev/block/mmcblk0p43
for MicroSD card check path on device
(example)
Code:
adb shell
$ ls -1 /storage
$ ls /storage/0815-4711
consider this does not work on FAT32 make sure MicroSD card is formatted exFAT and 43.img file size on MicroSD card is actually larger than 4 GiB.

Categories

Resources