Related
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
I was wondering if anyone had any info on the status of roms for the Behold II. I just got one, used but in very good shape, and I am trying to get it to work better. I am fairly sure these phones were pretty popular, and I can't believe they were (almost) completely ignored. I found a pretty nice clean android 1.6 rom that I threw on it, but it has no vibrate.
Does anyone know of any stable gingerbread roms for this phone? If not, anyone know how to get vibration to work? Is there anyone out there willing to work on this phone at all?
Or can anyone point me in the direction of some information on taking the rom apart and figuring out how to get the vibration working? Basically I need to find out how to take apart a rom, then figure out how to get vibration working properly. It's driving me nuts that the phone doesn't vibrate when I get calls/texts.
Isn't that Donut? *throws up*
Couldn't find any ROMs above 1.6 with some googling. Its also likely that you would not be able to fix the vibrate issue, if the Dev couldn't. If you want to "take the ROM apart," just take the .zip file and unzip it.
But I recommend getting a new phone.
Sent from my Nexus 4 using xda premium
It is indeed Donut. That's why I wanted to try and find a gingerbread rom or figure out how to make my own.
I unzipped the rom and dug around in there. I found some other thread on these forums about vibration and the symlinks and vibrate.ko. I checked in init.rc (on the phone) and found some lines about inserting modules relating to VibeTonez and the module "vtmdrv.ko" but I don't know if it is commented properly or turned on or symlinked or whatever. I see nothing about an actual vibrate.ko or anything.
How do I check my updater-script for the correct symlink?
I found this thread that has given me some interesting information: http://forum.xda-developers.com/showthread.php?t=1946614
and also this one: http://forum.xda-developers.com/showthread.php?t=1405366
Thanks for the interest! Unfortunately, I cannot just get a new phone. I am basically stuck with this one for the foreseeable future.
nookle said:
It is indeed Donut. That's why I wanted to try and find a gingerbread rom or figure out how to make my own.
I unzipped the rom and dug around in there. I found some other thread on these forums about vibration and the symlinks and vibrate.ko. I checked in init.rc (on the phone) and found some lines about inserting modules relating to VibeTonez and the module "vtmdrv.ko" but I don't know if it is commented properly or turned on or symlinked or whatever. I see nothing about an actual vibrate.ko or anything.
How do I check my updater-script for the correct symlink?
I found this thread that has given me some interesting information: http://forum.xda-developers.com/showthread.php?t=1946614
and also this one: http://forum.xda-developers.com/showthread.php?t=1405366
Thanks for the interest! Unfortunately, I cannot just get a new phone. I am basically stuck with this one for the foreseeable future.
Click to expand...
Click to collapse
No prob. Always interested in the legacy devices.
I wouldn't try to fix the vibrate, the developer himself states it will likely never be fixed (http://androidforums.com/behold-2-all-things-root/54769-port-galaxy-1-6-behold-2-final.html). I didn't read into the thread, but usually some user asks why vibrate doesn't work, dev explains, etc. You don't know if the problem with the ROM is the same as the issues found in the threads you searched.
If you want Gingerbread, it looks like the device is pretty much dead, however you can port CM7 from a similar device. It would be quite a chunk of work though.
Sent from my DROID2 using xda premium
Yeah, I have been going over all those threads that have that guy's roms. He made a few of them for this phone, and I am trying to find one that is better. Or the best of them.
I think I may have found a pretty major bug in the one I have, though. I got a call, I didn't want to answer it, and I hit the volume down button to silence the ringer, but it force closed android.phone.com and dropped the call. That wasn't cool.
I am also (kind of half-heartedly) pursuing creating my own rom from scratch. It's quite daunting, but I have a lot of time for the next week or so. My sister is having a complicated pregnancy so I am spending a lot of time at the hospital. There are plenty of guides and tutorials for beginners, so I am reading those and trying to figure things out.
Or I can figure out how to work on the rom this guy made, that would make life much easier.
nookle said:
Yeah, I have been going over all those threads that have that guy's roms. He made a few of them for this phone, and I am trying to find one that is better. Or the best of them.
I think I may have found a pretty major bug in the one I have, though. I got a call, I didn't want to answer it, and I hit the volume down button to silence the ringer, but it force closed android.phone.com and dropped the call. That wasn't cool.
I am also (kind of half-heartedly) pursuing creating my own rom from scratch. It's quite daunting, but I have a lot of time for the next week or so. My sister is having a complicated pregnancy so I am spending a lot of time at the hospital. There are plenty of guides and tutorials for beginners, so I am reading those and trying to figure things out.
Or I can figure out how to work on the rom this guy made, that would make life much easier.
Click to expand...
Click to collapse
I wouldn't try to make a ROM from scratch. A better thing to do would be to port. Basically find a ROM made for a phone with similar internals (type of CPU and RAM) and port the ROM. Much easier than making a ROM from scratch which requires knowledge of a few computer languages (mainly java). There are a few porting guides available on the forum.. Lemme find a link
Sent from my Nexus 4 using xda premium
Hey, thanks for your help! It's much appreciated! And believe me, if I could get a new phone I would. This phone is on my parent's plan, and only used for calling and texting family. I can't use data or anything. At this point it's more for the sake of learning about how to build an android operating system than anything else. I just want a nice, stable, useful phone that is better than the old school flip phones (of which I have had quite a few over the years).
Once again no prob. I used a legacy device just last year but it had quite some development so all I had to do was flash Roms lol.
Anyways this is how you compile GB
http://forum.xda-developers.com/showthread.php?t=1183832
And this is how you port. I would port from a similar device like the My touch 3g
http://forum.xda-developers.com/showthread.php?t=1598713
Sent from my Nexus 4 using xda premium
Haha yeah I am in the same boat with my nook. I have been following the devs over in the nook sub-forum for a couple years now. I have had several iterations of gingerbread, a couple of ics, and now a few of jelly bean. I am used to just slamming the rom zip on the sd card and booting into recovery and flashing it over.
For this phone I had to do odin, which was a new experience for me. Went pretty painless, and I figured it out. I prefer the recovery method over odin.
I have one question about the second link, about porting. It says in the first post that if you don't have gb already compiled for your (my)device that guide is useless for you (me). Is that what the first link is for? Compiling specifically for my device? What if my device is not supported at all? Do I just pick a somewhat similar phone, compile, port, make a flashable rom, and put it on the phone and hope it doesn't brick it?
Yep thats what the first link is for. Don't compile and port for a different device, that is a sure way to brick your phone.
Is your device not supported at all? Usually legacy devices are since back then (lol) there weren't a whole ton of Android phones
Sent from my Nexus 4 using xda premium
I don't know if my device is supported or not. I have not got to that part in the guide yet. I will report back if it is or isn't.
Sorry for not getting back earlier, I've been real busy the past week or two.
I finally got ubuntu set up on a computer, and was following the first guide and ran into a few problems.
First, I wasn't able to install all the required packages. If you want to know what ones they are I wrote them down. Not sure how essential they are in the grand scheme, but they weren't available.
Second, I tried to install java and ran into a problem adding the repos for it. The second one, for src, would not work at all. So I went on sun's or oracle's website and downloaded the linux package and installed it. But apparently it didn't work because all I get after trying to lunch are lots of these:
Code:
/bin/bash: java: command not found
Basically anywhere it tries to use java I get those messages. Eventually it gives up and says I have
Code:
version: /bin/bash: java: command not found
and I should have
Code:
version 1.6
Third, after I issue
Code:
source build/envsetup.sh
I see it includes some devices, like htc passion and samsung crespo4g and samsung crespo. Is this normal?
Fourth, When I do lunch I get five options
Code:
1. generic-eng
2. simulator
3. full_passion-userdebug
4. full_crespo4g-userdebug
5. full_crespo-userdebug
Should I just pick generic-eng?
I will be out of town all week for work, and won't have access to the computer I am doing all this on. For the life of me I cannot get unbuntu to install on my laptop. Never did like ubuntu, always favored fedora.
Anywho, thanks for any suggestions.
I have the T959v android phone, which I found out is a bit more complicated than my Samsung Vibrant.
I am running the gingerbread kernel after using Kies.
I have finally successfully flashed the T959v using Heimdoll following this guide. http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Super User has been installed using SuperOneClick.
After struggling with it and reading on some sites it's possible and some sites it's not possible, I've come to the conclusion that Rom Manager is not a good idea to use, to install a Rom on my particular phone.
I want to install this Rom here: http://forum.xda-developers.com/showthread.php?t=1402966
However I reviewed the instructions and found I was lost on some parts.
I know how to get to recovery mode (with the phone turned off, hold down volume up and down and the power button)
However, here's where I get lost:
6. Perform Voodoo -> Disable Lagfix.
I do not have this option, likely because I'm missing voodoo or some sort of app. I've tried googling this and figuring out what it is, but I don't even know what a CWM is.
I haven't tried (since I'm atleast smart enough to review information before I start following them, lest I get myself stuck somewhere and unable to back out of). However I believe I can get as far as Step 5.
Unfortuantely I can't get any further.
The only apps I have installed (besides the annoying bloatware on the phone) are the ones I listed above.
This is my first time flashing a phone or doing any of the above, previously my friend did it for me.
So I apologize for whatever Incompetence I may have, however if you can simplify instructions I'm pretty good at following them.
The hard part is that I don't know how to do a lot of the instructions.
Is there a video? Perhaps a guide with pictures that includes all the software I need and how to install that software?
I'm sorry for the questions, I hope someone can help. This has been a long and frustrating process but I'm determined to finish it.
Thank you in advance.
Ah also this: "Must have pre-installed kernel with clockwork recovery!"
I cannot do this because when I try and use clockwork recovery it says it cannot support my phone.
It gives me a list of 4 devices, none of which are my phone.
Then I click on "My device is not listed" and it states the T959v is not supported.
I'm really sorry for all the questions.
Not only does this app look nice, and sound nice due to hardware acceleration. Above all it gets rid of that bloatware crap from T-mobile.
I look forward to giving this app a try.
Hello my friend i know how excited you are when it come's to flashing, installing, removing apps on your phone, but before you do any harm to your phone maybe
consider reading this http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G before going further. it save's you a lot of time and headache plus you can avoid
flaming from other people here. and also try to use the search bar just i case you have further question's..
I advice you to take some time to read first on what do you want to your phone before doing anything.. don't be in a hurry we have tons of great roms in here..
Do not use clockwork manager...it is not for this device!
If you have super user ur rooted and good to go ...i would suggest you play around with the gingerbread roms for a spell before going to icecream sandwich roms,just so you get a feel for flashing on this device.....i too came from the vibrant and dearly miss it.
This phone is far from a vibrant but is coming along.
Feel free to pm me.....I may be a bit slow on replies since I'm working 7/12's 3rd shift.
Thank you both so much for your replies.
Warren I am checking that link out right now. Thanks
Shortbus, I miss my Vibrant too.
Technically speaking my Vibrant is still usable, but ever since I dropped it and cracked the screen it seems to have drastically slowed down (and the screen is annoying with all the cracks too).
Sad day for me.
I still want to try and get that Rom I had posted above working, as I doubt I'll move to another rom anytime after that. But I'll try and learn more about it using the link you gave me Warren. It'll probably take me several days ~_~
Shortbus I may email you with questions I come across from time to time if that's ok
Squeezitgirdle said:
Thank you both so much for your replies.
Warren I am checking that link out right now. Thanks
Shortbus, I miss my Vibrant too.
Technically speaking my Vibrant is still usable, but ever since I dropped it and cracked the screen it seems to have drastically slowed down (and the screen is annoying with all the cracks too).
Sad day for me.
I still want to try and get that Rom I had posted above working, as I doubt I'll move to another rom anytime after that. But I'll try and learn more about it using the link you gave me Warren. It'll probably take me several days ~_~
Shortbus I may email you with questions I come across from time to time if that's ok
Click to expand...
Click to collapse
If you want to install Valhalla Final - read the guide in the first link of my signature and begin where applicable.
I don't mind.
Flashing roms on this device is easy once you realize its not the vibrant lol.
Like the vibrant....this thing is near impossible to brick,....just a lil bit more complicated than the vib.....till you get to understand it.
lumin30 said:
If you want to install Valhalla Final - read the guide in the first link of my signature and begin where applicable.
Click to expand...
Click to collapse
Ah, so I should switch to Froyo instead of Gingerbread from the looks of it.
I'll get right on that I'm going to try following your guide now
edit: I saw that you switched to Gingerbread, jumped too far ahead of myself.
I'm getting pretty far along in the guide, I'm now at the part where I am about to install the rom.
I love that you guys respond so quickly too.
In the process of using Heimdall I ran into so many issues but was (slowly) able to work through them and figure them out.
It's nice to know I can come here if I have a quick question.
I'm not much help with heimdall....I use gremlin remover,its a one click Odin program....serves the same purpose....to bring you to a rooted stock state.
Alright so let me start off by saying that I have never had so much hell rooting and putting a custom Rom onto a phone. I am also a bit disappointed in xda as non of the articles were of much help, they were all broken up and I ran into trouble at literally every step. The easiest part was rooting the phone with ioroot, but finding it actually wasn't that easy because most of the tutorials I found from the start kept having me use other methods and none of them worked.
Second once I performed this step and had everything installed I realized that in order to use my wifi hotspot, I was going to need a custom rom. this was of course after trying dozens of worthless hotspot apps in the store, none of which worked. So I started trying to put a custom recovery on the phone, this was by far the hardest part, I tried and scoured the internet for 3 days, I swear to god I read every article and tried every method out there....the new ATT LG G2's however have a lock on the recovery to prevent people from doing this, I found it strange that none of these articles written based on 4.4.2 thought to mention that an exploit has not yet been found. Finally I ran across an article where I learned of this and was told to downgrade, so I downloaded SuperSport & big fau LG G2 D800 Flash stock. Thinking that this rom was going to unlock the recovery because it said it would, I ran through the process.
This however, was not the case and it didn't help, the whole time I was convinced that this had unlocked my recovery, I continued to try every tutorial on installing a recovery onto this device, the AT&T LG G2 kitkat 4.4.2 (D80020c), which btw is a week old from the date of this post. I like a lot of other people, will have this phone and be looking to unlock, root, install custom recovery, and install custom rom. For this I would like to figure out a few things and hopefully if y'all help me figure this out, I can include fixes for it in the next article that I write, which will explain how I successfully put a custom rom on my AT&T from start to finish. I will also include in this article what could go wrong and how to fix it, too many articles are written without taking into consideration the possibilities of what could go wrong.
It took me three solid days of scouring the internet to get a custom Rom on my phone, running through problems at every step I still have a few questions. After downgrading from 4.4.2 to 4.2.2 my recovery was broke, thankfully I was able to fix this using flashify in the app store. I then installed Cyanogen Mod 10 (cm-10.2.0-d802.zip). and installed it through recovery, when I rebooted I was presented with a fastboot which would do crap when I would plug the usb into my computer...I never figured out what the problem was for this, but I ended up trying a version of CM 10 which was released for the LG G2 D80010d that I downgraded too, the tethering doesn't work...no big deal, but the problem is when I set WiFi hotspot up and connect, on my computer I get SSL error's, my computer completely refuses to let my connect to facebook or google, saying that the connection is insecure, it won't let me grab any kind of certificate and I can't find a solution online. I have tried rebooting both the computer and phone, I don't get these errors on the WiFi at the gas station.
In the above paragraph, I stated the two problems I couldn't really figure out, I haven't tried to install any other custom roms, but I will try that today, I have to save my bandwidth on my phone so I will walk down to the truck stop and download one, ps I had to flash my phone back to stock about 5 times before I finally figured out I needed to downgrade it, then I had to do it 2 more times.
If y'all take the time to read this and help me, then I will take the time to write a new and working article describing how to do it from start to finish and it will be written with explicit detail on every problem I came across and how I fixed it.
Figured out how to mix the firmware
Alright, so I was reading through a few more articles and I ran across this link, which will allow you to upgrade back to D80020c, but without loosing the stock recovery. I'm going to have to wait till later today to give it a try though, because the internet at the truck stop is to slow to download something of that size.
J0hnC0nn3r said:
Alright so let me start off by saying that I have never had so much hell rooting and putting a custom Rom onto a phone. I am also a bit disappointed in xda as non of the articles were of much help, they were all broken up and I ran into trouble at literally every step. The easiest part was rooting the phone with ioroot, but finding it actually wasn't that easy because most of the tutorials I found from the start kept having me use other methods and none of them worked.
Second once I performed this step and had everything installed I realized that in order to use my wifi hotspot, I was going to need a custom rom. this was of course after trying dozens of worthless hotspot apps in the store, none of which worked. So I started trying to put a custom recovery on the phone, this was by far the hardest part, I tried and scoured the internet for 3 days, I swear to god I read every article and tried every method out there....the new ATT LG G2's however have a lock on the recovery to prevent people from doing this, I found it strange that none of these articles written based on 4.4.2 thought to mention that an exploit has not yet been found. Finally I ran across an article where I learned of this and was told to downgrade, so I downloaded SuperSport & big fau LG G2 D800 Flash stock. Thinking that this rom was going to unlock the recovery because it said it would, I ran through the process.
This however, was not the case and it didn't help, the whole time I was convinced that this had unlocked my recovery, I continued to try every tutorial on installing a recovery onto this device, the AT&T LG G2 kitkat 4.4.2 (D80020c), which btw is a week old from the date of this post. I like a lot of other people, will have this phone and be looking to unlock, root, install custom recovery, and install custom rom. For this I would like to figure out a few things and hopefully if y'all help me figure this out, I can include fixes for it in the next article that I write, which will explain how I successfully put a custom rom on my AT&T from start to finish. I will also include in this article what could go wrong and how to fix it, too many articles are written without taking into consideration the possibilities of what could go wrong.
It took me three solid days of scouring the internet to get a custom Rom on my phone, running through problems at every step I still have a few questions. After downgrading from 4.4.2 to 4.2.2 my recovery was broke, thankfully I was able to fix this using flashify in the app store. I then installed Cyanogen Mod 10 (cm-10.2.0-d802.zip). and installed it through recovery, when I rebooted I was presented with a fastboot which would do crap when I would plug the usb into my computer...I never figured out what the problem was for this, but I ended up trying a version of CM 10 which was released for the LG G2 D80010d that I downgraded too, the tethering doesn't work...no big deal, but the problem is when I set WiFi hotspot up and connect, on my computer I get SSL error's, my computer completely refuses to let my connect to facebook or google, saying that the connection is insecure, it won't let me grab any kind of certificate and I can't find a solution online. I have tried rebooting both the computer and phone, I don't get these errors on the WiFi at the gas station.
In the above paragraph, I stated the two problems I couldn't really figure out, I haven't tried to install any other custom roms, but I will try that today, I have to save my bandwidth on my phone so I will walk down to the truck stop and download one, ps I had to flash my phone back to stock about 5 times before I finally figured out I needed to downgrade it, then I had to do it 2 more times.
If y'all take the time to read this and help me, then I will take the time to write a new and working article describing how to do it from start to finish and it will be written with explicit detail on every problem I came across and how I fixed it.
Click to expand...
Click to collapse
J0hnC0nn3r said:
Alright, so I was reading through a few more articles and I ran across this link, which will allow you to upgrade back to D80020c, but without loosing the stock recovery. I'm going to have to wait till later today to give it a try though, because the internet at the truck stop is to slow to download something of that size.
Click to expand...
Click to collapse
well first I want to clarify you on that week old part especially since we have had kitkat on d800 since about feb 27 in fact if you look at garys thread about kk with custom recovery which is originally from march 6(on 5th we figured out what needed to be done but on 6th they began rolling out) and also if you would have asked for assistance I could have helped to find all needed info on rooting and everything (I just don't spend a lot of time in the dedicated d800 thread) anyways as for 20c I've been on it since root was available(also on first day of release of 20c) and have been running garys rom since it was released and I love it but if you want tethering(I know a way to enable you just need a paid app) and there are already threads on doing things from start to finish http://forum.xda-developers.com/showthread.php?t=2633150
Thanks
XxZombiePikachu said:
well first I want to clarify you on that week old part especially since we have had kitkat on d800 since about feb 27 in fact if you look at garys thread about kk with custom recovery which is originally from march 6(on 5th we figured out what needed to be done but on 6th they began rolling out) and also if you would have asked for assistance I could have helped to find all needed info on rooting and everything (I just don't spend a lot of time in the dedicated d800 thread) anyways as for 20c I've been on it since root was available(also on first day of release of 20c) and have been running garys rom since it was released and I love it but if you want tethering(I know a way to enable you just need a paid app) and there are already threads on doing things from start to finish http://forum.xda-developers.com/showthread.php?t=2633150
Click to expand...
Click to collapse
Sorry, I didn't mean to sound like a ****. I just had a really hard time finding a complete walkthrough on this, I ended up taking bits and pieces from different tutorials and it seemed that most of them only covered one aspect of the process, like recovery, or if they covered the whole walkthrough they would either leave something out or I would recieve errors, such as the loki error, and the original adb not detecting my device. I had to download an adb from an alternative source because the official adb wouldn't detect my device, after trying everything but it didn't bother me because I figured it out and thanks for your response, really appreciated, I will check that out....How many mods have you tried and what features do you like about them? I liked the ideal of the CM 11 for the 4.4.2 because it boasted the porting of pretty much every feature that comes on the LG G2 4.4.2...Like the double tap to unlock and such....I will check out Gary's mod and see what it offers, thanks again
I would just like to start out by saying congrats on getting your device to where you've wanted it - I do agree that the G2 is a special case right now considering the lack of development and spotty information available for development.
With that being said...
There is a really good reason why the site was named XDA-"Developers" and not XDA-"Newbs". The primary focus of these forums is for the purpose of developers engaging one another and sharing their discoveries with the community. There are some really great developers here that take a LOT of their own PERSONAL time to create the stunning softwares, hacks, themes, etc. that often ultimately get freely distributed to the public. Take note that 99% of these threads start off with "Use my software and instructions with NO expectation of support or warranty" or "Flash at your own risk".
These folks give so much to the community and often ask for little or nothing in return. While the information right now is pretty sparse and scattered, do you think you could have achieved what you did without it? The mere fact that you have a custom ROM, root and recovery is a testament to the hard work of the folks here who are giving their own time up in the name of furthering development. Our G2s, while stellar devices, are the outliers in the world right now because they are not in the hands of the masses. How many people have looked at you and asked "is that the new Galaxy??" I believe in time, someone with way more time and Android know-how than I, will deliver something mind-blowing to the XDA community for this device. Just be patient and realize that the majority of Smartphone users right now have a GNote, S4, or HTC something-or-another.
Finally, re-read your post and try to hear the tone you delivered. You sound upset that the XDA community hasn't delivered you an easy root/recovery package on a silver platter with all the trimmings. Again - this forum is for developers. What they choose to share with the rest of us as non-developers is totally up to them. They also tend to share more when the support they receive is positive. Long rants about your disappointment in the community over how you had a hard time getting what you wanted on your device - well you catch more flies with honey...
Cliffs notes? Hug a developer, and say thank you for what you've managed to accomplish with your device. Without the info posted around here, we'd all be living with stock ROMs and unrooted, bland G2s. If you are unhappy with your own personal experiences with getting to where you are right now... Well, you obviously know where the "new post" button is. Become a contributor, tell us how YOU did it and give back to the community. If you only rant about your disappointments, then you aren't really making anything better for anyone around here - in fact it only serves to clutter up an already fragmented knowledge base.
From one long winded poster to another - good luck in your ventures with the G2. It has served me well so far and I believe it will continue to do so for quite a while.
Regards.
Sent from my LG-D800 using Tapatalk
tethering
If tethering is all you wanted. I would have done it the easy way. You can unlock WiFi tether by trying to turn it on, then when it fails use sqlite editor from the market to go in and change the provisioning status to 0 in the database file. Sqlite costs 2 bucks, it would be worth that to not have to go through all that. I never thought I would own a phone without a custom Rom, but so far I'm still stock on the lg g2 it's that good. Most annoyances can be fixed as long you have root.
Krayziepop said:
I would just like to start out by saying congrats on getting your device to where you've wanted it - I do agree that the G2 is a special case right now considering the lack of development and spotty information available for development.
With that being said...
There is a really good reason why the site was named XDA-"Developers" and not XDA-"Newbs". The primary focus of these forums is for the purpose of developers engaging one another and sharing their discoveries with the community. There are some really great developers here that take a LOT of their own PERSONAL time to create the stunning softwares, hacks, themes, etc. that often ultimately get freely distributed to the public. Take note that 99% of these threads start off with "Use my software and instructions with NO expectation of support or warranty" or "Flash at your own risk".
These folks give so much to the community and often ask for little or nothing in return. While the information right now is pretty sparse and scattered, do you think you could have achieved what you did without it? The mere fact that you have a custom ROM, root and recovery is a testament to the hard work of the folks here who are giving their own time up in the name of furthering development. Our G2s, while stellar devices, are the outliers in the world right now because they are not in the hands of the masses. How many people have looked at you and asked "is that the new Galaxy??" I believe in time, someone with way more time and Android know-how than I, will deliver something mind-blowing to the XDA community for this device. Just be patient and realize that the majority of Smartphone users right now have a GNote, S4, or HTC something-or-another.
Finally, re-read your post and try to hear the tone you delivered. You sound upset that the XDA community hasn't delivered you an easy root/recovery package on a silver platter with all the trimmings. Again - this forum is for developers. What they choose to share with the rest of us as non-developers is totally up to them. They also tend to share more when the support they receive is positive. Long rants about your disappointment in the community over how you had a hard time getting what you wanted on your device - well you catch more flies with honey...
Cliffs notes? Hug a developer, and say thank you for what you've managed to accomplish with your device. Without the info posted around here, we'd all be living with stock ROMs and unrooted, bland G2s. If you are unhappy with your own personal experiences with getting to where you are right now... Well, you obviously know where the "new post" button is. Become a contributor, tell us how YOU did it and give back to the community. If you only rant about your disappointments, then you aren't really making anything better for anyone around here - in fact it only serves to clutter up an already fragmented knowledge base.
From one long winded poster to another - good luck in your ventures with the G2. It has served me well so far and I believe it will continue to do so for quite a while.
Regards.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Nothing new to add to this but I've never had so much fun reading through a response that utterly fleeced another person for going full on ungrateful douche. Kudos sir. Lol
Sent from my LG-D800 using XDA Premium 4 mobile app
For me this was the easiest phone to root and flash recovery. Used ioroot for root and freegee to install custom recovery. That's when I was using jelly bean now I'm on stock kit Kat
Sent from my LG-D800 using xda app-developers app
Wow, I'm sorta surprised there's not a USCC-specific thread anywhere yet...unless I just missed it, like I could well have.
Oh well, just thought it'd be nice to have a thread here at XDA, especially since it's so hard to find much of anything about USCC-branded phones in general anyway.
As far as my experience so far, I can't report any real issues beyond the usual so-so signal strength that I've experienced on every US Cellular phone me or my wife have owned ever since moving to my current location in town (yet it was fine at our old house just a few blocks over!). In the six years or so I've had USC, I've never found their phones being notably loaded down in bloatware, and nor is this one, so that's nice I guess. I was hoping I'd find some unlikely, overlooked USCC-specific perk like an unlocked bootloader on their models, but I don't see that happenin'... siiigh.
As for the phone itself independent of US Cellular, eh, I'm no power user, I'm probably not the dude who should make too many hardware-based critiques because the thing's more than powerful enough to ably do anything I'll ever need a phone to do. I will say I briefly owned an S6 Edge (briefly being because it was stolen) and I can't say the S7 seems like a huge upgrade to me, not one worth full retail anyway, but obviously it's a damn nice phone anyhow. (...But I went from my stolen fancy S6E down to an old, cheap Motorola Razr M (aka Electrify M) for a little over a year before getting my S7E and I was, for the most part, totally satisfied with the Motorola's performance despite the huge discrepancy in horsepower, so what the hell do I know?)
So yeah, bring on your USCC-specific guides, thoughts, questions, complaints, opinions, etc etc!
So I'll kick things off with a bit of root discussion/issues...
I rooted my phone maybe a week or so after getting it back in July, taking the chance against my better instincts that the instructions found over in this Verizon thread would work out for USCC phones too. Much to my surprise, not only did it work, I experienced almost none of the many problems that the Verizon users kept encountering in the early weeks of that thread. Why that is, though, I still have no clue. I guess VZW's software is somehow different from USCC's in such a way that we simply weren't affected by whatever kept causing the boot loops, extreme battery-drainage and heat issues for those phones. (Mostly...)
I don't want to steal the work of thread-starter psouza4 or anyone else in that existing Verizon thread so I don't want to try and rewrite every full detail but for any future USCC S7/Edge owners who might wind up here, I guess I'll do a real basic rundown of exactly how I did mine (and also I'll do it so that maybe someone more versed in Android-tinkering than me can tell me where I may have gone wrong on certain steps). The files I used in my root/fix/debloat process are the ones listed in Bold below and all can be found on that thread - I'd link 'em directly here but I don't know how kosher that is - and what isn't there should be in the Play Store.
So, after disabling "Secure Startup" under Settings-->Lock Screen & Security (and ensuring I had the correct drivers and ADB working and such), I...
1). Flashed the Samsung_G935x_QC_Rooted_BOOT.TAR image using the Odin3_v3.12_PrinceComsy.zip variant. The Verizon thread reports that some AT&T users had recommended the Comsy version because they found it prevented boot issues that they were experiencing when flashing with the other "plain" version of Odin that was linked. As for me, I only used the PrinceComsy version because the plain version simply doesn't run on my computer for some reason. I have no idea what the difference is between the two versions, so I've got no idea if the Comsy version may be the better way to go for USCC users as well (or if it even makes a lick of difference for anyone really), but it works.
2). After successful flash and reboot, I installed SuperSU-v.2.76-S7QC.zip via the included root.bat file and waited for another reboot to finish. I can't recall if SuperSU prompted me to download a newer version of the "su" binary upon opening the now-installed SuperSu app (as the original thread indicated it might) or not, but I didn't and neither should you apparently. As of the original post in the other thread on 7/15/2016, the "2.76-S7QC" build was the most recent version for S7 models . Since that's been over a month ago, can anyone verify if the current 2.78 version of SuperSU works with S7s (and/or USCC phones), or if there's a 2.78"-S7QC" version specifically? (I'm guessing no and no, but I lost track of the Verizon thread a while back and haven't seen any specific reference to 2.78 working or not working...)
3). From there, I downloaded FlashFire (v051, I believe) and flashed the suggested S7_or_S7Edge_Fixes_Debloater_V15.zip file, which aims to, y'know, fix some stuff and debloat the thing. I didn't manually adjust any of the "fixes" applied by the patch, and many of the apps and services killed by the "debloater" part of the script don't even come on USCC-branded versions of the phone. The instructions in the thread go on to say that some users reported problems with a handful of the fixes - Lag issues, Wifi passwords refusing to save, "Unauthorized Actions" pop-ups, and problems with VoLTE icons (the last of which isn't relevant to USC really anyway). While it seemed like the majority of VZW/ATT/other-carrier users in the thread were experiencing at least one of these issues, I didn't. There was some lag, for sure, but sporadically, and the remaining steps mostly knocked it out and I didn't need to do anything extra.
4). Next I installed a couple, but not all (initially) of the programs/settings suggested in the separate . Amplify Premium 3.3.7 and L Speed 3.1.9.7 (though I updated to the current 3.1.9.8 Beta shortly thereafter with no ill effects). Now I thought I followed the thread's suggestions pretty much exactly for these two, but when I looked just now to verify, I found that I hadn't made quite a few of the recommended changes in Amplify after all. (Probably because many of them give warnings when adjusting that the other entries hadn't, and I figured I'd play it safe). Anyway, I went ahead just now and finished everything up so that it does follow that thread's suggestions - I'll report back on it if they seem to make a notable difference. Maybe worth noting here that not all of the recommended changes are valid on US Cellular phones, so no need to worry if you can't find a few of them. As for L-Speed, I did indeed have all of the thread's recommended settings for it set, except for one, "Storage IO Tweaks: Partition Remount - Enabled." Not sure why this wasn't set, guess I just didn't see it the first time. Anyway, I've enabled it now, and since it seems to be there for "giving more permissions to the SD card," it was probably irrelevant to me anyhow since I don't currently use one.
Now, the guide suggests installing Xposed when you do all of this, along with three more apps - Greenify, ForceDoze, and LeanDroid. I decided to hold off on all the above for a while when I did it, but I'd say it's plenty safe to do it all in one go if you choose to. By the time I got around to applying the L-Speed and Amplify settings and rebooting, I had been up and rooted for at least a couple hours altogether, enough to notice that I wasn't seeing the immediate disasters a lot of other posters were finding. The most common problem seemed to be bootloops and random resets, which I hadn't encountered (and still never have really, beyond a couple of unexplained reboots once or twice that had no noticeable effects other than mild annoyance). There were also a lot of complaints about some rather extreme-sounding overheating, terribly reduced battery life, and serious lag problems - these all appeared in some degree, but seemingly nowhere nearly as bad as what people were reporting from their VZW/etc-branded phones in the thread. Plus, after making the L-Speed/Amplify changes, the battery seemed to be holding up a bit better, the phone wasn't running as warm as it had been pre-tweaking, and the lag I had experienced had calmed down from "pretty minor but definitely kinda annoying" to mostly gone. I wondered why I was missing out or getting much milder versions of all the problems mentioned by others, but by that point in the thread people were beginning to suspect Xposed was the cause. Some reported their phones working well up until installing Xposed, after which they'd begin getting bootloops or other problems. Not wanting any of that headache, I decided to just wait it out a few days and see how it held up before risking the install.
The guide also suggests at this point to turn off Wifi Scanning, Bluetooth, Location and Location History. I left the Location stuff alone, but this all seems pretty optional. It's also suggested to turn off the AOD Clock, which I left alone at the time but later disabled (and am now having issues with, but more on that later). I don't think there's any need to do the recommended disabling of all animations in Developer Options either, at least for our phones. I've left those settings at their defaults and speed's been fine.
So, since I basically took a break at this point when I was actually doing all this the first time, I'll take a break here too before getting into the next stuff I did regarding debloating and how my now-rooted-but-not-yet-real-tweaked USCC phone would turn out to actually run over the next few days...
I'm looking for a firmware which has european languages any idea?
Any new news on root and roms for our phones?
HavING trouble unlocking bootloader and flashing custom rom.
Is this possible yet? I've achieved root, But failed to flash twrp or cm. Any help would be appreciated!
lugnut2099 said:
So I'll kick things off with a bit of root discussion/issues...
I rooted my phone maybe a week or so after getting it back in July, taking the chance against my better instincts that the instructions found over in this Verizon thread would work out for USCC phones too. Much to my surprise, not only did it work, I experienced almost none of the many problems that the Verizon users kept encountering in the early weeks of that thread. Why that is, though, I still have no clue. I guess VZW's software is somehow different from USCC's in such a way that we simply weren't affected by whatever kept causing the boot loops, extreme battery-drainage and heat issues for those phones. (Mostly...)
I don't want to steal the work of thread-starter psouza4 or anyone else in that existing Verizon thread so I don't want to try and rewrite every full detail but for any future USCC S7/Edge owners who might wind up here, I guess I'll do a real basic rundown of exactly how I did mine (and also I'll do it so that maybe someone more versed in Android-tinkering than me can tell me where I may have gone wrong on certain steps). The files I used in my root/fix/debloat process are the ones listed in Bold below and all can be found on that thread - I'd link 'em directly here but I don't know how kosher that is - and what isn't there should be in the Play Store.
So, after disabling "Secure Startup" under Settings-->Lock Screen & Security (and ensuring I had the correct drivers and ADB working and such), I...
1). Flashed the Samsung_G935x_QC_Rooted_BOOT.TAR image using the Odin3_v3.12_PrinceComsy.zip variant. The Verizon thread reports that some AT&T users had recommended the Comsy version because they found it prevented boot issues that they were experiencing when flashing with the other "plain" version of Odin that was linked. As for me, I only used the PrinceComsy version because the plain version simply doesn't run on my computer for some reason. I have no idea what the difference is between the two versions, so I've got no idea if the Comsy version may be the better way to go for USCC users as well (or if it even makes a lick of difference for anyone really), but it works.
2). After successful flash and reboot, I installed SuperSU-v.2.76-S7QC.zip via the included root.bat file and waited for another reboot to finish. I can't recall if SuperSU prompted me to download a newer version of the "su" binary upon opening the now-installed SuperSu app (as the original thread indicated it might) or not, but I didn't and neither should you apparently. As of the original post in the other thread on 7/15/2016, the "2.76-S7QC" build was the most recent version for S7 models . Since that's been over a month ago, can anyone verify if the current 2.78 version of SuperSU works with S7s (and/or USCC phones), or if there's a 2.78"-S7QC" version specifically? (I'm guessing no and no, but I lost track of the Verizon thread a while back and haven't seen any specific reference to 2.78 working or not working...)
3). From there, I downloaded FlashFire (v051, I believe) and flashed the suggested S7_or_S7Edge_Fixes_Debloater_V15.zip file, which aims to, y'know, fix some stuff and debloat the thing. I didn't manually adjust any of the "fixes" applied by the patch, and many of the apps and services killed by the "debloater" part of the script don't even come on USCC-branded versions of the phone. The instructions in the thread go on to say that some users reported problems with a handful of the fixes - Lag issues, Wifi passwords refusing to save, "Unauthorized Actions" pop-ups, and problems with VoLTE icons (the last of which isn't relevant to USC really anyway). While it seemed like the majority of VZW/ATT/other-carrier users in the thread were experiencing at least one of these issues, I didn't. There was some lag, for sure, but sporadically, and the remaining steps mostly knocked it out and I didn't need to do anything extra.
4). Next I installed a couple, but not all (initially) of the programs/settings suggested in the separate . Amplify Premium 3.3.7 and L Speed 3.1.9.7 (though I updated to the current 3.1.9.8 Beta shortly thereafter with no ill effects). Now I thought I followed the thread's suggestions pretty much exactly for these two, but when I looked just now to verify, I found that I hadn't made quite a few of the recommended changes in Amplify after all. (Probably because many of them give warnings when adjusting that the other entries hadn't, and I figured I'd play it safe). Anyway, I went ahead just now and finished everything up so that it does follow that thread's suggestions - I'll report back on it if they seem to make a notable difference. Maybe worth noting here that not all of the recommended changes are valid on US Cellular phones, so no need to worry if you can't find a few of them. As for L-Speed, I did indeed have all of the thread's recommended settings for it set, except for one, "Storage IO Tweaks: Partition Remount - Enabled." Not sure why this wasn't set, guess I just didn't see it the first time. Anyway, I've enabled it now, and since it seems to be there for "giving more permissions to the SD card," it was probably irrelevant to me anyhow since I don't currently use one.
Now, the guide suggests installing Xposed when you do all of this, along with three more apps - Greenify, ForceDoze, and LeanDroid. I decided to hold off on all the above for a while when I did it, but I'd say it's plenty safe to do it all in one go if you choose to. By the time I got around to applying the L-Speed and Amplify settings and rebooting, I had been up and rooted for at least a couple hours altogether, enough to notice that I wasn't seeing the immediate disasters a lot of other posters were finding. The most common problem seemed to be bootloops and random resets, which I hadn't encountered (and still never have really, beyond a couple of unexplained reboots once or twice that had no noticeable effects other than mild annoyance). There were also a lot of complaints about some rather extreme-sounding overheating, terribly reduced battery life, and serious lag problems - these all appeared in some degree, but seemingly nowhere nearly as bad as what people were reporting from their VZW/etc-branded phones in the thread. Plus, after making the L-Speed/Amplify changes, the battery seemed to be holding up a bit better, the phone wasn't running as warm as it had been pre-tweaking, and the lag I had experienced had calmed down from "pretty minor but definitely kinda annoying" to mostly gone. I wondered why I was missing out or getting much milder versions of all the problems mentioned by others, but by that point in the thread people were beginning to suspect Xposed was the cause. Some reported their phones working well up until installing Xposed, after which they'd begin getting bootloops or other problems. Not wanting any of that headache, I decided to just wait it out a few days and see how it held up before risking the install.
The guide also suggests at this point to turn off Wifi Scanning, Bluetooth, Location and Location History. I left the Location stuff alone, but this all seems pretty optional. It's also suggested to turn off the AOD Clock, which I left alone at the time but later disabled (and am now having issues with, but more on that later). I don't think there's any need to do the recommended disabling of all animations in Developer Options either, at least for our phones. I've left those settings at their defaults and speed's been fine.
So, since I basically took a break at this point when I was actually doing all this the first time, I'll take a break here too before getting into the next stuff I did regarding debloating and how my now-rooted-but-not-yet-real-tweaked USCC phone would turn out to actually run over the next few days...
Click to expand...
Click to collapse
Any updates on how this is running on USCC devices.
It's running beautifully for me. I haven't went through the entire guide for the improvements with the extra apps, but root and xposed are perfect. I am using the ForcedDoze app and it does help, without causing any issues.
Sent from my SM-G935R4 using Tapatalk
barndawg76 said:
It's running beautifully for me. I haven't went through the entire guide for the improvements with the extra apps, but root and xposed are perfect. I am using the ForcedDoze app and it does help, without causing any issues.
Sent from my SM-G935R4 using Tapatalk
Click to expand...
Click to collapse
Hello? I'm new to USC. Want to get one off ebay. Seller says AT&T works on it. Does it mean phone is sim unlocked? Considering USC is CDMA?
I'm not sure about that. Check with the USC guys over at teamuscellular.com It should be possible, but I don't want to steer you wrong.
Sent from my SM-G935R4 using Tapatalk
Yikes, sorry for never finishing that initial post, everyone. Nonetheless, most of it would be outdated by now anyway, and though it ran well-enough for a while after some more tweaks that I never got around to describing here, it was still never a fully satisfying experience just due to the inherent jankiness of the Engboot root. (And it gradually ended abruptly in a softbrick). I haven't kept up with developments on S7 root at all really, though I thought I saw something in regards to a new root method a while back - anybody know on that?
Anyway, here's what I found works much better, though still Engboot-based - the Stang5liter custom ROM found here - https://forum.xda-developers.com/verizon-s7-edge/development/stang5litre-edition-5-0-s7e-t3450208
All of the frequently found issues with Engboot root - heat, lag, battery life, etc. - were pretty much immediately greatly improved when I installed it. "Improved," not "gone" - they do still exist to a degree which some may find unacceptable, but if you don't expect 100% perfection, you shouldn't have any problem with it. The issue I notice most on this ROM is lag, but this tends to happen mostly only when attempting to do a lot of tasks quickly, opposed to just here and there all the time randomly the way it often seemed before I switched to the Stang ROM. Oh, and for whatever reason, it kinda frequently runs crappy while charging, but that's really a minor annoyance. The biggest plus of all, however, is that you don't need to waste hours tinkering with arcane settings like before to create minor improvements in performance - all the tweaks are integrated into the ROM, so you pretty much just install it and forget about it. Overall besides the lag I've been basically problem-free with it, especially in regards to heat, which I always had varying issues with on "plain" Engboot root. It's worth noting too that I'm still using the v1 version of stang5litre - v2 is current and was released a while back, I just never upgraded out of sheer laziness and the "good enough for me" status of v1. I will probably try to upgrade finally this week sometime, so if I do I'll note any improvements/problems here.
The caveat that you may have noticed here is that Stang5litre is a Verizon ROM intended for the SM-935V. The good news is that it runs just fine on our SM-935R4 without any adjustments - I don't think I even had to tinker with the APN. Your phone may exhibit some Verizony characteristics - your phone will identify itself as a Verizon phone, for one - but you should be good. If you want to root, this is the best way to go that I've found, plus it's quick and easy.
(Oh and hey, has USCC pushed Nougat yet?)
No, no nougat. No root for nougat anyway, so no real rush to see it.
Sent from my SM-G935R4 using Tapatalk
Any idea of when nougat will be released for this phone? I'm using one and live in Malaysia. Haven't receive nougat. Really want to have it. Dont really care about rooting, etc
A US Cellular version? In Malaysia? You are in the wrong thread my friend.
Sent from my SM-G935R4 using Tapatalk
Just wanted to let you guys know this works on our variant of the S7 Edge.
https://forum.xda-developers.com/showthread.php?t=3552824
I flashed with Flash Fire and mounted system as read/write without any issues and it definitely makes a big difference in sound output.
Try at your own risk!!, but is working on my rooted US Cellular S7 Edge running PK1 firmware. Gonna try the dual speaker sound mod next and will update here if it works.
The dual speaker mod also worked for me, link below. I am using windows 7 professional 64-bit.
https://forum.xda-developers.com/showthread.php?t=3494412
Here is something else I found that works on the the edge panel to control your music. I only tested with Spotify, as that is the music player I always use.
https://forum.xda-developers.com/showthread.php?t=3365528
Sentm my SM-G935R4 using Tapatalk
Sent from my SM-G935R4 using Tapatalk
huszonnegy said:
I'm looking for a firmware which has european languages any idea?
Click to expand...
Click to collapse
Hi, did you find a solution?
Anyone taken the Nougat update yet? Just wondering how its running for you, if so.
Sent from my SM-G935R4 using Tapatalk
My wife set the update to install tonight,I have yet update ,liking my rooted mm, will update on how she likes it in a few days.
Sent from my Nexus 6 using Tapatalk
Yeah, I'm kinda hiding out for a more stable Nougat root, but I don't thunk we'll see one.
Sent from my SM-G935R4 using Tapatalk
The wife took the update and is really liking her battery usage. Said it is lasting way longer before needing charged(no definitive proof here. just what she said). She is trying to get use to the ui changes. So i decided to go ahead and update mine as the last week or so it has been lagging more than normal and eating battery. So i downloaded our firmware from updato.com and flashed with odin 3.12.3 and used the home.csc so not to lose any apps and data(had everything backed up with titanium in case of issues). All went well and was running fine so i decided might as well root and see how that goes. Rooted using this thread https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502 and i used the alternative root.bat listed in the op(post #688) i also did the suggested cache wipe and leave the phone for 5-10min, i waited at least 10 watching a youtube video. Have been running all day with no noticeable lag and decided to download Antutu and do a test,pulled a 132374. I know that benchmarks dont mean dudu but to me it verified it is running as fast and smooth as it seems. So far i have no complaints and have not found anything not working properly.
Just an update, the update and root on nougat apparently broke the fingerprint sensor. Only had 1 app I use that on so no biggy for me.
Sent from my SM-G935R4 using Tapatalk