I just purchased my Free (after mailin rebate) G2. I rooted and added eng SPL for fastboot. then installed Clockworkmod recovery 3.0.0.5 via ROM manger and last did a nand-backup and installed Cyanogyn 6.1.1. Only to find that the GPS chip seems to be bad! when I run GPS test or GPS status, all the satellites status indicators (signal strength bars and dots on map) blink on and off. Sometimes they will stay on for a few seconds to lock, but then blink off again. To prove it's not Cyanogyn mod causing the issue I did a nand-restore to stock 1.19 and the problem is still there.
So I'm thinking about returning the phone. Since when I restore back to stock rom it keeps wanting to upgrade me to 1.22 via OTA. My question is if I let it upgrade it self to 1.22 will it remove perma root and ENG SPL? or will it hose the phone?!
thanks
Les
Related
I wanted to try NFSFAN's custom 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
esskay said:
I wanted to try NFSFAN's custom 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
Click to expand...
Click to collapse
OK, relax - its not bricked
the D 3NFS is just NFSFAN's signature on his ROM's nothing to worry about there
First try pulling the battery for a couple minutes and then putting it back in and trying to start, if that still fails, have you tried to hard-reset the phone? red+green+stylus in hole at bottom and hold until the gray screen appears warning you your about to reset the device (your lose you data but it will reload the last ROM you flash
try those if that still doesnt do it, rename the RUU_signed.nbh file to VOGUIMG.nbh and copy it to your SD card then put the SD card back into the phone and press and hold the power+camera+stylus and it will reflash from the SD card (referred to as bootloader mode)
hope that helps
Detroit Doug
I'm up and running again!
I can't thank you enough Detroit Doug, I don't know what I would've done without your help.
Same problem.. put NFSROM's 6.5 rom on my vogue and it worked fine at first, but froze while i was changing the Today theme, and when i soft-reset, it hard-reset itself instead. Never heard of that happening.
After the hard reset it restarted itself as usual, but never recovered after that, just gets stuck at Bell loading screen eternally.
I think it might be because I let customization run the first time, forgetting that I was supposed to reset before customizations run. Possible?
Anyways, I'm trying your last suggestion Detroit_Doug, I put the RUU_signed.nbh on my microsd and renamed it to VOGUIMG.nbh (no other files), popped it in and put it in bootloader... now it's at the gray screen saying it's updating, but the progress bar isn't going anywhere.
Any other solution to recover?
...
Fixed it. I gotta look around more for solutions! I downloaded the official Bell ROM from the HTC website and that ran flawlessly.
Now to do it all over again!
blackrook said:
Same problem.. put NFSROM's 6.5 rom on my vogue and it worked fine at first, but froze while i was changing the Today theme, and when i soft-reset, it hard-reset itself instead. Never heard of that happening.
After the hard reset it restarted itself as usual, but never recovered after that, just gets stuck at Bell loading screen eternally.
I think it might be because I let customization run the first time, forgetting that I was supposed to reset before customizations run. Possible?
Anyways, I'm trying your last suggestion Detroit_Doug, I put the RUU_signed.nbh on my microsd and renamed it to VOGUIMG.nbh (no other files), popped it in and put it in bootloader... now it's at the gray screen saying it's updating, but the progress bar isn't going anywhere.
Any other solution to recover?
...
Fixed it. I gotta look around more for solutions! I downloaded the official Bell ROM from the HTC website and that ran flawlessly.
Now to do it all over again!
Click to expand...
Click to collapse
No problem - the SEARCH feature can be your friend LOL
As for the initial issue - it came with the today theme - you state you flashed to 6.5 ROM which will NOT use today themes (not sure if it was a misused term on your part or if you were actually trying to use a today theme on a 6.5 UI (Titanium or CHome as it is referred to)
Even then, if you are flashing to the 6.5 ROM and wanting themes, they really are not needed - change the overall color via then included color themes and/or install the Color Bar cabs which can be found around the forum and then just browse to a picture it will work great doing something simple rather than complex on a pre-release OS
There are some "themes" available, but be careful and read the threads regarding them before installing and try to keep to the ROM thread itself when applying themes as other users will report pros and cons of such action and can keep you from having to hard reset or completely re-flash your phone for some colors and graphics
Detroit Doug
Okay, there is some misinformation going on.
If you are running a stock EVO, 3G works fine (I just did the 25MB speed test at testmy.net and averaged 1.1Mbps - when ROOTED, I can't get the 6MB test to finish).
When running a rooted EVO in Denver, for some reason, 3G cuts out constantly and won't last more than 2 minutes... generally about 30 seconds and then it dies for a few minutes or until you make a phone call, reboot, put it in airplane mode, etc.
I have tried literally EVERY ROM including the "stock rooted" ROM and they ALL exhibit this behavior.
The only thing I can think of is that something is amiss when flashing the new radio without using the official HTC update package but I'm not feeling like re-rooting my phone all over again with the old radio just to find out.
How many people are experiencing this?
I rooted my EVO and began having issues... Probably about the 13th as stated in the thread... Got really annoyed and flashed the stock RUU (had to take the rom.zip from the Temp folder and rename it to PC36IMG.zip in order to flash though because RUU would not find the phone)... Problem instantly was resolved. Ran the OTA update to get the new radio, thinking it was a radio problem, nope. Still works perfectly fine.
I decided I wanted to try EVOlution V8 today so I re-rooted. Right off the bat, 3G issues. I rooted manually, then NAND, then recovery, then flashed the new radio, REBOOTED, went back into recovery and flashed the ROM...
Now I just ran the RUU and flashed back to stock and everything is working fine. So there is something about the procedure to root that is causing the problem and I don't know if its Denver-specific or what...
I can tell you I didn't have any problems until I unlocked NAND and flashed the permanent recovery. Toast's original root gave me no issues... but that may just be coincidence.
If I decide to stop being lazy, I may re-root and skip updating the radio and see what that does... But for now, I have to conclude it is a rooting issue, NOT a network issue.
Nope this is NOT about the froyo update.
I've been using KingxKlick Roms Slide2G1 and Legend2G1
Tried to use GPS the other night and it would not lock *Slide2G1*
a few days ago i did a speedtest GPS locked super fast *legend2G1*
I use GPS alot so i used a nadroid i had of Cyanogen 2.1 still wont lock
wiped flash stock 1.6 still no go
full wipe again and reflashed CM5.0.8 and still nothing
My mom has a fender with 5.0.8 on it and her phone will lock its just taking 5+ minutes
So is my phones GPS broken from something or could this just be some other hardware issue *not on my part*
If its my phone I'll just unroot it and I think I'm still under warranty
Hi guys,
i have a strange problem with my desire.
I had a branded phone which i successfully unbranded with a goldcard.
Then i rooted it and installed clockwork succesfully with this guide:
http://forum.xda-developers.com/showthread.php?t=835746
The phone run perfectly the last days.
Then i decided to try the canyogen beta rom.
I made a backup with clockwork, then successfully installed canyogen.
After i had seen everything, i decided to go back to the stock rom and restored my clockwork backup.
Everything now works as it has before, except one point.
I get no more signal with my simcard anymore. Theres just a little cross above the signal strength symbol.
I tried to restore egain, i tried to wipe everything, i tried to install a completely fresh ruu file. Nothing helped, i still get no signal anymore.
The sim works perfectly in another phone.
Thanks for any help!!
Try flashing the branded RUU you had in the beggining.
If you cant get a hold of it, flash a WWE RUU with the goldcard inside your phone.
Cheers
So, I was finally offered the 1.8.3 update from the glorious AT&T, OTA. My Atrix is currently rooted on 1.5.7 with Gingerblur 2.5 installed, as well as the HUSPA radio mod. I went to download the 1.8.3 udpate with no problems. Here's where it gets interesting... when I went to install the update, my phone rebooted as expected, but when it came back up with the little android installation logo and the progress bar, after about 25% I get a spinning traingle with a exclamation point in it and the install freezes. I did a battery pull and tried the install again, but same results. Is anyone else experiencing this problem? Does it have anything to do with my phone being rooted? Any comments/suggestions will be appreciated.
wesglbrt said:
So, I was finally offered the 1.8.3 update from the glorious AT&T, OTA. My Atrix is currently rooted on 1.5.7 with Gingerblur 2.5 installed, as well as the HUSPA radio mod. I went to download the 1.8.3 udpate with no problems. Here's where it gets interesting... when I went to install the update, my phone rebooted as expected, but when it came back up with the little android installation logo and the progress bar, after about 25% I get a spinning traingle with a exclamation point in it and the install freezes. I did a battery pull and tried the install again, but same results. Is anyone else experiencing this problem? Does it have anything to do with my phone being rooted? Any comments/suggestions will be appreciated.
Click to expand...
Click to collapse
IIRC, you cannot install OTA updates while on GingerBlur as your OS is modified (root shouldn't matter, it is the fact that GB is DEODEXED). You will need to flash back to stock and update.