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/att/freegee/FreeGee-0.5_ATT.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...
Can't wait!
Great work guys! Cant wait to lend a hand getting this to us Canadians!!
Yes!
Sent from my LG-E970 using Tapatalk 2
Here we go. Lets make this LG OG what it should have been from the beginning.
Thanks for all the hard work.
Sent from my LG-E970 using xda premium
Thanks once again to you and the project team for your efforts and congratulations on the work completed so far! I will definitely be a willing participant when you guys get around to the Korean model(s). Unsure how much difference there will be in the 3 carriers' for the Korean devices.
Sent from my LG-F180L using xda app-developers app
woot!
I dont even have an lg og and im excited.
Hey thecubed,
Do you guys have the group set up, so I can donate?:good:
Wooo thanks guys. I'll definitely be donating this Friday when I get paid. This was really quick. =D Great work to the whole team.
Sent from my LG-E970 using xda premium
TheCubed!! You (and your team) are my HERO! Thank you for all your hard work.
Q : Is there an option we need to set that will not allow LG to install any OTA updates without my permission? The last update was pushed to my phone and I had no option to stop it from happening.
Awesome work....can't wait...thank you very much!!
Sweet
Looking forward to the official release. Thanks for the good work.
you guys are awesome
Now I can retire my Inspire 4G. I tend to wait for pretty massive spec bumps to happen before I upgrade, and ditching the landscape sliding qwerty was a big deal. However, I'll be damned to something awful before having a phone incapable of a few dozen GB's of capacity. F*** the cloud.
I'm going to best buy later today. Thank you, thecubed. Ideally I'd just like to subscribe to you on Amazon Payments for a while, otherwise I would forget.
Got it
Globalrebel said:
Q : Is there an option we need to set that will not allow LG to install any OTA updates without my permission? The last update was pushed to my phone and I had no option to stop it from happening.
Click to expand...
Click to collapse
I'm wondering the same..
I'm ordering an LGOG when I get home today. It'll be here by Wednesday most likely.
I'll be in touch on IRC. (OverTheStars)
this is great, I thought about not buying this device until you did this! I was going to wait!
just got the phone ....bring on some pure jelly!!!!
when is this going public?
cant wait lol
Did this make it out yet? How's the testing going?
And now we need some ROM devs.
Related
Alright so there are a few users who are locked on Jelly Bean and are wanting to take the dive of unlocking and installing a custom rom. So I figured I'd put together this little guide to hopefully help y'all out.
I am not responsible for any damage you do to your device. Following this is your choice.This will void your Asus warranty and you assume all responsibility from here on out.
As long as you follow all directions in this guide your device will not be bricked. It will be unleashed to this beast of a tablets max power
Before you continue make sure you:
1. Have the drivers for your device installed on your computer
2. Have made the upgrade to Jelly Bean
3. Have the USB cable for your Prime
4. Have nerves of steel and the ability to read all and follow instructions in this guide.
Useful Information for total beginners: Some people using this guide may not even entirely understand what they are undertaking. This is not acceptable so it's time for some education. Android is a Linux based operating system (in it's self, not direly important information but it's nice background knowledge) which means that there are certain permissions to users. Having "root" permission is like being an "Administrator" on Windows systems. All devices come without "root" permissions as the total new users can do irreparable damage to their device. This is different than unlocking your boot loader. Unlocking your boot loader (in the Transformer Prime's case) is the act of saying to Asus "I willingly give up my devices warranty in exchange for the ability to totally control my device so I can flash custom software". Unlocking does not automatically give a device root permissions. This can only be obtained through an exploit or by flashing the proper thing after unlocking. Since I'm not perfect at wording (and it's best to educate yourself as much as possible on the subject) there is more info here:
http://www.androidpolice.com/2010/0...top-5-benefits-of-rooting-your-android-phone/
http://www.droidforums.net/forum/ga...53-explain-unlocking-boot-loader-rooting.html
Step 1 Download the Unlock tool here: http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_Prime_TF201/#download (navigate to Downloads, then select the OS as Android, then scroll to utilities and expand the menu. Find the unlock tool and download that. Don't worry about the "For ICS only" disclaimer. This has been confirmed working on Jelly Bean). Install this app on your Prime and run it. Connect to a network before doing so and follow all on-screen directions.
Step 2. By this point the unlock tool has done it's job and when you boot your Prime now has a nice "Your device is unlocked" message in the upper left corner of the screen. The next step is to flash a custom recovery image (TeamWin Recovery Project(TWRP) in this guides case). This may sound complicated but there are multiple easy ways to do this.
Option 1: Go to the TeamWin website and download the needed files as directed on the page and follow the instructions on the website to flash TWRP. (http://teamw.in/project/twrp2/93)
Option 2 (easy option): This option flashes TWRP running a file from your Windows computer. The file attached at the bottom of this guide needs to be downloaded and unzipped to your desktop. Once this is done you power of your Prime and turn it back on while holding the volume down button. Once the tab vibrates release the power button but continue to hold the volume down button.
Once this has been done you will see 4 icons pop up. One is the USB symbol. Navigate to that by pressing the Volume Down button until the icon is highlighted and press volume up to select it (the menu will say use Volume Up to navigate but this is incorrect). This will put your device into fastboot mode. Connect your Prime to your computer via the USB cable and open the folder you extracted earlier. Run the Windows Batch File. This will automatically flash the TeamWin Recovery image for the Jelly Bean bootloader.
Now that you have unlocked and have a custom recovery installed you can begin the flashing. To get into your recovery all you do is power up while holding volume down and select the RCK icon. This boots the recovery image and you'll be able to flash, back up, and restore roms. All threads will have a guide on how to flash the rom in the thread so I won't go into detail. I do suggest however, using a microSDcard to store downloaded roms for flashing as it is safer than internal storage. If you are looking to back up your apps then there's this amazing app called Titanium Backup on the Android Market. It's very powerful and can backup your apps as well as user data.
HELP! Something went wrong and I need help: As with all processes there can be issues that arise. Some are common and others are individual. Let's address some common problems for all you who are still nervous about this:
1. Everything seemed to go fine but my Prime won't boot into TWRP
SOLUTION: This problem comes up for a few reasons and is pretty common. A lot of time it's simply a bad download or you have the wrong files. Check the files you have and make sure they are the right ones. If so then download them again. Sometimes a download just gets corrupted. If neither of these solutions worked either try another method of installing TWRP outlined on their website or post here and either I or another helpful person will do everything possible to help
2. When I tried to flash a custom ROM it won't boot:
SOLUTION: Usually this is an issue specific to the ROM you are flashing. The basic list of problems to eliminate are:
1.Ensure you have a good download
2.Ensure you have the proper boot loader for the ROM (i.e. JB boot loader for Jelly Bean ROMs
3. Try reflashing the rom. Sometimes something just doesn't work and the only way to fix it is to reflash
Vocab guide for totally new users:
Rom(s): Basically the operating system of your device.
TWRP: Team Win Recovery Project. Started by developers here at XDA and is a powerful recovery tool.
Brick/bricked device: Developer term for saying your device will no longer work due to software/roms and is basically a very, very expensive brick/paper weight.
FAQ: Q: My device is on Jelly Bean but the unlock tool will not work for me no matter what I do. What's wrong?
A: Asus has some issues as a company and certain people are completely unable to unlock their device no matter what. I suggest contacting Asus with your devices S/N and politely ask for an explanation and see if the issue can be resolved. Many users who have used the Asus RMA have still been unable to unlock afterwards.
Other useful links: http://www.youtube.com/watch?v=-pW05Jf87dg&list=UU7YzoWkkb6woYwCnbWLn3ZA&index=22&feature=plcp
Very comprehensive video guide with a full walkthrough to help all with this process. And of course all users can PM me with questions or ask them here.
SuperSU.zip attached is for those who want to root the stock rom. Any custom rom should already be rooted for you.
Good tutorial ..On your way to becoming a recognized contributer
Sent from my LG-P509 using Tapatalk 2
Unfortunately the unlocking tool doesn't work on my TFP, which currently is fully stock 10.4.2.17 and connected to network through wifi.
Tried rebooting, cold booting, waiting, cursing. Might try smashing it against a wall next.
Strange because I've read about many people confirming the tool working on JB. But no luck for me I guess.
DaLongTjeu said:
Unfortunately the unlocking tool doesn't work on my TFP, which currently is fully stock 10.4.2.17 and connected to network through wifi.
Tried rebooting, cold booting, waiting, cursing. Might try smashing it against a wall next.
Strange because I've read about many people confirming the tool working on JB. But no luck for me I guess.
Click to expand...
Click to collapse
The unlock tool doesn't work for about half the people on this forum. There is a separate thread about the whole unlock tool issue. Its useless. Asus refuses to do anything about it. They suggested RMA for some people to fix the unlock issue but when the tablet was returned, it was still locked. Take a look at the thread.
applesuckz said:
The unlock tool doesn't work for about half the people on this forum. There is a separate thread about the whole unlock tool issue. Its useless. Asus refuses to do anything about it. They suggested RMA for some people to fix the unlock issue but when the tablet was returned, it was still locked. Take a look at the thread.
Click to expand...
Click to collapse
I know. There are several threads concerning the unlock tool. My TFP went RMA 2 times, I was unable to unlock after both RMA's. I had root in ICS, but completely lost it after the JB OTA. I was hoping the recent OTA update would change something about the unlocking problems everyone's having, but for me it didn't change a thing.
The OP would be wise not to state that "Don't worry about the "For ICS only" disclaimer. This has been confirmed working on Jelly Bean". For it has be confirmed working on JB by a few user; many of us are unable to unlock even after the latest OTA.
Nothing works for me: reboot, cold boot, factory reset.
I desperately want to installl a custom rom on my TFP to see if that unleashes it's full potential. Right now I own a HTC One X+, which has the same cpu as the TFP but it's many times faster, smoother and less annoying. I still believe the TFP has the potential to be what it was intended to be, but ASUS software isn't going to do that for us.
DaLongTjeu said:
I know. There are several threads concerning the unlock tool. My TFP went RMA 2 times, I was unable to unlock after both RMA's. I had root in ICS, but completely lost it after the JB OTA. I was hoping the recent OTA update would change something about the unlocking problems everyone's having, but for me it didn't change a thing.
The OP would be wise not to state that "Don't worry about the "For ICS only" disclaimer. This has been confirmed working on Jelly Bean". For it has be confirmed working on JB by a few user; many of us are unable to unlock even after the latest OTA.
Nothing works for me: reboot, cold boot, factory reset.
I desperately want to installl a custom rom on my TFP to see if that unleashes it's full potential. Right now I own a HTC One X+, which has the same cpu as the TFP but it's many times faster, smoother and less annoying. I still believe the TFP has the potential to be what it was intended to be, but ASUS software isn't going to do that for us.
Click to expand...
Click to collapse
The issue is not Jelly Bean. The issue is sometimes the servers Asus uses to cross check your serial numbers loses some peoples S/N's. Without a registered S/N the unlock tool will not work. This is the fault of Asus and has been discussed many times. Developers have even decompiled the unlock tool and tried to reverse engineer it to solve this issue to no avail. Please, feel free to do some research if you doubt my answers. Many have spent hours doing so to only find out what they've been told.
McJesus15 said:
The issue is not Jelly Bean. The issue is sometimes the servers Asus uses to cross check your serial numbers loses some peoples S/N's. Without a registered S/N the unlock tool will not work. This is the fault of Asus and has been discussed many times. Developers have even decompiled the unlock tool and tried to reverse engineer it to solve this issue to no avail. Please, feel free to do some research if you doubt my answers. Many have spent hours doing so to only find out what they've been told.
Click to expand...
Click to collapse
I don't doubt your answer, I had never heard about any server-related issues though. Lots of people reported that their Prime's somehow had forgotten their serial numbers, but mine still has it's serial number. Also I registered my S/N online and it's still there, but I don't think that's related in any way. I RMA'd twice, I'm able to get OTA fm updates (possibly a clue that there are no server-side issues with my S/N), but now I'm unable to unlock.
Your guide is great and I really hope it helps many users unlock their Primes so they can get rid of the stock rom and flash a proper one onto their devices. You might want to insert a note though, that even though the unlock tool has been confirmed to work on some JB-primes there's still a chance it won't work (whatever the reason is).
OK let's stop squabbling about semantics here. Fact of the matter is that whoever's able to unlock at this point is quite lucky. The rest of us will just have to wait until ASUS fixes the issues or some whizzkid with too much time on his hands does.
You are a Gem, this finally made the process so much clearer
Shizbazki said:
You are a Gem, this finally made the process so much clearer
Click to expand...
Click to collapse
Thank you feel free to hit the thanks button
Sent from my Zio using xda app-developers app
Hi. I did all the steps you mentioned. In flashing TWRP I chose the 2nd option and everything went great.
The problem appears when I want to go to my recovery (power up holding volume down and then RCK) I get the droid with exclamation mark and nothing happens. Flashing recovery was succesful and I dont have an idea what could went wrong. I'm bit a new user of TF201 so would be grateful if You can help me
EDIT: Ah, I saw now that recovery is not flashing properly, saying sth like InvalidState.
EDIT 2: Ok I handled it myself, thanks again for the guide it was very useful!
Flashed Androwook this morning. Thanks for the painless guide.
Annoyed that nvflash isn't supported on Jelly Bean though. Now that I've flashed, can I get it?
GS_Dan said:
Flashed Androwook this morning. Thanks for the painless guide.
Annoyed that nvflash isn't supported on Jelly Bean though. Now that I've flashed, can I get it?
Click to expand...
Click to collapse
Nvflash is only available to users who did it while on ICS.
Sent from my Zio using xda app-developers app
McJesus15 said:
http://forum.xda-developers.com/showthread.php?t=1998359
Link to my guide thread in the general forum. If anybody has any questions you can PM me or comment there and it'll likely be answered quickly. I'll gladly guide anyone through this process if they need other information.
Click to expand...
Click to collapse
well, I'm unlocked and TWRPed, but what I would really like is root on my stock before flashing AW. So I can install and use TB for the apps...? (I'm on most current updated stock.)
BTW, your lil guide is stupendous. Stupid easy and took minutes. TYVM! I have only vaguely been following the TP forums, stock was fine enough for me, until recently. Was bored of flashing my phone and got the itch today to try something new with the TP. Did a backup, and ready to try some Wookie! Just that lil app issue, cause I'm lazy.
EDIT: correct me if I'm wrong, but after a bit of research (go figure!) it would appear that both Sparky and debugfs won't work on JB/most current stock? Tough sh** for me?
kingdazy said:
well, I'm unlocked and TWRPed, but what I would really like is root on my stock before flashing AW. So I can install and use TB for the apps...? (I'm on most current updated stock.)
BTW, your lil guide is stupendous. Stupid easy and took minutes. TYVM! I have only vaguely been following the TP forums, stock was fine enough for me, until recently. Was bored of flashing my phone and got the itch today to try something new with the TP. Did a backup, and ready to try some Wookie! Just that lil app issue, cause I'm lazy.
EDIT: correct me if I'm wrong, but after a bit of research (go figure!) it would appear that both Sparky and debugfs won't work on JB/most current stock? Tough sh** for me?
Click to expand...
Click to collapse
Once unlocked you can root with a flashable zip. Can't link to one but they're easy to find here on the TFP forum
Sent from my Zio using xda app-developers app
So this would be su.zip (or whatever it's called), and have the following structure?
su.zip
META-INF/
CERT.RSA
CERT.SF
MANIFEST.MF
COM/
GOOGLE/
ANDROID/
update-binary
updater-script
system/
app/
Superuser.apk
bin/
su
I just want to confirm if the file I found is correct or not. Does it need to be for a specific tablet/system? If it was just the app folder and the su binary I wouldn't ask, but the inclusion of metadata has me concerned as I can't seem to find one for the prime specifically.
EDIT: Yup, that's it. I stuck it on the internal storage, went into TWRP, choose "install", navigated to the zip, and it went without a hitch (installed the su binary and superuser app, effectively rooting the system).
Overall, this a good process for people that just want to root without all the hassle of replacing the whole OS.
the unlock tool failed to unlock on my tab... i think its because i did an RMA and asus changed the board inside the device..
GS_Dan said:
Flashed Androwook this morning. Thanks for the painless guide.
Annoyed that nvflash isn't supported on Jelly Bean though. Now that I've flashed, can I get it?
Click to expand...
Click to collapse
What do you think of androwook? Is much better than stock JB?
BashYaBro said:
the unlock tool failed to unlock on my tab... i think its because i did an RMA and asus changed the board inside the device..
Click to expand...
Click to collapse
Try contacting Asus.
sauliiin said:
What do you think of androwook? Is much better than stock JB?
Click to expand...
Click to collapse
Androwook 1.4 turns the prime into the tab it should be. Out scores stock by a lot on benchmarks
Sent from my Zio using xda app-developers app
sauliiin said:
What do you think of androwook? Is much better than stock JB?
Click to expand...
Click to collapse
Very fast, responsive. With the exception of the broken search (there is a fix), and a few other minor issues, I would not hesitate to flash it. Ver 1.5 is right around the corner with several things fixed, and apparently there will be a flashable update from 1.4.
mrwookie6379 said:
Just to give you guys a heads up I will be releasing v1.5 fairly soon to take advantage of the new update that is out but before anyone groans about only having just flashed v1.4 I will release it as an update to those already on v1.4 but also as a full ROM for those who want to skip v1.4 and go straight to v1.5.
Beta 1 for v1.5 was created this PM and is being uploaded for testing now so watch this space.
Click to expand...
Click to collapse
Awesome.
kingdazy said:
Very fast, responsive. With the exception of the broken search (there is a fix), and a few other minor issues, I would not hesitate to flash it. Ver 1.5 is right around the corner with several things fixed, and apparently there will be a flashable update from 1.4.
Awesome.
Click to expand...
Click to collapse
I really ansious about flashing androwook... Just have to found some time!! Thinking about doing it this weekend!
Well.... So do you think really worths the upgrade to Androwwok? I saw that the search bug has a fix, but are there too many other bugs?
And, the performance, is really much better?
Thansk for the answer, friend.
regards
INTRODUCTION
THIS IS A DETAILED GUIDE TO SHOW YOU HOW TO ROOT, BOOTLOADER-UNLOCK AND INSTALL CUSTOM RECOVERY AND ROMS ON YOUR LG OPTIMUS G E970/1/3 with a Windows PC. I will add to/edit it as necessary, and will probably beautify it a bit soon enough as well.
Disclaimer: This has worked successfully for many people on these devices, including myself on the E971. Having said that, I’m not responsible for any explosions or any other form of destruction you may end up with as a result of using this guide!
Click to expand...
Click to collapse
The Dropbox files I’ve linked here are from my own account, so rest assured everything is safe. I will be posting mirrors soon (or replacing if necessary).
A full list of “thanks” will be at the end.
PLEASE follow all the instructions carefully. I will try to help as much as I can, but I am in no way a developer. Just a guy who loves messing with stuff, especially these awesome devices. The #lg-optimus-g IRC chanel is always great help along with great folks here.
---
PRE-GAME CHECKLIST
COMPUTER PREP – Install the following before proceeding any further. If you know for sure you’ve got these taken care of, go ahead to the next section.
1) ADB/FASTBOOT/APX DRIVER - DOWNLOAD: https://www.dropbox.com/s/v7duwo5l09dky8n/Universal_Naked_Driver_0.72.zip
- This driver, in part, is needed for your phone to properly communicate with the PC for our needs. That goes for any Android device, so this is definitely a must have. For more details and discussion/help > http://forum.xda-developers.com/showthread.php?t=19960512) LG DEVICE DRIVER - DOWNLOAD: https://www.dropbox.com/s/dho1z4hdkyezkgp/LGUnitedMobileDriver.zip
- Just like most USB devices, your phone relies on this to communicate with your PC.3) Make sure you have 7Zip, WinRAR, WinZIP or another similar application installed on your computer to be able to extract archives.
- Download 7zip here: http://www.7-zip.org/download.html
PHONE PREP - you will need the USB cable, and your phone needs to have internet connection for the bootloader unlock section. I recommend having JellyBean installed already, the OTA upgrade method is fine with stock before you use this guide. I haven't tried or had any info on anyone else trying this with stock Ice Cream Sandwich, so I'm not sure about the compatibility there.
MEAT AND POTATOES
-ROOT-
1) Download the root package here > https://www.dropbox.com/s/fib80m6q9jzcj4t/ZV9-ZVB-Universal-Root.zip > and extract it to a folder.
2) Connect your phone to your computer with the USB cable and CHANGE THE CONNECTION TYPE TO “CHARGE ONLY” IN NOTIFICATIONS. This is important for the next step.
3) Open the folder you extracted to and double click the batch file “CurrentRoot” or “CurrentRoot.bat”.
4) The on-screen instructions are pretty clear for this part. To sum it up:
a. You’ll need to wait for the phone to be recognized, then you’ll be asked to change the USB mode to “MTP” - you must do this in order to proceed. Press Enter.
b. You may see some error and “daemon” messages along the way here. Don’t be alarmed by those, focus on the prompts.
c. Once you see “uid=0(root) gid=0(root)” you will be prompted to press Enter again. If you don’t get that, reboot your computer and repeat from step 2.
d. At the end, you should see a message that says you’ve been properly rooted. Press any key to continue, your phone should automatically be rebooted (if not, manually do so).
e. Open your app drawer and run the app called SuperSU and ensure it runs with no errors. *IF YOU DON'T HAVE SuperSU IN YOUR APP DRAWER, DOWNLOAD/INSTALL/RUN IT FROM THE PLAY STORE!*
f. You can download any root-required app from the Play Store (Root Checker is easy if you can’t think of one) to verify that you are properly rooted. Congratulations!
-UNLOCK BOOTLOADER AND INSTALL CUSTOM RECOVERY-
This section is done through an app, right in the Play Store thanks to Project FreeGee (XDA thread for thanks - http://forum.xda-developers.com/showthread.php?t=2001655). If you can, make sure to go there and give thanks to thecubed (and Shellnutt2) for this amazing app and all their efforts. Please get the $1 version if you can as well, it’s beyond worth it.
Head on over to the Play Store and download the app “FreeGee **ROOT Required**” or do it on your PC - https://play.google.com/store/apps/details?id=edu.shell.freegee&hl=en ($1 – if you can this would be the one to go for) OR https://play.google.com/store/apps/details?id=edu.shell.freegee_free&hl=en (free version). Run the app and grant it root permissions. FOLLOW THESE INSTRUCTIONS CAREFULLY!
1) In the app, ignore the main buttons and click Menu > SBL Unlock method.
2) Click “Get Unlock Code” – a browser window will open up. Here will be a hardcore disclaimer by Shelnutt2, and it should be taken seriously since there IS a possibility of something going wrong. The chances are EXTREMELY SLIM, but the disclaimers have to be put in place.
3) Enter your name (username for forums is the best way to go), click the checkbox, enter the CAPTCHA, and click “Submit”.
4) The next page will have your code. Copy it and go back to the FreeGee app.
5) Paste the code into the field and click “ok”. You should get a confirmation message that you’ve enabled the SBL Unlock method.
6) On the app’s main screen, click “Unlock my phone” and wait for the download to finish.
7) You’ll be asked to choose a recovery version. I personally use ClockworkMOD, but many people like TWRP. It shouldn’t make a difference at the end of the day, you can look into both and decide if you’d like. Choose one, and proceed through all the dialogue boxes, accepting everything. Your phone will eventually reboot.
8) To verify this was done properly, after the reboot you can reboot again into recovery mode. The easy way to do this is to download QuickBoot from the Play Store and use that. Otherwise:
a. Power off your phone
b. Press and hold the PWR button, while holding down the VOL-UP/VOL-DOWN buttons at the same time (I’ve seen VOL-UP/PWR as instructions, I haven’t been able to get it to work myself like that but YMMV).
c. You’ll see a black screen with some small writing in the bottom-left corner. Nothing will actually respond on-screen at this point, don’t worry.
d. Press VOL-DOWN twice, then press PWR.
e. Your custom recovery should now boot up. Here, you can backup your current software (DO THAT RIGHT AWAY), reboot the phone into whichever mode you want, and install custom ROMs (more and that after the break).
JOB WELL DONE. NOW WHAT DO YOU DO?
The very first thing I recommend you do is BACKUP YOUR EFS PARTITIONS!! Head over to this thread by autoprime on XDA: http://forum.xda-developers.com/showthread.php?t=2161611&highlight=efs - this is important to have in case things go wrong down the road.
Now you have the freedom to do quite a bit, most notably install custom ROMs. It’s important to read through the entire original post of a ROM’s thread. The developer has put everything there for a reason, follow it to the tee! Methods of installation for ROMs may slightly vary. Use the files they link only and don’t stray from their installation instructions.
A loose reference to the most common method is:
a. Wipe data/factory reset
b. Wipe cache
c. Wipe dalvik cache
d. Install ROM file
e. Install GApps file
f. Wipe data/factory reset again (usually good measure regardless)
g. Reboot system
USEFUL INFO AND LINKS (more to come)
I cannot stress how crucial backups are. Back EVERYTHING up, and keep them in more than one place. Much, much better safe than sorry. Titanium Backup is your best friend, check it out.
https://www.dropbox.com/s/cbxid5abrqwkqe5/fix_nfc.zip - NFC fix for CANADIAN phones (E971/3) - this is important as pretty much any ROM you flash that was made for the E970 onto an E971/3 (which is not an issue) will have NFC problems. Simply flash this through recovery AFTER the initial reboot of the ROM.
http://forum.xda-developers.com/showthread.php?t=2010624 - Guide to unbrick your phone! This worked well for me when I bricked back in the day!
http://forum.xda-developers.com/showthread.php?t=2230994 - Another (awesome) method of restoring your phone if it gets messy (can only vouch for E970 based on the thread there) - has had much success.
http://forum.xda-developers.com/showthread.php?t=2181103 - Thread for original root method, good for help.
---
THANKS!
- carrett (original guide that, in part, inspired this one)
- 1wayjonny (original thread for ADB/FB/APX driver)
- fiddy619 (original thread for root method)
- thecubed (project FreeGee - enough said)
- Shelnutt2 (project FreeGee - enough said)
- kentek (source for awesome LG driver)
- autoprime (author of the EFS backup guide and general LG OG God status)
- Paulicat (responsible for much of my (yet limited) wisdom regarding this device)
+ Anyone directly or indirectly responsible for anything in that list who I've left out.
+ Sorry to anyone else I've missed, please send me a quick message and I'll add you in, and I will add in as I go if I remember more.
+ The awesomeness of the #lg-optimus-g IRC channel and everyone in it - check it out on http://webchat.freenode.net!
Reserved.
Sent from my Optimus G using xda app-developers app
How does this differ from carrett's thread that's been stickied at the top of this forum for 10 months or so?
http://forum.xda-developers.com/showthread.php?t=2006946
dbgeek said:
How does this differ from carrett's thread that's been stickied at the top of this forum for 10 months or so?
http://forum.xda-developers.com/showthread.php?t=2006946
Click to expand...
Click to collapse
It was initially written to be put on the CM wiki to have the instructions there. I made it very detailed and specific with everything contained within it, so I figured it would be good for beginners and other users alike. Another reason is that I noticed the Canadian E971/3 didn't have a guide in that section. Since it applied to the E970 as well, I thought I'd share it.
hv6478 said:
It was initially written to be put on the CM wiki to have the instructions there. I made it very detailed and specific with everything contained within it, so I figured it would be good for beginners and other users alike. Another reason is that I noticed the Canadian E971/3 didn't have a guide in that section. Since it applied to the E970 as well, I thought I'd share it.
Click to expand...
Click to collapse
Solid post dude, your attention to detail is top notch!!! Thanks for taking the time to help people out, keep up the great work!!!
Sent from my Nexus 4 Pimpin AOSPA 3+
Thank you sir!
Sent from my Optimus G using xda app-developers app
Great job on the write up. I never got a chance to check it out since the casa is loco when I get home (weekend night drinking is the only time I get and at "work", I'm on irc). Thanks for taking the time detailing everything for the noobies and for those of us that have the occasional brain fart.
Sent from my Optimus G using xda app-developers app
Does this mean
ATT Optimus G Roms work on Canadian Optims Gs?
jnhsd0319 said:
Does this mean
ATT Optimus G Roms work on Canadian Optims Gs?
Click to expand...
Click to collapse
Yup. They seem to be identical except for NFC. YMMV of course but all should be well. Just always back up! Make sure you flash the NFC fix after installing an AT&T ROM to make it work and to ensure you don't get bad battery drainage.
Sent from my Optimus G using xda app-developers app
mikeylikey said:
Great job on the write up. I never got a chance to check it out since the casa is loco when I get home (weekend night drinking is the only time I get and at "work", I'm on irc). Thanks for taking the time detailing everything for the noobies and for those of us that have the occasional brain fart.
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Thank you for the feedback, much appreciated!
Sent from my Optimus G using xda app-developers app
Hello guys,
Thanks for the guide. However I am having trouble getting my device recognized by the program. I have downloaded the files in order, including the LG drivers. I have only rooted phones the old school way on a g1 and a g2x from t-mobile.
EDIT: Sorry, I had forgot to have USB debugging enabled. Brand new phone and I forgot to enable it.
hv6478 said:
Yup. They seem to be identical except for NFC. YMMV of course but all should be well. Just always back up! Make sure you flash the NFC fix after installing an AT&T ROM to make it work and to ensure you don't get bad battery drainage.
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Hello, sorry to bother you again
I was just wondering if international optimus G roms can be flashed or is it just AT&T roms?
Also do you have a link to NFC fix?
Thank you so much!
jnhsd0319 said:
Hello, sorry to bother you again
I was just wondering if international optimus G roms can be flashed or is it just AT&T roms?
Also do you have a link to NFC fix?
Thank you so much!
Click to expand...
Click to collapse
Not a bother at all!
Make sure you do NOT flash any international ROMs, made for E975 for example. They are not compatible.
NFC fix is here. I have added it to the OP.
hv6478 said:
Not a bother at all!
Make sure you do NOT flash any international ROMs, made for E975 for example. They are not compatible.
NFC fix is here. I have added it to the OP.
Click to expand...
Click to collapse
Thank you so much for the answer.:good::good:
Ive been looking thoroughly in the forum to root/install custom roms for my phone. Just being really careful before hand because Im worried about my warranty.
Anyways
May I ask you another question? you seem to know your stuff and helpful :laugh:
If its ok, I was wondering if I can remove root and relock the bootloader if i flash a kdz file for my phone.
Is flashing kdz only changing the ROM or does it literally reset the device back to original factory option? (for warranty service)
Thank you and have a nice day!
hv6478 said:
Not a bother at all!
Make sure you do NOT flash any international ROMs, made for E975 for example. They are not compatible.
NFC fix is here. I have added it to the OP.
Click to expand...
Click to collapse
No problem!
The KDZ method WILL relock everything and bring it back basically to a factory phone. Just make sure you are using the correct KDZ file for your phone and you follow all instructions fully.
Sent from my Optimus G using xda app-developers app
When I'm in the freegee app I click menu and select sbl. In your instructions it says click get unlock code. I do not see this any where. After selecting sbl.
Sent from my LG-E970 using xda app-developers app
right now i am on e97011c software .,..
now i want to update to jellybean so i have downloaded jellybean rom from here ..
http://forum.xda-developers.com/show....php?t=2158144
it's a SnowJB v1.1 [2/20/13][STOCK][DEODEX]
So what will i have to do?
I have touch CWM install so i have to flash directly by going into recovery or not?
I am on ICS version e97011c rooted...
please help guys
hv6478 said:
INTRODUCTION
-UNLOCK BOOTLOADER AND INSTALL CUSTOM RECOVERY-
This section is done through an app, right in the Play Store thanks to Project FreeGee (XDA thread for thanks - http://forum.xda-developers.com/showthread.php?t=2001655). If you can, make sure to go there and give thanks to thecubed (and Shellnutt2) for this amazing app and all their efforts. Please get the $1 version if you can as well, it’s beyond worth it.
Head on over to the Play Store and download the app “FreeGee **ROOT Required**” or do it on your PC - https://play.google.com/store/apps/details?id=edu.shell.freegee&hl=en ($1 – if you can this would be the one to go for) OR https://play.google.com/store/apps/details?id=edu.shell.freegee_free&hl=en (free version). Run the app and grant it root permissions. FOLLOW THESE INSTRUCTIONS CAREFULLY!
1) In the app, ignore the main buttons and click Menu > SBL Unlock method.
2) Click “Get Unlock Code” – a browser window will open up. Here will be a hardcore disclaimer by Shelnutt2, and it should be taken seriously since there IS a possibility of something going wrong. The chances are EXTREMELY SLIM, but the disclaimers have to be put in place.
3) Enter your name (username for forums is the best way to go), click the checkbox, enter the CAPTCHA, and click “Submit”.
4) The next page will have your code. Copy it and go back to the FreeGee app.
5) Paste the code into the field and click “ok”. You should get a confirmation message that you’ve enabled the SBL Unlock method.
6) On the app’s main screen, click “Unlock my phone” and wait for the download to finish.
7) You’ll be asked to choose a recovery version. I personally use ClockworkMOD, but many people like TWRP. It shouldn’t make a difference at the end of the day, you can look into both and decide if you’d like. Choose one, and proceed through all the dialogue boxes, accepting everything. Your phone will eventually reboot.
8) To verify this was done properly, after the reboot you can reboot again into recovery mode. The easy way to do this is to download QuickBoot from the Play Store and use that. Otherwise:
a. Power off your phone
b. Press and hold the PWR button, while holding down the VOL-UP/VOL-DOWN buttons at the same time (I’ve seen VOL-UP/PWR as instructions, I haven’t been able to get it to work myself like that but YMMV).
c. You’ll see a black screen with some small writing in the bottom-left corner. Nothing will actually respond on-screen at this point, don’t worry.
d. Press VOL-DOWN twice, then press PWR.
e. Your custom recovery should now boot up. Here, you can backup your current software (DO THAT RIGHT AWAY), reboot the phone into whichever mode you want, and install custom ROMs (more and that after the break).
/QUOTE]
My big ass question is why we have to download this project thing and pay money! when you can just download clockwork recovery.apk and just adb install it. and plus im not signing up for crap because i just don't feel like haveing to type my stupid google info. and plus it anoys the hell out of me the phone is totaly mirrored of samsung with the default os.
Is there a way to network unlock the phone?
Click to expand...
Click to collapse
manojcitc said:
right now i am on e97011c software .,..
now i want to update to jellybean so i have downloaded jellybean rom from here ..
http://forum.xda-developers.com/show....php?t=2158144
it's a SnowJB v1.1 [2/20/13][STOCK][DEODEX]
So what will i have to do?
I have touch CWM install so i have to flash directly by going into recovery or not?
I am on ICS version e97011c rooted...
please help guys
Click to expand...
Click to collapse
So sorry for late reply.
In your case, you actually need to follow the entire method in the original post as it seems. If you're still on stock firmware, you need to unlock before you can install any custom software.
HelmetDoe said:
hv6478 said:
INTRODUCTION
-UNLOCK BOOTLOADER AND INSTALL CUSTOM RECOVERY-
This section is done through an app, right in the Play Store thanks to Project FreeGee (XDA thread for thanks - http://forum.xda-developers.com/showthread.php?t=2001655). If you can, make sure to go there and give thanks to thecubed (and Shellnutt2) for this amazing app and all their efforts. Please get the $1 version if you can as well, it’s beyond worth it.
Head on over to the Play Store and download the app “FreeGee **ROOT Required**” or do it on your PC - https://play.google.com/store/apps/details?id=edu.shell.freegee&hl=en ($1 – if you can this would be the one to go for) OR https://play.google.com/store/apps/details?id=edu.shell.freegee_free&hl=en (free version). Run the app and grant it root permissions. FOLLOW THESE INSTRUCTIONS CAREFULLY!
1) In the app, ignore the main buttons and click Menu > SBL Unlock method.
2) Click “Get Unlock Code” – a browser window will open up. Here will be a hardcore disclaimer by Shelnutt2, and it should be taken seriously since there IS a possibility of something going wrong. The chances are EXTREMELY SLIM, but the disclaimers have to be put in place.
3) Enter your name (username for forums is the best way to go), click the checkbox, enter the CAPTCHA, and click “Submit”.
4) The next page will have your code. Copy it and go back to the FreeGee app.
5) Paste the code into the field and click “ok”. You should get a confirmation message that you’ve enabled the SBL Unlock method.
6) On the app’s main screen, click “Unlock my phone” and wait for the download to finish.
7) You’ll be asked to choose a recovery version. I personally use ClockworkMOD, but many people like TWRP. It shouldn’t make a difference at the end of the day, you can look into both and decide if you’d like. Choose one, and proceed through all the dialogue boxes, accepting everything. Your phone will eventually reboot.
8) To verify this was done properly, after the reboot you can reboot again into recovery mode. The easy way to do this is to download QuickBoot from the Play Store and use that. Otherwise:
a. Power off your phone
b. Press and hold the PWR button, while holding down the VOL-UP/VOL-DOWN buttons at the same time (I’ve seen VOL-UP/PWR as instructions, I haven’t been able to get it to work myself like that but YMMV).
c. You’ll see a black screen with some small writing in the bottom-left corner. Nothing will actually respond on-screen at this point, don’t worry.
d. Press VOL-DOWN twice, then press PWR.
e. Your custom recovery should now boot up. Here, you can backup your current software (DO THAT RIGHT AWAY), reboot the phone into whichever mode you want, and install custom ROMs (more and that after the break).
/QUOTE]
My big ass question is why we have to download this project thing and pay money! when you can just download clockwork recovery.apk and just adb install it. and plus im not signing up for crap because i just don't feel like haveing to type my stupid google info. and plus it anoys the hell out of me the phone is totaly mirrored of samsung with the default os.
Is there a way to network unlock the phone?
Click to expand...
Click to collapse
You don't need to pay. There is a fee version of FreeGee available as indicated.
LG released the device with their own software - it was not the work of anyone here - if you don't like it, that is what XDA is here for! Welcome!
You need to first be able to access recovery and adb properly to push recovery.apk. Not to mention I'm not sure of any steps prior to that to make your phone ready to do so. That is a totally different guide. If you wish to use THIS method, everything you need is here.
Click to expand...
Click to collapse
Just got my phone yday. I've scoured the Ascend Mate2 threads, and al I see are questions about re-rooting the Lollipop build. Since it looks like Huawei has rescinded their Lollipop ROM for the moment, I'm just hanging on 4.3. With a screen this HUGE, I'd love to root to be able to lower the DPI. Can anyone advise how to do that? Or am I better just waiting for Huawei to officially release Lollipop?
EDIT: so I found this -- http://forum.xda-developers.com/showpost.php?p=61682526&postcount=3. I'm confused, cuz one page of Huawei's blog says they hit pause on the 5.1 rollout, yet this 5.1 download looks like it's hosted on GetHuawei.com. I'm so confused...
adogg222 said:
Just got my phone yday. I've scoured the Ascend Mate2 threads, and al I see are questions about re-rooting the Lollipop build. Since it looks like Huawei has rescinded their Lollipop ROM for the moment, I'm just hanging on 4.3. With a screen this HUGE, I'd love to root to be able to lower the DPI. Can anyone advise how to do that? Or am I better just waiting for Huawei to officially release Lollipop?
EDIT: so I found this -- http://forum.xda-developers.com/showpost.php?p=61682526&postcount=3. I'm confused, cuz one page of Huawei's blog says they hit pause on the 5.1 rollout, yet this 5.1 download looks like it's hosted on GetHuawei.com. I'm so confused...
Click to expand...
Click to collapse
Since you just got your phone, I would say get to know it on 4.3 first. Lollipop is prettier, but you can do more root things on JB, it runs better, has better battery life, and is an all around better experience, IMO.
Lollipop doesn't have xposed either, if you planned on using that. On top of that, it is missing some core functionality like a startup manager(apps that should be running after a reboot are not!) and has a crippling audio bug.
First thing you have to do for root is email Huawei with your IMEI and SN asking for a bootloader unlock code.
[email protected]
Here is the email I sent them:
Hello, I would like a code to unlock the bootloader on my Huawei Ascend Mate 2, please.
Serial - *********
IMEI - *******
Thank you
Click to expand...
Click to collapse
I then got an unlock code within minutes, so it may or may not be somewhat automated.
TWRP for Mate2
Basically that is a zip file with everything that you need to install TWRP on the Mate2. It has:
SHM's Unified TWRP(v2.8.7.3).
Huawei drivers
ADB/Fastboot
SuperSu(v2.46)
stock 5.1 recovery(just incase)
!Readme file with step by step.
TWRP is needed to install SuperSu, which in turn gives you root.
First, make sure you leave all the files in the same folder. Extract them anywhere, like your desktop. Install the Huawei drivers if you don't already have them installed.
***Put the UPDATE-SuperSU-v2.46.zip on your phone's sdcard somewhere easy to find***
1. Turn off your phone
2. Hold Volume DOWN and Power button for a few seconds. When the screen turns on let go of the power button.
3. Now you should be on the bootloader screen, also known as fastboot.
4. Plug your phone into your PC and wait a minute to make sure any additional drivers are installed and setup.
5. Hold shift and right click an empty space in the folder you downloaded with adb.exe and fastboot.exe and select "Open command window here". A command window should open.
6. In command window type 'fastboot devices' and make sure it says there is a fastboot device. If it doesn't, that means your drivers didn't work. Try unplugging your phone and using another USB port.
7. If it showed a device, its working. Type 'fastboot flash recovery twrp.img'
8. If successful, your phone now has twrp installed
9. While still in fastboot, hold VOLUME UP and the POWER BUTTON for about 8 to 10 seconds, as soon as the screen turns off and then back on again, let both buttons go.
10. In TWRP, hit install and find your UPDATE-SuperSU-v2.46.zip and flash it.
11. Should be rooted and good to go.
12. I included the stock recovery if you ever want/need to go back. Just follow the same steps but replace "twrp.img" with "stock_recovery.img"
Click to expand...
Click to collapse
To lower DPI on our phone, a line will need to be added to the build.prop in the "root/system/" directory.
Add:
Code:
ro.sf.lcd_density=264
to the end of the text on a new line. 264 is the lowest you can go without causing multiple apps to crash.
You can go lower, but you will need Xposed and App settings to change the crashing apps to 264 or above.
Wow, thank you SO much for all of this!! So awesome of you!
adogg222 said:
Wow, thank you SO much for all of this!! So awesome of you!
Click to expand...
Click to collapse
Build prop editor on Google play store can very easily change your dpi. And makes a backup if you want to go back. Better than modding it yourself. And I agree with ark. Hold.off on L until things are fixed. Or until Tom get cm12 up and going.
Props to Ark for putting so much effort into his reply. (I would not have done the same.)
My advice to this self proclaimed "noob" is to read the threads and get more educated before just posting a question that has already been answered with it's own thread. All of the info that Ark posted is in these forums. Please don't get in the habit of asking to be spoon fed. That is certainly frowned upon on XDA.
kimtyson said:
Props to Ark for putting so much effort into his reply. (I would not have done the same.)
Click to expand...
Click to collapse
I had most of it done and copy pasted from another post I already made.
I'm glad someone finally gave simple comprehensive instruction. Unlike someone stated above, it was not that easy to find. I have had my phone for about 1 1/2 months since I returned from vacation in Europe. Ordered it online from Frys while I was there. Anyway, I have searched many times for instructions and couldn't find one thing definitive. Always comments alluding to root, and "does this keep root after update" or "how to get root back" or "this root method didn't work" etc... But never could I find instructions on how to achieve root on stock 4.3 until now. So Thank you sooo much. Now are we sure about the email link you provided above? Because I sent them (Basically copy and pasted ) your email above email twice. About a week ago, and a few days ago. And still no response! Any other suggestions? And shouldn't this be stickied since Root is the most basic of function of what we all want?
Some great information in this thread. Thanks guys. So unlocking the bootloader will wipe the device correct?
I got my unlock code and was going to unlock and make the device see itself as OEM. I was going to install L but it sure seems from the few posts here that it might not be worth it. Crippling audio bug? Can anyone elaborate on that?
Would it be better to unlock, convert my device to OEM and register with Huawei for OTA updates and simply wait for an official release? If I do the conversion, will the OS still be 4.3 at least?
Just like the thought of the updated Huawei EMUI 3 1.
I'm reading so many different confusing post. So does towelroot or kingroot work on MT2 L03 Android 4.3? I've read other places those methods work? And does anyone have the instructions on the easiest way to unlock bootloader (I hear that is necessary before we root)? I already have the unlock code. This phone has been in a box for the last 1 1/2 months waiting for me to have the time to play. Thank you.
TheIgster said:
Some great information in this thread. Thanks guys. So unlocking the bootloader will wipe the device correct?
I got my unlock code and was going to unlock and make the device see itself as OEM. I was going to install L but it sure seems from the few posts here that it might not be worth it. Crippling audio bug? Can anyone elaborate on that?
Would it be better to unlock, convert my device to OEM and register with Huawei for OTA updates and simply wait for an official release? If I do the conversion, will the OS still be 4.3 at least?
Just like the thought of the updated Huawei EMUI 3 1.
Click to expand...
Click to collapse
The audio bug is a bug that happens while listening to any audio. The audio will cut off completely. If you press the either of the volume keys, the phone will basically freeze for around 30 seconds and then usually it starts working like normal again.
It happened to me very often, like every time I listened to anything. But after installing Viper and its drivers and boosting the audio levels I haven't had this bug happen once. So that seems like a fix to me.
---------- Post added at 11:41 PM ---------- Previous post was at 11:36 PM ----------
TTJB said:
I'm reading so many different confusing post. So does towelroot or kingroot work on MT2 L03 Android 4.3? I've read other places those methods work? And does anyone have the instructions on the easiest way to unlock bootloader (I hear that is necessary before we root)? I already have the unlock code. This phone has been in a box for the last 1 1/2 months waiting for me to have the time to play. Thank you.
Click to expand...
Click to collapse
If you have the code, just boot into fastboot and use the command
Code:
fastboot oem unlock *your code, no asterisks*
ArkAngel06 said:
The audio bug is a bug that happens while listening to any audio. The audio will cut off completely. If you press the either of the volume keys, the phone will basically freeze for around 30 seconds and then usually it starts working like normal again.
It happened to me very often, like every time I listened to anything. But after installing Viper and its drivers and boosting the audio levels I haven't had this bug happen once. So that seems like a fix to me.
Click to expand...
Click to collapse
Hmmm. I have finally loaded LP, but haven't messed too much with audio playback. I'll have to listen for it. So where is this viper that I can load?
TheIgster said:
Hmmm. I have finally loaded LP, but haven't messed too much with audio playback. I'll have to listen for it. So where is this viper that I can load?
Click to expand...
Click to collapse
It's on Google Play or XDA. Try looking for it.
kimtyson said:
It's on Google Play or XDA. Try looking for it.
Click to expand...
Click to collapse
Thanks. Maybe try being less snarky next time?
Just a simple question in a forum that doesn't have a helluva lot of posts anyway.
alright so i got to the stage where i have superSU. however when i open it it says SU binary needs to be updated
i tried using twrp and installed the updated 2.4.6....and it still says i need to update the binary
any suggestions?
thanks ark for the detailed instructions tho
Callmebaus said:
alright so i got to the stage where i have superSU. however when i open it it says SU binary needs to be updated
i tried using twrp and installed the updated 2.4.6....and it still says i need to update the binary
any suggestions?
thanks ark for the detailed instructions tho
Click to expand...
Click to collapse
Just let it update itself.
Moody66 said:
Just let it update itself.
Click to expand...
Click to collapse
how? selecting normal? instead of twrp?
Callmebaus said:
how? selecting normal? instead of twrp?
Click to expand...
Click to collapse
Normal
jesus christ i remember normal fkin up my phone so i was sure not to press it then i formatted my phone using twrp
os....as well
I can't do anything
i should shoot myself.
trying to install stock again, having no luck
Callmebaus said:
jesus christ i remember normal fkin up my phone so i was sure not to press it then i formatted my phone using twrp
os....as well
I can't do anything
i should shoot myself.
trying to install stock again, having no luck
Click to expand...
Click to collapse
If you still not resolve the problem yet, try this:
http://forum.xda-developers.com/showpost.php?p=58208866&postcount=9
and remember always take backup...
xordos said:
If you still not resolve the problem yet, try this:
http://forum.xda-developers.com/showpost.php?p=58208866&postcount=9
and remember always take backup...
Click to expand...
Click to collapse
that's the exact post that I used yesterday, haha
all fixed and rooted
thank u
Don't forget to hit the thanks button.
http://superstarmobility.weebly.com/
New thread: http://forum.xda-developers.com/android/development/twrp-m1-lg-k7-t3462130.
(Above TWRP can be flashed with Flashify from Playstore)
Instructions from video:
With phone powered off, hold POWER and VOLUME DOWN buttons until LG logo shows. Release POWER then quickly press and hold again until factory reset menu comes up. Select YES and you will be booted into recovery instead of a factory reset ; )
Thanks @czarsuperstar!
V2 with the proper cmd line from m1 aka LG K7
Reserved.
This the real deal?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
Of course. You looked at the video?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
I've used it and can confirm, first tested it with fastboot without flashing of course(use adb to get to the bootloader: adb reboot bootloader , then fastboot:fastboot boot "twrp.img file, tested then rebooted into bootloader, then flashed via fastboot:fastboot flash "twrp.img file") instructions are for any random person that come by i know you know how to do all this
concerned xda citizen
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
The first twrp was from a htc phone. This is from lg leon lte. Same manufacturer. I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon twrp is missing the options seen on this one. Don't use it. But I'm working on cm_m1 so continue to use the old one and when your phone can't come on have fun getting in recovery. Make it better.
Recovery log
Make a log.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
Check out the LG L70 it's the same way to get in recovery. This must be your first LG phone.
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Go spam the other thread. Over 200 downloads and no problems but there was problems right away with the first version. For your info download Twrp c50 from the Twrp site examine it and ask why it's incomplete. That's why I linked the video of the Twrp from the site and same problems. Bye and leave me be. Hd2 check it out. Czarsuperstar's HTC HD2 android custom roms. Check it out and leave me alone. Thanks for your concern. Oh and for your info we have the same keyboard configuration as the LG Leon. There's a device tree. Google it. Google is your friend bro.
NASSTYROME said:
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Click to expand...
Click to collapse
not saying a official twrp isn't preferable, but man you got to learn how to talk to people, you were just short of cursing the dude out, and as far as the recovery the thing is solid(tested backup, flash and restore/ anyhow we got LGUP if you **** up so its not a huge deal), but anyone on this site shouldn't take someones word for things like recovery's and you should always test boot before you flash, also you don't seem to understand the first rule of xda-whatever happens to your device is on you, been that way since the og day's- talking politely to others is the way to go about things, people wont listen if you combative.
Kernel
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Didn't work, after selecting yes twice, my phone just starts like normal, doesn't go to TWRP or factory restore, it is there though because I can boot to it from the flashify app, ah well.
wait...my bad, I was highlighting the wrong one, lol, works great, thanks
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
callihn said:
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
Click to expand...
Click to collapse
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
[email protected] said:
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
Click to expand...
Click to collapse
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
callihn said:
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
Click to expand...
Click to collapse
I'm working on building it from source but keep getting errors and I'm trying it with another device that has Twrp (Moto E 2015) and followed the directions to the T and no luck. So I am trying......... Will let everyone know how it's going.
[email protected] said:
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Click to expand...
Click to collapse
kernel??????????????????????????
im down!
New here. Didn't see a forum for the Moto G Pure XT2163. Mods - I am sorry. Please move wherever's best.
Discovered that the version Verizon is selling (notably the slickdeals thread on the one from Visible) is different. It's -2 vs. -4.
Looks like VZW disabled most of the bands that T-Mobile/Sprint use - 25, 41, 71, for example.
Looking to see if it's possible to enable those bands. One report on SD thread says they bricked their device trying RETUS version but IDK if the bootloader needs to be unlocked first, or if it would even help. Probably more work to unlock these bands if it's even possible.
Downloads look available here https://mirrors.lolinet.com/firmware/moto/ellis/official/
Haven't messed with flashing a phone in years. May be able to try later but hoping anyone else here can look into this.
I'm going to guess as is the case with most other Android devices branded by Verizon that the bootloader will be restricted from being unlocked. There is really no way around this as it's an OEM based policy. If you want to play with custom ROMs or root based modding, I would highly recommend ditching the Verizon or any other carrier branded variant with the exception of T-Mobile/Metro and Google Fi (there are others) that actually allow OEM unlock. Not only that, but if you're looking for certain connectivity bands, you don't want to settle for a carrier device variant designed to use a particular set of bands which don't include the ones you need. No sense getting a Verizon variant to run on T-Mobile/Sprint bands when you can, you know, get the T-Mobile variant in the first place. Get the global unlocked variant model if you can and start from there. Far easier than the headaches you'll get trying to transform VZW to TMUS.
Cross-flashing is not going to unlock bands, you need to change modem configuration. Throw your SoC(Mediatek) followed by "unlock bands" into Google and see if you have any luck.
I also didn't see a forum for the Moto G Pure and was wondering if anyone knows of a custom bootloader like TWRP or CWM for it? I think I have enough understanding of how to sideload the app, I just need something to send the phone. I tried using a random TWRP mod on it but it fails, invalid signature. I haven't tried doing the phone rooting thing in years now, but I have this Moto G Pure phone without any service on it that I'm willing to experiment on. It can be used as a test bed or data extraction device to put code from it on the internet if someone needs it to help custom rom makers for example by testing stuff on it. Perhaps that's why no one has a custom recovery for it yet.
I don't know exactly how to extract the phones current ROM data so all I've done so far is unlock the bootloader. The phone's carrier based on the unactivated sim card shows it's a T-Mobile branded device, but the T-Mobile and other carrier software is inactive other than the few Moto apps. An article on XDA say's the phone's suck, but that's just not true at least not to me. It's a fine phone like it is, but if I can format it's SSD and only install what I want it to have on it that would be great. It's just a spare sim locked phone that I can't use my active sim card in. So with that it's now a project phone. I would like to mainly just unbloat it and free up all that used space occupied by the recovery partition. I don't necessarily need a whole new ROM, just want to root it. That's the only way to erase those factory files that I know of.
For me unlocking the bootloader wasn't to hard to do. You have to make sure the drivers from Motorola are installed and have a current version of ADB available on a computer. I still had a version of ADB tools that was almost a decade old now so I had to update that for the fastboot oem_unlock_unlockcode (automated code from Motorola support) command to work. To find out if it can be unlocked or not go here:
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
At the Moto site they will guide you on how to generate the code they want you to send them. You have to sign in to their site to use that function though. After I finally figured out what to type in the CMD window it generated that code and I edited it down to one long line of numbers and give it to the page. In seconds I had an email with the unlock code inside.
Unlocking it seems to help with uninstalling some of the built in stuff, before I could only disable most of the apps that come with it. The apps are still probably on there I just have to factory reset it and they'll come back. Now however the removed apps don't show as using any internal storage, all the apps info numbers go to 0 bytes, but still even doing that it's still over 10GB of unmovable data. When it should really be more like 2-3 GB for the entire system. I hate how Google just inserts itself in your life even when you don't want it at all.
I anyone passing by reading this post needs more details please let me know and I'll try to get the information or even data files from the phone. Would a copy of it's stock firmware be of any help? If so let me know how I would go about saving a copy of it. I'll keep looking for answers but it seems this phone is not high on the priority list or is new or something. So there is only scam guides trying to tell you "How to unlock your phone" or "Install TWRP on Motorola devices" and other clearly click bait sites. I can't even find the stock rom for it on Motorola's site, just outdated versions from 2016, with different build numbers, that can't be right.
All I know is unlocking the bootloader was the first step on all the guides and I've done that. Got a warranty voided notice and everything. There currently isn't a custom recovery mod for this model as far I can tell. If I can ever find that then I can try Linage or just debloat Android 11 which is probably the safer and easier option provided I can find that Custom Covery'.
When it boots up now, it has to tell me it's unlocked and all the dangers it poses. Dangerous if you cared about what was on it I suppose. There is nothing on it I can't just copy back over to it, other than the stock operating system.
Oh yeah, it's model number and other side of the box information is:
Model Name: Moto G PURE
SKU: MO-XT21634-AJB (MOXT21634AJB)
Software Version RRH31.Q3-46-20
Production date was 12/15/2021
I'm not sure what other information to include.
BrittonCBurton said:
I also didn't see a forum for the Moto G Pure and was wondering if anyone knows of a custom bootloader like TWRP or CWM for it? I think I have enough understanding of how to sideload the app, I just need something to send the phone. I tried using a random TWRP mod on it but it fails, invalid signature. I haven't tried doing the phone rooting thing in years now, but I have this Moto G Pure phone without any service on it that I'm willing to experiment on. It can be used as a test bed or data extraction device to put code from it on the internet if someone needs it to help custom rom makers for example by testing stuff on it. Perhaps that's why no one has a custom recovery for it yet.
I don't know exactly how to extract the phones current ROM data so all I've done so far is unlock the bootloader. The phone's carrier based on the unactivated sim card shows it's a T-Mobile branded device, but the T-Mobile and other carrier software is inactive other than the few Moto apps. An article on XDA say's the phone's suck, but that's just not true at least not to me. It's a fine phone like it is, but if I can format it's SSD and only install what I want it to have on it that would be great. It's just a spare sim locked phone that I can't use my active sim card in. So with that it's now a project phone. I would like to mainly just unbloat it and free up all that used space occupied by the recovery partition. I don't necessarily need a whole new ROM, just want to root it. That's the only way to erase those factory files that I know of.
For me unlocking the bootloader wasn't to hard to do. You have to make sure the drivers from Motorola are installed and have a current version of ADB available on a computer. I still had a version of ADB tools that was almost a decade old now so I had to update that for the fastboot oem_unlock_unlockcode (automated code from Motorola support) command to work. To find out if it can be unlocked or not go here:
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
At the Moto site they will guide you on how to generate the code they want you to send them. You have to sign in to their site to use that function though. After I finally figured out what to type in the CMD window it generated that code and I edited it down to one long line of numbers and give it to the page. In seconds I had an email with the unlock code inside.
Unlocking it seems to help with uninstalling some of the built in stuff, before I could only disable most of the apps that come with it. The apps are still probably on there I just have to factory reset it and they'll come back. Now however the removed apps don't show as using any internal storage, all the apps info numbers go to 0 bytes, but still even doing that it's still over 10GB of unmovable data. When it should really be more like 2-3 GB for the entire system. I hate how Google just inserts itself in your life even when you don't want it at all.
I anyone passing by reading this post needs more details please let me know and I'll try to get the information or even data files from the phone. Would a copy of it's stock firmware be of any help? If so let me know how I would go about saving a copy of it. I'll keep looking for answers but it seems this phone is not high on the priority list or is new or something. So there is only scam guides trying to tell you "How to unlock your phone" or "Install TWRP on Motorola devices" and other clearly click bait sites. I can't even find the stock rom for it on Motorola's site, just outdated versions from 2016, with different build numbers, that can't be right.
All I know is unlocking the bootloader was the first step on all the guides and I've done that. Got a warranty voided notice and everything. There currently isn't a custom recovery mod for this model as far I can tell. If I can ever find that then I can try Linage or just debloat Android 11 which is probably the safer and easier option provided I can find that Custom Covery'.
When it boots up now, it has to tell me it's unlocked and all the dangers it poses. Dangerous if you cared about what was on it I suppose. There is nothing on it I can't just copy back over to it, other than the stock operating system.
Oh yeah, it's model number and other side of the box information is:
Model Name: Moto G PURE
SKU: MO-XT21634-AJB (MOXT21634AJB)
Software Version RRH31.Q3-46-20
Production date was 12/15/2021
I'm not sure what other information to include.
Click to expand...
Click to collapse
hey i just came up on one of these today, nice phone considering... Any luck with trying to find a custom recovery? I have been looking as well but development seems pretty sparse right now. I am in the same boat as you, unlocked bootloader, locked everything else lol. I cant even find a way to root it without TWRP! I am curious if one of the other moto G series phones would have the same TWRP? Also check this out. It sounds legit but IDK...https://www.getdroidtips.com/root-motorola-g-pure-xt2163/
Agent_Orange1488 said:
hey i just came up on one of these today, nice phone considering... Any luck with trying to find a custom recovery? I have been looking as well but development seems pretty sparse right now. I am in the same boat as you, unlocked bootloader, locked everything else lol. I cant even find a way to root it without TWRP! I am curious if one of the other moto G series phones would have the same TWRP? Also check this out. It sounds legit but IDK...https://www.getdroidtips.com/root-motorola-g-pure-xt2163/
Click to expand...
Click to collapse
Well I was able to use Magisk to "root" it with the patched boot file trick, but still that's not the same thing as I did before with a Samsung phone and the CWM recovery deal. That gave the user all the control they wanted. Even though the phone claims I have root access, I'm not sure what to do with Magisk's root trick. I still don't see a way to backup or install a different operating system or just a blank Android 11 OS. My knowledge there is limited and there isn't a custom recovery for this model as far as I can tell.
So I still can't wipe the drive or remove the OEM partition that contains the installers for the bundled stuff. I'd still need some form of interface that has more features than the stock Fastboot and Bootloader modes offer I guess, or I just don't know how to use the software tools correctly. It's still locked even with root as far as I can tell but if there is something more I'm missing or an additional app to install for example, like SU. Is that still a thing? If I'm on the right track let me know.
BrittonCBurton said:
Well I was able to use Magisk to "root" it with the patched boot file trick, but still that's not the same thing as I did before with a Samsung phone and the CWM recovery deal. That gave the user all the control they wanted. Even though the phone claims I have root access, I'm not sure what to do with Magisk's root trick. I still don't see a way to backup or install a different operating system or just a blank Android 11 OS. My knowledge there is limited and there isn't a custom recovery for this model as far as I can tell.
So I still can't wipe the drive or remove the OEM partition that contains the installers for the bundled stuff. I'd still need some form of interface that has more features than the stock Fastboot and Bootloader modes offer I guess, or I just don't know how to use the software tools correctly. It's still locked even with root as far as I can tell but if there is something more I'm missing or an additional app to install for example, like SU. Is that still a thing? If I'm on the right track let me know.
Click to expand...
Click to collapse
Thanks for the reply!!! I am speaking from a place of semi-ignorance here but I would thing that you could install SuperSU from inside the system, right? As long as the root binary is there...idk though and from what I hear, chainfire is not responsible for SuperSU anymore so it has become somewhat sketchy. I saw a post (about this phone, I think) that mentioned having to install terminal emulator and running root command from there to achieve legit root after flashing the patched boot.img. I will see if I can find the post again and update you. Is there anyway you could post the boot.img? Or give me a link for it?
Agent_Orange1488 said:
Thanks for the reply!!! I am speaking from a place of semi-ignorance here but I would thing that you could install SuperSU from inside the system, right? As long as the root binary is there...idk though and from what I hear, chainfire is not responsible for SuperSU anymore so it has become somewhat sketchy. I saw a post (about this phone, I think) that mentioned having to install terminal emulator and running root command from there to achieve legit root after flashing the patched boot.img. I will see if I can find the post again and update you. Is there anyway you could post the boot.img? Or give me a link for it?
Click to expand...
Click to collapse
Well I can try and learn how to extract the phones information to my computer. I don't know how to do that exactly. The way I was able to get a hold of the phones stock firmware data was by using Lenovo's Smart Rescue and Recovery software.
You have to enable usb debugging mode, attach the phone to the computer with the software running and make sure that you didn't disable/delete Device Help. That app is what makes the Lenovo software work, otherwise the Recovery software fails to see the phone. If it sees the phone correctly then you can see the preselected target firmware it wants you to download under the Rescue tab along the top.
So I did that and grabbed the files it created without actually applying them to the device. The whole thing is a little over 2GB and difficult to host but I put the stock boot.img file here for anyone who needs it. If anyone wants all the files I can try to upload the whole thing one file at at time. That's the way it was sent to me, an uncompressed folder. If I zip it all up and try to upload it most sites will say file size exceeded. Anyway here's the link...
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Thanks I was able to patch it with Magisk and achieve root. It looks like Magisk is an SU manager anyway. I have never used it before so this is a first for me. The root and bootloader unlock seem a little pointless without any recovery or ROM though....I guess it's time to learn how to compile one lol
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Agent_Orange1488 said:
Thanks I was able to patch it with Magisk and achieve root. It looks like Magisk is an SU manager anyway. I have never used it before so this is a first for me. The root and bootloader unlock seem a little pointless without any recovery or ROM though....I guess it's time to learn how to compile one lol
Click to expand...
Click to collapse
Yeah now we're on the same page then. I thought the same thing, not much use to have an unlocked boot loader and root access without software to make use of it. I gave the phone to my nieces to play with for now, but it's with in arms reach if I need it for instructions yet to be defined. I should receive updates to this post if anyone else responds.
Gamekeeper408 said:
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Click to expand...
Click to collapse
Yeah appears it was produced in late 2021 or sold at that time so it's new and no one has made any custom firmware's or recoveries for it as far as I know. I don't know how to do that, requires computer programming skills. I don't have any of those.
Gamekeeper408 said:
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Click to expand...
Click to collapse
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
BrittonCBurton said:
Yeah now we're on the same page then. I thought the same thing, not much use to have an unlocked boot loader and root access without software to make use of it. I gave the phone to my nieces to play with for now, but it's with in arms reach if I need it for instructions yet to be defined. I should receive updates to this post if anyone else responds.
Click to expand...
Click to collapse
Excellent, it's nice to be caught up with everyone else haha!! I am going to do some digging and posting and whatnot to try to find some info on porting a recovery for this model. I feel like it can't be too different from at least one or two of the other G series phones. I will see updates as well so please post if you come up with anything!!
BTW does anyone know the process of creating a device page for this joint?! I think this phone is definitely worth some development...
Agent_Orange1488 said:
Excellent, it's nice to be caught up with everyone else haha!! I am going to do some digging and posting and whatnot to try to find some info on porting a recovery for this model. I feel like it can't be too different from at least one or two of the other G series phones. I will see updates as well so please post if you come up with anything!!
BTW does anyone know the process of creating a device page for this joint?! I think this phone is definitely worth some development...
Click to expand...
Click to collapse
Good luck finding anything that will load onto the phone. Seems like it would be possible to install LineageOS on it if nothing else. You'd think by now installing a phone's operating system would be similar to how operating systems are installed on other computers. All I get is invalid signature, way to much security (for them) on phone OS'es. With phones and PDA's apparently you can't just find the OS you want to use and install it. Where's the generic and bloat free Andriod 11 stock OS/firmware at? No such thing? It's either "Gaggles" way or nothing apparently. (It's ok if you don't know either, maybe someone else has more information about that.)
BrittonCBurton said:
Good luck finding anything that will load onto the phone. Seems like it would be possible to install LineageOS on it if nothing else. You'd think by now installing a phone's operating system would be similar to how operating systems are installed on other computers. All I get is invalid signature, way to much security (for them) on phone OS'es. With phones and PDA's apparently you can't just find the OS you want to use and install it. Where's the generic and bloat free Andriod 11 stock OS/firmware at? No such thing? It's either "Gaggles" way or nothing apparently. (It's ok if you don't know either, maybe someone else has more information about that.)
Click to expand...
Click to collapse
Ya I'm definitely not going to try anything on the actual device, (ESPECIALLY if I am trying to put it together myself) but I am pretty sure you can test that stuff on a virtual system. Some kind of android emulator or whatever. As for a stock/debloated/de-odexed ROM, I haven't seen one but that couldn't be all that difficult to put together, right? I mean as long as the patched boot.img is included anyway. I feel like a recovery would be a higher priority though...? BTW, I have never used Lineage before, how is it?
Agent_Orange1488 said:
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
Click to expand...
Click to collapse
That would be great if you could share that patched boot.img......it is for the XT2163-4 MOTO G PURE correct?
Gamekeeper408 said:
That would be great if you could share that patched boot.img......it is for the XT2163-4 MOTO G PURE correct?
Click to expand...
Click to collapse
Agent_Orange1488 said:
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
Click to expand...
Click to collapse
I would also like the patched boot.img if it is for the XT2163-4. Thanks
Hey boys I actually got rid of the moto g pure...for now at least lol! GREAT phone and I would be willing to get it back once there is some dev work done on it...will definitely be watching the threads on it. Good luck boys!!!
Hi
I read the above posts, and it seems like even if I am able to root it using Magisk, I won't be able to flash it with custom rom?
Thank you Agent_Orange1488 for the posts.