[Q] Problems getting perm root s=off on MT4G HELP!!! - myTouch 4G Q&A, Help & Troubleshooting

I have been trying to perm root (s=off) my MT4G using the visionary method on the xda perm root procedure (s=off) threads and I can't for the life of me get it to work? I have a MT4G with 2.2.1 and HBOOT -0.86.0000.
I have run visionary r14 and run the su commands outlined in the procedure and the root.sh script runs fine and when I power down and reboot into hboot, I keep getting s=on??
I have rooted a couple of MT4G phones in the past and I am stumped. I have tried running visionary 3 times then running the su commands and root.sh script and still get s=off.
Any help would be greatly appreciated please. I almost at the point of tossing it in the toilet.

Have you rebooted and then run visionary again to gain temp root and then ran visionary to gain perm root?? Once you do temp root in visionary, go into terminal and run the root.sh command and reboot, it was only temp rooted so you have to run temp root and then perm root in visionary again and it should stick...

I have tried the following procedures with no success:
Run visionary r14 to get temp root
Goto terminal and run change directory commands to run root.sh script
Script runs fine and tells me to power down and check for s=off
I power down and boot into HBOOT S=ON
Phase two:
Run visionary r14 to get temp root
Run root.sh script in terminal
Run visionary r14 and run get perm root
Visonary tells me superuser was granted, screen goes black and reboots
I run terminal and try su command and "access denied"
I try and boot into hboot and S=ON
Phase Three:
Run visonary r14 to get temp root
Run root.sh script in terminal, tells me to reboot into hboot and check for s=off
I reboot
I run visionary again to get temp root
I run visonary again to get prem root, visionary runs and phone reboots
I run terminal and try su command "access denied"
At this point I am fustrated, I have rooted a couple of MT4G phones in the past and never had this hassle before.
I have followed the procedures to the letter, double check the files I downloaded, What am I doing wrong?

http://forum.xda-developers.com/showthread.php?t=858996
try this one....worked for me on hboot 0.86.0000

Are you checking "set system r/w after root?"
Is usb debugging enabled?
Is fast boot disabled under apps settings?
If you're doing everything right and it fails, use the gfree method linked in the post above mine.

This might help you out its what i did and im on hboot 86,
Follow that gfree method, and afterwards go into visionary r14 and go for a temproot And then a permaroot and your phone should reboot and you should be good... I did this because even with s=off i still had permission issues.

Same issue, with HBoot 86. So going through the gfree method is the only way to obtain S-Off then?
I thought I was losing my mind, using the tried-and-true Visionary+ and Terminal route. I tried it seven times: "S-ON"...
Thanks for the tips. Please update this thread with any new info.

