Develop Bugs

[GUIDE][ROOT][19/Nov] r14: VISIONary + one click root

{
"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"
}
Note: This application is no longer being updated and is only recommended for use on Froyo builds.
What is VISIONary?
VISIONary (so named because it was originally an application designed for the T-Mobile G2 / HTC Vision) is an application you install on your device that allows you to Temproot or optionally Permroot your device, using the 'rageagainstthecage' exploit.
How do I use it?
It's pretty simple really. The options appear as follows:
Temproot on boot - use this to automatically Temproot on each boot (I suggest Temprooting manually first to confirm all is well before enabling this)
Run visionary.sh after root - this allows you to run a script (as root) after rooting. The script file is /data/local/visionary.sh
Set system r/w after root - this allows you to leave the /system partition read/write after root
Temproot now - root temporarily (the root wil be lost after reboot)
Attempt permroot now - attempt to apply a permanent root (please read the safety information below before doing this!)
Unroot now - this will unroot your device
Safety information!
You use VISIONary at your own risk! Although we test it as much as possible, we are unable to guarantee that weird things won't happen.
As a rule, the 'Temproot' option of VISIONary should be completely safe. It installs an application (Superuser) in the conventional way and then sets up a 'ramdisk' for the other parts, which is wiped on boot. As such, no changes are made to the system partition of your device, hence it is considered a 'safe options'.
Permroot on the other hand is inherently more risky. Permroot does make changes to the /system partition of your device. Technically speaking the only change that is made is the installation of a small file to /system/xbin, but any system partition change comes with risks. If you try to permroot, be aware that you might get into a situation where your device will not boot. For this reason, we recommend you have a 'safety net'.
In general, the best 'safety net' for going ahead and doing a Permroot is ensuring that you have a copy of the stock ROM to reinstall should things go wrong. This should be an original update EXE or zip from your device manufacturer / provider which matches the software version currently installed on your device. Bear in mind that flashing older versions is often not possible, so if your device has been updated over-the-air, an update may not yet be available in this form. Hence, you may not be able to find a 'safety net' and attempting to Permroot would be inherently risky. For HTC devices at least, one option would be to Temproot, edit the MISC partition to revert the 'mainver' to an older version, thereby allowing you to flash an update older than the currently installed version should things go wrong. That option is currently outside the scope of this post, although I will provide details on how to accomplish this in another post.
Got your safety net? Aware of the risks? The download is below.
Download
r14 - (see changelog below for details) - [url="http://android.modaco.com/content/software/320350/19-nov-r14-visionary-one-click-root/]DOWNLOAD[/url]
The download is in APK format (if it is downloaded with a 'zip' extension simply rename). Copy to your device and click to install (or run 'adb install -r com.modaco.visionaryplus.r14.apk' if you have the SDK installed).
NOTE: USB DEBUGGING MUST BE ENABLED FOR VISIONARY TO WORK!
And finally
Details on how to donate should you wish to do so are in download topic at MoDaCo.
Enjoy!
P

thanks for you guys work

works perfectly! thanks

Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App

Question Answered..
Thank you P, my reboot question has been answered... just click and proceed. (To Be Tested)
It feels so good to see you on the scene.. It's been a while.. Since the N1

v8pwrdz28 said:
Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Same here

v8pwrdz28 said:
Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Reboot and try again...
P

paulobrien said:
Reboot and try again...
P
Click to expand...
Click to collapse
How long should the program run?

I have no experience whatsoever in developing or rooting on Android, so excuse me if this is a stupid question. When you say that if we want something to happen every time we finish rooting at bootup, to put it in /data/local/visionary.sh, what exactly does that mean? How does one go about doing this?

when i run this it just keeps saying rooting device with spinning wheel at top then it reboots

Not Working
Just getting the spinning wheel and flashing with no progress. Even tried to reboot and start over with no results

Thank you for making my life easier.

Does this app require you to do the "one-time" first step of the temp root process before you can use it?

Like others have said, this doesnt work for me. Just flashes rooting please wait and nothing happens.

Hey thanks it worked .. At first it kept running and nothing happened, so i rebooted the phone and it worked in the first try.

LogicHell said:
Does this app require you to do the "one-time" first step of the temp root process before you can use it?
Click to expand...
Click to collapse
No...
P

What should happen...
Boot device
Click VISIONary icon
Phase 1 runs
Logo disappears briefly as app reloads
Phase 2 runs
App disappears and root is complete
If this doesn't happen, I suggest rebooting and trying again.
P

Does it use the old 'root' script (copy everything to /system/bin and /system/app) or the new method? The old one expires eventually when linux drops the cache, the new one stays forever (until reboot). (Also, putting superuser on /data/app means it remembers it's permissions and grants across reboot, instead of losing it every time.)
The updated script is here:
Disconn3ct said:
FYI I altered the script to survive cache flushes and such. If you use this instead of the old 'root' script (and put everything in /data/local/bin instead of tmp) it will make the bare mininum number of changes to /system and those changes will last until you reboot (instead of flushing out over time).
Click to expand...
Click to collapse

Auto Root
I downloaded Startup Manager from the Market and set VISIONary to auto load on each bootup and so as of right now it auto loads with each restart. Very handy until it auto loads on itself. Just a thought.

Disconn3ct said:
Does it use the old 'root' script (copy everything to /system/bin and /system/app) or the new method? The old one expires eventually when linux drops the cache, the new one stays forever (until reboot). (Also, putting superuser on /data/app means it remembers it's permissions and grants across reboot, instead of losing it every time.)
The updated script is here:
Click to expand...
Click to collapse
Good call on putting the Superuser APK on /system/app! re: the 'old' or 'new' way, i'm doing it the old fashioned way (didn't know there was another way, heh)!
If you can point me to it, i'll change it for r2.
P

[STOCK][C650X][4.3] Update to 10.4.B.0.569 [Root & XZDualRecovery][DE-/ODEX]

{
"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"
}
Requirements:
Flashtool by @Androxyde
XZDualRecovery 2.6 RELEASE or newer.
Current FW version: 10.3.1.A.2.67, maybe others too, let me know!
Special features:
SuperSU integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.7.43 BETA (CWM & PhilZ Touch & TWRP) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
For both locked and unlocked bootloaders!
The C6503 ROM is based on the FTF provided by @Androxyde in this thread. Thanks dude
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
How to update to 10.4.B.0.569:
Files:
For C6502: Download C6502.flashable.10.4.B.0.569.zip (Bittorrent: 807MB) and C6502_10.4.B.0.569_Stripped.ftf (18MB)
For C6503: Download C6503.flashable.10.4.B.0.569.zip (Bittorrent: 778MB), SuperSU_fix.zip (1.1Mb) and C6503_10.4.B.0.569_Stripped.ftf (18MB)
For C6506: Download C6506.flashable.10.4.B.0.569.zip (Bittorrent: 778MB) and C6506_10.4.B.0.569_Stripped.ftf (18MB)
Save them somewhere you remember;
Put 'C650X.flashable.10.4.B.0.569.zip' on (the external) SDcard1;
Put 'C650X_10.4.B.0.569_Stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C650X.flashable.10.4.B.0.569.zip' in TWRP (after flashing the ROM also flash 'SuperSU_fix.zip', needed only when using the C6503 package)
do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C650X_10.4.B.0.569_Stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone.
As I do not have a ZL, @Bird40 tested this release prior to creating the thread, so I know it works fine
Enjoy! :laugh:
DE-ODEX your ROM! (Read the NOTE below this guide before flashing!)
AFAIK you can use this deodex package on the C6502 and C6506, as the base apps and framework are the same.
Make sure you have the flashable ROM installed before you do this.
Download C6503_deodex.10.4.B.0.569.zip (Bittorrent: 383MB), save it somewhere you remember;
Put 'C6503_deodex.10.4.B.0.569.zip' on (the external) SDcard1;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6503_deodex.10.4.B.0.569.zip' in recovery, do not reboot but go back to the main menu;
Clear dalvik-cache ONLY;
Reboot to system.
The first boot after flashing this you will see Android optimizing the apps on your phone, this might take a while... but should be just fine
NOTE: There are some issues with the deodexed ROM, it sometimes causes a FC, specifically if you go to keyboard & language settings through the settings app. I'm not able to find why it does this but my guess is that it's a bug in the Sony ROM that surfaces with deodexing it... There is a work around for this one though: Open any keyboard driven app (text editing/entering box), tap '12!?' and then tap the tools button on the right of the space bar. This will take you to the app to modify your keyboard settings.
Known XZDualRecovery Issues:
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a /system ONLY using any means you are familiar with so you can try again.
Root it using [Z][ROOT] DooMLoRD Easy Rooting Toolkit.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you

thanks!!! testing

It works perfect! Thanks a lot

will it work on c6502 .569 fw?

[NUT] said:
As I do not have a ZL, @Bird40 tested this release prior to creating the thread, so I know it works fine
Click to expand...
Click to collapse
All is well.
Thank you.

So we can't install busybox on this?

LiLTrippz said:
So we can't install busybox on this?
Click to expand...
Click to collapse
Whenever I try to open root explorer it doesn't work, as if I don't have root perms, it's like superuser is denying everything but in root checker it says i have root access???

LiLTrippz said:
Whenever I try to open root explorer it doesn't work, as if I don't have root perms, it's like superuser is denying everything but in root checker it says i have root access???
Click to expand...
Click to collapse
ok same problem and i cant boot into recovery as well
root checker : this device does not have proper root access

demonicjas said:
ok same problem and i cant boot into recovery as well
root checker : this device does not have proper root access
Click to expand...
Click to collapse
Well I just fixed it, my problem was fixed by going into supersu and i just made the settings to always grant.

LiLTrippz said:
Well I just fixed it, my problem was fixed by going into supersu and i just made the settings to always grant.
Click to expand...
Click to collapse
i have to do everything all over again ..
back to .244 and headed from there now
edit : done .
all good

If you run into the superuser 'grant all' issue, look up the app in the settings and clear all its cache and user settings.
That should fix that problem.

i have a problem.....
when i give root acces to a app (like root explorer or unnistaller root) before the update, i have no problems with root access after the update.... but if i do this after update, i mean, install a root app after update, i have not root access for that app, even if i have the supersu app and recovery.
any idea about how to resolve it????
MY PRINCIPAL PROBLEMS IS WITH XPOSED

There is one problem, Xposed Framework doesn work I installed the last version but still when I reboot phone, it still shows me framework is not installed yet and tells me I need to reboot again, but still it doesn work.
Anyone got this issue?

someone is having trouble with ADB after updating with this method?
Enviado de meu C6503 usando Tapatalk

felipeacydc said:
i have a problem.....
when i give root acces to a app (like root explorer or unnistaller root) before the update, i have no problems with root access after the update.... but if i do this after update, i mean, install a root app after update, i have not root access for that app, even if i have the supersu app and recovery.
any idea about how to resolve it????
MY PRINCIPAL PROBLEMS IS WITH XPOSED
Click to expand...
Click to collapse
batrian said:
There is one problem, Xposed Framework doesn work I installed the last version but still when I reboot phone, it still shows me framework is not installed yet and tells me I need to reboot again, but still it doesn work.
Anyone got this issue?
Click to expand...
Click to collapse
xposed issue is known .. Rovo89 is already working on it

any other root app have the same problem..... it doesnt apear the messege requesting root access.

[NUT] said:
If you run into the superuser 'grant all' issue, look up the app in the settings and clear all its cache and user settings.
That should fix that problem.
Click to expand...
Click to collapse
felipeacydc said:
any other root app have the same problem..... it doesnt apear the messege requesting root access.
Click to expand...
Click to collapse
.....

fixed.... my bad!
i just grant root access without request, just to all, and it works perfect.

I'm trying to find a solution to this... Luckily we have a working recovery to restore it any way we can

bug from busybox!!!
tnx for rom

[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

Busybox fails to install

Accidentally installed the wrong busy box apk but cleared data and uninstalled then i tried installing the correct version of stericson busybox free and I'm greeted by this message
"There was a problem opening a shell with root access. this is either cause by supersu or by a device that is improperly rooted..."
It then goes on to say i should change permissions in supersu then reinstall. Of course I can't do this because our supersu does not have a settings menu.
I'm looking for help. Is there a way to resolve this over adb and change the su settings? Or can i reinstall supersu?--would that give me the popup i need to grant permissions (if that is in fact the issue...)
I'm not certain i can just run towel root again and reinstall supersu. I have the latest prerooted firmware installed.
BTW--I'm curious as to what happened. thinking the wrong busy box app is still causing issues because i did the same thing on my other fire tv and could easily install busy box again. Thanks.

You should be able to open the settingsmenu (or the apps list) of SuperSU in the FireTV system settings menu -> installed apps tab. Just start the SuperSU app for that.

Calibaan said:
You should be able to open the settingsmenu (or the apps list) of SuperSU in the FireTV system settings menu -> installed apps tab. Just start the SuperSU app for that.
Click to expand...
Click to collapse
Unless I'm misunderstanding, you can't do that with our supersu (think its just the way rbox designed it that supersu can't be opened). Go to applications and try it. I assume your setup is the same as mine--cwm & and prerooted firmware.
I'm thinking I'll just uninstall/reinstall supersu, but not even sure that will resolve the busybox issue.

No, I have not a rooted aTV (those for the german market were never deliverered with a rootable firmware, hope this changes with stagefright vulnaribilty). I assumed you´re running the regular SuperSU from Chainfire which does acts as a Superuser access management tool:
{
"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"
}
It should be possible to call this superuser app from the apps tab within the system menu like every other sideloaded app. Of course when you´re running another supersu app this probably won´t work.

Calibaan said:
No, I have not a rooted aTV (those for the german market were never deliverered with a rootable firmware, hope this changes with stagefright vulnaribilty). I assumed you´re running the regular SuperSU from Chainfire which does acts as a Superuser access management tool:
It should be possible to call this superuser app from the apps tab within the system menu like every other sideloaded app. Of course when you´re running another supersu app this probably won´t work.
Click to expand...
Click to collapse
Thanks. I have read in other thread people talking about using superuser app to access those settings we can't get with supersu on AFTV. That was a long time ago and don't think there was much feedback on how it worked.
I messed things up more than I thought. None of my root apps are working (ROM manager, titanium backup, samba file sharing, etc.
Wondering if just reinstalling the ROM.zip will fix everything? Only thing about that is it doesn't ask to regrant su for my installed apps normally. Not sure if it'll be different because root isn't functioning properly...

So maybe someone can confirm this? If I wipe factory reset in cwm will supersu reinstall and reset su settings? (Actually pretty sure it will) But really rather not do that because I'm forward thinking enough to install titanium backup but not smart enough to backup apps and data (always put it off then forgot) Now of course I can't use titanium.
So if that's my only option I'll do it but hoping there's a simpler way like flashing supersu zip in recovery. AND if that's an option should I first remove supersu apk in system/app?

I've had issues with the Busybox installer, too. It claims you can begin installing right away, but it's a good idea to wait until it finishes its scan to do the install.

Sizzlechest said:
I've had issues with the Busybox installer, too. It claims you can begin installing right away, but it's a good idea to wait until it finishes its scan to do the install.
Click to expand...
Click to collapse
Well I didn't actually want busybox installer. I wanted busybox free by stericson. I'm not even sure if the installer is by stericson. So did you try to run that installer program again and let it complete? Or were you actually talking about busybox free which is what I've always used on AFTV (its the recomended version we all are probably using). But not paying attention I installed the wrong apk. Now none of my root apps work which I don't understand. Busybox having trouble makes sense but pretty sure I've run other root apps without busybox in the past.
Its looking like I need to wipe it but not in a huge hurry. The AFTV functions OK without root so I'll hang around for a better solution.

KLit75 said:
Well I didn't actually want busybox installer. I wanted busybox free by stericson. I'm not even sure if the installer is by stericson. So did you try to run that installer program again and let it complete? Or were you actually talking about busybox free which is what I've always used on AFTV (its the recomended version we all are probably using). But not paying attention I installed the wrong apk. Now none of my root apps work which I don't understand. Busybox having trouble makes sense but pretty sure I've run other root apps without busybox in the past.
Its looking like I need to wipe it but not in a huge hurry. The AFTV functions OK without root so I'll hang around for a better solution.
Click to expand...
Click to collapse
This is what I was referring to: https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Can you connect to your Fire TV using adb and do a "su" command to see if you get root? Did you fully unlock your bootloader?

Sizzlechest said:
This is what I was referring to: https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Can you connect to your Fire TV using adb and do a "su" command to see if you get root? Did you fully unlock your bootloader?
Click to expand...
Click to collapse
That's the one that won't install. Yes. I can connect adb, reboot recovery and bootloader fully unlocked. I can't access everything in es file explorer because the root explorer option won't work without su permissions. But adb shell will get the # sign.

[GUIDE][BR][LP]Complete guide for unlock bootloader and flash TWRP in H442F DUAL SIM

Hello folks!
It's been a while since last time I spent in this forum section (when the method for flashing Poland MM KDZ was published), but suddenly I decided to check the current development and it was great do discover that developers found a way to unlock bootloader! Then, I tried to do the procedures, found some adversities around the path, flashed stock KDZ for my device A LOT and finally managed to obtain a fully working LP stock with root and TWRP for my model: H442F (Dual SIM) ("LG Volt 4G" in Brazil).
The thing is: although a lot was done regarding the Spirit LTE, I found near zero information specifically for my device variant. Since I tried a lot of paths and eventually achieved an interesting result, I decided to write a full tutorial, with a lot of instructions and pictures for "novices" who desire learn all the steps but gives up at the high learning curve. Finally, I also wrote this tutorial in Brazilian Portuguese, which I believe will help at least some comrades (you can download the PDF in portuguese HERE).
Needed files:
LG Drivers (remove old ones if already instaled)
LG Flash Tool 2014 (credits to @quangnhut123 from this thread)
Brazilian H442F10a Firmware (this is a low speed server, I can upload to a better one if someone asks)
Android SDK Tools (for Windows users; Linux ones just install the package android-tools-adb)
Kingroot (or download here: www.kingroot.net)
Latin America Patched Aboot (credits to @pvineeth97 , for more info check this thread)
TWRP (or download here: https://twrp.me/lg/lgspiritlte.html)
Flashfy (or download here: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en)
SuperSU (or download here: http://www.supersu.com/)
Finally, if you prefer, you can download a full pack in this link (except for KDZ), however, I did prefer to keep isolated links for better credits and referrals
Step-by-step
Download all needed files
Install drivers, SDK and unpack Flash Tool
Save all files in the same folder, but keep KDZ file inside Flash Tool folder
Put your phone in download mode (power off, hold vol+, plug usb in pc, keep holding until download icon appears)
Wait a little for Windows completely detects device and load all drivers
Verify in Device Manager if your pc detects phone as "LG Mobile USB Serial Port (COM#)"
{
"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"
}
Open LG Flash Tool as admin
Select KDZ file
Choose the downloaded H442F10a_03.kdz file
Choose CSE Flash
Click START
Then, "Clear phone software update registry"
You'll see a warning
Then, OK (no need to change country)
Another app will open for the flashing. If you are offline, it is possible to show just a "?" character. Wait patiently...
In about 5min it will finish
After some reboots, you'll see the phone starter screen. Just move forward (no need to configure anything right now, maybe wifi, but not google account)
Enable Developer Options going to Settings/General/Common/Software Information and tap some simes in Build Number until the "You are a developer" message appears
Go back to Settings/Developer Options and turn on USB Debugging
With Debugging on, choose MTP (for Windows) or PTP (Linux), and when asked, allow the computer
Now, make sure you installed (and know how to use, since I will cover just a few commands here) the Android Debugging Bridge (adb). It will be essential for some steps, as well for entering Recovery Mode (I will show some Linux screenshots because I do not use Windows - for this tutorial, just for KDZ flash - but with a working adb the commands are the same)
Open a command prompt (Windows: right click in start menu) or a terminal (Linux) and run "adb devices" to see if the device was detected. If not, run again and check if phone are asking permissions (and grant it)
Go (cd) to the folder with all downloaded files and write the commands (some names may be different if you downloaded individual files from official links)
adb push aboot_5120_patched.bin /sdcard/
adb push twrp-3.2.1.0-cn70n.img /sdcard/
adb push SuperSU-v2.82-201705271722.zip /sdcard/
adb install Flashify_1.9.2.apk
adb install KingrootV5.3.1.apk
At whit point, make sure your internet is fully working (3-4G or WIfi), then, open Kingroot and root the device
After a well successful root, go back to adb and run "adb shell" and then "su". The phone will ask root permission. Grant it and in adb again run "cd /sdcard"
Now we arrived a critical step. Make sure to type the command as is show, because an error may result brick. We will copy the modified aboot into the respective phone partition (check code, check picture, and double check!)
If everything occurs all right, will appear this message
Great! Now you have an unlocked bootloader! What we have to do now is fhash a custom recovery (in this case, TWRP).
Open Flashify, give root rights, then go into Flash/Recovery Image/Choose a file/File explorer/sdcard/[downloaded file]. When asked to flash click "YUP!" and then "Flash More" (as we do not want the phone to reboot right now)
An extra step I prefer to do is remove Kingroot, since it installs a lot of services and keep device substantially slow. If you prefer Kingroot over SuperSU, you are DONE!
Case you prefer SuperSU... Open Kingroot/.../Settings/Uninstall Kingroot
It will prompt if you are sure. Just click Continue/OK
Go back to prompt/terminal and run "adb reboot recovery"
Phone will enter TWRP!
Now, just a few steps!
Go to Install and flash SuperSU
Go to Wipe and do a Factory Reset
Go to Settings and disable TWRP app installer (optional)
And finally go to Reboot and choose System
DONE!!!
Now you have a phone with an unlocked bootloader, a recovery capable of doing a lot of stuff (sideload, wipe cache, backups), and rooted as well.

A really good job, I'm sure a lot of your fellow countryman will find this very useful!

Korelev said:
A really good job, I'm sure a lot of your fellow countryman will find this very useful!
Click to expand...
Click to collapse
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!

Valeeeu dms irmao, ajudou dmss

Ninloth said:
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!
Click to expand...
Click to collapse
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?

Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Hi!
Well, unfortunately I don't know. I made the procedure, wrote the tutorial, and 2 months later changed my phone for a new one. Can't test anymore.

Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Yes, it should be compatible with any custom rom as long as your phone is Lg spirit LTE( snapdragon variant ).