Develop Bugs

[HOW TO][LTE] Revert to original 4.0.1 STOCK on Windows

Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!

Thanks, this worked for me. However, it does not re-lock the bootloader. You can tell by when the Google logo is on the screen while booting up, if there is an unlocked lock on the bottom then it is unlocked. To fix this, type in:
flashboot oem lock
Click to expand...
Click to collapse
After that you should be good to go again and be stock.

Why not use the 4.0.2 image? Makes more sense to use the latest version:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz

I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?

Zzim said:
I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?
Click to expand...
Click to collapse
If you've got the SDK installed put the fastboot files in the sdk\tools or sdk\platform folder where adb is located. The adbwinapi.dll should be located in there.
Or just copy adbwinapi.dll into the same folder where you have the "restore kit" files downloaded from the OP.

confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus

error
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz

djeddieone said:
confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus
Click to expand...
Click to collapse
cerotes have galaxy nexuses? hrm

mikedfromaz said:
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz
Click to expand...
Click to collapse
Winzip.. unzip it twice...
Sent from my Galaxy Nexus using XDA App

edit: got it thanks

Thank you for the script..i know it will come in handy one day or another!
Sent from my Galaxy Nexus using xda premium

whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?

bigeric828 said:
whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?
Click to expand...
Click to collapse
It was zipped with WinRAR as a standard zip file. Should be able to be opened on just about anything... Have you tried redownloading?

oops already posted this but i put it in the wrong thread but here it is again sorry.
does anyone know how i can get this working? whenever i run it i just get an error: device not found
waiting for bootloader...
flashing bootloader...
error cannot load "bootloader-toro-primek10.img"
<waiting fo device>
anyone suggestion? ive tried reinstalling the drivers and its still not working
any help is appreciated thanks

so.....how do we run the script? with fastboot? with what commmands? it's late, i'm tired and i just want to start from scratch on my GNex...had Wallet running, then loaded BB, lost Wallet, now wallet won't run on ANY rom i have, even rebuilt to 4.0.2, but need to get back to 4.0.1...i posted a question in the Q&A section if there was an ODIN of 4.0.1 lying around somewhere....hopefully i'll get some help either way...
thanks.
EDIT...got it, double click the bat file...the original post did not say that.....thanks for the last post for mentioning it

|Jason8| said:
Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!
Click to expand...
Click to collapse
Having seen the Nexus S sticky for factory firmware etc., I think its time we see this or another post evolve into the same sort of thing including full restores for 4.0.1, 4.0.2 and the eventual 4.0.3(lte) radio's etc.,

Here's a modified script that will allow you to choose between 4.0.1 and 4.0.2. (as long as you have either image or both) It also has the option to re-lock the bootloader.
I'll also update it when the official 4.0.3 images are released.
I don't take no credit for what was already done, I just modified it
{
"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"
}
Instructions:
=========
1- Extract folder with contents of this package.
2- You will need the Google Factory image for the version you want to restore, or both if you want.
3- Extract the image files to the same folder in step one. Image files should not be in a seperate folder!
So you should have, in one folder, the above files contained in this package plus:
image-mysid-xxxxxx.zip (xxxxxx= pertains to what version)
radio-tor-i515.xxxx.img
radio-cdma-tor-i515.xxxx.img
flash-all.sh
bootloader-tor-primexxxx.img
4- Dbl click on GNexRestore.bat and follow the prompts.
Optionally, if you do have the Android SDK installed, just copy the image files and GNexRestore.bat to the platform-tools folder.
fastboot.exe will also be needed, if you don't have it already, just copy the one in this package to the same location.
Then run GNexRestore.bat

when you extraxt the factory image i get one file and the icon looks like a blank piece of paper. is that how it is suppose to be

When you extract the image, you should see a folder with the files you need.
e.g. this is from 4.0.2

Sorry, just a mess

But thank all you guys to point it out

Very kind, hope it helps many.

Should we format /system qheb installing rom? When is the best time to wipe battery stat?
Sent from my GT-I8150 using Tapatalk

