Develop Bugs

[Q] Problems getting S-Off

Well ive tried to permroot using rage, VISIONary, and gfree but there seems to be a problem everytime i try to push something with adb it gives me a permission denied message or a message like cant insmod /data/local
Can anyone help? I have tho ota update with baseband 12.28b.60.140eU_26.03.02.26_M Kernel 2.6.32.17-g9ab3677 Build Number 1.22.531.8 CL277427

Alex530 said:
Well ive tried to permroot using rage, VISIONary, and gfree but there seems to be a problem everytime i try to push something with adb it gives me a permission denied message or a message like cant insmod /data/local
Can anyone help? I have tho ota update with baseband 12.28b.60.140eU_26.03.02.26_M Kernel 2.6.32.17-g9ab3677 Build Number 1.22.531.8 CL277427
Click to expand...
Click to collapse
Try here post #2
http://forum.xda-developers.com/showthread.php?t=895760

Alex530 said:
Well ive tried to permroot using rage, VISIONary, and gfree but there seems to be a problem everytime i try to push something with adb it gives me a permission denied message or a message like cant insmod /data/local
Can anyone help? I have tho ota update with baseband 12.28b.60.140eU_26.03.02.26_M Kernel 2.6.32.17-g9ab3677 Build Number 1.22.531.8 CL277427
Click to expand...
Click to collapse
Where are you typing the adb commands ? A common mistake is to run "adb shell" and then run the "adb push" etc at the $ prompt, which is actually a command prompt on your phone, so it won't work and will give you "permission denied".
What error message are you getting from the "insmod" command exactly ?

steviewevie said:
Where are you typing the adb commands ? A common mistake is to run "adb shell" and then run the "adb push" etc at the $ prompt, which is actually a command prompt on your phone, so it won't work and will give you "permission denied".
What error message are you getting from the "insmod" command exactly ?
Click to expand...
Click to collapse
Well I rooted using blackprinces method. But with gfree id get #insmod can't locate /data/ local or /data/sdcard/ something like that
Sent from my HTC Vision using XDA App

Alex530 said:
Well I rooted using blackprinces method. But with gfree id get #insmod can't locate /data/ local or /data/sdcard/ something like that
Click to expand...
Click to collapse
You don't need to run insmod if you're using gfree, because gfree has got that functionality inside it already.
See http://forum.xda-developers.com/wik...Phone.2C_Set_SuperCID.2C_and_Turn_Radio_S-OFF and follow the procedure there.

steviewevie said:
You don't need to run insmod if you're using gfree, because gfree has got that functionality inside it already.
See http://forum.xda-developers.com/wik...Phone.2C_Set_SuperCID.2C_and_Turn_Radio_S-OFF and follow the procedure there.
Click to expand...
Click to collapse
Wait so can I do this without unrooting and such. And what's the advantage of Radio-off?
Sent from my HTC Vision using XDA App

Alex530 said:
Wait so can I do this without unrooting and such. And what's the advantage of Radio-off?
Click to expand...
Click to collapse
Yes, if you're already rooted you can just use gfree via that link that I posted, which assumes you are already rooted. No need to undo what you've done already.
See http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Background for an excellent explanation as to why "radio S-OFF" is much better, and safer, than the "fake" S-OFF through the eng hboot.

i seem to be having problems too but i have permissions and get SU
i seem to be having issues with gfree not giving s-off. have eng hboot installed and perm rooted.
Code:
# chmod 777 ./gfree
chmod 777 ./gfree
# ./gfree -s off
./gfree -s off
--secu_flag off 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-gd2764ed
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a6a54, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a6000
Kernel memory mapped to 0x40011000
Searching for brq filter...
- Address: 0xc02a6a54 + 0x34c
- ***WARNING***: Found fuzzy match for brq filter, but conditional branch isn't. (0xea000012)
Patching and backing up partition 7...
patching secu_flag: 0
Done.
# sync
sync
# start ril-daemon
start ril-daemon
gfree_verify and the at commands both state that secu_flag is still 1
any help appreciated

