I recently updated my pri to 1.4 and found that you can't make calls or surf the web when roaming. How do I revert back to 1.3?
*UPDATE* I was able to get roaming to work on 1.40. No need to revert back now
Flash the eng-PC36IMG...170mb
snandlal said:
Flash the eng-PC36IMG...170mb
Click to expand...
Click to collapse
Can you direct me to where i can find this? I think i flashed the wrong one..
just re-root with simple root?
Don't re-root. Go to Settings>Privacy>Factory Data Wipe and everything will work. If it doesn't, call Sprint from your landline and talk to them. They'll do some hocus-pocus on their end, and have you do a Factory Data Wipe.
So I flashed a pc36img (not sure if this is the right one) and it didn't change my pri...
Sent from my CM6 powered device
The only way I could possible think to revert would be to do the original method you used to get pri 1.34 because Rooting your phone is what caused the PRI to downgrade in the first place...
Related
I just did the root, nand, and radio
However I didn't know that I was going back to 2.1
What are the cons of 2.1 vs 2.2 and how long usually before there is an updated rooted 2.2?
Thanks
2.2 is out officially??? Where/how can I/we get it?
It just automatically downloaded when I got my phone yesterday. Now I'm wondering if I should go back and update and wait then re root later or just wait.
Are you sure you had 2.2? Where did you get your phone? What is your hardware version?
Positive I had it. I got it at walmart yesterday. As soon as I activated it downloaded like three updates.
I was using flash etc.
kikwear002 said:
Positive I had it. I got it at walmart yesterday. As soon as I activated it downloaded like three updates.
I was using flash etc.
Click to expand...
Click to collapse
Flash lite?
Flash works with 2.1 also (at least on the evo)
I'm not really sure. I just know it said 2.2 and not 2.1.
also my hardware is 2.2
I wish I would've known I would've backed up before rooting. I didn't see any reason since the phone was new with nothing on it.
I just checked and it said no updates available.
So in order to go back to stock all I have to do is reflash with the stock rom. Just throw it on sd and flash as normal?
kikwear002 said:
I'm not really sure. I just know it said 2.2 and not 2.1.
also my hardware is 2.2
I wish I would've known I would've backed up before rooting. I didn't see any reason since the phone was new with nothing on it.
I just checked and it said no updates available.
So in order to go back to stock all I have to do is reflash with the stock rom. Just throw it on sd and flash as normal?
Click to expand...
Click to collapse
Just flash RUU from your computer.
Settings > About > Hardware, your Hardware Version is 2.2, NOT 002 or 003?
no its 002 sorry running on two hours of sleep here.
Ok i'm going to try to go back to stock then upgrade.
at least I know I can root it again. maybe faster next time too.
well I unrooted and got some prl updates but no firmware
here goes
Take the battery out of the for about 5 sec then put the battery back in and go in to recovery and try reflashing the rom that work for me
One of three things happened..
You are either have a nexus one and are in the wrong forum..
Are mistaken that you had 2.2 prior to root..
Or you're just trying to mess with everyone..
2.2 is not out in any way officially on any HTC phone, so you couldn't have had it. And no, you couldn't have been the only person in the country to have accidentally gotten it somehow.
Can the OTA Update be uninstalled? or is it possible to reinstall the old one (Stock) ROM?
FULL STOCK, never rooted etc...
factory reset would reset the phone back correct?
oOflyeyesOo said:
factory reset would reset the phone back correct?
Click to expand...
Click to collapse
Actually I bet it would still have the OTA updates installed. If you want to go back to full stock you can download the .exe from the top of this thread and run it on your computer with the Evo plugged in.
http://forum.xda-developers.com/showthread.php?t=685835
I have used it twice and it works without hiccup. Goodluck!
Ive been trying with no luck. I even have a rooted version of 1.47 installed and I cant get into any custom recoveries to allow me to do a nandroid restore. Its driving me insane. Despite every spouting off about the ruu utillity, it DOES NOT WORK. Any ideas of how to fix all of this?
I cannot get this to work either. It keeps telling me that it cannot communicate with my phone.
The bootloader was updated (this happened with radios on Windows Mobile phones back in the day) - there is no downgrading from this point.
EtherealRemnant said:
The bootloader was updated (this happened with radios on Windows Mobile phones back in the day) - there is no downgrading from this point.
Click to expand...
Click to collapse
Thank you... Guess I'll have to wait for the tether root for this... update
So basically because the bootloaders where updated we are unbale to use any of the Stock ROMs listed in the wiki?
firefoxinc said:
So basically because the bootloaders where updated we are unbale to use any of the Stock ROMs listed in the wiki?
Click to expand...
Click to collapse
Correct. None of them will work.
Ok, I'm mixed up and maybe I still have too much noob left in me. I've got a rooted phone, software version 1.32.651.6. I know there was an update but I didn't do it b/c of fear of losing my root. So, what I did do was update some things "manually." I now have Baseband 2.05.00.06.10, and PRL Version 60667. I also flashed new Wimax as found within these forums. My question now is: I'm hearing about PRI version. How do you update this? And, is it necessary or useful? And finally, was there anything other than the above changes that I'm missing as a result of not doing the OTA?
Any info on any of these questions would help.
Thanks!
After downgrading my PRI to 1.34_003 (using the NAND unlock), I have not been able to receive text messages from AT&T. I have tried everything I possibly could to restore the PRI, but am helpless because it's an issue that resides in the roms themselves, according to toast (forum.xda-developers.com/showpost.php?p=6845492&postcount=75). I am really hoping that we can find a way to update back to the stock 1.40_003 or better yet, an updated version. That's just my 2 cents!
The_Infamous_One said:
After downgrading my PRI to 1.34_003 (using the NAND unlock), I have not been able to receive text messages from AT&T. I have tried everything I possibly could to restore the PRI, but am helpless because it's an issue that resides in the roms themselves, according to toast (forum.xda-developers.com/showpost.php?p=6845492&postcount=75). I am really hoping that we can find a way to update back to the stock 1.40_003 or better yet, an updated version. That's just my 2 cents!
Click to expand...
Click to collapse
Hmm thats strange. I have no problems sending or receiving from AT&T. All my friends but 2 are on it (one T-Mo & one Sprint) and I have no problem whatsoever messaging them.
I flashed the rooted 3.36.651.3 ROM when it came out. Now that .6 is out, and 2.2 has been rooted can I accept the .6 OTA? I am not sure what will happen.
I am fully rooted and unlocked. Will I retain root? I prefer not to wipe my phone if I dont have to. Thanks for helping a confused noob!
You're better off flashing the rooted version of .6 instead of doing the OTA. The OTA will unroot you unless you have Unrevoked Forever, but even then, why risk it? Even if you did do the OTA, you COULD unroot, but that would be more of a "oh, crap, I screwed up, at least I can fix it" way of doing things. I'm not super-familiar with what UF actually does, but definitely don't do anything without installing that and switching to S-OFF. Then you can try the .6 OTA. If it works, great. If not, you'll have to use the new root method (and wipe your phone anyway) to downgrade, then you'll HAVE to flash the rooted version or another custom ROM after that to get up to 2.2 again.
Thats what I figured too. I wasnt sure if the OTA would leave the su and various pieces in place or what... Is it safe to flash the .6 rooted over .3 rooted? Suggestions on which version? I prefer to stay as close to stock as I can. Thanks for the quick reply.
^^What he said^^ Here's one:
http://forum.xda-developers.com/showthread.php?t=743352
If you want stock, use the stock version. There's one odexed and one deodexed. Don't ask what the difference is, there's already answers to that around. Use the wiki link at the top of each forum to find all the ROMs.
As for flashing up to a new version without wiping, that's up to you. Within the same version (stock to stock) it should be okay, but if you're switching to a custom version, you have to wipe. I do anyway just to make sure there aren't fragments or anything lying around that will screw things up. I'm cautious like that.
netarchy recommends doing a full wipe first. Has anyone done an upgrade over .3 successfully? There also appear to people experiencing issues toward the 56th page.... that was my initial concern in why I was asking about the OTA.
cool, I will flash the one Jim M linked. I have been lurking it for a while. Thanks!
after i rooted last night, i tried to update to the ota, and keep root then, i could download the file, but it would not install, started to, but froze everytime, tried it a few times, and just said forget it.
SilverZero said:
If you want stock, use the stock version. There's one odexed and one deodexed. Don't ask what the difference is, there's already answers to that around. Use the wiki link at the top of each forum to find all the ROMs.
Click to expand...
Click to collapse
I was just going to ask that. So I went to the wiki ansd got:
Create the page "Deodexed" on this wiki!
I did a search and came up with:
Search: Keyword(s): deodexed ; Forum: HTC Supersonic: EVO 4G and child forums Showing results 1 to 25 of 170
AH: http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=7435282
deodexed = you can change things, such as themes, more easliy transported and packed smaller or changed.
odexed = basic stock
That's it in a nutshell from a nut.
@Gary - I'm waving back, can you see me?
Jim M said:
@Gary - I'm waving back, can you see me?
Click to expand...
Click to collapse
Is that you with the bottle in your hand? I think I'll stop at Outback and grab a beer and burger on the way home.
Thanks for all the responses. I was able to use the update and flash right over .3 and now .6 still rooted! I used titanium & rom manager to backup everything in case I needed to roll back. Its been a day without any issues.
Reverting to stock for replacment (on "developer edition")? Revert CID/need for PIT?
Hey all,
I gotta send N4 to verizon for replacement (no 4G anymore) and I am trying to get back to as close to stock as possible. My big questions before I go about the final Odin restore flash are:
1. Will the fact that I changed it to developer edition (not developer options) by changing the CID matter at all? Do I need to undo my developer edition tweak as well? Worried about bricking by flashing the full stock images on a "developer edition".
2. Do I need to use a PIT during flashing, to really get it all fully stock?
3. With regards to TWRP, will flashing a stock image revert back to stock android recovery as well? Do I need to mess with TWRP before flashing via Odin?
4. Is it hopeless to try and remove the "custom" pad lock on boot? Is there any way to achieve that?
5. Is it better to use the "Stock" images from the community or should I use those from SamMobile?
Currently on a nandroid restore of my unrooted, fresh install of 6.0.1. Baseband ver CPF3, build CPD1 (using bootlader from hsbadr SafeUpgrade to MM).
Why do you need to send it to Verizon and to get fixed. Have you tried flashing back to a stock ROM and checking for 4g.
I lost my 4g a while back it turned out to be my sim tray and was a 5 dollar part and was 10 minutes to mix.
celticpride34 said:
Hey all,
I gotta send N4 to verizon for replacement (no 4G anymore) and I am trying to get back to as close to stock as possible. My big questions before I go about the final Odin restore flash are:
1. Will the fact that I changed it to developer edition (not developer options) by changing the CID matter at all? Do I need to undo my developer edition tweak as well? Worried about bricking by flashing the full stock images on a "developer edition".
2. Do I need to use a PIT during flashing, to really get it all fully stock?
3. With regards to TWRP, will flashing a stock image revert back to stock android recovery as well? Do I need to mess with TWRP before flashing via Odin?
4. Is it hopeless to try and remove the "custom" pad lock on boot? Is there any way to achieve that?
5. Is it better to use the "Stock" images from the community or should I use those from SamMobile?
Currently on a nandroid restore of my unrooted, fresh install of 6.0.1. Baseband ver CPF3, build CPD1 (using bootlader from hsbadr SafeUpgrade to MM).
Click to expand...
Click to collapse
never heard of a fried phone where 4G only does not work. Are you getting any signal? Try going back to a mostly stock Rom.
Plus if you ever rooted, you tripped knox and Efuse. Not likely that the would just overlook that
LumberjackZac said:
never heard of a fried phone where 4G only does not work. Are you getting any signal? Try going back to a mostly stock Rom.
Plus if you ever rooted, you tripped knox and Efuse. Not likely that the would just overlook that
Click to expand...
Click to collapse
Yeah, didnt make sense to me either. Odin'd back to CPD1 and signaling was fine again. As soon as I throw a ROM at it (any 7.0 AOKP and tried Jasmine which is 6.0), the radios get drunk. Seems like a common issue for some. Oddly enough Emotion build 109 worked flawlessly on 4G, once I updated to 328 I've been unable to get 4G back, where texts work). Yeah, Knox 0x1 tripped, I was thinking it was hardware so was toying with taking the gamble that they wouldn't check on such an old phone.
celticpride34 said:
Yeah, didnt make sense to me either. Odin'd back to CPD1 and signaling was fine again. As soon as I throw a ROM at it (any 7.0 AOKP and tried Jasmine which is 6.0), the radios get drunk. Seems like a common issue for some. Oddly enough Emotion build 109 worked flawlessly on 4G, once I updated to 328 I've been unable to get 4G back, where texts work). Yeah, Knox 0x1 tripped, I was thinking it was hardware so was toying with taking the gamble that they wouldn't check on such an old phone.
Click to expand...
Click to collapse
how close did they look ? triangle away is cosmetic and wont withstand a logcat but might fool dip**** behind the verizon counter