Develop Bugs

[Q] Recovery problems after Uncommon Sense

Wondering if I could get some ideas on why I experienced the following failure.
Was rooted with UnrEVOked 3.x for awhile. Installed ROM Manager and experimented with CM6. Didn't like it, restored back to stock with no major
issues. Today, I experimented with Uncommon Sense (did cache/data wipe and backup before). I used "MyBackup Pro" to get all my Apps back and some data. Loved it! After about 4 hrs, I started getting FC on mostly Google apps, but even some HTC apps. Exchange mail wouldn't sync. Phone, TXT, Web all worked fine.
I recovered with Clockwork to the backup I made just before going to Uncommon but all the FC issues persisted. I recovered again 2-3 times, making sure I did data/cache/delvik wipes. FC issues persisted. I pulled the battery sometime in there after a power down. No help.
Finally, I recovered to a backup I had from 6 days ago when I was experiementing with CM6. Fortunately this worked. No FC issues.
Now I'm paranoid about trying out other ROMs. If I cannot cleanly recover after an update, I really don't want to try another ROM.
Any help out there?
1) Why did Uncommon melt down? I'm running pretty standard stuff. No kernal changes, etc.
2) Why did the issues persist when I recovered? Any bullet proof ways of preventing this?
Crispy

Did you try running the "fix permissions" utility in ROM Manager? Noted there that it normal fixes force close issues.
Currently I am running Myn's Warm2.2 RLS3 but had previously loaded Uncommon Sense 1.0 and 1.1 anmd had no major issues with it. ( Myn's is nice! )
Try that permission fix utility and see if that solves your problem.

Yes, I tried the fix permissions utility, but I think it gave me errors.

crispy1 said:
Yes, I tried the fix permissions utility, but I think it gave me errors.
Click to expand...
Click to collapse
Download a terminal emulator, type in
su
fix_permissions
The reboot when done.
Sent from my ADR6300 using XDA App

Thank you. I could try that if I'm brave enough to go to Uncommon Sense again. Any explanation as to the cause? Is what happened to me normal when flashing ROMs and recovering?
Sent from my ADR6300 using XDA App

crispy1 said:
Thank you. I could try that if I'm brave enough to go to Uncommon Sense again. Any explanation as to the cause? Is what happened to me normal when flashing ROMs and recovering?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
ROM's are self contained entities - you probably just had an issue with that particular ROM. I've had awesome experience with the "Revolution" rom by HeyItsLou, Myn's Warm, Skyraider, and Virtuous.

[Q] Nonstop rebooting, even after full wipe/reinstall - last_kmsg inside

Hey everyone.
I know there's a couple other threads with this problem, but none of them included their last_kmsg files. It took a bunch of tries before I could stay booted up long enough to grab it, but I have one.
I'm getting a significant number of reboots on my EVO. Like almost unusable at times. It seems fairly random, although there's a slight suspicion is has something to do with the GPS. Maps has been a crash-cause before and the most recent bout last night was brought on by foursquare. (the annoying part is I had just used 4sq fine 30 minutes prior with no issues. Then, booted it up, refreshed locations and my phone was unusable for hours.)
I've done all the standard things. Fix permissions, wipe cache, wipe dalvik, wipe data/system, reinstall the latest CM7 build (update-cm-7.0.2.1-Supersonic-signed.zip), wipe cache, wipe dalvik. I entered my google account info but told it not to sync anything. It is now rebooting less than a minute after it starts up. I haven't installed any apps at all since this most recent wipe/reload of CM7. It reboots with and without the sd card installed.
I'm at a loss here and getting incredibly frustrated. Many replies say it's as easy to fix as wipe everything and re-do it. Obviously something abnormal is screwed up on my phone and I can't figure it out.
Here's the pastebin from this morning: pastebin.com/Ki7H8bH3 (Crap, I don't post here enough to be allowed to post links. Just add the http part to that.)
And then when I got awake enough, I did another complete wipe/reload. The rebooting is even worse now, it's taken me almost an hour to get to a point I can install es explorer to try and pull another file. And when I did, it was blank.
Any ideas?
Thanks!

1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.

Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!

grifta67 said:
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
Click to expand...
Click to collapse
You're very welcome. Sorry for the delayed response. I was having a late lunch and then drove home. Anyway, keep us informed of your progress and enjoy the rest of your day.
posting & replying via the XDA Premium app.

