Develop Bugs

Restore gfree backup

Hello all,
I've had a DZ for nearly 2 weeks now, and have been holding off on installing roms, overclocking etc until there were clear, reversible guidlines available.
A few days ago I was being curious and ended up doing this the UBERROOT guide.
Essentially I temprooted using Visionary then executed the gfree script on my PC:
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
This went well, and when I got to the bootloader I could see indeed that my S was OFF.
However, before I go any further I want to know how to reverse what I've done. This is mentioned at the bottom of the UBERROOT guide:
'run gfree, which will create a new backup of partition 7 in its unlocked state.
this will disable wp on the emmc, as well as remove the brq filter from the kernel.
at this point, you can dd if=/wherever/your/partition7-relock.img of=/dev/block/mmcblk0p7
sync; reboot'
I found the backup, although it was a .bin file not .img
I entered in the command above, but my phone rebooted before I could enter the 'sync' command. My S is still off, it would seem.
So my question to you fine people, having typed all this is:
How can I use the gfree backup to return my phone back to stock?

nofixio said:
How can I use the gfree backup to return my phone back to stock?
Click to expand...
Click to collapse
You can use the "dd" command to copy back the image of that original partition, as you mention.
However, the latest version of gfree now includes some new options to un-do that stuff, e.g. you can switch S-ON back on and change your SID via options. See the Wiki on this - http://forum.xda-developers.com/wik...Phone.2C_Set_SuperCID.2C_and_Turn_Radio_S-OFF

nofixio said:
Hello all,
I've had a DZ for nearly 2 weeks now, and have been holding off on installing roms, overclocking etc until there were clear, reversible guidlines available.
A few days ago I was being curious and ended up doing this the UBERROOT guide.
Essentially I temprooted using Visionary then executed the gfree script on my PC:
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
This went well, and when I got to the bootloader I could see indeed that my S was OFF.
However, before I go any further I want to know how to reverse what I've done. This is mentioned at the bottom of the UBERROOT guide:
'run gfree, which will create a new backup of partition 7 in its unlocked state.
this will disable wp on the emmc, as well as remove the brq filter from the kernel.
at this point, you can dd if=/wherever/your/partition7-relock.img of=/dev/block/mmcblk0p7
sync; reboot'
I found the backup, although it was a .bin file not .img
I entered in the command above, but my phone rebooted before I could enter the 'sync' command. My S is still off, it would seem.
So my question to you fine people, having typed all this is:
How can I use the gfree backup to return my phone back to stock?
Click to expand...
Click to collapse
When you run gfree, it creates a bin file in your sd card. That bin file you shall rename it to "whatever".img, to be more specific rename it to partiiton7-relock.img.
Now once you did this, just run gfree again:
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
Once done the above, just download terminal emulator and from there run:
su
dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7
sync
exit
And reebot the phone, Now you can go and see you are S-ON.
This method above works without a problem as myself have tried several times, however as steviewevie mentioned, the new version of gfree does this easier.

buzmay said:
When you run gfree, it creates a bin file in your sd card. That bin file you shall rename it to "whatever".img, to be more specific rename it to partiiton7-relock.img.
Now once you did this, just run gfree again:
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
Once done the above, just download terminal emulator and from there run:
su
dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7
sync
exit
And reebot the phone, Now you can go and see you are S-ON.
This method above works without a problem as myself have tried several times, however as steviewevie mentioned, the new version of gfree does this easier.
Click to expand...
Click to collapse
How to get that file (partition7-relock.img)? Because I formated the card after g-free method and I runned the official Ruu, so now I have that stupid S-Off, I need it S-On...

Niiceg said:
How to get that file (partition7-relock.img)? Because I formated the card after g-free method and I runned the official Ruu, so now I have that stupid S-Off, I need it S-On...
Click to expand...
Click to collapse
You don't need the backup for that. Just check the Wiki to find the options for gfree that will set it back to S-ON
Sent from my HTC Desire Z

steviewevie said:
You don't need the backup for that. Just check the Wiki to find the options for gfree that will set it back to S-ON
Sent from my HTC Desire Z
Click to expand...
Click to collapse
I don't find anything more than this guide:
Turning S-On
If you are returning your Vision to stock, you will want to flash your stock ROM and Recovery image before starting this, as root permissions and S-Off are required for both of those processes.
Remove Gfree (turn back S-On):
When you first ran Gfree, it automatically backed up your stock partition 7 (with S-On) and placed it on your microSD card as a file named part7-(something).bin and you will need to rename this file to: partition7-relock.img
Open up your ADB command prompt on your computer (with your phone plugged in) and type the following exactly as shown:
Code:
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7
sync
reboot bootloader
Your phone will reboot into bootloader. Look at the first line. The end should now say "S-On".

