Database Users

Nandroid Backup > Run Release RUU 2.27.651.5 > Nandroid Restore = Safe?

----------------------------------------------------
Original Text:
----------------------------------------------------
Firstly, I tried to search but if this ends up simply rehashing another thread, mods please direct me to proper thread and delete this.
Now to my question. I am still running the base HBoot of my phone from the 1.56 RUU (I bought phone in December 2009). I'm rooted right now with that and using custom ROM/radio.
Now that the infamous 2.1 official RUU is out, would it be safe to up my phone to the root-included TEST RUU, RUU_Hero_C_Sprint_2.20.651.1_signed_test, and re-push flash_image or does it even really matter which hboot I'm running on (figure hboot is the only thing permanently stuck on phone from RUU)?
Or to put another way, do I gain anything from a higher-version hboot from the Test RUU other than it looking more like the official release so root isn't as obvious?
Any thoughts welcome
-----------------------------------------
This is sorta deprecated now that we have Root on the Release RUU, so repurposing the thread.
My new question: Now that i've rooted the Official Release version, can I restore my old nandroid backup without breaking my phone?
I did a nandroid backup of my fully-set-up Fresh 2.1.2 Install before I ran the Official RUU to 2.27.651.5 and now I'm wondering if it will break anything to "restore" that backup.
Again, any thoughts are welcome.

diaknia said:
Firstly, I tried to search but if this ends up simply rehashing another thread, mods please direct me to proper thread and delete this.
Now to my question. I am still running the base HBoot of my phone from the 1.56 RUU (I bought phone in December 2009). I'm rooted right now with that and using custom ROM/radio.
Now that the infamous 2.1 official RUU is out, would it be safe to up my phone to the root-included TEST RUU and re-push flash_image or does it even really matter which hboot I'm running on?
Or to put another way, do I gain anything from a higher-version hboot from the Test RUU other than it looking more like the official release so root isn't as obvious?
Click to expand...
Click to collapse
to my knowledge if your hboot changes from 1.56 to the one from the official you will lose root as of now, the test RUU still has root but its super buggy, why would you want to flash the official or the test anyways, theres roms here that blow the stock ones out the water, but once again to my knowledge you WILL lose root. And the test ruu with root has mad issues you should do a search bro as far as upgrading to the newer hboot well im not sure if it has features but the devs are still trying to break root in the new hboot.
check this out bro just in case you already flashed it http://forum.xda-developers.com/showthread.php?t=693449&highlight=hboot

I have not yet flashed the Test RUU.
From what I understand the Test RUU still has su built in, so all I need to do is re-push flash_image to get a custom recovery back on it and I'm golden from there.
I don't plan on using the stock ROM that comes with the RUU more than I have to, just curious about installing custom ROMs from that base versus the 1.56 base.
I still plan on uploading flash_image and doing the custom ROMs and Radio like now.

diaknia said:
I have not yet flashed the Test RUU.
I don't plan on using the stock ROM that comes with the RUU more than I have to, just curious about installing custom ROMs from that base versus the 1.56 base.
I still plan on uploading flash_image and doing the custom ROMs and Radio like now.
Click to expand...
Click to collapse
well from what i heard recently that base doesnt have audio issues that some people deal with on certain roms like the drivers are better, but my old hero i always had audios issues not with this refurb i dont get um anymore. but that 1.56 base is solid theres so much **** to work outta 2.1, until then im rocking darchdroid2.63 the only asop rom out there for our phones!
Im running Godspeed recovery, darchdroid2.63 and the latest 2.1 sprint radio and i cant complain

good to know
dirkydirk23 said:
well from what i heard recently that base doesnt have audio issues that some people deal with on certain roms like the drivers are better, but my old hero i always had audios issues not with this refurb i dont get um anymore. but that 1.56 base is solid theres so much **** to work outta 2.1, until then im rocking darchdroid2.63 the only asop rom out there for our phones!
Im running Godspeed recovery, darchdroid2.63 and the latest 2.1 sprint radio and i cant complain
Click to expand...
Click to collapse
I've already had audio issues installing custom ROMs based on 2.20.651.1 Test while using the 1.56 base, yet Fresh 2.1.2 based on 2.27.651.5 has yet to glitch on me for audio *crosses fingers*.
I'd still prefer to run a 2.27.651.5-based ROM like Fresh 2.1.2 even after upgrading my HBoot to the one from the 2.20.651.1 Test RUU, if I do so.
Original point of my question was if there was anything buggy in the HBoot itself moving from 1.56 to 2.20 RUU. Correct me if I'm wrong but HBoot is really the only thing that can't be easily flashed. You can flash both ROMs and Radio.
Far as AOSP, it's cool and all, but call me crazy: I actually like Sense.