No worried on any delay, just glad to have someone that took a read and time to reply!
Ugh, it's the randomness of this that has me so frustrated. I thought I had a good install again, I left it sit on the "touch the android" screen for a few minutes and it stayed on. Made it through the setup process ok. I allowed the setup to "auto-download" a handful of the google apps it asks if you want. Once they got to about 38%... boom, restart.
So I did another toooootal wipe and I'll manually install those apps one by one. We'll see...

dougjamal said:
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Seems like this gets posted quite often, huh??? lol

Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.

HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
Indeed, my friend...lol...but it works.
posting & replying via the XDA Premium app.

HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
It does and it wish it was that easy. It's frustrating to read that others seem to have no issues at all yet when I follow those directions, which are everywhere, nothing seems to work.

dougjamal said:
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I re-downloaded CM7 this morning thinking that might be the issue, but it hasn't seemed to help. I'll give a different rom a try probably, maybe there's something other than CM7 I'd be content with.

Whelp, I downloaded SalvageMod and their gapps. Wiped everything, installed salvage, installed gapps, rebooted.
I got through set-up, was ok for a couple minutes, then as I was going into my contacts to see if they had sync'd yet... reboot.
This makes me think this can't be a ROM issue.
Any other ideas?

Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.

jesuspgt said:
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
Click to expand...
Click to collapse
Hey jesuspgt,
I haven't tried that yet. I'll look around for a rooted stock ROM later and give that a shot.
My current status is back to uncertainty. At the moment, my evo has been sitting here fine, not rebooting, for the past hour or two. It's still the Salvage ROM I first installed (i.e. I haven't reinstalled it since it rebooted). Now I haven't really used it any, so it might go to hell as soon as I do that, but for now, it's on and only had that one (maybe two, I can't keep track...) initial reboot.
That's what makes it tricky to diagnose. I know using any custom ROM runs the risk of loosing stability and all ROMs probably produce a reboot here and there. Tough to tell if it's just a "comes with the territory" type of reboot or an actual problem.
Even though I'm sure there's some CM features I'll miss, maybe Salvage is my answer.
Thanks!

*sigh* Well I decided to try using some apps and guess what... reboot.
All I was doing was trying to play a game of Androminion, which is about as basic and not-tasking as possible, so I can't imagine that's what crashed things.

The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.

dougjamal said:
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Excellent, I'm going to try that. My hboot is still 0.93!

Hey dougjamal,
Just wanted to drop an update. I know how annoying it is to help someone out and never hear how things ended up!
Who knows what combo helped, but I'm fairly stable now. After updating my hboot, I flashed to Sprint Lovers, did the ##GPSCLRX# trick and then flashed to the latest nightly of CM7 (63 I believe). Only one or two crashes and one bootloop since then.
Of course, as luck would have it, a new problem showed up in the form of a dead spot on my touch screen. Right about where the "Clear" button is for notifications, that entire strip across the phone won't respond to touch. I was hoping it was a nightly issue, but I switched to a different rom and the issue was still there. Looks like it's going in for a warranty claim after-all!
Thanks for all your help
-grifta67

[Q] Synergy Phone FC's

Running Synergy RLS1 my phone app (com.android.phone) keeps not responding apparently so I get the popup for wait or force close. If i reboot it fixes it for a while but it keeps happening. Im worried im missing calls or texts. And what if theres an emergency and I cant make a call lol. Is this a Synergy issue or what? PS I tried fixing permissions.

You have proper version of hboot and at least a 2.1.x radio?
Sent from my ADR6300 using XDA Premium App

To be honest, I have no clue. How can I find out and is that something I can fix without reflashing/wiping/etc.?

Boot into hboot menu; device off, hold volume DOWN and power until booted into white screen. Hboot version is listed at the top. Use volume button to navigate and power button to select. Radio version ; Settings, About Phone, software information, look at the baseband version, that's the radio.
Sent from my ADR6300 using XDA Premium App

Hboot 0.92.0000
Radio 2.15.00.07.28

Hmm, which version of CWM does the thread say is required, and are those versions of hboot and radio acceptable per the thread?
Got ample space on the sd?
Sent from my ADR6300 using XDA Premium App

What clockworkmod recovery version are you using and what was your rom installation procedure?

ive been using rls1 since it was released and this just started happening the other day. i think it may have something to do with Faceniff. I remember it starting sometime around installing and using that app

Do you know what a clockworkmod is Paintboarder? Its a recovery system and you can find out easily what version you are running by using Rom Manager in your app drawer, and just look under recovery, and it says current recovery: Clockworkmod ?.?.?.?
Hope that helps you if you dont already know. And maybe your getting FC's because you didnt do a clean wipe and install. Did you try fixing permissions?

im completely aware what clockworkmod is. im not that much of a noob. im running 3.0.0.8. like i said. my installation process couldnt be the issue since i have been running without issues since the release of rls1

the issue is seeming to have receded a little since removing Faceniff. That doesnt mean it doesnt still happen. It does. And btw read the OP. I did try fixing permissions.

My bad, didnt mean to downgrade you just wanted to be sure. Well im running Synergy RLS1 right now and i havent experienced that issue. If it were me i would just try reflashing it. So far it is an amazing ROM.
Sorry man i guess i looked past that part about the fixing permissions.

flashed a different radio i saw in someones signature. seems to be working fine now. also i had the 3G and 1X connectivity issues and the solution in the ROM thread fixed it.

I'm using the older incredible without slcd and have had no issues, wonder if that connectivity issue is tied to that in any way? Guys with the newer incredible vs. Old
Dink sporting Synergy RLS1. Xda app.

Mods and not wiping seem to cause pretty much every error with FCs that I run into. Only time I get them reintroduced it seems is if I freeze/remove something that's needed by another program or if I restore data for certain programs (which were backed up under another ROM).

I have RLS 1 installed too and it ran fine for about 6 days before I started getting fc's. I was rebooting at least once a day the first 6 days then I didn't reboot for 2 days and started getting fc's. So I started rebooting daily again and I don't seem to have any more problems.

[Q] GNx bricked? Screen not unlockable, constant softreboots

Hi all,
this is the 3rd time this is happening to me with different ROMs. The problem is:
The phone boots up normal, I can swipe to unlock, enter my PIN, but after pressing OK it won't unlock the SIM. If I lock the screen it won't come back on. It stays black whatever I do. After some time the phone reboots (soft reboot) and everything starts from the beginning.
The first time this happened I was using Modacos Ir9. I had the phone switched off over night and switched it on. Only thing that seemed to help was completely unrooting the phone and rerooting it again.
The second time I was using codeworkx CM9 Builds and tried to update. I restored my nandroid, but it kept happening. Flashing the XXKK1 Radio did the trick here.
Now it is happening again. This time I installed dropbox and the phone froze on the setup wizard...
I don't want to unroot the phone, it takes forever to restore the SD card.
Any advice on this one?
Update:
- Flashed the following radio images without any success: XXKL1, KRKL1, UGKL1 and XXKK1
- Used my older nandroids from CM9 and Modaco Ir10. NOT WORKING
- Wiped every nandroid. NOT WORKING AT ALL
- Reflashed CM9 and Ir10. Still NOT WORKING
I'm so lost I'm going to revert to stock and unroot... and try how far I can throw an 1 month old GNx from the fourth story.

I don't know much on the development part so I don't know why its doing that I can only suggest using odin and going back to stock.
Sent from my Galaxy Nexus using xda premium

I had similar problems with mine once. Only thing that helped me out wasn't unrooting though. A complete factory reset was enough to make me go on again.
I posted a thread here then to ask people if anyone experianced the same but got no reaction what so ever zo I guess "we" are a dark minority.
I don't know what it caused it or what the solution might be but a Factory reset did it for me.
Good Luck!

C-4Nati said:
I don't know much on the development part so I don't know why its doing that I can only suggest using odin and going back to stock.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Last time it was working again after reverting to stock. But I bought it to use Custom Roms

I would say go back to stock w/ odin, Wipe everything and start again.

Diger36 said:
I had similar problems with mine once. Only thing that helped me out wasn't unrooting though. A complete factory reset was enough to make me go on again.
Click to expand...
Click to collapse
Factory Reset wasn't helping unfortunatly.
Flashed the original factory image through fastboot. Now everything is working again. I'm restoring my SD backup now and will try to get CM9 working again.
If it would keep failing in stock I could return the phone. Now I'm left with "hopefully it isn't happening a fourth time" and "My phone doesn't work I need 4 hours to get ich working"

the_alien said:
Factory Reset wasn't helping unfortunatly.
Flashed the original factory image through fastboot. Now everything is working again. I'm restoring my SD backup now and will try to get CM9 working again.
If it would keep failing in stock I could return the phone. Now I'm left with "hopefully it isn't happening a fourth time" and "My phone doesn't work I need 4 hours to get ich working"
Click to expand...
Click to collapse
Fastboot flash stock google images. And your phone isn't bricked. Stop using the term wrong. It's most likely a software issue or you're doing the rom flash procedure incorrectly.
A bricked phone is a phone that is unaw to go into bootloader and recovery mode and cannot start android.
Sent from my Galaxy Nexus using xda premium

zephiK said:
Fastboot flash stock google images. And your phone isn't bricked. Stop using the term wrong. It's most likely a software issue or you're doing the rom flash procedure incorrectly.
A bricked phone is a phone that is unaw to go into bootloader and recovery mode and cannot start android.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sorry for using the term wrong, I thought it just referes to broken phones.
The ROM flash is correct and it runs for some time and the problem occours after a few days... the only thing that helped was reverting to factory images and after that restore the nandroid from the "broken" Rom.
So the Rom works... than keeps crashing, I do a nandroid backup and only a factory image stops the crashes. But the Rom keeps working after I restore it.
I can't see why this could be a hardware issue. And I can't see how I should explain it to the store "Yes, it is working but not with custom roms, and I bought the Nexus because of custom roms..."

the_alien said:
Sorry for using the term wrong, I thought it just referes to broken phones.
The ROM flash is correct and it runs for some time and the problem occours after a few days... the only thing that helped was reverting to factory images and after that restore the nandroid from the "broken" Rom.
So the Rom works... than keeps crashing, I do a nandroid backup and only a factory image stops the crashes. But the Rom keeps working after I restore it.
I can't see why this could be a hardware issue. And I can't see how I should explain it to the store "Yes, it is working but not with custom roms, and I bought the Nexus because of custom roms..."
Click to expand...
Click to collapse
I'm willing to bet an app is causing it.
Sent from my Galaxy Nexus using xda premium

One of my colleagues had this issue with an early CM9 build on his Nexus S - turned out it was an app that is incompatible with ICS. Every time it tried to launch a notification, poof. So I would have to side with Josh in the post above mine.
A way for you to verify / discredit this theory would be : When you say it works with the stock ROM, are you re-installing everything you have when you are on stock? My understanding from what you've written above is that you're only getting your full suite of apps back when you restore your (presumably custom ROM) nandroid backup...

Potterified said:
One of my colleagues had this issue with an early CM9 build on his Nexus S - turned out it was an app that is incompatible with ICS. Every time it tried to launch a notification, poof. So I would have to side with Josh in the post above mine.
A way for you to verify / discredit this theory would be : When you say it works with the stock ROM, are you re-installing everything you have when you are on stock? My understanding from what you've written above is that you're only getting your full suite of apps back when you restore your (presumably custom ROM) nandroid backup...
Click to expand...
Click to collapse
It can't be any app or ROM because IF it happens, it happens on all ROMs, regardless of wipe or not.
It just happened again and i wiped everything and tried using AOKP MS 3. Wasn't working... So I tried using the phone without the SIM card, because the hell only breaks loose after entering my PIN. And it worked. I could use the phone...
I put it back in and it worked...
I'm restoring my CM9 nandroid right now. I'm hoping it works...
edit: Nope, ripping out the SIM doesn't work. I'm reverting to stock and wait what happens. If it crashes again I'm trying to return it.

One X: Apps break on restart

Has anybody else had this problem? Everytime the phone reboots, loads of apps break completely, and the only way to fix this is either by moving the app to the storage and back, or by restoring a titanium backup and praying the data is restored
It's a wholly tedious and not a nice thing to do every time you need to rebbot the device. Is there a solution to the problem? I'm using the stock 4.0.3 Rom supplied by Orange, and unlocked and rooted using the htcdev method.
Sent from my HTC One X using xda app-developers app

Hi, something has gone wrong, you'll need to wipe, re-flash etc

freakzone said:
Hi, something has gone wrong, you'll need to wipe, re-flash etc
Click to expand...
Click to collapse
Huh, kinda unusual for a huge carrier like Orange to ship phones with problems that can only be fixed by re-flashing. Probably some meddling on their part that's made it unstable. I'll wipe/flash the normal stock 4.0.3 ROM, and see if that helps.

Kyoraki said:
Huh, kinda unusual for a huge carrier like Orange to ship phones with problems that can only be fixed by re-flashing. Probably some meddling on their part that's made it unstable. I'll wipe/flash the normal stock 4.0.3 ROM, and see if that helps.
Click to expand...
Click to collapse
Three shipped me an HTC Desire and the gmail app crashed every single time with the stock rom. If you wish you can bring it to orange and they will sort it out for you. I assumed you were looking for a different type of solution.