Develop Bugs

[ROOT] Superboot - Galaxy Nexus root solution

Introducing.... Superboot!
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
APPLY THIS AT YOUR OWN RISK!
Superboot r5 - DOWNLOAD - MD5: 510c4a0c5a62407550abc5e028c6fd82
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume up' and 'volume down' buttons both pressed to enter the bootloader (as pictured below)
- WINDOWS - double click 'superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-mac.sh' followed by './superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-linux.sh' followed by './superboot-linux.sh'
Note: If you are using a retail device, you may need to unlock the bootloader first, using './fastboot-windows oem unlock' (or the appropriate version for your machine, included in this zip). Note that the OEM unlock sequence wipes your device, so consider doing an 'adb backup' beforehand if required!
Enjoy!
P
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

cheers paul for this now can you sort an unlock please so i can get my tmobile sim working in it anytime before my t would be great in the next say 30 mins would be smashin

treble4 said:
cheers paul for this now can you sort an unlock please so i can get my tmobile sim working in it anytime before my t would be great in the next say 30 mins would be smashin
Click to expand...
Click to collapse
Done!
P

so this is a temporary or permanent root because i didnt understood well the ''until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash').''

pan24 said:
so this is a temporary or permanent root because i didnt understood well the ''until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash').''
Click to expand...
Click to collapse
Permanent root.
P

great, can't wait to get mine!

paulobrien said:
Permanent root.
P
Click to expand...
Click to collapse
I'm sorry, i find this a bit confusing. Why do you make mention then to 'reboot', if people dont have to worry about it (as in my definition of permanent).
Does superboot allow for root under adb (until restart), and for normal os operation+root access, the latter not being affected by a reboot, is that it?
Sent from my GT-I9000 using Tapatalk

I'm a little confused by the terminology used here too. This is a permanent root? Not one that must run after every reboot?
Sent from my Galaxy Nexus using Tapatalk

bk201doesntexist said:
Does superboot allow for root under adb (until restart), and for normal os operation+root access, the latter not being affected by a reboot, is that it?
Click to expand...
Click to collapse
This is what he means. Running "fastboot boot" allows you to access the root shell using adb, however after reboot you will not be able to do that again until you reboot with the same command, or flash his permenant adb root .img from his other thread.
Once you have done this method once, the su binary and Superuser.apk are on your device, and will be there permentantly, until such a time as you remove them or you reflash a stock image. This means your on-device root is permenant too.

Worked flawlessly on my Mac. Cheers!

I can't think of any reason why this method using the r2 files won't work equally well on the USA VZW version when (if) we finally get it -- true?

John Markley said:
I can't think of any reason why this method using the r2 files won't work equally well on the USA VZW version when (if) we finally get it -- true?
Click to expand...
Click to collapse
The boot image used here is a modified version of the GSM Galaxy Nexus boot image, I don't think it'll boot on the LTE version.

el3ctrik said:
This is what he means. Running "fastboot boot" allows you to access the root shell using adb, however after reboot you will not be able to do that again until you reboot with the same command, or flash his permenant adb root .img from his other thread.
Click to expand...
Click to collapse
I've come from using a Desire and just got the Galaxy Nexus. I've just unlocked the bootloader and flashed superboot using fastboot.
What I don't quite understand is why you wouldn't just want to flash the unsecure boot image from the other thread ? Or why this method doesn't do the same. I understand that this method reboots the phone using the superboot image rather than flashing over the system boot image file. But why wouldn't you want to override the system boot image to get full access? I suppose this is just highlighting my lack of knowledge of what I was doing before as I used unrevocked to get root access and custom recovery all in one go.
Sorry for asking these questions but it seems like there are a few people wanting to know the same thing.
@Paul - Big ups and thanks for posting this easy to use version.

siedkins said:
I've come from using a Desire and just got the Galaxy Nexus. I've just unlocked the bootloader and flashed superboot using fastboot.
What I don't quite understand is why you wouldn't just want to flash the unsecure boot image from the other thread ? Or why this method doesn't do the same. I understand that this method reboots the phone using the superboot image rather than flashing over the system boot image file. But why wouldn't you want to override the system boot image to get full access? I suppose this is just highlighting my lack of knowledge of what I was doing before as I used unrevocked to get root access and custom recovery all in one go.
Sorry for asking these questions but it seems like there are a few people wanting to know the same thing.
@Paul - Big ups and thanks for posting this easy to use version.
Click to expand...
Click to collapse
Because the insecure boot image is just that, an insecure boot image - it doesn't root your device with the superuser binary / APK.
P

Excellent ... um quick question before i pop out - are the o2 contract handsets sim locked and if so if there an unlock solution ? (paid or otherwise) - i tend to switch between 02/voda a lot so need to unlock

