We learned about this on the IRC tonight, so I wanted to pass it on. The v2 Malata devices have a different partition stucture, as well as 1GB of RAM and not 512. It seems that this device is actually showing up in the States, and at least one user here in XDA got one via a SEARS.COM order.
His model number is UPC-320-2.2, and 1GB RAM should actually show on the box, as well. If you happen to have one of these, consider yourselves lucky for the RAM bump, but also unlucky because using our nvflash batch scripts could bork your device. So beware. It's also possible that bekit had one of these, at one point.
Since most of us don't even have the device, there's really no way for us to support it. I would actually love to get my hands on one of these things, but the likelihood of getting one of these is probably very slim.
Also, be aware that having a 300 is still no guarantee that the nvflash tools will work. As far as we know, there could be 320's repackaged in 300 boxes. Just the fact that these v2's showed up in the States at all should something to keep in the back of your mind.
Wait, so this one is brickible?
I wonder if that model is ready for a SIM card???
bijan588 said:
Wait, so this one is brickible?
Click to expand...
Click to collapse
Not that I know of. The only couple people that did use the original restore on one of the 1GB models did get it back working with the restore built for them.
Darn! I got a 300-2.2 ...
jimcpl said:
Darn! I got a 300-2.2 ...
Click to expand...
Click to collapse
Me too
Well I guess its not all bad. Our device is actually supported, so
How's the viewing angle on that model? ( Got UPC300-2.2. ) meh is running perfectly so no complain.
roebeet said:
We learned about this on the IRC tonight, so I wanted to pass it on. The v2 Malata devices have a different partition stucture, as well as 1GB of RAM and not 512. It seems that this device is actually showing up in the States, and at least one user here in XDA got one via a SEARS.COM order.
His model number is UPC-320-2.2, and 1GB RAM should actually show on the box, as well. If you happen to have one of these, consider yourselves lucky for the RAM bump, but also unlucky because using our nvflash batch scripts could bork your device. So beware. It's also possible that bekit had one of these, at one point.
Since most of us don't even have the device, there's really no way for us to support it. I would actually love to get my hands on one of these things, but the likelihood of getting one of these is probably very slim.
Also, be aware that having a 300 is still no guarantee that the nvflash tools will work. As far as we know, there could be 320's repackaged in 300 boxes. Just the fact that these v2's showed up in the States at all should something to keep in the back of your mind.
Click to expand...
Click to collapse
This probably isn't really a different model, other than the ones that are supposed to be the gTab are just cost-reduced versions, i.e. half the RAM, no mini-PCIe slot for the SIM/3G support...
...but it would be nice to get the 1GB model simply for the extra RAM, AND if it had the miniPCIe to see if that could be swapped for GPS...
As to the flash problem... wasn't that just because it had a different partitioning of the internal flash? I never did hear what finally happened to that one, but I just thought that bekit had gotten one with a semi-borked partitioning of internal flash...
It's the same in the respect that it has an APX mode and it's hard to brick. But, if you didn't back up your partitions in advance, the scripts we use wouldn't work because they're designed for a device with a different partition structure. You could actually fix it by using a bekit script (if he still has it) or a script supplied by Malata.
Mrbobrowitz is the user, and he told me that the viewing angles are the same.
roebeet said:
It's the same in the respect that it has an APX mode and it's hard to brick. But, if you didn't back up your partitions in advance, the scripts we use wouldn't work because they're designed for a device with a different partition structure. You could actually fix it by using a bekit script (if he still has it) or a script supplied by Malata.
Mrbobrowitz is the user, and he told me that the viewing angles are the same.
Click to expand...
Click to collapse
I figured as much... they changed as little as possible, just removed some things so that they could get to a lower build cost for some customers...
[EDIT]
...and while we're on cost reduction, it's ALWAYS puzzled me that they left that hw reset button on the board, while providing no way to access it short of disassembling the gTab...
[/EDIT]
roebeet said:
It's the same in the respect that it has an APX mode and it's hard to brick. But, if you didn't back up your partitions in advance, the scripts we use wouldn't work because they're designed for a device with a different partition structure. You could actually fix it by using a bekit script (if he still has it) or a script supplied by Malata.
Mrbobrowitz is the user, and he told me that the viewing angles are the same.
Click to expand...
Click to collapse
I asked about something similar earlier, but if you used nvflash to pull the partitions, couldn't,t be used to restore from the same files? Is it just a matter of getpartitiontable, then using info from that to restore? BTW I notice when I did getpartitiontable, the output is binary, so how do you read that?
Jim
jimcpl said:
I asked about something similar earlier, but if you used nvflash to pull the partitions, couldn't,t be used to restore from the same files? Is it just a matter of getpartitiontable, then using info from that to restore? BTW I notice when I did getpartitiontable, the output is binary, so how do you read that?
Jim
Click to expand...
Click to collapse
That's interesting, because I was on IRC when I decided to try the custom fws and bekit had just gotten his oddball gTab at the time, so I dumped my partition table for him and it came out as ASCII text... while for other, like you apparently, it's a binary dump...
cutterjohn said:
That's interesting, because I was on IRC when I decided to try the custom fws and bekit had just gotten his oddball gTab at the time, so I dumped my partition table for him and it came out as ASCII text... while for other, like you apparently, it's a binary dump...
Click to expand...
Click to collapse
Thanks for that! I thought I was imagining it ...
jimcpl said:
Thanks for that! I thought I was imagining it ...
Click to expand...
Click to collapse
Any idea why the getpartitiontable returns binary?
I'm using:
nvflash --bl bootloader.bin --getpartitiontable
Jim
I'm looking into getting ag tab very soon and wondering if this means if I get one of the newer versions, 3.20, well I all be able to root and flash a ROM? Not really sure what nvflash does sorry :/
ellis125 said:
I'm looking into getting ag tab very soon and wondering if this means if I get one of the newer versions, 3.20, well I all be able to root and flash a ROM? Not really sure what nvflash does sorry :/
Click to expand...
Click to collapse
It's unlikely that you'd get a 320. But, if you did, update.zips should still work fine - this is what all the mods are.
nvflash is more of a low-level tool that a few of us, use. That's the one you have to be careful with, if you have a 320. The early bekit scripts are based on the 300, not the 320.
ellis125 said:
I'm looking into getting ag tab very soon and wondering if this means if I get one of the newer versions, 3.20, well I all be able to root and flash a ROM? Not really sure what nvflash does sorry :/
Click to expand...
Click to collapse
This is from a relative Gtab newbie, but nvflash is a low-level command line tool that Nvidia provided as part of their Tetra SDK, which allows you to do things like:
- retrieve and push partitions from/to the sdcard
- push a bootloader to the memory
So, it's a kind of 'bare metal' type tool, I.e., doesn't rely on an OS, and you need to know about partitions, etc. to not mess you system up. On the other hand, in some situations, it can be the only tool that can help.
There are other methods for flashing a Gtab. like stock recovery and CWM, which are more user-friendly and 'safer'
Jim
Alright as long as I can still flash everything and only have to use clockwork I don't mind. Thanks for the info!
ellis125 said:
Alright as long as I can still flash everything and only have to use clockwork I don't mind. Thanks for the info!
Click to expand...
Click to collapse
Actually IF you do get the 1GB version consider yourself VERY lucky. I'd almost kill to get that for the extra RAM alone, and if it has the mini-PCIe slot to boot, well... [EDIT] I mention the mini-PCIe because well, internal GPS would be so NICE to have instead of having to pair an external bluetooth GPS, which I still need to buy... [/EDIT]
If worse comes to worst and those start showing up more commonly, I'm sure that someone who has one will mod the scripts for others with the same variant that want to use nvflash...
cutterjohn said:
Actually IF you do get the 1GB version consider yourself VERY lucky. I'd almost kill to get that for the extra RAM alone, and if it has the mini-PCIe slot to boot, well... [EDIT] I mention the mini-PCIe because well, internal GPS would be so NICE to have instead of having to pair an external bluetooth GPS, which I still need to buy... [/EDIT]
If worse comes to worst and those start showing up more commonly, I'm sure that someone who has one will mod the scripts for others with the same variant that want to use nvflash...
Click to expand...
Click to collapse
If they start showing up more commonly, I might go out and buy another Gtab !
Having said that is there any easy way to tell? Roebeet said that it was labelled on the (outside?) box?
Jim
Related
When I boot up the phone, I get a message in my notification bar saying:
Damaged Internal SD Card.
Not an external memory card. My internal SD card. The one built into the phone. Anyone know if there's a way to fix this? Is there a way to reformat the built in SD card? My computer can't recognize it anymore. Am I pretty much screwed?
I posted this in androidforums as well.
EDIT: I found the "Format Card" option in settings. It's working fine, although the fact that this came up in the first place is very troublesome. Some further information: I did the GPS thing where you dial *#*# and some number, then rebooted my phone. My internal card was fine until I rebooted. That was the first time I got that message of a damaged internal sd card.
dude same thing happened to me today - any way to fix this ?
Format it, and hope you never see those dreadful words again.
norcal einstein said:
Format it, and hope you never see those dreadful words again.
Click to expand...
Click to collapse
This is a known fact that has been reported on some Galaxy S phones, it is coming from doing multiple Lag fixes of the phone internal SD from RFS to EXT. buyer be ware when flashing lag fixes over and over.
dpmurphy81 said:
This is a known fact that has been reported on some Galaxy S phones, it is coming from doing multiple Lag fixes of the phone internal SD from RFS to EXT. buyer be ware when flashing lag fixes over and over.
Click to expand...
Click to collapse
what about when you flash a ROM that comes with LAg fix by default ? and you Disable it all the time can that happen to you? cuz ive flashed but most roms r being gay now with Lag fix ... i disable always might i get that msg? :/
dpmurphy81 said:
This is a known fact that has been reported on some Galaxy S phones
Click to expand...
Click to collapse
This affects the bell vibrants only, the captivates never had this issue.
peachpuff said:
This affects the bell vibrants only, the captivates never had this issue.
Click to expand...
Click to collapse
One can assume that the captivate can have this problem also the hardware is no different really from the vibrant. And I feel in my opinion that it is related to the quality of the flash memory chip itself weather you have this problem. compound this with the relentless conversion of the RFS file system it is just a matter of time I believe. The trade off of speed is stability. But that is only my opinion...
dpmurphy81 said:
One can assume that the captivate can have this problem also the hardware is no different really from the vibrant. And I feel in my opinion that it is related to the quality of the flash memory chip itself weather you have this problem. compound this with the relentless conversion of the RFS file system it is just a matter of time I believe. The trade off of speed is stability. But that is only my opinion...
Click to expand...
Click to collapse
That actually is a pretty big assumption. Just because two phones appear "similar" based on the published specs doesn't mean their insides are at all related. We already know that from a strictly hardware standpoint, even the two GSM cousins in America (the Vibrant and the Captivate) have different physical hardware inside, and many other versions of the i9000 abroad vary quite a bit too. Samsung produces these phones in very large batches, and who knows exactly what the differences are in the individual components put onto each board.
And as far as I'm aware, there's not been a single case of repeated "lag fix" operations causing damage to the hardware. Which makes sense when you think about it too. If I load a single 720p movie onto my internal SD (OneNAND), that probably requires a lot more NAND cells to be touched than an entire system/data/dbdata/cache lag fix being applied. Since all those operations really do is backup the partition, delete the partition, format a new partition, and then restore the data back over. Not really the most intensive thing you can do with your internal SD...
The OP's problem probably lies somewhere in PEBKAC. Not unmounting storage cleanly from the PC, or accidentally unplugging during a file transfer, battery came out unexpectedly at some point, etc. I end up re-flashing my ROM so regularly that I never really have time for little problems to build into big problems, but that might have happened here. Just so many corrupt sectors before the OS finally gives up trying to deal with it. Either way, since formatting seems to have fixed the problem, and this storage is solid-state, not mechanical, the problem is probably not in the hardware.
I had this issue on my captivate, as did two others that I know of, with a certain release of voodoo lag fix. Haven't heard of complaints since, and although it was tricky to fix haven't had problems since
Its not just with Bell phones. But I agree I think its software not hardware (at least for us Cappy folks!)
Sent from my GT-I9000 using XDA App
fatttire said:
I had this issue on my captivate, as did two others that I know of, with a certain release of voodoo lag fix. Haven't heard of complaints since, and although it was tricky to fix haven't had problems since
Its not just with Bell phones. But I agree I think its software not hardware (at least for us Cappy folks!)
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
What was the fix you applied exactly? I'm interested to it. Thanks
I would like to know what else i can try. I am currently.experiencing the same damaged internal sd card issue and have tried reformatting to no avail. It just seems to skip the actual formating. My pc also cannot see the phone as a drive. Any help would be appreciated.
Bump. Having the same issue. Cant see any files in 'my files' (samsung galaxy s i9000), internal sd wont mount or format in clockworkmod recovery
Hi guys, Did you solve the problem somehow?
I just wanted to state that this may be correctable with JTAG. If you guys are interested in letting me try to correct this with JTAG please let me know. I have been able to fix, what I refer to as partition bricking on the i9000 and T959 Vibrant and this sounds similar.
Nah.... JTAG is fully unnecessary. See, the SDCard is a shared space. It's likely the cause of this problem was flashing an inappropriate PIT file after performing a lagfix. Try flashing the stock pit file... I'd attach it as it's really small, but i seem to have lost it . You're going to need to do a total reset on your phone. Use CWM to wipe and delete and format everything you can.
If this is an ACTUAL bad SDCard, then nothing will bring it back short of replacing the chip. JTAG would not be the way to go for this.
AdamOutler said:
Nah.... JTAG is fully unnecessary. See, the SDCard is a shared space. It's likely the cause of this problem was flashing an inappropriate PIT file after performing a lagfix. Try flashing the stock pit file... I'd attach it as it's really small, but i seem to have lost it . You're going to need to do a total reset on your phone. Use CWM to wipe and delete and format everything you can.
If this is an ACTUAL bad SDCard, then nothing will bring it back short of replacing the chip. JTAG would not be the way to go for this.
Click to expand...
Click to collapse
Not trying to butt heads with you but I've worked on many phones with what I refer to as "partition bricking" and they were not fixable with any method of flashing. I've gotten a few that were able to be fixed with PIT repartitioning but many have not been. Also see the other thread I replied to you in as JTAG could be a fully capable solution in this instance.
As stated, JTAG can address any portion of the NAND, not just the PBL and SBL blocks.
connexion2005 said:
Not trying to butt heads with you but I've worked on many phones with what I refer to as "partition bricking" and they were not fixable with any method of flashing. I've gotten a few that were able to be fixed with PIT repartitioning but many have not been. Also see the other thread I replied to you in as JTAG could be a fully capable solution in this instance.
As stated, JTAG can address any portion of the NAND, not just the PBL and SBL blocks.
Click to expand...
Click to collapse
Sure, it can. By default Riff does not. Also, JTAG is overkill for a bad partition flash. Just reformat from CWM and it should be fine.
AdamOutler said:
Sure, it can. By default Riff does not. Also, JTAG is overkill for a bad partition flash. Just reformat from CWM and it should be fine.
Click to expand...
Click to collapse
RIFF DOES SUPPORT THIS NATIVELY. Also, the phones I obtained were not fixable with CWM repartitioning. I spent hours on the first few to still have mount issue with DBDATA and /dev/block/mmcblk0p1 and /dev/block/mmcblk0p0 errors. I have found a few that were fixable with re-partitioning via ODIN but several that required JTAG to fix. I didn't spend days trying to find the perfect combo before turning to JTAG but I spent a lot of time on many of these phones.
Hi Connexion, I would be interested in trying this, can we do this to Korean Variant of Galaxy SHW M110 (anucall) let me know
Hi,
Unfortunately, that is not a supported model on the RIFF box right now. I sent you a PM I believe with some advice though to hopefully get through it.
Hey all,
I'm getting my G Tablet tomorrow and I'd just like to get some things clarified.
I know, the first thing some will say is USE SEARCH! Well, I did - and that's actually why I just want to get some things straight before I go down the path of modifying the device software. See, reading it all has managed to confuse me more than help me get a definitive instruction set for forging ahead.
I'm seeing the update "****s on CWM" according to a user...and then a 'fix' for that. Than I see that Gapps causes FCs for some, while it works for others. So...yeah, a little back and forth on what to do and who's instructions to follow.
Alright, so first thing's first....Should I flash the Clockwork Mod that I'm seeing available - 0.8? or is there something else I should consider or that I've missed? or maybe wait for a newer version? Should I even flash CWM if I get the newest (and I WILL be getting the newest) S/W version? Are there any downsides at all to flashing CWM on there in terms of messing with OTA updates, etc?
I read this:
"All the ROMS use a standard firmware updater that can be used by non-technical users. Here is an explanation on how it works:...."
Sooo, does that mean I can live without CWM? If an update doesn't work for some reason, will I be able to fix it or overwrite it somehow if I can't get into the tablet at all from the tablet itself? I read something about going into APX mode and putting things on through Windows, is this an infallible method?
Second of all, I read the FAQ thoroughly (I think and hope) but I'm still not 100% on what Gapps to DL or how to put a working Android Market on there especially with this new S/W update. I've seen how to 'fix' the Market to see missing apps, but not how to actually install it on the G Tablet. I may have missed that post somewhere on here.
I'm also unclear if I should get Gapps or not at all, as I've read that some have FCs on there while others do not - so what's the general consensus in light of this update that was just released as of Dec. 21, 2010?
Ultimately, here is what I'd like from my GTab:
I'd like to run the new official Tapn'Tap released recently first and foremost.
I'd like to have the official/unofficial (w/e) Google Market.
I'd like to run Google Apps (Gtalk, Gmail, etc.).
IF I don't like Tapn'Tap, and this is a worse case scenario situation, as in if I HATE TnT - I'd like to have the option to slap something else on there and I'd like to make sure I don't brick my Tablet. Whether that means storing an original official TnT ROM or whatever.
Point me in the right direction please, especially considering things may have changed as of the new S/W update.
Thanks much and sorry for all the questions. I assure you I used search and I attempted to put it together on my own. It's been a long time since I've modded (G1 was the last time) and I don't do it often. Also, apologies if I posted this in the wrong section....I considered posting it in Dev. section but this one seemed better suited.
Thanks again, XDA rocks.
Neoprimal said:
Hey all,
I'm getting my G Tablet tomorrow and I'd just like to get some things clarified.
I know, the first thing some will say is USE SEARCH! Well, I did - and that's actually why I just want to get some things straight before I go down the path of modifying the device software. See, reading it all has managed to confuse me more than help me get a definitive instruction set for forging ahead.
I'm seeing the update "****s on CWM" according to a user...and then a 'fix' for that. Than I see that Gapps causes FCs for some, while it works for others. So...yeah, a little back and forth on what to do and who's instructions to follow.
Alright, so first thing's first....Should I flash the Clockwork Mod that I'm seeing available - 0.8? or is there something else I should consider or that I've missed? or maybe wait for a newer version? Should I even flash CWM if I get the newest (and I WILL be getting the newest) S/W version? Are there any downsides at all to flashing CWM on there in terms of messing with OTA updates, etc?
I read this:
"All the ROMS use a standard firmware updater that can be used by non-technical users. Here is an explanation on how it works:...."
Sooo, does that mean I can live without CWM? If an update doesn't work for some reason, will I be able to fix it or overwrite it somehow if I can't get into the tablet at all from the tablet itself? I read something about going into APX mode and putting things on through Windows, is this an infallible method?
Second of all, I read the FAQ thoroughly (I think and hope) but I'm still not 100% on what Gapps to DL or how to put a working Android Market on there especially with this new S/W update. I've seen how to 'fix' the Market to see missing apps, but not how to actually install it on the G Tablet. I may have missed that post somewhere on here.
I'm also unclear if I should get Gapps or not at all, as I've read that some have FCs on there while others do not - so what's the general consensus in light of this update that was just released as of Dec. 21, 2010?
Ultimately, here is what I'd like from my GTab:
I'd like to run the new official Tapn'Tap released recently first and foremost.
I'd like to have the official/unofficial (w/e) Google Market.
I'd like to run Google Apps (Gtalk, Gmail, etc.).
IF I don't like Tapn'Tap, and this is a worse case scenario situation, as in if I HATE TnT - I'd like to have the option to slap something else on there and I'd like to make sure I don't brick my Tablet. Whether that means storing an original official TnT ROM or whatever.
Point me in the right direction please, especially considering things may have changed as of the new S/W update.
Thanks much and sorry for all the questions. I assure you I used search and I attempted to put it together on my own. It's been a long time since I've modded (G1 was the last time) and I don't do it often. Also, apologies if I posted this in the wrong section....I considered posting it in Dev. section but this one seemed better suited.
Thanks again, XDA rocks.
Click to expand...
Click to collapse
I don't know how much direction pointing I can do but here goes..
Clockwork mod in my opinion is a necessity. Version 0.8 is the best one for most people because of how it deals with the memory locations. Yes, you can do things without it. The update process is as simple as putting an update.zip file, and a recovery folder with a command file in it on an sdcard and holding the vol + button while hitting power. It is easy. Clockwork has a lot of little features though that make life easier. You can make a complete system backup with it. You can install updates, and new firmware with it. You can completely lock up your tablet and using clockwork and your backup be back in business in about 3-4 minutes. You can load new roms and if you hate them you can go back to your old working stuff in minutes. Yes, there are ways to make one of these tablets work again when they get stuck. I don't think anyone has actually bricked one. Some may think they have, but I doubt it.
Unless you are dead set on wanting the stock TnT interface the easiest way to get what you want is to load one of the roms. Yes, there are ways to get most of it without loading a new rom. Most everyone that has gone the I have to stay stock but want all the mods has eventually just loaded a rom. TnT3.0 is based on the latest stock stuff. It has the market, flash, etc. already in it. VegaN is what I use mostly but they are both stable and fast.
Before you flash something brand new that just came out I would read about it and see what others have to say about issues. It usually only takes about 30 minutes until you can tell if it is going to be good or not.
All of the roms for this tablet have there own little quirks. The stock has gotten better with each update but it still is not as good as the ones I named.
Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard.
With a little bit of searching almost everything you may want it to do can be done. I really love mine, and when I got it almost 2 months ago I hated it...
"Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard."
"Sigh" of relief. Then I'm not too worried. As I said I've dabbled in modifying my G1 and it is mostly cake. But I've just been seeing conflicting posts on whether cwm works with the newest official tnt release or not so I wasn't sure what to do.
Thanks for your advice. And when I said pointers, I meant like this as well as pointing me to any posts I may have missed on how to do whatever. Though I THINK I found most of them.
Neoprimal said:
"Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard."
"Sigh" of relief. Then I'm not too worried. As I said I've dabbled in modifying my G1 and it is mostly cake. But I've just been seeing conflicting posts on whether cwm works with the newest official tnt release or not so I wasn't sure what to do.
Thanks for your advice. And when I said pointers, I meant like this as well as pointing me to any posts I may have missed on how to do whatever. Though I THINK I found most of them.
Click to expand...
Click to collapse
The new release overwrites clockwork. But it is not hard to put back. Always a good idea to copy the clockwork backups folder to your pc, or somewhere they won't be lost. The custom roms typically leave the recovery image alone and can be installed with or without clockwork by either extracting the zip contents for stock recovery, or installing it as is in clockwork.
Sprdtyf350 said:
Finally.. This tablet is very easy to play with. It is pretty much unbrickable.
Click to expand...
Click to collapse
I can vouch for that. Erased system, boot, data and cache in preparation for a new ROM. Accidentally rebooted and couldn't get into recovery. Booted it into APX mode, flashed stock and was on my way.
I would just run ZRoot, then upload the TnTLite 3.0 recovery and update.zip and then do the recovery mode process. You should have a microsd handy just in case it doesn't work, but so far I haven't needed that.
This tablet is much easier to work with and very forgiving since VS never took the time to lock down the bootloader etc like Motorola did with my Droid X. You really shouldn't fear changing files out etc, provided you're getting a ROM from one of the people providing them here. If you can press and hold two buttons at once, you can make your gTab an awesome little tablet. It benchmarks about 1000 points higher than my Droid X on quadrant. Can't wait to see what these guys can do with Gingerbread.
Sprdtyf350 said:
The new release overwrites clockwork. But it is not hard to put back. Always a good idea to copy the clockwork backups folder to your pc, or somewhere they won't be lost. The custom roms typically leave the recovery image alone and can be installed with or without clockwork by either extracting the zip contents for stock recovery, or installing it as is in clockwork.
Click to expand...
Click to collapse
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
hogasswild said:
I would just run ZRoot, then upload the TnTLite 3.0 recovery and update.zip and then do the recovery mode process. You should have a microsd handy just in case it doesn't work, but so far I haven't needed that.
This tablet is much easier to work with and very forgiving since VS never took the time to lock down the bootloader etc like Motorola did with my Droid X. You really shouldn't fear changing files out etc, provided you're getting a ROM from one of the people providing them here. If you can press and hold two buttons at once, you can make your gTab an awesome little tablet. It benchmarks about 1000 points higher than my Droid X on quadrant. Can't wait to see what these guys can do with Gingerbread.
Click to expand...
Click to collapse
with the new update however does the z4root still work? i heard it may not anymore. just curious also since im hopefully getting mine on sat for xmas
rothnic said:
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
Click to expand...
Click to collapse
Thanks for the info Rothnic! I had already flashed it before I figured out it removed Clockwork. Learning new stuff every day is good... Thanks..
dragonfly1113 said:
with the new update however does the z4root still work? i heard it may not anymore. just curious also since im hopefully getting mine on sat for xmas
Click to expand...
Click to collapse
The very first time I rooted, I used ZRoot and installed 2.4.0. I didn't change anything and used the exact same process of simply copying over the 3.0.0 files over to the root directory of the internal memory and did the recovery procedure (vol+ and pwr keys). It worked like a charm.
hogasswild said:
The very first time I rooted, I used ZRoot and installed 2.4.0. I didn't change anything and used the exact same process of simply copying over the 3.0.0 files over to the root directory of the internal memory and did the recovery procedure (vol+ and pwr keys). It worked like a charm.
Click to expand...
Click to collapse
Ok cool, thanks cant wait for my g tablet hopefully sat morning
I think you'll like it a lot. I also own an iPad. While they are similar they are also a little different. Merry Christmas!
hogasswild said:
I think you'll like it a lot. I also own an iPad. While they are similar they are also a little different. Merry Christmas!
Click to expand...
Click to collapse
my mom has an ipad and my dad could only buy it while i was on my honeymoon bc he knew i wouldnt approve of an apple device in the house haha.
rothnic said:
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
Click to expand...
Click to collapse
My device hasn't come yet (damn you FedEx!) but I'm eagerly awaiting it.
My plan:
Unbox, start it....do a factory reset from the getgo if it has enough juice.
Set it back up. Charge it to full. If whatever comes on it is as unbearable as I've seen in on Youtube - start modifications.
Will CWM install on it AFTER I do the update if it's available to me? I've seen that the update messes with it if it's already there - but noone's mentioned putting it on there after the fact. I may just go that route for simplicity sake.
Thanks for this!, and thank you all for chiming in with your experience. I feel much better about just getting my hands dirty in it all. I had wrote something to someone yesterday about jumping in and just doing it, but when it comes to dealing with it yourself it can be a daunting task - especially when it still has that new smell, lol. Anyway, thanks again. You guys really rock.
Will stop back later on after I've done my thing
I think they are both nice devices. There are trade off for both of them. I think the screen on the iPad is wonderful, where the gTab's is okay. But the gTab has a forward facing camera, you can print from it, and you can modify it fairly easily too.
Sprdtyf350 said:
Finally.. This tablet is very easy to play with. It is pretty much unbrickable.
Click to expand...
Click to collapse
...famous last words...
Seriously though...trust the directions from the great devs like roebeet. Follow their instructions word for word. You can switch ROMs and then flash back if you want. No worries...
Off topic!
Well...disappointment! Fedex had my package out for delivery at 8am and at 8pm, they're not here. This is why I like UPS, they show up at my door on the day of delivery, no exceptions - they have shown up at almost 9pm before. The Archos 101 I got was sent out at 8am as well but got here at 1:30pm - I suppose that was before the holiday rush.
Checking the details of my tracking I'm seeing a "delivery exception" at 7:30pm (I guess it was time to get back to the facility so they can clock out by 8pm?) and upon calling them I get a somewhat stumbling but polite CS who tells me the delivery went out "late" - upon which I asked if 8am was considered late, especially from a distribution facility WITHIN the same zip code as I am, and all he could say was "Very sorry about this".
Aaaanyway....I guess it will be tomorrow before I can report my adventures.
Think I'll be able to get my $3.99 back from Amazon? I have Prime and with that the package would have come tomorrow anyway. Basically my $3.99 is wasted. Imagine if I didn't have Prime though? Whew.
ima_UNC_fan said:
...famous last words...
Click to expand...
Click to collapse
If you can figure out how to brick it you will probably get an award.. It won't be a good award but probably one of those top ten dumb things people do awards. So far unless you plug the motherboard into a wall socket no one has bricked one. May think they have, but like I said before I doubt it..
And your right.. If it can be done, someone eventually will figure out how. And then we will all laugh at them.. At least I will
I finally got the G tablet tonight and...alright, don't flame me for this - but I don't see what all the complaints about the screen being horrendous or the device being molasses slow are about?
I don't know how people are trying to view it...but when looking at it or setting it on a stand to watch media, I'm not seeing any problem with the viewing angles. It's about the same as my laptop so I watch it the same way.
It's not even a 1/4 as slow as the stuff I've seen on Youtube or in some of the review videos I've seen around the net. I haven't gotten a single FC. Granted, I haven't put in a SD Card yet so maybe problems will start then?
I guess I should note, the very first thing I did was did a factory reset. Then I hooked it up to Wifi and got the 3053 update. I'm one of those who will be waiting for the 'official' update on the 24th.
I set up the time and date, restarted and everything works. I haven't installed flash yet (don't need it that much) and stuff that I DO want on there right now works fine (skype, pandora, fring, dropbox, evernote). I'm slowly figuring out a list of what I want/need from my Mytouch 4G to port to the VS GTab. Figure I don't really NEED Gtalk, Gmail on there because I have these on my phone AND PC - do I really want them making noises all around my home on 3 devices? I was concerned about getting the Google Apps on but now I'm finding I really don't need them. So it seems to me this will be a matter of learning to separate what I need on a tablet vs. my phone - I was of the mentality that I should just get whatever's on my phone on the tablet, this is something others apparently do as they seem to want everything that's on their phone, on their tablets as well.
I personally don't see the point in that. Had I had the Google Market, that would have escaped me as I'd have used Appbrain to just get my motherload of apps from the MT4G to the GTab. Not having it has slowed me, and now I get to re-evaluate before I do grab apps for it.
Now I just have to merge/convert my HTPC into a NAS device as well and find an app that will allow me to DLNA stream media from it and I'll be in mobile heaven.
I haven't had my wifi drop at all anywhere in my home and I've marched all over with it (I use full Wifi N, no G compat. so maybe my range is wider?). Tried email, etc. to replicate crashes and force closes but haven't so far. No surfing issues. I DID find that one app got 'stuck' being downloaded and I had to delete the file before the 'downloading' icon would go away, even after restart.
Maybe the trick to getting a workable GTab in the first place is to factory reset it before first use? Iunno. Things may change and issues may pop up the more I use it and as time passes - but so far, so good!
Again, I can't thank XDA enough for the advice and info. I've found and been given.
Sprdtyf350 said:
If you can figure out how to brick it you will probably get an award.. It won't be a good award but probably one of those top ten dumb things people do awards. So far unless you plug the motherboard into a wall socket no one has bricked one. May think they have, but like I said before I doubt it..
And your right.. If it can be done, someone eventually will figure out how. And then we will all laugh at them.. At least I will
Click to expand...
Click to collapse
I figured it out. Accidentally hit one of the devkit nvflash .cabs and boom
Hello,
i've found that somewhere in our ancient G1's is hidden partition where's stored stock firmware with stock radio, SPL and recovery. I wasn't using it and had it off about 2 months. When I've brought it back to life i was very surprised that it was derooted, stock. I had to do it again, everything. So it means that somewhere has to be partition with it. I think this could save bricked phones and it could be used as extended phone memory. Just an idea..
you sure its the same G1?
Maybe its your brother/sisters one
Removed...
kostnacsek said:
Hello,
i've found that somewhere in our ancient G1's is hidden partition where's stored stock firmware with stock radio, SPL and recovery. I wasn't using it and had it off about 2 months. When I've brought it back to life i was very surprised that it was derooted, stock. I had to do it again, everything. So it means that somewhere has to be partition with it. I think this could save bricked phones and it could be used as extended phone memory. Just an idea..
Click to expand...
Click to collapse
post tech detail or me think u = idiot
You'd be the first person it has happened to.
I see two options;
1. you're right and there's said "rootkit", it would bridge the gap between trout and sapphire boards by possibly bringing trout storage capacity closer to that of sapphire because, otherwise, they're identical.
2. the rooted build you were using was possibly using a build fingerprint that allowed the updater program to identify it as a legitimate device. if the new boot took longer than expected (or if for any reason during those two months the phone was turned on by somebody else without your knowledge and given access to a network) then there's the possibility that an OTA update was delivered and the phone updated, but I believe those updates require confirmation (unfortunately, my ADP1 doesn't receive OTAs, so I wouldn't know how the process works).
I'm more inclined to believe that the second option is the most likely, but the first option sounds tempting. Has anybody done a close inspection of the trout and sapphire boards? how different are they inside? is the nand inside the msm chip or outside on the pcb? if the nand is inside the msm, then it would make very little sense for qualcomm to make only one chip that was used exclusively for only the htc dream (is there any other device that uses msm7201A AND has only 256 MB internal storage?) and make an exactly identical one for wider use...
====edit====
After some wikipideaing, found out that there's only one another HTC device that uses the same layout as the dream, the touch diamond (msm7201A AND 256 nand). The majority of MSM7201As all have the sapphire's 512 nand. Oh, well, it was worth a shot.
So you're saying that patition maybe really could exist? I'm not a developer, i don't really understand it.
And ad 2. thougt - I can be really sure that no-one but me turned the phone on and boot was pretty fast opposed to CM 6 which i was using before this incident. And even if so, it wouldn't be 1.5 ...
kostnacsek said:
So you're saying that patition maybe really could exist? I'm not a developer, i don't really understand it.
And ad 2. thougt - I can be really sure that no-one but me turned the phone on and boot was pretty fast opposed to CM 6 which i was using before this incident. And even if so, it wouldn't be 1.5 ...
Click to expand...
Click to collapse
practically no developers on xda-developers
the question is why do you think there is a hidden partition
and I do hope you are not getting mixed up with French cache
we all know about cache
And where could be whole stock firmware stored if it isn't in partition which is hidden for us? BTW it has to be in ready-to-use state, something like a BART backup, the partition must be big enough.
I think that if we knew about it, we were using it now, in example as extension of phone memory. Or as i said to recover bricked phones. It just happened that way. If you have other phone you could use instead, try to power off your G1 for same time.
You wanted tech specs - i dunno what exactly you want, it's just general G1, not ADP, stock version was 1.5. And even if i had last SPL, radio, AmonRa's recovery, after two months off, everything was stock, 1.5. I tried to start recovery - stock,.. i had to do whole rooting process again.
BTW - what's French cache?
kostnacsek said:
And where could be whole stock firmware stored if it isn't in partition which is hidden for us? BTW it has to be in ready-to-use state, something like a BART backup, the partition must be big enough.
I think that if we knew about it, we were using it now, in example as extension of phone memory. Or as i said to recover bricked phones. It just happened that way. If you have other phone you could use instead, try to power off your G1 for same time.
You wanted tech specs - i dunno what exactly you want, it's just general G1, not ADP, stock version was 1.5. And even if i had last SPL, radio, AmonRa's recovery, after two months off, everything was stock, 1.5. I tried to start recovery - stock,.. i had to do whole rooting process again.
BTW - what's French cache?
Click to expand...
Click to collapse
http://www.answers.com/topic/cache
http://en.wikipedia.org/wiki/Caché_(2005_film)
Caché loosely translated is hide,conceal,mask
this is where cache comes from
Effdee said:
post tech detail or me think u = idiot
Click to expand...
Click to collapse
loll you always speak your mind
e334 said:
loll you always speak your mind
Click to expand...
Click to collapse
cruel to be kind
There isn't a thread for this for our phone, so I thought I would make one seeing as i've tried it. A program called mobile odin https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&feature=nav_result Will allow you to run odin from your device without connecting it to your computer. Its super simple to use and it works pretty well. My charging port is hosed so I can't connect it anyways. I was on ICS and needed to go back to GB. Had to use this app and got back on GB no problem. I don't see a free version of the app anywhere so depending on how much you use odin, 5 bucks might be a good investment.
Hmm I ran the program and sent the logs a few months ago and never heard anything back to get our device supported and still doesn't say it supports this device.
It takes 30 minutes to run the system dump to find out our device isn't compatible......after running the dump....and to find out it wouldn't work
Its not worth the hassle when you've only got 15 minutes to get the refund.
I'd like to see screenshots or something to show that this actually does officially work on our device ....considering its not on the list of compatible devices.
Thanks
I guess after 2 days without a response ....there's not going to be one?
To bad I was hoping that it was going to be worth the money
Too bad I'm stuck on ics as well got excited when I started reading this thread.
Sent from my SGH-T959V using xda app-developers app
??? Anything???
Or is this just a bogus post....and in the wrong section....should have went in themes and apps
A search would show that XDA members gets a lite version as with lots of other apps for free.
http://forum.xda-developers.com/showthread.php?t=1347899
Ive run it.....it generates a dump file (mobileodin.txt) that you send in and hope that he incorperates your device in the next update .....and since it does this ...it basically is not suported as of yet.
So the op is saying it works.....but in fact it doesnt.
I would like to see some evidence that it works for him and like to know how it does on his device and not on mine.
Also with the lite version you have to dl a flash kernal specific to your device from that same thread....but since our device is not suported...you wont find one.
Y'all should do alot more reading before posting links to something that doesnt suport our device.
i did read that thread thuroughly....very thuroughly,even flashed a few flash kernals he added that were for the other models similar to ours in great hopes of getting this to work.
This is what you get....it does take about 30 minutes to generate the text file to send in
Oh magda623....are you there?
we are awaiting your reply.
Im sure there is hundreds of us that would like to have this running on our phones...please let us know how to make it work.
Ok ok i give up on magda to humor us on how it works on his device.
I urge everyone to use the link a couple posts up and dl the mobile odin lite,run it and send your mobileodin.txt to chainfire and plead with him to include our device....im sure he will eventually get our message.....after all he does say he is only working on samsung devices at this time.
****wouldnt it be awsome to flash back and forth from mtd to bml roms without ever having hook up to your comp!!!****
Lol am i seriously the only one that finds this to be something that would make life amazing on the sgs4g?
new ealsjur
Mobile ODIN did not recognize the device when I was on CM9
Something about flashing the phone from the phones makes me uneasy. What if you need to repartition using a pit or something, while the phone is on and in use.
Btw short I sent a dump file a long time ago and have been retrying ever since with no luck so far, maybe I'll make another dump today after work
Sent from my SGH-T959V using Tapatalk 2
getochkn said:
Something about flashing the phone from the phones makes me uneasy...
Click to expand...
Click to collapse
I've stayed out of this one for just that reason. It's bad enough to be messing with the underpinnings of an OS when you don't have true single-user mode, a "safe" boot, kernel, and emergency filesystem available, nor alternate boot media if things go really bad. Doing all that from user-land while the system is running all services sounds like just asking for trouble.
You can do most of what you are asking for in Recovery
Flash kernel/boot/recovery
Flash /system
Flash other run-time partitions
Flash modem
If you can't get into recovery, are you really able to run some Android program?
I'm not really seeing the need for this, except for people who have broken their USB connector and can't connect to a computer. Even then, when would you need ODIN? When things are so hozed up you need to start from scratch, yes, but if you have a broken USB, what are you doing flashing risky things?
If someone can show what this would do that you can't do in recovery, as well as a meaningful use case for it, I'll mull over how to do it. Basically, if an app can do it, a script in recovery sure should be able to as well.
I tend to think the reason we dont have support is because of the quirkiness of this phone.
I agree eollie ....I gave up on this a while ago...really it doesn't matter to me anyhow....I mostly thought it was a great idea.
I don't tend to have issues with flashing...or recovering.
And even if I did....I wouldn't be dumb enough to post here lmao.
Okay, so I know this phone doesn't exactly win the spec war, but it's awesome and would make a fantastic rooted phone. Unfortunately there isn't a forum here on XDA for the device (either because it's too new or there isn't a demand for it)
Do you guys think a forum will be made for this device? It'd be nice to at least have a place to say what root methods DON'T work (I've tried a few)
Thanks for the help, XDA rules!
I second this. I am planning on buying a new phone and after researching numerous phones out there based on my tastes and constraints, I think this phone works very well (another is Samsung Galaxy Exhibit 2). One flaw that I heard is the amount of storage in this phone is around 4gb. Without a way to put apps on an external SD card (which I believe would require a custom ROM), the storage would probably fill up pretty quickly. So it'll be great if XDA opened a forum for this phone.
As a side note if anyone can point to other devices that fit my needs I would be grateful:
- Less than 4.2" screen (preferably 4").
- Android only
I don't have any financial constraints or any favorite companies.
Thanks!
What root method did you find worked? Did you try framaroot? Also have you found any Roms?
Sent from my SPH-D710VMUB using Tapatalk 2
bbradf44 said:
What root method did you find worked? Did you try framaroot? Also have you found any Roms?
Sent from my SPH-D710VMUB using Tapatalk 2
Click to expand...
Click to collapse
I used Motochopper, worked like a charm. make sure you have the LG Optimus f3 drivers on your computer.(found on LG website)
habitforming said:
I used Motochopper, worked like a charm. make sure you have the LG Optimus f3 drivers on your computer.(found on LG website)
Click to expand...
Click to collapse
Ratified. Motochopper worked flawlessly for me as well.
richardpwnsner said:
Ratified. Motochopper worked flawlessly for me as well.[/QUOT
Anyone find a tethering ap that works?
Click to expand...
Click to collapse
wolfu11 said:
richardpwnsner said:
Ratified. Motochopper worked flawlessly for me as well.[/QUOT
Anyone find a tethering ap that works?
Click to expand...
Click to collapse
Do tethering apps need to be phone specific? I don't have data, but I'll let you know if I come across one.
Click to expand...
Click to collapse
Bad news
I have created the recovery tree, and have created a recovery.img for this phone. ok now heres the bad news OUR lg optimus f3 has a stock 3.4 kernel with a locked bootloader. Even worse news is that 3.4 "locking" features a sha5 hash system for its image/partitions (recovery, boot, and bootloader). Even worse news there is no known (or atleast what i know or have heard) way to get around this. The phone will be forever locked until lg updates or allows said lock to be removed. I have flashed the recovery and have had no damage to my device but it just sticks at "unsecure recovery" and does a hard reset (factory restore) every time i try to play with it which is a huge flaw if you ask me.
I have hexedited the bootloader and found that there is indeed "juicy" strings within that may tell to a future unlock these strings being
-Device UnLock!, so Boot Success!!
-oem unlock
-ERROR: Could not do normal boot. Reverting to fastboot mode
Also these strings could just be defualt with all lg bootloaders meaning....there is no hope.
My phone is without a soul and I will never be buy lg again.
If anyone is able to get into fastboot
1. PM ME
2. run : fastboot oem unlock
Again root for this phone works great as long as you dont touch recovery, bootloader, or boot partitions
inyourface09 said:
I have created the recovery tree, and have created a recovery.img for this phone. ok now heres the bad news OUR lg optimus f3 has a stock 3.4 kernel with a locked bootloader. Even worse news is that 3.4 "locking" features a sha5 hash system for its image/partitions (recovery, boot, and bootloader). Even worse news there is no known (or atleast what i know or have heard) way to get around this. The phone will be forever locked until lg updates or allows said lock to be removed. I have flashed the recovery and have had no damage to my device but it just sticks at "unsecure recovery" and does a hard reset (factory restore) every time i try to play with it which is a huge flaw if you ask me.
I have hexedited the bootloader and found that there is indeed "juicy" strings within that may tell to a future unlock these strings being
-Device UnLock!, so Boot Success!!
-oem unlock
-ERROR: Could not do normal boot. Reverting to fastboot mode
Also these strings could just be defualt with all lg bootloaders meaning....there is no hope.
My phone is without a soul and I will never be buy lg again.
If anyone is able to get into fastboot
1. PM ME
2. run : fastboot oem unlock
Again root for this phone works great as long as you dont touch recovery, bootloader, or boot partitions
Click to expand...
Click to collapse
Ugh. Thanks for the work. This is bad news indeed. I'll keep poking around and let you know if I find anything.
richardpwnsner said:
Ugh. Thanks for the work. This is bad news indeed. I'll keep poking around and let you know if I find anything.
Click to expand...
Click to collapse
Out of curiosity, any chance Loki would work? I'd be willing to give it a go if there's a decent chance—still within the 14 day exchange window .
Will motochopper work on any carrier version of this phone? Thanks!
jjfad said:
Will motochopper work on any carrier version of this phone? Thanks!
Click to expand...
Click to collapse
I've seen confirmations on three carriers (can't remember which ones off the top of my head, sorry [edit-well, T-Mobile and Virgin Mobile come to mind now]), so I'd assume the answer is yes. Regardless, I have yet to see anyone complain about adverse affects, so no reason not to try (though, grain of salt—I'm brand new to android).
For anyone that has this, how are the antennas on this phone?
I just ordered one from tmo and am hoping to get better reception at my house than from my Samsung or HTC.
Sent from my SGH-T999 using xda app-developers app
Steve5400 said:
For anyone that has this, how are the antennas on this phone?
I just ordered one from tmo and am hoping to get better reception at my house than from my Samsung or HTC.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
They seem better and with WIFI calling built in the phone hasn't skipped a beat.
Check my way!
http://forum.xda-developers.com/showthread.php?t=2420178&highlight=rooting+lg+optimus+f3
I failed rooting my phone with Windows system, maybe cause I'm not familiar with the process or I was just to lazy, but it does work if you use motochopper. Try looking it up youtube. You could try my method, it should work on Jellybean 4.1.2!
richardpwnsner said:
Out of curiosity, any chance Loki would work? I'd be willing to give it a go if there's a decent chance—still within the 14 day exchange window .
Click to expand...
Click to collapse
BAHAHA me to man i think im down to 10 days. Im trying to get some attention but i need someone who knows little endian, and their way around bootloaders. Id be willing to donate to someone who can help me out, also to support the other 3 variants (if the aboot differs).
I have a recovery created also and a device tree (needs gpio support for kernel).
And to awnser your question, yes loki will work IF i can get the needed values so that when recovery/boot is read into memory that it overwrites the security check feature in aboot. If the wrong values are give you may end up with a brick (very slim chance)
My return window just closed . If it helps, you can pull the open source from LG's website and merge it with the android source. I also discovered an even easier solution: set up the LG Sync application, and select the "upgrade recovery option". Then, when it begins downloading, remove your phone, set Windows (or your relevant OS) to show hidden files and folders, and go the the Program Data folder. There should be something like "PHONEAX" under the LG Electronics folder that will contain the full stock kdz file when the download is complete.
It's really kind of surprising that there's absolutely no dev love out there for the F3. I suppose it's because the phone is entry level, but it's really not that bad but for the storage. I got it as a gift, so no complaints here—of course, if anyone wants to donate a Note or Galaxy gratis, I suppose I'd be willing to switch .
I had a Galaxy S4 from Verizon. I switched to T-Mobile Because believe it or not the network is stronger where I work. Also, there pricing on plans cannot be beat. But, I digress. The Galaxy S4 being a Verizon device never really functioned the way it was supposed to on T-Mobiles network. It was unlocked however was still useless for 4G LTE and while I could do better than edge in some places, those places were few and far between. I started to assess what it is I actually used my phone for these days. I'm not into modding with custom ROMS and kernels anymore and I'm not much of a multi-tasker either so I decided that I did not need the super power device anymore. The specs on this phone are perfect for what I need my phone to do. Its been a long time since I have gone beyond rooting to remove bloat and tether. I agree that the storage on this sucks. I don't understand why there are any devices anymore that come with less than 32gb internal. storage is the cheapest thing that can be added to a device and its not as though it uses much physical space. other than the storage I will say that I am impressed with the quality of this device and I don't know that I would even put this as low as "entry level device." I would say its more of a mid-grade device. I am also happy with the reception on this device and its nice to have a compact phone again that actually fits comfortably in my hand and on my belt.
yutzyscott said:
I had a Galaxy S4 from Verizon. I switched to T-Mobile Because believe it or not the network is stronger where I work. Also, there pricing on plans cannot be beat. But, I digress. The Galaxy S4 being a Verizon device never really functioned the way it was supposed to on T-Mobiles network. It was unlocked however was still useless for 4G LTE and while I could do better than edge in some places, those places were few and far between. I started to assess what it is I actually used my phone for these days. I'm not into modding with custom ROMS and kernels anymore and I'm not much of a multi-tasker either so I decided that I did not need the super power device anymore. The specs on this phone are perfect for what I need my phone to do. Its been a long time since I have gone beyond rooting to remove bloat and tether. I agree that the storage on this sucks. I don't understand why there are any devices anymore that come with less than 32gb internal. storage is the cheapest thing that can be added to a device and its not as though it uses much physical space. other than the storage I will say that I am impressed with the quality of this device and I don't know that I would even put this as low as "entry level device." I would say its more of a mid-grade device. I am also happy with the reception on this device and its nice to have a compact phone again that actually fits comfortably in my hand and on my belt.
Click to expand...
Click to collapse
No argument here. I like it well enough, but I'm (1) a closet geek; and (2) a heavy multitasker, so given the option I'd prefer something with more screen space (I just graduated from law school, so I do a lot of reading on the go). As a phone, however, you really couldn't ask for more—the size otherwise pretty much perfect, it's relatively snappy with most applications, and once debloated the stock launcher is pretty good.
That being said, the second I see a safe way to deal with the bootloader pop up, I'm diving in, no question .
Decided to share my home screens.
Sent from my LG-P659 using XDA Premium 4 mobile app