So, my miscnew.img and PC10IMG.zip both have matching numbers (1.19.531.1). However, when i get to the last step of unrooting (flashing zip) i get "main version older, update fail!" Even though everything matches. Im at my wits ends. please help
You have started 5 different threads with this same question. Just stick to one and stop flooding the forum.
But, I will try to help. Did you flash a rooted stock rom before you flashed the pc10img.zip?
I didn't freeze or remove any bloatware so I just stayed on the stock rom I'm on
Sent from my T-Mobile G2
I wasn't trying to flood the forum intentionally, I'm just freaking out. My apologies.
Sent from my T-Mobile G2
how did you originally root your phone? gfree, rage, visionary?
Visionary
Sent from my T-Mobile G2
I just did this the other day so I'll see if I can help.
Just to clarify where you are right now, are you on stock OTA rooted? Or stock Pre OTA rooted?
I'm on stock ota rooted
Sent from my T-Mobile G2
Dswag said:
So, my miscnew.img and PC10IMG.zip both have matching numbers (1.19.531.1). However, when i get to the last step of unrooting (flashing zip) i get "main version older, update fail!" Even though everything matches. Im at my wits ends. please help
Click to expand...
Click to collapse
Sorry if this don't help but this is what I used to Root and Unroot:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
Step 1.) Flash Stock Rooted PRE-OTA Rom via ClockWorkMod
^^ Did that step cause you any issues?
I didn't flash any rom via clockwork. Is that the step I've been missing?? -_- Sent from my T-Mobile G2
Could very well be. I have unrooted 2 g2's using this method and I have always flashed a stock pre ota rom with root before continuing with the steps.
Sent from my HTC Vision using XDA Premium App
So I have the miscnew.img and PC10IMG.zip (both the 1.19 version). Could it be that I need to flash the rom that matches these two (pre ota), then flash the zip in hboot?
Sent from my T-Mobile G2
Dswag said:
So I have the miscnew.img and PC10IMG.zip (both the 1.19 version). Could it be that I need to flash the rom that matches these two (pre ota), then flash the zip in hboot?
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Wait, did you actually write your miscnew.img file back to partition 17 on your phone? Were there any errors when the command completed?
I don't know what a partition 17 is, but I created the misc.img file in terminal, then hex edited it to (1.19) version to create the miscnew.img, just like the guide of downgrading said.
Sent from my T-Mobile G2
Edit: if your asking did I have any errors after entering "mmcblk...17" etc, no. All that came up was something along the lines of "bytes received/sent".
Dswag said:
I don't know what a partition 17 is, but I created the misc.img file in terminal, then hex edited it to (1.19) version to create the miscnew.img, just like the guide of downgrading said.
Sent from my T-Mobile G2
Edit: if your asking did I have any errors after entering "mmcblk...17" etc, no. All that came up was something along the lines of "bytes received/sent".
Click to expand...
Click to collapse
Right, but simply creating the new misc.img file and sticking it on your SD card doesn't actually do anything. Both the guide on removing permanent root and the guide on downgrading both say the same thing---after you create the new miscnew.img file, you flash it back to your phone with the following command:
Code:
dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p17
Did you actually do this? It is the key step in the entire process.
Yes, I did that. But I did not flash a rooted stock pre ota rom. Is that what's ailing me? Because both the PC10IMG.zip and miscnew.img match.
Sent from my T-Mobile G2
Dswag said:
Yes, I did that. But I did not flash a rooted stock pre ota rom. Is that what's ailing me? Because both the PC10IMG.zip and miscnew.img match.
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Someone correct me if I am wrong but from my understanding, you need to be on the rooted stock pre ota before you can flash the PC10IMG.zip.
That's what I'm thinking also. I didn't know that
Sent from my T-Mobile G2
Dswag said:
That's what I'm thinking also. I didn't know that
Sent from my T-Mobile G2
Click to expand...
Click to collapse
You can give it a shot, but flashing back to a pre-rooted stock ROM shouldn't be necessary. It sounds to me like either the miscnew.img wasn't edited properly or it didn't get flashed back to your phone correctly when you ran the command I listed above (I had questioned whether or not you ran it since you didn't list it as one of the steps you did in an earlier post).
Try running the following commands in Terminal:
Code:
# su
# dd if=/dev/block/mmcblk0p17 bs=1 count=10 skip=160 2>/dev/null
It should return your current version number, which if you followed the steps in the guide, should be 1.19.531.1. If that is not what is returned (I'm guessing it is most likely still 1.22.531.8), then you need to check your modified image again and then flash it back to the phone as instructed in the guide.
Related
Well I need to help my friend Unroot her Evo.
I have tried the PC36IMG image copying and that didnt work. It would keep telling us that the main version is older and tell her to reboot. When i tried to use the RUU exe it would tell us...
HTC Android Phone Rom Update Utility 1.0.2.10
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct Update Utility and try again.
I dont understand since we're using the HTC Evo 4g one. She also already had the Htc sync connect.
Any ideas on what the problem could be. She has the latest update and currently is using the Fresh ROM.
Do the flash_image misc mtd-eng.img part of toast's part 2. That will reset the build number. Then flash the pc36img.zip through hboot.
Also: Wrong forum.
Not wrong forum. Maybe wrong thread but not wrong forum.
jrmithdobbs said:
Do the flash_image misc mtd-eng.img part of toast's part 2. That will reset the build number. Then flash the pc36img.zip through hboot.
Also: Wrong forum.
Click to expand...
Click to collapse
edit: nvm ^^ do what jrmithdobbs said
eskomo said:
Not wrong forum. Maybe wrong thread but not wrong forum.
Click to expand...
Click to collapse
either post in the thread that contains the rom or recovery in question or post the question in Q&A.
you'll have more luck if you post in the thread about the rom or recovery you are using.
I am confused. She has the latest update but is running Fresh ROM? Is she running the Froyo OTA update?
If she wants to unroot her phone just wait until tuesday when the release the Froyo RUU
jrmithdobbs said:
Do the flash_image misc mtd-eng.img part of toast's part 2. That will reset the build number. Then flash the pc36img.zip through hboot.
Also: Wrong forum.
Click to expand...
Click to collapse
I am also trying to unroot coming from Simple Root and can not simply run the RUU due to the Version Error. I can not follow Toast's Part 2 due to the fact I can not mount the sdcard, and the ls command returns no results in recovery (but will while OS is running).
I am at a loss as how to proceed...
Didnt Work...
same issue here....
put the img mtd-eng.img on root of card go terminal and type.
su
flash_image misc /sdcard/mtd-eng.img
reboot
all will go fine then run an ruu ota
it will work fine
I was a simpleroot user too. and had the same issues.
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Sticky this. In big bolt capital letters. I've seen this happen once already, and just saved another phone from this headache.
More people need to know about the DON'T-FLASH-PC10IMG.ZIP
dyndragon said:
Sticky this. In big bolt capital letters. I've seen this happen once already, and just saved another phone from this headache.
More people need to know about the DON'T-FLASH-PC10IMG.ZIP
Click to expand...
Click to collapse
When u say u saved a phone. Do u mean u stopped someone before they did it, or you mean u have a working fix. Pls post fix if u have one. I will post mine as soon as I confirm it.
Btw- I have seen 5 happen in the last 3 days. As I haven't gave up on any yet, some are worse off then others and only 2 have a possible fix in the am, well a fix I know of.
After I permarooted, I decide to flash a Z ROM. I did, and I didn't care for Sense, so I flashed PC10 and didn't have any issues. Mind you, I didn't flash the OTA at that point either. Phone booted up without an issue, I got the OTA almost immediately, and I permarooted again.
Basically, if you applied the OTA, don't flash PC10 to get stock again.
So does that mean the instructions for how to Un-Root are no good?
KronicAnarchy said:
So does that mean the instructions for how to Un-Root are no good?
Click to expand...
Click to collapse
I unrooted my phone, no problems.
No the instructions to unroot are correct because at the beginning you flash an alternate misc.img to change the main version number. I got stuck the other day because my phone wouldnt boot and i couldn't flash the ota because i had removed google goggles and some other system apps so i tried to downgrade using PC10IMG.zip and it cancelled during installation just as stated in the op and i was somehow able to flash the misc.img through fastboot and reflash with PC10IMG.zip
sethrd said:
After I permarooted, I decide to flash a Z ROM. I did, and I didn't care for Sense, so I flashed PC10 and didn't have any issues. Mind you, I didn't flash the OTA at that point either. Phone booted up without an issue, I got the OTA almost immediately, and I permarooted again.
Basically, if you applied the OTA, don't flash PC10 to get stock again.
Click to expand...
Click to collapse
If you did not flash the stock rom before you flashed the pc10, you got lucky. When it reboots half way though, it does a version check, and the rom version you happened to be running must have been an older base. If your phone is bootable and you flash the pc10 OUT OF ORDER it will lock you down that way, ie locked on sense. If anyone wants to go back to stock, just flash one of the stock w/root roms in recovery or via rom manager... trust me on this, there are more people screwing up there phone because of this then anything, just not posting about it. I've been up all hours of the night, helping differnt people the last few days.
KronicAnarchy said:
So does that mean the instructions for how to Un-Root are no good?
Click to expand...
Click to collapse
No the unroot guide is ok. If you notice, the first thing it has you flash is the stock w/root rom. Like I said if you follow proven instructions to a T, you will be ok. That is if you want to go back to non-root only though. If you just want stock with root, flash a stock with root rom via RECOVERY or ROM MANAGER.
Im not to sure how it all works and i just got up a little bit ago .
but since s-off doesnt check the sign couldnt we unpack and repack pc10img with the hboot with s-off?
fastludeh22 said:
Like I said if you follow proven instructions to a T, you will be ok.
Click to expand...
Click to collapse
Well he's edited his post now, and people have followed his instuctions and bricked their phones.
So just to confirm before I brick mine: The instructions in their current form will not brick my phone, right?
I had s-off when running baconbits. I tried to revert back to stock but couldn't. I then flashed pauls prerooted phone rom and tried to install the stock rom back onto the phone. I seems to have removed the s-off and now displays s-on. I am permanently rooted, but fastboot still shows s-on. Was this caused because I tried to flash the pc10img.zip? Now how do i revert back to stock? I don't have a nandroid backup for the stock rom, just paul's which after a recovery still displays s-on. It doesn't loop, I just can't install anything else on there.
I flashed pc10 and it turned S-ON. But when I booted it up I still had root acess, so it was like a temp root but where I could not write to the system. I took the ko file from the perm root and hex edited it to match the kernal on my phone.. boom rooted again and I was able to flash recovery and do a nand restore
I tested it out again by hbooting pc10.. and I was able to obtain s-off by changing the kernal number in the ko file
Sent from my T-Mobile G2 using XDA App
So let me get this straight, in order to flash pc10 safely we MUST have an existing PreRooted STOCK ROM?
No all you have to do is run hexeditor to change build number then you can flash pc10img
Sent from my T-Mobile G2 using Tapatalk
marc91988 said:
No all you have to do is run hexeditor to change build number then you can flash pc10img
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
Exactly. If you actually follow the directions in the thread you will be fine. I've done it more than a few times and have not had any problems yet.
I have also updated the instruction on the unroot guide aswell.
I was running the original Sense rom that was loaded via hboot which kept me at s-off. I was able to revert back to stock using the PC10 zip from here http://forum.xda-developers.com/showthread.php?t=831398 At the time I had no clockwork recovery. Was what I unsafe?
Thanks for the piece of mind. I don't want to unroot just yet, I'm running pretty much the stock rom w/ ota and bacon bits anyway, so........ Still it's nice to know that I can get back to stock should I NEED to.
Okay so I did this and I didn't brick my phone...and still have root/s-off
Did an ota update, after I found out there was perm root I perm root g2 s-off, then I went and downloaded clockwork/rom manager
Created a backup of the current g2, and did a wipe
Then hboot to sense ui (still have root). I went into clockwork create another backup. Played around with desire z rom.
After I decided to go back to stock 2.2 performed a restore with clockwork and now I am back to my original g2 stock.
So am I missing something here?
fryrice8850 said:
Okay so I did this and I didn't brick my phone...and still have root/s-off
Did an ota update, after I found out there was perm root I perm root g2 s-off, then I went and downloaded clockwork/rom manager
Created a backup of the current g2, and did a wipe
Then hboot to sense ui (still have root). I went into clockwork create another backup. Played around with desire z rom.
After I decided to go back to stock 2.2 performed a restore with clockwork and now I am back to my original g2 stock.
So am I missing something here?
Click to expand...
Click to collapse
These people didnt nand back before messing around with stuff
Sent from my T-Mobile G2 using XDA App
I've been having some issues with my screen recently, probably due to a cable being loose or something like that so I want to send my phone back to be repaired. I have S-OFF and am running CM6.1.1. I have a nandroid backup for the original stock rom, but this is obviously rooted. So have to i get to back to S-On with the original stock room un-rooted so my warranty isn't technically void??
edit: Its a EU desire z,
Restore the backup of the stock ROM that you have.
If you have S-OFF via gfree then you need to un-do that via "gfree -s on".
If you have the eng hboot then you need to dd back the stock hboot (get it out of a PC10IMG.zip file.
Finally you can remove root. Removing the Superuser app will almost certainly be enough, no-one is going to notice anything more.
I flashed a hboot to get s-off, how exactly do i dd back to stock hboot? Do i extract the file from the PC10IMG zip?
jakbjak said:
I flashed a hboot to get s-off, how exactly do i dd back to stock hboot? Do i extract the file from the PC10IMG zip?
Click to expand...
Click to collapse
Yes, extract the stock hboot from the correct PC10IMG.zip file, then you can dd it to your hboot partition just like you originally did with the eng boot.
Or if you just flash a complete stock ROM over the top (the same version as your backup, once the backup has been restored), it will install the stock hboot anyway.
ok still, just to be certain (last thing i want is to brick my phone!!) restore rooted stock rom from the nandroid backup, then get a copy of the original rom i have a flash it? and do i flash it through cwm or the other menu?
jakbjak said:
ok still, just to be certain (last thing i want is to brick my phone!!) restore rooted stock rom from the nandroid backup, then get a copy of the original rom i have a flash it? and do i flash it through cwm or the other menu?
Click to expand...
Click to collapse
If that stock ROM is the same version as your rooted backup that you restored, then yes, that should be fine because the stock ROM will include the stock hboot, to put you back to S-ON via hboot.
If however the stock ROM is an earlier version than your backup, you will have to go through an additional downgrading procedure to safely be able to flash an earlier ROM (or you could end up bricked).
No, you don't flash it via Clockwork. You put the ROM image (not RUU) onto the root folder of your SD card, called "PC10IMG.zip", then boot into hboot (with the phone powered off, hold Volume Down and then press Power until it switches on) and it will open the ROM and ask if you want to flash it.
Cool, that makes sense. Thanks
is this safe to flash on ANY Desire Z?
RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe
(This RUU is exactly the one used in the 1.72 root procedure to downgrade to 1.34)
Like I plan to just execute it on the computer and let it do its thing.
My baseband version:
12.28b.60.140eU_26.03.02.26_M
My rooting route was exactly as the XDA wiki, but stopped short of flashing ENG HBOOT.
I know I can restore my backup ROM, and s-off using gfree. My problem is with CWM recovery because if the people at the shop try to charge it with the power down, they will know I've rooted before due to the phone booting into recovery.
djfoo000 said:
is this safe to flash on ANY Desire Z?
RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe
Like I plan to just execute it on the computer and let it do its thing.
My baseband version
12.28b.60.140eU_26.03.02.26_M
My rooting route was exactly as the XDA wiki, but stopped short of flashing ENG HBOOT.
I know I can restore my backup ROM, and s-off using gfree. My problem is with CWM recovery because if the people at the shop try to charge it with the power down, they will know I've rooted before due to the phone booting into recovery.
Click to expand...
Click to collapse
I belive this is the RUU for the Europe Vision only, so if your Desire Z is not the Europe Vision I would not run this RUU.
Edit: I found this thread on your RUU, I would check it out first before flashing:
http://forum.xda-developers.com/archive/index.php/t-822908.html
In skimming the thread I see someone flashed this on a Bell Desire Z, but they super-cid with gfree first.
Edit 2:Cant you just find the stock recovery.img and then flash it to your phone using the flash_image method from terminal emulator? Since you dont have fastboot. Then re-run gfree with the -s option to get S-on again.
Heres the link to the Flash_image method:
http://forum.xda-developers.com/showthread.php?t=902493&highlight=flash_image
i was thinking of a pseudo-one click method. hahaha
I've just finished downloading the RUU i mentioned.
How do I go about extracting the recovery.img? I tried extracting with 7zip and it says cannot open file.
djfoo000 said:
i was thinking of a pseudo-one click method. hahaha
I've just finished downloading the RUU i mentioned.
How do I go about extracting the recovery.img? I tried extracting with 7zip and it says cannot open file.
Click to expand...
Click to collapse
Just download it myself, good question, not quite sure myself on an RUU since it wants to exe. , thought it might be a simple a unzipping it but ?
Edit : found this:http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html
there's nothing dangerous about it, right? As in the recovery.img extracted from any RUU is not baseband specific or anything? My radio is stock.
djfoo000 said:
there's nothing dangerous about it, right? As in the recovery.img extracted from any RUU is not baseband specific or anything? My radio is stock.
Click to expand...
Click to collapse
Im not gonna lie, I really dont know if the G2 and the Desire Z recovery.img are the same, I know theres a link to the stock G2 recovery image here:
http://forum.xda-developers.com/showthread.php?t=834545&highlight=unroot
hrmm... Just a thought, is that issue worthy of a thread? That whether stock recoveries of G2 and Desire Z are the same, regardless of location of origin (ie Asian/European etc).
You just need to run the RUU but then not press any buttons on the screen, then find the folder where the RUU has extracted temporary files. There will be a standard location on this that depends on your exact OS. Look for the most newly-created folders at this location, and a couple of levels down from there you will find the extracted files, including rom.zip.
Sent from my HTC Desire Z
The same version of Clockwork recovery is used on the G2 and all Desire Zs. So I would have thought you'd be absolutely fine to flash the stock recovery from that DZ RUU onto your own DZ.
Sent from my HTC Desire Z
So I recently put Virtuous Unity on my unbranded Desire Z and now I'd like to go back to stock and unroot the phone.
Wiping the system with Clockwork Recovery and flashing my backup stock ROM created by ROM Manager.
After that I'd probably have to replace partitions 7 and 17 with the respective stock versions and finally make it S-ON only since the phone came unlocked anyway. Flashing the recovery image may come last.
Correct me if I'm wrong but wouldn't that work and once the stock ROM is on there again it should be plain sailing. No?
EDIT: Before anyone mentions using the wiki unrooting guide, I'm probably missing something here but the the PC101IMG.zip files I can get from there may not be of any help.
I would say pc10img it back, then temp root with the included psneuter on the wiki and use gfree to turn s back on. All done.
Sent from my HTC Vision using XDA Premium App
xsteven77x said:
I would say pc10img it back, then temp root with the included psneuter on the wiki and use gfree to turn s back on. All done.
Click to expand...
Click to collapse
Isn't there a potentially high chance that I might brick it if the wrong PC101 is used though?
Finally managed to unroot it, temp root just wasn't doing it for some reason so instead of running around in circles I tried this.
Involved
1. Re-flashing the Stock ROM provided in this guide.
2. Following the WHOLE guide linked above.
3. To make it S-ON again we do this:
Code:
adb shell
/data/local/tmp/gfree -s on
exit
adb reboot bootloader
Should now say 'S-ON' at the top of the bootloader.
4. (Optional)
Covering up the evidence with one last flash.
The CID still shows up as "super CID" when I run 'fastboot oem boot' via ADB, but its the next best thing if you want to squeeze a free warranty repair out of HTC.
Hi guys,
Desire Z.
Vision PVT SHIP S-OFF
HBOOT-0.85.0005
Have been using rooted Desire Z on stock for months. I followed Rooting the Vision (G2/DZ) and DHD .
I recently decided to try out new ROMs. I had been using [ROM][Nov 6][v3.1][Desire Z] BeatMod BlissSense Hybrid | Sense 3.5 | 2.3.5 but ended up in a constant boot loop.
I got in to Recovery, but as soon as I got in, it scanned my sd card and asked me if I wanted to update. If I chose No, then all I could do was reboot. I couldn't select any other options. I eventually chose Yes and the pc10img.zip was flashed. I guess this was from when I downgraded my ROM during the root procedure.
I am now back at stock. Titanium Backup says it can't acquire root privileges. ROM Manager says it can't find SuperUser and that I need to root.
Have I just unrooted myself? Do I just follow the same procedure as before? Or can I use a backup that I made (with ROM Manager) a few days ago to get back to where I was?
Thanks guys for any help.
Can you boot into recovery? Vol up and power (i think) if so then flash a new rom! Or flash your backup from there.
Else yes follow the steps to root again.
Sent from my HTC Vision using Tapatalk
H4rry said:
Hi guys,
Desire Z.
Vision PVT SHIP S-OFF
HBOOT-0.85.0005
Have been using rooted Desire Z on stock for months. I followed Rooting the Vision (G2/DZ) and DHD .
I recently decided to try out new ROMs. I had been using [ROM][Nov 6][v3.1][Desire Z] BeatMod BlissSense Hybrid | Sense 3.5 | 2.3.5 but ended up in a constant boot loop.
I got in to Recovery, but as soon as I got in, it scanned my sd card and asked me if I wanted to update. If I chose No, then all I could do was reboot. I couldn't select any other options. I eventually chose Yes and the pc10img.zip was flashed. I guess this was from when I downgraded my ROM during the root procedure.
I am now back at stock. Titanium Backup says it can't acquire root privileges. ROM Manager says it can't find SuperUser and that I need to root.
Have I just unrooted myself? Do I just follow the same procedure as before? Or can I use a backup that I made (with ROM Manager) a few days ago to get back to where I was?
Thanks guys for any help.
Click to expand...
Click to collapse
You need to delete the PC10IMG file from your SD card. Then you should be able to restore a nandroid and be fine...
Sent from my HTC Vision using XDA App
Sorry forgot to say thanks guys for responding. (really think I'm losing my mind here)
I mentioned above about being able to get to recovery. This is where I could get to : http://www.hard-reset.com/images/htc_desire_z_hard_reset_android_reset.png
When I got there, the sd card was scanned and I was only given the option to upgrade or reboot as the phone found the pc10img.zip from when I rooted.
I chose upgrade (aw crap). I have just changed the name of the pc10img.zip file and I could access all the options but when I try recovery I just get a dark picture of a phone with a red triangle and exclamation mark.
So I guess I can't access recovery so I'll have to re-root ??
Am I right in thinking if I had changed the name of the file earlier before doing the update I'd have been able to access recovery?
[why didn't I think to do that file name change earlier, excuse me while I go off and beat my head against a wall]
You're gonna have to go through the rooting guide again. Except you are still S-OFF, so you can either modify the gfree command (leave out the -f arg) or leave out gfree entirely, and flash recovery through ROM Manager, after getting perm-root (running ./root_psn)
-Nipqer
Thanks Nipqer.
Am in work for the next 10 hours or so. I'll get back to this then.
edit
Nipqer, Can I clarify the modification to the gfree command you are talking about.
Just do the rooting procedure as normal except for section 4.a.2 of the rooting guide which currently says:
# ./gfree -f -b hboot-eng.img -y recovery.img
Should I change this to:
# ./gfree -b hboot-eng.img -y recovery.img ?
Again thanks for your help.
eh, didn't realise that editing my previous post may not bump/ alert you guys that I have posted again. So, eh, well, hmmm, I have.
thanks guys
H4rry, yes that is the correct command to use.
The -f switch is for S-OFF, SuperCID and SimUnlock, but you already have all those from your first root, so there is no need for it again.
-Nipqer
Thanks Nipqer, gonna give this a try now.
Thank you, thank you, thank you.
I am now rooted again. Just got to get all my apps back onboard and I'm back to two days ago.
Yea and sorry i didnt read your post as well as i should have. Glad you got it all worked out.
Sent from my HTC Vision using Tapatalk
No probs man and thanks anyway. You were right, just that I gave the wrong info.