Develop Bugs

[Q] Weird problem installing custom ROMs

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?

[Q] wifi - unable to scan for networks

Hi Guys
I have become a victim of the dreaded "unable to scan for networks" wifi issue and need some suggestions.
The problem originally occured when I upgraded my phone to MIUI-Au, I also upgraded the radio to the recommended version.
When I enabled the wifi after the reflash the phone went into a reboot loop which I could not get out of. I reflashed the phone again with MIUI, everything worked fine until I enabled the wifi and then ended up in the loop again.
I did some looking around and found the suggestions to rename/delete the /data/misc/wifi/wpa_supplicant.conf file which I tried to no avail. I gave up with MIUI and decided to go to another Rom and decided to try out InsertCoin CM7/A2SD+. I installed the rom as per the recommended procedure i.e. Wiped Malvik and normal cache partition & data/factory reset. I also tried both of the recommended radio's on the Insertcoin thread.
My system now no longer gets into a reboot loop when trying to enable the wifi but simply comes up with a "unable to scan for networks" message and then switches the wifi off. I have tried resetting data/ factory resets, Cache and Malvik settings and everything else I could think of.
Has anyone got any other suggestions as to how I could try and sort this out as I have followed all the suggestions I could find on the site?
Thanks
JohnB

Did u try only a factory reset without data wipe? Usually a factory reset solves the problem...
Maybe this might help:
MasDroid said:
First, perform a Nandroid Backup via Recovery Mode, which you can later restore, just incase anything goes wrong.
Try flashing the modified kernel 2.6.29 in Recovery Mode (MCR_oc_v14-signed.zip ), it should work then.
Here is the link to the kernel thread: http://forum.xda-developers.com/showthread.php?t=682419
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showthread.php?t=705214&styleid=16

Thanks for the suggestion MatDrOiD. Yes,I have done a factory reset, if that means setting/SD & Phone Storage/factory data reset (tried with "erase SD card" ticked and without ticked). Have however tried your suggestion again but still comes up with the "unable to scan networks" message.
I have also reflashed several new roms (in default settings) in an effort to try to find something that would work, all seem to have the same problem.
I also tried with a different SD card with nothing on it and have reformatted it several times.
System info
Kernel version 2.6.35.10-gdd56551 [v03]-snq-is-still # 1
Build Number: IC GS A2SD+ V20
Software number 2.36.405.8
Android Version 2.3.3
Rom version: InsertCoin_GB_Sense2.1_A2SD+_v20
Radio: 32.56.00.32U_5.17.05.23 tried 32.56.00.32U_5.17.05.08 as well
Would changing the radio make any difference? I have tried the versions recommended for MIUI as well.
Anything else I could try?

Changing radio could work. At first, i would do a full wipe and flash the original htc froyo rom. If the issue still exits, wifiadapter could be broken.
Sent from my HTC Desire using XDA App

Thanks for the suggestions Mat, I tried to reflash the 2.6.29 kernal as suggested but my phone seems to just sit with a black screen with white stripes on the edges when trying to restart with the new kernel. Left it for 1/2 hour but just sits there. Also tried a few other versions of the kernel but all seem to just sit with the white stripes on the scree.
I am going to carry on trying over the weekend and if I don't get it sorted will switch back to the orginal HTC froyo ROM and see if that sorts out the problem. If not will send it back to manufacturer
Thanks again for the suggestions.
JohnB

GPS fix?

I've tried running cm7.0.3 and virtuous 1.0.2 and I can't get a GPS lock while using runkeeper. Is this because of my location?? or the rom?
I've also tried the clear cache zip file for CM7 and it still didn't work.
Thanks

Did your GPS work when you were stock?
There are quite a few reports of GPS issues with CM, I know I experienced (and still do to some degree) a lot of them.
There are several things that people have tried to fix this issue..
You can wipe your "EFS" data, I tried this and it made things different but I'm not sure if it made them better.
You can flash a new radio, I'm currently running 12.50.60.24_26.08.04.16 and it's working reasonably well for me but there is a newer one available that I plan on switching to the next time I upgrade CM
See http://forum.cyanogenmod.com/topic/21454-gps-on-g2-not-working-stable-7/ for more information

Thanks, tried wiping efs but that didn't work. Will try the radio now

Cannot connect to 3g

Hey whats up guys...im really not sure what the problem is but maybe some one has experienced with before..
My droid incredible cannot connect to 3g service...i tried installing all different kinds of roms even the latest gingerbread releases but still nothing.
Some times i allows me to connect to 1x but then you see the "3g" on the top but then it instantly disconnects.
Ive so tried 3 different radio from the NIS business sense release...all failed..
Any ideas?!?!?
Or if i just need the stock radio??

