I was following instructions on verifying if my HTC Desire Z has been rooted using this guide
I was expecting to see the result as the same subject as above but got this instead
===================
$ su
su
# cd /data/local
cd /data/local
# chmod 777 gfree_verify
chmod 777 gfree_verify
# stop ril-daemon
stop ril-daemon
# ./gfree_verify
./gfree_verify
gfree verify_cid returned:
@CID: HTC__044
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
===================
What does HTC__044 mean?
it means that you do not have supercid
tazz9690 said:
it means that you do not have supercid
Click to expand...
Click to collapse
Despite that, did I do a successful root?
From the information you posted, you are S-Off (@secu_flag:0) and your sim is unlocked (@SIMLOCK=00), so you should have successfully rooted.
Just to verify, do you have superuser privileges? If you do, then you should be set.
If you want the supercid privileges, I cannot help you there. I did not have that problem when I used gfree, nor have I seen anyone else with this problem.
Quick question though. Since you have everything but supercid, did you run:
# ./gfree -f
# sync
Or did you run another line besides "-f".
That is the only thing that I can see as to why you do not have it, but then again, my knowledge is limited when it comes to gfree.
tazz9690 said:
From the information you posted, you are S-Off (@secu_flag:0) and your sim is unlocked (@SIMLOCK=00), so you should have successfully rooted.
Just to verify, do you have superuser privileges? If you do, then you should be set.
If you want the supercid privileges, I cannot help you there. I did not have that problem when I used gfree, nor have I seen anyone else with this problem.
Quick question though. Since you have everything but supercid, did you run:
# ./gfree -f
# sync
Or did you run another line besides "-f".
That is the only thing that I can see as to why you do not have it, but then again, my knowledge is limited when it comes to gfree.
Click to expand...
Click to collapse
I did run -f and sync. The Superuser app is on the applications menu. I just wanted to make sure I was properly rooted. I was also able to make a backup of the ROM (I already had S-Off before from a previous attempt). I tried following the procedure to set S-Off back to S-On using #./grfree -s on but I got permission denied. I am not sure if I was doing it right.
My HTC Desire Z was bought in Singapore last December and this is the current About Phone information I have:
=========
Android version 2.2
Baseband version 12.28b.60.140eU_26.03.02.26_M
Kernel version 2.6.32.21-gd2764ed [email protected] #1 Tue Oct 26 16:04:03 CST 2010
Build number 1.34.707.5 CL273326 release-keys
Software Number 1.34.707.5
Browser version
Webkit 3.1
==========
I am not even sure if this already has the 1.72 update everyone has been talking about. How do I find that out?
Your software number tells you what version you are running.
You have 1.34, not the 1.72 update.
If you had the 1.72 update, you would not have been able to use the wiki, you would have had to use the new method (psneuter) to obtain temp root and then downgrade to an older version to then be able to use gfree.
tazz9690 said:
Your software number tells you what version you are running.
You have 1.34, not the 1.72 update.
If you had the 1.72 update, you would not have been able to use the wiki, you would have had to use the new method (psneuter) to obtain temp root and then downgrade to an older version to then be able to use gfree.
Click to expand...
Click to collapse
Thanks! I was able to flash to Cyanogen 6.1.1 but the onscreen buttons are just making haptic feedback but no response. I'll see what I can find to get this one working and will try other ROMs as well. I am currently downloading MIUI. What other ROMS can I try?
iamthechickengod said:
Thanks! I was able to flash to Cyanogen 6.1.1 but the onscreen buttons are just making haptic feedback but no response. I'll see what I can find to get this one working and will try other ROMs as well. I am currently downloading MIUI. What other ROMS can I try?
Click to expand...
Click to collapse
Cynogen Mod and MIUI are like the only ones ;p
you could try GingerVillan 1.4 but that requires Clock works recovery 3.0
You can also try a rooted sense rom as well, if you so please.
Also, the CM7 nightlies are on the Cyanogenmod website if you so please to run that, but that requires clockworkmod recovery 3.x.x.x
Stuck with HTC__044
I did the gfree per rooting process with -s off only. I have even installed cm7 with no problem. Now i need totryied change my CID to 11111111 to update more things. I tried running gfree again with -cid 11111111 but no success. How do i change it? Im stuck.
Related
I have a problem rooting a friend's phone using gfree.
When I rooted my phone, I used a different method since it was in the early days of rooting the desire z. I've followed the instructions found here: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Everything seems to work correctly until I execute ./gfree -f
At this point I get the error "Error reading input file" and the phone gets stuck (I have to remove battery to boot it up again).
Anyone has had this problem before? Possible fixes? Any help is appreciated.
Has he done the OTA update??
Edit: @Dan.. Oh yeah... my bad
MacaronyMax said:
Has he done the OTA update??
Click to expand...
Click to collapse
Look at the picture
The # is there.
Which means root.
WHich means rage / VISIONary worked.
He hasn't OTA'd
yea rage seems to have worked, i'm just getting that error at the end and can't proceed with the rooting.
If I'm not mistaking I believe he is rooted.already ( don't flame me if he's not I can't really see the pic on the xda app ....)
tsubus said:
yea rage seems to have worked, i'm just getting that error at the end and can't proceed with the rooting.
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
unfortunately i am not rooted (i can't even sync after ./gfree -f, gives an i/o error)
tsubus said:
unfortunately i am not rooted (i can't even sync after ./gfree -f, gives an i/o error)
Click to expand...
Click to collapse
You're running as root though (# prompt), so you have at least got temp root even if it isn't permanent.
You're getting an error when it tries to disable the write protection though, so I am guessing it is indeed temp root and you lose it after a reboot.
What ROM/kernel are you running exactly ? Some don't work with gfree.
Am having the exact same problem as Tsubus.
Orginal rom, no updates applied.
details:
Vision PVT SHIP S-ON
HBOOT-0.85.0005
MIRCOP-0425
RADIO-26.03.02.26-M
Did try Visionary, rage and gfree03 without luck
stringbean82 said:
Am having the exact same problem as Tsubus.
Orginal rom, no updates applied.
details:
Vision PVT SHIP S-ON
HBOOT-0.85.0005
MIRCOP-0425
RADIO-26.03.02.26-M
Did try Visionary, rage and gfree03 without luck
Click to expand...
Click to collapse
Which original ROM exactly though ? There are loads.
steviewevie said:
Which original ROM exactly though ? There are loads.
Click to expand...
Click to collapse
Android version 2.2
Kernel 2.6.32.21
Software version 1.34.405.5
stringbean82 said:
Android version 2.2
Kernel 2.6.32.21
Software version 1.34.405.5
Click to expand...
Click to collapse
Hmm, gfree should work fine on that version
What happened with Visionary ? I wonder if Visionary messed things up somehow ?
How much of a pain would it be for you to re-flash the ROM and see if it's happier after that ? (e.g. how difficult to get your data/settings back ?)
Let's see if anyone can come up with another idea.
Am available for any test, been busy for the last 6 hours at work trying to get it to work.
stringbean82 said:
Am available for any test, been busy for the last 6 hours at work trying to get it to work.
Click to expand...
Click to collapse
Well, it should work perfectly with that ROM version. That's the same version that I'm using. If you don't mind re-flashing your ROM (with the same version) it could be worth a try. I am not saying that I think it will definitely fix it, this is a long shot, but I can't think what else to suggest right now.
Edit - have you also tried the older method using the "insmod" command, the one in the threads on rage ? That would be interesting to double-check that the insmod is coming up with the "wrong" error message, similarly showing that it failed to disable the NAND write protection.
doesn't work with this on my friend's phone:
android version 2.2
kernel 2.6.32.21
software number 1.34.166.5
haven't tried visionary, only gfree...might give visionary a try later on if you guys think it could work.
Tomorrow am going to load the same image as i have now on it and then try again.
What is the recommended method?
Sent from my HTC Vision using Tapatalk
tsubus said:
doesn't work with this on my friend's phone:
android version 2.2
kernel 2.6.32.21
software number 1.34.166.5
haven't tried visionary, only gfree...might give visionary a try later on if you guys think it could work.
Click to expand...
Click to collapse
Don't try to perm-root with Visionary it'll soft-brick... Just a warning
alright, thanks for the heads-up.
not sure what i should try now though, it kind of seems like there is no way to root it atm. i guess time will tell.
same problem for me =/
You probably need to push superuser to your phone in a different way. I had a similar problem using gfree. Hold on and I will send you a link to the nook method that I used. You do this after you run rage and are in the root shell on terminal emulator. (Pound symbol at the beginning of the command line). once you push superuser this way it locks in itself. then you can run the ./gfree command hopefully. I never had a problem with that command before I got the proper superuser but it might help you. Wait 1 and I will send the link.
Sent from my HTC Vision using XDA App
http://nookdevs.com/NookColor_Installing_su_and_the_Superuser_app
That should take you to the proper page. Don't run the first command that starts with unzip. Its easier to download the superuser zip to your desktop and then extract it to the root of Your android sdk tools folder. Aka put it in the tools folder and not inside any other folder that might be in your tools folder. Then run the next two commands on adb after you navigate to your androidsdk/tools folder to install. The next commands that you run in your root shell are run with terminal emulator. You should still be in a root shell if you used rage and haven't rebooted your phone. Pound sign will be present. Pm me if you have problems or if you are confused in any way.
Sent from my HTC Vision using XDA App
I recently Perm-Rooted and S-offed my T-mobile G2 using the Rage method and I just wanted to know is the S-off Method used the same as the Gfree True S-Off I am reading about?
Baphometa said:
I recently Perm-Rooted and S-offed my T-mobile G2 using the Rage method and I just wanted to know is the S-off Method used the same as the Gfree True S-Off I am reading about?
Click to expand...
Click to collapse
Unless when you rooted you pushed the gfree file to your data/local with this command in adb :
$ adb push gfree /data/local
and the entered the following commands:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
# sync
Then no you probably dont have radio s-off, super CID, sim unlock yet
Heres a link to the gfree guide on the HTC Vision Wiki.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
There is a diffrence between perm rooting with just Rage, and perm rooting with gfree+root. Follow the link above to the wiki for more detailed explainations.
First off Thanks for the reply I'm guessing since this guide i used http://forum.xda-developers.com/showthread.php?t=834228 didnt have those commands anywhere i could see that i dont have the radio s-off
Is it possible to just use those commands you posted to apply the radio s-off or will i have to go through a longer process?
Baphometa said:
First off Thanks for the reply I'm guessing since this guide i used http://forum.xda-developers.com/showthread.php?t=834228 didnt have those commands anywhere i could see that i dont have the radio s-off
Is it possible to just use those commands you posted to apply the radio s-off or will i have to go through a longer process?
Click to expand...
Click to collapse
Heres the link to gfree instructions, all you have to do is read and follow the instructions, shouldn't take you more than 10 or 15 minutes to gfree, remember some custom roms and kernels arn't working with gfree also some radio fireware versions, so make sure you have a compatible rom first, there is a list on the link I just gave you, after gfree is ran you can load any rom you want onto the phone and will still be gfree.
http://forum.xda-developers.com/showthread.php?t=855764
Thanks for all the help I really appreciate it espcially since im about as noob as it get with this stuff.
BTW got the gfree to work properly Thanks again!
Baphometa said:
Thanks for all the help I really appreciate it espcially since im about as noob as it get with this stuff.
BTW got the gfree to work properly Thanks again!
Click to expand...
Click to collapse
Glad I could help and believe me if you got ADB up and running and pushing commands to your phone thats half the battle so your not that much of a noob.
I'm using the DHD for a couple of weeks now and I'm glad to say its a BIG difference between my almost bricked Xperia X1. But... as all of you guys out there, it is interesting to try new roms and features.
Enfortunately I think I've got a branded phone but I don't know for sure... My carrier is Vodafone, and I already tried looking for the exact smalbandversion but I can only find "RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.03.02.26_M_release_155891_signed".
I think there is a difference between these roms because of the "12.28b.60.140eU", but I don't know for sure. Can someone clear this up for me please? Also because the release-keys don't match...
Code:
Android-versie
2.2
Smalbandversie
12.28b.60.140eU_26.03.02.26_M
Kernel-versie
2.6.32.21-gf3f553d
[email protected] #1
Thu Oct 28 13:24:11 CST 2010
Build-nummer
1.32.405.6 CL278359 release-keys
Softwarenummer
1.32.405.6
Browserversie
Webkit 3.1
Since I'm paying for ensurance of the phone, I must be able to set everything back to stock again. Is there a way to backup my stock rom before flashing a new one?
Anyone please?
Sounds like just ordinary 1.32.405.6... You can check that via terminal emulator (market), type "getprop ro.cid". If it is something like VODAPxxx, it is branded.
You can backup stock ROM in ClockworkMod before flashing, it is possible in "backup & restore" menu. Make sure that you have at least 1 gig of free space in your SD.
jkoljo, thanks a lot!
getprop ro.cid gives me -> HTC__E11, so I expect I'm good to go?
So with Clockworkmod I can generate a "stock.rom" file that I can flash when I need to send the phone to HTC/Vodafone for repair after I've worked with a couple of other roms?
HTC__E11 = Dutch offical HTC, not branded to any carrier
It "responds" to HTC WWE RUUs, congratulations. You do not even have to make a backup, WWE RUU is your stock ROM! And it is actually a lot easier to return to stock when you can use a RUU.
ClockworkMod will make kind of a stock.rom, but that image does not contain hboot, splash1 etc, which in a RUU can return ENG S-OFF, clockworkmod recovery and other stuff to stock condition. You can check out my Radio S-OFF Tool's S-ON instructions, it is very simple when you have the RUU.
Great news jkoljo, thanks a lot for your help and information!!!
I'll inform myself about how flashing/s-off etc. works, because its a bit different than with my X1, i'll definately use your s-off method, after watching your video it can't go wrong
Tnx m8
Rooting problem
I encounter a problem I want to S-OFF my device so I tried temprooting my phone by using visionary.
This results in a black screen after it says "rooting device". Rebooting/reinstalling whatsoever wont work... I tried looking for answers and found many users encountering this problem, only they use 1.72 and have android 2.2.1. I'm using 1.32 and 2.2 so I should be able to root normally right?
EDIT: I checked "Set system r/w after boot" and this seems to fix my problem. I guess rooting worked because Terminal Emulator lets me do the "su" command. (it do flashes an info box saying Terminal Emulator gained superuser permissions)
Next problem... your s-off tool says "error: connection problem". I set the connection mode to "charge only", and starting the .exe with admin rights wont fix it.
EDIT #2: I was too fast installing the HTC Sync app fixed this. Continuing...
I ran the command getprop ro.cid
And result was "HTC__038"
I would like to know, how to take a backup of my current Rom and also if possible is there a stock rom for it, in case i want to revert back after rooting.
Appreciate your help
I have a vodafone (Australia) branded HTC Desire Z A7272 I want to debrand, here is the specifics from hboot and software about screens
From Hboot
HBOOT-0.85.0010
MICROP-0425
RADIO-26.06.02.27_M
eMMC-boot
Dec 27 2010,22:19:17
From about software screen
Android Version
2.2.1
Baseband version
12.28.h.60.140fU_26.06.02.27_M
Kernel version
2.6.32.21-g132894e
[email protected] #1
Fri Jan 14 13:17:35 CST 2011
Build Number
1.85.861.3 CL331649 release-keys
Software number
1.85.861.3
Browser version
Webkit 3.1
I just want to know if this method
http://forum.xda-developers.com/showthread.php?t=832503
will work with the rom from RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed be safe to use for this phone?
I believe I will need to allow downgrade (part 3 in the guide) As from what I can tell I'd be going from 1.85 to 1.34 is that correct?
After it is done can I use over-the air updates in the generic HTC environment to update? what is the current version for this phone?
I've just tried running dd if=/dev/block/mmcblk0p17 of=/sdcard/misc.img from adb and got the error
/dev/block/mmcblk0p17: cannot open for read: Permision denied
Which makes sense because I don't have root and can't use SU to get #
Does that mean I'm going to need to root it before i can debrand it? - I don't know that this version can be rooted. Am I stuck until there is a root method for this software?
check out the G2 forums and work on the guide. the most popular is the gfree method. Hopefully that will help you out.
I ran Visionary+ r14 and the temproot now function won't even work, goes back to the menu and If i open the terminal emulator on the phone SU gives permission denied
I found a guide on cyanogenmod wiki that used misc_version and psneutter to gain temp root and that worked
Debranding worked an I'm now on 1.34, which is android 2.2 - thing is, now the over-the-air updates don't work. I'm not sure why, shouldn't I be able to just update to a higher (non branded) version now?
apopberz said:
I found a guide on cyanogenmod wiki that used misc_version and psneutter to gain temp root and that worked
Click to expand...
Click to collapse
I was just on that site trying to temporarily root my device, it has same software version as yours, from vodafone australia.
it says falied to open backup file after i enter this line
/data/local/tmp/misc_version -s 1.33.405.5 in command prompt
so did you actually root your device succesfully, beein trying but i keep getting permission denials and stuff
can you post me the method you used
Hi all
Definite noob so be easy on me. Just wanted to see if anyone has been successful since? I understand it's been a year, but google is of no help...
I'm with Voda with my HTC Desire Z and tried to gain root (even temp) but to no avail (using http: // wiki. cyanogenmod. com /wiki /HTC_Desire_Z:_Rooting sorry can't externalink because haven't posted enough yet).
I seem to stop somewhere pushing Superuser.apk
Reason for debranding is because I'm so sick of the crap Voda add in there...
for downgrade (u will need to create a goldcard for debranding):
http://forum.xda-developers.com/showthread.php?t=1178912
for permroot:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I ran gfree verify and this was the output that it recorded:
gfree verify_cid returned: ATV1
gfree verify_secu_flag returned:
OK
gfree verify_secu_flag returned: ATV1
gfree verify_secu_flag returned:
OK
gfree verify_simlock returned: [email protected]?
gfree verify_simlock returned:
@CID: T-MOB010
OK
[email protected]?AA
@secu_flag: 1
OK
My hboot says it is S-off, but @secu_flag: 1 says it is not S-off
My phone is currently running
Mimicry 1.5.0 using ext4 partition
4ext recovery
radio 26.13.04.19_M
I read in another post that having a fake S-off can lead to complications. In the wiki Gfree needs to have a radio less than 26.03.02.xx. Do I need to fully convert my phone back to stock and do the root process all over or can I just flash a radio less than 26.03.02.xx and run gfree?
you need to downgrade radio and have a "stockish" rom/kernel
best to just do the complete downgrade upgrade process
START HERE
THEN FOLLOW THESE STEPS
its not that fake s-off will inherently cause issues, its just that if you run into issues later on, things can be easier to fix with true radio s-off.
in someways it can cause issues as no more security checks at any level, but this also means fixing things may be easier
demkantor said:
you need to downgrade radio and have a "stockish" rom/kernel
best to just do the complete downgrade upgrade process
START HERE
THEN FOLLOW THESE STEPS
its not that fake s-off will inherently cause issues, its just that if you run into issues later on, things can be easier to fix with true radio s-off.
in someways it can cause issues as no more security checks at any level, but this also means fixing things may be easier
Click to expand...
Click to collapse
Ok thank you very much I will do that. The guide says this will only work if I have true S-off. Will this cause a problem for me?
I downloaded the radio and now i need a rom to install to run gfree. Any advice as to what rom will work with gfree?
Sorry, I linked you the wrong post
http://forum.xda-developers.com/showthread.php?p=15851661
Skip the temp rooting as you're already rooted
Do the supercid
And then follow the downgrade
(Steps 2 and 4 I think)
The use the wiki to finish rooting with the gfree method
The flash ROM of choice
Oh and the rooting guide will give you clockwork recovery and the downgrade will put you at an old radio, if you want to change either you will now be able to do it via fastboot
This is my preferred method as it is safest, I made I guide to do it if you have trobles
Sent from my Nexus 7 using xda premium
My problem is solved. I ended up going back to stock and re-rooting with gfree. Something messed up and was getting errors in the recovery screen. I ran mke2fs /dev/block/mmcblk0p27 through the adb shell and was able to use a nand backup. I hope that was just a one time thing and doesn't happen again. When I ran gfree the hboot and recovery both checked out and installed fine. Not sure what caused the problem I had, but now my phone has CID: 11111111, SIMLOCK= 00, and secu_flag: 0. Thanks for the help.