steviewevie said:
You don't need the backup for that. Just check the Wiki to find the options for gfree that will set it back to S-ON
Sent from my HTC Desire Z
Click to expand...
Click to collapse
I think they removed the automatic option for some reason, I beleive it was in version v.3 and now v.2 is back up. I was looking for that option for someone else early yesterday and noticed its not on the Wiki anymore, unless I missed it, but Im prettty sure I didn't. So I think were back to using the "dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7" command.
Update: On fattire's thread they said they took down v3 because people were having problems with it and are now advising using v2 and the old restore method.

joemm said:
I think they removed the automatic option for some reason, I beleive it was in version v.3 and now v.2 is back up. I was looking for that option for someone else early yesterday and noticed its not on the Wiki anymore, unless I missed it, but Im prettty sure I didn't. So I think were back to using the "dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7" command.
Click to expand...
Click to collapse
Where to get that file if i already formated the card?!

Niiceg said:
Where to get that file if i already formated the card?!
Click to expand...
Click to collapse
There is no where to get the file if you erased/formatted your sdcard without saving it somewhere else, the instructons on gfree tell you to do this:
"gfree created a backup of your original partition 7 at /sdcard/part7backup-<time>.bin you might consider copying this to a safe location on your computer."
So if you didnt do this I really dont know what you can do. I have my part7backup but I dont know if its specific to my device or if anyone can use it.

joemm said:
There is no where to get the file if you erased/formatted your sdcard without saving it somewhere else, the instructons on gfree tell you to do this:
"gfree created a backup of your original partition 7 at /sdcard/part7backup-<time>.bin you might consider copying this to a safe location on your computer."
So if you didnt do this I really dont know what you can do. I have my part7backup but I dont know if its specific to my device or if anyone can use it.
Click to expand...
Click to collapse
Well, What device you have? Z or G2? I think that it's not specific, because all phones are the same ;D

Niiceg said:
I don't find anything more than this guide:
Turning S-On
Click to expand...
Click to collapse
Look at http://forum.xda-developers.com/wik...Phone.2C_Set_SuperCID.2C_and_Turn_Radio_S-OFF
Scroll down to the bit that shows you the usage message for gfree and check out the "-s" option

joemm said:
I think they removed the automatic option for some reason, I beleive it was in version v.3 and now v.2 is back up. I was looking for that option for someone else early yesterday and noticed its not on the Wiki anymore, unless I missed it, but Im prettty sure I didn't. So I think were back to using the "dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7" command.
Update: On fattire's thread they said they took down v3 because people were having problems with it and are now advising using v2 and the old restore method.
Click to expand...
Click to collapse
The latest gfree 0.03 had problems, yes, so they went back to 0.02 in the Wiki. But as my previous post shows, you can still un-do things with gfree 0.02.
The only reason to use the backup of partition 7 that I can think of is if you don't know what your original CID was to reset to, or if you want to SIM Lock your phone again (there doesn't seem to be an undo option for the SIM Unlock).

steviewevie said:
The latest gfree 0.03 had problems, yes, so they went back to 0.02 in the Wiki. But as my previous post shows, you can still un-do things with gfree 0.02.
The only reason to use the backup of partition 7 that I can think of is if you don't know what your original CID was to reset to, or if you want to SIM Lock your phone again (there doesn't seem to be an undo option for the SIM Unlock).
Click to expand...
Click to collapse
Ok, I see the option for sec-flag on/off but does that also restore the sim lock?
Sent from my T-Mobile G2 using XDA App

joemm said:
Ok, I see the option for sec-flag on/off but does that also restore the sim lock?
Click to expand...
Click to collapse
No it doesn't as far as I know, but that's why I said restoring SIM lock was the only real use for that part7 backup that I could think of.

steviewevie said:
No it doesn't as far as I know, but that's why I said restoring SIM lock was the only real use for that part7 backup that I could think of.
Click to expand...
Click to collapse
I wasn't sure myself, thanks.
Sent from my T-Mobile G2 using XDA App