Lalalandrus, what ROM version are you running exactly ?
Sent from my HTC Desire Z

I was having problems with it running and not doing anything, but then i flashed cm 6.1 and all was good.
Sent from my HTC Vision using XDA App

previously rooted with hacked HBOOT
steviewevie said:
Lalalandrus, what ROM version are you running exactly ?
Sent from my HTC Desire Z
Click to expand...
Click to collapse
Bell Desire Z ROM version 1.34.666.5
baseband version 26.03.02.26_M

[Q] How to test if your phone has Root using Terminal and other Rooting question

Ok. I want to know how can you test that your phone is rooted. When I'm doing the XDA method of rooting my G2, I push all the needed files to my phone, and do the thing where Terminal Force closes and you open again after you had ran rage. Now I have the root shell in Terminal.
When I run command:
$ su
not found
($) is my command line, and (blanks) is what came back. ^^
Is it suppose to say "not found"? or is it suppose to say something else? I did exactly what I was suppose to do. It wasn't all that hard. Before I did the rage command, it was
$ su
Permission Denied
That seems normal. But after I supposedly temporarily root my phone, if I open ROM manager, it tells me that I need to root my phone. What tha truck? Am I missing something?
I run:
$ /data/local/gfree -f
{export PATH=/data/local/bin:$PATH
# # /data/local/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: 0x00015398 (86936)
Section index for section name string table: 41
String table offset: 0x000151df (86495)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x000011cc (4556)
-- size: 0x000000c4 (196)
Kernel release: 2.6.32.17-g9ab3677
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c029c72c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc029c000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc029c72c + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
patching secu_flag: 0
Done.}
I run command:
$sync
# {sync}
I run command:
$ /data/local/tmp/root
# {/data/local/tmp/root
mkdir failed for /system/xbin, File exists
cp: can't stat '/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
#}
(mkdir failed for /system/xbin, File exists) This is where I think I'm messing up. The directions say it should state:
( mkdir: /system/xbin already exists)
See the difference? The directions doesn't say "Failed" while mines does.
In Hboot mode:
VISION PVT SHIP S-OFF
HBOOT-0.82.000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
HBOOT
(How to navigate)
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
So what's going on? Is my phone rooted or not? Why when I go to recovery, there's this triangle thing there? LoL!! It's the picture of the phone with a red triangle.
Thanks for any help. And sorry. I completely changed the question.

I think for some reason you are missing the su binary do you have the superuser
app installed? when you type su, superuser should ask you if you want to allow terminal to access root and after accepting it $ will change to # which means you can run a command as root .
and for the red triangle, it is the stock recovery if you want to install clockworkmod ,you can flash it true Rom manager

