Database Users

[Q] PRL UPdate is it worth it?

I just got a text from sprint to update my PRL. I HAVE a rooted phone with cyanogenmod 6 on it. Should I update?

I just got the same text, running CM6 also. First time in a year now that I have ever seen a text about a PRL update. Not going to run out and restore a sense nandroid just to check to see whats up though.

This has me confused as well. In all my years as a sprint customer I have never received a text about an update.
Sent from my HTC Hero using the XDA App

Ive updated and for me a little better phone singal thats all i notice other than that its fine Im runnig CM6 Stable i used ninfinity stock rom to update then switched back hope this helps
Root-Hack-Mod-Always™

Anyone know is this the 60671 PRL or what? I got the text too and so did my wife...

I'm new at this with android. I have ROM Manager and I have a backup when I was on stock. Can I use Rom Manager backup/restore function and restore to stock and then update? I haven't tried restoring yet, will this restore exactly how it was or will I loose me data?

Ur better off flashing ninfinity rom after u do a nandroid backup of ur current rom its almost like stock but with performance enhancements use that to update ur prl/pri then nand restore back to ur current rom that way u wont loose root good luck
Root-Hack-Mod-Always%

pwachleman said:
Anyone know is this the 60671 PRL or what? ...
Click to expand...
Click to collapse
I updated last night and now have 60671. Sounds like you're in luck and don't need to update. Color me jealous.

I was pretty sure I've seen at some point that you can just flash the new PRL to your phone... I could be wrong though

I nandroided back to an old 1.5 rooted backup, but the PRL update function kept failing with error 1012.
I just downloaded it from PPCGeeks, pushed it to my phone and then used ##PRL# to manually load it. Then wiped and loaded a backup of my current Froyo 2.2.1 installation.

I just backed up my current CM6 rom, restored the Fresh 2.3.3 rom I was running before that, got the prl update with no problem, restored the CM6 rom and now I have 60671 in my CM6. I didn't even know you could download the file on PC and push it over.

I messed up once I decided to stick with cm6, I deleted my fresh rom back up. Where could I get a back up of fresh, I dont want to install fresh and have to wipe Or can I wipe and restore my current back up of cm6 via PC and be OK?
Thanks
Pulling fresh rom back up off my wifes phone

Just make a nandroid of your current setup, wipe, then flash fresh. After you get done you can just restore your nandroid.

cordell12 said:
I messed up once I decided to stick with cm6, I deleted my fresh rom back up. Where could I get a back up of fresh, I dont want to install fresh and have to wipe Or can I wipe and restore my current back up of cm6 via PC and be OK?
Thanks
Pulling fresh rom back up off my wifes phone
Click to expand...
Click to collapse
I was able to update my wifes PRL by flashing back to fresh rom, her back up. So I took her back up and put it on my phone. I tried to update PRL and am getting ERROR 1012 ??

Just flash the Rom from scratch...

joehunni said:
Just flash the Rom from scratch...
Click to expand...
Click to collapse
Doing that now, my main worry was starting over from a bare cm6
Thanks for the help
UPDATE....Flashing new working! Back to cm6 now, lol. Thanks again!

cordell12 said:
I was able to update my wifes PRL by flashing back to fresh rom, her back up. So I took her back up and put it on my phone. I tried to update PRL and am getting ERROR 1012 ??
Click to expand...
Click to collapse
I know you have it resolved now, but if anyone else doesn't have an old nandroid... you can download the 60671.prl file from various places - either on the phone itself or via pc and use adb to push it. Then you can load an older rom that has the ##PRL# code working, and have it load the file that way. Then just nandroid back to your everyday rom.

cant download from market after going back to a 2.1 rom from 2.2 beta

i need some help. i cant download from the market after i went back to a 2.1 rom from a 2.2 beta rom. any ideas?

Is it stuck on downloading?
Usually when it is, I just leave it there-- then after a few minutes, it will tell you it's installing.
You can also try going to Settings > Applications > Market and clearing data and cache. Then open up market again and let it refresh.

i tried that already and it still hasnt changed. even did a factory reset twice

