Database Users

[SOLVED] How to Delete System Apps after Loosing Root Access From 1.72.405.3 ROM

Ok so after much lots of frustration realising I'd lost access to the delete system apps after installing HTC 1.72.405.3 (in LeeDrOiD 1.3) I've finally figured out a way to do it and without needing to use ROM Cleaner then re-flash a ROM wich would remove all my data/apps/ect I've loaded. Now this may well be a guide for you guys like me who are very new to Unix commands and the whole Android system. I hope that it helps someone coz honestly the last couple of days I've searched high and low and haven't gotten any answers that worked until I worked it out tonight.
Just as a quick note I was able to delete apps from the /system/app folder before this update when I was still on 1.32.405.6 using Visionary+ in loading R/W access to the system folder on boot and a simple file manager like Astro or AndroZip to delete. Since updating to 1.72.405.3 without Radio S-Off I've tried the following methods and found they don't work:
- Flashing rmk40's Super User/Root patch for 1.72.405.3 as in this thread http://forum.xda-developers.com/showthread.php?t=886999
- Visionary+ selecting R/W system access then using a file manager like Astro or AndroZip to delete.
- Terminal Emulator after getting "supposed" super user access after typing su then going to the /system/data folder and typing rm Facebook.apk ect... also using the other unix commands to try and change the system apps from read only to writable still no access.
- Using Root Explorer which is granted "supposed" super user access does not want to mount as R/W the system/app folder and of course then won't let me delete the apps.
- One click Radio S-Off doens't work as obviously I'm already locked out as I've loaded 1.72.405.3 (LeeDrOiD 1.3) before running Radio S-Off.
- Re-flashing to a previous 1.32.405 ROM then trying to run Radio S-Off followed by all the steps above. Nope nuthin...
Okay and here is is here's how it's done. I had to have the Android SDK installed with USB drivers (HTC Sync has the USB Drivers). I then in windows I opened up command prompt and using the good old DOS commands like "cd\program files (x64)" I go to my android sdk folder platform-tools. Once in the platform-tools let the foreign Unix commands begin
Without the exclamation marks type I type "adb remount shell"
Then "adb shell rm /system/app/Facebook.apk"
Now Facebook.apk being an example of the app you want to delete. I use a file browser such as Astro on my phone to go the the /system/app folder and easily look around and get the file names of the apps I want to delete. An important thing to remember for all the other's unfamiliar with Unix commands like myself, this ain't DOS. Unlike DOS, files and commands are case sensitive so if you try to delete the Facebook app and type it in "facebook.apk" all lower case it won't delete. Make note of any letters uppercase or lowercase in the folder name and file and type it in correctly in the Unix commands or they won't work.
The other two important things to note before you go on a Spring cleaning, delete frenzy (like I will be after I finish typing this up ) is: 1) If you delete some certain system apps (for example TelephonyProvider.apk) Android will **** itself and after booting enter a loop where you can't access anything & you can't stop it complaining about blah blah app failed. So make sure you have on your microSD card either a Nandroid backup done recently using the Backp/Restore function under the Bootloader installed with Clockwork Recovery or a working ROM that you've tried and know works such as the stock ROM or a custom ROM from LeeDrOiD, Cyanogen, ect. If you get into one of those non recoverable loops you'll need to flash the ROM and of course loose any data and apps not backed up. Okay this brings me to my next point. 2) If you want to copy any of the system apps off to your microSD card either to backup or just if you're not 100% sure if you may want to install it again later then in command prompt type this:
"adb shell cp /system/app/Calculator.apk /sdcard/"
Obviously here Calculator.apk is the app we are copying but you can choose any app to copy. Also /sdcard/ means it will go to the root folder of your MicroSD card.
Stick it to tha man and have fun cleaning up your ROM and deleting all that crap bloatware your service provider and HTC don't wanna give you access to and now without the cripple of HTC update 1.72.405.3 stopping you!

Are these persistent changes? If so I think you will be the saviour of many on here!

Are you sure the apps are not back when you reboot your phone?

I'd be pretty surprised if they're persistent.

sorry i can't see how this has worked. unless by some weird chance when trying to get s-off, gain root and what esle you have try to do. has caused you to be able to r/w to the system partition.

