Develop Bugs

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).

[Q] Downgrade Problems

Hi guys. I have a brand new Desire HD, T-mobile (uk) branded.
Running Android 2.2.1
Build number 1.84.110.3 CL334589 Release-Keys
I am trying to downgrade to 1.32 so that i can root. I have made a goldcard, using various methods (HxD, goldcard helper, and goldcard tool)...Following the guides, everything seems to go to plan, no error messages or anything.
I then go through the process of....
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
cd /data/local/tmp
./misc_version -s 1.31.405.6
Again no problems there.....When phone is rebooted into bootloader, it loads the PD98IMG.zip file, and after checking it, I always get the error "update failed, incorrect cid" I don't know where I'm going wrong, the goldcard tools are reversing the CIDs for me.....Any tips ?
Thanks

mrmcox said:
Hi guys. I have a brand new Desire HD, T-mobile (uk) branded.
Running Android 2.2.1
Build number 1.84.110.3 CL334589 Release-Keys
I am trying to downgrade to 1.32 so that i can root. I have made a goldcard, using various methods (HxD, goldcard helper, and goldcard tool)...Following the guides, everything seems to go to plan, no error messages or anything.
I then go through the process of....
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
cd /data/local/tmp
./misc_version -s 1.31.405.6
Again no problems there.....When phone is rebooted into bootloader, it loads the PD98IMG.zip file, and after checking it, I always get the error "update failed, incorrect cid" I don't know where I'm going wrong, the goldcard tools are reversing the CIDs for me.....Any tips ?
Thanks
Click to expand...
Click to collapse
it can be by several thinks...
i would try to format the sd-card and re-do the goldcard again (goldcard tool works well) be sure about you have the correct CID in the sd card

SERGI.3210 said:
it can be by several thinks...
i would try to format the sd-card and re-do the goldcard again (goldcard tool works well) be sure about you have the correct CID in the sd card
Click to expand...
Click to collapse
I have tried the goldcard tool a few times now, with various micro SD cards (8GB samsung that was bundled with phone. 2gb sandisk. and 2gb kingston)
when I run it, selecting "mmc0" I get CID value as....
45010053454D3034479022CD0AA93E10
and it reverses it to...
003EA90ACD22904734304D4553000145 ...
Is that correct ? Then i fill in the details on PSAS and get my image emailed and load/patch the card with goldcard tool. If I try and get cid using "mmc1" I get messgae...
* daemon started successfully *
/sys/class/mmc_host/mmc1/mmc1:*/cid: No such file or directory
------------------------
Could not locate CID in output
And with gold card created, I o through the motions again, and keep getting Update failed, incorrect CID.

u can obtain temporary root???
i checked the commands of the first post and are ok...
really all the issues like this was solved formatting the sd again.. FAT for -2gb and fat 32 for 8gb sd card...
your troubble is weird...

mrmcox said:
when I run it, selecting "mmc0" I get CID value as....
Click to expand...
Click to collapse
Hmm, it might be useful to read the Downgrade guide again, mate Especially the bolded part after goldcard link..

jkoljo said:
Hmm, it might be useful to read the Downgrade guide again, mate Especially the bolded part after goldcard link..
Click to expand...
Click to collapse
Thanks for the reply. I tried to make the gold card again, using mmc2 with the gold card helper tool on the handset.
I get the reversed CID as
00b2003be96a721030303030304d531b Tired making gold card with HxD and with the gold card tool, but each time when I boot into bootloader on the phone, it loads the PD98IMG file and after checking it I get
CID incorrect!
Update fail
Press <power> to reboot
Any idea where I can be going wrong ?

Are you selecting physical disk and making sure write access is ticked in the hex editor?
Sent from my Motorola Startac running Atari 2600 software!

hey, need some help here.. i'm on stock froyo. the software version is 1.84.707.2. i downloaded the 2.36 and 1.32 version . but couldn't seem to flash both RUU at all. its an exe file. my phone entered into BOOTloader and while sending signature, the screen on pc says CID error 131. ask me to get the correct utility. my desire hd is unbranded and unrooted. its still new.. it is still S-ON. I had never rooted it or done anything to it . just wanted to make sure i have a functional RUU in backup in case i want to send for warranty.what should i do? i'm from malaysia btw