Hboot 0.86.0000 has nothing to do with it. All MT4Gs ship with this bootloader. You get Hboot 0.85.2007 either by flashing manually (as per the instructions in the gfree thread) or if you used the root.sh script (such as by following theunlockr.com's video walkthrough).
If VISIONary is giving you temproot, you should be able to do either the gfree script or the root.sh script (your choice, I say use gfree), and then you can permroot with VISIONary. If that's not working, wither you haven't followed the directions properly or something else is interfering, in which case more information is needed to help you.

The gfree way is the way to go. With the walk through under the development thread, it is pretty much dummy proof. I just rooted my buddy and his wifes phone last night using that method.

Related

[Q] G2 Lost S-OFF after hboot update?

First I want to thank all from this site for all the work you've done!
OK, got a G2 few days ago rooted it using rage method, updated radio to 26.04.02.17 (read that solved some problems with cyanogen's 6.1.1 ROM), installed 6.1.1 ROM and all was well... Then I decided to upgrade hboot (for no particular reason) to 0.85.005 with fastboot. After install it rebooted and noticed I now have SHIP S-ON ...and it wouldn't boot..got stuck on HTC splash screen. So I say oops...pull battery and go into recovery and do a restore to a rooted stock ROM. Was successful but was hoping it would give me root back but no joy. Then tried to install 6.1.1 from ROM manager but no joy. (no surprise with S_ON) So I'm wondering:
Why did hboot update change it to S-ON?
Why didn't my restore restore S_OFF? ( thought restore re-wrote everything)
AND..where do I go from here? Should I just use rage again to get root?
Any help would be greatly appreciated!!
Again, thanks to all!!
Edit: OK just realized I still have root access threw terminal emulator???
How can this be with S-ON??
So I guess I still have root so I tried to install cyogen 6.1.1 from sd card using revovery.
all seems to go well, says its complete but when I reboot, it gets stuck on HTC splash screen
Also tried gfree and this method http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
got to 2nd to last command:
# /data/local/tmp/root
and get
# mkdir failed for /system/xbin, file exists
Anyone??
That sounds like the stock *DZ* hboot, not the G2 one. If so, you're lucky you didn't brick your phone. I wouldn't switch hboots between DZ/G2 unless you were flashing the whole ROM.
The fact that it's a stock one explains why you have S-ON, if you only had S-OFF via the eng hboot before.
What you need to do is run gfree, as you say, to get proper radio S-OFF.
S-ON/S-OFF has nothing to do with root. So you can still be S-ON and have root.
If you did a nandroid restore through Clockwork then as far as I'm aware that doesn't include a restore/backup of hboot.
You won't be able to flash another custom ROM/recovery until you get S-OFF back again.
That "mkdir" error message is normal, just ignore it. But gfree doesn't work with CM 6.1.1. It will work on 6.1 but there are some incompatible kernels too.
I suggest installing the eng hboot (the correct one for your phone, see the Wiki) to get S-OFF (but be careful doing this, e.g the checksums). Then revert to a ROM that is compatible with gfree and run gfree to get radio S-OFF. Then you can revert back to 6.1.1 or whatever you want.
steviewevie said:
That sounds like the stock *DZ* hboot, not the G2 one. If so, you're lucky you didn't brick your phone. I wouldn't switch hboots between DZ/G2 unless you were flashing the whole ROM.
The fact that it's a stock one explains why you have S-ON, if you only had S-OFF via the eng hboot before.
What you need to do is run gfree, as you say, to get proper radio S-OFF.
S-ON/S-OFF has nothing to do with root. So you can still be S-ON and have root.
If you did a nandroid restore through Clockwork then as far as I'm aware that doesn't include a restore/backup of hboot.
You won't be able to flash another custom ROM/recovery until you get S-OFF back again.
That "mkdir" error message is normal, just ignore it. But gfree doesn't work with CM 6.1.1. It will work on 6.1 but there are some incompatible kernels too.
I suggest installing the eng hboot (the correct one for your phone, see the Wiki) to get S-OFF (but be careful doing this, e.g the checksums). Then revert to a ROM that is compatible with gfree and run gfree to get radio S-OFF. Then you can revert back to 6.1.1 or whatever you want.
Click to expand...
Click to collapse
Thanks for responding! Especially after this post has turned into more of a rambling blog as I learn more.
I tried to run gfree to get s-off and it doesn't work, stays s-on. Thought it was because of the "mkdir" error message I was getting. Then tried to install eng hboot using the whole G2 ROOT INSTRUCTIONS here:
http://forum.xda-developers.com/showthread.php?t=834228
Everything goes smooth except for the"mkdir failed for /system/xbin. file exists"
When I reboot, still have:
VISION PVT SHIP S-ON
hboot-0.85.0005
Any ideas??
Again thanks for any help and suggestions!
Just noticed the first commands in the G2 ROOT INSTRUCTIONS have a "$" sigh ie: "$ adb push su /sdcard/su"
Does this mean you should run "adb shell" first? If that.s the case, I get "adb: permission denied" although I do see su on sdcard.
(I know I'm really grasping here )
No, you don't run "adb shell" before running those adb commands, because "adb shell" will give you a command prompt on your phone, and those adb push commands need running from your PC's command prompt. That "$" prompt shown in the guide can be confusing, because it's being run from a PC running Linux, which has a $ prompt. If you have Windows then you will have some sort of "C:\" prompt.
If you are only installing the eng hboot though, you don't need to do all that, since you already have root. Skip to the "Perm Root" section in that guide that you linked, and do everything up to and including the "dd" command. Then the sync and reboot bit (skip over the "root" script).
Although check what message you get from the insmod command. We might have a problem here, because if you're on CM 6.1.1 (that's what you're on, right ?) then gfree won't work and I don't know if either of those wpthis modules (OTA and pre-OTA) will work properly on CM 6.1.1.
The insmod is crucial because unless that command gives you the "right" error message as shown in the procedure, it won't disable the NAND write protection and so won't let you write the hboot permanently.
A bit offtopic, but maybe someone will find this helpful: in many tutorials for *NIX (Linux, OSX, BSD etc.) users you'll find that what you need to type in a command prompt (terminal) starts with either $ or #.
While that may be confusing for Windows users, it is a hint as to whether you are supposed to run the commands as a simple user (the prompt shows a $) or as the administrator (or root) user (in which case, the prompt shows a #).
steviewevie said:
No, you don't run "adb shell" before running those adb commands, because "adb shell" will give you a command prompt on your phone, and those adb push commands need running from your PC's command prompt. That "$" prompt shown in the guide can be confusing, because it's being run from a PC running Linux, which has a $ prompt. If you have Windows then you will have some sort of "C:\" prompt.
If you are only installing the eng hboot though, you don't need to do all that, since you already have root. Skip to the "Perm Root" section in that guide that you linked, and do everything up to and including the "dd" command. Then the sync and reboot bit (skip over the "root" script).
Although check what message you get from the insmod command. We might have a problem here, because if you're on CM 6.1.1 (that's what you're on, right ?) then gfree won't work and I don't know if either of those wpthis modules (OTA and pre-OTA) will work properly on CM 6.1.1.
The insmod is crucial because unless that command gives you the "right" error message as shown in the procedure, it won't disable the NAND write protection and so won't let you write the hboot permanently.
Click to expand...
Click to collapse
ahhhh..thanx for clarifying "$" issue for me.
I am NOT on CM 6.1.1
I have stock OTA rom right now (with root), sorry for the misunderstanding
OK,this is exact error message I get:
insmod: init_module '/data/local/wpthis-OTA.ko' failed (function not implemented)
After I run dd=..... I get
2048+0 records in
2048+0records out
1048576 bytes transferred in 0.079 secs (13273113bytes/sec)
So all looks perfect to me, but I still get stuck with:
....S-ON
hboot-0.85.0005
does the "insmod" being in error message mean anything?
In any event, at least I still have a working phone and learned alot more
(like you said..I'm very lucky I didn't brick it flashing this hboot update)
That's the "correct" error message from insmod. But weird stuff is going on here, which isn't too suprising if you have the wrong hboot for your phone.
I'm getting confused, I thought you were on CM 6.1.1. I also thought your phone was stuck in a boot loop, but you seem to be able to still run commands as root, so presumly it boots ok now ?
steviewevie said:
That's the "correct" error message from insmod. But weird stuff is going on here, which isn't too suprising if you have the wrong hboot for your phone.
I'm getting confused, I thought you were on CM 6.1.1. I also thought your phone was stuck in a boot loop, but you seem to be able to still run commands as root, so presumly it boots ok now ?
Click to expand...
Click to collapse
Sorry for the misunderstanding, I had CM 6.1.1 on when I flashed wrong hboot. After that it would get stuck on HTC screen when trying to boot up into CM 6.1.1
So I booted into recovery and did a restore which luckily worked. Which now I have no idea why that worked looking back other than because it was a legit stock ROM, so it allowed it. Is this the case??
Last night I actually tried to un-root and get everything back to stock (including hboot) via this method:
ttp://theunlockr.com/2010/12/01/how-to-unroot-the-t-mobile-g2-htc-vision/
but got stuck on "dd if=/sdcard
/miscnew.img of=/dev/block/mmcblk0p17" with a read only ermision denied message
which I wasn't surprised because I have S=ON

[Q] 1.34 rooted and S-off.. Need to go back. How ?

So i've rooted my Desire Z with the stock rom of v. 1.34 .. I think i need to send it back for repairs since my green led is not working anymore.. But before i can do that i want to unroot the phone.. can someone here explain to me how i do it ? Im a total retard when it comes to this.. Sometimes i even wonder how the heck i managed to root the device
EDIT: Forgot to mention that i've applied a OC kernel.. !
No one ?
5char
I reckon ppl are a bit cautious in giving advice as there have been a few issues.
Lets start with which method did you use to root and s-off?
wileykat said:
I reckon ppl are a bit cautious in giving advice as there have been a few issues.
Lets start with which method did you use to root and s-off?
Click to expand...
Click to collapse
Thanks man.. Glad you want to help ..
I wanted to able to use this kernel, so i followed the suggested rooting guide from that thread.. Which i believe is this
I just want to make sure i do everything right you know
Da9L said:
So i've rooted my Desire Z with the stock rom of v. 1.34 .. I think i need to send it back for repairs since my green led is not working anymore.. But before i can do that i want to unroot the phone.. can someone here explain to me how i do it ? Im a total retard when it comes to this.. Sometimes i even wonder how the heck i managed to root the device
EDIT: Forgot to mention that i've applied a OC kernel.. !
Click to expand...
Click to collapse
Hi !
I need to know 2 things before I can help you:
1. Did you install the engineering hboot?
You can check this by booting into fastboot mode:
- Shutdown the phone
- Press and hold the touchpad-button and hold it while pressing the Power button.
-> On the screen with the surfing androids the first lines contains either SHIP or ENG. If you have ENG then you installed the engineering hboot.
2. Did you use gfree to achive radio S-OFF
You can check this by using the gfree_verify procedure - see http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#VERIFY_.28using_.22gfree_verify.22.29
if you have @secu_flag = 0 then you are radio S-OFF if @secu_flag = 1 you are radio S-ON.
Please check this and post your results, then i can post your way to go.
have fun - Guhl
guhl99 said:
Hi !
I need to know 2 things before I can help you:
1. Did you install the engineering hboot?
You can check this by booting into fastboot mode:
- Shutdown the phone
- Press and hold the touchpad-button and hold it while pressing the Power button.
-> On the screen with the surfing androids the first lines contains either SHIP or ENG. If you have ENG then you installed the engineering hboot.
2. Did you use gfree to achive radio S-OFF
You can check this by using the gfree_verify procedure - see http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#VERIFY_.28using_.22gfree_verify.22.29
if you have @secu_flag = 0 then you are radio S-OFF if @secu_flag = 1 you are radio S-ON.
Please check this and post your results, then i can post your way to go.
have fun - Guhl
Click to expand...
Click to collapse
1. Nope it shows SHIP
2. Gave me this output (My phone has allways been sim unlocked however.. Bought it without contract!)
Code:
gfree verify_cid returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
Da9L said:
1. Nope it shows SHIP
2. Gave me this output :...
gfree verify_secu_flag returned:
@secu_flag: 0
Click to expand...
Click to collapse
!!! WARNING FOR OTHERS - DO NOT DO THIS IF YOU ARE NOT RADIO S-OFF AND HAVE THE ENGINEERING HBOOT INSTALLED !!!
OK this is good because as you don't have the eng-hboot installed we can safely flash the full stock rom and i assume that you have a custom kernel and a custom recovery installed that we need to get rid off.
Before i go into details of commands i would like to give you the principle procedure:
1. reinstall the stock firmware by copying a PC10IMG.zip to /sdcard and then boot into hboot and let it install the complete stock rom.
2. temproot again using psneuter
3. restore the backup of your partition 7 using gfree 0.4
So what we need is:
- a stock rom from here http://www.multiupload.com/GH26HXLLES
- psneuter from here http://www.thinkthinkdo.com/trac/project1/raw-attachment/wiki/psneuter/psneuter.zip
- gfree 0.4 from here http://www.thinkthinkdo.com/trac/project1/raw-attachment/wiki/gfree/gfree_04.zip
You need to make sure that this PC10IMG.zip really is your stock version (maybe find yours somewhere else)
1. Installing the stock rom:
connect the phone to usb.
download the file and rename it to PC10IMG.zip and put it to the root of your sdcard using:
Code:
adb push PCIMG10.zip /sdcard/
shutdown your phone.
boot into hboot by holding the <Vol-Down> key while you press <Power> to boot.
hboot (white screen with surfing androids and the word HBOOT in blue) will scan for the file PCIMG10.img and load it.
Then you can use <Vol-Up> to start the process. In the middle of the process the screen will get dark for some seconds and then it will start again -> don't panic wait until it is completely finished.
When done - reboot
2. Temp-root using psneuter:
On the phone go to Settings - Applications - Development and enable USB debugging again.
Unzip the psneuter.zip, install and execute psneuter on your phone:
Code:
adb push psneuter /data/local/
adb shell chmod 777 /data/local/psneuter
adb shell /data/local/psneuter
3. use gfree to restore your partition 7 backup
Unzip gfree_04.zip and install it on the phone
Code:
adb push gfree /data/local/
adb shell chmod 777 /data/local/gfree
3.a When you used gfree to get radio s-off it created a backup of the partition named /sdcard/part7backup-<time>.bin (replace <time> with the time number). We will restore this file now.
Get a root shell:
Code:
adb shell
The prompt should be # now
Execute gfree to restore the backup (in the root shell) - replace <time> with your time number in the following command.
Code:
/data/local/gfree -r /sdcard/part7backup-<time>.bin
3.b Alternative: (if you don't have your partition 7 backup anymore - don't do if you did 3.a):
You need to know the CID that your phone had originaly, it could be HTC__001
Excecute gfree to set S-ON and CID:
Code:
/data/local/gfree -s on -c HTC__001
4. clean up (still in the root shell):
Code:
rm /data/local/psneuter
rm /data/local/gfree
rm /sdcard/PC10IMG.zip
So now you are back to stock.
You might want to boot to hboot again and use "FACTORY RESET" to wipe data and cache.
And you might format the micro-sd card before you return the phone.
I hope this is it (written without a phone so there might be typos)
have fun - Guhl
Wow guhl99 that is really really helpfull ! I appriciate it so much! Im gonna try it later today ..
However i dont think i got the backup of that partition.. Must have deleted by mistake for some reason
Is there anyway i can find out what CID my phone had originaly ?
EDIT: Another question.. What would happen if i just acceptet the OTA upgrade ? Wouldn't that unroot and s-on my phone ?
Da9L said:
Wow guhl99 that is really really helpfull ! I appriciate it so much! Im gonna try it later today ..
However i dont think i got the backup of that partition.. Must have deleted by mistake for some reason
Is there anyway i can find out what CID my phone had originaly ?
Click to expand...
Click to collapse
Hi !
Welcome, i think it was time to summarize this once. And as I am constantly going back to stock to test some exploits and then reroot i have some practive.
Yes there is. The CID is also stored in the first 8 bytes of partition 17 - the misc partition - (and no one knows why).
So you can to the following (in a adb root shell)
Code:
dd if=/dev/block/mmcblk0p17 bs=8 count=1 2>/dev/null
The first 8 characters of the output should be your CID (the # behind it is the prompt for the next command as you do not receive a new-line by the command above)
have fun - Guhl
Da9L said:
EDIT: Another question.. What would happen if i just acceptet the OTA upgrade ? Wouldn't that unroot and s-on my phone ?
Click to expand...
Click to collapse
Sorry I did not see this question.
It will unroot but will NOT S-ON the phone.
But something really nasty will happen:
- It will install a radio firmware version that prevents gfree from dropping the write protection of the emmc chip for the radio configuration partition 7. And because of this you are not able to set S-ON again or set your CID back (or restore your partition 7 backup).
You would then have to downgrade the firmware again to 1.34 (using a procedure that is documented in this forum) and is even more complicated. And after the downgrade (that includes installing the stock rom as i described above) you would have to continue at point 2 of my description above.
SO DO NOT ACCEPT THE OTA (it would not brick things but needs another 2 steps).
have fun - Guhl
Guhl, could you use Gfree to restore your backup (or go S-ON) first while you were still rooted? Then with S-ON, use the PC10IMG.zip to restore back to the shipping ROM (which should work, assuming the zip to be signed).
Just wondering if that extra step of temp rooting before using gfree is necessary...
ianmcquinn said:
Guhl, could you use Gfree to restore your backup (or go S-ON) first while you were still rooted? Then with S-ON, use the PC10IMG.zip to restore back to the shipping ROM (which should work, assuming the zip to be signed).
Just wondering if that extra step of temp rooting before using gfree is necessary...
Click to expand...
Click to collapse
Hi !
You are absolutely right, you could do it this way.
The reason why i always remove s-on as the last step is just to have the system and recovery partitions write enabled till the last step.
So if anything goes wrong you still have options till the end.
But if you don't need that extra security you could do it your way.
have fun - Guhl

[Q] Unroot guide???

http://www.youtube.com/watch?v=eHrtVzlsA_s
i followed this guys video tutorial to rooting my device. so please confirm if its the 'ultimate rooting' method or watever cus im so confused ever since the original s=off forums been modded with the new gfree root/unroot method.
i used visionary and the terminal emulator plus that whole blue screen 'su' thingy to root.
how do i come about UNROOTING from using this guys rooting method????
help
msyang20 said:
http://www.youtube.com/watch?v=eHrtVzlsA_s
i followed this guys video tutorial to rooting my device. so please confirm if its the 'ultimate rooting' method or watever cus im so confused ever since the original s=off forums been modded with the new gfree root/unroot method.
i used visionary and the terminal emulator plus that whole blue screen 'su' thingy to root.
how do i come about UNROOTING from using this guys rooting method????
help
Click to expand...
Click to collapse
I actually just unrooted my phone yesterday to send it in.
I used the same method and all you need is the PD15IMG file to unroot.
Save it to the root of your SD Card.
Power off your phone. Hold Volume Down + Power and let it install the file.
Done!
http://www.mediafire.com/?12oi5elu7v2y8og
Download it, the make sure you have superuser, vishionary and terminal installed.
In terminal:
1. Open up terminal editor on your device.(I prefer this method b/c you can see the output.)
a. Type "su" + enter to gain root privileges.
b. Type "cd /sdcard/unroot" + enter.
c. Type "sh unroot.sh" + enter.
Restart into recovery and make sure it says s=off, then restart and go into vishionary and click unroot. This is what I did. Took 2 minutes.
darksulfur5 said:
http://www.mediafire.com/?12oi5elu7v2y8og
Download it, the make sure you have superuser, vishionary and terminal installed.
In terminal:
1. Open up terminal editor on your device.(I prefer this method b/c you can see the output.)
a. Type "su" + enter to gain root privileges.
b. Type "cd /sdcard/unroot" + enter.
c. Type "sh unroot.sh" + enter.
Restart into recovery and make sure it says s=off, then restart and go into vishionary and click unroot. This is what I did. Took 2 minutes.
Click to expand...
Click to collapse
Will this work if I rooted using gfree method? I did the unlocker unroot method but when I checked it still said s-off.
darksulfur5 said:
http://www.mediafire.com/?12oi5elu7v2y8og
Download it, the make sure you have superuser, vishionary and terminal installed.
In terminal:
1. Open up terminal editor on your device.(I prefer this method b/c you can see the output.)
a. Type "su" + enter to gain root privileges.
b. Type "cd /sdcard/unroot" + enter.
c. Type "sh unroot.sh" + enter.
Restart into recovery and make sure it says s=off, then restart and go into vishionary and click unroot. This is what I did. Took 2 minutes.
Click to expand...
Click to collapse
el-jodio said:
Will this work if I rooted using gfree method? I did the unlocker unroot method but when I checked it still said s-off.
Click to expand...
Click to collapse
Being that that file is only ~200kb, this will only work if you used the root.sh script, AND you NEED to be on a near stock MySense ROM..Now i will say there is one of those files floating around that contains a script to download and put the PD15IMG in the correct place reboot the phone into HBoot and flash the PD15IMG.
If you did the ./gfree method you have to reverse the ./gfree which can be found the the ultimate guide in the development section.

S=ON but still can't stock unroot

hi i recently rooted my mytouch4g but know i want it back to stock OFTB
s=on in hboot but the pd15img.zip said no image
i have repeat tons of time but nothing
root phone by:
visonary temp root then i did perm root gfree for s=off steps was
gfree moving files to data/local/ with root explorer
then i did the commands for gfree and s=off
now thats what i did for root s=off
CWM = 3.0.0.5
now am running ice glacier (newest)
i did the unroot Automated way to unroot your myTouch 4G (difficulty level 1) method by jjjackson56 and got s=on
1. To use this simply download the zip and extract the two items to the root of your sdcard (ones a folder and ones the PD15IMG)
2. Open terminal and type
su (press enter)
cd /sdcard/unroot (press enter)
sh unroot.sh (press enter
3. Let it work.
after it did its thing and try to reboot itself it couldn't said that reboot: no such tool
so i reboot myself to hboot by vol+power
but the phone doesn't flash hboot did not find it said no image and i have the pd15img in my sdcard root
can anybody help
Can you verify that your PD15IMG is named exactly "PD15IMG.zip" and not "PD15IMG.zip.zip" or something similar? If it is, possibly try a different sdcard if hboot still won't detect the file.
Yes the file name is correct no double zip and I trade with a different card didn't work
What error are you getting in hboot? Does it display the messages of searching for an image then that it can't find one, or what?
Be sure that the file is on the root of the card, and not in another folder.
Yes its on the root of my sdcard not in any folder just like glacier Rom am using right now and when it search in hoot it says no image to all 4 search
is it my hboot version is 86
ok i found the problem i know its noob
but for noobs make sure u make sure your sdcard is fat32 format
or it will not work THX BYE!

[Q] my MT4G already Ship S-OFF how to root, thanks

my MT4G already Ship S-OFF how to root, here is my HBOOT information, thanks
GLACIER PVT SHIP S-OFF
HBOOT-0.86.0000
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Sep 27 2010, 11:12:59
Before you start, read through the forums and LEARN before you attempt to flash any device.
I am not responsible for your bricked phone or the ignorance that may or may not have caused it based on the fact that you CHOSE to follow these steps.
Follow these steps carefully
1. Make sure fastboot is turned off and USB Debugging is on.
2. Download Terminal and Astro off the market. Download Visionary r14 here.
3. Temp root using Visionary, make sure "set system r/w after root' is checked before you root.
4. Download the necessary root.rar file from here onto your pc.
5. Place the files on your phones SD Card in the root directory
6. Open up terminal, type in "su" then press enter. Then without exiting type in "insmod /sdcard/wpx.ko" and press enter. If you got the proper message type in "dd if=/sdcard/hboot_dhd.nb0 of=/dev/block/mmcblk0p18". Do not exit terminal in this step at all.
7. If it works press the back button to exit terminal.
8. Run visionary again, should say you're already rooted.
9. Wait 5-15 seconds then pull the battery out.
10. Reboot then run Visionary again.
11. Pull the battery, wait about 2 minutes. Boot into recovery by holding both the power on and volumn down buttons until it comes off.
If it says S-OFF, you're rooted! Good job!
Both the videos below are based on visionary, if one method failed, the other will work for you.
Or... significantly fewer steps:
Consult this thread:
http://forum.xda-developers.com/showthread.php?t=1200147
From S-OFF you may be able to flash the following unsigned PD15IMG.zip:
http://www.megaupload.com/?d=Y2A16P54
Then you can boot your phone into Clockwork Recovery, and install the Superuser zip:
http://forum.xda-developers.com/showthread.php?t=682828
Use this file: su-2.3.6.1-ef-signed.zip
And there you go, since you already have S-OFF.... root!

Categories

Resources