The other day i found the Galaxy s and dont use android cause i have a HD2 but was wondering if there is a way to reflash the phone so everything gets deleted off it, was gonna possibly give it to my brother or sell. I know Verizon uses CDMA as a band but is there anyway to use it for tmobile? Dont think so but someone might know more. Thanks!
first thing, but this is not a dev question, please post in the correct section next time to keep the dev section uncluttered
secondly, there is no way to get a VZ phone to work on tmobile. Two completely different network technologies. The ESN on the phone you found is probably blocked anyways
"Found" phone?
Might want to call Verizon with the IMEI and they can probably return it to its owner. Or the registered Google email address. Or...
5 Finger discount.. maybe be a decent person and call one of the saved numbers in the phone and try to find the owner.
Try booting into recovery and wiping the phone.
sent using the WWW.psxforums.com app
heeey, thats my phone. i would like it back
Sent from beyond the Galaxy
Not to rain on anyone but this side of the world is for the Samsung Galaxy S 4G... Not the Galaxy S... 2 diff phones
BTW i would not want to loose my phone around that guy bet i would find it on ebay...
Sent from my SGH-T959V using XDA App
What does this have to do with development?
Thread closed
So, sprint just released an OTA update to 2.3.6 for the Samsung Replenish (SPH-M580). Thing is, for me (and others, I'm sure) the update somehow both automatically applied an obnoxious Sprint ID skin as well as crippled the Sprint ID service. This leaves users with an ungodly 2.2/2.3 hybrid which manages to look even worse than Froyo, and no Sprint-sanctioned method of fixing it.
So, rather than sit idly by and wait for Sprint to slowly/never patch this (neither Sprint nor Samsung had anyone who could help me), I've decided to root the device.
A few questions:
1. Here, someone achieved root back in mid-2011. Would that method be viable after the update to 2.3?
2. Would other exploits (i.e. gingerbreak via SuperOneClick) be viable with 2.3.6?
3. Is CWM or Cyanogen compatible with this handset? The whole reason I was looking forward to the update was certain UI features that I noticed on newer gingerbread devices like the SGS2 (power options on notification screen, paged applications drawer, zoom-out on home screen), and none of those are available thanks to Sprint.
Hopefully this gets more than 2 replies; sometimes it seems like nobody owns this phone on here.
Sent from my SPH-M580 using XDA App
Wow, just found another UI goof - in some apps (XDA included) the loading icon is a rotating circle, but it's in a non-square space, so it ends up looking like a goofy wobbling ellipse. Urgh.
Sent from my SPH-M580 using XDA App
Agh, can't anybody help with this?
I guess nobody anywhere ever had this device.
Can someone direct me to a forum where I might find help? :c
Sent from my SPH-M580 using XDA App
Im on the same boat as you, but my phone is on Boost. I've been looking for hours and can't find anything. I'll let you know if I find any leads.
Are you on Froyo? If so, I think someone posted a batch file a few months ago that would work.
Sent from my SPH-M580 using XDA App
Has anyone figured this out yet? Is there a comparable root for another Samsung device that would work with the replenish? Seems like someone should have figured it out by now...
I have a rooted Replenish on 2.3
I have a rooted replenish on Phoenix 0.2 the Download and instructions are on android central just search replenish
forums.androidcentral.com/samsung-replenish/148702-acs-rom-phoenix-rom-0-2-a.html
It wont let me post the link because im new here
Odin may be only option right now
I have a coworker with a Replenish. Rooted it with KMS originally (was a PITA, but if you timed it right, it worked), since he updated it to gingerbread I have not found a working solution.
I downloaded the Phoenix 0.2 rom from above and will test it out when I see the phone again. I'm guessing from what I read in the comments relating to that ROM that it will work fine.
Note about flashing using ODIN: From what I know, ODIN is the tool samsung uses to push firmware to their phones. This will overwrite the boot loader and if something goes wrong during flashing you can brick your phone. Make sure you are using a good powered USB port on your computer with a good working USB cable for the phone (preferably the one that came with it that has the samsung sticker on it). I've bricked a phone before using a crappy USB port on my computer, so be careful :-/
your savior!!!!!!!!! lol XD
Jack Sawyer said:
Has anyone figured this out yet? Is there a comparable root for another Samsung device that would work with the replenish? Seems like someone should have figured it out by now...
Click to expand...
Click to collapse
_allen said:
Im on the same boat as you, but my phone is on Boost. I've been looking for hours and can't find anything. I'll let you know if I find any leads.
Click to expand...
Click to collapse
sirdangolot5 said:
Agh, can't anybody help with this?
Click to expand...
Click to collapse
sirdangolot5 said:
So, sprint just released an OTA update to 2.3.6 for the Samsung Replenish (SPH-M580). Thing is, for me (and others, I'm sure) the update somehow both automatically applied an obnoxious Sprint ID skin as well as crippled the Sprint ID service. This leaves users with an ungodly 2.2/2.3 hybrid which manages to look even worse than Froyo, and no Sprint-sanctioned method of fixing it.
So, rather than sit idly by and wait for Sprint to slowly/never patch this (neither Sprint nor Samsung had anyone who could help me), I've decided to root the device.
A few questions:
1. Here, someone achieved root back in mid-2011. Would that method be viable after the update to 2.3?
2. Would other exploits (i.e. gingerbreak via SuperOneClick) be viable with 2.3.6?
3. Is CWM or Cyanogen compatible with this handset? The whole reason I was looking forward to the update was certain UI features that I noticed on newer gingerbread devices like the SGS2 (power options on notification screen, paged applications drawer, zoom-out on home screen), and none of those are available thanks to Sprint.
Hopefully this gets more than 2 replies; sometimes it seems like nobody owns this phone on here.
Sent from my SPH-M580 using XDA App
Click to expand...
Click to collapse
help is here!:
http://forum.xda-developers.com/showthread.php?p=23577887#post23577887
follow the steps and please back it up. ive verified this many times today, but you never know what might happen...
Thanks! Unfortunately I sold my phone!! I wish I had this in January. lol
mirror
Can anybody mirror this my girlfriend has this phone and she hates not having enough spce for her apps so i wanna install a custom rom and enable sd-ext.
Need rooting for dummies
I need help. I have read, re-read and read again every and any instructions I have located for rooting a Boost Samsung Replenish and am still completely confused. I need step-by-step instructions from A to Z which most do not have and to complicate things more, instead of using Odin I am using Heimdall since Odin can not run on Mac. I have been unable to find any instructions on using Heimdall to root my phone. Please help. Phone information below
Boost Samsung Replenish
Model SPH-M580BST
Android Version 2.3.6
Band Version S:M580.06 x FB03
Kernel Version 2.6.35.7
Build Number GINGERBREAD.FB03
Hardware Version M580.06
Folks,
There's been no word, no dates given or leaked about the ICS update we're supposed to be receiving. Samsung has said we're supposed to get the update, but T-Mobile has been quiet. Hell, Samsung just announced that the GS2 will be getting JB and they've been working on it. I don't know how well that translates to the T-Mobile variant of the GS2, but it's still something. All we need is a kernel and some camera drivers. Hell, we could probably get away without the camera drivers and mangle the old ones using a compatibility HAL..
It is starting to feel like T-Mobile is simply going to forget the blaze. I mean, they released an update already, why would they hurry on to the next update...
I think if we're going to get something for nothing, we'll have to make noise about it. Same way we got this forum. I think it's going to take bugging t-mobile on the forums and on their support lines. You people on contract have it worse. You bought a really powerful phone in the presence of ICS, some of you after the promise that it would receive the update. T-Mobile wouldn't suffer penalties if they didn't push it, but I imagine they'll respond to some social pressure enough not to simply forget the update.
Hell, it'd be nice if we could even just get a date.
I agree with you. At this point I'd be happy with some sort of update from Samsung/T-Mobile. Even if they just said "we're still working on it" and gave no ETA at least we'd know they hadn't forgotten about it.
If the Blaze Q whatever the hell they've decided to call it launches here in a few weeks with ICS and we still don't get the software I will be ticked.
If push comes to shove and they don't release it can the devs port it or JB from another galaxy phone?
Correct me if I'm wrong but my understating is that it can but would take a lot of work and all are holding off since ICS is supposed to be dropping at anytime. No sense in going thru all that work only to have an official release dropped on us.
Sent from my Samsung Galaxy S Blaze.
Lol bugging xda mods for a forum is NOT the same a bugging T-Mobile for eta.
Sent from my SGH-T769 using xda app-developers app
dr4stic said:
Folks,
There's been no word, no dates given or leaked about the ICS update we're supposed to be receiving. Samsung has said we're supposed to get the update, but T-Mobile has been quiet. Hell, Samsung just announced that the GS2 will be getting JB and they've been working on it. I don't know how well that translates to the T-Mobile variant of the GS2, but it's still something. All we need is a kernel and some camera drivers. Hell, we could probably get away without the camera drivers and mangle the old ones using a compatibility HAL..
It is starting to feel like T-Mobile is simply going to forget the blaze. I mean, they released an update already, why would they hurry on to the next update...
I think if we're going to get something for nothing, we'll have to make noise about it. Same way we got this forum. I think it's going to take bugging t-mobile on the forums and on their support lines. You people on contract have it worse. You bought a really powerful phone in the presence of ICS, some of you after the promise that it would receive the update. T-Mobile wouldn't suffer penalties if they didn't push it, but I imagine they'll respond to some social pressure enough not to simply forget the update.
Hell, it'd be nice if we could even just get a date.
Click to expand...
Click to collapse
I completely agree with you. To be honest, I am already pissed off that they still havent released it. When I got this phone, T-Mobile promised I was going to get an ICS update in July. Yeah, so much for that. At the very least they could acknowledge our presence and let us know that they havent forgotten about us
Chitown021 said:
If push comes to shove and they don't release it can the devs port it or JB from another galaxy phone?
Correct me if I'm wrong but my understating is that it can but would take a lot of work and all are holding off since ICS is supposed to be dropping at anytime. No sense in going thru all that work only to have an official release dropped on us.
Click to expand...
Click to collapse
The problem is the kernel and libraries specific to our hardware. We have to have a working kernel and libraries before the rest of the rom can come.
I'm not sure why people thought the Blaze Q would've been a good thing for us because unless the hardware was identically similar (which no one had any proof that it was), the releases for that phone would've been useless for ours. The fact that it's now coming with a 720p display (I would've stayed with my Blaze 4G if it had that), and a keyboard tells me that there will be PLENTY different between the phones.
Hardware-wise, the T769 (Blaze) is EXTREMELY similar to the T989 (T-Mo SGS2). How similar you ask? In the original kernel configuration file for the T769, the options are set to build it as a T769 AND T989. There are a few ifdefs that exist purely to stop little snippets of the T989 code from taking effect.
I worked on my own time to try and hack together a kernel from the released sources for the T989 for ICS. Porting specific code from the T769 sources to try to come up with something that worked. Here's the problem: it was stressful and thankless, and at the end of it all I had a kernel that would compile and not boot. No one collected anything to help me attempt this and I was getting tired of having a non-functioning phone that pissed me off. So I ordered me a Galaxy Nexus. I received 2 in a row with screen issues and ended up returning them. I figured I would return to my efforts with the blaze, but at that point I was used to the big phone with a beautiful 720p resolution... so I shelled out the money for a GS3.
I have thought of returning and making a second attempt to port the kernel, and have actually started setting up to do just that. I think I made some mistakes my first time around, so the second time might actually work. But it is A PAIN.
chjema said:
Lol bugging xda mods for a forum is NOT the same a bugging T-Mobile for eta.
Click to expand...
Click to collapse
You're right, it isn't... but it's the last time I saw this community bug an outside source for something, aside from buying a couple of guys a phone
Yeah, a 720p screen would have been nice... thanks for the detailed explanation.
I still find it comical that my old HD2 is on the verge of having a fully functional JB rom but my brand new Blaze is still stuck on GB.
Honestly if I could've afforded it I would have probably gone the Nexus or S3 route but given my limited funds and needing to cover two phones (wife needed an upgrade) I thought this was the best value ($30 upgrade cost at Target).
Sent from my Samsung Galaxy S Blaze.
Yes lets please do this.
T-Mobile hasn't updated their page for a month now, and that was for the Gingerbread update they released when they could have been making headway on ICS. I can't find out how to submit any new pages, but I can see two requests for an update that were a couple months old (click on the link, then read on the right side in section "Incoming Links") source = http://support.t-mobile.com/docs/DOC-4182
I went to Samsung's page about ICS updates, and rated it "very dissatisfied," informing them they should have supplied target Year and Quarter (i.e. 2012 Q3) at the minimum, but preferably a specific month. source = http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00046726&fm_seq=49755
Let's continue to put pressure on these assholes, or they will sweep us under the bus while they pursue development of the Samsung Galaxy Supernova 4G Touchwiz Xtra 4.1.
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem. I have ICS on a tablet and like it, but I never felt like I needed to light the torches and march on the castle because I didn't have the latest **** on my phone.
And honestly, if a delay of an update for a great phone that works perfectly fine is what keeps you up at night, just wow...
If I am missing something critical here that I should know about (phone will explode without ICS ROM installed, I have a higher risk of cancer if I don't have ICS on phone, etc) please let me know immediately. I have poster boards, Sharpies, and a willingness to assemble if needed.
Dr4stic
If you need want help, testing, anything.let me know of beer more than happy to help.. we need to get ics to this phone
Sent from my SGH-T769 using xda app-developers app
heavenlydemonic said:
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem. I have ICS on a tablet and like it, but I never felt like I needed to light the torches and march on the castle because I didn't have the latest **** on my phone.
And honestly, if a delay of an update for a great phone that works perfectly fine is what keeps you up at night, just wow...
If I am missing something critical here that I should know about (phone will explode without ICS ROM installed, I have a higher risk of cancer if I don't have ICS on phone, etc) please let me know immediately. I have poster boards, Sharpies, and a willingness to assemble if needed.
Click to expand...
Click to collapse
Nope, just a league of people whining because that makes things happen faster. There really is nothing more to it.
I'll be the first to admit I've become a bit jaded because of my experiences with T-Mobile / Samsung and the Samsung Vibrant.
I heard promises about updates to that phone - they even set dates and pushed them back and back and back and finally... nothing.
If anything I think the release of the Blaze Q is a strike against us because our phones are now the "out dated" version of the Blaze and why put development hours into an "old" device.
I'm happy that I have a fully functional phone as it is now (the Vibrant never really had a fully working GPS). An update would be nice but I wouldn't lose any sleep over it because honestly, you may just be setting yourself up for a lot of sleepless nights.
Oh, and on the Vibrant Forum they started a twitter campaign #NeverAgain demanding the promised upgrade or they would never use T-mobile or Samsung again. No one listened.
I know this all sounds cynical but I've seen this show before.
Edit to add: If memory serves correctly this was also the case with the Behold on T-mobile.
Hey i know im new here, but i was wondering if you guys have only attempted to port ics roms from the SII? Ive tried to do the same and only recieved a glittery sparkly screen. I was wondering if anyone tried other devices with similar hardware like the HTC amaze 4g. I tried to port that one and actually got the boot animation to pop up. I havent tried to do any logcats or anything because i have been to busy and i need my phone for work, but if anyone else has tried to port from other devices i would like to know so i can know where to start if i do decide to try again.
L7ChrisL7 said:
Hey i know im new here, but i was wondering if you guys have only attempted to port ics roms from the SII? Ive tried to do the same and only recieved a glittery sparkly screen. I was wondering if anyone tried other devices with similar hardware like the HTC amaze 4g. I tried to port that one and actually got the boot animation to pop up. I havent tried to do any logcats or anything because i have been to busy and i need my phone for work, but if anyone else has tried to port from other devices i would like to know so i can know where to start if i do decide to try again.
Click to expand...
Click to collapse
The reason you get a glittery screen when coming from roms that are like the SGS2 is because they use different display panel hardware than we do. I'd be careful porting things from different manufacturers unless you really know what you're doing. You'd hate to go and format some partitions you can't get back
heavenlydemonic said:
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem.
Click to expand...
Click to collapse
What happens when more "cool new apps" are released to the market that require Android 4.0 API's or better? Chrome immediately comes to mind, and there are others with many more on the way. What happens 4 months from now when you are only 6 months into your 2 year contract and you're wondering why you can't realistically run things on your phone that has 1 gig of ram and a dual-core 1.5ghz cpu?
And honestly, btw... I had a myTouch 4G running CM7 that felt miles faster than my blaze. The samsung crapware is not only bloated, but breaks the system in a number of places. You can see this in the fact that you can't have a scrollable wallpaper, or that the system doesn't understand all the loop points in ringtones that work properly in other phones. I can't tell you how frustrated I get by an unlock and/or answer mechanism that can't track my fingers in real time like something as simple as CM7 does.
And don't get me started on the underutilisation of the video hardware.
AwesomeTurtle said:
Nope, just a league of people whining because that makes things happen faster. There really is nothing more to it.
Click to expand...
Click to collapse
No, this phone was released with a promise. When it was released, ICS had been out for 6 months or more, and I'm sure the OEMs had access to the system and API's well before the official release. By the time ICS is released for our phones (IF it is released for our phones), JB will have been out for several months.
This is a matter of support and broken promises. I am NOT just whining. I was sold a phone with a promise of ICS and it has NOT been delivered, and at this point the time has gone beyond reasonable.
If we don't make noise now, it WILL be forgotten and you're going to end up with a phone outdated well before it's time.
dr4stic said:
The reason you get a glittery screen when coming from roms that are like the SGS2 is because they use different display panel hardware than we do. I'd be careful porting things from different manufacturers unless you really know what you're doing. You'd hate to go and format some partitions you can't get back
Click to expand...
Click to collapse
Yeah the first time i tried to flash the rom nothing happened. ahah but then i went into the updater script changed some things and got it to flash. but since the hard ware is the same do you think i could use the display drivers from the amaze 4g and replace them in the SII rom and maybe it will work? well maybe i will have to do some logcats to see why the amaze rom isnt booting.
L7ChrisL7 said:
Yeah the first time i tried to flash the rom nothing happened. ahah but then i went into the updater script changed some things and got it to flash. but since the hard ware is the same do you think i could use the display drivers from the amaze 4g and replace them in the SII rom and maybe it will work? well maybe i will have to do some logcats to see why the amaze rom isnt booting.
Click to expand...
Click to collapse
I doubt it. The drivers are baked into the kernel, they aren't modules or libraries. You'd have to get another compiled kernel working for our device, and you'll undoubtedly lose other drivers (camera, wifi come to mind). It's, of course, up to you to brick your own phone
dr4stic said:
I doubt it. The drivers are baked into the kernel, they aren't modules or libraries. You'd have to get another compiled kernel working for our device, and you'll undoubtedly lose other drivers (camera, wifi come to mind). It's, of course, up to you to brick your own phone
Click to expand...
Click to collapse
Well cant you decompile a kernel? or maybe if i get the source of both devices i can use the code to compile a new kernel... hmmm all stuff to try. but compiling a kernel takes a while i think ill update my PC first haha. Im not necessarily worried about the other drivers not working, i just want to make progress, or at least help us make a push in the right direction. Im sorry if im being too optimistic or noobish, i just want to learn what people have and havent tried, so i dont waste my time on what has already been done.
http://support.t-mobile.com/community/phones_data_devices/android/blaze_4g?view=discussions
^--Post a thread in the T-mobile discussion forums! The most recent thread so far is asking for a status update, and if you guys can make more posts/threads about it, maybe we'll get a response from someone
here's a thread we can vent at!
spartanerik said:
http://support.t-mobile.com/community/phones_data_devices/android/blaze_4g?view=discussions
^--Post a thread in the T-mobile discussion forums! The most recent thread so far is asking for a status update, and if you guys can make more posts/threads about it, maybe we'll get a response from someone
Click to expand...
Click to collapse
I already did - rather I saw a post and have decided to bump it daily so it remains at the top.
http://support.t-mobile.com/thread/31124?tstart=0
Create a support account and let's let them know they need to get this done!!!
Every post on the support forum discussing the ICS update will get a post (and bump) from me everyday!
anactoraaron said:
I already did - rather I saw a post and have decided to bump it daily so it remains at the top.
http://support.t-mobile.com/thread/31124?tstart=0
Create a support account and let's let them know they need to get this done!!!
Every post on the support forum discussing the ICS update will get a post (and bump) from me everyday!
Click to expand...
Click to collapse
http://support.t-mobile.com/people/tmo_erica
Try sending an email to [email protected] and ask (nicely) about a status update on the ICS update for our phone! I just sent one, and hopefully if we send enough we can get some traction
Hello Fellow XDA Members,
I am about to purchase my T-Mobile LG G2 as of tomorrow. Coming over from a Nexus 4 rooted / stock / Xposed. I am very excited about. This phone really caught my eye from beginning against the advice of my friends to wait for the Galaxy S5. This is the one I want. Of course there are tons of perks to being rooted and it's usually the first thing I do when I get a new phone. One thing I noticed about this phone is there doesn't seem to be an inclusive *ROOT* thread and I am not sure where to start other than the regular stuff; ADB enabled, drivers installed, etc. Also I know this phone is in sort of a transitional update to Android 4.0 presently (although this doesn't apply to T-Mobile as of this writing). So, I guess what I am looking for is.
1. Can someone link me a solid thread to ROOT instructions for the T-Mobile variant or is it carrier specific? Does it even matter?
2. Are there any special things I should know about like ( I recently helped a friend fix his LG Optimus due to the fact that he did not have an unlocked bootloader, rooted it and uninstalled system apps and got himself in a bootloop / soft brick) because the phone had some special *EVIL* software that would do that without first unlocking the bootloader.
3. Is there any "going back" from root on the LG G2? I mean I was reading something about root detecting, warranty voiding software. So, in other words if I get the device tomorrow and have it rooted by tomorrow night, then over the weekend I notice a weird glitch that would be covered under warranty, am I S.O.L. because I rooted it or can I flash back to stock and unroot and RMA the device?
4. Anything else I should know about that is an issue for the LG G2 during the root / romming process or otherwise.
Also I would like to thank everyone again. Going on my 4th device using only XDA as my source of info and help and still 100% HARD brick free and I plan to keep it that way. IMHO I don't see how people use phones unrooted. Thanks for the help! See you around the forums.
jcnbama said:
Hello Fellow XDA Members,
I am about to purchase my T-Mobile LG G2 as of tomorrow. Coming over from a Nexus 4 rooted / stock / Xposed. I am very excited about. This phone really caught my eye from beginning against the advice of my friends to wait for the Galaxy S5. This is the one I want. Of course there are tons of perks to being rooted and it's usually the first thing I do when I get a new phone. One thing I noticed about this phone is there doesn't seem to be an inclusive *ROOT* thread and I am not sure where to start other than the regular stuff; ADB enabled, drivers installed, etc. Also I know this phone is in sort of a transitional update to Android 4.0 presently (although this doesn't apply to T-Mobile as of this writing). So, I guess what I am looking for is.
1. Can someone link me a solid thread to ROOT instructions for the T-Mobile variant or is it carrier specific? Does it even matter?
2. Are there any special things I should know about like ( I recently helped a friend fix his LG Optimus due to the fact that he did not have an unlocked bootloader, rooted it and uninstalled system apps and got himself in a bootloop / soft brick) because the phone had some special *EVIL* software that would do that without first unlocking the bootloader.
3. Is there any "going back" from root on the LG G2? I mean I was reading something about root detecting, warranty voiding software. So, in other words if I get the device tomorrow and have it rooted by tomorrow night, then over the weekend I notice a weird glitch that would be covered under warranty, am I S.O.L. because I rooted it or can I flash back to stock and unroot and RMA the device?
4. Anything else I should know about that is an issue for the LG G2 during the root / romming process or otherwise.
Also I would like to thank everyone again. Going on my 4th device using only XDA as my source of info and help and still 100% HARD brick free and I plan to keep it that way. IMHO I don't see how people use phones unrooted. Thanks for the help! See you around the forums.
Click to expand...
Click to collapse
Awesome phone and great choice I totally agree.
Proceed with caution though, I have extensive experience with android phones and this one has turned into a flourishing source of nightmares for me and is seeming to head towards a total "paperweight" story. This all stems from rooting and recovery installation and such obviously, I am sure if you leave it untouched it is fantastic.
Just make sure you follow things EXACTLY as told. :good:
zprovo said:
Awesome phone and great choice I totally agree.
Proceed with caution though, I have extensive experience with android phones and this one has turned into a flourishing source of nightmares for me and is seeming to head towards a total "paperweight" story. This all stems from rooting and recovery installation and such obviously, I am sure if you leave it untouched it is fantastic.
Just make sure you follow things EXACTLY as told. :good:
Click to expand...
Click to collapse
Well, I'm not one to ever leave anything untouched. What has been the main issue? Finding credible threads? Roms, etc? One thing confusing for me is I've been kinda used to the T-Mobile thread or the AT&T thread. Seems like this is mostly compiled into one with the development section being separated.
Sent from my Nexus 4 using xda app-developers app
jcnbama said:
Well, I'm not one to ever leave anything untouched. What has been the main issue? Finding credible threads? Roms, etc? One thing confusing for me is I've been kinda used to the T-Mobile thread or the AT&T thread. Seems like this is mostly compiled into one with the development section being separated.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Neither am I trust me. i would never sport a locked/crippled/stock device.
There is a lot of info out there honestly. Search for Ioroot and read about that, it's pretty awesome basically an automated rooting software.
Hardest thing for me has been all kind of compatibility/driver issues. Had to use multiple computers, x64 and x86 architectures.
But there are obviously loads of people out there enjoying this phone. I am just part of the select few who had issues.
You should go for it seriously, the display is breathtaking, I have pretty large hands and this is the first time I have had one that feels just perfect in one hand which is huge to me. Can't comment much on the using of it since it only worked for about a day and a half before i wrecked it apparently .
It seems very intuitive though, the camera is really awesome too. Being a photographer I was really impressed by the menu flow and the amount of options you have. Its really amazing that they include cameras like these at the price the phone sells for.
Is it dangerous to uninstall system apps or LG apps once rooted? On my friends Optimus that's what jacked him up. If you didn't have an unlocked bootloader and you just simply rooted and removed system apps then you would get a soft brick. Is there any similar issues here?
Sent from my Nexus 4 using xda app-developers app