Related
Hello.
I recently got a droid 2--LOVE IT! Coming from several crackberries for years. This makes the bb look like a kids toy!
I have achieved root thanks to the fins instructions posted here--phone works like a charm.
I am curious if I can run the current cyanogen on my droid 2? I have searched around the net, and have seen that yes, you can, as the ROM is not hardware specific, and also, No, not yet.
I am running 2.2 froyo.
Hope this isnt too n00b.
Thanks for any help/input/guidance you may provide.
Cheers!
Far as I'm aware, it's not possible yet as Cyanogen is an entirely new kernel which requires being able to write to the bootloader which is not possible on both Droid 2 & Droid X yet.
the bootstrap just came out several days ago so roms and themes should be out within the next week or two
but yes anything with a modified kernal is not going to work as the bootloader will reject it
Note: I'm hoping this is the correct place for this thread, hopefully others with this same phone would benefit from it, as this sub-forum seems barren of any guides on what I am looking for
After Christmas, I decided to get my first smart phone, the D2G. I ordered it through Newegg and had it linked to a family account on Verizon.
So what I currently have now is Android 2.2, System Version 2.4.330.A956.Verizon.en.us, and tons of Verizon branded bloat.
My goal is that I would like to install a vanilla version of gingerbread. Being my first smartphone, and my first time on these forums, I'm greatly lacking in knowledge of these phones and how to get from where I am at to where I want to be. What I do have, however, is an understanding of operating system architecture, UNIX experience and good technical knowledge of PCs. I understand what rooting means, what apps are, what a bootstrap does, however I know nothing of how to get or use these things on this phone, nor any idea where to look for this information. Because this phone is on contract (and thus only paid $150 for it), I'm hoping to minimize the risk of bricking it, or otherwise costing me more money.
What I am looking for: any information/guides/links that will help me to get me from Android 2.2 to a vanilla version of gingerbread on the D2G. From what I have gathered from other threads is that I need to root it (by installing z4root I read), boot in recovery mode, then install ROMs. None of those things I know how to do right now. I suppose helping me learn how to do those would be a great start.
tl;dr I need a layman's guide to get gingerbread on D2G
Thanks in advance for any help
To begin you won't be able to get Gingerbread until Motorola releases an update. The Droid 2 (and D2 Global) have a locked bootloader which means the kernel can't be changed except by Motorola. Without a kernel upgrade Gingerbread will remain out of reach.
You can, however, grab some things that have been backported from Gingerbread like the keyboard and theme. As time goes by more and more external things from Gingerbread will become available for non-GB users, but certain things that rely on the GB kernel will be elusive.
Now as for FroYo, there currently isn't a completely working AOSP (Android Open Source Project) ROM yet. Fission and GummyJAR strip away as much Blur as possible and work towards AOSP. Unleashed, Ultimate Droid, and Tanzanite are all AOSP ROMs in development but are lacking full functionality at the moment. Basically you've got to pick your poison: AOSP-like that works or AOSP that's not quite done.
Given that you have a D2 Global I'd personally hold off on changing ROMs at the moment. The D2G SBF (System Boot File) hasn't been leaked yet so if anything were to go wrong while changing ROMs your phone would be bricked until the SBF is released. A SBF allows you to revert your phone back to its out-of-the-box state should anything go wrong; your phone can be in a boot loop but you can turn it on in a way that will allow you to get things back to square one at least. Without the SBF you're really taking a gamble.
Alright, so I take it I just got too new of a phone then ~_~
thanks
Don't be too upset that your phone is too new yet...
Just be very careful with what you try for now.
It is just over a year since I got my first Droid and while there were plenty of hacks and roms for that back then, few were really STABLE. It didn't take long before not only were stable roms available, they were far better and included features that were not supposed to be on the phone.
Including overclocking it to twice the stock speed.
The D2G is in a similar place right now but the whole "eFuse" thing makes hacking a lot trickier. Its much easier to brick a D2/DX than an original Droid.
BUt progress is being made and there is little doubt in my mind that all the devs out there will make this phone what it should be just like they did with the Droid.
Gingerbread will get to us eventually, but for now Fission rom has already improved my D2G 100% over stock.
rogerdugans said:
Gingerbread will get to us eventually, but for now Fission rom has already improved my D2G 100% over stock.
Click to expand...
Click to collapse
Interested in Fission, but as I have previously stated, I'm quite clueless for the time being
Is this something that is safe?
Kenshin- said:
Interested in Fission, but as I have previously stated, I'm quite clueless for the time being
Is this something that is safe?
Click to expand...
Click to collapse
If you want 100% safe- leave your phone exactly as you received it.
Seriously.
There is risk in doing this stuff, even when we are simply taking advantage of the very risky work done by devs to figure out HOW to modify our phones.
Generally speaking, the longer you wait the less risky it is, but the fact is that there is never ZERO danger to it. Even if all the mods and hacks you use are time tested and there has not been a single bug found by anyone- flashing a rom can go wrong and leave a device bricked.
Even flashing a manufacturer provided BIOS on a computer has risk.
All of that said, if you want to minimize risk, wait just a little while for the bugs to be worked out more thoroughly.
I just saw that there is now an SBF for the D2G last night- that helps provide a buffer for accidents (disaster recovery!) but I don't know how well tested it is. We should know fairly soon- quite a few folks with bricked phones have been waiting for it!
I would say that right now the D2G has risk in the "moderate" range- new phone, not that much dev time, etc.
The only other phone I have personal experience with is the original Droid- risk on that is "minimal." Hard to kill those things.
All that said, I have accepted the risk and did so before the sbf was out. I have had no problems at all so far.
IF you choose to do so, I highly recommend following instructions exactly and making sure you know what you are doing and why.
I don't mean to talk you or anyone else out of improving their smart phone, but I do believe that realistic risk assessment is a wise thing to do before starting.
I used the SBF to flash my phone 2 days ago, with no issues.
rogerdugans said:
Generally speaking, the longer you wait the less risky it is, but the fact is that there is never ZERO danger to it.
...
All of that said, if you want to minimize risk, wait just a little while for the bugs to be worked out more thoroughly.
Click to expand...
Click to collapse
I have a D2 and I got it pretty new a few months ago it was my first Android phone but I watched the forums and learned as things became available how to do it all. I watched as the device everyone thought wasn't even going to get root access got it, then the ROMs came; it wasn't easy and they aren't like the ROMs that came for previous devices because of the locks Moto put on the phone. But, we were happy with it and I've been pleasantly surprised at what the devs have come up with and have been running custom ROMs so long I don't remember what stock was even like. I just know it wasn't as cool as the custom stuff I'm running.
So hang in there and read all you can about your device or similar devices (D2, DX, DPro) so that when something comes along that you want to try you know what to do to make it work and what to do if it doesn't go as planned.
I went from a Motorola Milestone to a Droid 2 Global. And as much as I am enjoying the Fission ROM from Team DeFuse, I am wondering why there seems to be such low interest in the Droid 2 Global compared to the original Droid 2? Can anyone give me some info as to why this is the case? I realize that with the Droid 2 globals additional radios that that transcribes to more work to get those operational in a custom ROM, I just dont understand why this powerful phone is ignored and left to sit on the curb. Thank you to all in advance.
1. The Global is hard to dev for. There aren't many Global devices to go off of, so the radios are hard to get 100% working on custom roms
2. It was launched silently. No one really knows it exists, so it just didn't receive the initial dev bump that phones usually get when they're first released
3. It didn't sell very well. I can't speak for the whole sales numbers, but my friend who works for Verizon Corporate (or something like that) said the numbers weren't fantastic in New York.
4. Three devices is a lot. Any devs willing to work on the Global probably already work on the Droid X and Droid 2. Adding a third device to the list is just too much for people who do this as a hobby.
That's the best explanation I can give... sorry for how negative it was, lol.
To be fair, the D2G is receiving more support this last month or so. Look on droidforums.net, some good work being done on there (3 or 4 roms available).
I will keep an eye out on droidforums. I was also thinking that with the possibility of 2.3 coming out for it most devs dont (myself included) see a point in making a ROM on froyo when 2.3 is around the corner. Thank you for your input. Its much appreciated
Most of the correct answers were already stated...
Just wated to point out that only people who truly needed global support would buy the D2G.
Droid Pro got play merely because it was targeted at the Crackberry crowd conversion which really didn't work.
Those are the only two GLOBAL phone I know of. Doesn't make sense to make many more with the 4G revolution under way.
Business have bought into the form factor but the Devs they all look at the performance specs and the EASE of development regarding the model.
The biggest issue though is the locked bootloader! Since the boot loader is locked you can not run custom Kernels so any development that could be made is limited to the stock kernel.
All of the Motorola development you see regarding phone with lockd bootloaders are really nothing more than a bunch of stock and AOSP apps and system files that change the look and the startup sequence but the base code that runs the phone pretty much stays the same!
I would love to see more people making ROMs for the unit but what I really want to see is the unlocking of that boot loader.
If we managed to do that then none of us would be worrying how many roms were available or which one updates next.
We would probably all be running Cyanogen at this point and merely wait for the next release of stable! And also be looking for the next great Kernel update to make it even better!
Asphyx said:
Most of the correct answers were already stated...
Just wated to point out that only people who truly needed global support would buy the D2G.
Droid Pro got play merely because it was targeted at the Crackberry crowd conversion which really didn't work.
Those are the only two GLOBAL phone I know of. Doesn't make sense to make many more with the 4G revolution under way.
Business have bought into the form factor but the Devs they all look at the performance specs and the EASE of development regarding the model.
The biggest issue though is the locked bootloader! Since the boot loader is locked you can not run custom Kernels so any development that could be made is limited to the stock kernel.
All of the Motorola development you see regarding phone with lockd bootloaders are really nothing more than a bunch of stock and AOSP apps and system files that change the look and the startup sequence but the base code that runs the phone pretty much stays the same!
I would love to see more people making ROMs for the unit but what I really want to see is the unlocking of that boot loader.
If we managed to do that then none of us would be worrying how many roms were available or which one updates next.
We would probably all be running Cyanogen at this point and merely wait for the next release of stable! And also be looking for the next great Kernel update to make it even better!
Click to expand...
Click to collapse
Won't anyone who wants a keyboard on verizon also get the D2G? I mean it's the only half decent phone with a physical qwerty keyboard on verizon, and the droid 2 itself was phased out months ago, 4 months ago when I got my D2G you couldn't get a new Droid 2 at verizon, though I think Best Buy might have still had them, though they were just clearing out stock.
Also I thought fact that everything has to be signed is the problem with the phone. When you don't know how to sign the kernel and other things the phone has hardware to autobrick which is why no one can get around it. Tons of phones out there have locked bootloaders that are gotten around well before or within a few days of the phone being released. If it was just the locked bootloader then I'd say motorola has found the holy grail of security, because everything else out there has been hacked through.
The problem isn't that the bootloader is signed, its that its encrypted. Newer htc phones have bootloaders that require signed kernels and people have found ways around them already, the encryption prevents us from loading custom software on it.
Sent from my DROID2 GLOBAL using XDA App
maybe....
http://au.ibtimes.com/articles/5034...veals-android-4-kitkat-os-11.htm#.UicpuH-I68A
here's a quote from the article:
Android 4.4 KitKat Features
Google hasn't revealed any features yet of the upcoming Android 4.4 KitKat but instead, the company said: "our goal with Android KitKat to make an amazing Android experience available for everybody."
With this statement from Google, it is expected that KitKat will become accessible to Android-running devices with lower RAM such as 512MB and older Android version such as 2.3 Gingerbread. This optimisation has been rumoured to be included in Android 5.0 Key Lime Pie.
Click to expand...
Click to collapse
What...
http://signatures.mobile-overload.com/wp-content/uploads/2013/07/sig-cm-5.png
I would not hold my breath.
Sent from my SCH-I545 using XDA Premium HD app
lol no. Unless if it was created by an awesome person here, but there's no point in that. This phone is long dead, earlier this week I finally moved on, and oh my gosh, its been great having a Nexus 4 over this phone that was out-dated before it was even released back in Spring 2011.
Nope
You'll probably never see a KitKat version on the Charge. The main reason is the same that you never saw ICS or JB on the Charge. The code for the radios was never released. I've tried JB on the Charge, it runs well; however the camera and data don't work. Also, while I still use the Charge as my primary phone, there's not many of us left.
ICS and all versions of JB work fine on this phone already... we are just missing the radios.
I doubt anyone cares about this phone anymore anyways...
10amla said:
You'll probably never see a KitKat version on the Charge. The main reason is the same that you never saw ICS or JB on the Charge. The code for the radios was never released. I've tried JB on the Charge, it runs well; however the camera and data don't work. Also, while I still use the Charge as my primary phone, there's not many of us left.
Click to expand...
Click to collapse
I'm inclined to agree, though it would be awesome to be proven wrong!
JihadSquad said:
ICS and all versions of JB work fine on this phone already... we are just missing the radios.
I doubt anyone cares about this phone anymore anyways...
Click to expand...
Click to collapse
Yeah not many folks left that's for sure... still a few that care though
dwitherell said:
I'm inclined to agree, though it would be awesome to be proven wrong!
Yeah not many folks left that's for sure... still a few that care though
Click to expand...
Click to collapse
I agree with both assessments. Thanks for all the work you've done on Tweaked, Dwith. My wife and I love it on our charges.
P.S. One problem I had with Tweaked Lite, when I installed it, it didn't install file manager(I think that's what it's called on stock) and when I went to select a sound(not ringtone) for a ringtone it would show and error. I went to tweaktools and installed the file manager and it works fine. Not sure why it wouldn't work with my other file management programs.
10amla said:
I agree with both assessments. Thanks for all the work you've done on Tweaked, Dwith. My wife and I love it on our charges.
P.S. One problem I had with Tweaked Lite, when I installed it, it didn't install file manager(I think that's what it's called on stock) and when I went to select a sound(not ringtone) for a ringtone it would show and error. I went to tweaktools and installed the file manager and it works fine. Not sure why it wouldn't work with my other file management programs.
Click to expand...
Click to collapse
Yeah I am not a fan of MyFiles, and for better or worse the call to that for ringtone selecting is hardcoded... at least tweaktools brings it back quick enough - forgot about that tbh, sorry for the troubles!
dwitherell said:
Yeah I am not a fan of MyFiles, and for better or worse the call to that for ringtone selecting is hardcoded... at least tweaktools brings it back quick enough - forgot about that tbh, sorry for the troubles!
Click to expand...
Click to collapse
I agree with your take on MyFiles, one of the first thing I did was replace it with something else(currently FX File Manager). I wasn't a big deal, I had planed on copying my few ringtones to system anyway.
while I agree that the we are more likely to see Republicans and Democrats agree on something, would still be interesting to see if this holds true. I really would not be surprised though, if older devices do get upgraded to the latest OS - that could mean larger revenues for Google. more folks would be able to use their apps, services, etc. without having to get a new device.
however, after then, they could see how slow their device is, and then they decide to upgrade. but still, worth keeping an eye on.
Google and Verizon both agreeing to do this? Hell will freeze over first.
Sent from my SCH-I510 using xda app-developers app
From my understanding of several stories posted from Android sites since KitKat was announced, It sounds like either Google is going to update phones to KitKat silently like they have been doing everything else without the help of Samsung or Verizon or perhaps we just get these features without ever actually upgrading to KitKat
Hangouts is supposed to be replacing the stock Messaging app-If Google can do that then why would they need anything from Samsung/Verizon??
http://www.androidpolice.com/2013/1...msmms-integration-video-sharing-capabilities/
http://mobilesyrup.com/2013/10/08/h...uts-will-almost-certainly-integrate-with-sms/
4.4 "Google Experience" Launcher Launcher could be released from the Play Store (which would replace touchwiz??)
http://www.androidpolice.com/2013/1...re-some-things-we-are-expecting-to-see-in-it/
The truth of the matter is this. The Motorola Droid 1, a phone I bought as a media/mp3 player for 50 bucks and fixed up, is working better than a phone I paid 300 new and had nightlies and better support. I loved my charge, the battery sucked. And the phone I use now is the Verizon note 2 and sprint note 3 as a business phone since I now work for the sprint corporation. Do I miss my charge? Yes. Do I wish it had some cyanogenmod support being a phone 1 1/2 years newer than the droid 1? yes. As soon as I can learn how to make a rom for the charge, I plan to make an ics or jb nightly that will support a wifi only support on this relic. It was my first 4g phone. I have it in my desk and feel sad since it helped me achieve so much.
asacado said:
The truth of the matter is this. The Motorola Droid 1, a phone I bought as a media/mp3 player for 50 bucks and fixed up, is working better than a phone I paid 300 new and had nightlies and better support. I loved my charge, the battery sucked. And the phone I use now is the Verizon note 2 and sprint note 3 as a business phone since I now work for the sprint corporation. Do I miss my charge? Yes. Do I wish it had some cyanogenmod support being a phone 1 1/2 years newer than the droid 1? yes. As soon as I can learn how to make a rom for the charge, I plan to make an ics or jb nightly that will support a wifi only support on this relic. It was my first 4g phone. I have it in my desk and feel sad since it helped me achieve so much.
Click to expand...
Click to collapse
That's exactly what I was thinking - even if the radios weren't released, having the phone to use over wifi would be good enough for me. I guess that's the question - would it be possible to work up a kitkat ROM that was just purely wifi?
zereoue said:
That's exactly what I was thinking - even if the radios weren't released, having the phone to use over wifi would be good enough for me. I guess that's the question - would it be possible to work up a kitkat ROM that was just purely wifi?
Click to expand...
Click to collapse
I've seen an ics rom that was floating around, but support for this phone was always limited. It came and went faster than any other phone I saw. Hell, the bionic I owned had support and nightlies all the way up to the day I got the note 2. I digress. I am looking into it as soon as I can get a linux kitchen set up.
asacado said:
I've seen an ics rom that was floating around, but support for this phone was always limited. It came and went faster than any other phone I saw. Hell, the bionic I owned had support and nightlies all the way up to the day I got the note 2. I digress. I am looking into it as soon as I can get a linux kitchen set up.
Click to expand...
Click to collapse
I am learning how to build for android. Starting with the fascinate since there is a lot of support so I can gain familiarity and then I'm going to do a build for the charge. I intend to only use it as a media device. I can't promise or guarantee anything but, I will try my best to deliver a bootable kitkat rom. This is all pretty difficult. We shall see what happens.
pyroman512 said:
I am learning how to build for android. Starting with the fascinate since there is a lot of support so I can gain familiarity and then I'm going to do a build for the charge. I intend to only use it as a media device. I can't promise or guarantee anything but, I will try my best to deliver a bootable kitkat rom. This is all pretty difficult. We shall see what happens.
Click to expand...
Click to collapse
I have a Fascinate as well, but haven't installed any of the KK offerings for it yet. I did notice that when updating the Fascinate to KK you have to flash a 4.1 or 4.2 rom first, to get the file system setup, right? Then flash the 4.4 rom. Would the steps be the same for the Charge?
zereoue said:
I have a Fascinate as well, but haven't installed any of the KK offerings for it yet. I did notice that when updating the Fascinate to KK you have to flash a 4.1 or 4.2 rom first, to get the file system setup, right? Then flash the 4.4 rom. Would the steps be the same for the Charge?
Click to expand...
Click to collapse
AFAIK you shouldn't have to flash any rom first.. I could be wrong. I don't keep up with all the fascinate development. I did flash a 4.4 rom in the past from cm10.1.
I have a build enviroment set up and I am running into problems building cm11 for the fascinate. I think by the errors that I need to increase the system partition. Because the build always fails at making the system.img. The build guides make it seem like you should run into no errors at all.
I'll start building for the charge soon. I'm too much of a noob to actually develop for it right now, but I think I can atleast boot it once I figure out how to build it.
pyroman512 said:
AFAIK you shouldn't have to flash any rom first.. I could be wrong. I don't keep up with all the fascinate development. I did flash a 4.4 rom in the past from cm10.1.
I have a build enviroment set up and I am running into problems building cm11 for the fascinate. I think by the errors that I need to increase the system partition. Because the build always fails at making the system.img. The build guides make it seem like you should run into no errors at all.
I'll start building for the charge soon. I'm too much of a noob to actually develop for it right now, but I think I can atleast boot it once I figure out how to build it.
Click to expand...
Click to collapse
not sure if I mentioned this earlier, but it could be the fact that the charge is based on RFS system (GB 2.3). I believe android went EXT4 with ICS and higher. there are some kernels that can convert the Charge to EXT4 - so not sure if that would help ya.
I have a Samsung Infuse SGH-I997 that I rooted and installed Zeus Build 6 version 2.0. I believe it was the last supported version of Zeus. Anyway, that was back in 2011 and I can't even begin to remember how I even started to get the thing rooted let alone successfully install a custom rom. I'm not asking anyone to tell me how to do it, but I am asking for suggestions on which rom to upgrade to. I'm trying to get some apps that are telling me I need a minimum of android 4.0 and I'm not sure if the custom rom version coincides with the android version. This phone has been pretty reliable over the years. I'm wondering if it is worth the trouble to update the rom or go out and get an updated phone. I don't feel like spending 500 bucks on a new phone. It's not that much of a necessity for me to justify that. So any suggestions are appreciated.
jdjeff said:
I have a Samsung Infuse SGH-I997 that I rooted and installed Zeus Build 6 version 2.0. I believe it was the last supported version of Zeus. Anyway, that was back in 2011 and I can't even begin to remember how I even started to get the thing rooted let alone successfully install a custom rom. I'm not asking anyone to tell me how to do it, but I am asking for suggestions on which rom to upgrade to. I'm trying to get some apps that are telling me I need a minimum of android 4.0 and I'm not sure if the custom rom version coincides with the android version. This phone has been pretty reliable over the years. I'm wondering if it is worth the trouble to update the rom or go out and get an updated phone. I don't feel like spending 500 bucks on a new phone. It's not that much of a necessity for me to justify that. So any suggestions are appreciated.
Click to expand...
Click to collapse
Hi,
There is a process littered in the development threads (flash CWM if not already, turn off voodoo lagfix and flash the desired ROM -or- with CWM, flash ICS (CM9), then CM10.1, then (if you want), a Kitkat ROM.
Sadly if you have the AT&T version (vs Rogers i997R) and still on 2.x, you will need to patch your bootloader as well. That requires a download noone can find anymore. The effect without the patch starts with a garbled CWM.
So you can try the above, my guess is that you will probably just be flashing back to stock/Zeus (so have all fallbacks ready).
Would have been much-easier/possible 2 years ago before the mirrors shut down (I rescued some stuff, just not the bootloader patch). Ah well, hope this helps nonetheless.
My version is the ATT version. So you are saying even if I wanted to just flash to a new rom from Zeus, I need some unavailable files to do so? Is it possible I have the files from the Zues flash? Or are you saying the newer roms require at least an updated version of those files?...especially if it's the ATT version. Maybe it's time for another phone....I guess.
jdjeff said:
My version is the ATT version. So you are saying even if I wanted to just flash to a new rom from Zeus, I need some unavailable files to do so? Is it possible I have the files from the Zues flash? Or are you saying the newer roms require at least an updated version of those files?...especially if it's the ATT version. Maybe it's time for another phone....I guess.
Click to expand...
Click to collapse
Breaking the Gingerbread barrier requires an updated bootloader (which cannot be found these days), or else this happens.
You may be patched already. Only one way to find out. Just be sure to have Odin back-to-stock files ready (check out my sig link, follow "something"...I have a mirror thread with a few things) if your CWM goes sideways.
Rogers version (the one I had) seems unaffected maybe because it had the updated BL from the start maybe (as Rogers version always had Gingerbread where AT&T started with Froyo)? Too bad they are not interchangeable (from what I can tell).
Fighting with older phones is only fun up to a point (and this one turns five this year). I moved on a couple times (mind you my Infuse was never really a daily driver, rather relegated to a media player even back when I used a slider feature phone as my DD), my latest phone being the ASUS Zenfone 2. $500 price tag for a new phone (as you mentioned earlier) isn't all that fair (unless you are looking for a big name), as I got my current for half that (CDN) + tax & shipping. Based on that, and with the (USA <> CDN) exchange rate these days, you can probably find the ZF2 Laser (which comes with a removable battery and MicroSD slot) for around $200. Food for thought.
OfficerJimLahey said:
Breaking the Gingerbread barrier requires an updated bootloader (which cannot be found these days), or else this happens.
You may be patched already. Only one way to find out. Just be sure to have Odin back-to-stock files ready (check out my sig link, follow "something"...I have a mirror thread with a few things) if your CWM goes sideways.
Rogers version (the one I had) seems unaffected maybe because it had the updated BL from the start maybe (as Rogers version always had Gingerbread where AT&T started with Froyo)? Too bad they are not interchangeable (from what I can tell).
Fighting with older phones is only fun up to a point (and this one turns five this year). I moved on a couple times (mind you my Infuse was never really a daily driver, rather relegated to a media player even back when I used a slider feature phone as my DD), my latest phone being the ASUS Zenfone 2. $500 price tag for a new phone (as you mentioned earlier) isn't all that fair (unless you are looking for a big name), as I got my current for half that (CDN) + tax & shipping. Based on that, and with the (USA <> CDN) exchange rate these days, you can probably find the ZF2 Laser (which comes with a removable battery and MicroSD slot) for around $200. Food for thought.
Click to expand...
Click to collapse
Ok...thanks for the additional insight. Looks like I have a decision to make.