Database Users

[Q] Tried every guide I can find, can't get S-Off

I've tried every guide here on XDA...tried the Cyanogen Wiki...ever tried the Unlockr's guide...I can root the phone, but I can't get S-Off. This is my third Mytouch 4G, and the only one I've been unable to get S-Off on. the other ones I was able to use rage to root and get S-Off on, but this one I only seem to be able to root. I've even tried visionary and can still only get root but not S-Off. I'm just so frustrated at this point I feel like smashing the phone and telling T-Mobile the replacement came like this...

mytouch4g ya say?
hmm..
http://forum.xda-developers.com/showthread.php?t=858996
look for gfree.

Are you getting a "failed to powercycle eMMC" error?

synaesthetic said:
Are you getting a "failed to powercycle eMMC" error?
Click to expand...
Click to collapse
Yes...the guide at the CM wiki said if I get that to use gfree .05 instead, but then when I get this running this part again
Code:
./gfree -f -b hboot-eng.img -y recovery.img
./root_psn
sync
it says that the -y parameter isn't recognized

Just run ./gfree -f
Everything else can be done later.
http://forum.xda-developers.com/showthread.php?t=858996

Followed that page..this is what I get
Code:
# ./gfree -f
./gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.21-g899d047
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a63a4, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a6000
Kernel memory mapped to 0x40011000
Searching for brq filter...
- Address: 0xc02a63a4 + 0x34c
- 0x2a000012 -> 0xea000012
Patching and backing up partition 7...
Error opening copy file.
#

Mackster248 on YouTube... he's got a great tutorial video using the gfree method...
Sent from my HTC Glacier using XDA App

try a different usb port?
I had some issues rooting an entirely different device where it had difficulty copying files, it basically all boiled down to the usb port i was trying to use. Bypass any hubs, plug directly into rear of machine.
Shot in the dark, worth a try tho...

cbutt said:
Mackster248 on YouTube... he's got a great tutorial video using the gfree method...
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yea..ok..I dunno what the hell it was, but I followed that guide word for word last night and it didn't work. Went fine just now...thanks

Try this
http://forum.xda-developers.com/showthread.php?t=995549
Sent from my HTC Glacier using XDA App

[Q] Unlock bootloader Flashtool

Hi,
i've just tried to unlock blootloader with flashtool,it returned me:
PHP:
Searching Xperia....
12/030/2011 10:30:00 - INFO - Found at USB\VID_0FCE&PID_ADDE\6&A050C15&0&1
12/030/2011 10:30:00 - INFO - VER="R8A013";DATE="20100119";TIME="17:24:00";
12/030/2011 10:30:00 - INFO - Start Reading property
12/030/2011 10:30:00 - INFO - Reading property finished.
12/030/2011 10:30:00 - INFO - You can now unplug and turn on device, then plug it again
12/030/2011 10:30:00 - INFO - Waiting for device
12/036/2011 10:36:04 - INFO - Connected device : X10
12/036/2011 10:36:04 - INFO - Installed version of busybox : BusyBox v1.18.4 (2011-04-04 18:40:20 CDT) multi-call binary.
12/036/2011 10:36:04 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
12/036/2011 10:36:05 - INFO - Root Access Allowed
12/036/2011 10:36:06 - INFO - Pushing .\devices\X10\features\X10UnlockBL\fixPart to /data/local/tmp
12/036/2011 10:36:06 - INFO - Running runfixPart as root thru sysrun
12/036/2011 10:36:06 - INFO - Successfully applied fixPart. Rebooting
12/036/2011 10:36:07 - INFO - Waiting for device
12/036/2011 10:36:41 - INFO - Pushing .\devices\X10\features\X10UnlockBL\mapper_2.6.29.ko to /data/local/tmp
12/036/2011 10:36:41 - INFO - Pushing .\devices\X10\features\X10UnlockBL\qsd8250bootwrite_semcSL to /data/local/tmp
12/036/2011 10:36:42 - INFO - Running runqsd8250bootwrite as root thru sysrun
12/036/2011 10:36:43 - INFO - Successfully applied unlock. Rebooting
Altough i see successfully applied unlock, is there a way to be sure it has done it correctly before applying doom's kernel or i can just expect flashtool log says the right?
Thanks