cattleprod sorry i can't see how this has worked. unless by some weird chance when trying to get s-off, gain root and what esle you have try to do. has caused you to be able to r/w to the system partition.
Click to expand...
Click to collapse
Ok I assure you it has worked and continues to work. One possible major difference I've just been told supposedly the stock HTC RUU 1.72.405.3 reverts you back to original hboot eng s-on. Me on the other hand I never loaded a stock HTC ROM 1.72.405.3 or an update. I loaded LeeDroiD 1.3 which has in it the base as 1.72.405.3 but also his modifications to that. So never lost clockwork recovery hboot. I can still load ROMs fine, I just lost functionallity from Visionary+ or anything else for that matter on the phone to access System folder R/W access. Using ADB on my PC as described above however did solve this. Unfortunately the other issue is after loading LeeDroid 1.3 it's permanently done something to my phone and even after flashing back to previous stock 1.32ROM the 1click Radio S-Off patch does absolutely nothing. Luckily Vodafone supposedly offers a free SIM unlock and there are also cheap alternatives on ebay.
dr.m0x I'd be pretty surprised if they're persistent.
Click to expand...
Click to collapse
Eddie1506 Are you sure the apps are not back when you reboot your phone?
Click to expand...
Click to collapse
andyharney Are these persistent changes? If so I think you will be the saviour of many on here!
Click to expand...
Click to collapse
Yes guys these are all persistant. I've rebooted quite a few times and none of the apps I've deleted have come back. These are the apps I've deleted from the "/system/app" folder and they 4 sure have not come back to annoy me: Facebook (crackbook as I like to say ), Twitter & Flickr including any widgets of the same name, stock or shares trading apps, default internet browser (replaced it with Dolphin HD), Flashlight (replaced it with moddified HTC one that says "torch" as I'm not a fan of US English), HTC Likes, HTC coin, probably some others I can't remember now.
So anyway go for it just use your clockwork recovery (modified hboot) to do a full backup first as if you remove the wrong system apps it goes in a non working error loop.
I'm only real new to the whole Android thing. Only had the phone 4 bout 2 weeks and never hit up any Unix commands before then. I'm happy to help out if I can though. Just message me and when I'm on next I'll try to help.

[RESOLVED] Stubborn security on MT4G. Will not Temp-Root.

I was able to root my MT4G with ease using VisionARY r14. My friend purchased a MT4G shortly after and I was trying to root it for him, I used several methods and no luck on any of them.
I've tried using:
1. Visionary temp root>attempt perm root
2. Visionary temp root>terminal (sh root.sh)
3. Visionary temp root>terminal (/data/local/wpx.ko)
From what I understand #2 & #3 basically are the same. So going back to the problem, on MY phone (I don't recall if I used #1 or #2), I rooted with no issues. On his phone, the root is not sticking, every time I go into the bootloader on his S=on still. Nothing stands out or is out of the ordinary, and I would think it would have rooted just fine, the scripts ran via terminal emu and looked okay and all.
Something else I've noticed is when I install CWM Recovery via ROM Manager, after temp root from Visionary the install of CWM Recovery itself was fine, though after going into bootloader and trying to access recovery or booting into recovery from ROM Manager, it doesn't go into recovery, I get the cell with red triangle and "!" on it. I'm assuming that this is a result of it being unrooted still? Anyone else run into a stubborn MT4G like this? I've attached 2 pictures for visual aid of the phone's bootloader screen and about screen below.
Any suggestions or help is greatly appreciated, I've been trying to root it for over a week now and no luck.

I can't see the pics you posted, but I had this issue myself, for me the answer was to find a stock recovery pre ota update and force it, then I ran visionary and terminal with sh root.sh or whatever... Hope this helps... Just try to find an image of pre ota stock rom and go from there... There is a good forum here with a walkthrough to do this... Post results please, would like to know if this was your issue...
Sent from my HTC Glacier using XDA App

Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App