diaknia said:
I've already had audio issues installing custom ROMs based on 2.20.651.1 Test while using the 1.56 base, yet Fresh 2.1.2 based on 2.27.651.5 has yet to glitch on me for audio *crosses fingers*.
I'd still prefer to run a 2.27.651.5-based ROM like Fresh 2.1.2 even after upgrading my HBoot to the one from the 2.20.651.1 Test RUU, if I do so.
Original point of my question was if there was anything buggy in the HBoot itself moving from 1.56 to 2.20 RUU. Correct me if I'm wrong but HBoot is really the only thing that can't be easily flashed. You can flash both ROMs and Radio.
Far as AOSP, it's cool and all, but call me crazy: I actually like Sense.
Click to expand...
Click to collapse
There is nothing wrong w/ the hboot. and the hboot isn't even the thing blocking root. The audio issue seems to differ from phone to phone, I have never had audio issues on my phone.

Thanks for the responses, regaw and dirky.
It looks like doesn't matter one way or another which base (rooted 1.56 or rooted 2.20) I use. I should have same functionality either way. I'm just gonna stick with 1.56. Really comes down to "if it ain't broke..."
On a side note.... i'm an eager follower of the official RUU ROOT thread on the dev sub-forum, Regaw, keep up the good work. Still feel bad for you that you've been stuck without root so long...
When you crack the thing, and I maintain hope you will, that's when I'll probly go and upgrade to the Release RUU.

diaknia said:
It looks like doesn't matter one way or another which base (rooted 1.56 or rooted 2.20) I use. I should have same functionality either way. I'm just gonna stick with 1.56. Really comes down to "if it ain't broke..."
Click to expand...
Click to collapse
Basically this.

abcdfv said:
Basically this.
Click to expand...
Click to collapse
yeah ive yet to run into it but i hear hboots are *****es to downgrade, but yeah i guess you and i both learned something dude, im rollin with your last post, if it aint broke dont fix it lol

dirkydirk23 said:
yeah ive yet to run into it but i hear hboots are *****es to downgrade, but yeah i guess you and i both learned something dude, im rollin with your last post, if it aint broke dont fix it lol
Click to expand...
Click to collapse
If you had run the test ruu and already pushed flash_image and custom recovery back to the phone then you can restore the original hboot in about 10 seconds if you want.
From recovery flash the .zip attached here and the hboot will revert to 1.41 instead of 1.47.

Cool, moot point now, though.
Now that the release version is rooted, I upgraded to the release RUU and re-rooted. Got Toast's OC recovery kernel rocking already.
Sorta off-topic, but I do have one small question:
I made a nandroid of my install of Fresh 2.1.2 before I upgraded. Would it be safe to restore that nandroid back now that i'm on the 2.27.651.5 RUU?

diaknia said:
Cool, moot point now, though.
Now that the release version is rooted, I upgraded to the release RUU and re-rooted. Got Toast's OC recovery kernel rocking already.
Sorta off-topic, but I do have one small question:
I made a nandroid of my install of Fresh 2.1.2 before I upgraded. Would it be safe to restore that nandroid back now that i'm on the 2.27.651.5 RUU?
Click to expand...
Click to collapse
I am curious about this also. Currently running fresh 2.1.1 previously from a 1.5 root and was thinking about updating to the .5 ruu and doing the root and than restoring a nandroid

regarding the next ota from verizon....

i like the rom i am using and do not want the next update from verizon. how do i got about keeping what i have and not taking the next update? i obviously don't want my phone asking me every day if i want to apply the update. do i need to trick it into thinking i already have it? if so, how do we do this?

Are you running a custom rom? If so, it shouldn't nag you for any Official OTA's.

TheGamerZ said:
Are you running a custom rom? If so, it shouldn't nag you for any Official OTA's.
Click to expand...
Click to collapse
i'm running version 2.0 of Virtuous rom. it's based off of the build that is currently on any stock Incredible. it's deodexed and stuff, but it's based off of the current build. 3.21.605.1 is the build of my current rom, not 3.26.605.1.
i have put a lot of work into getting it where it is right now and i have no desire at all to run anything different. i keep updating kernels as they get better and better, but thats it.

