[Q] Help! Mytouch 4g 2.3.4 Gingerbread - myTouch 4G Q&A, Help & Troubleshooting

Let me first say sorry if I am posting where I should not. I'm a noob and completely frustrated. I successfully rooted and unrooted a MT4g on 2.2.1 which I shipped back to Tmobile for a replacement. I now have a new shiny MT4g on 2.3.4. I originally mistakenly tried to root using visionary. I was then stuck on splash screen. I found the 2.3.4 PD15IMG that I booted from SDcard from bootloader. I then ran the downgrade successfully or at least I believe successfully. I am again now stuck on the splash screen and really need a hand. When I run the 2.2.1 stock it changes the hboot to what ever it should 0.86.0000 or something like that but the rom never boots. I can intermittently get into the 2.3.4 rom after flashing and hboot changes to 0.89.0005 but the moment the phone is turned off BAM splash screen again. Any help is greatly appreciated.
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 800
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Potential exploit area found at address fbb55c00:400.
Exploiting device...
C:\android-sdk\platform-tools>adb shell
# exit
exit
C:\android-sdk\platform-tools>adb push misc_version /data/local/tmp/misc_version
198 KB/s (15837 bytes in 0.078s)
C:\android-sdk\platform-tools>adb push flashgc /data/local/tmp/flashgc
1362 KB/s (712688 bytes in 0.511s)
C:\android-sdk\platform-tools>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version: permission denied
#
C:\android-sdk\platform-tools>adb push misc_version /data/local/tmp/misc_version
1189 KB/s (15837 bytes in 0.013s)
C:\android-sdk\platform-tools>adb push flashgc /data/local/tmp/flashgc
1599 KB/s (712688 bytes in 0.435s)
C:\android-sdk\platform-tools>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version: permission denied
# dd if=/dev/block/mcblk0p17 bs=1 skip=160 count=10
dd if=/dev/block/mcblk0p17 bs=1 skip=160 count=10
/dev/block/mcblk0p17: cannot open for read: No such file or directory
# exit
exit
C:\android-sdk\platform-tools>adb push fre3vo /data/local/tmp
797 KB/s (9796 bytes in 0.012s)
C:\android-sdk\platform-tools>adb shell
# chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
# /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 0
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Potential exploit area found at address fbb55c00:400.
Payload verification failed.
Scanning region fbb70000...
Scanning region fbc60000...
Scanning region fbd50000...
Scanning region fbe40000...
Scanning region fbf30000...
Scanning region fc020000...
Scanning region fc110000...
Scanning region fc200000...
Scanning region fc2f0000...
Scanning region fc3e0000...
Scanning region fc4d0000...
Scanning region fc5c0000...
Scanning region fc6b0000...
Scanning region fc7a0000...
Scanning region fc890000...
Scanning region fc980000...
Scanning region fca70000...
Scanning region fcb60000...
Scanning region fcc50000...
Scanning region fcd40000...
Scanning region fce30000...
Scanning region fcf20000...
Scanning region fd010000...
Scanning region fd100000...
Scanning region fd1f0000...
Scanning region fd2e0000...
Scanning region fd3d0000...
Scanning region fd4c0000...
Scanning region fd5b0000...
Scanning region fd6a0000...
Scanning region fd790000...
Scanning region fd880000...
Scanning region fd970000...
Scanning region fda60000...
Scanning region fdb50000...
Scanning region fdc40000...
Scanning region fdd30000...
Scanning region fde20000...
Scanning region fdf10000...
Scanning region fe000000...
Scanning region fe0f0000...
Scanning region fe1e0000...
Scanning region fe2d0000...
Scanning region fe3c0000...
Scanning region fe4b0000...
Scanning region fe5a0000...
Scanning region fe690000...
Scanning region fe780000...
Scanning region fe870000...
Scanning region fe960000...
Scanning region fea50000...
Scanning region feb40000...
Scanning region fec30000...
Scanning region fed20000...
Scanning region fee10000...
Scanning region fef00000...
Scanning region feff0000...
Scanning region ff0e0000...
Scanning region ff1d0000...
Scanning region ff2c0000...
Scanning region ff3b0000...
Scanning region ff4a0000...
Scanning region ff590000...
Scanning region ff680000...
Scanning region ff770000...
Scanning region ff860000...
Scanning region ff950000...
Scanning region ffa40000...
Scanning region ffb30000...
Scanning region ffc20000...
Scanning region ffd10000...
Scanning region ffe00000...
Scanning region ffef0000...
Scanning region fffe0000...
# adb shell
adb shell
adb: not found
# exit
exit
C:\android-sdk\platform-tools>adb push misc_version /data/local/tmp/misc_version
1189 KB/s (15837 bytes in 0.013s)
C:\android-sdk\platform-tools>adb push flashgc /data/local/tmp/flashgc
1661 KB/s (712688 bytes in 0.419s)
C:\android-sdk\platform-tools>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version: permission denied
# exit
exit
C:\android-sdk\platform-tools>adb push misc_version /data/local/tmp/misc_version
1405 KB/s (15837 bytes in 0.011s)
C:\android-sdk\platform-tools>adb push flashgc /data/local/tmp/flashgc
1611 KB/s (712688 bytes in 0.432s)
C:\android-sdk\platform-tools>adb shell chmod 777 /data/local/tmp/*
C:\android-sdk\platform-tools>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
# ./flashgc
./flashgc
Backing up sd-card MBR to file "./sdcardMbr-backup.img".
Making sd-card golden.
Writing gold-card to sd-card (/dev/block/mmcblk1) ...
SUCCESS: SD-card is golden.
# dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
1.00.000.010+0 records in
10+0 records out
10 bytes transferred in 0.003 secs (3333 bytes/sec)
# exit
exit
C:\android-sdk\platform-tools>adb push su /data/local/tmp/
278 KB/s (22228 bytes in 0.078s)
C:\android-sdk\platform-tools>adb push busybox /data/local/tmp/
1616 KB/s (1372660 bytes in 0.829s)
C:\android-sdk\platform-tools>adb push fixsu.sh /data/local/tmp/
13 KB/s (594 bytes in 0.042s)
C:\android-sdk\platform-tools>adb install SuperUser.apk
1004 KB/s (196521 bytes in 0.191s)
pkg: /data/local/tmp/SuperUser.apk
Success

Ok so are you saying you ran visionary before downgrading to the PD15IMG(2.2.1)?
Sent from my HTC Glacier using xda premium

Yes. I didn't realize that the new MT4G that Tmobile shipped was on 2.3.4 so I just went in and followed the GFree Root process using visionary so that I could downgrade.
Currently:
Glacier PVT Ship S-Off
Hboot - 0.89.005 - this changes when i flash the 2.2.1 or the 2.3.4 PD15IMG
microp-0429
Radio -26.11.04.03_m
emmc -boot
every now and again when I flash the 2.3.4 PD15IMG I can get the phone booted, but as soon as it powers down splash screen. additionally, it now gets the green circle when going into recovery for 30 seconds or so and then the red triangle. further feedback is greatly appreciated.

ihackback said:
Yes. I didn't realize that the new MT4G that Tmobile shipped was on 2.3.4 so I just went in and followed the GFree Root process using visionary so that I could downgrade.
Click to expand...
Click to collapse
You cannot root 2.3.4. You need to downgrade to 2.2.1. Please see my noob thread in my signature. It has all of the information you need, on that and other topics you might want to check prior to rooting your phone.

Understood. The issue I am having is that I tried to root using visionary gfree with 2.3.4 and have been having issues since. I am now trying to determine if my phn is done. I brought it back to life briefly after flashing the 2.3.4 gingerbread which was stock on the new phn, I then followed the down grade process and flashed back to 2.2.1 which booted up fine. The phone then powered down and now I can't get passed the splash screen. I've tried flashing back to 2.3.4 and to 2.2.1 and the only thing that happens is the hboot number changes, but the rom never boots.

ihackback said:
I've tried flashing back to 2.3.4 and to 2.2.1 and the only thing that happens is the hboot number changes, but the rom never boots.
Click to expand...
Click to collapse
You have good matching MD5SUMs?

Dunno, can you further explain MD5SUMs?

He is saying you probably had bad download and I know you can't even check because you can't pass the the splach screen so what I would do is download the PD15IMG for 2.3.4 (again) and it should erase anything you have done and try again that way.
Sent from my HTC Glacier using XDA App

Yeah, try redownloading. Your connection was probably interrupted during the download.

ihackback said:
Dunno, can you further explain MD5SUMs?
Click to expand...
Click to collapse
Was your replacement s=off when you received it or did you manage to get it s=off with gfree process?
To answer your question about md5sum. It is the alpha numeric code you get after hashing the file. It's purpose is to make sure the received download file matches the original.
Sent from my HTC Glacier using xda premium

I managed to get S-Off using the visionary / gfree method on the 2.3.4 gingerbread. The phone just got all flaky after that. I got access, downgraded, flashed rom, and it just keep getting stuck on the splash. Appreciate all the help. Tmobile rocks. They sent me another, no questions asked. I got the new one up and running after a downgrade (1st). I missed the downgrade part last time round. Thanks again.

help error!!
C:\android-sdk-windows\platform-tools>fastboot-windows devices
SH13PRM05225 fastboot
C:\android-sdk-windows\platform-tools>fastboot-windows oem rebootRUU
... OKAY
C:\android-sdk-windows\platform-tools>fastboot-windows flash zip StockRom.zip
sending 'zip' (319593 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
C:\android-sdk-windows\platform-tools>fastboot-windows flash zip StockRom.zip
sending 'zip' (319593 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
C:\android-sdk-windows\platform-tools>fastboot-windows flash zip StockRom.zip
sending 'zip' (319593 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
C:\android-sdk-windows\platform-tools>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\android-sdk-windows\platform-tools>fastboot-windows flash zip StockRom
error: cannot load 'StockRom'
C:\android-sdk-windows\platform-tools>fastboot-windows flash zip StockRom.zip
sending 'zip' (319593 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
C:\android-sdk-windows\platform-tools>

Related

[GUIDE] How to get root/flash custom roms with HTCDEV unlock

I know some people out there will use the new "official" htcdev.com unlock option for the G2/DZ, but they will still need to do **** to get root or flash custom roms.
I REALLY RECOMMEND USING THE XDA METHOD OF ACQUIRING ROOT AND S-OFF
S-OFF is possible! We can relock the bootloader to allow a downgrade
Go to FASTBOOT USB mode (where you got the unlock token code, and unlocked the bootloader)
Code:
fastboot oem lock
You can then downgrade by following this guide
And get S-OFF with this guide
DO NOT LOCK THE BOOTLOADER IF YOU DON'T WANT TO ROOT PROPERLY!
LOCKING THE BOOTLOADER WILL CAUSE THE REST OF THIS GUIDE TO FAIL!
-------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------------
First, some background as to why these methods are needed.
The HTC 'official' unlock method lets /system be written (given root access) in any mode.
The boot partition, and recovery are only writeable in fastboot mode though. So we need to flash a recovery through fastboot, flash a custom rom, then flash its boot image to be able to boot it.
GAINING ROOT ON STOCK ROM
Gaining Temp Root
DHD USERS WITH SENSE 3.x WILL HAVE TO USE TACOROOT
1. Download the attached files, unzip them, and place the files in your platform-tools folder. To elaborate, place the fre3vo file inside of the fre3vo.zip file in your platform-tools directory.
2. Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
> adb shell cat /dev/msm_rotator
[I]/dev/msm_rotator: invalid length[/I]
4. If you received the same message, you're good to continue on. If not... I'd recommend going back to #g2root and asking them. (I am just passing along the information after all).
5. Run the following commands from your platform-tools directory.
Code:
> adb push fre3vo /data/local/tmp
> adb shell
$ chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
6. After you enter that command, with luck you should see something similar to the last few lines in the following displayed. (It may take a minute or two. From what I can tell, this appears to be the quickest method as the exploit seems to be found in the latter regions.)
Code:
[I]Buffer offset: 00000000
Buffer size: 8192
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba90000...
Potential exploit area found at address fbb4d600:a00.
Exploiting device...[/I]
7. If you did get kicked out of adb shell, open it again. You should now see the lovely # instead of $, thus granting you temp root. Go ahead and exit out of shell to proceed to the next stage.
Code:
> adb shell
# exit
Getting Perm-Root
1. Download the attached file, "Vision-fre3vo-temp-root.zip".
2. Extract the contents to your platform-tools directory.
3. Run the following commands in command prompt while in platform-tools directory:
Code:
> adb push su /data/local/tmp/
> adb push busybox /data/local/tmp/
> adb push fixsu.sh /data/local/tmp/
> adb install SuperUser.apk
> adb shell chmod 755 /data/local/tmp/fixsu.sh
> adb shell chmod 755 /data/local/tmp/busybox
> adb shell /data/local/tmp/fixsu.sh
Note: If you get permission denied errors on busybox when trying to run fixsu.sh, please let me know.
4. Reboot phone, you should now have perm-root.
FLASHING A CUSTOM ROM
Flashing a custom recovery
Note: this only needs to be done once
1. Download a custom recovery: Latest Clockworkmod, Clockworkmod Touch, 4ext Touch
2. Place the recovery img in the folder with fastboot.exe (which you used to unlock your device), rename the recovery to recovery.img
3. Reboot phone to fastboot mode: Either pull battery and hold TRACKPAD and press power, or run 'adb reboot bootloader' from a cmd/terminal
4. Run
Code:
> fastboot flash recovery recovery.img
[I]sending 'recovery' (4930 KB)...
OKAY [ 0.851s]
writing 'recovery'...
OKAY [ 0.819s]
finished. total time: 1.670s[/I]
Flashing a custom rom
1. Download the rom.zip you wish to run.
2. Extract boot.img from the zip and place it in the folder with fastboot.
3. Copy the rom.zip to your sdcard
4. Flash the rom.zip from your sdcard
5. Reboot to fastboot mode (as above)
6. Run from a cmd/terminal
Code:
> fastboot flash boot boot.img
[I]sending 'boot' (4096 KB)...
OKAY [ 0.711s]
writing 'boot'...
OKAY [ 1.085s]
finished. total time: 1.798s[/I]
7. Reboot, you will now have a custom rom!
Credits:
Setherio, seeing as I ripped off half his guide.
Pierre_ja, helping figure out how to go about this.
If you get stuck with any of this, join #G2ROOT on freenode
-Nipqer
I'll try this ASAP. This bootloader have only brought me a **** load of headache, hope this works..
Thanks!
Yay a tester. let me know how it works.
We've had 1 person get root, and 2 flash custom roms with this, but I'd appreciate any feedback.
-Nipqer
fixsu.sh permissions denied
good to know that xda has people like you to help out
couldn't get root here's the result
C:\Android SDK\android-sdk\platform-tools>adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length
C:\Android SDK\android-sdk\platform-tools>adb push fre3vo /data/local/tmp
869 KB/s (9796 bytes in 0.011s)
C:\Android SDK\android-sdk\platform-tools>adb shell
$ chmod 777 /data/local/tmp
chmod 777 /data/local/tmp
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
$ /data/local//tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local//tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 0
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Potential exploit area found at address fbb6e200:e00.
Exploiting device...
C:\Android SDK\android-sdk\platform-tools>adb shell
# exit
exit
C:\Android SDK\android-sdk\platform-tools>adb push su /data/local/tmp/
1205 KB/s (22228 bytes in 0.018s)
C:\Android SDK\android-sdk\platform-tools>adb push busybox /data/local/tmp/
1683 KB/s (1372660 bytes in 0.796s)
C:\Android SDK\android-sdk\platform-tools>adb push fixsu.sh /data/local/tmp/
109 KB/s (560 bytes in 0.005s)
C:\Android SDK\android-sdk\platform-tools>adb install Superuser.apk
1060 KB/s (196521 bytes in 0.181s)
pkg: /data/local/tmp/Superuser.apk
Success
C:\Android SDK\android-sdk\platform-tools>adb shell chmod 755 /data/local/tmp/fi
xsu.sh
C:\Android SDK\android-sdk\platform-tools>adb shell /data/local/tmp/fixsu.sh
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
C:\Android SDK\android-sdk\platform-tools>adb shell chmod 755 /data/local/tmp/fi
xsu.sh
C:\Android SDK\android-sdk\platform-tools>adb shell /data/local/tmp/fixsu.sh
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
/data/local/tmp/fixsu.sh: /data/local/tmp/busybox: permission denied
C:\Android SDK\android-sdk\platform-tools>
Click to expand...
Click to collapse
Hmm, I wonder why thats happening...
Want to join the IRC channel so we can sort this out?
-Nipqer
how do i join?
EDIT: i'll do a full factory restore, format sdcard and try this out again
Go to http://webchat.freenode.net/
choose a nickname, in channels enter #G2ROOT (with the hash)
-Nipqer
Hi Guys.
I'm @ work, but gonna try this in my break asap.
Sorry if I have missed something, but don't you need the eng hboot in order to use "fastboot flash" ?
Sent from my Desire Z running CM7.
I've done everything as above.
Everything went just fine.
But when I start SetCPU, It comes up with "root acces not detected" did you allow setcpu through superuser permissions?
In the superuser app (which is visible) I can't edit anything?
Also, it's not showing a pop up with "allow"
Am I doing something wrong?
C:\>cd android
C:\Android>cd platform-tools
C:\Android\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ fastboot flash recovery recovery.img
fastboot flash recovery recovery.img
fastboot: permission denied
$
$ exit
exit
C:\Android\platform-tools>fastboot flash recovery recovery.img
< waiting for device >
steviewevie said:
Sorry if I have missed something, but don't you need the eng hboot in order to use "fastboot flash" ?
Sent from my Desire Z running CM7.
Click to expand...
Click to collapse
the hboot htc provides for the unlock supports fastboot commands, took us a while to figure that out at #g2root.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
wm6.5 said:
C:\>cd android
C:\Android>cd platform-tools
C:\Android\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ fastboot flash recovery recovery.img
fastboot flash recovery recovery.img
fastboot: permission denied
$
$ exit
exit
C:\Android\platform-tools>fastboot flash recovery recovery.img
< waiting for device >
Click to expand...
Click to collapse
you have to boot in fastboot mode to be able to issue fastboot commands:
from shell ($ or #) while the phone is connected to the computer:
Code:
exit
adb reboot bootloader
from normal win cmd (the > prompt):
Code:
adb reboot bootloader
petarpLab said:
the hboot htc provides for the unlock supports fastboot commands, took us a while to figure that out at #g2root.
Click to expand...
Click to collapse
Ok, cool, thanks for the info. That's something useful it does then.
Sent from my Desire Z running CM7.
wm6.5 said:
C:\>cd android
C:\Android>cd platform-tools
C:\Android\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ fastboot flash recovery recovery.img
fastboot flash recovery recovery.img
fastboot: permission denied
$
$ exit
exit
Click to expand...
Click to collapse
You need to run fastboot from your PC, not the phone
Sent from my Desire Z running CM7.
wm6.5: I don't know if SetCPU can work on stock roms with root. You might need a different kernel for it.
-Nipqer
Nipqer said:
Yay a tester. let me know how it works.
We've had 1 person get root, and 2 flash custom roms with this, but I'd appreciate any feedback.
-Nipqer
Click to expand...
Click to collapse
You sir, just made my day!
Guide works like a charm! thank you!
Nipqer, thanks Mate.
Got everything sorted out on G2root on irc!
Your guide is the .... thanks again!
Thanks this saved me! The guys on g2root irc are way too helpful! Much thanks to them, no thanks to HTC unlocker for wasting a day of my life.
Is there any way of getting S-Off after you've used the HTC Dev Unlock?
No, not yet. As soon as we have figured out a way I'll update the OP.
-Nipqer

Cant perm root Mytouch 4G please help before you move my thread

I have spent hours on xda, downloading gfree, trying to downgrade, trying taco root. I even unlocked bootloader at htc dev and cannot get my phone perm rooted
I have 2.3.4
software 2.32.531.1
i used the guide on how to downgrade to 2.2.1 for the visionary exploit
i keep getting permission denied
Potential exploit area found at address fbb80e00:200.
I am sorry for sounding like "noob" but i wasted the day trying to do this and have given up
Someone please help me, ill even donate a cup of coffee to whoever helps me fix this. No joke from 9 am to 530 pm, i have been going in circles, i downloaded the htc easy root tool all failed
the farthest i made it was getting temp root with taco root, but there are no clear cut instructions for what to do after, these guides are over a year old prior to my version of android
I'm not sure where your going wrong but the guides work fine. I used them to downgrade, perm root, and flash the engineering bootloader. Have you tried asking in the q and a section? I'm sure you will find a solution, if you ask in the proper place.
Sent from my HTC Glacier using Tapatalk
I would try this guide http://forum.xda-developers.com/showthread.php?p=15851661
Sent from my HTC Glacier using xda premium
i have been on here for 9 hours going through the q/a this is a brand new str8 from t-mobile mytouch 4g with the newest possible rom, a year ago i successfully did this dozens of time with visionary, its this new rom thats the problem, i put virtuous rom successfully on my first mytouch a year ago, and ive rooted my hd2 for friends and family, so i know my way around xda, this is the first time im truly stuck
cnote 74 i tried that guide my expolit area "fbb80e00:200" is not covered by that guide, if you look at the 5 or 6 lines
$ /data/local/tmp/fre3vo -debug -start 10000000 -end 1FFFFFFF
$ /data/local/tmp/fre3vo -debug -start 20000000 -end 2FFFFFFF
$ /data/local/tmp/fre3vo -debug -start 30000000 -end 3FFFFFFF
$ /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF
$ /data/local/tmp/fre3vo -debug -start E0000000 -end EFFFFFFF
mine is different than all of these
this is what ive been getting, i followed the guide to the T
C:\AndroidSDK\platform-tools>adb shell cat /dev/msm_rotator
adb server is out of date. killing...
* daemon started successfully *
/dev/msm_rotator: invalid length
C:\AndroidSDK\platform-tools>adb push fre3vo /data/local/tmp
869 KB/s (9796 bytes in 0.011s)
C:\AndroidSDK\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 800
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Potential exploit area found at address fbb6c400:c00.
Exploiting device...
C:\AndroidSDK\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
# exit
exit
C:\AndroidSDK\platform-tools>adb push misc_version /data/local/tmp/misc_version
1718 KB/s (15837 bytes in 0.009s)
C:\AndroidSDK\platform-tools>adb shell chmod 777 /data/local/tmp/
C:\AndroidSDK\platform-tools>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version: permission denied
#
1st off.......THIS IS THE DEVELOPMENT SECTION! NOT Q&A! THATS WHAT THE Q&A IS FOR!
2nd....its because you unlocked via htcdev, which we have warned users multiple times if you did read the Q&A and General forums.
Htcdev method makes it harder to root/flash a ROM. We warned you. And then you complain and post in the wrong section!
Edit: also.....If you knew to put "DON'T MOVE THREAD", why did you post it here in the first place?
Sent from my HoneySmartDroid Port using XDA Premium.
Edit: I like that better /\
Sent from my HTC Glacier using Tapatalk
Chek this out bro hope it help ;-) http://forum.xda-developers.com/showthread.php?p=9551846
Sent from my HTC Mytouch 4G using xda premium
still stuck invasion2 you have a solution
michael.racelli said:
still stuck invasion2 you have a solution
Click to expand...
Click to collapse
Sorryf for flaming.....anyway I did find something... http://www.forum.xda-developers.com/showthread.php?p=21563546
Sent from my HoneySmartDroid Port using XDA Premium.
michael.racelli said:
I have spent hours on xda, downloading gfree, trying to downgrade, trying taco root. I even unlocked bootloader at htc dev and cannot get my phone perm rooted
I have 2.3.4
software 2.32.531.1
i used the guide on how to downgrade to 2.2.1 for the visionary exploit
i keep getting permission denied
Potential exploit area found at address fbb80e00:200.
I am sorry for sounding like "noob" but i wasted the day trying to do this and have given up
Someone please help me, ill even donate a cup of coffee to whoever helps me fix this. No joke from 9 am to 530 pm, i have been going in circles, i downloaded the htc easy root tool all failed
the farthest i made it was getting temp root with taco root, but there are no clear cut instructions for what to do after, these guides are over a year old prior to my version of android
Click to expand...
Click to collapse
no need to downgrade
http://forum.xda-developers.com/showthread.php?t=803682
I relocked the bootloader, still the same thing permission denied, am i the only one who has encountered this issue, i cannot root downgrade right now if my life depended on it right now
adb push misc_version /data/local/tmp/misc_version
> adb push flashgc /data/local/tmp/flashgc
> adb shell chmod 777 /data/local/tmp/* <--------(THIS LINE IS YOUR MISTAKE)
> adb shell
# cd /data/local/tmp
# ./misc_version -s 1.00.000.0
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
# ./flashgc
Click to expand...
Click to collapse
Click to expand...
Click to collapse
From what I gathered on your post, I am thinking you did a pastebin which is good. If you did, and it copied straight from you command prompt, than you are missing an (*) at the end of the adb chmod 777 /data/local/tmp/.
I recently used the guide to downgrade/root/flash e-bootloader/flash rom on 2 brand new 2.3.4 mytouch 4gs 2 weeks ago.
Also if you can manage to safe some time and headache reformat your SD card with the PD15IMG on to to fat32. If you dont you have a very likely chance that when you attempt to flash the PD15IMG to get a no image or bad image error in your bootloader when downgrading.
Slow down, step away from the computer, take a break and come back and START OVER. I spent 2 days getting that damned error on the pd15img.
edit:The quoted text is from the downgrading guide.
thank you for responding but that link you sent me shows up as a dead link, didnt go anywhere bro
michael.racelli said:
thank you for responding but that link you sent me shows up as a dead link, didnt go anywhere bro
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=15851661
This is the downgrading guide that I believe you have been using. Its the same I used. Like I said start over, and make sure every line in your cmd is typed exactly the way it is written in the thread.
If you feel you must, you can even copy and paste line by line into command prompt
Heh, sorry. Here you are! http://forum.xda-developers.com/showthread.php?p=21563546
hellmonger said:
no need to downgrade
http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
Hellmonger, I never got superoneclick to work on 2.3.4 mytouch 4g. Tried it and it gets stuck on the psneuter
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
invasion2 said:
Heh, sorry. Here you are! http://forum.xda-developers.com/showthread.php?p=21563546
Click to expand...
Click to collapse
This is for the desire/g2 it wont work. Use the link I posted.
. . .
knew someone was gonna take me the wrong way. deleted.
seeing from what other users have posted, it seems that you have "unlocked" your bootloader the Official HTC way. then there's not much anyone here can do for you, since that way wasn't recommended anyway.
but since your bootloader is now "unlocked", i don't see why you need to follow the downgrade procedure anymore. from looking at other device forums, i see that all you gotta do is get a custom recovery on there somehow, flash a rooted ROM, flash the boot image of that ROM (since you decided to do it the HTC way) and that's pretty much it...
Contacting a mod at once...
^^^^^^^ I did the same -______-

[Q] downgrading problem mytouch 4g

downgrading problem
every thing goes good till i get to here im on mytouch 4g help me
i use this guide
http://forum.xda-developers.com/showthread.php?t=1178912
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version: permission denied
adb shell chmod 777 /data/local/tmp/*
You didn't do that or didn't successfully do that.
Redo that. COPY the command AS IS.
If you want, you can do it just before running ./misc_version, while being in the shell. In this case you just need to type chmod 777 *.
C:\android-sdk\platform-tools>adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length
C:\android-sdk\platform-tools>adb push fre3vo /data/local/tmp
push: fre3vo/__MACOSX/._fre3vo -> /data/local/tmp/__MACOSX/._fre3vo
push: fre3vo/fre3vo -> /data/local/tmp/fre3vo
2 files pushed. 0 files skipped.
222 KB/s (10025 bytes in 0.043s)
C:\android-sdk\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 0
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Scanning region fbb70000...
Potential exploit area found at address fbb80e00:200.
Exploiting device...
C:\android-sdk\platform-tools>adb shell
# exit
exit
C:\android-sdk\platform-tools>adb push misc_version /data/local/tmp/misc_version
push: misc_version/misc_version.c -> /data/local/tmp/misc_version/misc_version.c
push: misc_version/misc_version -> /data/local/tmp/misc_version/misc_version
push: misc_version/gopt.h -> /data/local/tmp/misc_version/gopt.h
push: misc_version/gopt.c -> /data/local/tmp/misc_version/gopt.c
4 files pushed. 0 files skipped.
341 KB/s (31399 bytes in 0.089s)
C:\android-sdk\platform-tools>adb push flashgc /data/local/tmp/flashgc
push: flashgc/flashgc -> /data/local/tmp/flashgc/flashgc
1 file pushed. 0 files skipped.
1566 KB/s (712688 bytes in 0.444s)
C:\android-sdk\platform-tools>adb shell chmod 777 /data/local/tmp/*
C:\android-sdk\platform-tools>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version: permission denied
#
Click to expand...
Click to collapse
this is what i did
Jack_R1 said:
adb shell chmod 777 /data/local/tmp/*
You didn't do that or didn't successfully do that.
Redo that. COPY the command AS IS.
If you want, you can do it just before running ./misc_version, while being in the shell. In this case you just need to type chmod 777 *.
Click to expand...
Click to collapse
# chmod 777 /*
chmod 777 /*
Unable to chmod /bootcomplete.rc: Read-only file system
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version: permission denied
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version: permission denied
# chmod 777 *
chmod 777 *
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version: permission denied
# chmod 777 *.
chmod 777 *.
Unable to chmod *.: No such file or directory
#
i just dont see what im i dong wrong
You unzipped the ZIP file misc_version in another subfolder, rather than locally.
When you're pushing misc_version, you're pushing subfolder instead of the file. This makes the executable file misc_version to be at /data/local/tmp/misc_version/misc_version and not /data/local/tmp/misc_version, as it should have been. The log is clear as a sun and shows it in a very visible way. Of course it means that the simple earlier step that says "extract the files here" wasn't executed properly, and you couldn't see this mistake of yours.
Of course, since the file isn't in the correct place, the command doesn't work.
Execute the commands as follows:
C:\android-sdk\platform-tools>adb shell chmod 777 /data/local/tmp/misc_version/*
C:\android-sdk\platform-tools>adb shell
# cd /data/local/tmp/misc_version
# ./misc_version -s 1.00.000.0
C:\android-sdk\platform-tools>adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length
C:\android-sdk\platform-tools>adb push fre3vo /data/local/tmp
push: fre3vo/__MACOSX/._fre3vo -> /data/local/tmp/__MACOSX/._fre3vo
push: fre3vo/fre3vo -> /data/local/tmp/fre3vo
2 files pushed. 0 files skipped.
113 KB/s (10025 bytes in 0.085s)
C:\android-sdk\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 0
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Scanning region fbb70000...
Potential exploit area found at address fbb80e00:200.
Exploiting device...
C:\android-sdk\platform-tools>adb shell
# exit
exit
C:\android-sdk\platform-tools>adb push misc_version /data/local/tmp/misc_version
push: misc_version/misc_version.c -> /data/local/tmp/misc_version/misc_version.c
push: misc_version/misc_version -> /data/local/tmp/misc_version/misc_version
push: misc_version/gopt.h -> /data/local/tmp/misc_version/gopt.h
push: misc_version/gopt.c -> /data/local/tmp/misc_version/gopt.c
4 files pushed. 0 files skipped.
268 KB/s (31399 bytes in 0.114s)
C:\android-sdk\platform-tools>adb push flashgc /data/local/tmp/flashgc
push: flashgc/flashgc -> /data/local/tmp/flashgc/flashgc
1 file pushed. 0 files skipped.
1322 KB/s (712688 bytes in 0.526s)
C:\android-sdk\platform-tools>adb shell chmod 777 /data/local/tmp/*
C:\android-sdk\platform-tools>adb shell chmod 777 /data/local/tmp/misc_version/*
C:\android-sdk\platform-tools>adb shell
# cd /data/local/tmp/misc_version
cd /data/local/tmp/misc_version
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
#
Click to expand...
Click to collapse
thx man we need to fix the guide
./flashgc
./flashgc: permission denied
#
C:\android-sdk\platform-tools>
The guide isn't wrong, you are. Probably hundreds or thousands of people used this guide for downgrading, here you come and the guide is suddenly wrong? And the same applies to the next failure - it's EXACTLY the same. Why is it so hard to make a single small step yourself?
Plus, you don't need flashgc. You can proceed with downgrading now.
thx jack_R1 you the man im perma root and s-off now i just have to see how to flash roms
Install custom recovery, boot into it, copy the ROM on SD card, wipe everything, flash.
These are the approximate steps. You can search for each step, or just search "mytouch 4g flash custom rom" in Youtube, you'll likely find a guide.

Help please! Want to root my HTC DesireZ 2.3.3

Hi
I am a noob and google translation is my friend but is not 100% reliable, so be patient.
I want to downgrade but when I do adb shell commands have errors and something you are wrong:
C:\android-sdk-windows\platform-tools>adb push fre3vo /data/local/tmp
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1195 KB/s (9796 bytes in 0.008s)
C:\android-sdk-windows\platform-tools>adb push misc_version /data/local/tmp
2209 KB/s (15837 bytes in 0.007s)
C:\android-sdk-windows\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
$ chmod 777 /data/local/tmp/misc_version/data/local/tmp/fre3vo -debug -start FAA
90000 -end FFFFFFFF
chmod 777 /data/local/tmp/misc_version/data/local/tmp/fre3vo -debug -start FAA90
000 -end FFFFFFFF
Unable to chmod /data/local/tmp/misc_version/data/local/tmp/fre3vo: Not a direct
ory
$
C:\android-sdk-windows\platform-tools>
I think the installation of the adb is correct but I can not find the problem.
You accidentally put 2 commands together
chmod 777 /data/local/tmp/misc_version/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
Should be:
chmod 777 /data/local/tmp/misc_version
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
-Nipqer
upss
I will try, thank you
Now i got this:
C:\android-sdk-windows\platform-tools>adb push fre3vo /data/local/tmp
1195 KB/s (9796 bytes in 0.008s)
C:\android-sdk-windows\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 800
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Potential exploit area found at address fbb55c00:400.
Exploiting device...
C:\android-sdk-windows\platform-tools>
Is normal?
I got # when i type the command adb shell
# in the shell means you have escalated acess (root/super user).
$ means normal access.
What method are you using?
It's been a long time since I went through it, but I believe all you've done is gained temp root access. You still need to S-OFF, hboot, and install a recovery which will then allow you to flash different ROMs.
I'm using this method: http://wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Firmware_Downgrade_(Gingerbread)
I need downgrade my phone for root, I can not have the root with the gingerbread.
Use flashgc from this guide
The 'Gaining SuperCID with a Goldcard' part
-Nipqer
I'm in 2.2 now , thank you all, what tutorial you suggest?
I'd recommend either the XDA Wiki, or the Cyanogenmod Wiki
Both guides are identical for the method, but the XDA wiki has a lot of information, explaining what is happening, whereas the cm wiki is just commands.
-Nipqer
I already root and the s-off, thank you for the help
Silence7887 said:
I already root and the s-off, thank you for the help
Click to expand...
Click to collapse
can u explain me the way u tried?
Use this method: http://forum.xda-developers.com/showthread.php?t=1178912
For me, I had no root, I had the s-off and recovery install but not the root! Try and if you also have the s-off and recovery install but without the root, then I would try to help you.

Problem with rooting MyTouch 4G Phone ($ exploit error)

Hello,
I have had my MyTouch 4G since January of 2011, and today I decided to finally root my phone (growing sick and tired of HTC sense and the tremendous bloatware lag with it). I still like the phone itself (perfect size), and so I was came across CM7, it looks like it is the most stable and popular rom for the MyTouch.
Of course, I myself, I am an IT professional, but have no idea on what the rooting process is, so I have been following the steps CM team has posted on rooting my android device (wiki(dot)cyanogenmod(dot)org/w/Install_CM_for_glacier). I was currently in the process of downgrading the android version, and came across an error. So according to this guide, it said if you come across an $, your exploit has failed, if # you have gained temporary root.
That being said, I have came across the $ sign, which I assume is the exploit. I don't know why I have come across this error, and so, I have posted all the notes from my command line:
C:\adt-bundle-windows-x86-20130729\sdk\platform-tools> ad
local/tmp
1366 KB/s (9796 bytes in 0.007s)
C:\adt-bundle-windows-x86-20130729\sdk\platform-tools> ad
/data/local/tmp
1882 KB/s (589849 bytes in 0.306s)
C:\adt-bundle-windows-x86-20130729\sdk\platform-tools> ad
/local/tmp
1753 KB/s (712688 bytes in 0.397s)
C:\adt-bundle-windows-x86-20130729\sdk\platform-tools> ad
chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/misc_version
chmod 777 /data/local/tmp/flashgc
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFF
adb shell
cd /data/local/tmp
./misc_version -s 1.00.000.0
./flashgc
exit $ chmod 777 /data/local/tmp/fre3vo
./misc_version -s 1.00.000.0
./flashgc
$ chmod 777 /data/local/tmp/misc_version
$ chmod 777 /data/local/tmp/flashgc
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 2fd00000
smem_len: 300000
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 800
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Frame Buffer handle: 4
Buffer offset: 002ee000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Scanning region fbb70000...
Potential exploit area found at address fbbb5600:1a00.
Exploiting device...
I hope someone can help me out on this one... would be awesome if I can manage to root my phone and install the ROM all by today...
Thanks!
Bump bump bump bump bump
please i need help!!
UPDATE: I HAVE GONE PAST THIS ERROR.
Now, my current situation, I had followed the root guide that was stickied on this forums, and it looks like my "S=Off" is on the HBoot loader thing (when you press power + volume down). But, when I try to follow the steps of flashing an actual ROM (through clockworkmod) it says I am not rooted? Any idea on how to fix that?
Been working on this phone for over 15 hours... and will only go to sleep once I know I will have my ROM installed.
How can clockworkmod tell you your not rooted? Have you already flashed a recovery?
Also try this to re-root
http://forum.xda-developers.com/showthread.php?t=1343114
Then install the 4ext app and let it install the recovery.
N_otori0us_ said:
How can clockworkmod tell you your not rooted? Have you already flashed a recovery?
Also try this to re-root
http://forum.xda-developers.com/showthread.php?t=1343114
Then install the 4ext app and let it install the recovery.
Click to expand...
Click to collapse
Actually, I have no idea why is that O.O
But I will follow those steps on that link you send me, and post an update if it all works out!!
Thanks a lot!
So, after trying out that link that was posted earlier, it looks like I have found my real problem now.
My S=off looks like is permanent. But my root is not (I dunno why, no flash or anything yet)
So when I try to connect my phone to my PC (USB Debug Mode on, USB Tethering) it doesn't connect anymore, nor show up on ADB. And in fact my PDAnet driver does not detect it either!
Any idea on what can be the problem?
Update:
I am done!! I installed cm10!! It works
omg, this is awesome!!
sorry for making this thread, i managed to re-root it and now it all worked out.
I love you xda developers, i apologize for making a thread, i managed to research all my information and it worked after 25+ hours of working on my phone.
darkgiant said:
Update:
I am done!! I installed cm10!! It works
omg, this is awesome!!
sorry for making this thread, i managed to re-root it and now it all worked out.
I love you xda developers, i apologize for making a thread, i managed to research all my information and it worked after 25+ hours of working on my phone.
Click to expand...
Click to collapse
You thought the mytouch was hard to root. Try the Panache lol.
Sent from my HTC Glacier using xda app-developers app
N_otori0us_ said:
You thought the mytouch was hard to root. Try the Panache lol.
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
haha, that is the older version right?
Honestly, it was not hard at all, the fact is that the information provided, is all cluttered around the interwebz (requireing actual hours of researching) and to find that perfect stable rom is another animal... haha.
I don't feel like buying another smartphone, I know that the mytouch 4g is still capable of competing with smartphones in the market (of course, it has no fancy camera or gimmicks like the S4) but it works!
darkgiant said:
haha, that is the older version right?
Honestly, it was not hard at all, the fact is that the information provided, is all cluttered around the interwebz (requireing actual hours of researching) and to find that perfect stable rom is another animal... haha.
I don't feel like buying another smartphone, I know that the mytouch 4g is still capable of competing with smartphones in the market (of course, it has no fancy camera or gimmicks like the S4) but it works!
Click to expand...
Click to collapse
Naa it's not the older version... Its the Canadian version
Sent from my HTC Glacier using xda app-developers app
I guess for any moderators preference, I am open to compiling how I went about my situations and such if this is a persistent issue! If not, feel free to close this topic, as my problems are now all solved (THANKFULLY!)
~Darkgiants

Categories

Resources