bahmanxda said:
I think for some reason you are missing the su binary do you have the superuser
app installed? when you type su, superuser should ask you if you want to allow terminal to access root and after accepting it $ will change to # which means you can run a command as root .
and for the red triangle, it is the stock recovery if you want to install clockworkmod ,you can flash it true Rom manager
Click to expand...
Click to collapse
I have the SuperUser app installed on my phone. But once I get the root shell (#) symbol in Terminal Emulator, if i type (su) I get the response " not found ". I don't know what it's saying. It sounds like you're right when you say the file (su) isn't moving to my phone.
Dugh!!

When you're in terminal and you get the root # symbol there's nothing more to do. Just open terminal, type 'su' and hit enter. The $ should change to a # and that means you are root. If you get anything but that then like the other guy said, your su binaries are probably messed up.
In that case you the search function on here and look for something like 'reinstall su binaries'. That should set you straight. Btw, make sure to use the binaries from the gfree method, their the most current as far as I know.
Sent from my HTC Vision using XDA App

Ok. Now I really don't know what's going on. When I reboot while holding Power, and Vol+Down, I can see that I have S-Off, but when I open ROM Manager or any other root app, it tells me I need to Root my phone. Am I missing something?
And yes, I did check the forums about when people had this same problem. They aren't helping. Somehow, people are getting their root after they find something out, but I don't know what's going on.
It seems that my phone isn't TempRooting.
I did notice that when I go to Super User app, it tells me that there is an update to the SU Binary, and it fails to update, so there is a zip file on my SD Card, and that I should start the phone in recovery mode and flash it.
Right now, it says Superuser v2.3.6.1 Is that the most current, or no?
The zip file name is su-2.3.1-bin-signed.zip
Thanks for any help. I don't know how I got S-Off, a Root Shell, and still don't have Temp Root to go to PermaRoot.

What instructions did you use to root? Sounds like you might have skipped a step. Also how did you temporarily root?

What do you have in /system/xbin ?
HTC Vision 1.8 OC, CM7 RC1==HAPPY!!

G2 rooting help, how to chmod?

I ran all the required commands and noticed that the chmod did not do anything. So I decided to run the temp root command abd I get permission denied.
Sent from my T-Mobile G2 using XDA App

Please anyone? I run this command "adb shell chmod 755 /data/local/tmp/*" but it does not do anything, is there something I have to change on that line?
Been trying to root for 2 days now but unsuccessful.

you're not supposed to see any return on the command prompt. Just continue with the procedure.

Thanks for giving me a reply, waited many hours. THANK you though.
When I run the temp root command, I get this.
"C:\android-sdk-windows\platform-tools>adb shell /data/local/tmp/psneuter
mmap() failed. Operation not permitted
C:\android-sdk-windows\platform-tools>adb shell
"

C:\android-sdk-windows\platform-tools>adb shell
#
#
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox md5sum /dev/block/mmcblk0p18
./busybox md5sum /dev/block/mmcblk0p18
b532ca54a073f0c4043bd7be69ebce8d /dev/block/mmcblk0p18
# cd /data/local/tmp
cd /data/local/tmp
# ./gfree -f -b hboot-eng.img
./gfree -f -b hboot-eng.img
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
--hboot set. hboot image hboot-eng.img will be installed in partition 18
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x00015384 (86916)
Section index for section name string table: 41
String table offset: 0x000151cb (86475)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x000011cc (4556)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.17-g9ab3677
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c029c72c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc029c000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc029c72c + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 18 and installing specified hboot image...
Backing up current partition 7 and patching it...
patching secu_flag: 0
Done.
# ./flash_image recovery recovery.img
./flash_image recovery recovery.img
# cd /data/local/tmp
cd /data/local/tmp
# ./flash_image recovery recovery.img
./flash_image recovery recovery.img
# ./root_psn
./root_psn
# sync
sync
#
Did these commands run right?
# cd /data/local/tmp
# ./gfree -f -b hboot-eng.img
# ./flash_image recovery recovery.img
# ./root_psn
# sync

All looks good to me.... When yoh restart the phone do you have s off?
Sent from my HTC Vision using XDA App

have i bricked my desire Z?

hello guys
please i need your help i think i have screwed up my htc, i downgraded my desire z 2.33 to 2.2 and was trying to run the permanent root by strawmental, after running the sequence the phone could not boot again, it stuck at the white background with htc logo.
How can i boot it back to life.
i tryed fix it with recovery boot, but the clockworkmod v5.02.7 is not working, its log shows
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
vision pvt ENG S is off
h.boot now is 0.76.2000 (PC1011000)
MICROP 0425
CID 11111111
OS 1.34.405.5
below is the cmd log
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Patrolscsn>cd C:\platform-tools
C:\platform-tools>adb devices
List of devices attached
SH0B1RT02382 device
C:\platform-tools>adb push psneuter /data/local/tmp/
1453 KB/s (557962 bytes in 0.375s)
C:\platform-tools>adb push gfree /data/local/tmp/
1357 KB/s (716548 bytes in 0.515s)
C:\platform-tools>adb push busybox /data/local/tmp/
1468 KB/s (1926944 bytes in 1.281s)
C:\platform-tools>adb push hboot-eng.img /data/local/tmp/
1456 KB/s (1048576 bytes in 0.703s)
C:\platform-tools>adb push root_psn /data/local/tmp/
0 KB/s (564 bytes in 1.000s)
C:\platform-tools>adb push su /sdcard/
109 KB/s (26264 bytes in 0.234s)
C:\platform-tools>adb push Superuser.apk /sdcard/
1535 KB/s (196521 bytes in 0.125s)
C:\platform-tools>adb shell chmod 755 /data/local/tmp/*
C:\platform-tools>adb push recovery-clockwork-5.0.2.7-vision.img /data/local/tmp
/recovery.img
1479 KB/s (3739648 bytes in 2.468s)
C:\platform-tools>adb shell /data/local/tmp/psneuter
property service neutered.
killing adbd. (should restart in a second or two)
C:\platform-tools>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox md5sum /dev/block/mmcb1k0p18
./busybox md5sum /dev/block/mmcb1k0p18
md5sum: can't open '/dev/block/mmcb1k0p18': No such file or directory
# ./gfree -f -b hboot-eng.img -y recovery.img
./gfree -f -b hboot-eng.img -y recovery.img
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
--hboot set. hboot image hboot-eng.img will be installed in partition 18
--recovery set. recovery image recovery.img will be installed in partition 21
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-gd2764ed
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a6a54, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a6000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc02a6a54 + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 18 and installing specified hboot image...
Backing up partition /dev/block/mmcblk0p18 to /sdcard/part18backup-315983571.bin
...
Writing image hboot-eng.img to partition /dev/block/mmcblk0p18 ...
Backing up current partition 21 and installing specified recovery image...
Backing up partition /dev/block/mmcblk0p21 to /sdcard/part21backup-315983571.bin
...
Writing image recovery.img to partition /dev/block/mmcblk0p21 ...
Backing up current partition 7 and patching it...
Backing up partition /dev/block/mmcblk0p7 to /sdcard/part7backup-315983571.bin .
..
patching secu_flag: 0
Done.
# ./root_psn
./root_psn
# sync
sync
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox md5sum hboot-eng.img
./busybox md5sum hboot-eng.img
7669ae12dc2faa10ae555a164980efd0 hboot-eng.img
# ./busybox md5sum /dev/block/mmcb1k0p18
./busybox md5sum /dev/block/mmcb1k0p18
md5sum: can't open '/dev/block/mmcb1k0p18': No such file or directory
#

0.76.2000 > G2
0.84.2000 > DZ
if you have a DZ you have flashed the g2 hboot which is why it wont boot

like pnut said you may be just fine and still just need to flash a rom
can you do anything in recovery from here?
just because that message showed doesnt mean recovery wont work
but if flashing a rom via recovery dosent work try this
download this : http://www.4ext.net/ddl/vision/recovery.zip
this is a version of 4ext recovery to be flashed through fastboot
unzip it and put the image in the same folder as fastboot.exe on your computer
(if you are unfamiliar with fastboot just think of it as adb)
now open a cmd in that directory (easiest way hold shift and right click in that folder)
make sure you have phone plugged in pc and in fastboot mode
now type this into cmd
Code:
fastboot devices
if you see some leters and numbers good, this is your serial number
now type
Code:
fastboot -w
now
Code:
fastboot flash recovery recovery.img
now
Code:
fastboot reboot-bootloader
from here boot into recovery and you should see 4ext recovery now (better than clockwork)
try and flash a rom from recovery now, something known stable like cm7
reboot and see if it all works
if you want sense roms or any other reason you want the dz hboot go here for a better explanation
http://forum.xda-developers.com/showthread.php?t=1728208
good luck

PNuT. said:
0.76.2000 > G2
0.84.2000 > DZ
if you have a DZ you have flashed the g2 hboot which is why it wont boot
Click to expand...
Click to collapse
i just rechecked and you are 100% right.
Please how can i reflash hboot 084.2000?

PNuT. said:
0.76.2000 > G2
0.84.2000 > DZ
if you have a DZ you have flashed the g2 hboot which is why it wont boot
Click to expand...
Click to collapse
i just rechecked and you are 100% right.
Please how can i reflash hboot 084.2000? Is it posible through fastboot

kenanibeze said:
i just rechecked and you are 100% right.
Please how can i reflash hboot 084.2000? Is it posible through fastboot
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=27796375
Sent from my HTC Vision using xda premium

demkantor said:
http://forum.xda-developers.com/showthread.php?p=27796375
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
thanks i have booth the phone back to life:victory:
but the gapps(gapps-jb-20120802-signed.zip) i flashed is not working...its like it could not connect. keeps showing sever error
is there any gapps i can flash in. i'm running on Andromadus Mimicry ROM – version 1.5.0

the gapps would be flashed via the aroma installer in mimicry, any google apps not included in the installer would be downloaded from play (maps, gmail, etc) even then you could just use a file explorer to download any .apk from your sdcard or use titanium backup to get any apps back
Sent from my HTC Vision using xda premium

Unable to ROOT Desire Z from 2.2.1?

I want to load a custom ROM on my Desire Z. (finally!)
And I eventually got adb to work.
Now following the guide: Rooting the Vision (G2/DZ) and DHD; I got as far as this step:
4 S-OFF, root and its friends Super-CID, SIM-unlock, engineering hboot, clockwork recovery and root
In the following section we are trying to gain write access to the emmc by power cycling it.
We recommend to install the engineering hboot as part of the gfree procedure.
In the root shell (indicated by the #) that you got in the Temporary root section execute the following commands:
Code:
# cd /data/local/tmp
# ./gfree -f -b hboot-eng.img -y recovery.img
# ./root_psn
# sync
Wait a few seconds for the changes to "take".
Click to expand...
Click to collapse
Before receiving this error:
Code:
# ./gfree -f -b hboot-eng.img -y recovery.img
./gfree -f -b hboot-eng.img -y recovery.img
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
--hboot set. hboot image hboot-eng.img will be installed in partition 18
--recovery set. recovery image recovery.img will be installed in partition 21
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-g132894e
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02adc44, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02ad000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc02adc44 + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 18 and installing specified hboot image...
md5sum #1 = 62c0aac0a85f3a0a0cbe364b64c552e6
md5sum #2 = 2ce1bdd5e4c1119ccfcecb938710d742
Backing up partition /dev/block/mmcblk0p18 to /sdcard/part18backup-1363017105.bin ...
Writing image hboot-eng.img to partition /dev/block/mmcblk0p18 ...
md5sum #3 = 62c0aac0a85f3a0a0cbe364b64c552e6
md5sum #3 == md5sum #1 - the hboot image was not installed!
Probably the power cycle of the eMMC failed. Check the messages above.
You might join the IRC channel #G2Root on Freenode for further help!
What should be my next course of action?
Thanks for all suggestions,
Alec Taylor

Double check you have the right hboot downloaded and that the md5sum matches, then run the command again. If you still have issues copy and paste your input/output from cmd here
Sent from my Nexus 7 using xda premium

I have included the input/output from my CMD in the initial post.

Sorry I thought you were just copying and pasting from the guide you were folowing. I guess I was reffuring to the entire root procedure but its no big deal
Its telling you exactly what is happening, phone didn't take the flash of the new engineeging bootloader, probably the emmc didn't cycle, try running command again, if its the same outcome double check your radio version as that can cause this or can you post all info from your hboot screen here
Sent from my SGH-T839 using Tapatalk 2

Also I couldn't get it to work with Gingerbreak or DooMLoRD's Easy Rooting Toolkit either.

*bump*

Right down all info on boot loader, you seem to know what to do but you're missing something, possibly need to change radio as gfree will not work with newer ones
Sent from my Nexus 7 using xda premium

FYI: Was able to root it finally by upgrading my stock to gingerbread from froyo; then back down to non-stock froyo followed by upgrade to modded Jelly Bean.