Aloha! I'll see if I can help.
1) Do a nandroid backup in recovery.
2) Wipe data/cache/dalvik cache then flash rmk40's gingersense leak: http://forum.xda-developers.com/showthread.php?t=1087077
3) Reboot and skip set up. Turn on 3G and even test it out for a bit. You should have whatever signal you are used to having return.
4) reboot into recovery and wipe cache, then go into advanced and wipe dalvik cache
5) Restore your latest Nandroid backup
Let me know how this works.

SlimSnoopOS said:
Aloha! I'll see if I can help.
1) Do a nandroid backup in recovery.
2) Wipe data/cache/dalvik cache then flash rmk40's gingersense leak: http://forum.xda-developers.com/showthread.php?t=1087077
3) Reboot and skip set up. Turn on 3G and even test it out for a bit. You should have whatever signal you are used to having return.
4) reboot into recovery and wipe cache, then go into advanced and wipe dalvik cache
5) Restore your latest Nandroid backup
Let me know how this works.
Click to expand...
Click to collapse
How would this fix any 3g issues by flashing a new rom and then returning to you old Rom with a backup? I seem to have an issue changing from 1X to 3g causing me to restart my phone at times to pick up the 3g signal again.

Primarily, the people who noticed this issue were/are folks who try out the various gingersense roms available. I've been a member of XDA since January and haven't noticed users in large numbers have issues with 3G until these roms came out. Whether it's due to there not being an official base or what, idk but many users have had these issues with 3G since the May unofficial gingersense leaks:
1) 3G being present and fully functional then disappearing from the notification bar altogether even while still being enabled in Settings
2) 3G signal dropping down to 1x and not displaying again until you perform a reboot.
I have experienced this issue and know this resolved it. This rom as well as Incubus26jc or JoelZ's stock OTA gingersense leak, for whatever reason, are a solution to resolve the 3g drop issue not the only solution. Incubus26jc, JoelZ, and Nils each have recommended and note this is a fix. My (non-fact and own) answer to you would be I believe since these three roms are the unaltered and "(un)official gingerbread Sense" files, they recorrect the 3G signal that is going awry.
Try it and let me know how this works. You don't stand to lose anything except a few minutes haha

This solution fixed my problem.

Dang it actually worked. Wish i had done this a while back. Thanks for the simple fix.

Not a problem, I'm just thankful there's a fix.

Accidentally worked for me too
I had the same problem on CM7. Flashing back to my stock 2.2 Android backup fixed the problem. Flashing back to CM7 and OMGB caused the problem to return. I am on the leaked ota now, I have flashed the gingerbread radio, and I am having no 3g issues. I wish that I had found this thread earlier.

Had this exact issue with synergy rls1 and was also told to flash the rom above to fix it. It worked for awile but then 3g issues would return again, even on non sense 3 roms and even on my old virtuous nandroid. If just flashing the above rom works for you and permanetly fixes it thats cool, but if your like me the only fix is to revert back to compleet stock and i mean compleet stock rom radio recovery boot img everything the only thing not stock would be you still want to have s-off as a matter of fact make sure to check you are s-off before going stock. Once stock you need to do a factory reset from the settings menu. What this does is it compleetley wipes your phone back to stock including wiping vzw programing, wich is the key to fixing 3g. Once your phone reboots from the factory reset you will be prompted to dial *228 option 1 to reprogram your phone. Once reprogramed your 3g will be fixed. From there flash clock work or amon ra recovery and then restore your favorite nandroid or install a new rom. I personaly would stay away from sense 3 roms as after fixing mine with the above steps i not thinking installed another sense 3 rom and broke 3g again making me fix it all over again. I have stayed away from sense 3 and havent had any problems since. Note if you have a compleete stock nandroid you can just flash that then flash stock recovery and radio do the factory reset .....
Sent from my ADR6300 using XDA Premium App

Well this is why Android is all about choice.

Well, I tried to install rmk's rom and that didn't work. I also tried to go back to stock with the RUU and the PB31IMG.zip file to do a factory reset, but that didn't work either. Are there any other suggestions that I can try?

Devildog8791 said:
Well, I tried to install rmk's rom and that didn't work. I also tried to go back to stock with the RUU and the PB31IMG.zip file to do a factory reset, but that didn't work either. Are there any other suggestions that I can try?
Click to expand...
Click to collapse
If an ruu and a factory reset with new programing didn't fix your 3g issue its possibly hardware related. Can you still connect at 1x speed?