grankin01 said:
Ok guys, first of all Scotty2 gets all the credit for the program R&D. I used my device as a test bed and have tried a couple different kernels (Gr8Gorilla's O/C Kernel and the stock kernel).
Now for the boring stuff ...
This is a very invasive way of rooting your device but the benefit is TRUE S=Off and root privileges throughout the system. As such, you do this at your own risk and if you brick your device neither Scotty2 nor myself are responsible, YOU ARE!!! Do this at your own risk!!!
This is not for the faint of heart and if you have any reservations about doing things like this do not do it.
This process will do three things for your device. I will explain them here:
1. It will set up Super CID on your device allowing you to flash any carriers rom (not just tmobile). Giving you more freedom with your choice of software. The software still needs to be device specific to the glacier for compatability reasons though. Like vodafone glacier roms etc.
2. It will subsidy unlock your device. In other words, it will SIMUNLOCK your phone allowing you to use an AT&T sim card and so on in your device without needing the unlock code from HTC.
3. Most important of all it will turn the RADIO S=Off. This is the ultimate S=Off because the radio is what controls the security flag in the first place. Once you turn it off here it is off everywhere and will allow you pure unadulterated access to your device.
This process will not change your bootloader (unless your on 0.86.0000 and you follow the optional steps).
Now, you may be asking "Why do this? I already have root from your other guide and it has given me r/w access to system and recovery. I thought this meant we had permanent S=Off." This is only partially true. We have had an engineering bootloader and "Label" s=off not radio s=off. When you turn the security off in radio it is off permanently no matter what hboot you have installed engineering or otherwise. However, it is optional but you can still copy the engineering hboot over and it will allow you to flash whatever you like without (as much) fear of bricking your device.
This guide assumes you know how to use ADB. If you do not there are guides all over XDA to show you how. There is even a really good one in this forum. Also here is a video on how to setup adb discovered by topgun303: http://www.youtube.com/watch?v=1UF5w1dKe2U
*NOTE*
For some reason this process can bork your recovery. If you notice after following the steps below that in order to reboot from recovery you have to uninstall/reinstall the battery and hit the power button, just install/reinstall clockwork recovery through Rom Manager in the android market and it will fix your problem.
CONFIRMED: Guide does work for pre-OTA devices!!! Thanks xanz!
Here we go:
If you are already permarooted per the other guide just follow the first 11 steps.
Make sure you have visionary installed on your device. (If you were already permarooted w/s=off ignore this step.)
Download this file:
http://www.mediafire.com/?s7afymwe2wb3x60 New version of gfree with more options! See below.
md5sum: b73c56ca0e21664c5756d4ad295063c5
1. Now unzip the file into your SDK tools directory.
2. Plug your device into your computer.
3. Now open explorer and hold down shift at same time you right mouse click on your SDK tools directory (platform-tools if you have the R8 version of the SDK). Select open command window here. If you are in linux (ubuntu) right mouse click on your SDK tools folder, choose actions, and choose open command window(or whatever it's called). Otherwise, open a command prompt and cd your way to your SDK tools directory.
4. Type "adb push gfree /data/local" and hit enter.
Optionally, you could dl the file to your phone use androzip or something like it to unzip the file and then use root explorer to move the file named gfree to /data/local. Not the gfree.h file. All the other files are source code inlcuded for the gnu license. This would skip the first 4 steps.
5. Now unplug your device from the computer.
6. Run visionary to gain temp root. (If you were already permarooted w/s=off ignore this step.)
7. Open terminal emulator on your device, type "su", and hit enter to gain root privileges.
8. Type "cd /data/local" and hit enter.
9. Now type "chmod 777 gfree" and hit enter to make the program executable.
10. Type "./gfree -f" and hit enter.
New features in gfree.
gfree usage:
gfree [-h|-?|--help] [-v|--version] [-s|--secu_flag on|off]
-h | -? | --help: display this message
-v | --version: display program version
-s | --secu_flag on|off: turn secu_flag on or off
-c | --cid <CID>: set the CID to the 8-char long CID
-S | --sim_unlock: remove the SIMLOCK
With the new features you can turn off one thing at a time. You can also turn security back on and set the CID back to stock if you wish. To turn simlock back on you still have to follow the revert procedures on this page as the information that is patched to turn the lock off is encrypted and we can't write back to it other than restoring the entire image.
So, if you wanted to leave simlock on but turn security off and set super CID the command would be "./gfree --secu_flag off --cid 11111111" + enter. The -f switch after ./gfree that is now in the above step (./gfree -f) just tells gfree to patch everything.
11. Wait for the program to finish and then reboot into HBoot to see if S=Off. Also, check your bootloader version. If it says s=off and has bootloader version 0.86.0000 it worked.
If you already had hboot 0.85.2007 you can check it through the hboot menu. It gives you an option for "system info" in the hboot menu. Highlight it and hit power. It should say CID = 11111111 or something like that. If it does your golden.
Congratulations!
12. If this is the first time you have rooted your device you will need to run visionary again (temproot w/set system r/w after root checked and then attempt permroot) to make root privileges permanent and then reboot again. Now "su" should work properly for you.
Gfree writes a backup of the file that it patches named Part7backup-numbers.bin on your sdcard. I suggest putting this file in a safe place as it is the only way to revert if you need to.
[Optional] Steps to flash engineering bootloader.
1. Restart your phone and plug it back into your computer.
2. Download this file: http://www.megaupload.com/?d=NN5726Z8
md5sum: df4fd77f44993eb05a4732210d2eddc6
3. Copy the file to your SDK tools directory.
4. Open a command prompt again and cd into your SDK tools directoty (platform-tools if your on the new R8 SDK).
5. Type "adb push hboot_dhd.nb0 /data/local" and hit enter.
6. Now open terminal on your device and type "su" and enter to gain root priviliges.
7. Type "cd /data/local" and enter.
8. Now type "dd if=hboot_dhd.nb0 of=/dev/block/mmcblk0p18" and hit enter.
9. You should see something like: 2048 bytes in 2048 bytes out 1048576 bytes copied blah blah blah.
10. Now restart the device into hboot and check if your bootloader version is 0.85.2007. That is what you want to see.
Congratulations, you now have a TRUE root and engineering bootloader on your shiny MT4G!!!
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA Premium App

ZuluNexus said:
Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
I second this, gfree works great

ZuluNexus said:
Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
This would explain why I had to flash the pre ota stock image before I could root using the sh root.sh.... I am sure the chmod777 would have worked also...
Sent from rooted Royal Glacier using XDA app

powduh09 said:
I can't see the pics you posted, but I had this issue myself, for me the answer was to find a stock recovery pre ota update and force it, then I ran visionary and terminal with sh root.sh or whatever... Hope this helps... Just try to find an image of pre ota stock rom and go from there... There is a good forum here with a walkthrough to do this... Post results please, would like to know if this was your issue...
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I see. So just get a pre ota stock rom and Visionary would be the simplest way then? But would the pre ota stock ROM also include the < 86.0000 botloader?
ZuluNexus said:
Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
ZuluNexus said:
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
ziggy34 said:
I second this, gfree works great
Click to expand...
Click to collapse
Thumbs up
powduh09 said:
This would explain why I had to flash the pre ota stock image before I could root using the sh root.sh.... I am sure the chmod777 would have worked also...
Sent from rooted Royal Glacier using XDA app
Click to expand...
Click to collapse
Which method did you use to flash the pre ota image?
And thanks everyone for the quick replies!

When I flahed pre ota I found the forum on here for it. Just placed the file on my sd card and named it PD15IMG and booted phone to hboot, it found update and went from there
Sent from rooted Royal Glacier using XDA app

powduh09 said:
When I flahed pre ota I found the forum on here for it. Just placed the file on my sd card and named it PD15IMG and booted phone to hboot, it found update and went from there
Sent from rooted Royal Glacier using XDA app
Click to expand...
Click to collapse
Awesome, what is hoped for! Thanks!
Sent from my HTC Glacier using XDA App
EDIT!!
RESOLVED!
Unfortunately the method of just using the PD15IMG did not work because the bootloader recognized it as an older image and wouldn't update it. I came across this thread and successfully rooted!! =]
http://forum.xda-developers.com/showthread.php?t=995549
I improvised a bit and did not use "Androzip" I had "Adao File Manager" already installed on my friends phone. Basically.
Credit goes to the OP of the posts!! But here's the link to the gfree the OP is referring to. http://forum.xda-developers.com/showthread.php?t=858996

I am having a problem getting the gfree files to move where they need to be and sry guys, unsure of ow to use sdk, im need the dummy dummy guide anyone? Ive been researching for days lol

Rainbowbright081 said:
I am having a problem getting the gfree files to move where they need to be and sry guys, unsure of ow to use sdk, im need the dummy dummy guide anyone? Ive been researching for days lol
Click to expand...
Click to collapse
You need a root explorer.
*Root can be accomplished without SDK.
Sent from my Glacier running CM7 RC2 via XDA app.

YOu can try using mt4groot.zip google it

I managed to get it done right with adb, s=off perm, running cm7 with honeycomb. Quite awesome!
Sent from my HTC Glacier using XDA Premium App

lilazngoku8 said:
YOu can try using mt4groot.zip google it
Click to expand...
Click to collapse
It's in the second link I posted. Safer than Googling.
Rainbowbright081 said:
I managed to get it done right with adb, s=off perm, running cm7 with honeycomb. Quite awesome!
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Running CM7 with Honeycomb? I am mistaken? You mean the honeycomb theme?
Sent from my Glacier running CM7 RC2 via XDA app.

Sry yes running the honeycomb theme
Sent from my HTC Glacier using XDA Premium App

Rainbowbright081 said:
Sry yes running the honeycomb theme
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Lol cool, I was going to say, 3.0??!! ; )

gordonzhao said:
Awesome, what is hoped for! Thanks!
Sent from my HTC Glacier using XDA App
EDIT!!
RESOLVED!
Unfortunately the method of just using the PD15IMG did not work because the bootloader recognized it as an older image and wouldn't update it. I came across this thread and successfully rooted!! =]
http://forum.xda-developers.com/showthread.php?t=995549
I improvised a bit and did not use "Androzip" I had "Adao File Manager" already installed on my friends phone. Basically.
Credit goes to the OP of the posts!! But here's the link to the gfree the OP is referring to. http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
This is just a laid out variant of the ./gfree method. It'll work but it's been around since the dawn of the Glacier. It's nothing special .

[Q] Gfree problem

Why am I having a problem with something so simple. This is what I have done so far.
I first tried to run gfree from the mexdroid ROM and got the module error, file not found. Realized I need to be on stock so I flashed my stock ROM
My original root was the sh root way and I am on Eng bootloader.
I run through all the steps in terminal, it does its thing and say's done. It create's a part 7 back up. I power off, take the battery out, re-boot in h-boot scroll to system info and the CID is still T-Mobile not 11111111.
I have repeated this 5 times and now have 5 part7 backups " I know the original one" but the CID will not change to 111111. In H-boot if I scroll sim lock it shows mmddcc error but the phone works fine and I am on the latest radio.
What am I doing wrong that the CID will not stick?
Thanks
Edit: I do have the good chip

Use stock PD15IMG.zip and the try it.
http://forum.xda-developers.com/showthread.php?t=1066966
^ I ran in to same problem.
EDIT: Here is my rooting nandroid backup with everything ready to root. So just put download it and extract it and your ready to go as it has gfree/visionary all installed via default with right files everywhere. Make sure once your rooted you go back to whatever rom you have as this rom is only for rooting and you can't do anything on it.
http://www.mediafire.com/?105ueuyj0l14ltj
File: 2011-05-26.07.52.08.ZIP
Total size: 247MB (259,386,782 bytes)
Compressed size: 132MB (139,106,215 bytes)
MD5: 8568314B4998DCAB6646309E0CF8CE3C
Extract point: /SDCard/clockworkmod/backup/2011-05-26.07.52.08/ - DIR
./.android_secure.img
[OBJ-md5:36a87d39856575e5da51db9db2e2119e (2,112 bytes)]
./boot.img
[OBJ-md5:fa48bf8dd44c4c49eb5048d608a0a813 (4,194,304 bytes)]
./cache.img
[OBJ-md5:9b5ad23fd902f20864c91fe10a7d76d9 (23,232 bytes)]
./data.img
[OBJ-md5:14fbc81e859c1cda02f3d5ed4540ea9b (8,640,192 bytes)]
./nandroid.md5
[OBJ-md5:58e98c6065afec65edf5a19f161c2350 (222 bytes)]
./recovery.img
[OBJ-md5:ec577fdd0dd71135b1902a558ac61bec (8,909,824 bytes)]
./system.img
[OBJ-md5:a65858a953447ba16e6d3d89cf371bc3 (237,616,896 bytes)]
Apps:
ASTRO File Manager (v2.5.2)
Android Terminal Emulator (v1.0.29)
Superuser (v2.3.6.1)
VISIONaryPlus (r14)
Misc:
/data/local/gfree
/data/local/hboot_dhd.nb0
/data/local/Root.sh
/data/local/wpx.ko

PD15IMG, I see you had the exact same problem I did. Thank you for sharing your routing Rom for me to try. I did have one question. In your forum post jdkoren responded "You could have just run gfree again with the option --CID 11111111."
Is he suggesting to change "./gfree -f" to "./gfree --CID 11111111." with a space between the CID and 11111111 and a period after the 11111111.?

Coppo said:
PD15IMG, I see you had the exact same problem I did. Thank you for sharing your routing Rom for me to try. I did have one question. In your forum post jdkoren responded "You could have just run gfree again with the option --CID 11111111."
Is he suggesting to change "./gfree -f" to "./gfree --CID 11111111." with a space between the CID and 11111111 and a period after the 11111111.?
Click to expand...
Click to collapse
Well that was period he posted as it was just end of sentence. But if you rip the command apart you will understand it.
./ = child
gfree = call
--CID = condition
11111111 = value
Which is already passed using "-f" condition. Which alone using it by itself didn't work for me as I tested it. So I suggest you download the nandroid backup I provided and then run it from terminal. I use this backup always as I am testing MT4G and I need to root/unroot always.

PD15IMG said:
Well that was period he posted as it was just end of sentence. But if you rip the command apart you will understand it.
./ = child
gfree = call
--CID = condition
11111111 = value
Which is already passed using "-f" condition. Which alone using it by itself didn't work for me as I tested it. So I suggest you download the nandroid backup I provided and then run it from terminal. I use this backup always as I am testing MT4G and I need to root/unroot always.
Click to expand...
Click to collapse
Hmmm it did not work. Here is where i'm at. I DL your ROM and install. Run terminal with the code and get "file not found".
I push Gfree from my computer"and I see it push", run terminal again "file not found"
I copy Gfree to my SD card use Root Explorer to move the files to data/local, run terminal. It runs through the gfree setup and says done.
Re-boot to H-boot and still on T-Mobile. I repeat terminal 2 more times to make sure and still on T-mobile.
Am I doing something wrong?

Well I used that to always root with both gfree and permroot (root.sh) always worked. Also gfree and eng_hboot was already in /data/local as I included it along with VISIONary installed.
Now I am not sure what happened but I suggest you revert back to stock rom/radio with our PD15IMG.zip and then try it. So whatever happened it would be all gone and you would start from new fresh start. Post back if it does not work, at that point it should.

PD15IMG said:
Well I used that to always root with both gfree and permroot (root.sh) always worked. Also gfree and eng_hboot was already in /data/local as I included it along with VISIONary installed.
Now I am not sure what happened but I suggest you revert back to stock rom/radio with our PD15IMG.zip and then try it. So whatever happened it would be all gone and you would start from new fresh start. Post back if it does not work, at that point it should.
Click to expand...
Click to collapse
It did find your file this time but it did not work. Let me go through exactly what I am doing and see if you can find where I may be messing up
Boot into recovery. wipe data/factory reset. Wipe cache. Wipe dalvik.
Go to backup and restore. click restore. click on yours that is dated 5-26-11
Your ROM is now installed. Open up terminal
Type "su"
Type "cd /data/local
Type "chmod 777 gfree"
Type "./gfree -f"
Terminal successfully runs through and says done.
Rebot to H-boot. Click on system info and it's still the t-mob
I repeated 3 times. I now how 10 part7 backups and they are all 2.0MB
Thank you for your help so far, do you have any ideas or see something I am doing wrong?
You mentioned Visionary but I am already S-Off, should I be using that?
EDIT: I re-falshed the stock radio like you said and it WORKED. thank your for your help. Thanks added

I am glad it worked for you. Mostly those issues you won't find work around on the original thread. Maybe when I have time ill look in to Ginger based rooting with Gingerbreak, ect and see if we can find meth for those folks on Panache based roms.

[Q] how can re-root the offical update?

hi.. after following the instructions on how to downgrade my phone, and obtain root, i have, and after i had my foryo rooted, i downloaded RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2 because my original intent was to have a rooted gingerbread and it didn't make much sense to have roms provided by htc itself.
but now i see i don't have root, so oops, i guess i was wrong.
so do i have to go though the whole kaka procedure again, and then find a custom rom, because my end game, is to have as close as possible a rooted gingerbread as close as possible to the original HTC rom. where can i get one?
oh, and what's the difference between the asia and wwe? does any of them handle hebrew bidi writing correctly (without applying the patch?)

I think there is a way to root gingerbread, or you have to downgrade. At either rate, you want to get to a place where you can flash your own ROM. Having clockworkmod installed would be just fine.
Then you would take the stock gingerbread, extract and unzip it, add Superuser and su, make the boot insecure, repack it for flashing, flash via CWM, and presto- rooted stock gingerbread. If you want to build in hebrew bidi writing, you can add that too.
There might be a few rooted stock gingerbread roms out there, but it seems that the trend is toward cooked up versions, rather than stock.

AFAIK i don't there's a way to root gingerbreak, it's un-rootable, that's why i downgraded in the first place. i think i can do it again, question is:
where do i find the stock gingerbread rom? is it in the RUU exe? if so, how get it out from there, without installing it
second, how on earth would i do all the things you said (add su,make boot insecure,repack,flash cwm).
is there a guide out there for all there above?

I think there is a some software for windows that will allow you to extract the rom from the RUU. I don't use windows, so I don't know anything about it. I've seen some posts about it, so I can say it seems to involve using the RUU to almost install the ROM, but at the last minute, just stop and the ROM will be extracted into one of the temp directories. You just use the RUU to extract the rom, not install it.
As far as all those other steps, I think all the information is scattered about xda.
Here's some information about the insecure boot image. It's for the transformer, but it's essentially the same thing, except for the blob parts. You'll have to use something like splitbootimg or bootunpack, and mkbootimg (search for them) instead of blobunpack.
http://forum.xda-developers.com/showthread.php?t=1193737
This might be more helpful:
http://forum.xda-developers.com/showthread.php?t=1100189
As for the other parts, you can use some of the other updates and zip files as a guide to figure out how to unpack, mod them, and repack them. I think there might be a rom kitchen script that will do this too, but I can't speak to that either.
Sorry if this sounds so complex- it's not that bad once you've done it once. I have a rooted stock GB that I made this way from the GB update, but it's the US version. Let me know when you have the WWE version extracted.

ok, let's take it one step at a time, (maybe we'll make a guide out of it
i activated the but i never continued instead i used process explorer to find out which files it's holds, so i got the temp directory and extracted rom.zip a 260 mg file (containing various img files)
now what?
btw is this relavent? http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
yea, i've seen it is, but one issue is that where do i get the cpio and makebootfs, (if i need to compile stuff, this is where i stop, i allready downloaded the perl scripts, as well as GZIP

ok, so far so good.
That link is exactly what you need. You can use that info to unpack the boot.img and make it insecure "ro.secure=0" by editing the default.prop file in the ramdisk.
I think some of the links to the tools might not work, but these will work instead - https://github.com/AndroidRoot/BootTools
Use the guides to mod and then repack the ramdisk
put the kernel and the modded ramdisk back together with makebootimg. There might be some specific command lines and kernel addresses- the hdrboot tool will show you want they should be from the original boot.img
Also, could you upload the zip file or PM me a link? This would be a perfect project for a guide.

ok wait, which tools am i missing? i have a windows machine (ultimate 7 64 bit) and the boottools needs to be compiled, (i don't have developer studio installed just eclipse)
so far i have the following tools:
repack-bootimg.pl
unpack-bootimg.pl
split-bootimg.pl
cpio for windows
gzip
what zip file?
(i'm going to sleep now as i'm in israel,i will "boot" in 6 hrs, luckily i have a vacation tommorow, so i hope we'll have time to finish this.

I think you might need gunzip to extract the ramdisk. unzip might work, but I'm not sure with Windows.
The zip is the rom.zip which has the rom.

I seem to recall there being at least 2 rooted stock ROMs in the dev forum. I think the one I've used was posted by either suilmagic (may be siulmagic), or rmk40. Xboarder56 posted one some time ago, but he started stripping things out that I used, like QuickOffice. If nothing else, this finally drove me to use Titanium backup...
Sent from my HTC Vision using Tapatalk

Yeah, I guess a search would take some of the fun out of it....
http://forum.xda-developers.com/showthread.php?t=1169004

actually i DID google "rooted stock rom desire z"
but i could find anything for sure, that's why i posted this, is this rom appear in the developer list of roms linked in the downgrade wiki? because i couldn't find it there either, would be nice if it was added.

No worries- I didn't actually search for it- I just paged through some of the dev sections.
I think you'll have flash it using CWM recovery.

great, i'm assuming CWM is Clockwork something?

Yup- look for the 3.x version. There was a 5.x, but i think it has some issues.

ok, so now, i must re-downgrade, root,
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
get rom manager, and ah... wait, what's the update.zip? is that actual image i need to place on the sdcard?

That wiki seems kinda old- I don't think the stock recovery will flash the update.zip
This is more up to date and specific for the G2/DZ:
http://forum.xda-developers.com/wiki/HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD

yea i've read that one (that's how i rooted in the first place.
isn't there a way to short ciruit this somehow and instead of pc10img have the update itself installed ? or is it because it's a an OTA, i have to do the whole thing?
looking at the image, i think i'm missing someting it looks like i can somehow use the scripts inside the image when i get temp_root (meaning i won't have to update the original image. am i wrong?

ok i've gone through the motions over and over, finally rooted it, have rom manager, clicked flash recovery, copied the zip file for rom i wanted to the root of sdcard, selected it rom manager, rebooted, now i selected apply update from sdcard,
now i see the hat signal and nothing happens, (i also selected backup rom and wipe cache and data)
i also noticed that i have install zip from sdcard, but i didnt' select it, how long should it take?
ok i FINALLY managed to install (it actually i pressed power button again and immdietly returned the cwm main menu, from then on, i chose reboot, i think it's moved on.
problem is, some things looked odd, for example the phone bar on the buttom, looks distorted, when i click on the application list i can only see half the list (meaning half the screen shows the list although i can scroll up and down the buttom half remains blank..
never mind it's ok now after re-boot..
btw i tried creating a batch file like so:
adb shell cat /dev/msm_rotator
rem expected output
rem /dev/msm_rotator: invalid length
pause
rem temp_root
rem adb push fre3vo /data/local/tmp
rem adb shell chmod 777 /data/local/tmp/fre3vo
rem adb shell /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
echo wait for device to reconnect
pause
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/misc_version -s 1.00.000.0
adb shell sync
adb shell dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
rem expected output is:
rem 1.00.000.010+0 records in
rem 10+0 records out
rem 10 bytes transferred in 0.001 secs (10000 bytes/sec)
pause
rem downgrade
rem wget http://www59.multiupload.com:81/fil...118187CA1236F3BA6767A7/1.34.405.5_PC10IMG.zip
adb push 1.34.405.5_PC10IMG.zip /sdcard/PC10IMG.zip
adb reboot bootloader
but it didn't workout so much, don't know why it said something about it couldn't write recovery img file

Umm if you already rooted via the xda wiki then you should've had a bootloader that was engineering s-off right? Just saying because you could've flashed a custom rooted rom through bootloader and not had to re-root, that is unless the ruu applied an updated bootloader with s-on. Maybe boot into bootloader and see if the top line says PVT ENG S-OFF, worth a look anyway, could save you some headache
Sent from my Bulletproof G2

actually i'm haveing another headache a couple actually, for some reason, during the restore, it failed to download google maps among the gailion apps i downloaded, now i can't download no matter, i tried installing it manually, and it worked, but i can't see in the market.
the market on the web site says the application is not compatible.
also when i tried using anysoft keyboard and use the hebrew fonts, even though it installed i still couldn't get the keyboard.
right not i have no idea what's the state of my phone.

[HOW TO] Return to a Stock Branded RUU that isn't on AAHK

When returning to stock, I found this the most simple way to do it.
You will need:
AAHK
Your carrier's branded RUU (I'm using the Orange UK one found here
A computer with Windows on it (Annoying, I know), however this is just needed for the RUU exe process, not for AAHK
Disclaimer: I'm not responsible for anything you do to your device! I recommend making a backup of AAHK's file you will be editing before you start editing it
1. Download and open AAHK, entering the passcode (read the manual)
2. Type "o" and press enter
3. Type "s" and press enter
4. Find the closest generic RUU to your device, but DO NOT SELECT IT
5. Remember the CID of the one you chose (for me it's HTC__001, as I chose the UK generic one)
6. Close the terminal
7. Select your respective file that runs AAHK (.sh for Linux, .cmd for windows [I think])
8. Open it in a text editor
9. Use a find tool within the file to find the CID of your closest generic RUU, which should look a little like this:
Code:
elif [ "$inp" = "0" ]; then
cid="HTC__001"
dlFlash
10. Find your CID for your carrier, this thread is very useful: http://forum.xda-developers.com/showthread.php?t=1195475
11. Change the CID within the AAHK text file, to match your carrier's CID, for example my carrier's CID is ORANG001, so my text would now read this:
Code:
elif [ "$inp" = "0" ]; then
cid="ORANG001"
dlFlash
12. Save and close that file
13. Open AAHK in a terminal again, entering the passcode and then selecting "o" and "s"
14. Go to your generic RUU again (Don't worry that the CID hasn't changed in the terminal, it will have done in the code)
15. Now select that RUU, and let it download, but DO NOT YET SELECT FLASH "y", and DO NOT CLOSE AAHK
16. Download this PD98IMG http://cmw.22aaf3.com/ace/stock/1.32.405.6/PD98IMG.zip
17. Copy it to your AAHK folder, within the folder named PD98IMG, where there will be the one you just downloaded
18. Select the one that AAHK downloaded(will be called something like "PD98IMG_GB2" and rename it to "BACKUP_ZIP"
19. Select the one you just downloaded from my link, and rename it to what you just renamed the other one from, so it will be something like "PD98IMG_GB2"
20. Return to AAHK, that you left open, and now select "y" to flashing the RUU and "y" to setting S-ON
21. Wait for the phone to finish rebooting, returning to the stock, unbranded froyo RUU. You're not done yet.
22. When the phone is done turn on USB debugging, open a second terminal and run
Code:
adb shell getprop ro.cid
It should return your carrier's branded CID. If not, you did something wrong, re-root using AAHK and do the process again. ONLY IF IT does, then continue
23. Now you need to flash your branded RUU. If you need to, boot a Windows computer now and download it. Else, just open it
24. Accept everything it says about readmes and things, if you're nervous, read them
25. Let it flash, once it's done it should reboot the device
26. Again, enable USB debugging, open a second terminal and run:
Code:
adb shell getprop ro.cid
If it returns your carrier's branded CID, you're good, continue. Else, re-root and start again
27. Your phone should now prompt a software update if the RUU is older than the current version, accept and install these
28. Hit the thanks button, it took me a while to figure out and put this together
Thanks to attn1 for the AAHK, Chris Moyles for the Toby Lerone references on radio stations and Real Radio Northwest for providing me with background music for most of the time I was writing it.
You are done, now go do whatever you were going to do, whether it be warranty or trading it in

Any chance of re upping the Orange UK Firmware. As all the ones i have tried that said they was orange was telsa. Thanks in advance

hacktrix2006 said:
Any chance of re upping the Orange UK Firmware. As all the ones i have tried that said they was orange was telsa. Thanks in advance
Click to expand...
Click to collapse
I don't have the exe anymore, and it seems Goo doesn't either
You could try torrenting it from this site, appears to have it
http://bitsnoop.com/ruu-ace-orange-uk-1-40-61-2-radio-1-q24244672.html
Sent from my Galaxy Nexus using Tapatalk 4 Beta

Quinny899 said:
I don't have the exe anymore, and it seems Goo doesn't either
You could try torrenting it from this site, appears to have it
http://bitsnoop.com/ruu-ace-orange-uk-1-40-61-2-radio-1-q24244672.html
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you will give it a go.
Edit: Na its not working nothing there.(Seeder wise)

I managed to get a copy in the end, Install all the OTA's and then Nandroid the whole phone and made a new rom.zip for orange.
So its now the latest firmware 2.3.5 with the Latest Hboot as well that came with the OTA's.