Any problems regarding CID Error mean you need a goldcard. If you've made one and you still get this error, your card isn't gold. Try using a different card.

thanks guys for all the help and replies.
I finally got my goldcard to work, ended up buying a new card and using that, and it worked first time.
I now have downgraded to 1.32, have perm root, radio s-off, and eng s-off. I've just upgraded radio to latest version, and I'm about to upgrade to android revolution HD 5.1.7.
Thanks again for all the help

andyharney said:
Any problems regarding CID Error mean you need a goldcard. If you've made one and you still get this error, your card isn't gold. Try using a different card.
Click to expand...
Click to collapse
Thanks. Even if my phone is unbranded and new, I still need a goldcard??
Sent from my HTC Desire using XDA App

dunstan92 said:
Thanks. Even if my phone is unbranded and new, I still need a goldcard??
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
if your phone is unbranded you don't need a gold card

I will repeat what I said just incase there is any confusion.
Any CID related errors while trying to downgrade mean you need a goldcard. No if's no but's, a goldcard will be required. Remember there are unbranded builds that will not have the WWE CID.
One example is builds found in the East. WWE = x.xx.405.x Indian = x.xx.720.x
They are both unbranded, however a goldcard is required to flash from 720 to 405. I hope I've cleared things up.

andyharney said:
I will repeat what I said just incase there is any confusion.
Any CID related errors while trying to downgrade mean you need a goldcard. No if's no but's, a goldcard will be required. Remember there are unbranded builds that will not have the WWE CID.
One example is builds found in the East. WWE = x.xx.405.x Indian = x.xx.720.x
They are both unbranded, however a goldcard is required to flash from 720 to 405. I hope I've cleared things up.
Click to expand...
Click to collapse
Thank you
Sent from my HTC Desire using XDA App

Yes, you have cleared things up. Thank you very much. So if I create a goldcard and flash the ruu 1.32.405.x ,will it cause any problem if I send it for warranty service? Because I can't find the ruu with 1.84.707.2 for my phone. Is there any ruu for Malaysia or Asia yet?
Sent from my HTC Desire using XDA App
Sent from my HTC Desire using XDA App

I'm pretty sure the 405 version WWE (World Wide English) will be Ok to return as it is an official HTC build.

Alright. Thanks. So do I still need to downgrade my stock rom even with a goldcard? Am planning to flash the 2.36.405.x ruu over my current rom.
Sent from my HTC Desire using XDA App

i need some help here, im getting to section B step 23 of the guide to rooting and flashing and then something not so good is happening with my phone.
In getting "process stopped unexpectedly" messages from (android.process.acore)
they are constantly popping up.

i've previously had the problem of incorrect CID as well, but it solve after i format the MMC to FAT 32 and redo the goldcard steps

[Q] How to unlock Desire HD 4G?

Well, as the title says, how do I unlock the Desire HD 4G, now that the aahk tool is not being used? I've searched and searched but I don't find anything.
Thanks in advance.

ghosts3v3n said:
Well, as the title says, how do I unlock the Desire HD 4G, now that the aahk tool is not being used? I've searched and searched but I don't find anything.
Thanks in advance.
Click to expand...
Click to collapse
Did you search the Development forums? Easy Ace Root Tool.

bananagranola said:
Did you search the Development forums? Easy Ace Root Tool.
Click to expand...
Click to collapse
I've read about it, but I see it only works for root. I've already rooted my phone and booted up a custom rom, I just don't find a way to unlock it and make it work with Simple Mobile.

ghosts3v3n said:
I've read about it, but I see it only works for root. I've already rooted my phone and booted up a custom rom, I just don't find a way to unlock it and make it work with Simple Mobile.
Click to expand...
Click to collapse
So you're asking about SIM unlock, not bootloader unlock? AAHK's old website has a high-level manual guide for how to do everything AAHK used to do.

bananagranola said:
So you're asking about SIM unlock, not bootloader unlock? AAHK's old website has a high-level manual guide for how to do everything AAHK used to do.
Click to expand...
Click to collapse
Well, I can't say i'm a pro at Android, but I ain't bad either. I took a read at that. I believe that manual is to SIM Unlock? Again, I read it but tbh, not everything is explained easily. It would help if someone would explain what is going on. (not what do I have to do.)

