Related
Hey Dudes,
I have a really big problem, i bought for my father a navigation system. clarion Map360, but I was so stupid and tried to but a other windows mobile on it. Now I have the problem that I have a blue screen and the navi asked me if I want to upgrade the windows mobile by USB or SD-Card. But I didn`t have the right Image i think.
I need the Winceimg.cks or the whole Image. I hope somebody can help me.
Sorry for my English..
Greetz Slimer
What situation are you in right now?
Did you try to reboot it?
Did you back up the old image before attempting this?
Generally this thing are protected from writing images not belonging to them so unless you selected to format the flash first you may still be ok.
If not, I doubt your unit can be salvaged without a lab since ROM images for PNDs are almost impossible to come by, specially for less popular brands.
My Situation, i think i killed the flash rom, if i start the system normally nothing works, no screen nothing, but when i started with the start and the reboot button i come to the menu with a blue screen.
1. wince upgrade
2. uboot upgrade
3. exit
Greetz Slimer
P.S.: I didn`t backup the Image, but i have the same system Clarion Map360 at home to, thats working. Maybe you can give me tutorial, how to backup the image from the other one, to repair the old one.
Other Question, Is it possible to put a Windows Mobile 5 System on it, to run another GPS Software like TomTom 6
Well sounds like you are in trouble.
You need to look around the menu options. Sometimes with thees devices there is an option to dump the current ROM to SD.
If it exists use it if not you probably need a lab.
You can not put WM 5 or any other Windows Mobile on this device unless:
1) You can get the original ROM
2) Extract all drivers from that ROM
3) Incorporate drivers in Windows Mobile image
4) Package Windows Mobile image to suite your device memory configuration
I other words: mission impossible.
You can try to use the cab at this link to run WM software.
hmm damn.. there is no point for dump rom to sd card... but if its possible to get this rom somewhere in the Internet. maybe somebody have it here in this forum.. because i found a thread but the link to the image is down...
Greetz Slimer
Hi,
I'm looking for full backup (making image, like a ghost for laptop PC) software.
I've ever used SPB, but it was not full image.
I'd like to make a image backup file onto storage card or my PC through USB, then once my TyTN has some critical issue, I'd like to do image back.
Do you have any recommendation software?
Your advices I appreciate!!
i haven't come across anything for ppc .. only software that allows backups. would be nice to create image backup though.
I think Sprite Clone does what you are asking for.
I use BackupManager that allows me to create .exe full backups.
Take a look here.
http://www.sunnysoft.com/software.php?idarticle=245
Price is $20 but it's worth the price.
Have to do a hard reset? Fine, just execute the backup file and everything is back!
I'm VERY happy with it.
By the way, it's very quick and my backup is stored on the memory card.
Sprite backup appears to backup the entire filesystem (PIM, windows, all folders and even SD) to an executable file. It runs before the device boots so i guess you could use it to "image" your phone. I have made a backup of my filesystem but i haven't tried to restore it yet. If it works, let me know, its the only thing stopping me flashing (apart from waiting for the drivers of course!!)
I dunno if its free, it came with my o2 stellar (kaiser)
http://www.spritesoftware.com/sprite-backup/
Actually, it looks like it might be free
My AT&T Tilt came with Sprite Backup, which seems to do a full image. I ran with the stock AT&T setup for the first 30 days I had the Tilt, but installed a lot of stuff on top of that. When I tried hard resetting it, I was able to restore everything right back to the way it had been at the time of last backup - data, apps, settings, registry tweaks, so forth (I was trying out Sprite to be sure of what it was actually doing).
I've also saved Sprite *.exe backups to my Vista desktop, via USB (home premium 32-bit SP1), and my G4, OS X 10.4.11 powerbook, for that matter (via bluetooth file transfer), put them back on my Tilt's storage card, and run them from there - no problems (I do not have my 4GB card encrypted).
Sprite works well. Ive done restores successfully and you can get Sprite Explorer which runs on your desktop and allows you to restore single files from your image which is great.
Thanks for your information!!
Now I'm trying to use Sprite Backup. Looks nice.
This is the one I was looking for.
Thanks (^_^)v
hmm but does it take a picture of the os stack as well? Im wondering because i want to experiment with ROMs when my current rom is working fine (i know i know - dont fix what aint broken!). I found spb clone which looks like it would do it so im gonna give it a shot.
spb clone is my 2c opinion.
never used others.
I've used it several time to clone my phone to a friend of mine phone's.
result = wonderful!
I use sprite backup aswell and its the best iv seen so far but it doesnt work across roms. So if you made a backup on a stock rom, you cant restore that backup onto a different rom.
So guys I'm really getting sick of using Windows XP and want to upgrade to Windows 7.
I'm just wondering how the best way to go about it after I've got the ISO burned or whatever, like how to copy my files etc. without any corruption. Also W7 will work with any hardware if I'm correct so it won't matter that I have outdated hardware?
Basically, can anyone give me a step-to-step guide on how to upgrade from scratch.
Any help appreciated guys.
I think when you insert the disk with windows running you'll have an upgrade option which will backup everything, install the new OS, then put back everything the way they were before (by everything I mean, registry entries, documents, user settings...)
or you can boot from the disk and choose click the upgrade button.
It's an easy process, but it took me a few hours to upgrade from windows vista to 7
husam666 said:
I think when you insert the disk with windows running you'll have an upgrade option which will backup everything, install the new OS, then put back everything the way they were before (by everything I mean, registry entries, documents, user settings...)
or you can boot from the disk and choose click the upgrade button.
It's an easy process, but it took me a few hours to upgrade from windows vista to 7
Click to expand...
Click to collapse
actually the upgrade option is only if your on vista, best thing to do is backup your files to a external hdd and start fresh
Yep. Back up your files to an external drive, insert disk, boot from CD, once you get to the drive selection menu, select the drive, drive options and format. This will clear your HD, and give you a fresh install. Also make sure you can find all the drivers for 7, and if you don't want to pay for 7, find a backup of an OEM Win 7 disk, and install with that. Might need to update your BIOS to 2.1, but that isn't always the case.
Where are the files I should be backing up? Do any files need to be backed up in like sys32 or anything or just files like music, pictures, programs etc.? Is there a way I can backup program data too? The likes of favourites and bookmarks for chrome etc.
How do I go about checking/updating my BIOS?
If you're going 32-bit to 32-bit you can put the 7 install on the same partition as the xp install, but you won't have any registry keys from XP.
As for backup, music, photos etc. And usually you can find the update on the manufacturers website, it's a regular install. What MB to you have?
Back online, some editions done.
There is always easy transfer. RUN THE UPGRADE ADVISOR before purchasing though
Sent from my HTC Wildfire using XDA App
Hi,
i've imported my photos from my internal memory via sony bridge for mac accidentally in Iphoto. I didn't see the app was faded and crossed. Turns out only the app Photos is still working. So after importing 2700 pics (big trip and behind with backup), the question popped if I wanted to delete the fils on my phone and I said yes. I tried to re install Iphoto, but nothing there, but older pics. I tried the temporary files from the Mac, but nothing.
So now I got my hopes up for a data recovery software thing. But although Windows (Im working on another laptop) did install the drivers correctly and I see my phone in the folder structure, no data recovery software recognises my phone although I switched to MSC and USB-debugging. I think because I haven't rooted it i suppose. Well, that's what all the forum members say
So I think rooting is my only option left? I am wondering if it works for my goal to get my data back. I read that unlocking the boot loader means everything will be erased, so then there would be no point for me to do this. Is it possible to root it without losing my (deleted) data on the internal memory? I know it is being overwritten now as we speak, but I'm sure I can save a few photos!
thanks a million!
First off, I don't fully understand the first bit involving iPhoto. But if I understand correctly, you need to recover files deleted from internal memory.
I think recognizing a phone's internal memory is indeed a steep expectation for general Windows file recovery software. However, there may be some specialized programs out there designed just for that purpose. I know for a fact they exist for iOS for example. Not that I'm a fan. Anyway, googling "recover Android files Windows" showed some interesting results, but as I have no experience I can make no recommendations. I did see Easeus among the results, and I personally would start there based on experience with other software by them: http://www.easeus.com/android-data-recovery-software/free-android-data-recovery.html
This would be your safest bet. As you probably know, your photos are still there as long as they are not overwritten. Being able to recover from an external device (PC) is therefore preferable to making changes to your internal memory. It's also far less complex than rooting
Another thought before getting into rooting: I don't suppose you had an app like Google+ making automated backups of your pictures? If so, you might find them on your Google Drive. This also might be a good idea to avoid trouble like this in the future
Third and last resort: you could try a data recovery app on your phone, like GT Data Recovery. That does requires root. The good news: you don't need to unlock your bootloader to be able to root. Locked bootloader means you're limited to stock roms, but they too can be rooted.
Here's a useful thread describing in detail what you'd need to do:
http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
In your case, I'd run data recovery ASAP, meaning
Downgrade your firmware, leaving data in Flashtool unchecked (!!) (See thread's FAQ for detailed explanation)
Root
Install GT Data Recovery or similar from Google Play and run it
After you've recovered all photos you can and backed up all your other data, follow the procedure in the recommended way, which includes wiping data. Do note however, that the firmware mentioned there is outdated (March 2015). You can find up to date firmware here: http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
Good luck!
(Thanks to @bilboa1 and @istux for their useful posts!)
Thanks!
I did try several data recovery software programs, including EaseUS, but none recognised my internal memory unfortunately. I switched all auto back up programs like Google Plus off, because it was just too much. I take so many pics of my kids and the selection process usually doesn't take place directly, so it backs up everything and I've got to many pics in my Google Plus account. But this was a wise lesson i should backup somehow.
So only option 3 is left. As i read it, when I root it, the data on my internal memory won't be deleted? Stock ROM is fine for me, I'm very happy with my standard software, if rooting is what it takes, that's what i should do.
If you're rooted, you can use the app DiskDigger. Worked for me
Sent from my D5833 using XDA Free mobile app
kjoz said:
Thanks!
I did try several data recovery software programs, including EaseUS, but none recognised my internal memory unfortunately. I switched all auto back up programs like Google Plus off, because it was just too much. I take so many pics of my kids and the selection process usually doesn't take place directly, so it backs up everything and I've got to many pics in my Google Plus account. But this was a wise lesson i should backup somehow.
So only option 3 is left. As i read it, when I root it, the data on my internal memory won't be deleted? Stock ROM is fine for me, I'm very happy with my standard software, if rooting is what it takes, that's what i should do.
Click to expand...
Click to collapse
Generally speaking, wiping data is recommended when flashing a new ROM. Because Giefroot requires older firmware, you need to flash that firmware. Which means a data wipe comes recommended. Technically however, wiping data is optional. It is possible to downgrade without wiping data (by unchecking the respective option in Flashtool). So that is what I'd do in order to recover your pictures.
Once that has been accomplished, along with a backup of all other data you wish to keep, I would start the whole process again as described in the thread I linked to. Because this time, the objective would be not data recovery, but ending up with a stable phone. And that means wiping data. (Highly recommended.)
I don't want to complicate things further, but if you don't care about being rooted after data recovery, you could just upgrade to regular stock firmware instead of pre-rooted firmware. This would allow you to skip a few steps of the process, and also avoid being unable to apply Sony's OTA updates. (Significant updates can cause a loss of root.)
Personally, I would not want to give up root once I have put effort into getting it.
kjoz said:
Hi,
i've imported my photos from my internal memory via sony bridge for mac accidentally in Iphoto. I didn't see the app was faded and crossed. Turns out only the app Photos is still working. So after importing 2700 pics (big trip and behind with backup), the question popped if I wanted to delete the fils on my phone and I said yes. I tried to re install Iphoto, but nothing there, but older pics. I tried the temporary files from the Mac, but nothing.
So now I got my hopes up for a data recovery software thing. But although Windows (Im working on another laptop) did install the drivers correctly and I see my phone in the folder structure, no data recovery software recognises my phone although I switched to MSC and USB-debugging. I think because I haven't rooted it i suppose. Well, that's what all the forum members say
So I think rooting is my only option left? I am wondering if it works for my goal to get my data back. I read that unlocking the boot loader means everything will be erased, so then there would be no point for me to do this. Is it possible to root it without losing my (deleted) data on the internal memory? I know it is being overwritten now as we speak, but I'm sure I can save a few photos!
thanks a million!
Click to expand...
Click to collapse
If you have successfully imported from the phone into iPhoto, then you simply need to import your iPhoto Library into Photos in Mac.
Check if you can find the iPhoto library by going to Finder -> Home -> Pictures
There should be 2 libraries there - one for iPhoto, and one for the newer Photos app that came along in April. Double-click the iPhoto library and wait for Photos to launch, then follow the instructions to import the library into Photos.
Make sure you have enough disk space (on the Mac) to do this. You'll need at least as much free space as the size of the iPhotos library to import it into Photos and possibly more.
Hello, all! Just joined up to post a few questions. Every Android phone I have owned has been rooted and a custom ROM installed, so I am no stranger to all this. I'm finally getting around to replacing my ancient Motorola Triumph (Virgin Mobile USA) and for cost reasons I am seriously considering the Desire 510. I'd love to get the Desire 816 but that's out of my current price range Anyway, I have been reading the posts here and over at Android Forums dot com and I am confident that I will have no problems with the 510 should that be the phone I end up purchasing. But I've got several questions before I make a final decision.
1. Can anyone tell me (or how can I find out) if the 510 from Virgin Mobile USA is the 32-bit or 64-bit phone? I wasn't able to find much information except something online (unrelated to Virgin Mobile) that says the U.S. version is 32-bit while all other countries get the 64-bit. Since that information is now several months old can anyone confirm that it still holds true, or is there a possibility that 64-bit devices are now available in the U.S.?
2. If the Virgin Mobile USA version is indeed 32-bit, is there anywhere I can get a 32-bit ClockworkMod recovery? I see a post here for a 64-bit CWM but couldn't find mention of 32-bit anywhere. Nothing against TWRP, just that I have been using CWM since Day 1 of rooting and that's what I'm comfortable with. Also, before flashing a new recovery, how do I go about making a backup of the stock recovery.img? I imagine there's a way to rename it (i.e. recovery-stock.img) or copy it to my PC for safekeeping, but I'm not very familiar with Android SDK. (My current phone does not need SDK for anything. Simply plug in, copy new recovery where it needs to be, and reboot.)
3. What, exactly, is the write protection that I have seen mentioned all over the place? Correct me if I'm wrong, but it *SOUNDS* like rooting and/or installing a custom recovery and/or installing a custom ROM essentially cuts off SD card access until a "fix" is applied. So if anyone can offer a simple explanation or a link to some information, that would be fantastic.
4. Taking #4 into mind, what do I need to consider in choosing a kernel? If it matters, I have been looking mainly at CurbThePain's RevMod, but also LarryBoyG's RaptorRom GPE v2 and shinru2004's Unofficial CM11.
I know that's a lot of questions all in one place but I figured I'd start somewhere. Any and all answers are appreciated, and any questions for me will be answered in as timely a manner as I can. Thanks in advance for any info you guys are able to provide me.
EDIT:
5. Supposedly this phone has 8GB of internal memory but all the screenshots I see say it has 4GB, and most of that is taken up by the operating system. I was just reading the reviews on virginmobileusa.com and almost every single one of them is negative, focusing on the fact that nobody can download more than a few apps before the phone runs out of memory. What's the official internal storage for OS and apps, 4GB or 8GB, and how does the memory look after a custom ROM is installed?
Some answers before you purchase
GKNByNW said:
Hello, all! Just joined up to post a few questions. Every Android phone I have owned has been rooted and a custom ROM installed, so I am no stranger to all this. I'm finally getting around to replacing my ancient Motorola Triumph (Virgin Mobile USA) and for cost reasons I am seriously considering the Desire 510. I'd love to get the Desire 816 but that's out of my current price range Anyway, I have been reading the posts here and over at Android Forums dot com and I am confident that I will have no problems with the 510 should that be the phone I end up purchasing. But I've got several questions before I make a final decision.
1. Can anyone tell me (or how can I find out) if the 510 from Virgin Mobile USA is the 32-bit or 64-bit phone? I wasn't able to find much information except something online (unrelated to Virgin Mobile) that says the U.S. version is 32-bit while all other countries get the 64-bit. Since that information is now several months old can anyone confirm that it still holds true, or is there a possibility that 64-bit devices are now available in the U.S.?
2. If the Virgin Mobile USA version is indeed 32-bit, is there anywhere I can get a 32-bit ClockworkMod recovery? I see a post here for a 64-bit CWM but couldn't find mention of 32-bit anywhere. Nothing against TWRP, just that I have been using CWM since Day 1 of rooting and that's what I'm comfortable with. Also, before flashing a new recovery, how do I go about making a backup of the stock recovery.img? I imagine there's a way to rename it (i.e. recovery-stock.img) or copy it to my PC for safekeeping, but I'm not very familiar with Android SDK. (My current phone does not need SDK for anything. Simply plug in, copy new recovery where it needs to be, and reboot.)
3. What, exactly, is the write protection that I have seen mentioned all over the place? Correct me if I'm wrong, but it *SOUNDS* like rooting and/or installing a custom recovery and/or installing a custom ROM essentially cuts off SD card access until a "fix" is applied. So if anyone can offer a simple explanation or a link to some information, that would be fantastic.
4. Taking #4 into mind, what do I need to consider in choosing a kernel? If it matters, I have been looking mainly at CurbThePain's RevMod, but also LarryBoyG's RaptorRom GPE v2 and shinru2004's Unofficial CM11.
I know that's a lot of questions all in one place but I figured I'd start somewhere. Any and all answers are appreciated, and any questions for me will be answered in as timely a manner as I can. Thanks in advance for any info you guys are able to provide me.
EDIT:
5. Supposedly this phone has 8GB of internal memory but all the screenshots I see say it has 4GB, and most of that is taken up by the operating system. I was just reading the reviews on virginmobileusa.com and almost every single one of them is negative, focusing on the fact that nobody can download more than a few apps before the phone runs out of memory. What's the official internal storage for OS and apps, 4GB or 8GB, and how does the memory look after a custom ROM is installed?
Click to expand...
Click to collapse
Hello GKNByNW,
1. Only one person on here said they have a 64-bit model that they bought in the U.S. from Cricket. You can probably ask the salesperson when you purchase it, but I think it's highly likely that the device you are going to buy will be 32-bit.
2. I don't know of a CWM for the 32-bit model. I was the same way. CWM was the only recovery I was used to. The first time I used TWRP was with this phone. I think you should try TWRP. I like it a lot. I have never used CWM Touch, but I'm sure TWRP may be like that. It is very user friendly. I don't know how you would go about making a backup of your stock recovery, but you should be able to use this one. It works great for my Boost phone. You may need to get familiar with adb and fastboot if you are not already. I don't know if we can just copy the recovery to where it needs to be, but most of us have been fastboot flashing it.
3. Write protection was included with Android KitKat. It has nothing to do with modding the phone. Google restricted some access to the sdcard, I believe for security reasons. When you flash a write-protect removed kernel, you can delete system apps, make changes to build.prop and make other changes. If you do not have a write-protect removed kernel, you can delete system apps, but when you restart the phone, they will return. You can also make changes to build.prop but when you restart they will not stick. I'm not sure of all of the things that will not stick if you have the stock kernel but those are a couple. Here is some more information: http://www.androidcentral.com/kitkat-sdcard-changes and https://source.android.com/devices/storage/index.html.
4. There are currently 2 kernels that most people use: Modded Desire 510 Kernel v2.6.1, which is tuned more for stability and Rhinstone-kernel, which is tuned more for performance. I haven't tried RevKernel and it hasn't been updated in a while, but you can check it out. Definitely check out the ROMs we have available and read through some threads to see which you like best.
5. The phone has 8GB internal, but we can only use ~1GB in the /data partition. I guess ~5GB is used for Android and Sense, since ~2GB is used for the /system partition. Check out this Storage Truth: https://goo.gl/photos/tCD1P26QTXM7my2r7
It's kind of weird, but this is the Storage Truth from my wife's phone, which has never been modded, and she has Cricket:
https://goo.gl/photos/uijoVA8Bk8tCtwe3A
She can still only use ~1GB, but I wonder why it shows ~4GB for the /data partition and only ~1GB for me.
After app updates and after you download a couple of apps the storage gets full, quick. The custom ROMS free up a lot of space. On a Jelly Bean based phone I had, without the sdcard restriction, I was able to integrate pretty much all of my apps on /system and have tons of room left over in /data. So I had so much space for apps and that phone didn't have as much "space" as this one has. On this one we're not so lucky. If you integrate the Google Play Store, Google Play Services, and the Gallery you will get force closes. There are more apps that will cause force closes if you integrate and delete them, but those are the main ones. You can delete the lockscreen with no issues, if you prefer the AOSP one. You can use Aparted and Link2SD to free up space. This method will allow you to download apps to your heart's content. Check out this thread to find out how to do that.
honestly,id skip the 510 and go for the 816 any day of the week. even if its more expensive,if i would have checked this thing out before i bought it after breaking my moto g,i would have bought a new moto (cricket dosent carry the 816)
blaqueknight said:
Hello GKNByNW,
1. Only one person on here said they have a 64-bit model that they bought in the U.S. from Cricket. You can probably ask the salesperson when you purchase it, but I think it's highly likely that the device you are going to buy will be 32-bit.
2. I don't know of a CWM for the 32-bit model. I was the same way. CWM was the only recovery I was used to. The first time I used TWRP was with this phone. I think you should try TWRP. I like it a lot. I have never used CWM Touch, but I'm sure TWRP may be like that. It is very user friendly. I don't know how you would go about making a backup of your stock recovery, but you should be able to use this one. It works great for my Boost phone. You may need to get familiar with adb and fastboot if you are not already. I don't know if we can just copy the recovery to where it needs to be, but most of us have been fastboot flashing it.
3. Write protection was included with Android KitKat. It has nothing to do with modding the phone. Google restricted some access to the sdcard, I believe for security reasons. When you flash a write-protect removed kernel, you can delete system apps, make changes to build.prop and make other changes. If you do not have a write-protect removed kernel, you can delete system apps, but when you restart the phone, they will return. You can also make changes to build.prop but when you restart they will not stick. I'm not sure of all of the things that will not stick if you have the stock kernel but those are a couple. Here is some more information: http://www.androidcentral.com/kitkat-sdcard-changes and https://source.android.com/devices/storage/index.html.
4. There are currently 2 kernels that most people use: Modded Desire 510 Kernel v2.6.1, which is tuned more for stability and Rhinstone-kernel, which is tuned more for performance. I haven't tried RevKernel and it hasn't been updated in a while, but you can check it out. Definitely check out the ROMs we have available and read through some threads to see which you like best.
5. The phone has 8GB internal, but we can only use ~1GB in the /data partition. I guess ~5GB is used for Android and Sense, since ~2GB is used for the /system partition. Check out this Storage Truth: https://goo.gl/photos/tCD1P26QTXM7my2r7
It's kind of weird, but this is the Storage Truth from my wife's phone, which has never been modded, and she has Cricket:
https://goo.gl/photos/uijoVA8Bk8tCtwe3A
She can still only use ~1GB, but I wonder why it shows ~4GB for the /data partition and only ~1GB for me.
After app updates and after you download a couple of apps the storage gets full, quick. The custom ROMS free up a lot of space. On a Jelly Bean based phone I had, without the sdcard restriction, I was able to integrate pretty much all of my apps on /system and have tons of room left over in /data. So I had so much space for apps and that phone didn't have as much "space" as this one has. On this one we're not so lucky. If you integrate the Google Play Store, Google Play Services, and the Gallery you will get force closes. There are more apps that will cause force closes if you integrate and delete them, but those are the main ones. You can delete the lockscreen with no issues, if you prefer the AOSP one. You can use Aparted and Link2SD to free up space. This method will allow you to download apps to your heart's content. Check out this thread to find out how to do that.
Click to expand...
Click to collapse
pattyboi:) said:
honestly,id skip the 510 and go for the 816 any day of the week. even if its more expensive,if i would have checked this thing out before i bought it after breaking my moto g,i would have bought a new moto (cricket dosent carry the 816)
Click to expand...
Click to collapse
Thanks for the replies, guys. I'm sorry for taking so long to get back and respond. Anyway... Yes, pattyboi, I am in total agreement. After reading reviews on Virgin Mobile USA's website and Amazon, I am definitely NOT going for this phone. Virgin no longer carries the 816 though it is still available new through retailers on Amazon, but the $180 price tag is a bit more than I want to spend on a phone right now. The other phone I had considered was the Samsung Galaxy Core Prime but it looks like that is only available for their Data Done Right plans, unless I am misunderstanding something. I don't really get what the whole Data Done Right thing is. It looks to be cheaper than my current plan ($45/mo. for unlimited talk/talk/1GB data) but I think Data Done Right is only for multiple lines. Also, I looked up the Galaxy Core Prime a couple weeks ago and it doesn't look like there's much information yet in regards to rooting and custom ROMs for that particular phone, so I might want to wait a while.