cmlusco said:
If an ruu and a factory reset with new programing didn't fix your 3g issue its possibly hardware related. Can you still connect at 1x speed?
Click to expand...
Click to collapse
No, I called Big Red and they're sending out a replacement phone. I'm one of them weird people that don't use their phone as a phone too much, but I realized that I couldn't make or receive phone calls or texts either. We got that issue fixed, but they couldn't get the data working.
I guess the world of root is gone for me since it will probably come with Gingerbread on it already. Oh well, I'm probably going to buy a new phone in December anyway, so I'll have a new Dinc to put away in the drawer.

Devildog8791 said:
No, I called Big Red and they're sending out a replacement phone. I'm one of them weird people that don't use their phone as a phone too much, but I realized that I couldn't make or receive phone calls or texts either. We got that issue fixed, but they couldn't get the data working.
I guess the world of root is gone for me since it will probably come with Gingerbread on it already. Oh well, I'm probably going to buy a new phone in December anyway, so I'll have a new Dinc to put away in the drawer.
Click to expand...
Click to collapse
Root may still be possible, check out this thread http://forum.xda-developers.com/showthread.php?t=1306400. Mabey you will get lucky and they will be out of incredibles and they will send you an incredible 2. Ive heard it happens .

cmlusco said:
Maybe you will get lucky and they will be out of incredibles and they will send you an incredible 2. Ive heard it happens .
Click to expand...
Click to collapse
Looks like they are sending me a Rezound...JK. Actually, it looks like they are sending me an OG Incredible. I'll know more tomorrow and will let you know.
Thanks for the link to the root method. I have been studying it and I have all the files downloaded just waiting.
Edit: I did get an OG Incredible, but it came with Froyo on it. I should be good to go as far as rooting it goes. I think that I have an SLCD model though which sucks.

Strange occurence of phone constantly restarting.

Hello,
I have owned a Sprint Galaxy S III since August of 2012 and have been using it pretty much flawlessly until this week.
To give some history, I rooted it once it became a common thing to do and have CWM-based Recovery v5.5.0.4.
I have loaded many different roms - cyanogenmods, m.o.a.r., wicked, miui to try out and many others and have never had an issue.
I recently upgraded to M.O.A.R. v 6.0 at home and everything seemed great - loaded apps, settings, etc. The next day on the way to work, the phone restarted by itself. I thought was strange but chalked it up to a new rom issue. When I got to work, the frequency of the issue increased to the point that the phone was no longer usable as it would just continue to restart, boot, etc.
Restoring the rom I previously had did nothing to help the issue.
I looked up online at possibilities and came across the SD card issue. I replaced it, but still occurs. I've tried a few different roms and no matter what, it seems to continuously boot and restart based on certain locations that I am in or am passing through.
Today, I turned off 4G LTE as preferred mobile network and it seemed to keep the phone on. I have not done extensive testing, but could this be an issue? I am able to use 4G LTE at home with no problem as well as other areas, but it seems that once I am in or pass through certain locations, that it is crashing my phone? Maybe the GPS?
Are there any tips or suggestions of what I can do or try? I am at a loss as to how to fix this when it has not been an issue up until this week after flashing to MOAR v6.0. I've wiped data, cache, dalvik, many times and retried but still is happening.
Any feedback would be much appreciated.

At first it sounded like sudden death syndrome (a power button failure) but when you said turning off 4G fixed it that is very weird. Have you tried asking in the M.O.A.R thread?
------------------------
Sprint Galaxy S3
Stock - Whiplashh Rom - MIUI - Wicked Sensations
Sprint Evo 4G "OG"
Stock - Cyanogenmod 7 - MIUI - Swagged Out Stock
Hit That "Thanks" Button if I Helped You!

Could be your kernel. Or any kernel tweaks you are using