pjames said:
i need some help. i cant download from the market after i went back to a 2.1 rom from a 2.2 beta rom. any ideas?
Click to expand...
Click to collapse
I SO don't know what I'm talking about. Ever. But especially here.
However having said that, perhaps you flashed the baseband to 2.2 with the modem file and Odin, and need to flash it back to a 2.1.
Anyone confirm/feel free to correct me and call me names....
Also I've had issues with the market upon restoring backups after trying out different ROMs. Sometimes I stop all the backed-up market downloads, then clear the cache, the reboot and try downloading apps again one or two at a time and that works. Recently I had an issue where the market thought I didn't have a program installed, but I did have it from a Titanium backup. Market kept trying to restore it. Then I uninstalled it from my Epic and reinstalled it from the market.

pjames said:
i need some help. i cant download from the market after i went back to a 2.1 rom from a 2.2 beta rom. any ideas?
Click to expand...
Click to collapse
I had the same issue when I reverted back to 2.1. Are you doing a restore from a nandroid backup? I tried doing a straight nandroid restore, failed. I tried wiping and flashing a 2.1 rom and then doing a data restore, failed. Finally, I just gave up and forwent the data restore. I had to rebuild everything, but it worked.
I'm sure you can find a more elegant solution, but it's what worked for me.

Darkshneider;9343371Content deleted/QUOTE said:
While I don't necessarily disagree with the point you're trying to make, there is no need to be an ass about it.
The damage is already done. Mods can move or whatever they want with the thread. You have no control over it, other than to state your discontent with it. At that point, polite encouragement is better than abusive.
Click to expand...
Click to collapse

Ibwas having the same problem. It was caused by restoring from a nandroid backup. I just reflashed and restored all my apps manually
Tapatalkin it from my Epic 4G

i fixed it by going back to the 2.2 beta rom i was using. i reverted back to 2.1 because gps wasnt working but now gps is working on 2.2 and i have market access. i would say close this thread but i sure somebody else will have this problem and need the help so leave it open

Nandorid process for the epic?

So I'm new to this phone and I'm unsure about its backup process and its restore process. I come from the moto cliq phone and that phone had a different custom recovery that in my opinion was better.
With this clockwork recovery unless I'm doing something wrong I get force closes left and right when I do a rom restore. So what happens is I completely restore the rom and as soon as the phone loads into it everything will give me force close warnings which in return never let's me fully load in, making the restore crap! Because I have to start fresh.
So could anyone here tell me the proper process of backing up my rom/ restoring, using this clockwork recovery? Or is this a known bug? Rom I was using was EE 1.2.9.
Thank you for any sorta help.
- Its just going to be Epic!

Pvt WhoOkid said:
So I'm new to this phone and I'm unsure about its backup process and its restore process. I come from the moto cliq phone and that phone had a different custom recovery that in my opinion was better.
With this clockwork recovery unless I'm doing something wrong I get force closes left and right when I do a rom restore. So what happens is I completely restore the rom and as soon as the phone loads into it everything will give me force close warnings which in return never let's me fully load in, making the restore crap! Because I have to start fresh.
So could anyone here tell me the proper process of backing up my rom/ restoring, using this clockwork recovery? Or is this a known bug? Rom I was using was EE 1.2.9.
Thank you for any sorta help.
- Its just going to be Epic!
Click to expand...
Click to collapse
I can't tell right off, because EE is updated now, but is EE 1.2.9 a froyo ROM? Some apps will FC because they are NOT for froyo. If you did the backup from eclair and then flashed to a Froyo rom you may see those FCs.
You might try booting into clockwork, wiping the cache and user data and system, then doing an advanced restore and restoring just the data. But again, apps that are not supposed to run on froyo will fc.
Also, it sounds like you can re-load everything fresh with too much hassle - you've had lots of practice by now - why not try flashing a new EE ROM like 2.0.0.01. Follow the instructions and FLASH the DK17 modem. Then you can reload your apps from the market and do an updated nandroid/clockwork backup.

EE 1.2.9 is the rom before the froyo beta drop that he did. When I do backups everything goes smoothly, but when I restore and I just hit restore a rom it seems to restore fine, but the min I pass the load up screen all I get is force close for everything.
I don't know if I'm doing my back ups or restores wrong or if maybe it could be the rom? But somehow I doubt its the rom. I'm trying to figure out if there's a procress to backup or restore that I'm doing wrong?
All I hit is back up when doing my nandroid and to restore I just hit restore, I didn't do advance restore. Any tips?
Thanks for the reply.
- Its just going to be Epic!

Are you using a theme? Any time I have tried to restore a theme it has caused endless force closes.
Sent from my SPH-D700 using XDA App