Unknown.
P

gaspodex said:
Excellent ... um quick question before i pop out - are the o2 contract handsets sim locked and if so if there an unlock solution ? (paid or otherwise) - i tend to switch between 02/voda a lot so need to unlock
Click to expand...
Click to collapse
I think you can just call O2 and ask for an unlock code. Don't quote on that though

I must be stupid or something cause I can't seem to unlock my phone? :-( done everything. :-S
Sent from my Galaxy Nexus using XDA App

recklesslife85 said:
I must be stupid or something cause I can't seem to unlock my phone? :-( done everything in a shirt quide :-S
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
You got it plugged in on the bootloader screen?
Just cd to wherever you extracted Pauls superboot too and type:
./fastboot-windows oem unlock
Assuming you are on Windows..if not just change it for your os
Linux = ./fastboot-linux oem unlock
OS X = ./fastboot-mac oem unlock

Evostance said:
You got it plugged in on the bootloader screen?
Just cd to wherever you extracted Pauls superboot too and type:
./fastboot-windows oem unlock
Assuming you are on Windows..if not just change it for your os
Linux = ./fastboot-linux oem unlock
OS X = ./fastboot-mac oem unlock
Click to expand...
Click to collapse
Actually it didn't work... ;-/ its finding the phone so not a driver problem but typing in ./fastboot-windows oem unlock does nothing other than give me an error saying its not recognized as a internal or external command.

[ROOT](11-17-12) Root Nexus 10 with CWM and SuperSu Zip (Stress Free and Simpler)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Updated 11-17-12: Now that we have a stable CWMR image thanks to damien667 this procedure should be a lot less risky and less stressful!
This is confirmed working but due to the procedure involved is risky! The standard XDA disclaimer applies: I take no responsibility for bricked devices due to the following rooting procedure, no warranty express or implied is given, I will not be held responsible if you mess up your tablet by following this procedure!​
You must unlock the bootloader before performing this procedure!
Credits: Kidgoo for testing and coming up with the method, thanks to damien667 for the fixed CWM images, and Chainfire for the SuperSu zip and binaries!
Before you begin make sure you read and reread the procedure and fully understand the directions.
1. Download the CWM-SuperSU-v0.98.zip
2. Download damien667's fixed CWMR 6.0.1.6 touch version of from here
3. Connect the Nexus 10 to your computer
4. Flash the CWMR image you downloaded in step 2 using fastboot
Code:
fastboot flash recovery /path/to/<recovery>.img
fastboot reboot
5. Touch "Install from SD Card" in CWMR
6. Select CWM-SuperSU-v0.98.zip that was downloaded in step 1
7. Let CWM-SuperSU-v0.98.zip install
8. Select "Reboot System"
9. Enjoy your rooted Nexus 10 !
To keep your custom recovery installed permanently and not get overwritten by the stock recovery when your reboot your tablet delete the following:
Code:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p

Reserved

works! thank you very much!

Awesome!
Now, if only we could code it so it does it all for us!
1-click and go! Im afraid ill fat finger something and have a $550 paper weight :'(
Thanks for the write up!

WannaB101 said:
Now, if only we could code it so it does it all for us!
1-click and go! Im afraid ill fat finger something and have a $550 paper weight :'(
Thanks for the write up!
Click to expand...
Click to collapse
One-Klick CWM Tounch + SuperSU would be great!!! :good::good::good:

So what am I supposed to do if ADB doesn't recognize the "sideload" command?

gravis86 said:
So what am I supposed to do if ADB doesn't recognize the "sideload" command?
Click to expand...
Click to collapse
You will need to download the latest vesion of ADB included in the Android SDK, which can be found here.

Perhaps a video?
Perhaps you could provide a video to help us along?

shimp208 said:
You will need to download the latest vesion of ADB included in the Android SDK, which can be found here.
Click to expand...
Click to collapse
Yep, my ADB was out of date... Thanks!

Got the latest version of ADB?

With regard to downloading the CWM-SuperSU file (for sideloading) do you mean that it should be downloaded on the tab itself, or downloaded into the same folder as adb and fastboot?

WannaB101 said:
Perhaps you could provide a video to help us along?
Click to expand...
Click to collapse
If my Nexus 10 had arrived yet then I would be more then happy to post a video until then you'll have to make due with the written guide I'm afraid . But if you or any one else has any questions regarding the procedure feel free to ask!

shimp208 said:
If my Nexus 10 had arrived yet then I would be more then happy to post a video until then you'll have to make due with the written guide I'm afraid . But if you or any one else has any questions regarding the procedure feel free to ask!
Click to expand...
Click to collapse
I hit ya with a question above...

