Develop Bugs

[Q] Lose Root after Nov 13 Update with WiFi Calling?

Our GS2 and the Amaze 4g are getting an update Nov 13 that will add WiFi Calling. I was wondering if we would lose the existing root and will have to re-root, or what precautions to take? Any tips?

I believe if you're rooted and have deleted some bloat.. you will not receive the ota.. may have to wait for the release and pull the apk so we can get wifi calling goodness..
Sent from my SGH-T989

Ah Crud, The only thing I have uninstaleld with Titanium Backup (I do not have pro so had to uninstall instead of freeze, but I did back it up) was the Tethering Manager so my tethering would work since they pulled some shenaningans on tethering and went ninja on customers tryingto charge them now. Would I hve to restore that then do OTA then uninstall again?
Back to the original question, would my root remain intact so I can go ahead and uninstall right after the OTA? Or would I have to re-Root?

If you made a Nandroid backup before you flashed SU...why don't you just restore that?

I did make a nandroid, does restoring that restore apps and app data to that point? Basically would I lose any apps I have installed since nandroid and its data?

manolodf said:
I did make a nandroid, does restoring that restore apps and app data to that point? Basically would I lose any apps I have installed since nandroid and its data?
Click to expand...
Click to collapse
Yes and yes. You will lose any data/apps you have installed/made after the nandroid backup. My suggestion is to do this before the update.

after removing "tethering manager" can one use simultaneous data on device and phone?
@manolodf after removing tethering manager can you use wifi tether and data on the actual phone simultaneously? While using a MyTouch 4g i was able to accomplish that feat but note i can't replicate on the galaxy s2, i already pay the 14.99/mo but will root and remove that tethering manager if it could enable me to use data on both the wifi tethered device and my phone simultaneously.

@ggfb20 I also came from the MT4G and yes I remember that ability, I do think after removing tethering manager that it is possible, though I cannot tell you with 100% accuracy, but what I can tell you that I did notice since is that the prompt warning you about not being able to use it simultaneously is now gone.
-- I just enabled hotspot and then opened web browser and it worked, so I would be very likely to say that it does work, I just did not have any device actually connected to the hotspot at the same time.

If your rooted you wont be able to take the ota anyway. You have to have the stock recovery to flash or it just errors. Someone will have a rooted rom posted the day of the ota so I wouldn't worry about it.
Sent from my HTC Glacier using XDA App

Ok, primarily my main concern is the WiFi Calling, so I just want to make sure i can either get APK or whatever other bug fixes etc in a rom. Hopefully I wont have to do a full wipe though, thats annoying!

manolodf said:
Ok, primarily my main concern is the WiFi Calling, so I just want to make sure i can either get APK or whatever other bug fixes etc in a rom. Hopefully I wont have to do a full wipe though, thats annoying!
Click to expand...
Click to collapse
If you're going to a different you're gunna have to do a full wipe no matter what...to avoid endless bootloops.

thanks for the info...
I can't wait to root now...well just a little, Ill do so shortly after getting that update on the 13th of November.

I had to retire my G S2 till the WiFi update comes out because I have no Tmobile service at my house. I rooted the S2 but I am positive someone will post the apk that we can install as soon as it come out.
Sent from my HTC Sensation Z710e using xda premium

In case you missed it!
We now have stock recovery thanks to buddy323
So we can go back to stock, to take the update, if we want.
Probably not necessary, I'm sure it will be posted here soon after the update.
[ROM] SGH-T989 // UVKID // Stock // Deodexed // Rooted //Busybox (
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1 2 3 ... Last Page)
Originally Posted By: bubby323
[STOCK] T-Mobile Samsung Galaxy S II Stock Kernel // UVKID (
1 2 3)
Originally Posted By: bubby323
[STOCK] T-Mobile Samsung Galaxy S II Stock Recovery (
1 2)
Originally Posted By: bubby323
Don't forget to thank bubby! Even better donate! No better way to say thank you!

