I just rooted my G2. I made a backup after I got Rom Manager and updated to Cyanogen Mod 7. After that the phone dialer stopped working, including SMS and EDGE/3G/HSDPA+. The launcher then crashed, and then the entire phone. After multiple resets, "fix permissions", and troubleshooting I restored from backup and still have all the same problems. I factory reset from there and still the dialer crashes when calling someone.
I used cyanogen's mod wiki to root.
I am trying to flash the phone with a newer radio but now it won't pick it up.
Current Radio is 26.01.00.17
Anyone have a fix for this?
Do you have the engboot? You can try to do fastboot if you do or go to the pcimg adio thread, also try to do a full wipe, cache dalvik, data and reflash rom
I tried the fastboot with a newer radio. Didn't realize they were listed oldest to newest.
Did the fastboot with a new radio and it worked! Thanks!
Related
Trying to install Vaelpak 3.0 and I am having 1 hell of a time. I'm thinking it has something to do with my radio wimax pri nv ect.... because earlier in the week I tried flashing the combo and everything went to hell on my phone. I since then had to flash back to the previous radio and then had vp 2.3 running fine again. After that I learned that it was kernel specific problems with older HTC kernels so I flashed netarchy's and then went back to the radio combo and had this problem with my CPU load at 100% and always running at near 1ghz. Then I learned if your rom is not based on the 3.3 that the newest PRL with continue to overload your CPU the entire time. I hadn't gotten this problem really fixed by the time I found VP 3.0 and figured flashing this would just fix my problem with the newest PRI because its based on the 3.3 update.
After a full wipe (data, 2x cache, 2x dalvik) I flashed 3.0 only to get stuck in a white screen boot loop. So I DLed the file from another link moved it manually to my SD and flashed that... same problem. Then I decided I would restore my 2.3 through RA install rom manager and change my recovery over to clockwork to try to install the rom. No go. Then I flashed a previous version of 2.1 used rom manager to put RA back on (I've found this more reliable but at this point who the hell knows). Went into recovery and restored my backup made as of this friday. Still having the problems with the CPU load so I went back to recovery and flashed the older radio combo but noticed this doesn't have NV on it(not sure what NV is either). But all seemed to be working fine for moment until 2.3 started randomly restarting on me. So now my 2.3 isn't working and can't get 3.0 to flash.
Next thing I thought to do was to wipe all again flash 3.0 and then flash netarchy's kernel over the htc #15. BAM!! I get it to run through the boot into the set up menu asking for my gmail account. I enter my account info and wait, wait, wait, then it says cannot get reliable connection to google servers (also I notice that my data instead of a 3g icon says EvDo). Well now this can't be good. I try to turn on my wifi it says that wifi cannot perform search. I enter my network manually cannot find network. I've tried updated profile pri and everything else from settings and always get same error with communications saying call sprint(don't wanna do this will immediately void my warranty I'm thinking). Now the last thing left for me to check is if I can get 2.3 up again and check my wifi ect... through that.
Wipe, Wipe, Wipe, flash older radio combo, flash previous NV that wasn't in combo as far as I could tell, restore 2.3. All seems to be going well until I try my wifi. Cannot search again. WTF?? then instantly black screen to no where. Pull battery try again, get into the settings and then black screen back to Vaelpak boot animation. I am completely lost here I could really use some help. Like I said in the beginning I have a sneaking suspicion it has something to do with the radios combo ect... but can't figure it out on my own.
Well in case this has happened to anyone else and it is likely to happen somewhere down the road from people upgrading to roms based of the 3.7 update. The quickest fix I found was.
1. DL Unrevoked Forever from web page and flash it
2. Find a stock ruu for the 3.7 or do what I did and just DL Sprint Lovers PC36IMG.zip place in root of SD card and boot into hboot. Install the ruu.
3. Go to settings>software updates and update the PRI and the Profile
4. Remove the PC36IMG.zip from root of your SD card
5.(only applicable if you used the stock ruu) take your recovery of choice name it PC36IMG.zip and place in root of SD card. Boot into HBoot and install
then remove that from root as well.
6. Flash the Rom you were wanting to flash. This will take care of all Radio, Wimax, PRI, NV, and other problems between 3.7 based roms, Kernels and Radios.
Hopes this helps someone along the way.
Ugh, I'm newly rooted, and I already messed things up.
I rooted a few days ago, ran cyanogen for a bit, loved it, but wanted to try fresh, then ava, then wanted to go back to cyanogen. I felt I wanted to 'start fresh' sorta. Like I had just rooted again. I like... lost 3G. it just keeps saying "turning on" and I think it may be from updating the radio. Because, I was flashing different roms without updating the radio, and everything was working perfectly. But then, like half an hour ago, I updated the radio to the latest version, 2.15.00.09.01, and things started acting up.
So, here's a rundown of what I did. I was running Fresh before I did all of this.
Formatted SD card so I could start from scratch.
Copied the latest cyanogen to SD card
Copied the latest gapps to SD card
Copied the latest radio to SD card. 2.15.00.09.01
Turn off phone and boot into recovery
Wipe cache, the other Dvichik or something cache, and wipe/factory reset
flashed the latest radio, then flashed Cyanogen, then flashed gapps.
it did its thing, and I turned on phone, and saw that I only had 1x coverage. So, I went back to recovery, did a nandroid backup of cyanogen, flashed fresh, started up, and went to update PRL to see if that would fix it. At first, It wouldn't update, and I went and saw that the "mobile network" was just saying "turning on". I restarted the phone, and then went to update PRL, and it did update, however, my data was soooooo slow. Now, the phone went back to the mobile network just "turning on"...... So right now I'm running fresh with basically no data connection. It didn't do any of this before I updated the radio. Before I updated the radio, I had 0 problems.
Soooooo, Yes, I am a HUGE noob. I know. I knowwwww.
What can/should I do?
Is it as simple as just downloading an older radio? I THINK before I updated, I had radio version 1.39.00.05.31...
Can I just go to recovery, wipe cache, and factory reset, flash the radio, then cyanogen, then gapps?
Should I unroot, and start all over again?
I dont think that is the most recent radio. Where did you dl it from? What is your prl version? I flashed the most recent radio combo from calkulin recently, and my radio ends in .19(2.11.00.15.19). That combo included a new radio, wimax, and prl. Only use these updated radios with the most recent 3.70 software. So if I were you,i would try flashing the correct radio combo. Sorry,i dont have a link, but search calkulins posts/threads and surely you will find it . Hope that takes care of it for you!
Sent from my PC36100 using XDA App
josh995 said:
Ugh, I'm newly rooted, and I already messed things up.
I rooted a few days ago, ran cyanogen for a bit, loved it, but wanted to try fresh, then ava, then wanted to go back to cyanogen. I felt I wanted to 'start fresh' sorta. Like I had just rooted again. I like... lost 3G. it just keeps saying "turning on" and I think it may be from updating the radio. Because, I was flashing different roms without updating the radio, and everything was working perfectly. But then, like half an hour ago, I updated the radio to the latest version, 2.15.00.09.01, and things started acting up.
So, here's a rundown of what I did. I was running Fresh before I did all of this.
Formatted SD card so I could start from scratch.
Copied the latest cyanogen to SD card
Copied the latest gapps to SD card
Copied the latest radio to SD card. 2.15.00.09.01
Turn off phone and boot into recovery
Wipe cache, the other Dvichik or something cache, and wipe/factory reset
flashed the latest radio, then flashed Cyanogen, then flashed gapps.
it did its thing, and I turned on phone, and saw that I only had 1x coverage. So, I went back to recovery, did a nandroid backup of cyanogen, flashed fresh, started up, and went to update PRL to see if that would fix it. At first, It wouldn't update, and I went and saw that the "mobile network" was just saying "turning on". I restarted the phone, and then went to update PRL, and it did update, however, my data was soooooo slow. Now, the phone went back to the mobile network just "turning on"...... So right now I'm running fresh with basically no data connection. It didn't do any of this before I updated the radio. Before I updated the radio, I had 0 problems.
Soooooo, Yes, I am a HUGE noob. I know. I knowwwww.
What can/should I do?
Is it as simple as just downloading an older radio? I THINK before I updated, I had radio version 1.39.00.05.31...
Can I just go to recovery, wipe cache, and factory reset, flash the radio, then cyanogen, then gapps?
Should I unroot, and start all over again?
Click to expand...
Click to collapse
Did you try the ##DATA# (##3282#) and entering your MSL so you can restore your profile?
I've rooted my phone for the first time the other day and started venturing into the custom ROM's realm, but so far all I got were dramas and failures.
I started by downloading Cyanogen 6.1.1 and 7 RC1. I thought I'll try each to see how they perform. So I copied them to the sd-card, along with the radio update that was recommended on the Cyanogen 7 RC1 thread, and rebooted to Clockswork recovery. I wiped my data and cache and went on with the ROM installation followed by the radio update (notice that I skipped the backup stage. stupid, I know).
Upon booting, I immediately noticed that I have no signal, and a force close message that says: "the process com.android.phone has stopped unexpectedly. Please try again" pops up every 2 seconds. Nothing happens when the message is dismissed, mind you, but it still comes up constantly every couple of seconds. This, along with the 'no signal' thing, rendered the phone unusable.
At this point I'm thinking that maybe my phone is just not reacting well to the non-final build of the Cyanogen 7, so I gave the stable Cyanogen 6.1.1 a go. Lo and behold, same thing happens with it also. Now panic kicks in when I realize that I have no backup, and no stock ROM to go back to.
Eventually, I downloaded the latest rooted Desire 2.2 ROM, got it into my sd-card and installed it. Thankfully, everything was working properly again. After some asking around in the Cyanogen forum, it got to my attention that the update to the radio might have caused all of this trouble, and that the installation of the stock ROM brought the previous radio version with it, which solved the problem. But when I tried to install Cyanogen again, without tinkering with the radio, same thing happened. I then tried Oxygen 2, thinking that maybe my device just doesn't like Cyanogen, but the exact same problem persisted.
Anyone have any idea what's the deal here?
Did you wipe dalvik cache after flashing the roms?
Sent from my HTC Desire using Tapatalk
I wiped the cache partition before I flashed. It didn't say 'dalvik' specificaly, just 'cache partition'. I never wiped any type of cache *after* the flashing process.
You should wipe the dalvik cache after (or just before) flashing roms.
You can find it under the advanced menu in clockworkmod recovery.
Sent from my HTC Desire using Tapatalk
Alright, tried wiping the Dalvik Cache after flashing, problem still persists.
You could try downloading another radio and trying it. Even if it's not the recommended one, an older radio works better for some people. There is no such thing as 'the best radio to use', since result may have large variations for different people (in different locations, using different phones and ROMs). Just browse the radios post and pick one
Btw, since the dalvik cache is stored at /data/dalvik-cache, wiping the /data partition implies deleting the dalvik cache
Well, since the radio that I have installed now works, and since it stays the same one after installing a different ROM, it seems to me that the radio is not the problem here. I really would like to stay away from tinkering with the radio stuff...
Bump.
This really bugs me that it wont work. I feel like I'm missing out on the biggest feature of having a rooted phone...
Hmm... I've found that if I force the phone into Airplane mode, the FC messages stop. Of course, I still have no signal.
So, the reason for the FC messages is due to the failure to connect to my mobile network. Now, why would I be able to connect to my network fine on the official Desire ROM, but not on any other ROM?
If all else fails you could always trying flashing the RUU for your phone then start from the beginning and root again if you've tried everything else.
Sent from my HTC Desire using XDA App
Ok, I'll try that.
Just a quick question. After I run the RUU and the device is unrooted, will I be able to recover my nandroid backup fully after I re-root?
So I've seen other people that have this problem but the difference is usually they get the message when opening this or that, while I get the message constantly. As is, if I force close it, it pops right back up again leaving me no time to actually do anything on my phone.
Any help would be appreciated, I have CM7 installed and this just happened after a reboot.
Did you flash the latest gapps when you flashed CM7?
Yeah, and CM7 had been working great up till this point. Now it says I have no service and I can't do much of anything.
TheUnknowing said:
Yeah, and CM7 had been working great up till this point. Now it says I have no service and I can't do much of anything.
Click to expand...
Click to collapse
Did you flash anything without wiping data? if you did you might have to wipe data. Before you do that try to fix permissions in rom manager and clear the data for the phone app. If those things dont work wipe data. If a data wipe doesnt work you have a problem with the ROM you flashed. If its a nightly you should either flash a different nightly or flash the stable.
As for the service you can try to flash a new radio. If that doesnt work i recommend going back to a sense rom updating your profile, and then your PRL. I wouldnt imagine the radio is the problem, because ROM's shouldnt normally include radio files, but you might as well try to flash the newest radio anyways. Newest radio is 2.15.00.11.19.
flashing a new radio, updating your prl, and updating your profile are about the only things you can do to help your service. updating prl and profile can only be done on sense roms through settings, because those involve sprint code, which is not made public.
Update: I'm not sure how to do most of the things you mentioned but my radio is up to date. I discovered that this problem only occurs after I reboot the phone. It flashes fine, works normally, but once I reboot it the problem starts up.
Hi everyone, this is somewhat complicated and il try my best to describe what happened.
My device is a i747m (rogers).
I was running CM10.1 (running gapps-jb-20130812 and CWM recovery 6.0.4.3) for a long time, tried to update to 10.2.
(i messed up on 2 things.I don't think i cleared neither of the cache or data and also didn't have proper gapps which would be 20130813).
After installing 10.2 through recovery, it would just stay in the boot Cynogen booting logo.
i restarted into recovery, since my old CM10.1 zip was still there, i installed that instead, but same thing happened, it would just stay at booting logo.
I had made a nandroid back up from before all of this, and so i wiped data, dalvik cache, cache, formatted system, and i recovered into that, which was a stock 4.1.2 rooted (rogers).
However, nothing worked, only WiFi. I couldn't make any phone calls, send/receive messages, or get data.
I then used ODIN 3.07 to flash the new stock 4.3 rooted (rogers). WiFi worked as before, but i still couldn't make any phone calls, send/receive messages, or get data.
i then re-installed the latest recover 6.0.4.5, and installed paranoid android 4.4.2 and gapps for this version. But still nothing, so i went back to the stock 4.3 rooted.
4 months ago, when i made the nandroid back up, i also made an IMEI back up as well (i did not do a full imei/NV/EFS/IMSI/data backup) , i only had my IMEI backup, so i wrote using "NV items reader writer" the IMEI back onto my phone, and now i can recieve/send messages, and get phone calls and make phone calls. wifi also works.
But my data is stuck in Edge, its extremely slow, takes 10min to download a 15mb file.
so far:
-The APN settings are correct
-my IMEI number in settings menu, matches the one on the back of my phone.
-network mode is GSM/HSPA/LTE
-i have installed the latest modem for i747m through CWM recovery and also tried slightly older versions.
i am pretty much lost and i dont know what i should do.
-rogers has told me to use kies and perform backup and then recovery, apparently that will factory reset my phone.
-should i simply use kies to install the latest 4.3?
-does anyone have the imei/NV/EFS/IMSI/data files? or the full NV file?
-should i install CWM recovery and wipe everything that i can? and re-install stock rooted 4.3?
-should i use QPST to fix my IMEI? <-- dont know anything about this, noticed a few threads.
i have used these threads in all my rooting and so forth.
http://forum.xda-developers.com/showthread.php?t=2179330
http://forum.xda-developers.com/showthread.php?t=1831898
http://forum.xda-developers.com/showthread.php?t=2129993
please someone help me out, I dont know how to fix this.
thank you for reading this long and complicated problem.
same problem, ive spent every minute working on it for a week