Hello boys and girls!
The word of the day is... "Nandroid"... Can you say it with me? "Naaaaaaandroid" Good, I knew you could! (^_^)>b
p.s. - the previous poster is correct. Any custom ROM should either A)not get the OTA update at all or B)get the OTA and prevent it from installing which will shut up that bothersome notification lol

dimebagdan65 said:
The word of the day is... "Nandroid"... Can you say it with me? "Naaaaaaandroid" Good, I knew you could! (^_^)>b
p.s. - the previous poster is correct. Any custom ROM should either A)not get the OTA update at all or B)get the OTA and prevent it from installing which will shut up that bothersome notification lol
Click to expand...
Click to collapse
i have several nandroids of my current rom from different dates, so i have that covered.
thanks. i'll wait and see what happens.

jasonb1985 said:
i have several nandroids of my current rom from different dates, so i have that covered.
thanks. i'll wait and see what happens.
Click to expand...
Click to collapse
Good deal, I'm just holding my breath for the LTE Incredible HD hehe
Sent from my ADR6300 using XDA App

FYI - There's a post on the development forum for the skyraider rom where a user says they're receiving the update message too! Sounds like not all custom ROMS block OTA's.
________________________________
Unrevoked forever
SkyRaider Sense 3.3.3
KiNgxKernel BFS (#5)
Radio 2.15.00.07.28

Here, this should help stop the nagging:
netboy3 said:
Thanks for the reference. The leaked build version seems to be working for this purpose.
To get this to work, you need to edit the /system/build.prop. find the line that begins with "ro.build.fingerprint" and change it to:
Code:
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/264707:user/release-keys
Once rebooted, the nag might appear once more, but if you go to Settings->About phone->System updates you wil now get "your system is currently up to date".
Click to expand...
Click to collapse
I was getting bothered by it, since like 10am on the 8th, did this, bugged me after the reboot once, and was done after that.

Blah12543 said:
Here, this should help stop the nagging:
I was getting bothered by it, since like 10am on the 8th, did this, bugged me after the reboot once, and was done after that.
Click to expand...
Click to collapse
saw this in the skyraider sense thread. thank god for Root Explorer.

jasonb1985 said:
saw this in the skyraider sense thread. thank god for Root Explorer.
Click to expand...
Click to collapse
Yeah lol that's what I used as well.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.

[q] will ota updates stop me getting root in future?

OK a nice simple one,
had my dhd a few weeks now very pleased with it. Am a massive fan of cyanogenmod roms, previously had a magic 32b and his roms were the best thing to happen to the phone, so am holding out for a cyanogenmod dhd rom - fingers crossed!
So if I install OTA updates will it stop me from getting root with S-OFF in the future. Golden rule of flashing anything (apart from backing up first!!) is not to update to the latest system software. Well this has always been the case with anyhing I have flashed in the past (psp, ps3, magic 32b, ipod, iphones etc...) is that also the case with the DHD?????
DHD on T-Mobile UK.

nop, its not like "apple" devices, you can install otas from htc and hack your device, the ota include some software issue that fix (bugs and so).
btw: if you have root and recovery - you will not get any OTA, the recovery blocks it,
but you will get it from your costom rom vision.

As I thought, same deal as my old magic 32b then. Still think i'm going to sit on the fence for a while an watch what roms get developed or ported over.
I just miss a few of the mods in CM roms, silly thing like being able to enter a custom field in the add contact menu. Im sure i'll get over it. Although I believe that was a wysie mod to the phone book.
Thanks for the quick response.
Just gotta say how nice this phone is after my magic 32b, its like upgarading the ram and processor on your PC, it flies!!

An afterthought,
it seems it would be sensible to install the first few OTA updates before rooting so any stock software bugs are fixed before you loose the ability to update OTA.
Unless of course you are flashing a custom ROM which I assume the devs would include the bugfixes within their ROMS.

Why dont you try the CM rom now and if you dont want to keep it unroot the phone ?

Its brilliant by the way

I didnt realise there was a CM rom for the DHD, i couldnt see a category on his site for the DHD

But I do see it on the first page here in the dev section. Very pleased CM for the DHD and the phone has only been out a short while!
http://forum.xda-developers.com/showthread.php?t=844703

liorra3 said:
nop, its not like "apple" devices, you can install otas from htc and hack your device, the ota include some software issue that fix (bugs and so)...
Click to expand...
Click to collapse
Untrue: OTAs can and surely will fix the exploit used to root our DHD. Once rooted, never install an OTA and wait for a custom rom with the fix(es).
f.
Sent from The Galactic Empire using the Dark Side of The Force

forelli said:
Untrue: OTAs can and surely will fix the exploit used to root our DHD. Once rooted, never install an OTA and wait for a custom rom with the fix(es).
f.
Sent from The Galactic Empire using the Dark Side of The Force
Click to expand...
Click to collapse
Although if they do screw us over it is still possible to restore an older ruu image and re-root. I have archived myself a copy of the original WWE just in case.

dr.m0x said:
Although if they do screw us over it is still possible to restore an older ruu image and re-root. I have archived myself a copy of the original WWE just in case.
Click to expand...
Click to collapse
No, because they usually update the hboot, and when they do that, you're properly f#@&!d because Devs have to find a new exploit.
f.
Sent from The Galactic Empire using the Dark Side of The Force

forelli said:
No, because they usually update the hboot, and when they do that, you're properly f#@&!d because Devs have to find a new exploit.
f.
Sent from The Galactic Empire using the Dark Side of The Force
Click to expand...
Click to collapse
Couldn't you make a goldcard with sdk and a HxD hex editor??...then flash the ruu and you should be able to OTA..
Not as I see a need to do this as the Devs will always make new custom roms with the updated offical roms anyway..

Rooting With The 2.3 O.T.A. Update

For everyone who's been wondering and asking,
As of right now there is NO WAY to root your phone if you accepted the 2.3 Gingerbread OTA update and there is no way to revert back to 2.2.
For all the people who have accepted it, you are stuck with a non-rootable phone until a dev can produce a new root method.
With that being said, temp-root is also NOT available.
Also, flashing anything like a different ROM or a new kernel is NOT possible at this time.
If you accidentally updated or just got the phone from Sprint, you are out of luck for now.

thanks for the info. i have been waiting to update because i suspected as much. For all those that updated to 2.3, is it awesome????
Sent from my PG06100 using XDA App

How long did it take for 2.2 to be rooted? Hopefully 2.3 should take the same amount of time/less time.
-CM7 ADR6300

Caiaphas said:
there is no way to revert back to 2.2.
Click to expand...
Click to collapse
The old official RUUs don't work on the phone?

x99percent said:
The old official RUUs don't work on the phone?
Click to expand...
Click to collapse
Nope, they don't.

Lancerz said:
Nope, they don't.
Click to expand...
Click to collapse
Any more of an explanation than that? ...like the error message you get?
People had to RUU back to an older version of Froyo when the latest update plugged up what was the latest root exploit, and that old RUU always worked without a problem. It would be a shame if HTC/Sprint didn't "allow" people to revert back to the older OS.

I think the error code was error 170 when running the RUU, but I have tried all the ways just like everyone else and none of them work.

dpwhitty11 said:
How long did it take for 2.2 to be rooted? Hopefully 2.3 should take the same amount of time/less time.
-CM7 ADR6300
Click to expand...
Click to collapse
FOREVER!!!! At least it felt that way. More people should have the phone now so shouldn't be too long.

Lancerz said:
I think the error code was error 170 when running the RUU, but I have tried all the ways just like everyone else and none of them work.
Click to expand...
Click to collapse
I would guess that booting into the bootloader to load the old Froyo RUU would still work. I always thought the RUU was looking for the proper phone, regardless of its firmware/OS versions.

Nope, in order for a ruu to run, the phone has to have the same or older hboot
Sent from my PG06100 using XDA App

I wish it was that easy because I forgot how much the GPS sucks on sense roms. Got a trip out of town coming up this weekend also, grrrr.

Lancerz said:
I wish it was that easy because I forgot how much the GPS sucks on sense roms. Got a trip out of town coming up this weekend also, grrrr.
Click to expand...
Click to collapse
Really? I always thought Sense was great, but AOSP roms sucked at GPS.

Just used the gps in the 2.3 rom and it worked out great. It was a short distance though so might need more testing fyi

I think the GPS on sense (stock at least) tends to take a little longer to lock on, that's all.
Hopefully this gets rooted soon since I've got to send my current phone back in a couple of days, and it wouldn't surprise me if the new one has the update already

danaff37 said:
Nope, in order for a ruu to run, the phone has to have the same or older hboot
Click to expand...
Click to collapse
So is this "170" error seen in the RUU program or on the phone itself?
Forgive me if I'm way behind the ball on this: The Froyo RUU contains a "rom.zip" that looks like it could simply be renamed to PG06IMG.zip and flashed from the bootloader.

x99percent said:
So is this "170" error seen in the RUU program or on the phone itself?
Forgive me if I'm way behind the ball on this: The Froyo RUU contains a "rom.zip" that looks like it could simply be renamed to PG06IMG.zip and flashed from the bootloader.
Click to expand...
Click to collapse
I don't know bout that error but when I tried twice to ruu my wife's phoneI think the error was 104 bootloader not new enuff something like that.

Well when you run the RUU it goes through all the motions like its going to be successful. Then it reboots into the bootloader and you get the all black HTC screen on your phone while its updating. The RUU on your pc screen is at the part where it says updating your rom image may take 10 minutes etc. Then you get the error [140] Bootloader version error. "The rom update utility cannot update your Android phone, please get the correct ROM update utility and try again."The error [170] is when it doesnt find your phone connected to the usb.

This should be done uploading in about 3 minutes. Rename to PG06IMG.zip, place it in the root of your SD card, and boot up in the bootloader. If it doesn't work, I'll have another to try tomorrow.
BACK UP YOUR DATA/APPS/CONTACTS FIRST (I recommend using Titanium Backup, SMS Backup & Restore, and Call Logs Backup & Restore... and you should be syncing your contacts to a google account)
http://www.4shared.com/file/ADnrxUXB/Stock-Froyo-ROM-1176511.html

I'll give it a try now
Edit: Nope, that doesn't work.

great.
i guess i am stuck with this buggy 2.3 rom until a root solution is found and i can get this crappy rom off my phone. i am tired of the apps not working. locking up & same with the OS.
do the world a favor and steer clear of the RUU 2.3 rom. dont be stuck like the rest of us with a rom we cant do anything with.

PC10img.zip from Tmobile store sd card

Here is the pc10img.zip file that is available from T-Mobile stores. Make sure your phone is fully charged before you attempt to install it, the demo I installed it on would not install unless the battery was 100%.
https://rapidshare.com/files/3796067356/PC10IMG.zip

Great, thank you! Not looking forward to reinstalling all my apps but downgrading again from 2.3.3 would have been a lengthy process as well.
I guess I know what I'll be doing tonight...
Sent from my T-Mobile G2 using XDA App

So does this mean a dev can finally tear this apart and give us some debloated roms with goodies added. Been trying to be patient
Sent from my HTC Vision using XDA Premium App

xsteven77x said:
So does this mean a dev can finally tear this apart and give us some debloated roms with goodies added. Been trying to be patient
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I hold out hope that someone can unpack and build a rooted flash out of this. Otherwise, it's going to be just like the leak in that once you flash it you're left sitting around waiting for someone to do something...anything with it.
Mad props to the OP for putting this up. This should definitely get a ball rolling since we now have the FULL PC10IMG ROM flash version of the newest build/GB available for the G2.
Interesting too - the newest stuff (tp's) in that archive are 7/29/2011 - soooo fresh

Thanks for uploading this file. I updated my G2 last week. Kinda odd the update zip I used was only 73.1 MB and this one is 131.MB almost doubled. What is the differance between the two files. It seemed to update just fine from 2.2 to 2.3.4. Everything is running just smooth. Unless there are files and apps that I might be missing. I might give this a try again. Currently running 2.3.4 unrooted with S-ON. Still waiting for someone who can fully root the OTA 2.3.4 with S-OFF. Anyone know about the update zip that was leaked last week? Should I flash this one instead or keep what I have?

zkid2010 said:
I hold out hope that someone can unpack and build a rooted flash out of this. Otherwise, it's going to be just like the leak in that once you flash it you're left sitting around waiting for someone to do something...anything with it.
Mad props to the OP for putting this up. This should definitely get a ball rolling since we now have the FULL PC10IMG ROM flash version of the newest build/GB available for the G2.
Interesting too - the newest stuff (tp's) in that archive are 7/29/2011 - soooo fresh
Click to expand...
Click to collapse
We already got a rooted flash of this we need it tweaked up with someone who knows what there doing. Seems we have little development for our phones anymore so I'm not holding out that it will be soon.
Sent from my HTC Vision using XDA Premium App

Kilroy672 said:
Thanks for uploading this file. I updated my G2 last week. Kinda odd the update zip I used was only 73.1 MB and this one is 131.MB almost doubled. What is the differance between the two files. It seemed to update just fine from 2.2 to 2.3.4. Everything is running just smooth. Unless there are files and apps that I might be missing. I might give this a try again. Currently running 2.3.4 unrooted with S-ON. Still waiting for someone who can fully root the OTA 2.3.4 with S-OFF. Anyone know about the update zip that was leaked last week? Should I flash this one instead or keep what I have?
Click to expand...
Click to collapse
The update.zip is an update from 2.2 to 2.3.4. This PC10IMG.zip is the whole operating system. You can be on the first OS that shipped with the phone (2.2 but before wifi calling) and still use this file. To use the update.zip, you must be running the update that included wifi calling.
PC10IMG.zip will factory reset your phone.

Just like blink said, this is the full system image, the update essentially just includes the updated code not the entire image.
My hope is that this will help the developers intigrate this into their roms.

xsteven77x said:
We already got a rooted flash of this we need it tweaked up with someone who knows what there doing. Seems we have little development for our phones anymore so I'm not holding out that it will be soon.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
lulwot? This is THE first I've seen of the PC10IMG - full ROM from the T-Mobile store sdcard update. If there is a rooted flash of this please provide the link. Like yesterday! ROFL
Otherwise, all we have or have had is a rooted franken-build flashable mashup of the OTA and whatever other stuff.
Like I said, if you got a link to the full rooted flash of THIS rom, I'm all ears
Again - huge props to @atlp99 who made good saying he would bring the in-store copy ASAP. Well done!
PS - @atlp99 I saw your thread and it looks like they deleted it. Regrettably unless your posting CM7 crap or some variation of that or some Sense rom, they seem to delete new threads.
@RM, question, why not just delete the Vision stuff off xda? Or, alternatively quit deleting **** you pinhead.

Mirror!
Does anybody have a mirror download for this? I cant seem to download it from radidshare

zkid2010 said:
Like I said, if you got a link to the full rooted flash of THIS rom, I'm all ears
Click to expand...
Click to collapse
I made a rooted version of the stock ROM. Right now I'm testing it, should be up in 20 minutes

rr5678 said:
I made a rooted version of the stock ROM. Right now I'm testing it, should be up in 20 minutes
Click to expand...
Click to collapse
Cool can't wait. What rooted version of what stock rom are you talking about? The PC10img.zip that we are talking about here ( I hope so) or the stock 2.2?

Kilroy672 said:
Cool can't wait. What rooted version of what stock rom are you talking about? The PC10img.zip that we are talking about here ( I hope so) or the stock 2.2?
Click to expand...
Click to collapse
Yep, the PC10IMG. (2.3.4)

rr5678 said:
Yep, the PC10IMG. (2.3.4)
Click to expand...
Click to collapse
Cool, please keep us updated if this is a working rooted rom. + 1 for you

Kilroy672 said:
Cool, please keep us updated if this is a working rooted rom. + 1 for you
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=16503984#post16503984
there it is

rr5678 said:
http://forum.xda-developers.com/showthread.php?p=16503984#post16503984
there it is
Click to expand...
Click to collapse
Sorry im a newbie..do i just rename the file PC10IMG.ZIP and put it on my sd card, boot up into the bootloader and go from there? I did that with the earlier PC10IMG.ZIP 2.3.4 that was posted on this thread..can it override that??

IllBill said:
Sorry im a newbie..do i just rename the file PC10IMG.ZIP and put it on my sd card, boot up into the bootloader and go from there? I did that with the earlier PC10IMG.ZIP 2.3.4 that was posted on this thread..can it override that??
Click to expand...
Click to collapse
No no, what this is is a stock 2.3.4 image created from the PC10IMG that will not overwrite hboot, will not kick you back to stock recovery, will not update your radio and is rooted.
Just flash it with CWM.

just wanted to say this worked to upgrade the leaked 2.3.3 to 2.3.4 . you lose your apps but that's not a big deal

thanks!!! i had the leaked 2.3.3 and was gonna go through the painful process of downgrading then upgrading to 2.3.4
but this file saved all that work! wuhu!

What is the diff between 2.3.3 and 2.3.4?
Sent from my T-Mobile G2 using XDA App