joeski27 said:
With regard to downloading the CWM-SuperSU file (for sideloading) do you mean that it should be downloaded on the tab itself, or downloaded into the same folder as adb and fastboot?
Click to expand...
Click to collapse
If you download it on your tablet you'll need to then place the downloaded zip on the root of the internal storage (I.E not in a folder). Alternatively you can download it using a computer and connect your tablet to the computer and transfer it to the root of the internal storage that way.

I know this is probably a noob question but the fastboot commands (the first two, for booting from CWRT) -- should they be done in Fastboot Mode or can they be done while Nexus 10 is on and at home screen with USB debugging enabled? If you need to be in Fastboot Mode, how do you get there with Nexus 10?
Thanks!

shimp208 said:
If you download it on your tablet you'll need to then place the downloaded zip on the root of the internal storage (I.E not in a folder). Alternatively you can download it using a computer and connect your tablet to the computer and transfer it to the root of the internal storage that way.
Click to expand...
Click to collapse
Ok, the problem I have now is while I have the files on my tablet, I cannot move them to the root of the internal storage at this point...??? Suggestions??? Don't you have to be rooted in order to do this???

For some reason when I'm not in fastboot mode, I can use adb (adb devices lists my Nexus 10), but when I'm in fastboot mode, adb no longer recognizes the device. fastboot devices does however see it when in fastboot mode.
Anybody else have this problem or know why this might be happening? Thanks!

I'm still getting the sideload error after updating the ADB
Any insight, please?

So to others who are working on this and awaiting responses from the OP, where exactly have you placed the downloaded files on your tablet? specific locations?? and if so how did you get them there? I'm totally lost at this point, LOL, hoping to get some clarification soon...