Pvt WhoOkid said:
EE 1.2.9 is the rom before the froyo beta drop that he did. When I do backups everything goes smoothly, but when I restore and I just hit restore a rom it seems to restore fine, but the min I pass the load up screen all I get is force close for everything.
I don't know if I'm doing my back ups or restores wrong or if maybe it could be the rom? But somehow I doubt its the rom. I'm trying to figure out if there's a procress to backup or restore that I'm doing wrong?
All I hit is back up when doing my nandroid and to restore I just hit restore, I didn't do advance restore. Any tips?
Thanks for the reply.
- Its just going to be Epic!
Click to expand...
Click to collapse
So at some point your phone is runnign with NO fc's? And then you back up and restore to test the backup, and suddenly you have FCs? You should not get FC's from restoring a nandroid backup that you had just made from a flawless ROM.
It's possible that one of your resident programs is conflicting with the others - if you go into settings, applications, running services, do you see anything there that perhaps should not be there?

s9ortner said:
Are you using a theme? Any time I have tried to restore a theme it has caused endless force closes.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I've never used a theme for my epic, none really catch my eye.
- Its just going to be Epic!

bilestoad said:
So at some point your phone is runnign with NO fc's? And then you back up and restore to test the backup, and suddenly you have FCs? You should not get FC's from restoring a nandroid backup that you had just made from a flawless ROM.
It's possible that one of your resident programs is conflicting with the others - if you go into settings, applications, running services, do you see anything there that perhaps should not be there?
Click to expand...
Click to collapse
You're exactly correct. A perfect example is right now I'm running EE 1.2.9 with no force closing problems with all my apps installed and everything is running smoothly, I made a back up and then wiped my phone completely of everything.
Then went ahead and tried hitting restore, everything seemed to have restored because I got no errors in recovery but the min the phone loaded into home screen I get errors like "launcher pro force close, beautiful widgets force close." And so on.. I've clicked over 100 times force close and everything seems to give to me force close errors renderng my phone useless, after the system restore.
So I had to start fresh again and just reinstalled everything and everything is working fine. Weird huh? I don't know what I could be doing wrong.
Thanks for the help.
- Its just going to be Epic!

You need to do an advanced restore and only restore data. Basically you flashing a 2.1 rom over a 2.2 rom this will break things. Since you are going from 2.1 to 2.2 your best bet is to reinstall all your apps from scratch or use titanium backup to restore your apps. You are bringing in data from 2.1 to 2.2 that shouldn't be there that is why your getting fc's.
Sent from my SPH-D700 using Tapatalk

skeeterslint said:
You need to do an advanced restore and only restore data. Basically you flashing a 2.1 rom over a 2.2 rom this will break things. Since you are going from 2.1 to 2.2 your best bet is to reinstall all your apps from scratch or use titanium backup to restore your apps. You are bringing in data from 2.1 to 2.2 that shouldn't be there that is why your getting fc's.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I'm not updating to 2.2 yet. This all is happening on 2.1 using EE 1.2.9 (eclair.) Which doesn't make sense to me at all. Unless something is wrong with clockwork recovery?
- Its just going to be Epic!

Is there a way to access Apps on a soft-bricked phone?

I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!

Android 17 said:
I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!
Click to expand...
Click to collapse
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.

mattykinsx said:
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.
Click to expand...
Click to collapse
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.

Android 17 said:
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.
Click to expand...
Click to collapse
You could wipe /boot and /system as well and reflash and see if that fixes it.

mattykinsx said:
You could wipe /boot and /system as well and reflash and see if that fixes it.
Click to expand...
Click to collapse
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.

Android 17 said:
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.
Click to expand...
Click to collapse
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.

mattykinsx said:
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.
Click to expand...
Click to collapse
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.

Android 17 said:
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.
Click to expand...
Click to collapse
Sorry I took my Xanax to sleep or else I'd likely be able to think of some kind of solution.
Hopefully someone else can help you out.

I think in CWM if you mount System&Data /apps you could utilize adb pull..... Also did you set up any custom partitions, a2sd, data2ext, ect... ?
Sent from my HERO200 using XDA App

Actually thanks for the suggestions guys, I managed to dig up an older version of the rom saved on my downloads folder and flashed it and booted.
For some odd reason, an older release labeled as experimental works better than the 1.2 stable...
It's strange too because I looked around Deck's thread and no one else reported any problems similar to what I was having at all.
For all intents and purposes it appears to be very stable and functional for everyone BUT me
Thanks for the suggestions though. I guess I'll hold off on flashing any roms for a while or wait for a newer version and try flashing with a full wipe.

