So the Girlfriends US Virgin Mobile PrimoC was running slow so she turned to her nerd boyfriend to help. Nerd boyfriend to the rescue I set out to root and install AOKP and after messing with this thing for 10 hours I'm stuck. I used the All-in-One Tool kit to root and install a new Rom. First I tried AOKP, but ran into the 1-minute restart issue, didn't know why so I tried PAC and the phone kept restarting every minute or so. Did some more searching and found that the restarting was due to the updated Radio. Found a tutorial thread for downgrading the radio by taking the RUU, extracting the rom.zip file, renaming it PK75IMG.zip placing it in the root of my sdcard and flashing in the bootloader. Did that, loaded up AOKP again and the restart issue was gone but I have no service now. It seems the radio is getting a signal, but it will not give me any service. I then just ran the full RUU from the computer, it completed without error and we are back on the stock Rom with downgraded radio. She still does not have any service. Tried downloading a different RUU (same RUU but from a different server) and still can not get any service.
Any suggestions?
tErbo b00st said:
So the Girlfriends US Virgin Mobile PrimoC was running slow so she turned to her nerd boyfriend to help. Nerd boyfriend to the rescue I set out to root and install AOKP and after messing with this thing for 10 hours I'm stuck. I used the All-in-One Tool kit to root and install a new Rom. First I tried AOKP, but ran into the 1-minute restart issue, didn't know why so I tried PAC and the phone kept restarting every minute or so. Did some more searching and found that the restarting was due to the updated Radio. Found a tutorial thread for downgrading the radio by taking the RUU, extracting the rom.zip file, renaming it PK75IMG.zip placing it in the root of my sdcard and flashing in the bootloader. Did that, loaded up AOKP again and the restart issue was gone but I have no service now. It seems the radio is getting a signal, but it will not give me any service. I then just ran the full RUU from the computer, it completed without error and we are back on the stock Rom with downgraded radio. She still does not have any service. Tried downloading a different RUU (same RUU but from a different server) and still can not get any service.
Any suggestions?
Click to expand...
Click to collapse
sometimes this happens to me when i reflash a new rom try to re activate the phone through the virgin mobile app when your phone is stock again. then change roms i personally dont use the all in one toolkit to flash i just flash the rom with recovery then bootload and flash the kernel that matches the rom. i dont know much about ruu ive never had to do it so sorry im not much help but try that.
Related
I know that I have already posted on someone else's thread, so I figured rather than hijacking someone else, I would start my own.
Here is my issue. I have tried every posted method out there for flashing Radios into my Sprint Vogue (flashed to MetroPCS). I am currently on NFSFAN's 1.00.6.5 Rom (21864), with radio 3.37.10.
I have tried...
*Flashing from SD card with a fat32 formatted 2 GB card, renamed radio to VOGUIMG.NBH (upper and lower case),
*Flashing via USB with ActiveSync on,
*Flashing via USB with ActiveSync off,
*Flashing via USB with bootloader preset,
*Flashed back to the Alltel rom used for SuperCID and tried to flash radio while in that rom,
*I have tried with radios 3.42.30, .40, and .50.
The only thing I have not tried has been mtty, but somehow I have my doubts that it will work.
Every time the RUU runs, it starts and the progress quits at 8%, with my phone being rebooted. Also, the RUU displays error message 328....
I have searched all over and tried a few things but most of them are related to the Titan and not to the Vogue. If anyone has encountered this issue and knows how to solve it, I am open for suggestions. Thanks...
I suggest your flash your phone with the stock rom of bell if your want the 3.42.5 radio. Just reset as soon as your see the 3 second customization screen.
Then unlock phone, and then flash your fav custom rom.....
SL said:
I suggest your flash your phone with the stock rom of bell if your want the 3.42.5 radio. Just reset as soon as your see the 3 second customization screen.
Then unlock phone, and then flash your fav custom rom.....
Click to expand...
Click to collapse
I'll give that a shot. Thanks for the suggestion...
@SL
I followed your advice to a certain extent. I went with the latest Sprint official rom, which carried 3.42.30 in it. This seemed to work ok. I still cannot go to .40 but I guess if I flash from the original carrier that had this rom, I will be in good shape (Bell with .50, etc). Do you know which carrier has .40? Thanks for the help!!!
@ SL
I finally went over to the Bell rom that can be found in HTC's official website. I am finally up and running with 3.42.50!!!
I will probably try to make a sticky or a post describing the problem and the solution for people with the same issue, which I have seen quite a bit looking for an answer...
Once again, thanks for all your help!
Hey all, long time lurker, first time poster....unfortunately....
So after sitting on MIUI for a good while, and having a blast with it, I decided to try out some other ROMs. I was interested in seeing Cyanogen 6, and so I went about attempting to get the latest stable, non RC ROM onto my EVO. I read into it seeing that I needed to downgrade my hboot, and found the image without a problem (running the .76 right now, had the 9something one before...)
Well, I downgraded my hboot without an issue, flashed the Cyanogen, and got into a splashloop. I figured out it was becaue I hadn't wiped my cache or data before flashing the rom, so I went into the Clockwork Recovery and wiped those, flashed once more, and it booted into Cyanogen perfectly!
Well, almost. I don't have 3G now.
For some reason, I am unable to connect to 3G no matter what I try. My nandroid's broke due to the hboot downgrading, rewiping the cache/data and reflashing cyanogen did nothing, and now for some reason, when I attempt to go back to MIUI, it still will not allow me to connect to 3G. I can send and receive texts, and make and receive calls, but alas, no data connection.
Should I get a fresh RUU and stock hboot, upgrade and restart from scratch? I just want to get back to MIUI at this point with a working, data enabled phone.....
If that's the case, that I do need to start over, where can I find a new hboot for the EVO that isn't .76? I'm pretty saavy when it comes to this stuff, but for some reason right now I just can't figure it out....
HTC EVO running MIUI v0.11 stable
.76 hboot w/ Clockwork recovery
Broken nand backup
whatdo?
Thanks in advance for the help
Sorry for the double post, but I resolved my issue.
I am unsure of what exactly went wrong, but I figured it was somewhere between downgrading my hboot, and flashing the CM 6 stable ROM that my 3G data got scrambled....
So! Using ROM Manager, I made a backup of my working (non 3G) MIUI image, and flashed the Odyxed version of the RUU found here (http://forum.xda-developers.com/showthread.php?t=836728). After flashing in Recovery, it booted into SenseUI, and worked like a charm!
My 3G hath returned, and issues have been solved. It's nice when you're able to fix things on your own, though I couldn't have done it without the help of that handy dandy search button, and the RUU keyword
Oh, yeah, and I guess xxbabiboi228xx as well.....maybe....^_~
Hi after days of searching the internet I have finally realised I need to post here and ask for help, sorry if this has been posted before though as I have really looked hard everywhere!
Anyway, after flashing a RCMix rom my desire started to drop calls as soon as I either picked up or answered one and only ever rarely got 2G signal in what I know is H signal zones. I changed roms but the problem persisted and after countless hours of searching and trying my sim in other phones, I have deducted that it is my desire which is the problem.
So I'm going to take it back to a t-mobile store, as I were unrooting using the RUU exe I got the 140 error, my phone will no longer boot but still has bootloader, fastboot and recovery working! Is my phone bricked, I can't find any help anywhere on how to put my desire back to stock
Please could any of you shine some light onto my situation?
Many many thanks
You have recovery? Did you try installing another rom to make the phone work again?
After that you can try to unroot it again, I think...
Okay, I will try installing a froyo rom now, will post the results of a second unroot...
Right very strange indeed, just flashed AceSMod007 and signal problems have seem to have gone away (although I had tried this before with many roms - maybe the unrooting process fixed my phone somehow?)... so this means there is no need to unroot and send back to t-mobile, hmmmm all seems to good to be true! thanks for the help though, wouldn't of tried flashing another rom if you hadnt mentioned it
I recently unrooted my EVO to exchange for credit for an upgrade. I decided to keep it as a backup. I was on Hboot 2.18.001 and I rerooted through HTCDev, then PC36IMG to 2.2 to get S-OFF, ending up with Hboot 2.10.001. Somewhere during this rooting process I lost Wifi. When attempting to turn Wifi on, it flickers off and on and reports back that it is unable to scan for networks. In CM7, it causes more problems like force quits and lag. I am using this as a wifi only device as a backup music and game device.
I tried downgrading and upgrading the radios, I tried changing to hboot 2.15.001, I tried different ROMs (AOSP, ICS, Sense, 2.2, 2.3), I tried redoing a PC36IMG, I tried combinations of all of the above. I also tried nandroid restore. Still no Wifi. I am using Smelkusmod recovery.
Currently I am at a stock latest OTA ROM with root.
Any suggestions?
just wondering, did u ever drop it? thats what happened to my evo shift and i couldnt do anything on it other than install roms. i dont remember the version of the firmware but there was one that made wifi useless, meaning like it would turn on and find signals but wouldnt connect. my suggestion is to start from scratch, get the 2.2 ruu stock, before rerooting check to make sure wifi works, if it does then another suggestion would be to follow zedomax's rooting with revolutionary (witch i currently have now). if none of that works then eather sell it for parts or take it to sprint to get a refurbished one.
Good luck!
Hey guys,
So a couple of weeks ago, I got a One and I unlocked everything and put CM10.2 on it. Yesterday, while needing the navigation to try and get un-lost, I couldn't get my phone to get a GPS lock at all, even while having a clear view of the sky and everything. I am running CM10.2 and CWM 6.0.4.5. I have already tried clearing and redownloading the AGPS data and that didn't help. So I found a comment saying that I should flash back to stock and change the location settings and the preferred network setting to see if that changes anything.
I found the stock ROM .zip on this forum, 1.10.605.10 (4.2.2/5.0) and tried flashing it after checking the MD5. That ended up not working at all, it starts but then fails saying that it can't open the update .zip and also says "(bad)".
Now I am trying to download 2.10.605.1 (4.3/5.0) and I will try that tomorrow.
The reason I posted is to ask 1) if anyone was able to fix the GPS problems without having to flash back to stock and 2) what I needed to do to flash back to stock if that's the only option that I have? I don't want to mess anything up and I am still kind of inexperienced at this.
Thanks!
OctaviusMaximus said:
Hey guys,
So a couple of weeks ago, I got a One and I unlocked everything and put CM10.2 on it. Yesterday, while needing the navigation to try and get un-lost, I couldn't get my phone to get a GPS lock at all, even while having a clear view of the sky and everything. I am running CM10.2 and CWM 6.0.4.5. I have already tried clearing and redownloading the AGPS data and that didn't help. So I found a comment saying that I should flash back to stock and change the location settings and the preferred network setting to see if that changes anything.
I found the stock ROM .zip on this forum, 1.10.605.10 (4.2.2/5.0) and tried flashing it after checking the MD5. That ended up not working at all, it starts but then fails saying that it can't open the update .zip and also says "(bad)".
Now I am trying to download 2.10.605.1 (4.3/5.0) and I will try that tomorrow.
The reason I posted is to ask 1) if anyone was able to fix the GPS problems without having to flash back to stock and 2) what I needed to do to flash back to stock if that's the only option that I have? I don't want to mess anything up and I am still kind of inexperienced at this.
Thanks!
Click to expand...
Click to collapse
The only option is to flash back to Stock to fix your GPS issues. You probably need to use a different recovery either from TWRP or Clockwork depending on the one that doesn't work to flash it.