ghosts3v3n said:
Well, I can't say i'm a pro at Android, but I ain't bad either. I took a read at that. I believe that manual is to SIM Unlock? Again, I read it but tbh, not everything is explained easily. It would help if someone would explain what is going on. (not what do I have to do.)
Click to expand...
Click to collapse
The manual is, top to bottom, what AAHK used to do. That includes SIM unlock. That also includes S-Off, recovery, and root. He gives a high-level explanation of each step. What kind of explanation are you looking for?

bananagranola said:
The manual is, top to bottom, what AAHK used to do. That includes SIM unlock. That also includes S-Off, recovery, and root. He gives a high-level explanation of each step. What kind of explanation are you looking for?
Click to expand...
Click to collapse
Well, first of all, I assume these are the steps to Sim Unlock my phone?
High Level Steps (some detail deliberately NOT included)
htc dev unlock, install cwm recovery and root ONLY
dd the stock boot image to /data/local/tmp and pull it to your pc HD (/dev/block/mmcblk0p22 is boot)
adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img
make a goldcard (for all CIDS not in android-info.txt in the firmware.zip to be flashed)
adb push goldcard /data/local/tmp
adb shell chmod 775 /data/local/tmp/goldcard
adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid (returns sdcard cid)
adb shell /data/local/tmp/goldcard -c <sd card cid above> -o /data/local /tmp/goldcard.img
adb shell dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1 (this writes the goldcard.img to the sdcard. Mileage on used sdcards may vary)
push misc_version to the phone and use to lower the mainversion (need to lower the mainversion in order to flash the firmware downgrade)
adb push misc_version /data/local/tmp
adb shell chmod 775 /data/local/tmp/misc_version
adb shell /data/local/tmp/misc_version -s 1.11.111.1
relock the bootloader
flash firmware.zip with from the zip below (this firmware contains the original radio exploit used by gfree)
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot-bootloader
unlock the bootloader again (use the same unlocktoken bin)
flash your stock boot.img to boot (this will get the current rom working again)
fastboot flash boot boot.img
flash recovery.img to recovery (from the zip below – this recovery has a kernel that works with the radio exploit)
fastboot flash recovery recovery.img
boot to recovery (yes, the screen may well be blank, but adb should work fine)
adb push gfree /tmp/
adb shell chmod 775 /tmp/gfree
adb shell /tmp/gfree -f >> yeilds – s-off, supercid, sim-unlock
reboot to bootloader and check success.
Click to expand...
Click to collapse

No, like I said, those are all the steps to do what AAHK used to do. That includes SIM unlock, as well as all those other things I mentioned previously.

bananagranola said:
No, like I said, those are all the steps to do what AAHK used to do. That includes SIM unlock, as well as all those other things I mentioned previously.
Click to expand...
Click to collapse
Well okay, so, which of those are the steps to SIM Unlock the phone?

ghosts3v3n said:
Well okay, so, which of those are the steps to SIM Unlock the phone?
Click to expand...
Click to collapse
Wait okay, I think I'm not being clear. I'm pretty sure that those instructions get your phone in a state where it can run the gfree exploit. It does this by unlocking, making a goldcard, and flashing an exploitable firmware. The gfree exploit does S-Off, SIM unlock, and superCID. I don't know what state your phone is in now, so you need to look at that to figure put what your next steps are.

hmm, gfree exploit? I haven't read about that. Care to send a link?
Sent from my HTC Desire HD using Tapatalk 4 Beta

ghosts3v3n said:
hmm, gfree exploit? I haven't read about that. Care to send a link?
Click to expand...
Click to collapse
It's included in the instructions you quoted above.

oh, I think I get it. Ignoring the first steps (I already have CWM, and root), I should follow everything else and I should end up with S-OFF, Supercid (what's this?), and sim unlock?
Sent from my HTC Desire HD using Tapatalk 4 Beta

ghosts3v3n said:
oh, I think I get it. Ignoring the first steps (I already have CWM, and root), I should follow everything else and I should end up with S-OFF, Supercid (what's this?), and sim unlock?
Sent from my HTC Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
SuperCID: All RUUs will be compatible with your phone, every region. This is because the cid is what determines what country and carrier you phone is from, it also helps unbranding.
Sent from my Desire HD using Tapatalk 4

[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 ?