Related
Currently have my phone rooted and running Cynogenmod 6 test 8 with the stock radio. This is an issue because I can't get my camcorder to work. I have been scared to update my radio in the past because 1, I didn't want to mess it up and 2, because I wanted to be able to go back to 100% stock at any time for warranty claims and what not.
With the unrevokedforever tool it looks like it is not easier to update radios on in any direction you want. So here are my questions.
1. Is there a way for me to backup my current radio prior to loading the latest radio?
2. Is there a place to download various radio versions to troubleshoot problems 1 radio might have with a rom?
3. Is there any way to roll back after applying the unrevokedforever fix? (can I change it back to s-on?)
I really want to try out skyraider but my understanding is I need a newer radio to do so.
There are many threads on rolling back your Radio.
As for "forever" the answer is no. While I hope/believe unrEVOked may be working on "S-ON" they have not done so yet. Since so many of these phones ultimately go bad (including blown speaker), people who have run "forever" are at risk with Verizon if they check since unrEVOked did not yet release S-ON.
If you do return your phone with S-OFF, please reply back if Verizon refuses to accept it or charges you for a new phone. There is considerable debate (in line with the requests for S-ON to be released) if VZW will refuse to replace obviously bad hardware, because S-OFF is showing.
Thanks!
Are you recommending that I update my radio the old fasion way until they come out with the s-on tool?
jdmba said:
There are many threads on rolling back your Radio.
Click to expand...
Click to collapse
I'm aware that there are tons of threads out there on this topic but thats kind of the problem. It seems everyone has a different method for doing this and they are all slightly confusing. With something as dangerous as updating the radio I don't want to be guessing anywhere along the way.
Can you recommend a good complete easy to follow tutorial on how to upgrade the radio to 2.x as well as a guide for downgrading back to stock if need be? It would be nice to find a guide that talked about both but I haven't found one yet.
Any ROM based off the 8/1 leak with Sense has a working camcorder. You can simply install that ROM and have a working camera/camcorder.
I thought those ROMs required the 2.x radio update. Do you have a list of ROMs based off the 8/1 leak? I thought the 8/1 leak was unstable.
trevoryour said:
I thought those ROMs required the 2.x radio update. Do you have a list of ROMs based off the 8/1 leak? I thought the 8/1 leak was unstable.
Click to expand...
Click to collapse
List of roms:
Sky raider
Aiccucs
jdfroyo
yasr
The actual 8/1 leak
That's all I know of....
sent from jdfroyo v2.0 EVO-lution
Sky Raider is the one I wanted to use but I read somewhere that it requires the 2.x radio.
All of the ones I listed are required to have the
2.x radio.....I cooked one of them, so I would know
sent from jdfroyo v2.0 EVO-lution
jdmba said:
There are many threads on rolling back your Radio.
As for "forever" the answer is no. While I hope/believe unrEVOked may be working on "S-ON" they have not done so yet. Since so many of these phones ultimately go bad (including blown speaker), people who have run "forever" are at risk with Verizon if they check since unrEVOked did not yet release S-ON.
If you do return your phone with S-OFF, please reply back if Verizon refuses to accept it or charges you for a new phone. There is considerable debate (in line with the requests for S-ON to be released) if VZW will refuse to replace obviously bad hardware, because S-OFF is showing.
Thanks!
Click to expand...
Click to collapse
I'll post my results sometime in the immediate future as well. I jut had to order a fru today. My phone started with random reboots and boot loops this past weekend. It's a double whammy or wonderment for me... am I going to get (justifiably) charged for the replacement and am I about to enter refurb hell? We shall see.
Just as jdmba said there's currently no way to revert back to s-on.
If you look through this users videos you should find how to upgrade and downgrade your phone (for those warrenty issues).
Link: youtube.com/user/mejdam
(Sorry for no link, not enough posts)
Sent from my ADR6300 using XDA App
Thanks
najaboy said:
I'll post my results sometime in the immediate future as well. I jut had to order a fru today. My phone started with random reboots and boot loops this past weekend. It's a double whammy or wonderment for me... am I going to get (justifiably) charged for the replacement and am I about to enter refurb hell? We shall see.
Click to expand...
Click to collapse
Wish you luck ... please remember it can take up to a month to see if VZW will refuse the warranty (which will likely take the form of a charge on your monthly bill). Let us know ... and fingers crossed that unrEVOked releases S-ON soon
Ok so that this is up front so that everyone understands.. I do not care about root and have no plans to root this phone for a while. (This is my primary phone and I need it working and not bricked)< I have personal reasons for not wanting root at this time so please don't ask.
Now my question is the following:
If I extract the rom.zip file from RUU that was leaked yesterday will I be able to just rename the file to PB31IMG.zip and place it in the root of my SD card. Then boot into hboot and apply the update?
From the threads I have found so far on how to do this state that the phone will do a quick reboot while applying this update. This is caused by the updating of hboot from what I have see. Then I'm suppose to just tell it again to apply the update. < Is Applying the update the second time safe?
Will this work to flash my phone to the new version of the android, hboot, radio and so forth? I just want to apply the update instead of waiting days or weeks for verizon to finally push it to my phone via OTA.
I'm currently with the following settings.
S-On
Hboot .77
Stock Android 2.1 update-1(not rooted)
radio 100
Additional Information.
I've tried just using the RUU but due to driver conflicts it keeps giving me the USB error. The most I've ever gotten was the phone into the bootloader then the RUU loses connection. Tried this on 3 machines now and it still fails. And yes I've installed HTC Sync only on 2 of those 3 machines and it still fails..
To be honest, I would say just wait for the OTA, Verizon themselves have confirmed it has been/will be released today 8/27. Then there will be no worrying, since you don't want root this would be the best way.
boomertwo said:
Ok so that this is up front so that everyone understands.. I do not care about root and have no plans to root this phone for a while. (This is my primary phone and I need it working and not bricked)< I have personal reasons for not wanting root at this time so please don't ask.
Now my question is the following:
If I extract the rom.zip file from RUU that was leaked yesterday will I be able to just rename the file to PB31IMG.zip and place it in the root of my SD card. Then boot into hboot and apply the update?
From the threads I have found so far on how to do this state that the phone will do a quick reboot while applying this update. This is caused by the updating of hboot from what I have see. Then I'm suppose to just tell it again to apply the update. < Is Applying the update the second time safe?
Will this work to flash my phone to the new version of the android, hboot, radio and so forth? I just want to apply the update instead of waiting days or weeks for verizon to finally push it to my phone via OTA.
I'm currently with the following settings.
S-On
Hboot .77
Stock Android 2.1 update-1(not rooted)
radio 100
Additional Information.
I've tried just using the RUU but due to driver conflicts it keeps giving me the USB error. The most I've ever gotten was the phone into the bootloader then the RUU loses connection. Tried this on 3 machines now and it still fails. And yes I've installed HTC Sync only on 2 of those 3 machines and it still fails..
Click to expand...
Click to collapse
I'm sorry this has nothing to do with what you're asking, I've read, and don't know sorry man, but I do have a quick question for you. I see you have never rooted, or maybe or have, I thought maybe you hadn't for some reason, but anyway, I see you HBOOT it .77, how long have you had your phone since?
Yes I had rooted the phone recently for about 2 weeks then it got messed up but thanks to an unrevoked member I was able to recover the phone. It wasn't bricked or anything but some how the NAM was messed up which prevented me from using *228 to update roaming or my ability to activate the phone after a factory reset. I do remember it having hboot .79 before rooting though.
Update: I verified that the hboot in the stock restore img file I used had only hboot 77 in it and not 79. This means I downgraded to 77 without knowing it at first. (From the threads I have read it is stated that .77 and .79 are interchangeable so I don't think I need to worry about it when the ota comes I hope..)
I've had it for about 3 months now so I'm out of the return policy and I do like the phone and have no intention of returning it.
After trying root out for those 2 weeks I found that for me I didn't really gain anything that seemed worth it for my personal needs.
Also I like to tinker with stuff but since I'm in a 2 year contract I rather not take the risk of bricking it and having to pay for the next 2 years for service I can't even use due to my own fault of breaking the device.
Right now I'm just wondering if it is safe to apply the file that can be found in the ruu without root and without breaking the device since it has the same build number and radio number as the update that verizon has stated on the update page.
.77
I am on my third incredible, and all 3 shipped to me with v.77. Last one shipped was 8/9 (wow, maybe this one is a keeper).
jdmba said:
I am on my third incredible, and all 3 shipped to me with v.77. Last one shipped was 8/9 (wow, maybe this one is a keeper).
Click to expand...
Click to collapse
were these all brand new phones, refurbs..?
To my understanding of this whole .77, .79 HBOOT is that these two are interchangeable and doesn't matter which one you have. I was just curious because at first I used the RUU that gave me software 1.22.605.0 and the latest is 1.22.605.2 and I never got an OTA update for the latest 2.1. but I think this is normal since the servers are doing the new thing.
and from what I think, if you had .77, and got the OTA for the latest 2.1 that came out a while ago, it kept the .77, but if you did the latest 2.1 through the RUU on ur computer instead of OTA it updated the HBOOT to .79 as well.
This is how it was with the Droid Eris with the leaks and stuff which blocked you out of root.
...
BlazeD OnE said:
were these all brand new phones, refurbs..?
Click to expand...
Click to collapse
Phone # 1 - New ... would get hotter and hotter (even when not in use) until it would enter a reboot cycle. It would also reboot randomly during the day.
Phone # 2 - Refurb ... got it with a bad speaker, but otherwise it worked perfectly.
Phone # 3 - Refurb ... still going.
boomertwo said:
Ok so that this is up front so that everyone understands.. I do not care about root and have no plans to root this phone for a while. (This is my primary phone and I need it working and not bricked)< I have personal reasons for not wanting root at this time so please don't ask.
Now my question is the following:
If I extract the rom.zip file from RUU that was leaked yesterday will I be able to just rename the file to PB31IMG.zip and place it in the root of my SD card. Then boot into hboot and apply the update?
From the threads I have found so far on how to do this state that the phone will do a quick reboot while applying this update. This is caused by the updating of hboot from what I have see. Then I'm suppose to just tell it again to apply the update. < Is Applying the update the second time safe?
Will this work to flash my phone to the new version of the android, hboot, radio and so forth? I just want to apply the update instead of waiting days or weeks for verizon to finally push it to my phone via OTA.
I'm currently with the following settings.
S-On
Hboot .77
Stock Android 2.1 update-1(not rooted)
radio 100
Additional Information.
I've tried just using the RUU but due to driver conflicts it keeps giving me the USB error. The most I've ever gotten was the phone into the bootloader then the RUU loses connection. Tried this on 3 machines now and it still fails. And yes I've installed HTC Sync only on 2 of those 3 machines and it still fails..
Click to expand...
Click to collapse
in theory that should work.
k.electron said:
in theory that should work.
Click to expand...
Click to collapse
Well I took the plunge and can confirm that the method in my original post does work and without a hitch(For me at least.)I did this after reading another question thread that had a guy basically asking the same thing and was recommended just to follow to step 6. I cannot link to anything yet so I will just give you the thread title that is located in the Q&A section of this forum for the droid incredible.
Thread Title: "[Q] Applying RUU update to stock phone"
The phone did however reboot the bootloader and put me into fastboot. I did not pull the battery but instead selected bootloader again and it continued the update on its own.
I'm successfully not root and s-on with android 2.2(HTC stock)
Hboot .92
Stock Recovery.
*Before you say it.. I know I'm now not able to get root till unrevoked or another dev team releases new tools for this version. I did this by choice*
*I in no way will recommend anyone to do this and will not take responsibility for your phone being turned into a paper weight* < You have been warned..
Sooooo.. anyone want to clarify how to extract rom.zip from the RUU please?
Just download the extracted ROM. It's on page 6 or 7 in the RUU thread.
NinjaRicky said:
Sooooo.. anyone want to clarify how to extract rom.zip from the RUU please?
Click to expand...
Click to collapse
did you get it?
Hi all,
I love this forum as it's got so much useful info so have just joined as I'm a little unsure of a few things and would really appreciate any help/advice.
Firstly, the big question, can I downgrade from 2.2 to 2.1 on a T-Mobile UK branded device without risking losing the warranty (only got the phone in March - just in case any hardware defects as I had the camera break a month after I got the phone!). I have read numerous guides and they seem to be associated with rooting and what confuses me is the stock roms I'm finding are for 1.14 not 2.1?
The reason is because (there may be an answer to this somewhere but have searched loads and can't find it) the Webkit browser on 2.2 seems to constantly crash. I didn't have the issue on 2.1 and have had the phone repaired twice, the issue occurs straight after a factory reset and is definitely an issue with 2.2 on T-Mobile UK branded firmware at least. T-Mobile UK assured me it was fixed but it certainly isn't as it crashed twice (just disappeared) within 5 minutes of browsing and later in the evening came up with the 'force close' error when browsing.
I loved using the stock provided browser over Opera/Skyfire etc and it was fine on 2.1...
So I am wondering whether T-Mobile UK have just bodged the firmware and whether rooting/debranding would give me a very stable version of webkit?
I had this with my first Wildfire after upgrading in December 2010, after two repairs they couldn't fix it so swapped for a new phone in March. The new phone was fine on 2.1 and this issue occurred again straight after the OTA update of 2.2 last night.
I'm really hoping someone can help with the above?
Many thanks in advance
1.14 is the ROM version number, and, is actually Android 2.1. But, you will not be able to downgrade without root. (Atleast easily).
If you wish to take the complex way out to downgrading to 2.1 without rooting and stuff, you can refer this guide here:
http://forum.xda-developers.com/showthread.php?t=921752
Excellent, many thanks 3xeno. I'll have a go at that. I am tempted to try unbranded 2.2 firmware as by the sounds of it the browser crashing issue might be specific to T-Mobile UK. I can't find other people reporting this issue anywhere and its happened to me with two phones, after 2 repairs with ota updates twice and after multiple factory resets.
Do you use webkit and get any crashes at all? I've tried other browsers but prefer the webkit one when it works, would be great if it played flash content like YouTube etc but I'll do some more research on that...
try dolphin browser HD(has many add-on's) or opera Mobile ,these are the best in the line & opera min for more data saving efficiency
Thanks all, I am having a lot of trouble with the SuperOneClick part though.
I have S-ON on boot and the boot loader that ends in 001 does that affect the ability of SuperOneClick to do Temp Root?
All I get is:
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
cannot stat 'C:\Documents and Settings\Marty\Desktop\HTC Downgrade\SuperOneClickv1.5.5\rageagainstthecage': No such file or directory
OK
chmod rageagainstthecage...
Unable to chmod /data/local/tmp/rageagainstthecage: No such file or directory
OK
Running rageagainstthecage...
It just says the last part for ages and never seems to go any further...
Do I need to do S-OFF using Unrevoke or similar?
It shouldn't, since the procedure was performed on an official Froyo release on HBoot 1.01.0001. BTW, You have to press 'Shell Root', not 'Temp Root'. Further make sure USB Debugging and all is on, as the author states.
Hi 3xeno,
I can confirm debugging is on and it is Shell Root I am trying but it just seems to stick on that last stage for ages.
I have the goldcard in, does that matter?
I have also tried unmounting the SD Card as mentioned on another thread?
It shouldn't matter. But, I think this should help you out:
http://forum.xda-developers.com/showpost.php?p=16634853&postcount=139
If you check the 2 posts above it, the user was experiencing similar problems as yours. So, I believe that solution should help.
(That guide is to downgrade to a WWE (Non Branded ROM) with HBoot 1.01.0001, and the 1st step is essentially the same as what you are attempting to do - Downgrade Misc Partition and flash an 'older' ROM)
Good Luck
Thanks 3xeno, I ended up doing the revolutionary thing in those steps and it says S-OFF now with Revolutionary at the top.
I was then able to use a stock RUU and install 2.1 on the phone but it looks different in that the clock widget and icons on the main screen weren't there? It's supposed to be the T-Mobile UK v2.1 firmware I thought?
I thought I might as well use unrEVOKed to root it anyway but I wondered if it was possible to revert it back to the way it was using the factory RUU if I needed any warranty repairs? Would reverting back then change the bootloader screen or is that permanently changed by Revolutionary?
martyp78 said:
Thanks 3xeno, I ended up doing the revolutionary thing in those steps and it says S-OFF now with Revolutionary at the top.
I was then able to use a stock RUU and install 2.1 on the phone but it looks different in that the clock widget and icons on the main screen weren't there? It's supposed to be the T-Mobile UK v2.1 firmware I thought?
I thought I might as well use unrEVOKed to root it anyway but I wondered if it was possible to revert it back to the way it was using the factory RUU if I needed any warranty repairs? Would reverting back then change the bootloader screen or is that permanently changed by Revolutionary?
Click to expand...
Click to collapse
Revolutionary introduces a new userspace issue. It can be fixed by flashing this (Needs Clockworkmod, I hope you had selected Yes to installing Clockworkmod to Revolutionary) -
http://forum.xda-developers.com/showthread.php?t=1156713
To change your bootloader from the Revolutionary one, you will need the HBoot.nb0 file from your TMobile Eclair RUU. Once you obtain that, you will need to follow this guide:
http://forum.xda-developers.com/showthread.php?t=1160251
So, essentially, once you perform this, you are back to factory stock, on a T-Mobile 2.1 ROM. (Essentially summing up my first post, its far easier to root and downgrade. )
Oh, and dont touch Unrevoked. Its not needed at all.
Many thanks 3xeno, really appreciate your help and such quick responses
I actually ended up with root (I think) as the super user icon is in there and I was able to do a nandroid backup on bootup.
Nice to be back to 2.1 though, I might leave it how it is at the moment and keep this info in mind to revert if needed for a warranty claim (fingers crossed it won't be a screen fault!).
One thing I'm really pleased about so far is that it doesn't seem to sync up immediately with my google account and fill my people list with a load of random e-mail addresses which is something I didn't like before.
So far so good, I'll have some fun playing with root now...
Thanks again
Cheers mate.
BTW, You can go to People > Menu Key > View > Check 'Only show Contacts with Phone Numbers'. It may not have synced immediately, but, it will, sooner or later.
EDIT: Did you flash the Sense Fix? If not, then, HTC Setup Wizard (The startup guide which greets you first thing when you boot up after a factory reset) will not work, implying that your Google Account is not setup on the phone. (Or, you'll have to do it manually.) Probably, that's why, its not syncing.
Hi Guys, I posted this in Android Software and Hacking General, but I didn't get a reply. Probably the wrong section!
my HTC Desire GSM is stuck in Fastboot and won't boot into the ROM. The background to this issue is that I installed S-Off and then ClockworkMod and flashed Cyogenmod 7 to see if it would fix a reboot issue on the phone. The damn thing just reboots itself when the CPU is used heavily...
Anywho, after realising that Cyogen wouldn't resolve the issue I flashed the standard Virgin UK rom back over it and upgraded to 2.22.351.2 via the system update feature. The problem was that ClockwordMod was still installed and I had to get rid of it to sent the phone off for repair to Virgin!
So I did further research and found that I could flash HBoot via the AlphaRev.nl downgrader tool. I downloaded it and popped it into the root of my SD card and it flashed the bootloader back to Hboot 0.80.0000. That should have been it, but all of the sudden the phone no longer boots into the Rom. All it does is to power on and then go into Fastboot. That's it! When I try putting the standard Virgin Rom back onto the SD it tries to load it and then says "Main Version is older!" "Update Fail!".
How do I get around this now? The phone doesn't boot, so I can't re-flash S-Off and start again, not am I able to run the stock Virgin Rom within Windows because it complains about the versions.
Is there any ways around this situation? I just want to get the phone back to stock so I can send it to Virgin and get it repaired.
P.S. I *have* used the search function and spent the last 4 hours testing various things but I'm now stuck.
Cheers Guys!
Mich
Well you obviously fckd up with the Downgrader, you should have run it first BEFORE RUU. Also did you flashed Stock Hboot prior to Downgrader? (if you used CM7 earlier)
I never played around with the hboot downgrading etc. so i wont be able to help you but im sure there is some workaround...
as your returning your phone anyway why don't you try the official HTC gingerbread update from the HTC developer site (sorry I don't have a link). It should return your phone to stock and when you get it back you need to use revolutionary to get s-off back. Also, there is a sticky from user bortac which has loads of help and trouble shooting advice.
iain2510 said:
as your returning your phone anyway why don't you try the official HTC gingerbread update from the HTC developer site (sorry I don't have a link). It should return your phone to stock and when you get it back you need to use revolutionary to get s-off back. Also, there is a sticky from user bortac which has loads of help and trouble shooting advice.
Click to expand...
Click to collapse
Any advice that uses the 2.3.3 RUU to fix something is plain bad advice - it can just make your problem a LOT worse.
@OP Go onto my guide, look at RUU problems for help
What you need to do:
-Make a goldcard (there is a tutorial there)
-Flash the WWE RUU
Guys, upgrading to Gingerbread has actually brought the phone back from the dead! =) And I can now return it to Virgin to get it repaired properly. The symptoms are that while the phone is plugged in and charging, and I'm doing stuff (taxing the CPU), the phone will eventually simply rebooting itself. Just *BANG*! And it's gone. And once it starts it's a bit of a run-away thing and just keeps on doing it until you leave the phone alone for a bit. Virgin had a look at it and simply re-flashed it, thinking that they could away with that. Typical, overworked, non-creative call centre workers..... I'm well pissed off with them!
Gonna send it back next week and force them to swap the motherboard or something, cause this is a serious fault with the phone.
Hello everyone, I'm running into a bit of a problem here with my sister's HTC EVO 4G.
You see her phone is a remanufactured replacement model from Sprint, and naturally it has a few minor problems with it. She wasn't thrilled with the battery life, so I rooted and flashed CM7.1 on her phone. She liked the rom and liked the extra battery life after I did some tweaking. Two Months later, for some odd reason, her phone will not connect to the data network at all. I flashed CM 7.2, same problem. Contacted sprint, where they refreshed the signal to the phone, no luck. So I concluded that it was a hardware error. Problem is, Sprint won't work on the phone without the Stock Sense Rom installed. I thought: "No big deal, I'll just flash it back to the stock sense rom" right? WRONG.
Never have I ever been so enraged by a cellphone. No matter what I do, no matter what I try, this phone absolutely REFUSES to go back to the stock rom. I've tried flashing several PC36IMG.zip files from the sdcard in HBOOT, and I have also tried several RUU updates from my PC while having the phone in Fastboot USB mode.
Quick Info:
Phone: HTC EVO 4G
Baseband: 2.15.00.12.19
HBOOT: 2.18.0001
Bootloader = Unlocked
Security = ON (S-ON)
Trying to flash PC36IMG.zip from HBOOT results in the phone loading the zip (with the little vertical progress bar on the side) and after loading completely, it just goes on it's merry way, checking for any other zip files and then HBOOT loads normally.
Running the RUU .exe files on my computer goes smoothly right up until somewhere in the update progress I get Error 155 (Unknown Error).
Now, it's my understanding that I don't need S-OFF to go back to the stock Sense rom, but I figured I should try to get S-OFF anyways. So I downloaded unrevoked and try to apply it from CWM, and it fails stating that it's not compatible with my radio version. Funny thing is, in all the radio lists for the HTC EVO 4G, I don't see 2.15.00.12.19 anywhere. In fact, 2.15.00.08.08 seems to be the newest one, unless I'm reading the lists wrong.
Either way I'm completely stuck here, and now I have a whining teenage sister screaming at me because she doesn't have a phone on a friday night. Go Figure.. Please guys, I know I'm a noobie here, but do me a solid. Please help me out, I'm stuck, frustrated, and I'm getting to the point where it's time to crack open a beer or 3 and say "f**k it".
Thanks in advance,
Alcolawl
you dont need s-off to return to stock..try the guide below in my signature to unroot and return to stock
XenonV said:
you dont need s-off to return to stock..try the guide below in my signature to unroot and return to stock
Click to expand...
Click to collapse
Does it matter which RUU version I download? (I've been extracting the rom.zips from the RUU's temporary files). I have the most current one on my computer named: "RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed". I usually take the Rom from that, rename it PC36IMG.zip, place it on a freshly formatted sdcard, and reboot into bootloader and hope for the best.
well, if you want the bootloader to be returned to factory stock settings then you can follow the guide below, BUT if you just want to UN ROOT, just copy a stock rom like the one you named, and flash it thru RECOVERY menu (install zip from sd card), dont install it from the bootloader (white screen)
XenonV said:
well, if you want the bootloader to be returned to factory stock settings then you can follow the guide below, BUT if you just want to UN ROOT, just copy a stock rom like the one you named, and flash it thru RECOVERY menu (install zip from sd card), dont install it from the bootloader (white screen)
Click to expand...
Click to collapse
Sounds easy enough. While messing around and waiting for Dominos to arrive, I decided to flash MikG (first time doing so, so I wasn't sure what to expect). Lo and Behold, I updated the PRL and Data Profile, and her Data works again. She also likes how Sense looks more so than CM7. Aesthetics > Functionality in her book I guess. If it comes down to having to bring the phone to the Sprint store, I'll try flashing the image through Recovery instead of Hboot.
Thanks for the help man, really appreciate it.
Alcolawl said:
Sounds easy enough. While messing around and waiting for Dominos to arrive, I decided to flash MikG (first time doing so, so I wasn't sure what to expect). Lo and Behold, I updated the PRL and Data Profile, and her Data works again. She also likes how Sense looks more so than CM7. Aesthetics > Functionality in her book I guess. If it comes down to having to bring the phone to the Sprint store, I'll try flashing the image through Recovery instead of Hboot.
Thanks for the help man, really appreciate it.
Click to expand...
Click to collapse
no problem :good::fingers-crossed: