Related
So, I've been ready to throw the Captivate away.
When I originally rooted and loaded Cognition 3.04 (Eclair based), everything worked like a charm. I used it for quite some time and was totally happy. For some reason that escapes me now, I decided to flash back to stock. And there is where my trouble began.
I used the Odin one-click that has the official 2.1 image included (file name I897UCJF6-final-OCD-REV0). That worked OK, but it seems to have disabled my 3 finger salute to recovery mode. This is on a batch 1009 phone.
I stayed with that for a while, and then the official AT&T Froyo came out. Oh my - what a piece of crap that is. I had lags, GPS problems, battery drain, and more.
So, I decided to move to Cognition 4.1.1. The first problem I ran into was rooting. With recovery mode effectively disabled, I ended up using the GalaxyS_One-Click_Root_All_Models file. So, I was rooted.
So I'm thinking load ROM Manager and I'm good to go. Wrong. Seems there is a new version of the boot loader in Froyo that requires ROMs to be signed. Cognition isn't, so it wouldn't load. Various places mention how you can change various things to make the bootloader version 3e look like 2e (which doesn't require signature and is standard on Eclair). None of those worked for me and ended up bricking my phone (AT&T white boot screen hang) from screwing around with system files. Word of advice - know well what you're doing before you patch individual files in ANY operating system.
As luck would have it, I ordered the $10 JiG from Josh over at MobileTechVideos (and boy did it get here fast - we're only about 2 hours away from each other). The JiG got me back to Download mode, so I once again used the one click Odin (see above) to reload Eclair.
With Eclair loaded, I again used the one click root (see above), loaded ROM Manager and proceeded to flash Cognition - or so I thought. Minor detail - CWM wasn't loaded so the installation failed with the error Installation aborted. I used ROM Manager to load CWM. Then I used ROM Manager to load Cognition. Since I dropped back to Eclair, I didn't have to worry about the 2e/3e/signed bootloader issue.
As Cognition 4.1.1 loaded I took notes on what I was seeing. It took longer than I remembered (but then again I was very eager to see this finally work). It did the backup, formatting, installing, and there was a funky message that was hard to read that showed up on a black screen which said "Don't turn off system." After a brief time, the phone rebooted. The white screen came back and stayed on. I'm thinking - great - not again. But as I was waiting, I could hear the phone talking to me (sounding alot like Rosie from the Jetsons) saying something about partition, backup, and 2 minutes ETA). That was a very reassuring message to know I wasn't again bricked.
After a bit, the Galaxy S screen came on. It was on long enough to make me think it was hanging again. I waited it out, and soon thereafter the phone came up.
Cognition 4.1.1 is finally loaded. Now to play with it.
I hope someone finds this story useful. In other words, don't do what I did. But if you do, follow my steps and you should be fine.
In summary:
1 - Flash to stock Eclair
2 - Root
3 - Load ROM Manager from Android Market
4 - Load CWM from ROM Manager
5 - Copy the ROM on to the root of the internal SD card
6 - Use ROM Manager to load the ROM
7 - Wait patiently while it does its thing
Good story...could have done away with some of that worry by reading about the long 1st boot boot times and the VooDoo voices, but your story is the same as lots of people...First time is always a rush and a worry, but glad to see yours worked out, and hopefully people will read your post and then read a lot of the others on here to avoid some of the worry! thanks for the post!
Yeah - that was kinda the point. I've been on the 'net since the late 80s (Ok, so I'm old), so I'm steeped in the "read first ask later" mentality. The problem here is that when I find an interesting post that may relate, it's 150+ pages long. And on page 187 someone says "Yes, didn't you read that 47 pages back?"
Did I make it to page 187? Did I miss the significance 47 pages back? Maybe & probably not.
I just hoped to have enough search keywords in here that someone can find my story and maybe save themselves alot of reading
One word of advice to anyone playing around with root and CFW: $10 isn't alot to pay for insurance that you don't brick your phone. In other words, buy the JiG and be done with it. It really saved my a$$ this time.
thehobster said:
The problem here is that when I find an interesting post that may relate, it's 150+ pages long. And on page 187 someone says "Yes, didn't you read that 47 pages back?"
Did I make it to page 187? Did I miss the significance 47 pages back? Maybe & probably not.
Click to expand...
Click to collapse
You are so correct. That's my only complaint about this forum. Since I've been here, I've learned a lot, but as far as the basic why and how stuff, it's buried amongst umpteen pages. Somewhere it would be nice to have the latest, greatest methods listed without tons of pages of follow-ups which also add the latest, greatest info. Who has time to dig through it all? Not me, which is why my phone is still stock, non-rooted, and non lagfixed.
kb0npw said:
You are so correct. That's my only complaint about this forum. Since I've been here, I've learned a lot, but as far as the basic why and how stuff, it's buried amongst umpteen pages. Somewhere it would be nice to have the latest, greatest methods listed without tons of pages of follow-ups which also add the latest, greatest info. Who has time to dig through it all? Not me, which is why my phone is still stock, non-rooted, and non lagfixed.
Click to expand...
Click to collapse
I wonder if any thought has been given to keeping moderated forums for just this sort of thing? Admins could maintain current data from the threads in all the other forums in the form of basic posts or stickies.
Of course, that would be alot of work for someone...
BTW - after Cognition 4.1.1, I'm loving the phone. Battery drain is gone and lags are gone. I haven't tested the GPS much, but I'm assuming the problems are more hardware than software (which no amount of CFW can fix).
You know all this your not a newbie. I read your post took me 3 days to install 2.2 froyo no pc (mac). I had to do it at work. My first time on this site and 99% of this seems like LATIN to me.
If ur a newb and you haven't watched connexion's videos, DO IT! they're great. I've flashed a couple different ROMs now and feel pretty comfortable with the process. And stay away from official froyo!
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
I ran into similar problems with my phone when flashing. I am running official 2.2 rom with CWM recovery, SuckerPunch #53 Kernel, lagfix installed, and I900 UCGJ2 modem. When I first tried to flash CWM, I kept getting the package unsigned error. So I downloaded the cracked 3e recovery without sign check. I followed the instructions on that post to a tee, rebooted, and hung at white att screen when boot into recovery. To get past this, I removed battery, reinstalled and rebooted. Still stuck at att white screen. Upon hooking back to computer, I ran adb devices command and saw my phone was still in recovery mode. So I typed adb reboot, and my phone came back on. After an hour of having similar results, I finally got the 3e unsigned recovery to work by following these steps:
1. Download recovery file to adb directory on computer
2. Adb push recovery /data/local/tmp
3. Using root explorer, remount /system as rw.
4. Adb shell
5. Chmod 777 /data/local/tmp/recovery
6. Cp /data/local/tmp/recovery /system/bin
7. Chmod 777 /system/bin/recovery
8. Exit from adb shell
9. Unhook from computer
10. Reboot phone.
11. Power phone off.
12. Reboot into recovery by using three button method.
This worked for me, and I had to mess around for an hour to figure it all out. I agree that a centralized location for instructions and information would be wonderful! Would save a lot if headaches, especially for people like me. I am new to smartphones, and I have only had my captivate since mid february. Thus was my first time flashing, and while I am very computer literate and am a self taught programmer, I have no experience in mobile phones. Luckily, android is based on linux, which I am well versed in. I hope this helps someone.
Sent from my SAMSUNG-SGH-I897 using XDA App
Omg gmab aufkm
A wise man once said
I just flashed from Cog 3.1 to Cog 4 too. I love it. Unbelievable what these phones are actually capable of.
TommyZee said:
A wise man once said
Click to expand...
Click to collapse
+1 is exactly what I was thinking when it first hung at att boot logo! I know the method I used is a pain, but it worked for me.
Sent from my SAMSUNG-SGH-I897 using XDA App
Forgive the off topic..it relates! (some of it anyway)
thehobster said:
Yeah - that was kinda the point. I've been on the 'net since the late 80s (Ok, so I'm old), so I'm steeped in the "read first ask later" mentality. The problem here is that when I find an interesting post that may relate, it's 150+ pages long. And on page 187 someone says "Yes, didn't you read that 47 pages back?"
Did I make it to page 187? Did I miss the significance 47 pages back? Maybe & probably not.
I just hoped to have enough search keywords in here that someone can find my story and maybe save themselves alot of reading
One word of advice to anyone playing around with root and CFW: $10 isn't alot to pay for insurance that you don't brick your phone. In other words, buy the JiG and be done with it. It really saved my a$$ this time.
Click to expand...
Click to collapse
I hear ya! Been there many times since my first PC, lol Break it then learn how to fix it instead of learning how to use it first! My first PC was an 8088 cpu with very little ram and only a 5 1/4 floppy drive...but I loved it! got a ram update to 512, then a 300 baud modem...then I got a 40 megabyte Hard Drive, I thought WOW, I will NEVER fill this thing up...lol and a cga monitor...I was king of the hill back then...ran a BBS for a few years...fun times...
My steps to flash a new ROM:
1 - download desired ROM
2 - place ROM on phone
3 - place cwm update.zip in root of internal SD card
4 - power off
5 - download mode
6 - stock eclair Odin
7 - after booted, reboot into recovery
8 - install update
9 - use cwm to install desired ROM
10 - enjoy
You don't have to root, or use ROM manager. Occasionally I toss in a master clear, but not every time. I do however delete every folder on the SD card except my media, ROMs and cwm update.zip.
Sent from my SAMSUNG-SGH-I897 using XDA App
So lets begin with, I have recently bought an SGS I5000 (March 25th). It has since then been working magnificent, until about 4 or 5 hours ago (lagging, force closing, and all that horrid stuff imaginable). I did indeed root via SuperOneClick and have successfully increased the performance. Linpack: 16+ (nearly eighteen at one point) and Benchmark (Antutu): 2,500 slighty above the HTC desire (including overclock; tegrak and (task killing, and freeing up as much space possible etc.). I have NOT however, flashed any kernels or ROMS. Mainly due to the fact that being this is my first official XDA forum post, I have not researched it nor have little to no knowledge of how to. Getting back to the matter at hand. My question(s) to you fellow androidians is: Is there a better way to root my phone using a different root tool? How do I get ROM manager to work? Is applanet worth the (lack) of expense? What is a "shell" root and how do I get it to work? (this part is a bit confusing because the box always pops up saying I have a temp. ADB root, and that I should reboot my phone to get rid of it. Well the problem in that area is that I need root to reboot my phone (even then it still fails to reboot using superuser) and standard reseting also fails miserably. How do I get most of my rooted apps to work? ( I've gotten the standard lagfix:v1+ to work ONE single time and then I turned it off, and it has not worked since and even before then due to not enough free space it tells me). Even though when I check my freespace I have more than enough. So it tell's me, and I was just wondering if anyone has any spare time to help me out? Now the MAIN question is! What can I do (in all general aspects of the android community) to get the ABSOLUTE best out of my mesmerize? Sincerely, David! SGS I5000 (froyo 2.2.2)
Alright you're going to have to be more clear and explain specifically whats going on...First off, did you successfully root the phone or not? If SuperOneClick successfully rooted your phone, then its rooted, thats it. There's no to be messing around in adb.
Sorry your post really is just confusing, I'm simply having a hard time deciding what your situation is.
Secondly, ROM Manager will not work on the Mesmerize, period.
Lastly, I don't know what applanet has to do with anything (it doesn't even require a rooted phone) but FYI, this is not the place to discuss pirating software (which is applanet's primary use). So, just keep that kind of jazz to yourself.
Nvm buddy, figured it out :7 thanks for the reply though! And as for the "blackmarket" apk. I have not used it, but seeing the reply you gave me about it told me everything I needed to know sorry for the confusion, I've had this thing for a month and this is the only time I've needed help, but I've got it worked out now.
No problemo man. Glad you got it up and running.
So all of the root methods for the I535 seem to require flashing a custom filesystem and everything. Right now I don't really want to do any of the more extremes like using custom kernels, CM, or etc, I just want to use a few basic apps that need SuperUser rights (in fact, mainly SetCPU, but I'd like to use TitaniumBackup ideally.) The current method I'm seeing in my searches involves flashing a custom system image and everything via Odin and if anything went wrong and I had to take it back, this is a lot trickier to deal with than just if it merely had some basic exploit or something installed... However, in my searches I thought at least one person alluded to a root only method that doesn't use quite such an extreme method -- or perhaps I've simply misunderstood?
http://forum.xda-developers.com/showthread.php?t=1792342
[ROOT][TOOL][2012-07-24] GS3DebugFSRoot: Root the Verizon GSIII without flashing
Hopefully this helps
sent from my freed beast&ikiller
As the previous guy pointed out, the primary root tool does not involve flashing an image of any sort. It's a three step install and is about the most simple thing you'll ever do on your phone. Its all automated too. And even if you did Odin an image onto your phone via other methods, going back to stock only involves Odin of the stock image. Just to ease your mind....Odin consists of selecting the image and pressing start. Also extremely simple. Good luck and have fun!
Huh. I should have seen that one in my searching. Well, now this thread will show up in searches for the next person and they'll get a link to that thread, lol. Anyway, that was definitely the sort of thing I was looking for. I didn't really want to flash the filesystem and everything. While I will someday go to CM I'm sure, I don't want that day to be today. To be clear, I wasn't afraid of the complexity of Odin or whatever (my previous Android device, an Archos 43, was running a custom firmware even) I just didn't want it to have to actually flash a custom filesystem and everything. This at least appears to be using a far cleaner and simpler method that a factory reset or whatever should revert if it came right down to it, which is what I wanted.
Oh, and unsurprisingly it worked without a hitch even though I had let it do the OTA update (well, others have reported it does, but I'm confirming that it does with this latest update as of today at least.) At least, so far in initial tests it's doing everything it should be doing, including letting me run su from the adb shell. (I don't have time to sufficiently test as I leave for work shortly, but I have already put SetCPU on there and all seems to be well so far.) I was hoping it would fix another issue I was having or I wouldn't have made that update (and of course it did nothing, but oh well.)
Thanks!
EDIT: I guess it must be working. Yesterday my phone spent almost all day not really being used just sitting in my pocket and by the end of the day the charge was down to about 60%. Today it was closer to 90% if anything and I played a couple of games for a bit... I'm forced to admit that I changed a few other things though, so I'm not 100% sure that SetCPU alone did everything. Still, not a bad result all the same...
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
From my first CM experience, I remember a time, where I connected my phone to a computer, went to get.cm, click one or two buttons and watched everything else happen automatically. THAT was an experience worth noting! Perfectly simply and jaw-dropping!
Nowadays, I have to read through several pages of an article, click multiple links, concentrate heavily on the contents, do EXTRA research on google, youtube and other how-to pages, use lots of trial-and-error, work though a bunch of frustration and when I'm lucky, after several hours or sometimes days of work, I can get CM working on a phone. This is unacceptable to a medium-experience user in the year 2016! (Note that I'm not your cookie-cutter idiot being able to repair MacBooks, phones and understanding most things quite quickly compared to normal users.)
1st experience: back in 2013, I believe on my Nexus 5 => Perfect!
2nd experience: S3 neo, 2014: => Horrible! (got it to work, however)
3rd experience: late 2015 on LG G4, waited for a new CM supporting my device forever, although a quick CM was promised. Read though pages and pages of forum threads. Decided not to risk my warranty and get a bad photo app by installing CM rather than an excellent one from stock LG android. (overall, a bad experience again)
4th experience: today on an HTC One M7: Just as bad as before with the exception that I quit out of frustration.
It's absolutely incredible how much effort still need to be brought the the table in order to install CM! I mean seriously now:
1) Installing adb and fastboot (not idiot-proof on Mac OSX)
2) unlocking dev mode on the phone
3) using terminal commands to move files on sdcard (didn't work for me)
4) using bootloader commands on trwp
5) and so on and so on (lots of errors and problems on the way)
These are all not things that people know how to do EVEN IF THEY HAVE DONE THAT BEFORE 1 OR 2 YEARS AGO!!!! What happened to all that simplicity from the nexus 5 2013 era? I know what you are going to say in response to this: "Google/Android makes it much harder to unlock bootloaders/root the phone/and yadayadayaaaa...." But in reality all of this could be developed so much easier to reach a much larger user base. Do you not have any benefits from a larger user base? Do you not want to make CM spread to as many phones in the world as possible? Come on now, you can do SO MUCH better than this!
Well, if you want an elite community with only very few noobies bugging you for support, well then I can understand that. But if not, this thing is just annoying and extremely frustrating!
Please review The Purpose of XDA Assist [Please Read]
This is a place for new users to find their way around XDA.
Thread closed
gsstudios