steviewevie said:
No it doesn't as far as I know, but that's why I said restoring SIM lock was the only real use for that part7 backup that I could think of.
Click to expand...
Click to collapse
Okey, can you tell how to do everything? Because I don't know anything with that gfree... And there is no instruction... Please, help me get the S-On

I have PM'd the author of gfree about an option for SIM re-lock, because that would be useful. I guess you will still need some sort of carrier string which it needs re-locking to though ? Would be handy if perhaps gfree told you what that was before you unlocked it.

Im in the same boat as niiceg, I cannot find my backup and have had no luck in my searchs. Any Idea's what I can do from here?
Thanks in advance..
ps I'm guess my next step is to re root and do
su
cd /data/local
chmod 777 gfree
./gfree -s on
sync
???

bildo said:
Im in the same boat as niiceg, I cannot find my backup and have had no luck in my searchs. Any Idea's what I can do from here?
Thanks in advance..
ps I'm guess my next step is to re root and do
su
cd /data/local
chmod 777 gfree
./gfree -s on
sync
Click to expand...
Click to collapse
Yes, you just need to run "gfree -s on" as root to go from radio S-OFF to S-ON, no need to find/restore that backup.

gfree

Hi
Is it possible to use gfree on a non-rooted phone just to do the SIM unlock?
I guess I could do temp root + SIM unlock, right?
Bell Desire Z

I'm wondering the same thing. I just wanted a sim unlock for the time being so can I just temp root the phone?

The phone needs to be temp rooted (use rage) and then you can do the subsidy unlock method. Once that is complete it will stick with the phone after reboot if I'm not mistaken. You will just lose your temp root. But why wouldn't you want full root? Its really not that much more work. Especially if you already have adb on your computer.
Sent from my HTC Vision using XDA App

If you don't disable the NAND write protection via a permanent root method, then any changes you make via a temp root will not be written to permanent storage. So you'll lose those changes after a reboot.
So you need perm root to use gfree and make it stick. In fact gfree makes the root permanent for you. See the Wiki for details.

so I need to do s-off + sim unlock?

gfree_verify returns simlock=00, even without S-OFF
So I think it means it worked, no? Anyways why would there be an option to do only SIM unlock in gfree if you can't do it without S-OFF?

zorxd said:
gfree_verify returns simlock=00, even without S-OFF
So I think it means it worked, no? Anyways why would there be an option to do only SIM unlock in gfree if you can't do it without S-OFF?
Click to expand...
Click to collapse
You're right. Sorry, I misunderstood the question, at least partially. gfree turns off the NAND write-protection so that it can make its changes, so you can run it with temp root if you really want. But then you've very nearly achieved permanent root, all you need are the su and Superuser.apk files, plus running the "root" script.