joebeem said:
Hello,
I have owned a Sprint Galaxy S III since August of 2012 and have been using it pretty much flawlessly until this week.
To give some history, I rooted it once it became a common thing to do and have CWM-based Recovery v5.5.0.4.
I have loaded many different roms - cyanogenmods, m.o.a.r., wicked, miui to try out and many others and have never had an issue.
I recently upgraded to M.O.A.R. v 6.0 at home and everything seemed great - loaded apps, settings, etc. The next day on the way to work, the phone restarted by itself. I thought was strange but chalked it up to a new rom issue. When I got to work, the frequency of the issue increased to the point that the phone was no longer usable as it would just continue to restart, boot, etc.
Restoring the rom I previously had did nothing to help the issue.
I looked up online at possibilities and came across the SD card issue. I replaced it, but still occurs. I've tried a few different roms and no matter what, it seems to continuously boot and restart based on certain locations that I am in or am passing through.
Today, I turned off 4G LTE as preferred mobile network and it seemed to keep the phone on. I have not done extensive testing, but could this be an issue? I am able to use 4G LTE at home with no problem as well as other areas, but it seems that once I am in or pass through certain locations, that it is crashing my phone? Maybe the GPS?
Are there any tips or suggestions of what I can do or try? I am at a loss as to how to fix this when it has not been an issue up until this week after flashing to MOAR v6.0. I've wiped data, cache, dalvik, many times and retried but still is happening.
Any feedback would be much appreciated.
Click to expand...
Click to collapse
Are you restoring any System Data ? I would suggest doing a Clean install. Meaning a FULL Wipe : System - Data - Dalvik - Dalvik Cache - Factory Reset ( 3x's ) . I also like to wipe Internal Storage. But that's up to you. Then Flash the Rom, and let it Boot. Do not load anything, or tweak anything. Just leave the device alone for the first 5min. Then test it to be sure everything is working correctly before loading apps, or doing any settings.

Just to update...
I clean installed MOAR 6 again - this time I upgraded CWM to latest version. I clean wiped data/cache, cache, dalvik about 3 or 4 times. Once it reinstalled, I noticed the data wasn't working at all so I did that ##72786# (forgot numbers off top of head) that reactivated phone. The data came back and I thought this was going to solve all the issues...keep in mind I did all this in the evening from home last night.
On the way to work this morning, sure enough once I got in the vicinity of work, phone restarted a few times. I was quick enough to catch it one time to turn preferred mobile networks to 3G first and disable 4G... my phone has not restarted for the rest of the day.
It's great that it seems the issue is isolated to 4G, but I don't understand how it can be fine in some areas and not in others. For instance, at home, 4G works just fine.
I think I will try to go back to stock or try an aosp rom. I've seen in some places talk of MB1 and MD4...is there a way to tell which I have or is that related to anything?

prboy1969 said:
Are you restoring any System Data ? I would suggest doing a Clean install. Meaning a FULL Wipe : System - Data - Dalvik - Dalvik Cache - Factory Reset ( 3x's ) . I also like to wipe Internal Storage. But that's up to you. Then Flash the Rom, and let it Boot. Do not load anything, or tweak anything. Just leave the device alone for the first 5min. Then test it to be sure everything is working correctly before loading apps, or doing any settings.
Click to expand...
Click to collapse
Actually, yes - I have been putting my gmail account information in and it has been syncing the apps. It's just so odd because I haven't had issues for over a year and I don't recall installing any new stuff.

well, now it happened at home when turning on 4g... damn.

joebeem said:
Just to update...
I clean installed MOAR 6 again - this time I upgraded CWM to latest version. I clean wiped data/cache, cache, dalvik about 3 or 4 times. Once it reinstalled, I noticed the data wasn't working at all so I did that ##72786# (forgot numbers off top of head) that reactivated phone. The data came back and I thought this was going to solve all the issues...keep in mind I did all this in the evening from home last night.
On the way to work this morning, sure enough once I got in the vicinity of work, phone restarted a few times. I was quick enough to catch it one time to turn preferred mobile networks to 3G first and disable 4G... my phone has not restarted for the rest of the day.
It's great that it seems the issue is isolated to 4G, but I don't understand how it can be fine in some areas and not in others. For instance, at home, 4G works just fine.
I think I will try to go back to stock or try an aosp rom. I've seen in some places talk of MB1 and MD4...is there a way to tell which I have or is that related to anything?
Click to expand...
Click to collapse
joebeem said:
Actually, yes - I have been putting my gmail account information in and it has been syncing the apps. It's just so odd because I haven't had issues for over a year and I don't recall installing any new stuff.
Click to expand...
Click to collapse
You did not mention wiping system. If you do not Wipe system, and also Factory Reset then it's really not a Clean install. I would still suggest a FULL Wipe, and Clean install. Then run the Device for a while without adding anything. See how it performs.

I ended up just flashing this - http://forum.xda-developers.com/showthread.php?t=1904099 to stock with flash reset.
I am not sure about wiping system - I always just follow the steps of the rom wipe data/cache/dalvik. I will have to research on how to wipe system.

If you never wipe system you are definitely going to run into problems.

joebeem said:
I ended up just flashing this - http://forum.xda-developers.com/showthread.php?t=1904099 to stock with flash reset.
I am not sure about wiping system - I always just follow the steps of the rom wipe data/cache/dalvik. I will have to research on how to wipe system.
Click to expand...
Click to collapse
You just do it in Recovery before you flash. If you look at my Sig on a PC / Internet Mode there is a link on how to do Full Wipe before flashing a Rom.
TEAM MiK
MikROMs Since 3/13/11