jangst123 said:
In case you missed it!
We now have stock recovery thanks to buddy323
So we can go back to stock, to take the update, if we want.
Probably not necessary, I'm sure it will be posted here soon after the update.
[ROM] SGH-T989 // UVKID // Stock // Deodexed // Rooted //Busybox (
1 2 3 ... Last Page)
Originally Posted By: bubby323
[STOCK] T-Mobile Samsung Galaxy S II Stock Kernel // UVKID (
1 2 3)
Originally Posted By: bubby323
[STOCK] T-Mobile Samsung Galaxy S II Stock Recovery (
1 2)
Originally Posted By: bubby323
Don't forget to thank bubby! Even better donate! No better way to say thank you!
Click to expand...
Click to collapse
Very Useful.

manolodf said:
Ah Crud, The only thing I have uninstaleld with Titanium Backup (I do not have pro so had to uninstall instead of freeze, but I did back it up) was the Tethering Manager so my tethering would work since they pulled some shenaningans on tethering and went ninja on customers tryingto charge them now. Would I hve to restore that then do OTA then uninstall again?
Back to the original question, would my root remain intact so I can go ahead and uninstall right after the OTA? Or would I have to re-Root?
Click to expand...
Click to collapse
Tether manager has nothing to do with the ota. To state it clearly root = no ota. But do not worry. Do not run and unrooted your phone. Do not panic. What ever the update does some one will post it so rooted users can get it. It was the same for the Vibrant.

can i still update if i rooted my phone and i froze the bloatwares? or do i need to un-freeze them?

If you do not have the stock recovery you can't update via ota. You will have to either flash the stock recovery or wait til someone roots it and posts it.
galaxys2noobs said:
can i still update if i rooted my phone and i froze the bloatwares? or do i need to un-freeze them?
Click to expand...
Click to collapse
Sent from my Nexus S using XDA App

ntellegence said:
Tether manager has nothing to do with the ota. To state it clearly root = no ota. But do not worry. Do not run and unrooted your phone. Do not panic. What ever the update does some one will post it so rooted users can get it. It was the same for the Vibrant.
Click to expand...
Click to collapse
Root does nothing to stop OTA updates. You will probably lose root if you run the update, but root does not stop it.

You might get the notification and download but without stock recovery it will not flash.
Astitious said:
Root does nothing to stop OTA updates. You will probably lose root if you run the update, but root does not stop it.
Click to expand...
Click to collapse
Sent from my Nexus S using XDA App

Help Please - Bricked sprint gs3

hey guys hope someone can help. i tried to return my gs3 to stock after rooting it and putting a rom on it, so i used odin and i downloaded the stock tar file from the stock rom thread, and all seemed to go alright but when it rebooted in got stuck on the samsung screen. it shows the sprint bootup thing and galaxy s3 but then gets stuck on samsung screen. i can access download mode and i can install a custom recovery using odin but when i try to just flash a regular custom rom using custom recovery it does the same thing, it boots but gets stuck on samsung screen.
hope someone can help, thanks

Issacbourne said:
hey guys hope someone can help. i tried to return my gs3 to stock after rooting it and putting a rom on it, so i used odin and i downloaded the stock tar file from the stock rom thread, and all seemed to go alright but when it rebooted in got stuck on the samsung screen. it shows the sprint bootup thing and galaxy s3 but then gets stuck on samsung screen. i can access download mode and i can install a custom recovery using odin but when i try to just flash a regular custom rom using custom recovery it does the same thing, it boots but gets stuck on samsung screen.
hope someone can help, thanks
Click to expand...
Click to collapse
Boot into recovery and wipe data/factory reset

and, if you need to start over
http://forum.xda-developers.com/showpost.php?p=32172292&postcount=165

Naddict said:
and, if you need to start over
http://forum.xda-developers.com/showpost.php?p=32172292&postcount=165
Click to expand...
Click to collapse
I doubt he needs ro start over. Its seems he did everything right and just didnt wipe. Bet it boots right up if he wipes/resets

billard412 said:
I doubt he needs ro start over. Its seems he did everything right and just didnt wipe. Bet it boots right up if he wipes/resets
Click to expand...
Click to collapse
yes, but the information can only help ...just in case

Naddict said:
yes, but the information can only help ...just in case
Click to expand...
Click to collapse
Lol not like it matters. 100 bucks says this is one of them posts that never gets a confirmation from the op. Just have that feeling lmao :laugh:

