Related
----------------------------------------------------
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
I'd like to use the new radio with my oem Donut. Is it as simple as taking the file from one of the update guides and flashing it in the traditional manner? I'm kind of noobish so I'm reluctant to try to take one piece of a Froyo update guide and flash the radio. I'm not really in the market for a sleek black paperweight.
I wouln't do it!
This has BAD IDEA written all over it please don't try this. That being said why not upgrade to the official FROYO? I know it's hard to fathom after seeing ECLAIR in action but it truly is a totally different and better experience.
QUESTION: What does DONUT have that you like so much?
Edubyah said:
This has BAD IDEA written all over it please don't try this. That being said why not upgrade to the official FROYO? I know it's hard to fathom after seeing ECLAIR in action but it truly is a totally different and better experience.
Click to expand...
Click to collapse
lol, I agree, that's why I posted first.
QUESTION: What does DONUT have that you like so much?
Click to expand...
Click to collapse
SPEED. I tried the TMUS rom posted up here a few days ago and it was ok, much better than other Froyo ROMs I've tried, but still laggy compared to my oem androoted Donut.
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
I'm scared to try this. Is this the radio that came with the T-MOUS Fro-Yo OTA? I wonder why there isn't a thread for it yet.
Moving to General
aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
The hboot? Which hboot are you talking about? The first half of the ota update succeeded but the second half failed so I have the new SPL but not the new radio or OS.
The new radio does work with cm6, well cm6.1 rc1. I flashed it on my wife mt3g 3.5mm awhile ago, everything booted up just fine.
d3vilskid said:
The new radio does work with cm6, well cm6.1 rc1. I flashed it on my wife mt3g 3.5mm awhile ago, everything booted up just fine.
Click to expand...
Click to collapse
Cool, did you or she notice any improvements?
Yea i got to messed with it a little bit more, signal is pretty strong and stays constant, but that might vary from phone to phone, not much to say about the market since it was down a couple days back. Overall she is satisfied with it. Cant wait till it is ported to the 32b phones so we can take advantaged of the extra 10-15mb it frees up.
aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
So I just flash this through recovery as I would any other zip file? Any idea if this is compatible with older roms? If I nandroid back to my oem 1.6 without rolling back to 23.02 will my phone explode? How about Eclair?
If I flash this is it just as easy to flash back to 23.02 if I need to for some reason?
Sorry for all the obsessive questions; I've never flashed a radio before so I don't know what it is that I don't know.
aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
im flashing that radio now onto cm6.1, ill post my results
EDIT: Your .zip file doesnt work. It did nothing, after i flashed and rebooted then shutdown and went into fastboot my radio was still 2.22.23.02.
Foo_Blyat said:
im flashing that radio now onto cm6.1, ill post my results
EDIT: Your .zip file doesnt work. It did nothing, after i flashed and rebooted then shutdown and went into fastboot my radio was still 2.22.23.02.
Click to expand...
Click to collapse
It worked for me, except it caused a bootloop because it's not compatible with the CM6 kernel, or at least ezterry's CM6 kernel. I had to flash back to 2.22.23.02.
If you're not using the oem t-mobile/android kernel, don't flash this radio.
I really want to know if this radio is compatible with oem Donut.
Came to my attention today that many rooted Eris users do not have an eng bootloader. Likely due to use of our one click, or other root methods besides the original ENG RUU. I could of sworn I had posted this mid 2010, but was unable to find it today when I needed it.
Here you go, confirmed working with RA Amon's recovery. Not tested with clockwork. Please check the md5sum before flashing.
ENG hboot allows use of more fastboot commands (great for recovering ""bricks""), and removes signature checks on images flashed through fastboot/hboot.
If you are unsure how to figure out which bootloader you have, then you don't need this file.
For users with 1.49.x bootloaders you can flash this
8d69c3fd10238094f0c6d84385e7cff5 eris_eng_hboot.zip
http://www.multiupload.com/25XWSSWTCJ
For users with 1.46 or 1.47 bootloaders, you have more work to do
first follow this guide
http://forum.xda-developers.com/showthread.php?t=725047
then use bftb0's flashback to get the lastest radio
http://forum.xda-developers.com/showthread.php?t=792026
then fastboot the recovery back in and flash the rom of your choice.
With Love,
AndIRC
Thank you, I actually used the first one you had posted last yr, trackball went out and got a replacement Eris, just used one click this time and used your original one. It worked great, thanks for work, I'm sure alot of people will appreciate this
gracias.
10char
jcase said:
I could of sworn I had posted this mid 2010, but was unable to find it today when I needed it.
Click to expand...
Click to collapse
jcase,
Yep, you posted this on 13th July 2010, 11:09 PM:
How To Install Engineering bootloader FOR LEAK ROOTERS
Cheers!
Is this any different from the version that doesn't work on the 1.47.0000 S-ON bootloader, and may brick phones with 1.46.0000 S-ON? See http://forum.xda-developers.com/showpost.php?p=10711166&postcount=7
Just asking - I'd hate to see somebody brick their phone if they weren't aware.
doogald said:
Is this any different from the version that doesn't work on the 1.47.0000 S-ON bootloader, and may brick phones with 1.46.0000 S-ON? See http://forum.xda-developers.com/showpost.php?p=10711166&postcount=7
Just asking - I'd hate to see somebody brick their phone if they weren't aware.
Click to expand...
Click to collapse
Well, I unpacked the eris_eng_hboot.zip and it contains the hboot.img file that is identical to the spl.bin file that is in the erisengspl.zip file.
So, I do indeed think its the same thing...
Looks like this is safe for the 2.1 leakers to install since they have the 1.49.0000 S-ON bootloaders, and is harmless (but ineffective) for a 1.47.0000 S-ON phone but potentially sketchy (bricky ) on the aforementioned 1.46.0000 S-ON phones.
I'll leave the final word on this to bftb0 and jcase, though...
scary alien said:
Well, I unpacked the eris_eng_hboot.zip and it contains the hboot.img file that is identical to the spl.bin file that is in the erisengspl.zip file.
So, I do indeed think its the same thing...
Looks like this is safe for the 2.1 leakers to install since they have the 1.49.0000 S-ON bootloaders, and is harmless (but ineffective) for a 1.47.0000 S-ON phone but potentially sketchy (bricky ) on the aforementioned 1.46.0000 S-ON phones.
I'll leave the final word on this to bftb0 and jcase, though...
Click to expand...
Click to collapse
Apparently I did post this last year, in .zip format on another forum, and bftb0 posted it here. Sorry for the repost.
I was unaware of issue with the 1.46/1.47 bootloaders, but I had amended the post with a method that will work for them (as I used this method on my original 1.46 and 1.47 Eris-es).
Any chance at getting these files re-upped to a different file host since mltiupload is dead?
williams1978 said:
Any chance at getting these files re-upped to a different file host since mltiupload is dead?
Click to expand...
Click to collapse
Here you go: View attachment erisengspl.zip
MD5 checksum: df014009668389ef145fbb047b5ec56c *erisengspl.zip
All due cautions apply--wouldn't use this on a 1.46.0000 S-ON device (see doogald's post above).
jcase said:
Came to my attention today that many rooted Eris users do not have an eng bootloader. Likely due to use of our one click, or other root methods besides the original ENG RUU. I could of sworn I had posted this mid 2010, but was unable to find it today when I needed it.
Here you go, confirmed working with RA Amon's recovery. Not tested with clockwork. Please check the md5sum before flashing.
ENG hboot allows use of more fastboot commands (great for recovering ""bricks""), and removes signature checks on images flashed through fastboot/hboot.
If you are unsure how to figure out which bootloader you have, then you don't need this file.
For users with 1.49.x bootloaders you can flash this
8d69c3fd10238094f0c6d84385e7cff5 eris_eng_hboot.zip
http://www.multiupload.com/25XWSSWTCJ
For users with 1.46 or 1.47 bootloaders, you have more work to do
first follow this guide
http://forum.xda-developers.com/showthread.php?t=725047
then use bftb0's flashback to get the lastest radio
http://forum.xda-developers.com/showthread.php?t=792026
then fastboot the recovery back in and flash the rom of your choice.
With Love,
AndIRC
Click to expand...
Click to collapse
good job
could anyone re-upload the eris_eng_hboot.zip for the 1.49 hboot, please?
Swifty31703 said:
could anyone re-upload the eris_eng_hboot.zip for the 1.49 hboot, please?
Click to expand...
Click to collapse
Wow! Holy Eris resurrection, Batman!
I think I've got it on my home PC...I'll look for it and upload it then after I get home from work (won't be for several hours, though).
scary alien said:
Wow! Holy Eris resurrection, Batman!
I think I've got it on my home PC...I'll look for it and upload it then after I get home from work (won't be for several hours, though).
Click to expand...
Click to collapse
Actually, check post #9 above (first/previous page)...I've already got it uploaded in that post.
Cheers and best of luck!
scary alien said:
Actually, check post #9 above (first/previous page)...I've already got it uploaded in that post.
Cheers and best of luck!
Click to expand...
Click to collapse
Yeah, I got bored and pulled out the old eris to tinker with. Thank you.
jcase said:
Came to my attention today that many rooted Eris users do not have an eng bootloader. Likely due to use of our one click, or other root methods besides the original ENG RUU. I could of sworn I had posted this mid 2010, but was unable to find it today when I needed it.
Here you go, confirmed working with RA Amon's recovery. Not tested with clockwork. Please check the md5sum before flashing.
ENG hboot allows use of more fastboot commands (great for recovering ""bricks""), and removes signature checks on images flashed through fastboot/hboot.
If you are unsure how to figure out which bootloader you have, then you don't need this file.
For users with 1.49.x bootloaders you can flash this
8d69c3fd10238094f0c6d84385e7cff5 eris_eng_hboot.zip
http://www.multiupload.com/25XWSSWTCJ
For users with 1.46 or 1.47 bootloaders, you have more work to do
first follow this guide
http://forum.xda-developers.com/showthread.php?t=725047
then use bftb0's flashback to get the lastest radio
http://forum.xda-developers.com/showthread.php?t=792026
then fastboot the recovery back in and flash the rom of your choice.
With Love,
AndIRC
Click to expand...
Click to collapse
Haha.... Just looking back to my first android and rooting experience... My how things have changed [emoji2]
whojabacod said:
Haha.... Just looking back to my first android and rooting experience... My how things have changed [emoji2]
Click to expand...
Click to collapse
Yep! :good:
Those were the days! But many of the "root" p base) concepts remain the same, eh?
I still have my Eris (sitting right above my monitor on a shelf ) and boot it up occasionally.
True! Root concepts are the same .. I did it before the one click all commands .. I miss mine sometimes ... The little ball lighting. Up the original play store with only a hand full of apps... I could query "root" and count the apps my hand .. Now its just crazy and mostly phishing and ads
Phandroid is reporting the official G2 gingerbread ROM has been leaked, anyone been brave enough to try it out?
link removed because i'm a new user and it won't let me post it
Um it's in the development thread. Did you look?
Sent from my HTC Vision using XDA Premium App
Been out yesterday posted by football and yes it gave my soft brick a revival!!
david279 said:
Um it's in the development thread. Did you look?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Just saw that thread ( http://forum.xda-developers.com/showthread.php?t=1074852 ). I wasn't quite sure why a final T-mo rom would be in the development forum, seems a little counter intuitive? I guess the dev forum really means the rom forum. anyway, thanks guys.
izzelsizzel said:
Just saw that thread ( http://forum.xda-developers.com/showthread.php?t=1074852 ). I wasn't quite sure why a final T-mo rom would be in the development forum, seems a little counter intuitive? I guess the dev forum really means the rom forum. anyway, thanks guys.
Click to expand...
Click to collapse
step back and think about it.....
wouldnt you want a rom dev to get their hands on it to work their magic?
izzelsizzel said:
guess the dev forum really means the rom forum. anyway, thanks guys.
Click to expand...
Click to collapse
Its got a lot more than just ROMs, but also kernels, radios, guides, and other tools. Some stuff are custom or modded, some are stock tools that developers and others will find useful.
Please help -- how to flash this new stock gingerbread rom to a rooted g2
I have a rooted G2 running CM7, but the gps is totally dead. I'm too much of a noob to flash a new radio, which I think would do the trick. Flashing this stock gingerbread rom seems like the perfect solution because it includes an updated radio and i am just sure it will fix the gps problem.
I bought the phone rooted and I know how to flash new rooted roms through clockwork (so easy), but I have absolutely no idea how to flash a rom like this that updates everything.
I'm sure this question has been asked here before, but can someone just point me to a step-by-step instructions about how to flash this particular stock gingerbread rom to a g2 that is rooted and has clockwork installed?
Thanks~! This is my first post.
sship said:
I have a rooted G2 running CM7, but the gps is totally dead. I'm too much of a noob to flash a new radio, which I think would do the trick. Flashing this stock gingerbread rom seems like the perfect solution because it includes an updated radio and i am just sure it will fix the gps problem.
I bought the phone rooted and I know how to flash new rooted roms through clockwork (so easy), but I have absolutely no idea how to flash a rom like this that updates everything.
I'm sure this question has been asked here before, but can someone just point me to a step-by-step instructions about how to flash this particular stock gingerbread rom to a g2 that is rooted and has clockwork installed?
Thanks~! This is my first post.
Click to expand...
Click to collapse
Flashing a radio is easy. Just follow the steps in the radio thread:
http://forum.xda-developers.com/showthread.php?t=970809
I know the second method (fastboot and radio.img files) is supposed to be safer. But that looks like it might be over your head, and you need the Eng Hboot to do it.
Flashing a ROM is easy, too. Just move the file to your SD card, and flash from ROM Manager. You will see an option "Install ROM from SD Card". Browse to the file, and the rest is the same as if you downloaded the ROM using ROM Manager.
Thanks, but a few more questions . . .
redpoint73 said:
Flashing a ROM is easy, too. Just move the file to your SD card, and flash from ROM Manager. You will see an option "Install ROM from SD Card". Browse to the file, and the rest is the same as if you downloaded the ROM using ROM Manager.
Click to expand...
Click to collapse
Thanks for the reply! I think you are underestimating how new I am to this, though. My question is really this: does it matter, when flashing the new gingerbread rom for g2 that just came out, that the rom is not just a rom, but also a radio and everything else? it is titled in the "PC10IMG" form, which seems to me, from reading other threads, to be a special thing.
[full title: PC10IMG_Vision_Gingerbread_S_TMOUS_2.13.531.8_Radio_12.52.60.25_26.08.04.30_M3_release_188635_signed]
also, would you recommend that i wipe stuff before flashing? when the person who flashed my phone with me last time did it, he wiped dalvik cache and two others (can't remember which, or where he found them in recovery), and user data as well. but if you go to do it within clockwork, it doesn't ask you to do that, does it? again, i'm sure there is a thread about this somewhere.
sorry sorry to be so new to this! and thanks a ton for the help.
sship said:
Thanks for the reply! I think you are underestimating how new I am to this, though. My question is really this: does it matter, when flashing the new gingerbread rom for g2 that just came out, that the rom is not just a rom, but also a radio and everything else? it is titled in the "PC10IMG" form, which seems to me, from reading other threads, to be a special thing.
[full title: PC10IMG_Vision_Gingerbread_S_TMOUS_2.13.531.8_Radio_12.52.60.25_26.08.04.30_M3_release_188635_signed]
also, would you recommend that i wipe stuff before flashing? when the person who flashed my phone with me last time did it, he wiped dalvik cache and two others (can't remember which, or where he found them in recovery), and user data as well. but if you go to do it within clockwork, it doesn't ask you to do that, does it? again, i'm sure there is a thread about this somewhere.
sorry sorry to be so new to this! and thanks a ton for the help.
Click to expand...
Click to collapse
well, it's a bit complicate.
supposedly the rom will return your phone to a totally stock state, which will give you the new radio etc, but you will not have root - this was already confirmed. One other forum member mentioned that he flashed the rom and did not loose S-OFF, which is a controversy...
update: lol, dude having CM on your phone means you already have clockwork installed. you just need the /system part of the leak and it's available here: http://forum.xda-developers.com/showthread.php?t=1074852
Really all he needs to do is run vision efs wipe. This been gone over a million times. CM + gps broke = needing efs wipe. No need to get into radios and all that just yet.
Sent from my HTC Vision using XDA Premium App
you can solve your gps issues by following two basics:
1. match libs in /system/libs with your radio version,
2. wipe two partitions like it is explained here: http://forum.xda-developers.com/showthread.php?t=1028405
You don't need the new rom, though - it still has the 2 muted seconds when receiving an incoming call - for me that is the no go.
sship said:
Thanks for the reply! I think you are underestimating how new I am to this, though. My question is really this: does it matter, when flashing the new gingerbread rom for g2 that just came out, that the rom is not just a rom, but also a radio and everything else? it is titled in the "PC10IMG" form, which seems to me, from reading other threads, to be a special thing.
[full title: PC10IMG_Vision_Gingerbread_S_TMOUS_2.13.531.8_Radio_12.52.60.25_26.08.04.30_M3_release_188635_signed]
also, would you recommend that i wipe stuff before flashing? when the person who flashed my phone with me last time did it, he wiped dalvik cache and two others (can't remember which, or where he found them in recovery), and user data as well. but if you go to do it within clockwork, it doesn't ask you to do that, does it? again, i'm sure there is a thread about this somewhere.
sorry sorry to be so new to this! and thanks a ton for the help.
Click to expand...
Click to collapse
I thought you were talking about the version of the leak that is mentioned in the last post (#10) and also mentioned above in post #4, which is pre-rooted. Thats the one you want. Flash from ROM Manager.
If you are talking about flashing this one:
http://forum.xda-developers.com/showthread.php?t=1074391
This is the official ROM, and as stated in the previous post, you will lose root. So you probably want to avoid this.
PC10IMG.ZIP files are flashable from Hboot (CWM not required). But since you have Clockwork, I believe you can flash any ROM or patch, as long as its a ZIP file. Its safer to flash from CWM anyway, so avoid Hboot for flashing ROMs.
Not positive, but I think you can keep your data since you are going between similar ROMs (Gingerbread, non-Sense). Wiping dalvik and cache are advisable. Not doing so when switching ROMs can lead to random bugs, and there is no real reason to not wipe them. You can wipe dalvik and cache in recovery. If you want to wipe data, you can also do that in recovery, under "advanced". But you will lose all your user data.
If you flash from ROM Manager, it will ask if you want to wipe. But I've never been clear on what all exactly is wiped (dalvik, cache, data). It might be all 3 of those.
Sorry, I've just stated a bunch of things I'm not completely sure about. So hopefully somebody else can confirm these.
The good news is, do a backup of your current ROM in ROM Manager before you flash anything, and if you screw up anything, you can just go into recovery and load your backup.
please help -- do not want to brick
petarpLab said:
well, it's a bit complicate.
supposedly the rom will return your phone to a totally stock state, which will give you the new radio etc, but you will not have root - this was already confirmed. One other forum member mentioned that he flashed the rom and did not loose S-OFF, which is a controversy...
Click to expand...
Click to collapse
I actually would prefer this to flashing a version of this rom that someone else has extracted/altered, however little. My fear is two things:
1 -- Will it brick my phone to flash a PCIMG file? (see here: http://forum.xda-developers.com/showthread.php?t=838484)
2 -- what do I have to do differently to flash a PCIMG file other than what I normally would do in clockwork to flash another rom (for example a CM rom)
THANKS!
xsteven77x said:
Really all he needs to do is run vision efs wipe. This been gone over a million times. CM + gps broke = needing efs wipe. No need to get into radios and all that just yet.
Click to expand...
Click to collapse
I have tried that, to no avail. I see others who have tried that and failed, and things seem to get tricky after that. I agree, I would rather avoid the nitty gritty stuff.
So I am devastated to see that there is no lock animation =(. That was something I was really looking forward to, despite the insignificance.
Sent from my T-Mobile G2 using XDA App
sship said:
I actually would prefer this to flashing a version of this rom that someone else has extracted/altered, however little. My fear is two things:
1 -- Will it brick my phone to flash a PCIMG file? (see here: http://forum.xda-developers.com/showthread.php?t=838484)
2 -- what do I have to do differently to flash a PCIMG file other than what I normally would do in clockwork to flash another rom (for example a CM rom)
THANKS!
Click to expand...
Click to collapse
My opinion, you're better off flashing the rooted ROM. If you flash the official PC10IMG.ZIP, you will lose root, and not be able to get it back without downgrading (negating the purpose of flashing the official ROM in the first place).
Are you worried about malicious, or accidentally harmful modifications to the ROM (in the rooted version of the leak)? I don't worry much about ROMs for reputable developers. But admittedly, I don't know anything about that user that posted the rooted version of the leak.
In response to your questions:
1) As the thread you posted indicates, its safer not to flash those files unless you know exactly what you are doing.
2) I think you can flash from Clockwork. But as I said, if you aren't sure what you are doing, its not a good idea. You will lose root, and I think some people have also gotten S-On by flashing the official ROMs also. I which case, you may be pretty screwed (as far as getting root), since you can't flash other ROMs with S-On.
Alright so I've reading through all sorts of different forums and feel lost and exactly what to do. I downloaded the official 2.3 update ROM for the G2 that Football had released off of a mirrored site from my phone's browser then renamed it PC10IMG and moved to the root of the SD card. I then did the whole volume down + power button to load the zip but for some reason it says:
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010,17:59:38
SD checking...
Loading...[PC10DIAG.zip]
No image!
Loading...[PC10DIAG.nbh]
No image or wrong image!
Loading...[PC10IMG.zip]
No image!
Loading...[PC10IMG.nbh]
No image or wrong image!
I have no idea what to do or anything so help would be much appreciated. Now I would post this in that forum but because I just recently joined this site it will not allow me to do so. So, yea. Thanks.
Mr. Shaggy said:
Alright so I've reading through all sorts of different forums and feel lost and exactly what to do. I downloaded the official 2.3 update ROM for the G2 that Football had released off of a mirrored site from my phone's browser then renamed it PC10IMG and moved to the root of the SD card. I then did the whole volume down + power button to load the zip but for some reason it says:
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010,17:59:38
SD checking...
Loading...[PC10DIAG.zip]
No image!
Loading...[PC10DIAG.nbh]
No image or wrong image!
Loading...[PC10IMG.zip]
No image!
Loading...[PC10IMG.nbh]
No image or wrong image!
I have no idea what to do or anything so help would be much appreciated. Now I would post this in that forum but because I just recently joined this site it will not allow me to do so. So, yea. Thanks.
Click to expand...
Click to collapse
Make sure it is named PC10IMG.zip and not PC10IMG.zip.zip
Sent from my LG-P990 using XDA Premium App
So I checked it out and it's named PC10IMG.zip so I don't know what could be wrong. I find it weird that I'm the only one having this problem.
As there are more and more firmware coming, people will be installing them more and more... Same thing about people that wants to go back to stock. This thread could be considered useless and will make people say "yeah man, I knew it I'm not so stupid" that's OK! You're right.
I just wanted to remember that you shouldn't ever ever ever S-ON your HBOOT if it is edited by someone else! This will immediately brick your device, if you want to check do it. You need first to replace your current HBOOT with a stock one and then you'll be good to go.
@Sneakyghost:
* Before resetting Security to ON (S-ON) you MUST flash a stock/unchanged HBOOT! Your device will brick instantly if you set Security ON and reboot on a modified HBOOT!
Click to expand...
Click to collapse
In all the hboot threads it clearly states this
And it's not locking your bootloader that bricks it, it's s-on that does it
Sent from my HTC One using Tapatalk
superchilpil said:
In all the hboot threads it clearly states this
And it's not locking your bootloader that bricks it, it's s-on that does it
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I thought it was if you: fastboot oem writesecureflag -3 it will check if it's a modified hboot.
Sent from my HTC One using Tapatalk
I knew That simply locking the hboot would have bricked the device
Sent from my HTC One using XDA Premium 4 mobile app
@superchilpil you were right, I've edited the OP now and it should be ok now... :good:
matt95 said:
@superchilpil you were right, I've edited the OP now and it should be ok now... :good:
Click to expand...
Click to collapse
Wow, I think I've read about 20 threads so far about this, and this is the first time I've seen this corrected... Lots of threads always mentioned locking the bootloader as the issue if you don't have stock hboot.
I actually had a few questions about this,
1. Does the hboot version have to match that of the firmware ? ( 1.54 for 2.24.x.x for example ?) or does it simply have to be any stock hboot ?
2. Are there any differences between hboot for various carriers ?
3. I've read multiple times that running an RUU will not allow you to downgrade unless you have superCID, I don't understand this. I thought the RUU wouldn't run if the CID didn't match. From what I had understood previous to reading that is simply that an RUU cannot be used to downgrade the firmware or the hboot version, that can only be done manually with S-off
Thank you for your time and for the clarification!
ieldra said:
Wow, I think I've read about 20 threads so far about this, and this is the first time I've seen this corrected... Lots of threads always mentioned locking the bootloader as the issue if you don't have stock hboot.
I actually had a few questions about this,
1. Does the hboot version have to match that of the firmware ? ( 1.54 for 2.24.x.x for example ?) or does it simply have to be any stock hboot ?
2. Are there any differences between hboot for various carriers ?
3. I've read multiple times that running an RUU will not allow you to downgrade unless you have superCID, I don't understand this. I thought the RUU wouldn't run if the CID didn't match. From what I had understood previous to reading that is simply that an RUU cannot be used to downgrade the firmware or the hboot version, that can only be done manually with S-off
Thank you for your time and for the clarification!
Click to expand...
Click to collapse
1. Matching firmware/hboot is always the best route possible as it can minimize any issues that may arise, so I suggest it.
2.As far as compatibility issues there aren't any, the hardware on all these devices are almost exactly alike so running another hboot is quite possible. Although I suggest keeping to your carriers hboot to minimize issues. Or atleast keep a backup of yours
3.You can downgrade only if you are S-OFF, otherwise you can only upgrade or flash the corresponding firmware you're currently on. SuperCID only allows you to flash RUUs/firmware from other carriers or regions. CID stands for Carrier Identification. So even with supercid you can't downgrade, there are security measures in place to stop you from downgrading you hboot without s-off, it either won't write or you will end up with a brick.
Sent from my HTC One using Tapatalk