Worked ... however .. you DO have to be in FASTBOOT already (power + Vol UP + Vol DOWN) - yeah it might be obvious when you're not tired as hell - but for those wondering
The first line should be:
fastboot boot /path/to/<recovery>.img
no fastboot reboot was needed - it rebooted itself.
I had a HELL of a time finding the sideload entry in CWM (that's just my brain deadness).
You have quite a bit of time More than enough.
THANK YOU!

Uninstalled Rom, don't have zip on sd. Help!

Ok, so I thought I still had the zip on my device after not being able to recall my gesture pattern lock. I could still access the device by logging into through my google account however I couldn't change the lock itself without doing a system wipe.(To my knowledge)
So now I'm stuck in TWRP with no rom to flash to my device, when I connect my nexus 7 to a notebook (win7) I do not get the MTP connection to drag and drop a rom over.
Everything I seemed to try in the ToolKit as well has been unsuccessful, can someone give me a step by step on how to push,flash,install PAC back onto my device and remove this headache of mine.
Thanks in advance!

DeeSlivers said:
Ok, so I thought I still had the zip on my device after not being able to recall my gesture pattern lock. I could still access the device by logging into through my google account however I couldn't change the lock itself without doing a system wipe.(To my knowledge)
So now I'm stuck in TWRP with no rom to flash to my device, when I connect my nexus 7 to a notebook (win7) I do not get the MTP connection to drag and drop a rom over.
Everything I seemed to try in the ToolKit as well has been unsuccessful, can someone give me a step by step on how to push,flash,install PAC back onto my device and remove this headache of mine.
Thanks in advance!
Click to expand...
Click to collapse
For future reference, I think you can send and email to your google account to reset your gesture lock.
If you want to flash a rom onto your device just use the toolkit. Should find what you need in Advanced utilities.

Where is the advanced utilities in the tool kit? you must have the wording wrong.
Wish I knew about the reset prior to the this mess >.<

DeeSlivers said:
Where is the advanced utilities in the tool kit? you must have the wording wrong.
Wish I knew about the reset prior to the this mess >.<
Click to expand...
Click to collapse
He is referring to this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These are the 4 items you will need to sideload P.A.C if you don't have them already.
http://goo.gl/QBnwND
http://goo.gl/jG0M9a
http://goo.gl/DEUHBC
http://goo.gl/WvFjl6

TWRP works with adb. Plug it in to your computer with the adb tools installed, run adb devices, you should see it listed. Change to the folder with your ROM zip, do adb push <rom>.zip /sdcard and it'll be on your device. No fuss, no muss.
Sent from my Nexus 7 using Tapatalk 4

This is the driver you need in order to use ADB while in recovery in addition to the Google Driver or else you would see "Flo" under Unknown Devices in your computer device manager.

Username invalid said:
This is the driver you need in order to use ADB while in recovery in addition to the Google Driver or else you would see "Flo" under Unknown Devices in your computer device manager.
Click to expand...
Click to collapse
Thanks I'm wiping the drivers and attempting your method! I'll be back with questions if I have any.:cyclops:

There we go, I had to use a different link in order to download the Minimal ADB And Fastboot Kit.
From there I was able to push the rom onto the device no problem what so ever thanks everyone!

DeeSlivers said:
For some reason the link you provided for ADB and Fastboot doesn't work. My device does show up as a ADB device in the device manager. However I'm still unsure how exactly I push or flash a rom from the notebook to the device itself.
Also his verison of ToolKit isn't what I been using, I have the terminal like green font'd 2013 toolkit by skipsoft is what I have outdated and no longer used or?
Click to expand...
Click to collapse
Yust use this command:
Code:
adb push (your rom file name) /mnt/sdcard/
Then go to flash menu and you will se your rom in your internal sd card

Ok, so I managed to re-flash my rom back on no problems at all. But problem with that is the gesture lock is still active.
Can someone give me a method to remove this from the account?

Try aroma file manager to delete gesture. Key
Sent from my GT-P3100 using xda app-developers app

sukkukikku said:
Try aroma file manager to delete gesture. Key
Sent from my GT-P3100 using xda app-developers app
Click to expand...
Click to collapse
Can you further explain this method?

Your device is rooted or not
Sent from my GT-P3100 using xda app-developers app

sukkukikku said:
Your device is rooted or not
Sent from my GT-P3100 using xda app-developers app
Click to expand...
Click to collapse
Have you read the thread what so ever..?
Yes the device is rooted, it's running PAC Rom newest Nightly.
The issue is, everytime I load the device I get the gesture lock which I don't have the correct information to. I want to reset the password back to a pattern or pin. Cause as of this point it requires me to login to my google account every time I fail to put the gesture in, meaning unless I have access to the wifi zone my device can't be logged into.

You need to install cwm recovery mode. You need to download aromafm1.80.zip file from net. It will be 1.4 mb. Place the file in external SD card. Go into recovery mode. Mount all partitions in advanced section. Then go to the file in SD card in recovery mode and flash the zip file there. Aroma file manager will open. Then go to data/system/gesture.key and delete that key. And reboot device. Pattern will appear but if you draw any pattern., the device will be unlocked
Sent from my GT-P3100 using xda app-developers app

i kinda get ya ,least ur not stuck in recovery same day buyin the bloody thing. my lil mistake of puttin folder instead of zip into internal storage now has me pullin hair out. why cant u just plug bk into pc and it opens the internal folder up.

sukkukikku said:
You need to install cwm recovery mode. You need to download aromafm1.80.zip file from net. It will be 1.4 mb. Place the file in external SD card. Go into recovery mode. Mount all partitions in advanced section. Then go to the file in SD card in recovery mode and flash the zip file there. Aroma file manager will open. Then go to data/system/gesture.key and delete that key. And reboot device. Pattern will appear but if you draw any pattern., the device will be unlocked
Sent from my GT-P3100 using xda app-developers app
Click to expand...
Click to collapse
You're telling me a several step process to "work around" the issue, instead of actually fixing it which isn't what I been asking.

It will remove the pattern lock
Sent from my GT-P3100 using xda app-developers app

[ROOT / TWRP][D851 ONLY][OSX/Linux/Windows] Root/TWRP your TMO G3 with PurpleDrake!

Howdy all!
What's this? Read on, dear reader, to discover the magic that is PurpleDrake.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is this?
This is a utility to easily root your LG G3 (specific models only). It's a fairly foolproof script that includes all the dependencies you'll need for getting your phone rooted easily.
This is the FULL version. This means that it will automatically root, and ask you if you want TWRP installed and a custom boot that doesn't trip the root checker!
Click to expand...
Click to collapse
Who made this?
This root is a collaboration between myself (IOMonster), jcase, and autoprime.
Special thanks also to beaups for some initial guidance looking at the vulnerable application.
Thanks to @Shelnutt2 for the security-disabled boot.img
Thanks to @Dees-Troy for the TWRP image!
Click to expand...
Click to collapse
Is my phone compatible?
The new LG G3 models each are slightly different with regards to rooting and unlocking.
To see a matrix of which LG G3 phones are compatible with this root, please see this Google Docs spreadsheet that we've compiled.
When you run this program, your phone will reboot and run a test to see if it's compatible. If the application succeeds, it'll let you know that it's able to permaroot you. If not, it'll fail gracefully and reboot you back to normal Android without having changed anything.
Please note that this version is currently only compatible with the T-Mobile D851 version of the LG G3. For other phones, we suggest you look for the LITE version of PurpleDrake.
Click to expand...
Click to collapse
How do I use this?
WE NOW SUPPORT WINDOWS! YAY ME
To start, for either platform you'll need to scroll down to the download section and get the file.
Ensure that your phone is in ADB mode (PTP Mode for everyone but Verizon. Verizon users need to be in "Internet"/"Ethernet" mode)
Linux Instructions (in a terminal!)
Extract the file you downloaded...
tar xvf ~/Downloads/PurpleDrake-TMO_VERSION.tar.gz
Mark the application as executable, and run it!
cd PurpleDrake-TMO
chmod +x purpledrake_linux.sh
./purpledrake_linux.sh
OSX Instructions (just a bit easier)
Extract the file you downloaded
Double-click on "purpledrake_osx"
Windows Instructions
Extract the file you downloaded
Double-click on "purpledrake_windows"
The application will guide you through all the steps you need.
You will still need to install SuperSU from the market after installing PurpleDrake. This pack does not include one.
If you choose to install the custom boot.img, your phone's root checker will not be tripped and your phone will show as UNROOTED.
After, be sure to check @autoprime's post for how to disable OTA upgrades! here : http://forum.xda-developers.com/showpost.php?p=54254111&postcount=2
Click to expand...
Click to collapse
But, what if I don't want to run your script to root?
Well then, I'd be a little hurt, but you can still do everything the script does manually.
Download the package, and extract it. Open a terminal in the main folder of the archive and run these commands:
Code:
adb reboot --bnr_recovery
adb push ./assets/start_restore /temp/start_restore
adb push ./assets/permaroot.bin /temp/start_restore
adb reboot
That will perma-root you, however there's no protection from doing something stupid or the phone being incompatible. Please be careful!
Click to expand...
Click to collapse
Where do I get this?
WINDOWS/OSX/LINUX VERSION OUT NOW!
- Fixed Windows support
- Fixed OSX ADB issues not detecting phone first try
- Fixed race conditions leading to errors permarooting
- Added 64-bit Linux ADB
Code:
[url]http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-TMO_R03.tar.gz[/url]
Old version here... (OSX/Linux only)
Code:
[url]http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-TMO_R01.tar.gz[/url]
Please DO NOT mirror or re-upload the PurpleDrake software to your own site, or any other file host.
If you need drivers for Windows (thanks @autoprime for having these handy!):
Verizon Drivers: http://downloads.codefi.re/autoprime/LG/LG_G3/LG VZW_United_WHQL_v2.14.1.exe
Everyone Else: http://downloads.codefi.re/autoprim...leDriver_S50MAN311AP22_ML_WHQL_Ver_3.11.3.exe
Click to expand...
Click to collapse
Help, it doesn't work!
Post here, let us know what happened and we'll try to help you. DO NOT private message us on XDA or on IRC asking for help. We will not assist privately.
Most questions if not answered here can be answered on #lg-g3 on IRC in Freenode.
Click to expand...
Click to collapse
Thanks so much! How can I show my appreciation?
Since this was a collaboration project, proceeds that are made from this root will be split between amongst us so we can purchase a Sprint test phone to root (as it's currently not rooted).
If you'd like to donate to us, click the "Donate to me" button on the left sidebar under my name, and be sure to enter a comment to let us know that you're donating towards the PurpleDrake project.
Thanks again!
Click to expand...
Click to collapse

FAQ:
Q: I'm running the Windows .bat as administrator and it's closing/not working.
A: There is no need to run the .bat as admin. Just double-click and run.
Q: I get the "Windows cannot find '.\assets\windows\bin\mintty.exe'." error.. watdo?
A: Try just double-clicking on the .bat instead of running as admin.
Also make sure the script is extracted properly first before running.
Q: I [used Flashify and] am stuck in fastboot.. how can I get out?
A: Be cautious using Flashify as it seems it's not working right.. or people are hitting the wrong buttons with it.
HERE are the stock TMO D851 partitions.
Use fastboot to flash recovery(TWRP or stock) and stock boot. This will install TWRP and fix booting into rom.
If on Windows you will need fastboot drivers. Use Google to find fastboot binaries and drivers.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
The commands to flash TWRP manually instead of using flashify is below.
Place TWRP on the root of your internal /sdcard/ using MTP, downloading it directly to phone or using ADB push.
Code:
adb push name_of_file.img /sdcard/
adb shell
su
dd if=/sdcard/name_of_file.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Disable OTA:
Open LG Hidden Menu (3845#*851#) --> WLAN Test --> OTA Setting --> OFF
*Replace "851" with your devices model number, 850, 852, 855 etc...
The first D851 update has been released (10M). Bootloader remained unlocked. It would appear future OTAs will be safe to take AS LONG AS YOUR PHONE IS NOT MODIFIED! If you have flashed TWRP or installed xposed or modified /system then you need to restore any changes made or flash stock firmware (tot/kdz) before taking OTA.
If using a non-tmobile g3 I would be hesitant about taking OTA updates. An OTA may update the boot stack to block Bump!
EFS Backup:
Code:
[FONT="Arial Narrow"][B]Backup EFS after jailbreaking your G3. EFS is split into 2 partitions modemst1 and modemst2.
img files will be on root of internal sdcard. Save the .img files somewhere else besides the sdcard... email, cloud, etc..[/B]
DO NOT FLASH OTHER PEOPLES EFS OR FLASH YOUR OWN BACKUPS ONTO ANOTHER PHONE.
THIS WILL BREAK EFS ON THE PHONE YOU ARE FLASHING TO. EFS BACKUPS ARE FOR THE PHONE THEY CAME FROM ONLY.
I have made a new thread on EFS backup and restore which can be found [URL="http://forum.xda-developers.com/lg-g3/development/efs-lg-g3-efs-backup-restore-t2907329"]HERE[/URL].
[/HIDE]
[B][SIZE="5"]Restoring Stock / Remove root flag:[/SIZE][/B]
[HIDE]
Download the tmo .tot file and use lg flash to restore it to stock. itll format everything on internal sdcard so backup anything u may need off it.
T-Mobile firmware can be found [URL="http://downloads.codefi.re/wolfgart/LG_G3/D851"]here[/URL]. Thanks to [user=608699]@wolfgart[/user] for the files and [user=1157052]@thecubed[/user] for codefire hosting.
*Step by step picture guide - [url]http://imgur.com/W83hMPE[/url]
install the drivers.
put phone into Download Mode (power off. unplug USB. pull battery. put battery back in. press/hold Volume Up then plug in USB cable.)
In Windows Device Manager set the phones serial COM port to #41. (*see picture guide for help)
Install [URL="http://downloads.codefi.re/autoprime/LG/LG_G3/Setup_LGFlashTool_1.8.6.527.zip"][B]LG Flash[/B][/URL]. In "C:\LG\LG Flash" folder delete megalock dll. Replace with .dll below.
new megalock dll - [url]http://bit.ly/1cQADXm[/url] (this site includes a "download manager.. UNCHECK THE BOX before downloading dll file.)
Run LG Flash in the "C:\LG\LG Flash" folder. Select korean factory if asked.
When LG Flash opens you will see a box to select firmware and dll.
Select [URL="http://downloads.codefi.re/autoprime/LG/LG_G3/LGUP_8974.dll"][B]LG Flash .dll[/B][/URL]
Select (.tot)
Hit OK (*see picture guide for help)
Hit yellow start button. If you get Milkyway error click ok. LG Flash will then run a crc check on the tot file. Takes a bit.
After crc check finishes unplug the phone. plug phone back in. it should now be seen in LG Flash and start flashing.
Phone will reboot when finished. You may end up on a screen with s "2"... let it sit there for a minute or two.
If stuck on "2" try unplugging the usb cable from the phone.. wait 10 seconds.. then plug the usb cable back in. now wait 30 seconds and hopefully it changes to a "3"
Once the phone says "3" you can unplug the USB.. remove the battery and plug back in.. boot back up... you are now 100% stock.
[/HIDE]
[B][SIZE="5"]PurpleDrake YouTube Videos:[/SIZE][/B]
[HIDE]
[url]https://www.youtube.com/watch?v=wJtz51KgxjM[/url]
[/HIDE]

And where is the bootloader unlock talked about at the bounty thread or was it just a hoax?
Gesendet von meinem LG-D855

Tectas said:
And where is the bootloader unlock talked about at the bounty thread or was it just a hoax?
Gesendet von meinem LG-D855
Click to expand...
Click to collapse
Hoax? What?
This pack is ONLY for the T-Mobile G3 which has an unlocked bootloader out of the box.
D855 support is NOT included in here. There will be a separate thread when we have an unlock for the bootloaders of the rest of the G3 family.

Tectas said:
And where is the bootloader unlock talked about at the bounty thread or was it just a hoax?
Gesendet von meinem LG-D855
Click to expand...
Click to collapse
There is no boot loader unlock..where ever you read this is misinformed...the T-Mobile variant ships boot loader unlocked, it is the only one so far to be shipping unlocked.

Sweet

thecubed said:
Hoax? What?
This pack is ONLY for the T-Mobile G3 which has an unlocked bootloader out of the box.
D855 support is NOT included in here. There will be a separate thread when we have an unlock for the bootloaders of the rest of the G3 family.
Click to expand...
Click to collapse
I'm aware of that and sry it wasn't meant offensive or to put this one down, autoprime, did imply at the bounty thread, that you as well managed to unlock the bootloader, at least at the beginning, that's what I'm referring to, sry that i said it the wrong way, was a bit disappointed, which for sure isn't your fault or the one of this tool, it's still great progress you made.
Gesendet von meinem LG-D855

I wish the international G3 D855 will be unlocked too
Sent from my LG-D855 using XDA Premium 4 mobile app

Great glad to see this released thank to all that is involved
LGG3 and beyond

All my family is sleep in the room with my Mac will be running asap bright and early. Thank you for your hardwork

Thecubed, autoprime, shelnutt2, jcase, and whoever else....thanks for this. Truly appreciated! Can't wait for Windows support. :Cheers:
Sent from my LG-D851 using XDA Premium 4 mobile app

Plans to support recovery for D855 in the near future?
Need to know to sell or not the G3 ?

What the hell software compatible with a mac that's a 1st whoop whoop well done guys and thanks for the hard work

Yeah great time to be a Mac owner

I have a feeling this treads about to turn in to a "when will this version be supported" topic :/
LGG3 and beyond

Success!
1. THANK YOU!
2. It didn't work the first time around, temproot worked but permaroot did not. Maybe it had to do with the fact that I was reading this forum while it was waiting for my input... I can't see how that would have made a difference but whatever. [[ Edit: It worked the second time running, I just followed the instructions immediately - no problems. /Edit ]]
3. Just a reminder for Linux users ... you have to add udev rules as described here: http://developer.android.com/tools/device.html ... and when you are done with that, also run:
$ sudo service udev restart; sudo killall -9 adb
4. My G3 would only connect to my laptop (Ubuntu 14.04) when it was in PTP mode. MTP or Charge Only did _NOT_ work... Only PTP.
5. THANK YOU AGAIN! You devs rock!
Frank.

Same as the guy above didn't work the first time but worked perfect the second! OSX here.

@ OP
http://forum.xda-developers.com/lg-g3/general/s-carrier-specific-g3-threads-t2818549

I keep getting no such file or directory, going to re download drivers and see

@thecuba not telling you what to do but maybe put this on T-Mobile thread as well http://forum.xda-developers.com/tmobile-lg-g3/development
Hope you don't take it the wrong way

Update to Marshmallow 6.0.1 Step by Step

This is a Step by Step guide to update from Lollipop build N920AUCU2APB2 to Marshmallow build N920AUCU2BPE5
Tools Required
1. ADB, download here, install with arguments Y, N, Y
2a If your current build is N920AUCU2APB2 download this update
2b If your current build is N920AUCS2APE3 download this update
2c. If coming from a different build number see Post #2 to manually ODIN back to PB2 then run the update in step 2a
******************
If you get "Error 403 Forbidden" on any of the downloads use the following work around:
Download the Chrome Extension 'User-Agent Switcher'
Once installed switch to the agent 'Googlebot (Googles Spider)'
Downloads will be working again
After the downloads have started switch the Agent back to 'Default'
******************
Thank you to @bmatney who uploaded the DL to here
MD5: 7941A2C689C5B141675593E3FA33FB9A
was tested on a Windows 10 64 bit machine.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and add the .zip extension to SS-G920AUCU3BOJ7-to-U3BOJ9-UP, so it is now called SS-G920AUCU3BOJ7-to-U3BOJ9-UP.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Danny\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCU2APB2-to-U2BPE5-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Danny\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
10.Type adb sideload SS-N920AUCU2APB2-to-U2BPE5-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Marshmallow
First time creating a How to post. If there is something not correct please let me know!
Thank you to
@sand_bit for his step by step guide in S6 forum here
@bmatney Mega upload

For those of you coming from a different builds here are the other links for updating:
From N920AUCU2APB2 to APE3 https://xdmd.sl.attcompute.com/agents/48725/1488/SS-N920AUCU2APB2-to-U2APE3
meek2100 said:
Here are the other update links people are asking for:
N920 Update File Links
(5.1.1) U2APB2 -> (6.0.1) 2BPE5 Credit to: ColoMtn
https://xdmd.sl.attcompute.com/agents/48725/1488/SS-N920AUCU2APB2-to-U2BPE5-UP
----------------------------------------
(5.1.1) 2AOJ1 -> (5.1.1) U2APB2 Credit to: meek2100
https://xdmd.sl.attcompute.com/agents/48725/1488/SS-N920AUCU2AOJ1-to-U2APB2-UP
----------------------------------------
(5.1.1) 2AOI6 -> (5.1.1) U2APB2 Credit to: meek2100
https://xdmd.sl.attcompute.com/agents/48725/1488/SS-N920AUCU2AOI6-to-U2APB2-UP
-----------------------------------------
(5.1.1) U2APB2 ODIN files for clean flash or restoring to STOCK can be found here. Credit to: Sunderwear
http://forum.xda-developers.com/att-galaxy-note5/general/note-5-marshmallow-odin-package-t3331843
------------------------------------------------------------------------------
Click to expand...
Click to collapse

ColoMtn said:
Tools Required
1. ADB, download here, install with arguments Y, N, Y
2. Odin, get a clean version from Sammobile here
3. Ensure your Note 5 is running Build: N920AUCU2APB2 this is the latest OTA available as of (5/16/16)
4. Download this to update from Lollipop PB2 ->PE5
Thank you to @bmatney who uploaded the DL to here
was tested on a Windows 10 64 bit machine.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and add the .zip extension to SS-G920AUCU3BOJ7-to-U3BOJ9-UP, so it is now called SS-G920AUCU3BOJ7-to-U3BOJ9-UP.zip
3. Shutdown your phone
4. Shutdown your phone, and enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd <Your Directory>
in my case: cd C:\Users\Danny\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCU2APB2-to-U2BPE5-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Danny\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCU2APB2-to-U2BPE5-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Marshmallow
First time creating a How to post. If there is something not correct please let me know!
Thank you to 
 @sand_bit for his step by step guide in S6 forum here
 @bmatney Mega upload
Click to expand...
Click to collapse
I'm getting "cannot read 'marshmallow.zip' " error

i keep getting dm-verity verification failed update from adb is disabled

creedicd said:
I'm getting "cannot read 'marshmallow.zip' " error
Click to expand...
Click to collapse
Did you make sure the directory had no Spaces and also move the ADB drivers to the same directory?
There are also users reporting that renaming the file 'marshmallow.zip.zip' fixes the issue.

im new to adb. i have no idea lol

blane3298 said:
i keep getting dm-verity verification failed update from adb is disabled
Click to expand...
Click to collapse
A quick google search says you may need to re-download the update

Odin?
ColoMtn said:
Tools Required
1. ADB, download here, install with arguments Y, N, Y
2. Odin, get a clean version from Sammobile here
3. Ensure your Note 5 is running Build: N920AUCU2APB2 this is the latest OTA available as of (5/16/16)
4. Download this to update from Lollipop PB2 ->PE5
Thank you to @bmatney who uploaded the DL to here
was tested on a Windows 10 64 bit machine.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and add the .zip extension to SS-G920AUCU3BOJ7-to-U3BOJ9-UP, so it is now called SS-G920AUCU3BOJ7-to-U3BOJ9-UP.zip
3. Shutdown your phone
4. Shutdown your phone, and enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd <Your Directory>
in my case: cd C:\Users\Danny\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCU2APB2-to-U2BPE5-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Danny\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCU2APB2-to-U2BPE5-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Marshmallow
First time creating a How to post. If there is something not correct please let me know!
Thank you to
@sand_bit for his step by step guide in S6 forum here
@bmatney Mega upload
Click to expand...
Click to collapse
Thanks man - awesome stuff. Why Odin download? Needed at this stage? Or just ADB sideload?

tr8ze said:
Thanks man - awesome stuff. Why Odin download? Needed at this stage? Or just ADB sideload?
Click to expand...
Click to collapse
Just ADB sideload. Will update. Thanks!
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app

Will these steps work on an encrypted phone?

darktrancer said:
Will these steps work on an encrypted phone?
Click to expand...
Click to collapse
Not sure.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app

I am on OJ1, do you think it will work? or is there any way to update from OJ1 to PB2, since I am not on the US and cant get OTA updates, thank you very much

any way this could be made into a odin flashable file?

mcepedaj said:
I am on OJ1, do you think it will work? or is there any way to update from OJ1 to PB2, since I am not on the US and cant get OTA updates, thank you very much
Click to expand...
Click to collapse
Try to update the url with in the original thread to reflect OJ1 and PB2 build numbers (can't look up the full build numbers right now). If that works use this same guide to apply the update.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app

blane3298 said:
any way this could be made into a odin flashable file?
Click to expand...
Click to collapse
I don't know how to do that but side loading was fairly simple.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app

so i can get up to the point of doing the "adb sideloade" command but i get the cannot read error. where can i locate the adb drivers? im new to adb and sideloading. thanks for the write up though.

bdevillier19 said:
so i can get up to the point of doing the "adb sideloade" command but i get the cannot read error. where can i locate the adb drivers? im new to adb and sideloading. thanks for the write up though.
Click to expand...
Click to collapse
Step 1
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app

ColoMtn said:
Step 1
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Click to expand...
Click to collapse
step 1 of the tools required section? i've done that numerous times. it says the driver is installed but doesnt give me any info as to where the drive is at. thanks for the reply

I'm trying to download the update from the Mega link provided earlier. It is taking SO LONG.
I'm getting impatient.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app

Working on getting apps reinstalled... AT&T loaded more **** on this firmware than they ever have before. Ridiculous.