I know, thanks
But I am a minimalist. I only enable features that I use.
There should be a simpler "how to". It's as easy as:
on computer:
get gfree and rage executables
adb push gfree /data/local/tmp
adb push rage /data/local/tmp
adb shell chmod 777 /data/local/tmp/*
on phone:
download and open terminal emulator
/data/local/tmp/rage
menu->reset terminal
open terminal emulator (force close)
open terminal emulator again
/data/local/tmp/gfree -S
reboot

zorxd said:
I know, thanks
But I am a minimalist. I only enable features that I use.
There should be a simpler "how to". It's as easy as:
on computer:
get gfree and rage executables
adb push gfree /data/local/tmp
adb push rage /data/local/tmp
adb shell chmod 777 /data/local/tmp/*
on phone:
download and open terminal emulator
/data/local/tmp/rage
menu->reset terminal
open terminal emulator (force close)
open terminal emulator again
/data/local/tmp/gfree -S
reboot
Click to expand...
Click to collapse
Your right, you are a minimalist
And this is exactly what you need to do to get sim-unlocked
I still would recommend you to -s off -c 11111111 too to get radio s-off and super-cid. In case you install the newer firmware versions by OTA you will not be able to:
- temp-root anymore because htc patched the exploit that rage used.
- not be able to change s-on/s-off perm-root because wpthis and gfree do not work on higher radio firmware versions
- not be able to downgrade to a lower firmware version (because this needs either radio s-off/super-cid or temp-root to be able to edit the version info in the misc partition 17
Just my suggestion - have fun - Guhl

Ok so basically if I do S-OFF and remove carrier id now you are saying that it would be permanent, even if I upgrade to a newer firmware?

zorxd said:
Ok so basically if I do S-OFF and remove carrier id now you are saying that it would be permanent, even if I upgrade to a newer firmware?
Click to expand...
Click to collapse
Yes for now this is permanent, the new updates to not change this.
But the new updates prevent you from rooting and changing any of these.
But if you are S-OFF you can downgrade and then you can change everything you want again.
Or let me summarize it like this:
- If you are radio s-off/super-cid you are safe because you will keep it and you still can downgrade

Thanks for the info. I ended up doing all three options with gfree.
Quick question: if I ever have to send my phone in for warranty, is there a way to reverse these things?

Goozy said:
Thanks for the info. I ended up doing all three options with gfree.
Quick question: if I ever have to send my phone in for warranty, is there a way to reverse these things?
Click to expand...
Click to collapse
Yes. gfree has options to un-do those actions, see the Wiki for details.

Need Help Gaining S-OFF

Hey guys, I need help understanding how to achieve S-OFF using Gfree(i heard this was the safest/easiest way) also is this different than using adb? sorry for being n00b but i need help does anyone have guide to gain S-OFF, i bought my phone on the 28th of December so i assume it is 1.72 so do i have to downgrade or something before rooting
again i would appreciate a guide off rooting and gaining s-off on 1.72 using gfree and adb
thanks guys

zbrah said:
Hey guys, I need help understanding how to achieve S-OFF using Gfree(i heard this was the safest/easiest way) also is this different than using adb? sorry for being n00b but i need help does anyone have guide to gain S-OFF, i bought my phone on the 28th of December so i assume it is 1.72 so do i have to downgrade or something before rooting
again i would appreciate a guide off rooting and gaining s-off on 1.72 using gfree and adb
thanks guys
Click to expand...
Click to collapse
First thing you need to do is reading the WIKI
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
To use gfree you will need to set up ADB on your computer first. guide:
http://forum.xda-developers.com/showthread.php?t=865685
and regarding 1.72 update you probably need to downgrade first but i would read this 2 posts
http://forum.xda-developers.com/showthread.php?t=886023
http://forum.xda-developers.com/showthread.php?t=905261

bahmanxda said:
First thing you need to do is reading the WIKI
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
To use gfree you will need to set up ADB on your computer first. guide:
http://forum.xda-developers.com/showthread.php?t=865685
and regarding 1.72 update you probably need to downgrade first but i would read this 2 posts
http://forum.xda-developers.com/showthread.php?t=886023
http://forum.xda-developers.com/showthread.php?t=905261
Click to expand...
Click to collapse
ok i understand how to get adb but the last two are for the desire z can anyone confirm that the this will work for the htc g2(american version) thanks for everyones help on this forum

zbrah said:
ok i understand how to get adb but the last two are for the desire z can anyone confirm that the this will work for the htc g2(american version) thanks for everyones help on this forum
Click to expand...
Click to collapse
I would just a) verfiy you have adb setup and working, and then follow that wiki here: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
Just to verify, you are holding the T-mobile G2? If so you're fine even if you updated to 1.22 (for the tmob g2) ...just do an about phone in settings and scroll down to see what update you're on.
You'll read about possibly needing to do some hex editing to revert to 1.19 (if indeed you updated to 1.22), but steviewevie might correct me but I don't think that is the case any longer with the gfree method.

yes i have the 1.22 thanks for correcting me, so after i have adb up and working what are my next steps to root and s-off?

zbrah said:
yes i have the 1.22 thanks for correcting me, so after i have adb up and working what are my next steps to root and s-off?
Click to expand...
Click to collapse
Follow that wiki guide Really that's the best advice I can give, first you'll adb push some files to the phone to do a quick temp root. Then, you'll adb push some more files over and do the deed.
edit: right about here once adb is g2g http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Follow the Requirements part, do not pass go until you have it all including the terminal emulator app installed off the market (free is fine)

zbrah said:
ok i understand how to get adb but the last two are for the desire z can anyone confirm that the this will work for the htc g2(american version) thanks for everyones help on this forum
Click to expand...
Click to collapse
I assumed you have desire z because you said you got the 1.72 update!!!

sorry for the confusion guys im really sorry, i feel like a n00b but yea i have g2 not desire z so i have 1.22 so i can just root, im looking at the guide on the wiki and it says Make sure your phone's sdcard is mounted by your phone and not your computer when following these instructions so basically is saying make sure your sd card is in your phone not in the computer, right?

zbrah said:
sorry for the confusion guys im really sorry, i feel like a n00b but yea i have g2 not desire z so i have 1.22 so i can just root, im looking at the guide on the wiki and it says Make sure your phone's sdcard is mounted by your phone and not your computer when following these instructions so basically is saying make sure your sd card is in your phone not in the computer, right?
Click to expand...
Click to collapse
Right, just make sure you're not turned on to usb disk mode (not enabled) so the phone has use of it and not your pc.

zkid2010 said:
Right, just make sure you're not turned on to usb disk mode (not enabled) so the phone has use of it and not your pc.
Click to expand...
Click to collapse
how do i do that?

zbrah said:
how do i do that?
Click to expand...
Click to collapse
You should be ok. On the G2 you have to select "USB sharing" to mount the SD card on your PC, so by default your phone should be mounting it.
Sent from my HTC Desire Z

gfree usage:
gfree [-h|-?|--help] [-v|--version] [-s|--secu_flag on|off]
-h | -? | --help: display this message
-v | --version: display program version
-s | --secu_flag on|off: turn secu_flag on or off
-c | --cid <CID>: set the CID to the 8-char long CID
-S | --sim_unlock: remove the SIMLOCK
-f | --free_all: same as --secu_flag off --sim_unlock --cid 11111111
i dont get this part of the wiki do i type this into the command prompt?

zbrah said:
gfree usage:
gfree [-h|-?|--help] [-v|--version] [-s|--secu_flag on|off]
-h | -? | --help: display this message
-v | --version: display program version
-s | --secu_flag on|off: turn secu_flag on or off
-c | --cid <CID>: set the CID to the 8-char long CID
-S | --sim_unlock: remove the SIMLOCK
-f | --free_all: same as --secu_flag off --sim_unlock --cid 11111111
i dont get this part of the wiki do i type this into the command prompt?
Click to expand...
Click to collapse
NO.... these are the options you can run as part of the Gfree command, for example:
Code:
su
cd /data/local
chmod 777 gfree
./gfree[COLOR="Red"] -f[/COLOR]
sync
If you ran the -f option it would free everything, meaning it would "Radio S-Off, Sim Unlock and it would SuperCID(CarrierID) your phone.
OR
Code:
su
cd /data/local
chmod 777 gfree
./gfree [COLOR="red"]-S[/COLOR]
sync
If you ran the -S option it would only unlock your SIM to use other carrier SIM cards.
And so on.....

Its all clearly there in the wiki...
Sent from my T-Mobile G2 running Cyanogenmod.

i now have S-Off but i am still have no network. I am using Airtel in India. Any ideas, I booted holding the volume down and it said i had S-off I becoming sort of frustrated now with the phone

zbrah said:
i now have S-Off but i am still have no network. I am using Airtel in India. Any ideas, I booted holding the volume down and it said i had S-off I becoming sort of frustrated now with the phone
Click to expand...
Click to collapse
Did you run a full unlock so that you could use Airtels SIM?
Sent from my T-Mobile G2 using XDA App

yea i did the unlock using the tmobile code that didnt work still no network. then i used visionary (unlockr method) to gain S-off. i achieved s-off but still have no network connection.

zbrah said:
yea i did the unlock using the tmobile code that didnt work still no network. then i used visionary (unlockr method) to gain S-off. i achieved s-off but still have no network connection.
Click to expand...
Click to collapse
There were lots of reports of unlock codes causing the phone to not find networks. You need to follow the gfree method explained in the wiki. This will fix the no network issue (if it is the same as everyone else's anyway).

[Tool] Downgrade VivoW with hboot 0.98

Windows: Disable or remove all phone, PDA, MP3 sync softwares, including HTC Sync, itunes, and all Antivirus software and suspend all unnecessary processes.
Windows: Install HTC USB Drivers on your PC. http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
64 bit Linux Users: Android tools in the kit are 32 bit. You will need to install ia32-libs (Debian) or equivelent if they are not already installed. Debian/Ubuntu: sudo apt-get install ia32-libs
Get adb and fastboot working on your PC
Start with phone in Charge Only mode, sdcard mounted by phone, not PC, and USB debugging enabled
A kit with everything needed (including adb and fastboot) including scripts. vwhk-12102011-c.zip MD5: 26a2dbcb96d82153add7edaccd157996
IMPORTANT: Run the Linux script as ROOT, run the Windows script as Admin.
Run Revolutionary for S-OFF & CWM if desired after downgrade. http://revolutionary.io/
Notes:
No goldcard needed for Verizon DINC2. If you ask this, you'll get nothing but hate.
Yes, this wipes data and downgrades the ROM completely.
Code:
adb shell rm -r /data/local/tmp/*
adb push zergRush /data/local/tmp/zergRush
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/zergRush
adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
adb reboot bootloader
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip
fastboot reboot
Thanks to:
Revolutionary - for everything they do
Ch4lky - zergRush
Guhl - misc_version

Trying now
EDIT: I don't want this post to confuse anyone... I missed a step but this worked perfect for me.

loudaccord said:
Trying now
Dumb question... then I can run the regular revolutionary PRE4 to get s-off and install cwm recovery?
stuck on adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
C:\android-win-tools>adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_versi
on -s 2.18.605.3'
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up partition 17...
Error opening backup file.
C:\android-win-tools>fastboot oem rebootRUU
< waiting for device >
Can't get past there.
Click to expand...
Click to collapse
what happened when you tried to get temproot with zergrush?
was the phone in charge only mode? It needs be to write a backup file to the sdcard.
the < waiting for device > error is because the fastboot driver is not installed or there is contention with some program.
i missed a step; updated code above:
prerequisite: adb and fastboot fully working.

attn1 said:
what happened when you tried to get temproot with zergrush?
was the phone in charge only mode? It needs be to write a backup file to the sdcard.
the < waiting for device > error is because the fastboot driver is not installed or there is contention with some program.
prerequisite: adb and fastboot fully working.
Click to expand...
Click to collapse
Temproot with zergrush said that it was successful, phone is on charge only mode.
looks like fastboot doesn't seem to be working, I have it installed but I'll have to get to the bottom of this.
Any way for me to test if fastboot is working easily?

loudaccord said:
Temproot with zergrush said that it was successful, phone is on charge only mode.
looks like fastboot doesn't seem to be working, I have it installed but I'll have to get to the bottom of this.
Any way for me to test if fastboot is working easily?
Click to expand...
Click to collapse
I missed the adb reboot step. check the code above for where that line goes.

attn1 said:
I missed the adb reboot step. check the code above for where that line goes.
Click to expand...
Click to collapse
cool, trying again
edit... that worked... sending zip now.
edit2: ran through all the commands... going to try to get s-off now. Thanks!
edit3: Success

loudaccord said:
edit3: Success
Click to expand...
Click to collapse
Groovy. Have fun.

Does this mean alpharevx isnt working on a 2.3.4 root? Is this the only way or just a way if you dont want to wait?
Sent from my ADR6350 using xda premium

Bob-o said:
Does this mean alpharevx isnt working on a 2.3.4 root? Is this the only way or just a way if you dont want to wait?
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
It means its not working on any hboot other than 0.97

I saw the tool tweeted by AlpharevX. I wasn't sure if it would work for Inc2. I am already rooted, but thank you for writing a guide for us!!!!

subscribing.
so this is a legitimate way to root the .98 dinc2?? is it restore able to stock or is it permanent? thanks

lddrew said:
subscribing.
so this is a legitimate way to root the .98 dinc2?? thanks
Click to expand...
Click to collapse
Yes.
lddrew said:
is it restore able to stock or is it permanent?
Click to expand...
Click to collapse
is question able to muster or is it nonsensical?

disregard that last question, sorry i had read that if rooting it with something other than AlphaRevX that restoring it to stock may be more complicated. sorry about that.
thank you for the info

I know im prolly get flamed for askin this noob question, but how do i get adb and fastboot up on my laptop? I have rooted my fascinate and was good with odin, but im still learnin htc stuff. Thanks in advance.
Bob
Sent from my ADR6350 using xda premium

Bob-o said:
I know im prolly get flamed for askin this noob question, but how do i get adb and fastboot up on my laptop? I have rooted my fascinate and was good with odin, but im still learnin htc stuff. Thanks in advance.
Bob
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
Google it..it has step by step instructions on the website
Sent from my Incredible 2 using xda premium

Bob-o said:
I know im prolly get flamed for askin this noob question, but how do i get adb and fastboot up on my laptop? I have rooted my fascinate and was good with odin, but im still learnin htc stuff. Thanks in advance.
Bob
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
thats a fair question, but really, the answers are everywhere. I'll make it easy for you. Check back on post 1. I'll update it.

attn1:
You, Sir, are Incredible squared!!(No pun intended ) Do you realize how many searches and web pages I went through in vain before coming to this workaround. Awesome, to say the least. Thanks ever so much for this write up, it is greatly appreciated, and a beer or two (donation) will be coming your way Friday.
I had to get a replacement for my rooted DINC2, and wouldn't you know it, they sent me out one with the 0.98 bootloader. I thought all hope was lost, well, at least until revolutionary found an exploit for the 0.98. This has helped tremendously.
Thanks again ever so much,
Chris

attn1 said:
thats a fair question, but really, the answers are everywhere. I'll make it easy for you. Check back on post 1. I'll update it.
Click to expand...
Click to collapse
Thank you very much.
Sent from my ADR6350 using xda premium

okay i have the folder extracted in my downloads folder, it keeps saying the script location can't be found. i am confused. can you elaborate on the bits about where to put the files and whatnot before you execute the script??

lddrew said:
okay i have the folder extracted in my downloads folder, it keeps saying the script location can't be found. i am confused. can you elaborate on the bits about where to put the files and whatnot before you execute the script??
Click to expand...
Click to collapse
really? open a cmd prompt as admin and run hack-vivow.cmd

[how to] lock/unlock your bootloader without htcdev(s-off required)

this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock.
originally,we used a zip file flashable in recovery. i have found it to work on gsm devices with 1.44 hboot and CW recovery. it did not work with twrp. if the following is too scary,feel free to test the zip files. that thread,info,and downloads can be found here. since not all recoverys are working,these values can be changed with simple adb commands.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.
*you must be s off.
*you must have superuser installed(see this thread if you need help installing superuser. use the keep bootloader locked directions)
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for giving me the echo comand,so yall didnt need to dump,edit with a hex editor,and copy back
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
-kdj67f for fearlessly testing and putting up some screenshots in post 5. thanks!
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
*i have tested this on my gsm htc one. if someone wants to test on vzw,ill add you to the credits

mine!

So, this will work with hboot 1.54? And are you sure the memory blocks are correct for Verizon? I will test...
I'm s-off, stock Rom, cwm recovery and rooted.
Sent from my HTC6500LVW using XDA Premium 4 mobile app

kdj67f said:
So, this will work with hboot 1.54? And are you sure the memory blocks are correct for Verizon? I will test...
I'm s-off, stock Rom, cwm recovery and rooted.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
99% sure we can certainly dump p3 and have a look-see first,if you'd like. We woukd need a dump from someone whose unlocked or relocked
Sent from my HTC One using Tapatalk 2

99% is good enough for me haha! Phone just hut 50% charged, give me a minute. Will post back with pictures.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 08:56 PM ---------- Previous post was at 08:41 PM ----------
Confirmed, code working. Flags set/reset. Phone even reboots and works will upload pics/screenshots.
Thanks!
Starting out unlocked:
Locking:
Locked:
Unlocking:
Re-unlocked:
Very good work!

Awesome! Thanks for confirming
Sent from my HTC One using Tapatalk 2

That was super easy... great write up! This will save so much time getting an unlocktoken and running through HTCdev. Many thanks!

scotty1223 said:
99% sure we can certainly dump p3 and have a look-see first,if you'd like. We woukd need a dump from someone whose unlocked or relocked
Click to expand...
Click to collapse
Verizon HTC One here, S-Off with SuperSU but otherwise stock, locked bootloader, hboot 1.54. I just did
Code:
dd if=/dev/block/mmcblk0p3 of=orig bs=1 seek=33796 count=4
and looked at the resulting dump and it has "PGFS" not nulls at that offset. I'm wondering if we should write "PGFS" back on Verizon/hboot 1.54 and not nulls?

bjorheden said:
Verizon HTC One here, S-Off with SuperSU but otherwise stock, locked bootloader, hboot 1.54. I just did
Code:
dd if=/dev/block/mmcblk0p3 of=orig bs=1 seek=33796 count=4
and looked at the resulting dump and it has "PGFS" not nulls at that offset. I'm wondering if we should write "PGFS" back on Verizon/hboot 1.54 and not nulls?
Click to expand...
Click to collapse
sounds like youre looking at offsets 00 01 02 03. every device ive looked at so far has the PGFS at that location. i havent looked ata vzw p3,but t mobile follows that. youll find the HTCU,HTCL,or nulls at 8404 8505 8406 8407.
im not sure your command is showing you the correct location. id dump and look at the whole thing.
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3

Hey Scotty,
I can't thank you enough for this info. I really didn't want to unlock via htcdev and it's been getting tiring making zips for everything I want to flash. This solved my problem and is reversible without record. You are the man and thanks for putting in the time.

isdnmatt said:
Hey Scotty,
I can't thank you enough for this info. I really didn't want to unlock via htcdev and it's been getting tiring making zips for everything I want to flash. This solved my problem and is reversible without record. You are the man and thanks for putting in the time.
Click to expand...
Click to collapse
glad to help

Can someone explain the benefits to me of being able to change between locked/unlocked? If not.... That's cool.
Sent from my HTC6500LVW using Tapatalk now Free

BaBnkr said:
Can someone explain the benefits to me of being able to change between locked/unlocked? If not.... That's cool.
Sent from my HTC6500LVW using Tapatalk now Free
Click to expand...
Click to collapse
For this thread and most people's needs, unlocking this way after s-off saves time. Re-locking just proved it was reversible in case someone did want to be locked again. Another way to get back to stock for warranty purposes, etc...
Most importantly, to prove it can be done!
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Fantastic, can this work for HTC One S too?
maybe needs finding correct blocks?
what it is unclear to me is that:
your method to unlock bootloader needs S-OFF, but S-OFF needs Unlocked bootloader and SuperCID, so maybe for HTC One S it's different
thanks for clarification

icest0rm said:
Fantastic, can this work for HTC One S too?
maybe needs finding correct blocks?
what it is unclear to me is that:
your method to unlock bootloader needs S-OFF, but S-OFF needs Unlocked bootloader and SuperCID, so maybe for HTC One S it's different
thanks for clarification
Click to expand...
Click to collapse
blocks are the same for one s.
method does indeed need s off. most common way to achieve s off for devices on the unlock program is via intial unlock thru htcdev to install root and recovery. at this point the commands are useful to get back to locked,and if one needs unlock after being locked for some reason. vzw is a bit different in that they cannot use htcdev,so a hack is needed to temproot,then s off. this does give them the luxury of being able to unlock without htcdev alltogether.
its also possible to s off via a java card,or be lucky enuff to find a user trial device that came that way. in this situation htcdev can be left out of the picture entirely.
hope that clarifes it

scotty1223 said:
blocks are the same for one s.
Click to expand...
Click to collapse
ok!
scotty1223 said:
method does indeed need s off. most common way to achieve s off for devices on the unlock program is via intial unlock thru htcdev to install root and recovery. at this point the commands are useful to get back to locked,and if one needs unlock after being locked for some reason.
Click to expand...
Click to collapse
ok...clear
scotty1223 said:
vzw is a bit different in that they cannot use htcdev,so a hack is needed to temproot,then s off. this does give them the luxury of being able to unlock without htcdev alltogether.
Click to expand...
Click to collapse
ehm...sorry...what is vzw?
its also possible to s off via a java card,or be lucky enuff to find a user trial device that came that way. in this situation htcdev can be left out of the picture entirely.
hope that clarifes it
Click to expand...
Click to collapse
thanks :good:

vzw=Verizon wireless
Sent from my HTC One VX using Tapatalk

scotty1223 said:
vzw=Verizon wireless
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
ah ok...
but since they need a temproot to get unlock without htcdev, wouldn't this be possible for all htc one (s)?
why is it limited to vzw?

icest0rm said:
ah ok...
but since they need a temproot to get unlock without htcdev, wouldn't this be possible for all htc one (s)?
why is it limited to vzw?
Click to expand...
Click to collapse
technically,yes. you could use a temp root and make a tool for any other carriers device so you would not have to unlock.
however, temp root exploits are typically patched quickly. htcdev is a reliable means of root to make other tools/exploits work. its much,much easier to simply unlock and install root and recovery than to keep looking for softwate temp root exploits.
with verizon you have no choice,since they do not allow official unlock.

Hello, can you please tell me why do i get this error ?