Cool glad you got her going.
Kaaameeehameeehaaaaaa!

Services crashing 2.3.5

So ever since I started some 2.3.5 ROMs I've been noticing that the ROM runs great for a couple of days. Just when I think all is going great services start crashing. Google Services, Email, Browser, Titanium Backup... etc. I'm really not sure what is happening here. I've noticed it on MIUI ROM so I switched over to NoFrills-AOSP and nope still having the same issue. Does anyone else have this issue?

reboot your phone every no and again, never hurts, also, Q&A.
This has happened to me every now and then, and reboot your phone every couple of days is good for it. Could also be you have flashed a different kernel over kernel and not cleaned stuff out.

LoL Yeah this probably belongs in Q&A but what was there at the time didn't seem to Developer-ish looking haha.
Anyways, yeah I've tried rebooting about 5times already. After every flash I reboot twice before really settling down to put stuff back in. That might have been the case when I was doing the MIUI ROMs but the NoFrills-AOSP ROM I have now was fresh from Stock Odin flash. Should I just try a new Kernel maybe?

also happening to me. i reboot once a day but still it occurs. btw im on MIUI

Over time I've noticed the same thing. Similar to a Linux memory leak... No matter what rom, radio or kernel I use the available ram dwindles to almost inoperable speed. A reboot on my Vibrant is almost daily depending on what I do with my phone. Even with CWM, Overstock and Zendroid all together I still have the same issue's, any viable fixes for this?
Sent from my SGH-T959 using XDA App

i knew it wasn't just me. i just rid did my phone back to stock UVJFD. i'm trying to decided if i should just go back to Bionix or maybe try again with either MIUI or Simply Honey. If stock were 2.2 I'd be fine and just stick with it, but its not so I need to flash something AH!! lol

CharlieBoy808 said:
So ever since I started some 2.3.5 ROMs I've been noticing that the ROM runs great for a couple of days. Just when I think all is going great services start crashing. Google Services, Email, Browser, Titanium Backup... etc. I'm really not sure what is happening here. I've noticed it on MIUI ROM so I switched over to NoFrills-AOSP and nope still having the same issue. Does anyone else have this issue?
Click to expand...
Click to collapse
Stop restoring from titanium backup, and just reinstall your apps from scratch.
I had this same issue, found out it was my titanium backup app restores that were at fault.

Ya alot of people don't realize.. you can't use titanium with miui.. use the miui backup app.. if u come from a a different rom, Use titanium to restore, backup with the miui backup app, then reflash miui after wiping system, then restore using miui restore app.. everything should b alot better
Sent from my T959 using XDA Premium App

CharlieBoy808 said:
i knew it wasn't just me. i just rid did my phone back to stock UVJFD. i'm trying to decided if i should just go back to Bionix or maybe try again with either MIUI or Simply Honey. If stock were 2.2 I'd be fine and just stick with it, but its not so I need to flash something AH!! lol
Click to expand...
Click to collapse
Stock is 2.2
Sent from my T959 using XDA Premium App

i use titanium back up all thie time with miui and it gives me no problem at all and i havent had any crashing at all im runing miui 1.9.16 ss-6 with bail and its giving me no problems at all are u doing a full wipe when u install i always wipe data cache and then format data and system thin install everything hope this helps

ceoesquad said:
i use titanium back up all thie time with miui and it gives me no problem at all and i havent had any crashing at all im runing miui 1.9.16 ss-6 with bail and its giving me no problems at all are u doing a full wipe when u install i always wipe data cache and then format data and system thin install everything hope this helps
Click to expand...
Click to collapse
Well you've just gotten lucky
Sent from my T959 using XDA Premium App

TI backup is not necessarily the issue with this. I've had the same problem for the last few week, and I've been using the MIUI backup exclusively. I might've used TI the first time I restored, but every other time it's been MIUI, mostly because it's WAY better.

Hmm ok well maybe the stock Odin I have is 2.1 because that's what it said in the about phone section. Anyways, TI causing a problem? or not causing a problem.. hmm LoL Oh how I love technology conflicts. Well right now I'm sitting on Simply Honey RC1 and so far no crashes yet. I went from Stock to Light then to Simply Honey as instructed. I did restore using TI, but I might flash back to MIUI from Stock and give it another try.

check your datadata partition and see if it's full. since miui is based off cm7, i'm assuming it uses the same partition scheme. if datadata is full, that may be your problem.