franceX said:
Hi,
i've just tried to unlock blootloader with flashtool,it returned me:
PHP:
Searching Xperia....
12/030/2011 10:30:00 - INFO - Found at USB\VID_0FCE&PID_ADDE\6&A050C15&0&1
12/030/2011 10:30:00 - INFO - VER="R8A013";DATE="20100119";TIME="17:24:00";
12/030/2011 10:30:00 - INFO - Start Reading property
12/030/2011 10:30:00 - INFO - Reading property finished.
12/030/2011 10:30:00 - INFO - You can now unplug and turn on device, then plug it again
12/030/2011 10:30:00 - INFO - Waiting for device
12/036/2011 10:36:04 - INFO - Connected device : X10
12/036/2011 10:36:04 - INFO - Installed version of busybox : BusyBox v1.18.4 (2011-04-04 18:40:20 CDT) multi-call binary.
12/036/2011 10:36:04 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
12/036/2011 10:36:05 - INFO - Root Access Allowed
12/036/2011 10:36:06 - INFO - Pushing .\devices\X10\features\X10UnlockBL\fixPart to /data/local/tmp
12/036/2011 10:36:06 - INFO - Running runfixPart as root thru sysrun
12/036/2011 10:36:06 - INFO - Successfully applied fixPart. Rebooting
12/036/2011 10:36:07 - INFO - Waiting for device
12/036/2011 10:36:41 - INFO - Pushing .\devices\X10\features\X10UnlockBL\mapper_2.6.29.ko to /data/local/tmp
12/036/2011 10:36:41 - INFO - Pushing .\devices\X10\features\X10UnlockBL\qsd8250bootwrite_semcSL to /data/local/tmp
12/036/2011 10:36:42 - INFO - Running runqsd8250bootwrite as root thru sysrun
12/036/2011 10:36:43 - INFO - Successfully applied unlock. Rebooting
Altough i see successfully applied unlock, is there a way to be sure it has done it correctly before applying doom's kernel or i can just expect flashtool log says the right?
Thanks
Click to expand...
Click to collapse
Just flash doomkernal and reboot,
If you see a white sony ericsson logo it has not worked...
dont forget the correct wifi modules for the kernal you flash

gregbradley said:
Just flash doomkernal and reboot,
If you see a white sony ericsson logo it has not worked...
dont forget the correct wifi modules for the kernal you flash
Click to expand...
Click to collapse
can i ask i already unlock botloader already, how i flash wolffbreak room??? i flashed the doomkernel kernel, it stuck at doom kernel logo cannot enter into xrecovery??thn how should i flash it?

[Q] Please help I can not restore S-On!

Hi All,
I have been following the guide: http://forum.xda-developers.com/wiki/HTC_Vision#Restoring_the_backup_of_partition_7
To restore S-On on a Desire Z. I have tried both restoring the original image and using the S-On command as follows:
# ./gfree -s on
./gfree -s on
--secu_flag on set
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.21-g6e170e7
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02adc1c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02ad000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc02adc1c + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
Backing up partition /dev/block/mmcblk0p7 to /sdcard/part7backup-315968429.bin .
..
patching secu_flag: 1
Done.
# sync
sync
# reboot
reboot
Despite this the status is still S-OFF
Please can someone help!

What is your rom version/build number?
what is your baseband version?
-Nipqer

Nipqer said:
What is your rom version/build number?
what is your baseband version?
-Nipqer
Click to expand...
Click to collapse
It was on cyanogenmod but it was giving me errors trying to restore it, so I flashed an official RUU:
ROM/ Build Number:1.82.405.1 CL317545 release-keys
Baseband: 12.28e.60.140fU_26.04.02.17_M2
Thanks

You need to run misc_version and downgrade to a 1.32 firmware, with radio 26.03.xx.xx to change back to S-ON
-Nipqer

AAHK Fail - Main Version is Older