billard412 said:
Lol not like it matters. 100 bucks says this is one of them posts that never gets a confirmation from the op. Just have that feeling lmao :laugh:
Click to expand...
Click to collapse
yuup,
you can either give them too much info, or not enough and there are like, one million posts about something that has already been posted about.
I see you constantly providing the same answers to very similar questions in the Q and A threads...People just don't search..nor read.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

thanks alot worked. i was gettin a little scared there for a sec lol.

billard412 said:
Lol not like it matters. 100 bucks says this is one of them posts that never gets a confirmation from the op. Just have that feeling lmao :laugh:
Click to expand...
Click to collapse
Looks like you lost $100 Sir :laugh:

dbenney said:
Looks like you lost $100 Sir :laugh:
Click to expand...
Click to collapse
Lol.. Did you get your issue worked out?
Sent from my SPH-L710 using xda premium

Naddict said:
Lol.. Did you get your issue worked out?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
yeah i did, it was such a simple thing, i was getting so frustrated cause ive rooted a million phones ya know, thought i knew what i was doing lol...but anyway, thanks again

Thanks from me too. I ran into this after trying to go to LI3 from the LIF JB leak. (LIF worked great for me but I need tethering so I'll have to wait a bit.)

no help so far-please think this through before shooting from the hip
Naddict said:
Lol.. Did you get your issue worked out?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I'm stuck with the dwonload mode showing. No combination of button strokes or battery removals seems to change the screen. The PC cant see the phone anymore. The only thing I can think of to do is let the battery discharge or put another battery in. I could write to the external sd card for whatever help that could offer. I don't know where the internal sd card is, do you? Why there is an sd card and an external sd card? My PC sees the so-called sd card as "phone." I'm feeling totally discouraged and disenchanted.

ODIN is your best friend
alt230 said:
I'm stuck with the dwonload mode showing. No combination of button strokes or battery removals seems to change the screen. The PC cant see the phone anymore. The only thing I can think of to do is let the battery discharge or put another battery in. I could write to the external sd card for whatever help that could offer. I don't know where the internal sd card is, do you? Why there is an sd card and an external sd card? My PC sees the so-called sd card as "phone." I'm feeling totally discouraged and disenchanted.
Click to expand...
Click to collapse
If you have download mode, then you are only soft bricked. You will need to download one of these oneclicks to make things as simple as possible: http://goo.im/devs/billard412/d2spr/ODIN-ONE-CLICKS/LJ7_Jellybean
Attach phone to computer usb, make sure your still in download mode and make sure it says COM (some number). Go take a 10 minute break or so and it will be working again. THANKS TO billard412 for uploading those files

My S3 says "upgrading" all the time

After updating the phone with an ATT update, every time I restart or boot up my device it says that "Android is upgrading". Does anyone have the same issue? How do I get rid of that?

MickeyS said:
After updating the phone with an ATT update, every time I restart or boot up my device it says that "Android is upgrading". Does anyone have the same issue? How do I get rid of that?
Click to expand...
Click to collapse
I suspect that the update didn't go quite right. It says that when the system is rebuilding your cache/dalvik cache. It sounds like maybe one or both of those is getting cleared when you shut down or they may not be getting built properly in the first place. I'd suggest backing up whatever you care about and doing a factory wipe. It can be a bit of a pain, but it'll probably solve your problem.
Also, bring on the details yo. Phone? Android version you came from/upgraded to? Aaaaaanything at all.

I has Android 4.0.4 and the latest update. It's a rooted phone and AT&T is my provider.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Are you running a custom ROM? I agree, you should do a factory reset. Just be sure to back up your data beforehand.

smartnphone said:
Are you running a custom ROM? I agree, you should do a factory reset. Just be sure to back up your data beforehand.
Click to expand...
Click to collapse
No, I am not running a custom rom, all I have done to the phone is root it. What's the best way to back up your data? I useTitanium backup. How do I do a factory reset? I am new to the Android world and don't know much, any help will be greatly appreciated.

MickeyS said:
No, I am not running a custom rom, all I have done to the phone is root it. What's the best way to back up your data? I useTitanium backup. How do I do a factory reset? I am new to the Android world and don't know much, any help will be greatly appreciated.
Click to expand...
Click to collapse
What phone do you have? Titanium backups are fine. Make sure the backups are on an external SD card or get them off the internal flash. If you need to shuffle files around, you can use ES File Explorer but BE CAREFUL if you give it root privs for some reason. No offense, but since you're kinda new to this if you screw up and erase the wrong thing, stuff's gonna break. Without knowing who makes your phone, the best I can tell you is to go into settings and dig around for the factory reset. Good luck!

I fixed the first problem with the factory reset but now I can't connect the phone to my Mac using Android file transfer. Could the update had something to do with it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

MickeyS said:
I fixed the first problem with the factory reset but now I can't connect the phone to my Mac using Android file transfer. Could the update had something to do with it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I don't mean to be a jerk, but for god sake man/woman/person... For the 3rd time, what phone do you have? And yes, that's a good possibility...

He has said a S3 and ATT...I don't understand your question of what phone does he have?
Sent from my SGH-I747 using Tapatalk 2

m3741 said:
I don't mean to be a jerk, but for god sake man/woman/person... For the 3rd time, what phone do you have? And yes, that's a good possibility...
Click to expand...
Click to collapse
He did say s3 att my man.... And if not its in the s3 forum so it'd be a safe assumption it'd be an s3, and carrier for the steps he needs is regardless.
Sent from my SGH-I747 using Tapatalk 2

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Edit: ignore post.

corythug said:
He did say s3 att my man.... And if not its in the s3 forum so it'd be a safe assumption it'd be an s3, and carrier for the steps he needs is regardless.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Apologies... I'm blind as hell apparently. No more late night XDA...

MickeyS said:
I fixed the first problem with the factory reset but now I can't connect the phone to my Mac using Android file transfer. Could the update had something to do with it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Like the other guy said, the update could be a possibility.
Reminds me when I had iPhones before I discovered Android. If you wanted to stay jailbroken, you'd have to make sure it's safe to do so before you update. Like you had to make sure it was iTunes safe, etc.

Did you install Google wallet?
Sent from my SAMSUNG-SGH-I747 using xda premium

So if AT&T has an update and your phone is rooted, don't update? I went ahead and updated without thinking about it. I am an iPhone user and didn't think that ATT had anything to do with Android OS. I took care of the upgrading issue, before the update I was able to use Android File Transfer with my Mac and I would connect to the phone, now forget about it. I can only do it now using VMware Fusion. Kies works but it's kind of limited. My next thing will be to install a ROM, but I can't find exactly what kind of phone I have. I know it's a Galaxy S3 from AT&T.
This is the information:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/attachment.php?attachmentid=1402926&stc=1&d=1350272265
What kind of specific rom's I have to look for, I've herd that if you install the incorrect rom you will brick your phone.

Im not very familiar with mac or iOS but your problem sounds like a driver issue on the mac, not android. Is usb debugging enabled by chance? Settings>developer options>android debugging....if its on try turning off then reconnect your phone. If its off try turning it on and reconnect and see if it changes. Beyond that i would suggest deleting any samsung/android usb device druvers from the mac and reinstalling....although someone with more iOS experience will have to offer some advice in exactly how to do that if you dont know, i certainly dont.
As far as installing AT&T OTA updates with root, its generally not a good idea, especially if you do install a custom ROM. Even on a stock rooted ROM there is a pretty good chance the update will 'fix' your root access and if you are on a custom ROM there is probably an even better chance of screwing up the operating system to the point that it doesn't boot properly, or even brick. Only install updates to your ROM from the developer, and follow any instructions they give on how to apply the update.
Lastly, you are looking for AT&T i747 roms and you also have to pay attention to which version of android you are on as to how you go about installing the ROM. For instance if you are running the stock AT&T ROM and try to install an AOSP based rom without formatting the device you are more than likely to have all kinds of issues, IF the OS even boots properly. I would suggest you take some time to read up and become familiar with the terminology, differences in versions, etc with android before you just dive in. If you are unsure about something ASK SOMEONE...much better to look like a noob than standing in line at AT&T with a bricked phone.

I was under the impression that all of these show that when rebooting, its just a matter of how long it shows this message. I dont think anyone with a stock rom does NOT see this when they boot for a couple of seconds.

Any good place to begin looking for stock ROMS?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

[NOW PUBLIC!] Team Codefire Presents: Project FreeGee!

Please note, this is not compatible with the JB OTA - use the app in the Play store instead for now. Thanks!
Howdy all! So, it's time for me to dig out my release thread template... you know what that means?
The LG Optimus G is now unlocked.
Both the AT&T Version and the Sprint Version have been successfully unlocked with this method.
(To answer your question, if you're wondering, we're going to work on the Canadian version next, then the Korean version)
First off, I'd like to write a few words to LG:
Dear LG, a product will rise and fall on the shoulders of it's community.
If you lock a device, and shut out your community, you lose the backing of a very vocal group of people. When you lose the backing of your community, they no longer recommend your product, and you lose money. HTC has discovered this recently.
Please support your development community, we understand product security plays a role here, but ensure that you cater to your community still.
The second you try to fight your development community by locking them out of your products is the second that I will cease to recommend your products.
Keep this in mind, and I assure you that you will find yourself on the top of the game.
With all of that said, let's get back to the goodies.
What is this?!
This is Project FreeGee, silly!
Have an Optimus G ? This project will allow you to unlock your bootloader, and install whatever you want.
Click to expand...
Click to collapse
How does this work?
For the moment, that is a trade secret. Suffice it to say that we put some ones and zeros in the right places, and good things happen.
This is also my opportunity to say do not allow any OTAs to install without asking if they are compatible. LG could possibly patch this in such a manner that makes it rather hard to ever exploit it again.
Click to expand...
Click to collapse
I'm a skeptic. I demand proof!
Alrighty, here it is:
Once again, taken with my HTC Vivid, that would rather mute me than let me speak.
Damn "nose elimination"! I am not noise, and I will not be silenced! (mmhmhmhpmhmp!!)
Click to expand...
Click to collapse
Okay, I'm game. Where do I get it?
Version 0.3 has a confirmed bug-- camera app crashes phone after a few seconds!
If you have 0.3 installed, simply download this, extract the .zip, and extract the .tar file. Inside the freegee-working directory, you'll find boot-att-freegee.img .
Boot your phone to fastboot, then fastboot flash boot /path/to/boot-att-freegee.img
I will release a quick fix .zip for flashing in CWM tomorrow.
Current Version: 0.5
Changelog:
New in v0.5 Removed LG Security check. You are now free to remove any and all apps.
http://downloads.codefi.re/thecubed/lgoptimusg/sprint/freegee/FreeGee-0.5_Sprint.zip
Currently, the download is Windows-only. I will make a OSX/Linux/Windows version soon!
Click to expand...
Click to collapse
FAQ
Can I flash an OTA after installing this?
No. Flashing an OTA could contain a new bootloader, and it would replace the one we have put on your device. If you flash the new OTA, and it replaces the bootloader but not the boot.img, you could be left in a situation where you could not boot the phone due to a security error. Once you're in that position, the only thing you can do is LGNPST back to stock-- and even then, it is possible that an OTA could enable an anti-rollback feature which would disable LGNPST.
Does this mean I can flash custom ROMs now?
Yes. However, the custom ROM must be made for your device. We're working on a decrapified stock ROM, and AOSP ROMs as well. Be patient for those to come.
Can I install a Nexus 4 system image and boot.img and have it work?
We've tested that, and the answer is no, not yet. Some work needs to be done, but once we figure it out, we'll have a quick and easy AOSP ROM.
Does this mean that we can use the Nexus 4 sources (kernel and android) ?
Short answer: Yes.
This phone is essentially a Nexus 4, with minor differences in GPIOs, memory address space, and partition table layouts.
Kernel source is iffy, since we've got Eco mode and a few other things that actually make me like the Optimus kernel more than the Nexus kernel.
However, this discussion is best suited for a new post.
How can I uninstall this?
I'm working on an easy-uninstall for this as well. Stay tuned for the links...
Click to expand...
Click to collapse
Important Information
To enter bootloader, hold volume UP and power.
Upon entering the bootloader, you will notice that there is no 'menu' to enter fastboot or recovery. Unfortunately, since the stars didn't align properly, we were unable to tell the new bootloader where to load the images that contain the menu from.
In light of that, you'll have to navigate the menu blind. Use the volume keys to change selection, and the power key to select.
The choices are (in order of pressing volume down):
Start - boot the phone normally [already selected]
Restart Bootloader - reboot into the bootloader
Recovery Mode - enter recovery (CWM)
Power Off - powers the phone off
So, to get to Recovery, you would press volume down twice then power.
If you have trouble with this, watch my video below for a demonstration.
Click to expand...
Click to collapse
Instructions!
Please note: this requires root before you can install this! If you haven't rooted your phone yet, now is the time to do so.
Also, ensure that you have ADB drivers installed. This WILL NOT WORK without them.
Before we begin: please make sure you have USB Debugging turned on, your phone is in "Charge Only" mode, and your phone's screen is on and unlocked.
This will allow you to see the root access prompt if your phone asks for it.
Download the .zip from this post
Extract it somewhere on your hard drive
Ensure your screen is on and unlocked
Run the "freegee.bat" script, and follow the instructions.
Do not run this as administrator! the install will fail if you do so.
Once the unlock is complete, check to make sure you have a "backups" folder now in the folder where you put FreeGee. If not, DO NOT REBOOT your phone.
Even a failed unlock will still show the 'congratulations you're unlocked!' text, read the output to see if you have errors!
You should not see any "adb.exe not found" errors, or "tar: invalid magic" errors. Those would be errors in the script.
An error which you can ignore is "No space left on device" after it says erasing old recovery and boot. That's just a side effect of how we clear the old images out.
Click to expand...
Click to collapse
Contact Information
"Mister Cubed, how do I talk to you?"
That's easy! Hop on IRC and join me on Freenode in #lg-optimus-g . I'm in there as IOMonster (or IOMonster_desk, or IOMonster_work, depending on where I am)
There's also a lot of other cool people in there too!
When you hop in IRC, if you've got a question, just ask it. Don't say "halp! i does brick'd my phone, and i dunno wat to does?!!", but rather "can anyone help? my phone is stuck in fastboot mode, and I can't get out of it. I flashed <xyz> and now I'm stuck here."
Asking your full question (even though it might be a long message) helps us figure out the best way to assist you, without us having to lead the conversation and ask all the questions for you.
Also, on IRC (for those of you who have never used IRC) if you say someone's name, it will 'ping' (also called 'highlight') them. This tells us that someone is talking to us. So, if you pop in IRC and say "IOMonster, it worked!", I'll get a notification, and will probably say "that's awesome!" in response.
Click to expand...
Click to collapse
Special Thanks To!
None of this would be possible without the assistance of the following people:
Shelnutt2
g33k3r
kmdm
synergy
jcase
sextape
xboxfanj
...and the support of the entire #lg-optimus-g IRC channel
A project like this is really only a sum of it's parts, and in our case, we're over 9,000!
Please make sure to tell someone on this list that they're awesome if you see them on IRC or (*gasp!*) in real life.
Click to expand...
Click to collapse
All right, that about sums up my post. Did I forget anything? Let me know below...

Thanks to all of u guys for all your hard work!

Here is some proof, this is fully working...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the blurry images, took these from my old OG Evo... But can say its fully unlocked!!!
Nice work thecubed, and shellnut2 on this, thanks for keeping our freedom alive!!!

Does the sprint launch OTA prevent this from working?
Sent from my LG-LS970 using xda app-developers app

Tyederian said:
Does the sprint launch OTA prevent this from working?
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
I've already run the OTA, and had no issues unlocking, or rooting after the OTA...

I am so excited! I cannot wait to get this thing unlocked! :victory:

Sweet super excited

Awesome! Will be donating to the team on pay day thanks guys!
Sent from my PG86100 using xda premium

That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!

Wow! Many thanks to all the devs for their hard work and to the beta testers for their willingness to let their phones be guinea pigs. Very much looking forward to this!
Sent from my LG-LS970 using Tapatalk 2

jblazea50 said:
That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!
Click to expand...
Click to collapse
$55 they charged me $99 and some tax on top of it. how did you pull that off?

Super sweet you guys are awesome!!

Christmas came early this year.
Sent from my LG-LS970 using xda app-developers app

New build is up!
Fixed a typo in my code haha

awesome job, big thanks to everyone.
And I second that $55 question.

jblazea50 said:
That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!
Click to expand...
Click to collapse
How on earth did you get it for $55?

tabormeister said:
How on earth did you get it for $55?
Click to expand...
Click to collapse
Had signed up for phone freedom to get $50 gift card back in February.

So I just ran this and had a couple little panic moment!!
1. While reading the script, SU poped up and I missed the "Grant SU" button on the phone. I still got the backup folder but nothing was in it. I then thought it worked, rebooted, and nothing.
The second time I ran this, I got to the "Grant SU" button in time and all went GREAT!!! This time I had files in the backup folder.
2. When I rebooted into recovery, I tried to make a backup. I hit the backup button and got some message that said "Can't mount backup path". So i tried the backup to internal SD and it worked.
Figured I'd write this in case anybody else had the same moment's I did.
The files on the backup folder are very differnt from what I'm used to so hopefully I did it correctly. I noticed there was an option in CWM to choose the backup format after I'd made my backup, so I'm not sure which format is correct for Restore. I guess I used the default which is .dup.
Thank you very much dev's for this!!!!!:laugh:
---------- Post added at 05:54 AM ---------- Previous post was at 05:25 AM ----------
DO NOT use the camera!!!! It'll crash your phone!!!
I read about it in the ATT section just now, but it's too late for me. So I guess we have this bug also.
OK...so not quite a crash. Held the volume down button and power together and got it to reboot.
Now we just need to have a way to recover our phones if/and/or when we do crash our phones. I know the devs are working on this, as obviously they are the bomb!!!

Tease: Two things brewing that hopefully will be up today. Both directly related to this

Shelnutt2 said:
Tease: Two things brewing that hopefully will be up today. Both directly related to this
Click to expand...
Click to collapse
I'm sure hoping you're referring to my post above. I get alittle wiggy if I don't have a way to fix my phone myself.

Question Corrupted data error message after December update

Hi! Is everyone else here struggling with Corrupted data error message after December update? Pixel asks to wipe data, but even if you do, it still do the same on the next reboot. There's Reddit thread about that going on:
https://www.reddit.com/r/GooglePixel/comments/rfzz6j

Razviar said:
Hi! Is everyone else here struggling with Corrupted data error message after December update? Pixel asks to wipe data, but even if you do, it still do the same on the next reboot. There's Reddit thread about that going on:
https://www.reddit.com/r/GooglePixel/comments/rfzz6j
Click to expand...
Click to collapse
Did you try out the first posts suggestion?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Morgrain said:
Did you try out the first posts suggestion?
View attachment 5483007
Click to expand...
Click to collapse
Yep, didn't work. In the end, safe mode boot worked. Way to fix it:
1. Boot in safe mode (volume down while looking at boot animation)
2. Wifi on in safe mode
3. Open Play Market and update everything
4. Reboot normally.

Razviar said:
Hi! Is everyone else here struggling with Corrupted data error message after December update? Pixel asks to wipe data, but even if you do, it still do the same on the next reboot. There's Reddit thread about that going on:
https://www.reddit.com/r/GooglePixel/comments/rfzz6j
Click to expand...
Click to collapse
Hey! I also experienced this problem. Following the steps about updating Google apps doesn't really help as the error reboot will come again the next time you reboot your phone. Rather, follow Razviar solution that you need to enable airplane mode as soon as your phone boots up and enable wifi. Only after a while you can turn off airplane mode and start using cellular data. That way you'll be able to safely avoid the restart loop.
Never expected such a silly bug on a flagship device. Shame on you, Google!

hafatih27 said:
Hey! I also experienced this problem. Following the steps about updating Google apps doesn't really help as the error reboot will come again the next time you reboot your phone. Rather, follow Razviar solution that you need to enable airplane mode as soon as your phone boots up and enable wifi. Only after a while you can turn off airplane mode and start using cellular data. That way you'll be able to safely avoid the restart loop.
Never expected such a silly bug on a flagship device. Shame on you, Google!
Click to expand...
Click to collapse
I managed to restart the phone once without getting error message, but next reboot failed again. So currently on affected devices we have to do this reboot shaman dance every time we need to reboot.

hafatih27 said:
Hey! I also experienced this problem. Following the steps about updating Google apps doesn't really help as the error reboot will come again the next time you reboot your phone. Rather, follow Razviar solution that you need to enable airplane mode as soon as your phone boots up and enable wifi. Only after a while you can turn off airplane mode and start using cellular data. That way you'll be able to safely avoid the restart loop.
Never expected such a silly bug on a flagship device. Shame on you, Google!
Click to expand...
Click to collapse
Hey guys, I'm also having the exact same problem with my pixel 6 pro December build SQ1D.211205.016.A1. And I can confirm that restarting while airplane mode On prevents the phone from restarting again and crash with "failed to load Android system". I really hope Google acknowledge this problem and fix it in future updates. I posted the issue in google community support and no one replied. I thought I was the only one having this issue. Y_Y

imivantj said:
Hey guys, I'm also having the exact same problem with my pixel 6 pro December build SQ1D.211205.016.A1. And I can confirm that restarting while airplane mode On prevents the phone from restarting again and crash with "failed to load Android system". I really hope Google acknowledge this problem and fix it in future updates. I posted the issue in google community support and no one replied. I thought I was the only one having this issue. Y_Y
Click to expand...
Click to collapse
did you fix your issue? it looks like restarting in safe mode and updating all your google services apps can resolve your issue. if not, flashing the mid-november build can fix it also.

Alekos said:
did you fix your issue? it looks like restarting in safe mode and updating all your google services apps can resolve your issue. if not, flashing the mid-november build can fix it also.
Click to expand...
Click to collapse
I haven't tried restarting with my Internet turned on again. I'll just wait until January or February update by Google and see how it goes. I don't want to do any tinkering with safe mode or flashing of builds because my device is an import set and if I mess up, I'm literally burning the money I've spent on this phone. So, fingers crossed, google acknowledge and fix it in the future. If not, then at least I can still use my phone (if I need to restart, just turn on airplane mode). It's just annoying that such a fundamental bug that causes this kind of OS error happens at Google. Had I known that, I could've applied for a software engineer role there. Probably I'll fix it myself. XD

imivantj said:
I haven't tried restarting with my Internet turned on again. I'll just wait until January or February update by Google and see how it goes. I don't want to do any tinkering with safe mode or flashing of builds because my device is an import set and if I mess up, I'm literally burning the money I've spent on this phone. So, fingers crossed, google acknowledge and fix it in the future. If not, then at least I can still use my phone (if I need to restart, just turn on airplane mode). It's just annoying that such a fundamental bug that causes this kind of OS error happens at Google. Had I known that, I could've applied for a software engineer role there. Probably I'll fix it myself. XD
Click to expand...
Click to collapse
there's a known fix for this. restart in safe mode, enable wifi and update your play services apps (long press on play store icon, my apps, update all). every user I've seen has pretty much fixed it doing this. its an issue with Bluetooth actually.

Alekos said:
there's a known fix for this. restart in safe mode, enable wifi and update your play services apps (long press on play store icon, my apps, update all). every user I've seen has pretty much fixed it doing this. its an issue with Bluetooth actually.
Click to expand...
Click to collapse
Hi, it doesn't work. My apps are all updated. And based on my personal testing, it's not the bluetooth. It's the wifi/mobile network issue. Because when I tested it, my bluetooth was already off. It's the internet (either wifi/mobile network that's causing the restart and crash). I appreciate your help though :'). I'm just always unlucky when it comes to buying hardware. All kinds of hardware I bought always met with issues. I really put such high bar for Google. But unfortunately, it's really a shame and disappointing that such a giant company fails miserably in this kind of thing.

Were you rooted and manually flashed the update? I know of a few things that could cause a similar issue if the update was done manually over fastboot.

NippleSauce said:
Were you rooted and manually flashed the update? I know of a few things that could cause a similar issue if the update was done manually over fastboot.
Click to expand...
Click to collapse
Absolutely not. I don't do such things to an expensive phone

imivantj said:
Absolutely not. I don't do such things to an expensive phone
Click to expand...
Click to collapse
Ahh, gotcha. It's not too risky to do - but is if you know what you're doing / aren't willing to learn before doing it.
Regardless, good luck figuring this out (and Happy Holidays)!