FelixAusChina said:
[HOW TO]root, flash custom recovery ClockworkMod v5.5.0.4 and ROM Customized 1.8Ghz ROM (now with experiment EUR OC ROM) without odin step by step from offical ROM 2.3.6
1. Root your phone
Rooting via Recovery mode(SD card)
a. Download this Zip-file http://dl.dropbox.com/u/47601401/update.zip copy this into the internal SD card.
b. While switched off, keep the following buttons pressed. Release the power-button once the Samsung Galaxy W(I8150) is switched on. At last press the menu button quickly while pressing the other two buttons.
Note: This instructions is written for the stock recovery. Custom recoverys should work very similiar.
{
"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"
}
c. Navigate with the volume up and down to apply sdcard:update.zip in Recovery Menu. Use the home-button to confirm your selection.
d. Choose (with volume buttons) the update.zip file on your internal sd card and confirm again with Home-button. You will have to wait for several seconds.
e. Now choose reboot system now and confirm with home button.
Now you device should be rooted.
The link: http://forum.xda-developers.com/showthread.php?t=1317394
2. Enable recovery ClockworkMod v5.5.0.4 with flashing in adb shell.
Don't flash the zip file, but extract and flash the img file
a. Root your devece(look above)
b. Copy downloaded recovery ClockworkMod v5.5.0.4http://www.multiupload.com/KTNBHX6JBG on internal sdcard
c. Disconect phone from copmuter and make sure that USB debugging is on
d. Connect it again but don't connect phone memory (computer shouldn't see sdcard and internal memory in Windows explorer)
e. Download the adb shellhttps://rapidshare.com/files/1061144422/android-sdk-windows.zip
note:If you just want to obtain and perform adb command, rather than to develop Android software, in fact, there are many adb streamline packets in internet, don't need the full Android SDK.
As the android-sdk version started from r08, adb wasn't contained in the downloaded files from the beginning, but was downloaeded by SDK Manager after that, and adb wasn't under the original tools directory. To maintain the text of the description of teaching would continue to apply the screen, I made ​​out of adb streamlined package from the r07 version.
f. Extract the file android-sdk-windows.zip into the root directory of C for teaching easily
g. open command prompt
windows 7: start-all programs-accessories-command prompt or search cmd
h. Then in the "Command Prompt" window, type the following command to switch to the adb directory
c:
cd c:\android-sdk-windows\tools
i. Enter the "adb shell", enter the phone to start the next command (think of it as the phone has a similar "command prompt" environment)
go on with this code:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip
j. Now turn off phone and turnd it on like this: hold Volume Up + Home + Power button, when Samsung sign appears relese power button but still hold other two, until recovery is loaded.
3. Download which ROM you like
4. Put the zip into Internal SD
5. Boot into ClockWorkMod, backup your current ROM using nandroid (just in case) then, use Install menu to Wipe data/cache and to install it from the SD card.
By the way, when you enter into the ClockWorkMod recovery, press the volume up-down-up for 3 times, you will see the option "go back" in the recovery menu.
Click to expand...
Click to collapse
By this method, is our bootloader is still locked?

Man, with all due respects, your post, and instructions are a mess, and particularly where you show adb commands to flash RzRecovery, then tell ppl here to do this:
go on with this code:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
Click to expand...
Click to collapse
but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip
Click to expand...
Click to collapse
That is a total mess, and you make complicated particularly for noobs, something which is not complicated........
don't you know you have to be careful with "dd".....as it is called sometimes Data Destroyer:
http://www.softpanorama.org/Tools/dd.shtml
Just be careful ppl !!!

i just bought the new phone in germany, and updated to 2.3.6 by kies, then i decided to flash the custom rom, from root to recovery and to rom, so i checked all the trreads here, so i did it like i just said above, and it has worked for 3 days perfectly, so i wanna share my way to do that. because my phone is a new one, so i didnt' need to backup anything...
by the way, have u checked the thread [RECOVERY]Samsung Galaxy W i8150 RZRecovery by qzem??? it's here http://forum.xda-developers.com/showthread.php?t=1376196 i just followed that way...

irishpancake said:
Man, with all due respects, your post, and instructions are a mess, and particularly where you show adb commands to flash RzRecovery, then tell ppl here to do this:
That is a total mess, and you make complicated particularly for noobs, something which is not complicated........
don't you know you have to be careful with "dd".....as it is called sometimes Data Destroyer:
http://www.softpanorama.org/Tools/dd.shtml
Just be careful ppl !!!
Click to expand...
Click to collapse
i just bought the new phone in germany, and updated to 2.3.6 by kies, then i decided to flash the custom rom, from root to recovery and to rom, so i checked all the trreads here, so i did it like i just said above, and it has worked for 3 days perfectly, so i wanna share my way to do that. because my phone is a new one, so i didnt' need to backup anything...
by the way, have u checked the thread [RECOVERY]Samsung Galaxy W i8150 RZRecovery by qzem??? it's here http://forum.xda-developers.com/show....php?t=1376196 i just followed that way...

OK, Felix, it's not really a problem.......
but writing or copy/paste stuff in a Admin Command Prompt is hard enough, without having to modify the text you are quoting.
How hard could it be to post this:
adb shell
$su
#dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
Click to expand...
Click to collapse
This is what ppl will have to write into the dd command
if = input file.....of = output file
Use dd cautiously, improperly entering the wrong values could inadvertently wipe, destroy, or overwrite the data on the hard disk drive or device memory
Click to expand...
Click to collapse
BTW, me and qzem were probably two of the first on these forums, before we had dedicated forum......

irishpancake said:
OK, Felix, it's not really a problem.......
but writing or copy/paste stuff in a Admin Command Prompt is hard enough, without having to modify the text you are quoting.
How hard could it be to post this:
This is what ppl will have to write into the dd command
if = input file.....of = output file
BTW, me and qzem were probably two of the first on these forums, before we had dedicated forum......
Click to expand...
Click to collapse
but i have written "but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip" in my first post, haven't u seen that? I am gonna highlight it...but thanks for your remind and works for our SGW