Hi all,
Android 2.3.5
HTC Sense 3.0
Software 3.12.405.1
Attempting to root HTC Desire HD using AAHK. I have followed detailed instructions for rooting HTC Desire HD using AAHK. I have followed all instructions regarding, firewall, anti-virus, correct driver versions, validated all downloads with checksums.
As version is 2.3.5, AAHK attempts to downgrade to earlier version. Log from CMD
**********************************************************************************************
3.12.405.1
This version of Android cannot use the hack kit at this time.
You can downgrade if you like, then rerun the hack step.
WARNING: THIS WILL WIPE DATA
[Would you like to downgrade? y/n]y
Download this RUU? [y,n]y
--2012-08-11 15:14:47-- tau shadowchild nl /files/PD98IMG-GB2.zip
Resolving tau.shadowchild.nl... 176.9.40.154
Connecting to tau.shadowchild.nl|176.9.40.154|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 259503624 (247M) [application/zip]
Saving to: `PD98IMG/PD98IMG-GB2.zip'
100%[======================================>] 259,503,624 1.56M/s in 2m 41s
2012-08-11 15:17:28 (1.54 MB/s) - `PD98IMG/PD98IMG-GB2.zip' saved [259503624/259
503624]
a67daa6baa7ef085307593fef6329d14 *PD98IMG/PD98IMG-GB2.zip
Flash the downgrade RUU? [y,n]y
pushing rom to sdcard - this takes time please be patient.
1529 KB/s (259503624 bytes in 165.742s)
Setting up to temproot....
1150 KB/s (21215 bytes in 0.018s)
1630 KB/s (572752 bytes in 0.343s)
1342 KB/s (19240 bytes in 0.014s)
going for temproot using zergRush....
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x401219c4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd26019 0xafd39ef7
[*] Poping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
setting mainver lower for downgrade...
error: device not found
Creating goldcard....
HTC android goldcard tool Copyright (C) 2011, Wayne D. Hoxsie Jr.
Original code by B. Kerler. Special thanks to ATTN1 and the XDA team.
Donations can be made to the Electronic Frontier Foundation:
or to B. Kerler:
0+1 records in
0+1 records out
384 bytes transferred in 0.002 secs (192000 bytes/sec)
starting downgrade...
** The phone will now reboot into HBOOT.
** It will then check the file just sent.
** If everything is okay, the phone will
** prompt you to continue by pressing
** VOLUME UP. It will reboot, flashing twice.
**** PUSH POWER WHEN THIS STEP COMPLETES ****
****************************************************************************
Error then displayed on phone: which I assume is related to the preceding "set mainver" error.
**************************************************************************
*** LOCKED (OOW) ***
ACE PUT SHIP S-ON rd
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011,14:28:19
HBOOT
Main Version is older!
Update Fail!
Press <POWER> to reboot.
***********************************************************
6 hours in, have read many related threads without success, don't know what I did wrong. All suggestions greatly appreciated.

Have you tried re-running the hack kit?

factory wipe phone with both from phone software and also AAHK

alas yes, multiple times, same result
Main Version is older!
experience tells me that this will be my fault.

Jimpy0 said:
factory wipe phone with both from phone software and also AAHK
Click to expand...
Click to collapse
factory wipe?, can you elaborate? details or link much appreciated.
seems to me most things worked, which minor part of the process caused the failure of setting mainver to fail?

nathancoast said:
factory wipe?, can you elaborate? details or link much appreciated.
seems to me most things worked, which minor part of the process caused the failure of setting mainver to fail?
Click to expand...
Click to collapse
Hit the IRC channel in my signature...that is what u have to do when u get stucked. What I see there is that the connection with the phone is lost. Uninstall the driver and re install them from the tools>windrivers folder from the Kit WITH THE PHONE UNPLUGGED. Then, plug the phone and let the driver install...
If you are still stuck after that come to the IRC channel...:good:

AAHK trouble on DHD
DELETED

Help root ZTE Blade A512

I need help, I wanted to do my ZTE to 512 and I can not do it at all. Of all the programs that support the device I get the following:
--- = SRS One-Click-Root v5.1 =
16:30:09 - Starting ADB Server ..
16:30:16 - Manufacturer: ZTE
16:30:16 - Model: ZTE BLADE A512
16:30:17 - Android Version: 6.0.1
16:30:17 - Build ID: VDF-A512B01-PT_MR03b
16:30:17 - Board ID: MSM8917
16:30:17 - Chipset Platform: msm8937
16:30:17 - Getting OffSets ..: error: only position independent executables (PIE) are supported. (False)
16:30:18 - Query Server for Best Method .. Found Rootkit: 8
---- = Start Rooting Process .. Please Wait = ----
16:30:19 [+] Testing exploit: root8 (please wait ..)
16:30:21 [+] Remounting / system Filesystem as R / W ..
16:30:21 [+] Installing SU Binary ...
16:30:22 [+] Installing SuperUser APK ...
16:30:23 [+] Remounting / system Filesystem as R / O ..
16:30:28 [+] Rooting Complete!
It gives indication that it gets root but it does not stay.
Another program that supposedly works is this one spoken in this video:
Https://www.youtube.com/watch?v=w_U_pjwE_3Q
Program: http://kidapso.com/autorootdl I can not test because I can not download even responding to the proposed surveys.
If you know of any solutions, share. Thank you
Build ID: VDF-A512B01-PT_MR03b