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
Please forgive me, as I have not searched the forum extensively for an answer, but I'm in a bit of a time crunch as I am leaving on a trip tonight and need to get back to some semblance of a working phone.
Some time ago I flashed some rom (I think Paranoid Android; I don't remember. I liked it enough to keep it, then I didn't worry about it again after that.) Little by little it started getting slower and buggier, but for the most part it worked fine, so I ignored it. For the last couple of weeks it started losing signal and data constantly, with no change to the phone. I kind of just lived with it because I could usually restart my phone and I would regain signal, but as of a couple of days ago, it would just drop off and not come back until it wants to.
I had the day off to prepare for my trip, so I decided I would try to go back to stock; there's almost nothing that I do that requires a custom ROM and I had no data issues on stock, nor does my wife on her Note. I looked around for a bit for instructions to restore my phone, and found some, but out of the handful of pages I went to, each one had at least one link that was dead, rendering the method useless, to me, a layman, at least.
I then decided I would just find a Stock Rom, thinking that might be the next best thing. I found Clean Rom on here and decided to try to flash that. I made a backup of my system, wiped everything, and then flashed it. Except something is wrong with the zip and keeps giving me an error message. I then tried to restore my back up that I had just made to try something else, but something happened to that, and it also wouldn't open. I tried the backup before then (quite old, as I haven't done any tinkering with my phone for quite some time) and it worked, but it tells me that my sim card is disconnected, so I have no data or signal. As it is an old restore, I'm not sure what the name of the ROM is, but I can provide all of the information needed, if someone needs that to figure it out.
Anyway, long story slightly shorter: I need to fix this today, and like as soon as possible. I will give ten dollars, count them TEN DOLLARS, to the first person who can provide a set of working links and very straightforward instructions as to how to get back to stock (or if there is a good working ROM that will give me FULL functionality with no flares that would be easier to do. Easy and fast are the key components to this request). I'm not dumb, but I am no longer immersed in the lingo of this community, as it has been a few phones back that I really cared about actually experimenting much with my phone, so non-technical language would be nice. I know what flashing and wiping means. Most of the rest, probably assume I don't.
Thanks.
Your best (easiest) option is probably to flash another stock ROM, or stock-ish ROM. There are quite a few options in the Android Development section. There are a couple of stock rooted at&t ROMs in the first couple pages, also a stock rooted Telstra ROM.
You didn't mention which carrier you're with, whether your phone is branded, or any of your important details, like your firmware/hboot details and whether you're s-on or not. If you wanted to go back to completely stock, I'd need to know those details. Going completely stock can/will be a longer process though.
Sent from my Evita
Okay, I'll try another one. I'm not sure why Clean Rom didn't work, but if another one or two don't work I'll come back here and I'll have you talk me through getting back to stock and I'll throw you a digital Hamilton.
Thanks.
Well, I tried another couple of ROMs. They installed correctly, but it says that I have no sim card, so I still have no signal. Maybe I some how deleted my radio when I did a system wipe while trying to install one of the ROMs? I'm not sure.
Anyway, for "more details" I'm on AT&T, I'm not sure what you mean by branded, but it's the HTC One X, the current ROM is 4.1.1. I haven't done S-On/S-Off, or anything like that other than unlocking the bootloader a long time ago. The kernel version says 304010-g240d4d5, the baseban version is 0.17.32.09.12_10.86.32.08L The Build number is 3.17.707.1 CL134054 release-keys.
I'm not sure which of that information is relevant or not, but that's everything I can tell you.
Never mind that last post. When I said in the first post that I'm not dumb, apparently I lied. My phone fell off a table this morning, and I guess it knocked the sim card loose, but it coincided with doing the factory reset stuff, so I thought they were connected. I pushed it back in, restarted, and now the stock ROM I'm using works great.
Thanks/Sorry!
Well, it turned out to be an easy solution (Occam's Razor FTW yet again).
But this thread made me think . . . why the heck does it seem so many people lately flash ROMs without doing a nandroid first? Its a no brainer to me. If you are trying new ROMs, and not sure how they will perform, why would you not give yourself an easy way to simply revert to your last known good config?
I couldn't agree more, but there's plenty of not-so-smart practices on here, so I'm not at all surprised.
Sent from my Evita
Yea. Nandroid ftw
Sent from my HTC One using Tapatalk 2
Hi all, made an account in anticipation of my night spent mucking around with my new Galaxy S4 i9507. I had been reading about people who have had success and some who have had less success with getting custom ROMs on their devices. None said what methods they used, so I decided to compile together what I did today.
UPDATE 3/6/14
I installed a snapshot of CM 11 (KitKat) onto my device with little issues. I'll update this guide with the links to that firmware, and also update the existing links because of changes CyanogenMod made to how they aggregate their S4 devices now. They are treating them all as derivatives of 'jftle', so basically one firmware fits all devices, including the i9507! (even if not official yet).
Please read the bottom of this post if you wish to install KitKat on your device.
CUSTOM FIRMWARE ON SAMSUNG GALAXY S4 i9507 - Aus/HK
Tonight I have managed to root the device's stock firmware (I have the Australian Optus/Virgin device); install ClockworkMod Recovery on the stock firmware, and then use it to install CyanogenMod 10.2.0 (jfltexx) on the device.
If you're looking to root this device, I found that by treating it essentially as an international i9505 I was able to fulfil all three of the things I mentioned above.
UPDATE: THIS WILL VOID YOUR WARRANTY AND RESULT IN 'KNOX WARRANTY VOID 0x1' BEING DISPLAYED WHEN YOU ENTER DOWNLOAD MODE ON THE DEVICE. PLEASE BE SURE YOU ARE OKAY WITH THIS HAPPENING BEFORE TRYING THIS FOR YOURSELF. AS IT STANDS, KNOX CANNOT BE RESET, IT IS AT A HARDWARE LEVEL.
[ROOT i9507]
Using Chainfire's guide to CF-Auto-Root in the Galaxy S 4 i9505 Original Android Development section of this forum; I was able to root my device despite it being an i9507. Being a new user, I wasn't sure exactly what things to test out whether the root worked/was permanent, but I did install AdBlock Plus and it asked me for Superuser privileges, then proceeded to work. I also restarted the device and tested whether the root was still present; it was.
[INSTALL CLOCKWORKMOD]
I decided to install CyanogenMod as I have heard from friends that have it; and read online about it being one of the more stable custom ROMs available. It has been a while since I last owned an Android device! So, continuing with my theme of treating this device as being an international i9505, I obtained CM 10.2.0, a stable release of the jfltexx CM, based on from their website (as of December 2013, this was the most recent). Their custom installer app on Windows did not support my phone, so I had to use their guide for manual installation.
Their guide contained steps to installing ClockworkMod Recovery as well as the ROM installation. Following the guide, I installed it without a hitch. When rebooting the phone from ClockworkMod, it prompted me about the fact that the phone may reflash its own recovery tool, but this did not happen. Once again, a success.
[INSTALL CYANOGENMOD]
The last task was to install CM. This was quite an endeavour as I decided to use someone else's Windows 8 laptop (being the only Windows device I had access to at the time) and I forgot how much of a struggle it can be! Again, I used CM's guide to installing 10.2.0 (which by the way is Android 4.3.1, whereas the stock firmware is bloated and heavy at 4.2.2). This went off without a hitch once I reminded myself how the ADT works. I also did as CM suggested and installed the Google Apps pack alongside the ROM.
So, currently this is where I'm at. The device boots and reboots fine. Some users in certain threads had issues with loading 4.4 (KitKat) ROMs or custom ROMs that they didn't allude to the names of, so I don't know if they were having issues with CM or not. There are other threads, but that was the one that kickstarted my attempts to get this all to work. Their issues with the custom ROMs seemed to be related to the 4.4 ROM not recognising the modem of the i9507; I'm not sure why this is but the i9507 was made specifically for Australian/Hong Kong networks so perhaps 4.4 has not been updated yet or something of the like. Anyway, on 4.3.1, or CM 10.2.0, my SMS, calling, and internet are working fine (it displays Virgin Mobile as my carrier). My 4G reception is somewhat iffy in this town (or in particular my house), and the reception seems to be switching between 3G and H so whether that is indicative of 4G not working, I'm not sure. LTE is definitely checked in the settings, however, and my area does have 4G, but my parents' iPhone 5Ss sometimes do not have 4G in this house either. I'll report back tomorrow after having tested the phone for a day to see if the 4G does activate.
As it stands, however, the phone seems to be functioning well. Oddly the Settings report that the phone is an i9505, I assume that's normal as I'm using a ROM for that particular phone!
[CONCLUSION]
So, I hope that anyone who has been looking for a way to remove the carrier/Samsung bloat from their i9507 device will have a good time using the guides I've used. I followed them to the letter and I had no issues.
DISCLAIMER: I had no troubles, but that's not to say you won't either. Please be careful, as you may potentially risk affecting your phone negatively. I'm simply telling you what I did, not giving you a 100% correct and flawless guide that will work no matter what.
Also if you're looking for a 4.4 ROM then you might be out of luck, least till some dev or coder takes notice of this device's existence and helps out to develop a specific way of rooting this phone/installing custom ROMs for this phone. Overall though, it seems to all work fine so perhaps the 4.3.1 CM isn't such a bad thing.
If you try this and want the original firmware back on your phone, use this link. I believe that OPS is the Australian firmware, the other one is for Hong Kong. So, for the second link, HK is Hong Kong, and the one without is for Aus.
UPDATE 3/6/14
I've successfully managed to install a Nightly build of CM 11, based on KitKat. Read my latest post in this forum for more info. I essentially found that upgrading from within the phone itself caused a number of issues so I did a fresh flash. Please note that such a flash of a new OS wipes all personal data but not things like images, videos, etc. I lost all my contacts, SMS, browsing history, apps etc. But my Gallery, Downloads folder, etc remained intact.
I followed my guide to flashing the phone again, but I used a Nightly build of CM 11, based on KitKat. As I write this, there are actually stable versions of CM that you can use in place of the CM 10.2.0 I used in the above guide. If you follow those steps but use this firmware you'll find no issue. Feel free to use CM's guide, but don't, under any circumstances, forget to flash Google Apps to your phone!!!
If you need a hand or want a question answered, feel free to post here and I'll do my best to help you out. Thanks!
kaiserwatson said:
Hi all, made an account in anticipation of my night spent mucking around with my new Galaxy S4 i9507. I had been reading about people who have had success and some who have had less success with getting custom ROMs on their devices. None said what methods they used, so I decided to compile together what I did today.
Tonight I have managed to root the device's stock firmware (I have the Australian Optus/Virgin device); install ClockworkMod Recovery on the stock firmware, and then use it to install CyanogenMod 10.2.0 (jfltexx) on the device.
If you're looking to root this device, I found that by treating it essentially as an international i9505 I was able to fulfill all three of the things I mentioned above.
[ROOT i9507]
Using Chainfire's guide to CF-Auto-Root in the Galaxy S 4 i9505 Original Android Development section of this forum; I was able to root my device despite it being an i9507. Being a new user, I wasn't sure exactly what things to test out whether the root worked/was permanent, but I did install AdBlock Plus and it asked me for Superuser privileges, then proceeded to work. I also restarted the device and tested whether the root was still present; it was.
[INSTALL CLOCKWORKMOD]
I decided to install CyanogenMod as I have heard from friends that have it; and read online about it being one of the more stable custom ROMs available. It has been a while since I last owned an Android device! So, continuing with my theme of treating this device as being an international i9505, I obtained the latest stable release of the jfltexx CM from their website (it was the most recent stable release at the time, may be out of date by the time you get to doing this yourself). Their custom installer app on Windows did not support my phone, so I had to use their guide for manual installation.
Their guide contained steps to installing ClockworkMod Recovery as well as the ROM installation. Following the guide, I installed it without a hitch. When rebooting the phone from ClockworkMod, it prompted me about the fact that the phone may reflash its own recovery tool, but this did not happen. Once again, a success.
[INSTALL CYANOGENMOD]
The last task was to install CM. This was quite an endeavour as I decided to use someone else's Windows 8 laptop (being the only Windows device I had access to at the time) and I forgot how much of a struggle it can be! Again, I used CM's guide to installing 10.2.0 (which by the way is Android 4.3.1, whereas the stock firmware is bloated and heavy at 4.2.2). This went off without a hitch once I reminded myself how the ADT works. I also did as CM suggested and installed the Google Apps pack alongside the ROM.
So, currently this is where I'm at. The device boots and reboots fine. Some users in certain threads had issues with loading 4.4 (KitKat) ROMs or custom ROMs that they didn't allude to the names of, so I don't know if they were having issues with CM or not. There are other threads, but that was the one that kickstarted my attempts to get this all to work. Their issues with the custom ROMs seemed to be related to the 4.4 ROM not recognising the modem of the i9507; I'm not sure why this is but the i9507 was made specifically for Australian/Hong Kong networks so perhaps 4.4 has not been updated yet or something of the like. Anyway, on 4.3.1, or CM 10.2.0, my SMS, calling, and internet are working fine (it displays Virgin Mobile as my carrier). My 4G reception is somewhat iffy in this town (or in particular my house), and the reception seems to be switching between 3G and H so whether that is indicative of 4G not working, I'm not sure. LTE is definitely checked in the settings, however, and my area does have 4G, but my parents' iPhone 5Ss sometimes do not have 4G in this house either. I'll report back tomorrow after having tested the phone for a day to see if the 4G does activate.
As it stands, however, the phone seems to be functioning well. Oddly the Settings report that the phone is an i9505, I assume that's normal as I'm using a ROM for that particular phone!
[CONCLUSION]
So, I hope that anyone who has been looking for a way to remove the carrier/Samsung bloat from their i9507 device will have a good time using the guides I've used. I followed them to the letter and I had no issues.
DISCLAIMER: I had no troubles, but that's not to say you won't either. Please be careful, as you may potentially risk affecting your phone negatively. I'm simply telling you what I did, not giving you a 100% correct and flawless guide that will work no matter what.
Also if you're looking for a 4.4 ROM then you might be out of luck, least till some dev or coder takes notice of this device's existence and helps out to develop a specific way of rooting this phone/installing custom ROMs for this phone. Overall though, it seems to all work fine so perhaps the 4.3.1 CM isn't such a bad thing.
If you try this and want the original firmware back on your phone, use this link or this one. I believe that OPS is the Australian firmware, the other one is for Hong Kong. So, for the second link, HK is Hong Kong, and the one without is for Aus.
If you have any questions, please feel free to ask. I'll post later tomorrow when I've tested the phone for a day to see if it's still working, and to see if the 4G/LTE does actually work. Fingers crossed nothing goes wrong in the meantime!
Click to expand...
Click to collapse
I've had my i-9507 rooted for about a month now with foxhound rom, also on the optus variant.
One thing i've noted is, its next to impossible to update the MODEM for it.
I think because our latest modem for this variant is the one we have stock. And new updates haven't been put in terms of modem specifically for our variant yet.
We should keep this thread stickied for Australian OPTUS GT-i9507 discussion.
OR open up a sub forum for it.
kaiserwatson said:
I'll post later tomorrow when I've tested the phone for a day to see if it's still working, and to see if the 4G/LTE does actually work. Fingers crossed nothing goes wrong in the meantime!
Click to expand...
Click to collapse
Firstly, thank you for creating this complete description of your experiences with customising the i9507.
Secondly, just wanted confirmation that you do now have the pesky "KNOX WARRANTY VOID: 0x1" displayed when your device is in Download mode, right?
Lastly, any updates, issues? All still working, including 4G/LTE?
Hey sorry its been more than a day, I've been swamped with work, that Christmas time feel.
I do have the Knox 0x1, which I assume means my warranty is void. There's conjecture as to whether that will actually affect warranty for this device in Australia, as I've read up on the Knox system but i think the ACCC would have serious issues with this system actually affecting the warranty. But yes, it would seem my warranty is void, let's hope the phone lasts two years!
I have been able to access 4G, the phone says 4G or LTE, sometimes switching between the two. Again, the reception in the town I'm currently staying in is pisspoor so I can't say for certain whether the antenna/modem is fully functioning to the degree it would be on the stock firmware, but I can definitely access the Optus 4G network.
One issue I did have was that I sent an SMS then immediately turned my screen off, 40 minutes later the message was still 'sending'. I have recreated the same scenario but I haven't been able to get it to happen again, perhaps just a weird tower-side quirk. I know people were having issues with the modem and the phone sleeping but this doesn't seem to be related. Overall I'm really happy with how this has all gone. My battery life has been increased by at least 40% and the phone is so much faster. Very pleased.
kaiserwatson said:
Hey sorry its been more than a day, I've been swamped with work, that Christmas time feel.
I do have the Knox 0x1, which I assume means my warranty is void. There's conjecture as to whether that will actually affect warranty for this device in Australia, as I've read up on the Knox system but i think the ACCC would have serious issues with this system actually affecting the warranty. But yes, it would seem my warranty is void, let's hope the phone lasts two years!
I have been able to access 4G, the phone says 4G or LTE, sometimes switching between the two. Again, the reception in the town I'm currently staying in is pisspoor so I can't say for certain whether the antenna/modem is fully functioning to the degree it would be on the stock firmware, but I can definitely access the Optus 4G network.
One issue I did have was that I sent an SMS then immediately turned my screen off, 40 minutes later the message was still 'sending'. I have recreated the same scenario but I haven't been able to get it to happen again, perhaps just a weird tower-side quirk. I know people were having issues with the modem and the phone sleeping but this doesn't seem to be related. Overall I'm really happy with how this has all gone. My battery life has been increased by at least 40% and the phone is so much faster. Very pleased.
Click to expand...
Click to collapse
That occurs because the modem signal cuts out after you switch your phone off, or lock it.
This issue can be resolved by updating our modems, but with our current variant we can't update it yet apparently, until the correct new modem for our specific variant has been released.
Hi guys,
I thought I would also post here.
I have the optus 9507 and I tried a couple of different kitkat 4.4 roms. They all worked perfectly except for the fact that they lost data completely as soon as the phone went to sleep. the weird thing is, the phone showed 0 bars but i could take calls just fine, just had data issues.
i tried the slimkat rom and the echoe rom with the same issue
i went back to stock firmware, rooted, ran a debloat script i found on xda, removed a bunch more apps, then unrooted again because i need to run good for enterprise for work.
im getting decent battery life with the debloated stock rom but i would like to move to 4.4 if theres a rom that works. ive been watching the optus and sammobile site hoping there will be a newer modem for the hk version because i think optus will take their time releasing 4.3 for this model.
kaiserwatson said:
Hi all, made an account in anticipation of my night spent mucking around with my new Galaxy S4 i9507. I had been reading about people who have had success and some who have had less success with getting custom ROMs on their devices. None said what methods they used, so I decided to compile together what I did today.
Tonight I have managed to root the device's stock firmware (I have the Australian Optus/Virgin device); install ClockworkMod Recovery on the stock firmware, and then use it to install CyanogenMod 10.2.0 (jfltexx) on the device.
......
Click to expand...
Click to collapse
Thanks for your experience sharing,
I also started with Cyanogen and shared about the same experience.
Just didn't know the Knox thing before I started.. should had read up more before doing it.
So you did the Recovery with Heimdall also? What has made you switch to the customized Rom camp
kaiserwatson said:
Hey sorry its been more than a day, I've been swamped with work, that Christmas time feel.
Click to expand...
Click to collapse
Hey, no worries at all, anyone who works weekends can take all the time they need...
But yes, it would seem my warranty is void, let's hope the phone lasts two years!
Click to expand...
Click to collapse
Yea, I've done some reading also and you're right, it seems to be all conjecture, I really doubt handset warranty refusal can be based on the KNOX Warranty chip. I think the Samsung Enterprise Security Group VP explains it well here.
Overall I'm really happy with how this has all gone. My battery life has been increased by at least 40% and the phone is so much faster. Very pleased.
Click to expand...
Click to collapse
Great to hear, based on this I can ge ahead and 'burn out' my eFuse, happy in the knowledge that my Knox warranty has gone to a good cause. :fingers-crossed:
---------- Post added at 08:49 PM ---------- Previous post was at 08:40 PM ----------
opelcalibra said:
then unrooted again because i need to run good for enterprise for work.
Click to expand...
Click to collapse
I can only assume your "enterprise for work" has nothing to do with KNOX, right? Coz that option would be closed for you now...
CuriosityBrah said:
That occurs because the modem signal cuts out after you switch your phone off, or lock it.
This issue can be resolved by updating our modems, but with our current variant we can't update it yet apparently, until the correct new modem for our specific variant has been released.
Click to expand...
Click to collapse
That odd message not sending was the only issue I've had with this sort of thing; I can still download things, receive messages and calls just fine while my phone is sleeping, how do you know if the modem signal is cutting off? Perhaps it's just a selective thing, not sure. Don't know how to test if it's happening to me because it doesn't seem to be, lol.
opelcalibra said:
I have the optus 9507 and I tried a couple of different kitkat 4.4 roms. They all worked perfectly except for the fact that they lost data completely as soon as the phone went to sleep. the weird thing is, the phone showed 0 bars but i could take calls just fine, just had data issues.
Click to expand...
Click to collapse
Hey mate if you check the forum that I linked to the Knox issue; someone on there posted a fix for sound/WiFi issues post-Knox voiding, maybe that fix'll work for you. Sorry I can't link you to the exact post but it was about 10-20 pages in.
opelcalibra said:
i went back to stock firmware, rooted, ran a debloat script i found on xda, removed a bunch more apps, then unrooted again because i need to run good for enterprise for work.
im getting decent battery life with the debloated stock rom but i would like to move to 4.4 if theres a rom that works. ive been watching the optus and sammobile site hoping there will be a newer modem for the hk version because i think optus will take their time releasing 4.3 for this model.
Click to expand...
Click to collapse
Yeah I reckon they'll take ages, they have pretty much left everyone who's getting this phone in the next couple of months in the dark because of the (as I can tell) severe lack of devs etc in Aus who have Samsung phones and are willing to hack them to the ****. I wish I could help out somehow, but I don't have the time to learn so I figured I'd help out by putting up my experiences. I'm still learning as I go haha.
As for your KitKat problem, I have read that 4.4 didn't do so well in terms of battery life and bloat, what are your reasons for wanting to go to it? I wanted the most recent build also but I figured that if they're still having issues with it then it was better to go with something I knew would work (ie. 4.3.1).
phileasx said:
Thanks for your experience sharing,
I also started with Cyanogen and shared about the same experience.
Just didn't know the Knox thing before I started.. should had read up more before doing it.
So you did the Recovery with Heimdall also? What has made you switch to the customized Rom camp
Click to expand...
Click to collapse
I followed the Windows process on the CM wiki to the letter, so yeah I did the Heimdall also.
Mate legitimately I went from my stock firmware taking up so much space on the hard drive to the real lightweight CM, seeing as I haven't bought a micro SD yet that was a big deal. Also battery life was a major reason for me buying the S4 so to be able to further improve it is just hella.
siganid said:
Hey, no worries at all, anyone who works weekends can take all the time they need...
Yea, I've done some reading also and you're right, it seems to be all conjecture, I really doubt handset warranty refusal can be based on the KNOX Warranty chip. I think the Samsung Enterprise Security Group VP explains it well.Great to hear, based on this I can ge ahead and 'burn out' my eFuse, happy in the knowledge that my Knox warranty has gone to a good cause. :fingers-crossed:
Click to expand...
Click to collapse
In Australia I think we're pretty good. Funny that Samsung and Optus have given us this nice present and it's only a matter of time before someone cracks it open and remains above the warranty voiding
I have read that Knox may be software-based, which would make sense, and maybe it's a matter of time before someone cracks that too. Hehe.
Go ahead, post here if you have any issues and I'll see if I can help you out. What ROM would you be planning on using? A 4.3.x one?
kaiserwatson said:
I followed the Windows process on the CM wiki to the letter, so yeah I did the Heimdall also.
Mate legitimately I went from my stock firmware taking up so much space on the hard drive to the real lightweight CM, seeing as I haven't bought a micro SD yet that was a big deal. Also battery life was a major reason for me buying the S4 so to be able to further improve it is just hella.
Click to expand...
Click to collapse
Welcome to the rom flashing side
After read up more, I realize Odin is a more popular method for Galaxy S4 flashing,
Besides that, Stock rom battery life should also be all right. Samsung did quite some efforts to make the software user friendly.
Anyway, the Bloatware chunk are really irritating have to say.
because i cant keep still i have flashed my phone again lol.
i flashed the official CM 11 (4.4.2) and gapps for kitkat and all is working awesome so far.
no issues with losing signal when going to sleep. seems very fast. right now im happy with it.
Could someone please find new links for the original software posted in the OP?
Links are dead, would be greatly appreciated! =)
Also, Opelcalibra, you have no issues with network/signal on CM 4.4.2 with the Optus i9507?
I better give it a try then lol
RE: Signal issues
Hi,
I also have the AU i9507 Opus S4, I flashed the Omega based 4.4.2 KitKat (i9505 version) and had wifi problems (Greyed out) I tried various fixes and went back to 4.3 based Omega, this had its problems with cell signal being lost when locking the mobile.
I fixed this by going into settings and experimented with mobile networks i.e. Settings, more networks, mobile networks, network mode and tried all 4x options with (for me at least) the GSM ONLY option selected, great rom and worth losing the 4g which is very patchy in my part of Melbourne.
D
Anyone else had any sort of success rooting this phone without tripping Knox.
Also, is it just me, or does it suck pretty hard that we Aussies get stuck with an inferior version of a phone? (Snapdragon 600 in the I9507 vs the 800 in the other international versions)
Update
Hi
Just wondering if anyone has an update on this? Success or otherwise...
One of the main reasons I'm looking to root is to boost volume levels - I find the volume to be way too low. Does anyone know of a way to do that without rooting? Of course I'd like to remove bloatware but could live with it if volume was fixed.
Thanks in advance.
thestuntman80 said:
Anyone else had any sort of success rooting this phone without tripping Knox.
Also, is it just me, or does it suck pretty hard that we Aussies get stuck with an inferior version of a phone? (Snapdragon 600 in the I9507 vs the 800 in the other international versions)
Click to expand...
Click to collapse
Hey bro, no one has cracked without tripping Knox yet because as far as I can tell it's a phone specific fix/hack. So, because our phone is a different and 'rare' model, I doubt that the major heads in the Knox-proofing scene (CF comes to mind) will have the time to make a fix for the knox trip. So for now, either suffer in your jocks (QQ) get a different phone (uh, not likely) or wait for the minute chance that someone actually cares about Aussies )
As for your second point, yeah, it does suck. We get shafted with all sorts of things like prices, release dates, localization...the list goes on. Unfortunately the people who make these ploys know we're desparate and will pay the exorbitant prices anyway :/
jameshef said:
Hi
Just wondering if anyone has an update on this? Success or otherwise...
One of the main reasons I'm looking to root is to boost volume levels - I find the volume to be way too low. Does anyone know of a way to do that without rooting? Of course I'd like to remove bloatware but could live with it if volume was fixed.
Thanks in advance.
Click to expand...
Click to collapse
Hey mate, the rooting was probably the easiest part of the whole situation. You can follow my guide in the OP if you're having trouble. Just be aware about the warranty issues etc because your audio issue may be hardware related rather than software? Is the volume issue in the headphones or the speaker? Some apps may not utilise the phones full volume and also be sure to go into the settings of the phone and make sure the volume limiter is turned OFF. This **** me to tears for the longest time but once I figured out what the issue was, all good!
The only thing I'd say is just make sure its not a hardware issue because you don't want to root your phone, find out that it wasn't a software issue, take your phone into Samsung and have them tell you that your warranty is voided because you rooted. Obviously that's a worse case scenario but just be on the safe side.
I hope I helped you guys!
kaiserwatson said:
Hey mate, the rooting was probably the easiest part of the whole situation. You can follow my guide in the OP if you're having trouble. Just be aware about the warranty issues etc because your audio issue may be hardware related rather than software? Is the volume issue in the headphones or the speaker? Some apps may not utilise the phones full volume and also be sure to go into the settings of the phone and make sure the volume limiter is turned OFF. This **** me to tears for the longest time but once I figured out what the issue was, all good!
The only thing I'd say is just make sure its not a hardware issue because you don't want to root your phone, find out that it wasn't a software issue, take your phone into Samsung and have them tell you that your warranty is voided because you rooted. Obviously that's a worse case scenario but just be on the safe side.
I hope I helped you guys!
Click to expand...
Click to collapse
I'm fairly certain it's a software issue. I've done a fair bit of reading on it and the low volume is a very common complaint about the S4. My volute limiter is turned off - thanks for that tip though!
I'm going to try to root this weekend. I really hope that it works and I don't have any issues with reception dropping when the phone goes to sleep! Feels risky.
I've changed my firmware from Optus to XSA, but am still on 4.2.2, how do I upgrade now?
Kies says I have the latest release.
has anyone got links to newer modem files for this phone? been given one to update it to 4.4, but i know from experience that doing so without at least a 4.4 GSM modem, it wont behave right.
to the people without working wifi after updating: flash the Ktoonz kernel, he has a fix for that.
Hi All,
I recently updated to the new official 4.3 update from optus in order to update my baseband etc.
Then i immediately updated to the i9505 Goldeneye 4.4.2 rom. Ran a ebloat script to get rid of alot of the extras and its running very nicely.
Since updating the modem I get 4g at home which i never did before.
optus rom here
http://www.sammobile.com/firmwares/3/?download=27109
flashed via odin (will lose root and custom recovery). re-root and install recovery after flashing this room.
goldeneye rom here
http://forum.xda-developers.com/showthread.php?t=2313469
obviously this will flag knox, mine was flagged long ao
I originally used the Dirty Santa routine on my Verizon VS995, so it remained on VS99513A for a couple of years. Had all manner of issues over time - apps "failing to respond", YouTube not displaying video but rather black screens, green-screen crashes, etc. Finally had enough and used the LGUP process to return to stock and unroot, of course. I probably (assuming, anyway) could have gone right to the latest Oreo firmware with LGUP, but decided to go to the stock version of VS99513A and then just do the many system updates to get current.
It's now happily sitting on Oreo, and knock on wood it's like having a new phone! It's so much smoother, YouTube is working, lol, battery life is an order of magnitude better and it's working like a phone should work. No one knows the future, of course, but today, I'm happy.
Just passing this along, but I've gone from being ready to trash this thing to being able to enjoy it again without worrying about having to dump some $$$ into something else.
I had originally rooted to get around the Verizon mobile-hotspot check, but I have an unlimited plan that includes it anyway, now, so that's no longer an issue.
Possible placebo effect...
A clean stock unrooted firmware may run smoother than a few custom roms, but not smoother than a rooted version of the exact same rom.
I wouldn't give up on root, even if the best ever unrootable phone was given to me for free (Ad-blocking being the primary reason)
Prowler_gr said:
Possible placebo effect...
A clean stock unrooted firmware may run smoother than a few custom roms, but not smoother than a rooted version of the exact same rom.
I wouldn't give up on root, even if the best ever unrootable phone was given to me for free (Ad-blocking being the primary reason)
Click to expand...
Click to collapse
Blokada DNS changer. Also working without root. All problems gone. :good: for me the main reason for root is to prevent screen retention. The sucked soooo hart. If there would be an option without root I would also go with an unrooted stock fw.
Prowler_gr said:
Possible placebo effect...
A clean stock unrooted firmware may run smoother than a few custom roms, but not smoother than a rooted version of the exact same rom.
I wouldn't give up on root, even if the best ever unrootable phone was given to me for free (Ad-blocking being the primary reason)
Click to expand...
Click to collapse
It's not even a close comparison in my case. Admittedly I'm on Oreo now and not the original Nougat the phone came with (and was rooted with), but it's literally a night and day difference. It wasn't just performance - it was extreme instability, apps that wouldn't work or would constantly go into "not responding" mode, green screens, battery life that was awful to the point where it nearly always needed to be connected to a charger, etc. I'd tap on an app or a function in an app before, and I'd literally have to wait and wait for something to happen at times.
Now? Lightning fast and smooth operation, stability where there was none before, etc. And, as stated, for what I really needed root before (bypassing vendor check for mobile hotspot), it's no longer an issue due to the phone plan I'm on.
I'm not knocking rooting, so don't misunderstand. But for my experience with this phone, going back to stock where I could actually update the version of the OS, as well, has made all the difference in the world for my user experience. YMMV.
Interesting... I haven't tried stock Oreo yet but in every time I flash a new stock rom the phone runs great for 6 months then starts lagging.
oooh meee TOOO! me! meeeee!
Heyitsrick said:
I originally used the Dirty Santa routine on my Verizon VS995, so it remained on VS99513A for a couple of years. Had all manner of issues over time - apps "failing to respond", YouTube not displaying video but rather black screens, green-screen crashes, etc. Finally had enough and used the LGUP process to return to stock and unroot, of course. I probably (assuming, anyway) could have gone right to the latest Oreo firmware with LGUP, but decided to go to the stock version of VS99513A and then just do the many system updates to get current.
It's now happily sitting on Oreo, and knock on wood it's like having a new phone! It's so much smoother, YouTube is working, lol, battery life is an order of magnitude better and it's working like a phone should work. No one knows the future, of course, but today, I'm happy.
Just passing this along, but I've gone from being ready to trash this thing to being able to enjoy it again without worrying about having to dump some $$$ into something else.
I had originally rooted to get around the Verizon mobile-hotspot check, but I have an unlimited plan that includes it anyway, now, so that's no longer an issue.
Click to expand...
Click to collapse
Between the GIGANTIC pain in the ass that it was to root this phone (I have a VS995 rooted and on 13a ever since) and all the problems that rooting has caused I'd be ready to undo it all anyway. But due to some problem with internal storage* that started a couple weeks ago, I was fed-up and factory reset the phone. When it boots normally, a check in "about" shows the software status as "modified" but root checker says its not rooted, superSU can't find root (I installed it from play store).. Tried to update via the "system updates" in settings (could not get it to show developer options either).
* The storage issue: I have 50 gigs internal (or something similar) and I get a message that the storage is full and some apps may not work. Not possible, but I humored it and uninstalled everything, cleared cache, downloads cleared, etc ... still showing +/-1 gb free space avail. Factory reset, appears stock, but free space STILL less than 1 GB.
Regretted rooting this phone almost immediately since I still couldn't get rid of certain apps, I had to deal with the camera issues, etc... The only thing positive about it was that my work was unable to install their MDM crap (Mobile Iron shielding Gsuite etc). But anyway, it doesn't look like I'll be able to update the system - I tried it and now it boots to twrp, or boots regularly and then loops around to twrp again. I'm looking for the easiest way to get the phone working (with the persistent problem of internalstorage being full for no reason fixed) and at least reasonably updated. Don't care if it's rooted or not really.
Do you or does anyone have a link to a "play by play" for whatever might work? Its been too long since I rooted it for me to remember the nuances of the procedure so its safe to say that I don't really understand how Android works all that well, so instructions like, "flash xxx 3.2 then flash back to 2 then fastboot and load yer ROM but don't forget the dalvik blah blah" won't work... I'm looking for the idiot's version with hand-holding and everything.
Interesting analysis................ I mainly rooted my older phones due to the need for the mobile hotspot without paying VZ extra charges. However, now that I have the VS995, I was able to download and use the Foxfi app (I paid for the Pro upgrade license) so this left me thinking, do I really need to root my V20 at all? In the past, you couldn't run apps that ran many WIFI tools and other tech'y things, but it seems much of that has changed. I don't run custom ROMs so maybe I don't need to root. Would be glad to hear rebuttals on the subject
I received a new VS995 last week and I flash h910 to get FM radio. I could not be happier as I'm on OREO and the device is working perfectly without any issue whatsoever and with latest mk2000 kernel (2.2 beta) general interface performance is working very well - as it should. Hotspot needed a little workaround bit it wasn't too difficult. I wouldn't dream of going back to stock!
https://forum.xda-developers.com/showpost.php?p=79939652&postcount=269
I know it's not straight to bootloader unlock and root this phone but it's worth the trouble. I hope my new fone will last and last untill manufactures change mind about removable batter and horrible new aspect ratio! No thanks V30 !
You're right.
There's no good reason to root the v20. Even rooted you can't do things that other phones can do, like enabling monitor mode on the Wi-Fi. Nor have I been able to get an external Wi-Fi adapter to work on it.
0per said:
There's no good reason to root the v20. Even rooted you can't do things that other phones can do, like enabling monitor mode on the Wi-Fi. Nor have I been able to get an external Wi-Fi adapter to work on it.
Click to expand...
Click to collapse
YOU ARE WRONG.
AD BLOCK Yeah they have rootless ad block but they work like ****
screen burn fixes. hows the ghosting?
titanium backup still best option for absolutely all apps getting backed up.
Sorry i have run root too long i cant live without it anymore.
is this happening to just verizon version of LG V20? anyone?
is this happening to just verizon version of LG V20? anyone?
I am now running stock Android 8 with ezV2020 kernel for the DS version. Boot loader unlocked and Rooted.
As far as I can see, it is pretty stable. It was a long and tough process, but having already done the LG F800K it just took some hours to do the LG H990N and not days as the former did to break free.
So... just wanted to tell you guys, and let you know, it is possible. Both Sims are working, screen working, seems smooth and stable and all that.
Well, it was a lot of hoops, but I did think it might be possible - and it was and is.
Used my experience from the F800K on this little guy, and it seemed to have payed off, even if I had forgotten a lot of things or had to gather my thoughts on it.
But what a fight... But there you go.
Although it seems like it might be locked on the 4G, and I wanna have it run 3G as the radiation is much much much smaller compared to 4G. Like it is amazing to see the difference between the 2, one being nearly always in the Green by the testing instrument and the other nearly always in the Red. Just utter terrible. But I a have an app that should work that out, or maybe it just need a code and adjustment. dunno what they done to this. But should be workable. There was this code with putting the mobile number into it that got you into a menu... But I found an application for my new used LG mobile that could do the trick which name alludes me... but wait a minute and I will get it. That will most likely be my first try to fix the issue. 4G Switcher is the name of the app and it should be all clean and free!
Dearly regards
- Darkijah
Update... the good news first.
The H990N is running very smooth with the A8 Rooted with the DS kernel of ezV2020... The bad news... the Rotation and Camera does not work.
Not sure if this was something that happened after I installed Lineage 17.1 A10 and then stored it or if it was a problem before that. I just don't know. It looked like it did fine for me, and yet... apparently some issues. I tried to install a foreign kernel like I had done before, but TWRP would not flash it because the kernel file was foreign to the system. Which is odd as I flashed the mobile with the F800K kernel to get it working first hand, ezV2020 1.0 if I recall correct.
Maybe fastboot or something could installed it, adb whatever - still confused by it all...
Lineage by the way was somewhat horrible, and when I found out the sound from the Phone Jack was utter horrible I quickly turned around back to A8 stock. Although now witnessing these issues. I don't know if those issues where there before or not - or if it was something coming after the restoration from Lineage. A lot of factors can make issues.
But the mobile overall, works with network and it does run very smooth compared to my F800K, at least I seem to feel a difference here. One is slower to react, and the other is just butter smooth.
Not sure if I should toy more around with the stuff... I still have my new mobile incoming at some point when they change the broken screen. Getting a little sick and tired of the Android nonsense everywhere, which is literally is, everywhere. Issues, and looking for work arounds and what not, it is never ending.
Rooting should be as easy as pushing a button - and in my opinion should be default out of the box. No user should need to tinker and toy around with there expensive device to get things in order - the criminal companies purposely working against the users on so many levels. Highjacked the whole thing and filling it up with nonsense in the name of security or what not.
To early to say, but I might have found a fix. That took hours and hours... And still at it. But I have the Camera working and the rotation and it seems to still be running smooth. So... Hopefully no more issues, but I will further test it and try some things. It seems this issue is in all H990N20h stock Roms - I have one left to try out. I just tried a DS stock Rom and after installing the kernel and all, doing all the steps I am now into the system, need more testing if everything works, but... Well the Kernel ezV2020 is DS and now the system is DS, also known as Global if I recall. The TWRP is H990 another dual variant. There are absolutely some options to do, but they only allow 2 images being downloaded from the site and it takes a lot of time trying things out, installing it and making it work in the first place. Hours and hours wasted on this :/
But... just wanted to make an update for you guys Found a solution it seems - although there might come up new issues, usual do with Android, but hopefully it everything works!
You have to use the old version of TWRP to fix the lock issue if you get a screen like that. Very annoying, but the oldest version I have breaks it, and then you can install another higher version thereafter. Wipe out the data, and I have wiped out all else except system, not sure if it is needed overall... But in any case, that is my observations for now. I have used TWRP versions before 3.3.0 to unlock this locking issue.
Another issue is that if you go into the system it seems to delete TWRP, so... There are all these steps to do to make it work, *Sigh*.
H990N20f_00_OPEN_HK_DS_OP_1214 - camera and rotation not working.kdz
H990N20h_00_OPEN_HK_DS_OP_0225 - camera and rotation not working.kdz
H990ds20b_00_OPEN_AU_DS_OP_1108 - Newest DS version and working.kdz
H990N20d_00_OPEN_HK_DS_OP_0920 - Oldest H990N A8 but working.kdz
Here are my data so far.
I don't get it, Android is a madhouse. So after having tried things to get the Camera and the rotation to work in the stock A8, kernels and all... Then now installing the newest that did not work. Now it work all of the sudden. Makes zero sense and typical Android. I thought it might work and just for lunacy of it all I tried to install it to verify it still did not work - and now all of the sudden things that did not work, works even if I did the exact same things. It is an utter madhouse. And just typical Android...
After trying different kernels and what not... Downloading another version that did not work, downloading another and another variant of the DS... Then trying the DS that worked, then trying the oldest of the H990N working, and then trying the Newest of the H990N, and now working...
So once again I seemingly wasted hours and hours on something that now just works... Like this is something that happens all the time working with Android I have found out.
The only thing I can conclude by this, is that the installation of the DS in Partioning DL with boot and recovery unchecked, 4 unchecked in total. Must have done something to it, so it could apparently work for the other main images. At least, that's the best I can do, although I don't see why it would be related to fixing it, but it works now with the main and newest H990N image...
I wonder if my old backups would work with camera and rotation if I installed them... but... I'm not so sure I wanna try... But then again... If so, it would make zero sense. In any case I am now making a backup of the one I know 100% to work with camera and rotation H990N. Then I can always try to restore my old backups and see if the problem is there.
First older backup with the camera and rotation not working, restoring crashed the system now before being restored. *Sigh* Trying the first backup that also had the camera and rotation issue.
Well... At least I got it working, it seems. So, so far so good I guess...
My oldest backup got restored, and the Camera and rotation now works... Seems far out, but it is android so not a big surprize I guess. Faulty by design.
Anyway I will try to restore my second backup again and hope for the best... It must have been the H990DS Rom that fixed something while installing it, although have no idea why, and can make no sense of it.
Got my second backup up restored this time... The Camera and Rotation works... Like... I just don't know what could change here. But it started out working when I installed the H990ds stock so I guess it must have something to do with that, beside that I have no idea.
Seems the sickness went away from one mobile and planted itself on the other... I feel more and more that Satans minions are doing these things... Whatever the case, now my daily working mobile is having Camera problems all of the sudden... This is insane, 2 mobiles which should have nothing to do with each other, one mobile having a camera issue, and solving itself all of the sudden, and now the other mobile is infected... Like, just, just give me a break...
You gotta be kidding me, it now also have the turn issue!... This is utter insanity... Like seriously.... *Sigh* What is going on here.
Thinking seriously that a hammer can fix everything!
I downloaded US996 now that US996 is used so much for the F800 mobiles variants, well my F800K did absolutely not like that, I tried it twice and got nothing. It changes partitions apparently - It never loaded up in the system at all.
Anyway, so knowing that the H990DS stock seemed to have fixed the screen issue and rotation issue on my H990N version, I installed that on the F800K and the system worked, and with camera and rotation, although you need a lower version of TWRP to get through the security nonsense as seems to be standard. Well, the H990DS version worked on the F800K and I wonder if it might be a better choice overall to use for it. But it did look pretty good and no Korean nonsense text. Well... I am now restoring my backup of my former system with the sickness that I made before all this, and see if it has fixed it like it did with my H990N. Need to restore +50 GB because of TWRP programming nonsense and then we will see if the Camera and rotation has sorted itself out.
Interesting if it fixes both variant phones... And maybe then it might be better just to use that version on both phones, not sure...
If it sorts it out at least, I think we have a good indication that the DS version H990ds20b_00_OPEN_AU_DS_OP_1108 is a cure for this sickness, it seems.
The F800K seemed to become more sick and skype did not work and it was terrible slow to respond :/ And then of cause the camera and the rotation did not work either. Not sure what is up with that sadly. Not sure what the overall issue is. Maybe I need to keep to the older versions of TWRP or... Dunno...
But I might try the DS version on both systems, if it fixes the 2 main issues, it might not ever come on it. Maybe... Or maybe it just fixes it overall after having been installed, no idea.
I wonder if twrp-3.2.3-0-h990 might also be used on the F800K - if the US996 is not so compatible with the phone, maybe the TWRP is not so compatible either... And the H990 should be close to the DS and H990N version as far as I know...
Restoration failed.... ohh no.... hmmm - might be that the H990DS is different in regards of partitions I wonder...
I will try again and if it fails again, I will install the right stock image and see if it wanna change some partitions and thereby show if there is anything different which might break the beta full partitioning backup. The foolish nonsense of backing up a lot of empty space. Utter insane, but overall Android is insanity.
I feel that the TWRP programmers are lead by Satan, some of these choices that is found is just outrageous. But if you wipe out the competition you can rule over it all, the same with Magisk if there is no competition then it is easy for them to stir the boat. If programs takes the lead and crush everybody else, then they can begin to play tyrants and promote insanity.
Anyway, most likely will get another fail with the backup, partitioning being different in size or something. As TWRP forces this bull**** on the users, and many other things. But can't complain about it, then the blotting pen comes by here on the forum. Censorship, as always, nothing new these Satanic days of hating Truth.
Anyway, I will fix the F800K image and then restore things, that should do it. Then again, it might be better to jump on that DS image overall... *Sigh*
And see if I can get my data with me... Usually also makes issues, because programmers makes it near impossible for users to easily do what they wanna do.
We can't have to much freedom you see...
58 GB's... insanity and waste of time. Programmers love to put that bull**** on us, Android is faulty by design and the programmers outrageous following blindly along pushing more garbage - oh how I wish the Linux Pine or Librem phones had been closer to running as a daily. I would not be on this Android jail bull****, and insanity land of wasting my time with things which should have taken 1 second to fix without breaking anything and yet ends up taking months. Sick sick sick.
Android seem nothing related to Linux, no freedom, no nothing. Just Tyrant companies and programmers, ads all over and other filth. Well the progress is 42 GB and going, getting close to the breaking point I guess.
XDA is full of ads as well, same as all the website with any android stuff - ugly and disgusting filth. Because no website can be run without any ads, apparently...
Yup the restoration failed... but if the partitioning is different then it is no surprise when TWRP programmers program like drunkards full of demons.
Hopefully will soon have figure this out so I can wipe out windows 10 and get on linux... but using LGUP which is running on windows. Don't think there is a Linux version as far as I know. Okay system installed, although it did not give me any warnings of changing the partitioning... I wonder... If it will now restore my backup and if not... then I am in trouble. As this was my main phone... I should have copied everything from the internal to the Micro SD card before doing this.
Should have taken my precautions as Android never seem to do what is expected of it. Always new wacky loony things incoming from all sides. A backup should work but don't expect it too.... Because, Bull****.
Insanity: doing the same thing over and over again and expecting different results. Albert Einstein
I guess he never tried Android...
The error restoration in TWRP could also be related to the version of TWRP, dunno I might have used the old version. Can't remember, but have to take that into consideration as well... As it did not seem to do anything with any partitioning when I ran the H990N stock image.
In any case the H990N stock image is loaded this time - I will restore it with the old TWRP, and if that fails again try a newer version of TWRP and redo it again again again...
So many factors play in, and downgrading for this and upgrading for that. Because... that's Android.
Well, it restored it although with some errors, but not the overall error. Something about some folders it could not enter, which I have seen before. I don't think it is a problem but... I will just test out the Camera and rotation and then go back and restore it with the newest version of TWRP that I have working and see if I get the same issues. The BIG moment... Have it worked? Rotation works... next... Camera works!
Whatever seems to be the issue the H990ds20b_00_OPEN_AU_DS_OP_1108.kdz takes care of it and one can just return to the former stock version or restore the backup.
And I do wonder if I should just install the H990ds20b version on both mobiles really... Seems to be able to run on both variants of the LG that I have.