Felix, I give up....but thanks for taking on board my suggestion....it may just save someone from a major catastrophe.
thanx again
ATB

FelixAusChina said:
but i have written "but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip" in my first post, haven't u seen that? I am gonna highlight it...but thanks for your remind and works for our SGW
Click to expand...
Click to collapse
The point is - why include the first (i.e. incorrect) version of the command at all? It would be much clearer just to include the correct version, after the change you mention. Including the incorrect version just makes the instructions more confusing.

FelixAusChina said:
But thank all you guys to point it out
Click to expand...
Click to collapse
Man, don't cry!!!!
sorry for being so blunt, but it's important, especially when using adb, and commands like dd to get it exactly right/correct......
we don't wanna brick anyone's phone
But, thanks anyway, the guide is basically good!!!
cheers, OK

FelixAusChina said:
But thank all you guys to point it out
Click to expand...
Click to collapse
Don't mistake directness for hostility.
We didn't want you to remove your guide completely - we're just trying to help improve the quality of it, for everyone's sake. Collaboration is what this forum is all about.
Restore the guide, make the suggested improvements, and let's see if we can make it even better.

[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!

[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

Adb sideload error

hi, I've tried to clean install oos 4.0.3 with adb side load and it show me error 'cannot read .zip'
when I enable adb trace, it show me error like this
adb sideload ota.zip
load_file: 324: 1020 | load_file: could not allocate 1504196936 bytes
* cannot read 'ota.zip' *
anyone can help me ?
{
"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"
}

Yep known error, wrong drivers, not much known of the issue. Do you have TWRP? Then type adb push zipfile /sdcard/ then you can manually flash it.

Puddi_Puddin said:
Yep known error, wrong drivers, not much known of the issue. Do you have TWRP? Then type adb push zipfile /sdcard/ then you can manually flash it.
Click to expand...
Click to collapse
1.I'm not sure cause of wrong driver because I just sideload oos Open beta 11 3 days ago, and it work well;
2. yep I've TWRP, but I want to find down why I got this bug

isibiki said:
1.I'm not sure cause of wrong driver because I just sideload oos Open beta 11 3 days ago, and it work well;
2. yep I've TWRP, but I want to find down why I got this bug
Click to expand...
Click to collapse
Oh ye even weirder.. have you tried "adb kill-server"? Maybe rebooting the PC while keeping the phone plugged in? Last one helped for me once.. But i still cant sideload either.

Puddi_Puddin said:
Oh ye even weirder.. have you tried "adb kill-server"? Maybe rebooting the PC while keeping the phone plugged in? Last one helped for me once.. But i still cant sideload either.
Click to expand...
Click to collapse
I tried everything like re-install driver, adb kill-server, larger address adware and more, but it didn't work. Luckily oos stock recovery can install from internal storage or flash twrp and install throught it

You are on a 32 bits windows computer. Which is unable to load the entire file in memory on default settings.
You should try this:
jstegeman said:
I will point out that adb.exe on Windows is not linked to be "large address aware" If you set the environment variable ADB_DEBUG=all and try to adb sideload a large file, you'll see that the call to malloc is failing to allocate enough memory for the file. The "obvious" fixes would be for adb not to try to read the entire file into memory or to be linked with the /LARGEADDRESSAWARE flag on Windows.
As a workaround, I've used https://www.techpowerup.com/forums/threads/large-address-aware.112556/ to make adb.exe large address aware, and it's now working for me.
Click to expand...
Click to collapse

JorgeManuelSilva91 said:
You are on a 32 bits windows computer. Which is unable to load the entire file in memory on default settings.
You should try this:
Click to expand...
Click to collapse
My computer running 64 bit windows 10 and I already tried this solution and it didn't help me resolve this bug

isibiki said:
My computer running 64 bit windows 10 and I already tried this solution and it didn't help me resolve this bug
Click to expand...
Click to collapse
Then, your computer may be out of RAM, check how much RAM your computer has and close programs you're not using.

JorgeManuelSilva91 said:
Then, your computer may be out of RAM, check how much RAM your computer has and close programs you're not using.
Click to expand...
Click to collapse
8gb ram with 56% free memory isn't enough ?, I think it because L Speed app I install in my phone, after install it, I cannot full unroot in super su app and this adb error happened after that.

isibiki said:
8gb ram with 56% free memory isn't enough ?, I think it because L Speed app I install in my phone, after install it, I cannot full unroot in super su app and this adb error happened after that.
Click to expand...
Click to collapse
Check this topic on OnePlus forums: https://forums.oneplus.net/posts/15306505
I had the cannot read 'update.zip' issue. Turned out it'd been installed as the wrong device in Windows 10 - it'd been recognized as a Marshall London Phone for some reason. To fix it, I removed it from device manager, and told it to delete the drivers. Then rescanned, and reinstalled it as a standard Android ADB Interface - it then accepted the file on the sideload. Drove me mad for a couple of days!
Click to expand...
Click to collapse