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 LITE version. This means that this version will only ROOT your phone. If you have a T-Mobile G3, we'd suggest you look for the full version in this same forum on XDA, since that will root, install TWRP, and prevent your root checker from showing your phone as rooted!
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.
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.
The vulnerability we're exploiting for PurpleDrake has actually been present on quite a few LG phones for some time, and as such this script will automatically detect if your phone is capable of rooting with this method.
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.
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-Lite_VERSION.tar.gz
Mark the application as executable, and run it!
cd PurpleDrake-Lite
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.
After, be sure to check @autoprime's post for how to disable OTA upgrades! here : http://forum.xda-developers.com/showpost.php?p=54254062&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-Lite_R03.tar.gz[/url]
Old version here... (OSX/Linux only)
Code:
[url]http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-Lite_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
Disable OTA:
Open LG Hidden Menu (3845#*851#) --> WLAN Test --> OTA Setting --> OFF
*Replace "851" with your devices model number, 850, 852, 855 etc...
Look, instead of rushing to take an OTA to get the latest software.. think for a moment.
We do no know if the bootloader will stay "unlockable" in future updates. OTA's can update not only software..
but the boot stack as well.. enabling features to block downgrades.. close exploits.. and all sorts of fun stuff.
so.. instead of taking an OTA.. wait for the files to get posted so we can look at things first.. possibly only updating /system, /boot, /modem (maybe tz/rpm)
without updating the rest of the boot stack. ya... do that. Plan on making a lil thread on this soon to make things easier.
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]
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-Mmobile 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 LG Flash. 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 LG Flash (.dll).
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]
Yes ROOTS!!
this will work for sprint?
Sent from my LGLS990 using XDA Free mobile app
---------- Post added at 11:51 AM ---------- Previous post was at 11:47 AM ----------
mrkrabs said:
this will work for sprint?
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
ignore that question I just read alil bit
Sent from my LGLS990 using XDA Free mobile app
any possible release dates for F/G FWs?
can someone explain if there are any differences between towelroot, ioroot and purpledrake? the end result is the same, no?
cnn888 said:
can someone explain if there are any differences between towelroot, ioroot and purpledrake? the end result is the same, no?
Click to expand...
Click to collapse
towel root doesn't work for some phone that have taken firmware updates and ioroot doesn't work on D851 and purpledrake does
Thanks for the awesome work, devs!
Has anyone figured out what the hidden menu code is for the vzw vs985, to be able to turn off ota? Plugging in "985" for the model number doesn't work.
Will there be a method to turn off/reset root counter for those of us who used IOroot?
thecubed said:
I won't quote the whole OP
Click to expand...
Click to collapse
I can confirm that it worked on the D855 euro (10A). so you guys can go ahead and remove the question mark if you want. Also if you give me the right commands I can check if the 855 eur bootloader comes unlocked or not(google doesn't know them )
For me relaunching two times worked with d855 european version v10g leaked. But what about TWRP for D855?
lukemo said:
For me relaunching two times worked with d855 european version v10g leaked. But what about TWRP for D855?
Click to expand...
Click to collapse
I just hope that lg doesn't try to fix this exploit
Hidden menu for Verizon?
autoprime said:
ioroot is better
much thanks to iomonster jcase and dees_troy. glad i could play a part in this rad-ness.
I would be careful taking OTA's.. wouldnt want to lose an unlock(too early to say..)
Disable OTA:
Open LG Hidden Menu --> WLAN Test --> OTA Setting --> OFF
(This worked on LG G2.. hopefully work on G3 but won't be confirmed until OTA comes out)
Hidden menu = 3845#* then model then #.. so 3845#*851# --> 3845#*850# --> 3845#*855# etc etc
EFS Backup:
Code:
[FONT="Arial Narrow"][B]Backup EFS after jailbreaking your G3. EFS is split into 2 partitions modemst1 and modemst2.
iimg files will be on root of internal sdcard. Save the .img files somewhere else besides the sdcard... email, cloud, etc..[/B]
[B]Backup:[/B]
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/sdcard/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/sdcard/modemst2.img
[B]Restore:[/B]
adb shell
su
dd if=/sdcard/modemst1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
dd if=/sdcard/modemst2.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst2[/FONT]
Click to expand...
Click to collapse
Is there a different method for the Verizon models? I tried this but could not access the menu.
this root method works on 10G
http://forum.xda-developers.com/lg-...wrp-root-twrp-tmo-lg-g3-t2821005/post54258277
ofcourse using the corresponding file for d855 from THIS thread.
Thanks !!! Good work!!!!
Works with D855 10g on os x
Enviado desde mi LG-D855 mediante Tapatalk
Works on the F400S. Probably the easiest thing I have ever done in my life.
Is there a way to check root on LG G3 though? I don't see the SU app, though I can use Titanium Backup without a problem.
epikvision said:
Works on the F400S. Probably the easiest thing I have ever done in my life.
Is there a way to check root on LG G3 though? I don't see the SU app, though I can use Titanium Backup without a problem.
Click to expand...
Click to collapse
just download the app root checker from the store.
Sent from my LG-D850 using XDA Premium 4 mobile app
Yeah....I learned how to read! Had the waiting for device issue on Ubuntu, figured it out on the other thread.
Guys,
who tried this method with European D855 (3/32) model with E/F/G fw's but also taking a TWRP from the thread with full package?
[ROOT / TWRP][D851 ONLY] Root/TWRP your TMO LG-G3 with PurpleDrake!
some say it's for D851 only, is it true?
Who tried it on D855? Does it work?
MarvinFS said:
Guys,
who tried this method with European D855 (3/32) model with E/F/G fw's but also taking a TWRP from the thread with full package?
[ROOT / TWRP][D851 ONLY] Root/TWRP your TMO LG-G3 with PurpleDrake!
some say it's for D851 only, is it true?
Who tried it on D855? Does it work?
Click to expand...
Click to collapse
The d855 have a locked bootloader, that's why it will not work!! No recovery for us, at the moment!! We have to wait.
Gesendet von meinem LG-D855 mit Tapatalk
john0699 said:
The d855 have a locked bootloader, that's why it will not work!! No recovery for us, at the moment!! We have to wait.
Click to expand...
Click to collapse
I thought recovery goes to recovery partition, and locked bootloader have nothing to do with it, isn't it?
Related
I've made some changes to my previous modification of Lelus rooting method to work on V20 firmware.
All actions is like for old method for V10, except what must patch other .bin file from firmware. For V20B P765 CIS this is LGP765_AP[11].bin.
How to patch:
{
"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"
}
I've added busybox app from market into rooting procedure because this is important to reinstall busybox applets after rooting.
Good news. That means we can root without unlocking bootloader. Right? Can we have something similar on cmw?
Sent from my LG-P765 using xda premium
amnik said:
Good news. That means we can root without unlocking bootloader. Right? Can we have something similar on cmw?
Click to expand...
Click to collapse
You're right. CMW only by 2ndinit. I've tried 2ndinit CWM for v10 with no success - it starts (keys flashes at boot) but hung on LG logo. Suspect this happens because v20 have new kernel.
AngryWolf80 said:
I've made some changes to my previous modification of Lelus rooting method to work on V20 firmware.
All actions is like for old method for V10, except what must patch other .bin file from firmware. For V20B P765 CIS this is LGP765_AP[11].bin.
How to patch:
I've added busybox app from market into rooting procedure because this is important to reinstall busybox applets after rooting.
Click to expand...
Click to collapse
Good one angrywolf90 :good: Good for those who dont want to unlock bootloader.
please make proper full-length guide? I know all the steps. But the image is not very clear? attach GIF image inside zip file. XDA reduces image size and also reduces quality of images.
AREMCEE's "Rooting JB" method is more easy and faster, for People with already Unlocked Bootloader or who want to unlock bootloader. They dont need to edit bin and flash. just push CWM in fastboot mode and use flashable root file.
cmahendra said:
please make proper full-length guide? I know all the steps. But the image is not very clear? attach GIF image inside zip file. XDA reduces image size and also reduces quality of images.
Click to expand...
Click to collapse
I don't have much free time for this right now. Steps exactly same as guide for v10, except file to patch and text to change.
Image I've attached in zip.
cmahendra said:
AREMCEE's "Rooting JB" method is more easy and faster, for People with already Unlocked Bootloader or who want to unlock bootloader. They dont need to edit bin and flash. just push CWM in fastboot mode and use flashable root file.
Click to expand...
Click to collapse
Surely CWM method more simpler, but not for people, who want to keep their warranty for phone. And on 4PDA.RU some peoples complain what they unable to get in fastboot mode to unlock bootloader...
AngryWolf80 said:
Surely CWM method more simpler, but not for people, who want to keep their warranty for phone. And on 4PDA.RU some peoples complain what they unable to get in fastboot mode to unlock bootloader...
Click to expand...
Click to collapse
Sorry for off-topic, but I am responding to your information.
Mostly its drivers issue. Phone is not to blame. LG USB drivers include drivers for both ADB and FASTBOOT mode.
I think for unlocking you dont need fastboot mode. Actually "adb reboot oem-unlock" this command is given in ADB mode and it starts fastboot mode, which then asks user to just press VOL+ key for unlocking. Now I dont understand why they are not able to put phone in ADB mode and not able to shoot this ADB command?
Thanks for the IMAGE, its much clear and I have made small FILE WITH FEW PERFECT EDITED LINES to paste in said BIN file with the help of any HEX EDITOR. Should be pasted in overwrite mode of cursor.
cmahendra said:
Sorry for off-topic, but I am responding to your information.
Mostly its drivers issue. Phone is not to blame. LG USB drivers include drivers for both ADB and FASTBOOT mode.
I think for unlocking you dont need fastboot mode. Actually "adb reboot oem-unlock" this command is given in ADB mode and it starts fastboot mode, which then asks user to just press VOL+ key for unlocking. Now I dont understand why they are not able to put phone in ADB mode and not able to shoot this ADB command?
Click to expand...
Click to collapse
It's not a drivers case. Phone is just reboot in responce to "adb reboot oem-unlock" command. No matter to which drivers installed on your system (And what if I've see such thing on my Linux machine? Which drivers you suggest to install? Phone just reboots and thats all. Sad but true.)
cmahendra said:
Thanks for the IMAGE, its much clear and I have made small FILE WITH FEW PERFECT EDITED LINES to paste in said BIN file with the help of any HEX EDITOR. Should be pasted in overwrite mode of cursor.
Click to expand...
Click to collapse
With my HEX editor it can't be done like this (yes, I'm old fart who don't want to use some new cool modern tools ), your file much better if user know how to deal with it.
AngryWolf80 said:
It's not a drivers case. Phone is just reboot in responce to "adb reboot oem-unlock" command. No matter to which drivers installed on your system (And what if I've see such thing on my Linux machine? Which drivers you suggest to install? Phone just reboots and thats all. Sad but true.)
Click to expand...
Click to collapse
I dont know what to say but it worked for everyone here, except very few people who may be not more familiar with basic terms and are less experienced.
With my HEX editor it can't be done like this (yes, I'm old fart who don't want to use some new cool modern tools ), your file much better if user know how to deal with it.
Click to expand...
Click to collapse
Few weeks back (4 mar) I made this simple and small guide to EDIT BIN file, but almost everyone overlooked.
http://forum.xda-developers.com/showpost.php?p=38750385&postcount=47
If read with patience it clearly explains how to edit (paste) bin file.
Please have a look. The link was also given in OP of same thread, but unfortunately it was forgotten by all. I think I should have made it in new thread so some of the pals might have noticed it.
Just for the support of this thread I would like to say that, this attached patch bin file and this small guide will be helpful to make your own HEX EDITED BIN FILE for rooting Jelly Bean on L9.
waiting for tutorial for newbie
vinswong said:
waiting for tutorial for newbie
Click to expand...
Click to collapse
from whom?
@AngryWolf80
Are you making one?
cmahendra said:
from whom?
@AngryWolf80
Are you making one?
Click to expand...
Click to collapse
I don't have time for such things right now
And manual already exists for V10, changed only .bin file.
AngryWolf80 said:
I don't have time for such things right now
And manual already exists for V10, changed only .bin file.
Click to expand...
Click to collapse
but noobs want it spoon-feeded everytime.
@AngryWolf80, @Cmahendra Guys can anyone of you upload edited bin file for V20B P765 CIS ? #Beingnoob #beinglazy
er.davinder said:
@AngryWolf80, @Cmahendra Guys can anyone of you upload edited bin file for V20B P765 CIS ? #Beingnoob #beinglazy
Click to expand...
Click to collapse
sure, I have this KDZ and will make a bin for you. but now in office. please wait until i reach home
AngryWolf80 said:
I don't have time for such things right now
And manual already exists for V10, changed only .bin file.
Click to expand...
Click to collapse
OK! I modified the existing ROOTING guide by including your latest Rooting Files. Hope you will find it ok. Of course credit is given to you with Thanks.
er.davinder said:
@AngryWolf80, @Cmahendra Guys can anyone of you upload edited bin file for V20B P765 CIS ? #Beingnoob #beinglazy
Click to expand...
Click to collapse
EDIT: P765 V20B CIS BIN file edited and uploaded in 2nd post of ROOTING GUIDE.
Hope it works for you.
cmahendra said:
OK! I modified the existing ROOTING guide by including your latest Rooting Files. Hope you will find it ok. Of course credit is given to you with Thanks.
EDIT: P765 V20B CIS BIN file edited and uploaded in 2nd post of ROOTING GUIDE.
Hope it works for you.
Click to expand...
Click to collapse
does it work with p760?
Rewowski said:
does it work with p760?
Click to expand...
Click to collapse
No!!! Dont try!! This edited bin is created from kdz of P765. It will work with same KDZ only from which BIN file is extracted. Read post carefully.
cmahendra said:
No!!! Dont try!! This edited bin is created from kdz of P765. It will work with same KDZ only from which BIN file is extracted. Read post carefully.
Click to expand...
Click to collapse
ok thx.
So that means there is no way to root with offline method v20 p760?
I can't find any hex edited bin files for it.....
Rewowski said:
ok thx.
So that means there is no way to root with offline method v20 p760?
I can't find any hex edited bin files for it.....
Click to expand...
Click to collapse
Sorry, I've recently deleted v20 firmware from P760 and redownload it again will take many time (LG uses traffic shaper?)
Ask somebody to patch v20 for P760 for you...
Rewowski said:
ok thx.
So that means there is no way to root with offline method v20 p760?
I can't find any hex edited bin files for it.....
Click to expand...
Click to collapse
Not really
I have uploaded ready-made bin file for P760 V20B Europe firmware too. Links for BIN and KDZ can be found in 2nd post of this JB/ICS Rooting Guide
hope this helps.
{
"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"
}
Hello All, this will update your V500 to 4.4.2, as is mine. This is based off the leaked 4.4.2 tot file.
Thanks AICJOFS for sending me the link to the leaked 4.4.2 official update tot.
Install the Drivers
Be sure usb debugging is ON!
Download the 4.4.2 .TOT file from here:
https://drive.google.com/file/d/0B34qnFE3O_HbX2t6elg5UXZFNEk/edit?usp=sharing
or here
http://www.androidfilehost.com/?fid=23329332407581518
(Thanks DrGravy for the mirrors!)
or here:
http://goo.gl/BIiHT0 and yes one more for good measure
http://goo.gl/QHrcKm
- I strongly suggest using a download manager like IDM to download this file
in case you have an error with your internet etc, It's 2GB+ in size
that way if you do, it'll continue to download this once you regain your internet connection. Trust me, it's worth it.
Download the .dll file you'll need last here:
https://drive.google.com/file/d/0B34qnFE3O_HbVnJ3WEEtUU12NFE/edit?usp=sharing
DO NOT EXTRACT the .tot file, leave it alone!
Download and install LGFlashTool from here: https://drive.google.com/file/d/0B34qnFE3O_HbcHM5LWFKcU84WjA/edit?usp=sharing
or here: http://goo.gl/qO1tqB
Download the MegalockDLL file for LGFlashTool here: https://drive.google.com/file/d/0B34qnFE3O_HbdkpkcmV6Z3ZpYmc/edit?usp=sharing
or here http://goo.gl/oUa37Q
After the LG Flash Tool is installed, do NOT launch it.
-Extract MegaLock.dll from the zip and copy MegaLock.dll to C:\LG\LGFlashTool, replacing the old MegaLock.dll file
Power off your Gpad, plug in the usb into your Gpad (not your computer yet)...
Holding vol Up & Down, plug it into your computer and you should now be in DOWNLOAD mode,
Wait for the drivers to finish installing, after they are, open Device Manager
Scroll down and click Ports, now Right click LGE AndroidNet USB Serial Port (COM2), then properties, then Advanced,
Now change the port # to 41, save and close out device manager
Now unplug your G Pad again from your computer.
Open LG Flash Tool
Select Manual Mode
Click on Add button on S/W field and load the V500 4.4.2 .TOT file
Then click the .DLL field and add the DLL file here. NOT the megalock.dll the First one you downloaded with the tot file.
NOW CLICK THAT YELLOW ARROW up top.
Wait for it to say READY. Once it says Ready plug in your G Pad again, in download mode.
Now As soon as you plug in your G Pad, In Download mode, it'll begin to flash, WAIT for it to say Pass in Blue, and it's done!
You now have a LG G Pad V500 with 4.4.2 Stock Kit Kat
Everything is working as it should be. Including ART!Quick Smooth and Zippy with no lag for me.
Your Welcome.
JESSICA
**** Yes you can have root with this, I used kingo because it was quick and easy ****
--P.S. Since people have been asking me via PM:
**---*** TO GO BACK TO 4.2.2 STOCK EVERYTHING yes including the bootloader, use my new thread HERE:
http://forum.xda-developers.com/showthread.php?p=51466048
Jessooca said:
Your Welcome.
JESSICA
Click to expand...
Click to collapse
Thanks a lot, I'll try it ASAP.
Awesome!!!!!!
Any chance for someone to make a flashable zip in recovery ?
Also Ashby changes to q remote?
Sent from my LG-V500 using Tapatalk
Wow....lemme try too. Fingers crossed.
Edit: can u post a screenshot?
Sent from my LG-V500 using XDA Premium 4 mobile app
Thanks a lot for the detailed tutorial!
But I think I'll stay with AOSP for now
I hope this can somehow help the GPE ROM, can it?
Sent from my iPhone using Tapatalk
yep, when sources will be released
Inviato dal mio Nexus 5 utilizzando Tapatalk
TOT link dead. :crying:
Edit: web page not available when i click download.
Great job!
Jessooca said:
Links have been updated, in the original post, everything is now available on my Google Drive to download.
https://drive.google.com/file/d/0B34qnFE3O_HbQVlMZnc5YlBRT3M/edit?usp=sharing
https://drive.google.com/file/d/0B34qnFE3O_HbVnJ3WEEtUU12NFE/edit?usp=sharing
https://drive.google.com/file/d/0B34qnFE3O_HbX2t6elg5UXZFNEk/edit?usp=sharing
https://drive.google.com/file/d/0B34qnFE3O_HbcHM5LWFKcU84WjA/edit?usp=sharing
https://drive.google.com/file/d/0B34qnFE3O_HbdkpkcmV6Z3ZpYmc/edit?usp=sharing
Click to expand...
Click to collapse
Can this be rooted? And is there a working recovery we can install? Thanks a lot.
Sent from my LG-V500 using XDA Premium 4 mobile app
jchenny said:
Can this be rooted? And is there a working recovery we can install? Thanks a lot.
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Standard root works but it looks like it doesnt persist after cold reboot. Also (while no one has tried it) this is patched for the loki exploit so custom recovery is not possible (just like the G2).
nightanole said:
Standard root works but it looks like it doesnt persist after cold reboot. Also (while no one has tried it) this is patched for the loki exploit so custom recovery is not possible (just like the G2).
Click to expand...
Click to collapse
How did you get root?
As someone else mentioned, I believe this update breaks the Loki Bootloader exploit, meaning no more TWRP or custom kernels.
I'll look into this.. Maybe it's possible to install without updating Bootloaders through a custom recovery zip.
Great, thanks a lot! Could you please upload a system dump? I'm trying to extract the tot file in linux and I can't manage to do it.
Wonderful
Jessooca said:
For some reason, not sure why, but the pre existing Root method, didn't work, yet I used kingo and it's rooted, even after multiple reboots with no issues of any sort.
Click to expand...
Click to collapse
Outstanding job! What a breakthrough.
But I can't get root - even with Kingo. The app goes into a loop of downloading and waiting. This is with USB debugging enabled and the Pad connected as an MTP device. I also tried it connected with LG Software but got the same loop.
Never mind, the upgrade is wonderful.
id10terror said:
As someone else mentioned, I believe this update breaks the Loki Bootloader exploit, meaning no more TWRP or custom kernels.
I'll look into this.. Maybe it's possible to install without updating Bootloaders through a custom recovery zip.
Click to expand...
Click to collapse
please research the G2, Same thing happened with the G2, but once the source kernel was released they found a way to flash KitKat and keep their current custom recovery. I am sure it will be the same. One thing the G2 had going for it is you could go back to 4.2.2 at any time which works with Loki(as far as i know this is unconfrimed with the g pad). I am sure this will be the same.
But if you simply remove the recovery from the update it wont boot.
zahir32 said:
Outstanding job! What a breakthrough.
But I can't get root - even with Kingo. The app goes into a loop of downloading and waiting. This is with USB debugging enabled and the Pad connected as an MTP device. I also tried it connected with LG Software but got the same loop.
Never mind, the upgrade is wonderful.
Click to expand...
Click to collapse
Reboot an try again. I had the same problem. Now i have tried it again. Now it works. ROOTED.
But I dont get TWRP installed.
Miracast?
It has miracast?
Thanks
Perfect!
smoki3 said:
Reboot an try again. I had the same problem. Now i have tried it again. Now it works. ROOTED.
But I dont get TWRP installed.
Click to expand...
Click to collapse
Thank you! Worked fine after the reboot. Great help.
jsevi83 said:
Great, thanks a lot! Could you please upload a system dump? I'm trying to extract the tot file in linux and I can't manage to do it.
Click to expand...
Click to collapse
Don't have a windows computer around? This extracted it fine.
http://forum.xda-developers.com/showthread.php?t=2600575
Have any One found a possiblity to downgrade to 4.2
Gesendet von meinem HTC One mit Tapatalk
Enjoy. Don't forget to thank @beaups too, he discovered the eMMC backdoor and exploited it!
UPDATE: [8/2/16] I have recompiled the binary with some fixes beaups made. These fixes should take care of the "samsung device only" error some are getting on 4.4 roms.
Disclosure: I do not own a Note 3. The exploit happened to be applicable to the Note 3, and we compiled it for your devices rather than not release it at all. This seems like a reasonable and friendly thing to do for the community. I can't help you root or teach you how to use ADB. It's important you have the ability to do these things or research them a bit before blindly using this. I am very familiar with Samsung however, and time permitting, will do my best to help anyone having issues.
You should not run this if you don't understand it.
ROOT REQUIRED, we aren't responsible for anything you do with this.
You NEED a MicroSD, and it WILL be formatted during this process.
YOU MUST DISABLE REACTIVATION LOCK OR YOU WILL HAVE ISSUES!!!!!!!!!
You can download the eMMC brick bug check app on the Play Store to verify your CID starts with 15. If it does, you are good. If not, it will not work.
The code below is NOT a script, you must enter the commands manually.
You must unzip the file first.
Download
Code:
adb push unlock_n3 /data/local/tmp/
adb shell
su
cd /data/local/tmp/
chmod 777 unlock_n3
chown root.root unlock_n3
./unlock_n3
Allow device to reboot. After full reboot, run
Code:
adb shell
su
cd /data/local/tmp/
./unlock_n3
again, power down and pull battery. May need to run it again if it doesn't work after the battery pull.
Paypal: [email protected] [COMPLETELY VOLUNTARY AND OPTIONAL]
Your the best. Trying it right now
Sent from my SM-N900V using Tapatalk
---------- Post added at 02:10 PM ---------- Previous post was at 01:58 PM ----------
ryanbg said:
Enjoy. Don't forget to thank @beaups too, he discovered the eMMC backdoor and exploited it!
Disclosure: I do not own a Note 3. The exploit happened to be applicable to the Note 3, and we compiled it for your devices rather than not release it at all. This seems like a reasonable and friendly thing to do for the community. I can't help you root or teach you how to use ADB. It's important you have the ability to do these things or research them a bit before blindly using this. I am very familiar with Samsung however, and time permitting, will do my best to help anyone having issues.
You should not run this if you don't understand it.
ROOT REQUIRED, we aren't responsible for anything you do with this.
You NEED a MicroSD, and it WILL be formatted during this process.
YOU MUST DISABLE REACTIVATION LOCK OR YOU WILL HAVE ISSUES!!!!!!!!!
You can download the eMMC brick bug check app on the Play Store to verify your CID starts with 15. If it does, you are good. If not, it will not work.
The code below is NOT a script, you must enter the commands manually.
Code:
adb push samsung_unlock_n3 /data/local/tmp/
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n3
chown root.root samsung_unlock_n3
./samsung_unlock_n3
Allow device to reboot. After full reboot, run
Code:
adb shell
su
cd /data/local/tmp/
./samsung_unlock_n3
again, power down and pull battery. May need to run it again if it doesn't work after the battery pull.
Paypal: [email protected] [COMPLETELY VOLUNTARY AND OPTIONAL]
Click to expand...
Click to collapse
Perfect thanks so much ..this is tremendous [emoji120] [emoji120] donations are required. Donate to whom just breathed life into a great phone..Flashify idea by @alexp1289 was great idea to install recovery..this is f### ING awesome
Sent from my SM-N900V using Tapatalk
Awesome! Trying this now!
Cheers,
B.D.
God you are a life saver, I've been trying to get my uncle hooked up with a phone with a unlocked bootloader for awhile,
now he can use his current phone for it.
Does this work for v4.4.4 and 5.0?
Any idea how long it takes on the first reboot? I assume it formats the SD card and that takes some time and I only have a 64gb card so I'm guessing I'll be looking at the Verizon logo a while.
Do the commands HAVE to be entered via adb? If I downloaded the zip to my phone, could I enter the commands through a terminal editor possibly?
jellyhead said:
Does this work for v4.4.4 and 5.0?
Click to expand...
Click to collapse
Yes.
BackCheck said:
Any idea how long it takes on the first reboot? I assume it formats the SD card and that takes some time and I only have a 64gb card so I'm guessing I'll be looking at the Verizon logo a while.
Click to expand...
Click to collapse
Try removing your SDCARD, boot up, and put it back in before you do it the second time.
Gl17ch said:
Do the command HAVE to be entered via adb? If I downloaded the zip to my phone, could I enter the commands through a terminal editor possibly?
Click to expand...
Click to collapse
You should do it with adb instead of terminal emulator. You could do it with terminal emulator, but I don't recommend it.
I'm confused. It asked me to run the binary again to finish the process, but when i did that, it tried to change the CID again. Am i doing something wrong? The CID has changed to the one it displays on cmd.
tomixnscale89 said:
I'm confused. It asked me to run the binary again to finish the process, but when i did that, it tried to change the CID again. Am i doing something wrong? The CID has changed to the one it displays on cmd.
Click to expand...
Click to collapse
Do a battery pull and run the second step again. It will say "backing up loaders" when it is actually done.
ryanbg said:
Yes.
Try removing your SDCARD, boot up, and put it back in before you do it the second time.
You should do it with adb instead of terminal emulator. You could do it with terminal emulator, but I don't recommend it.
Click to expand...
Click to collapse
It works, I have TWRP installed. I'll be divvying out donations come payday.
BackCheck said:
It works, I have TWRP installed. I'll be divvying out donations come payday.
Click to expand...
Click to collapse
Where did you get your TWRP build from?
The Note 3 Verizon hasn't had a unlocked bootloader until now, so I can't imagine there was a TWRP build ready for it.
Was there something close enough to be compatible, like a TWRP build for the developer edition?
ryanbg said:
Yes.
Try removing your SDCARD, boot up, and put it back in before you do it the second time.
You should do it with adb instead of terminal emulator. You could do it with terminal emulator, but I don't recommend it.
Click to expand...
Click to collapse
dreyeth said:
Where did you get your TWRP build from?
The Note 3 Verizon hasn't had a unlocked bootloader until now, so I can't imagine there was a TWRP build ready for it.
Was there something close enough to be compatible, like a TWRP build for the developer edition?
Click to expand...
Click to collapse
Flashify. It didn't look like they had much trouble getting it ported quickly for us. Now to get CM13 going but that'll be a little longer.
BackCheck said:
Flashify. It didn't look like they had much trouble getting it ported quickly for us. Now to get CM13 going but that'll be a little longer.
Click to expand...
Click to collapse
Sweet so that app auto flashes the recovery of your choice? and they have a TWRP port already for this?
I've always done it the manual way.
Thanks for the information.
dreyeth said:
Sweet so that app auto flashes the recovery of your choice? and they have a TWRP port already for this?
I've always done it the manual way.
Thanks for the information.
Click to expand...
Click to collapse
Yep just download the app and select the one in the pictures.
Download link for Flashify--
https://play.google.com/store/apps/details?id=com.cgollner.flashify
{
"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"
}
Sent from my SM-N900V using Tapatalk
dreyeth said:
Sweet so that app auto flashes the recovery of your choice? and they have a TWRP port already for this?
I've always done it the manual way.
Thanks for the information.
Click to expand...
Click to collapse
I got sick of using dd to reinstall recoveries on my LG V500. There are one or two other apps I've seen that do this but this one always worked for me.
dreyeth said:
Sweet so that app auto flashes the recovery of your choice? and they have a TWRP port already for this?
I've always done it the manual way.
Thanks for the information.
Click to expand...
Click to collapse
https://twrp.me/devices/samsunggalaxynote3qualcomm.html
You still can download it manually. Read the notes and it shows the verizon note 3 supported.
Just confirmed good old "dd" method works fine and recovery boots nicely. Make sure you pick the correct version at the twrp website.
Now on to bigger and better things! Will donate!
I tried this, and no change to my CID... It's still starts with 15...... I'm expecting it to start with 11 when it works.... Any ideas? I'm using an 8GB sd card, and the card was erased as expected....
My output was:
<begin output>
Do you understand the implications of these warnings?
(Yes/No)
Y
Type "Yes" or "No"
(Yes/No)
yes
[+] CID at boot time is/was: 15------------------------------
[+] dev CID matching, proceding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
<end output>
I obfuscated the actual CID in the above output message. Is there any way to verify that this worked before I flash TWRP and possibly brick my device?
EDIT: Nevermind, I booted into download mode and found out that my device is seen as a "developer device". Anybody flash TWRP and CM13 yet?
Cheers,
B.D.
dreyeth said:
Where did you get your TWRP build from?
The Note 3 Verizon hasn't had a unlocked bootloader until now, so I can't imagine there was a TWRP build ready for it.
Was there something close enough to be compatible, like a TWRP build for the developer edition?
Click to expand...
Click to collapse
I'm supposing that if I am running 5.0 the 4.4 TWRP will not work...
Once I get this to work will I be able to downgrade to 4.4/install a custom recovery/etc. ?
BostonDan said:
I tried this, and no change to my CID... It's still starts with 15...... I'm expecting it to start with 11 when it works.... Any ideas? I'm using an 8GB sd card, and the card was erased as expected....
My output was:
<begin output>
Do you understand the implications of these warnings?
(Yes/No)
Y
Type "Yes" or "No"
(Yes/No)
yes
[+] CID at boot time is/was: 15------------------------------
[+] dev CID matching, proceding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
<end output>
I obfuscated the actual CID in the above output message. Is there any way to verify that this worked before I flash TWRP and possibly brick my device?
EDIT: Nevermind, I booted into download mode and found out that my device is seen as a "developer device". Anybody flash TWRP and CM13 yet?
Cheers,
B.D.
Click to expand...
Click to collapse
Sent from my SM-N900V using XDA-Developers mobile app
BostonDan said:
I tried this, and no change to my CID... It's still starts with 15...... I'm expecting it to start with 11 when it works.... Any ideas? I'm using an 8GB sd card, and the card was erased as expected....
My output was:
<begin output>
Do you understand the implications of these warnings?
(Yes/No)
Y
Type "Yes" or "No"
(Yes/No)
yes
[+] CID at boot time is/was: 15------------------------------
[+] dev CID matching, proceding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
<end output>
I obfuscated the actual CID in the above output message. Is there any way to verify that this worked before I flash TWRP and possibly brick my device?
EDIT: Nevermind, I booted into download mode and found out that my device is seen as a "developer device". Anybody flash TWRP and CM13 yet?
Cheers,
B.D.
Click to expand...
Click to collapse
App flashify installs Twrp easy. All there no searching works beatiful
Sent from my SM-N900V using Tapatalk
Hello everyone. This is my first tutorial with Gear S so I hope it will help someone.
First of all
I am not responsible for any damage done to you deviceI saw in this Tutorial thread: http://forum.xda-developers.com/gear-s/development/definitive-guide-to-rooting-gear-s-t2973455, that some people have unsupported firmware versions and they can't root they'r device. It is not true. You can root your device, if you will follow this simple guide.
What do you need:
1) Gear S
2) Charging cradle with USB cable
3) PC running Windows (because windows is only OS I know XD)
4) Odin 3.09: https://drive.google.com/open?id=0B4xXHWEm81OleU0wckt0S2pjSU0
5) supported firmware downloaded from here: http://www.sammobile.com/firmwares/database/SM-R750/ (it is just on you which one do you pick, but it must be supported in the root thread)
6) Drivers: https://drive.google.com/open?id=0B4xXHWEm81OlT1ZBeXdHYXZqQTA
If you have everything downloaded you can proceed to the tutorial it selfStep by step firmware changing guide:
1) Unzip downloaded software and install drivers
- you should end with one .MD5 file and one .dll file (I am not sure, if the .dll is needed)
2) Open Odin 3.09
{
"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"
}
- Here you have to Tick AP, click on AP and select your .MD5 file
-you should start to see something like this (wait until it says leave CS..)
- you can continue if you see this
3)Untick Auto reboot
4) Enable USB-Debugging on Gear S
- Settings -> Gear Info -> USB Debugging
5) Put your gear S into download mode
https://www.youtube.com/watch?feature=player_embedded&v=qwcf79m9ycw
- credits go to cipherswitch
6) Connect your gear S to PC
- you should see this
7) Click start and wait till it is done
- when it is done you will see this
8)Wait till Gear S reboot
- Now just look at the firmware page and there should be new software version
If you have an error
-repeat everything but with different firmware version
P.S.: Sorry if you can't see pictures, so if you have problem just look into attachment they are listed here
My tmobile gear is on a newer firmware. So do i just roll back to an earlier firmware then root?
Thanks
***firmware version R750TUVU1APC1
Sent from my SM-N930T using XDA-Developers mobile app
louforgiveno said:
My tmobile gear is on a newer firmware. So do i just roll back to an earlier firmware then root?
Thanks
***firmware version R750TUVU1APC1
Sent from my SM-N930T using XDA-Developers mobile app
Click to expand...
Click to collapse
I downloaded the exact same one from sammobile then I flashed the AOA7 root file from the root thread and it works fine. The software version will still be AOA7 but I think the baseband will be APC1 but mine is working flawlessly. Also you could still flash stock AOA7 first then root but theres no need as I've tested it.
i can't root my gearS R750XXU2BOK1_KTC ( korean) . Who will help me to root my gear ? i did look like that but it can't. please help me
vitdiesel said:
i can't root my gearS R750XXU2BOK1_KTC ( korean) . Who will help me to root my gear ? i did look like that but it can't. please help me
Click to expand...
Click to collapse
did u tried different supported rom?
Kubas_inko_CZ said:
did u tried different supported rom?
Click to expand...
Click to collapse
because my gear was from KTC carrier, so i am afriad to tried other room to lock sim.? if u know how i can root that, plz help me.
as long as i know, changing stock rom does not affect carrier, but if u are scared, dont try it (i would try it for sure), because u can go totally back by flashing your stock rom.
Do anyone have the root files still ?
Sent from my SM-N950U using Tapatalk
mr pnut said:
Do anyone have the root files still ?
Click to expand...
Click to collapse
I have the same question...
sonay705 said:
I have the same question...
Click to expand...
Click to collapse
As i do to, really in need of those files, i some o e find them give me a shout... thankx
Sent from my SM-N9300 using Tapatalk
sonay705 said:
I have the same question...
Click to expand...
Click to collapse
Alright guys i have the file rootfs.tar...
Give me a bit, i'll get it uploaded
Here's the root file....enjoy!
Hit the Thanks Buddy Button !
Lol
https://mega.nz/#!MYE1kSSS!PHy1-fa0Qdoy4lLVWDORcJ5CXqq8B_aBXXUiJx2C78w
louforgiveno said:
Here's the root file....enjoy!
Hit the Thanks Buddy Button !
Lol
https://mega.nz/#!MYE1kSSS!PHy1-fa0Qdoy4lLVWDORcJ5CXqq8B_aBXXUiJx2C78w
Click to expand...
Click to collapse
Thanks mate this will make the difference, flash with odin and push files trough adb right? Or is there a file explorer included. Thanks again most appreciated...
Sent from my SM-N9300 using Tapatalk
PTHugo said:
Thanks mate this will make the difference, flash with odin and push files trough adb right? Or is there a file explorer included. Thanks again most appreciated...
Click to expand...
Click to collapse
Sorry, sounds right...can't remember the steps off hand.
Inside the .tar is an image file, might need to be unpacked, sorry just don't remember the steps.
Just follow the guide and use this file.
Best of luck.
louforgiveno said:
Sorry, sounds right...can't remember the steps off hand.
Inside the .tar is an image file, might need to be unpacked, sorry just don't remember the steps.
Just follow the guide and use this file.
Best of luck.
Click to expand...
Click to collapse
Thanks again , i'll figure it out eventually, we always got stock to clean the mess when we **** the bed, [emoji4] can't thank you enough it's been long since someone played with this device but i just keep coming back to it, i really like it a lot... All the best, thanks once more [emoji4]
Sent from my SM-N9300 using Tapatalk
louforgiveno said:
Here's the root file....enjoy!
Hit the Thanks Buddy Button !
Lol
<url> ...
Click to expand...
Click to collapse
Which FW rooted?
sonay705 said:
Which FW rooted?
Click to expand...
Click to collapse
Good question.....all i know it was in a folder named latest created late in 2016.....not sure if that helps at all...
Maybe the info is somewhere in the "image" file...sorry been a long time since i used the files.....
louforgiveno said:
Good question.....all i know it was in a folder named latest created late in 2016.....not sure if that helps at all...
Maybe the info is somewhere in the "image" file...sorry been a long time since i used the files.....
Click to expand...
Click to collapse
Okay it is a custom binary but still write protected shows anther firmware version, now i miss something and coz the beginning of the thread was deleted i'm not quite sure what is i mean is rooted (at least i think it is coz the binary now shows custom), now the deal is there must be or should be some kind of file manager or su manager on the watch i already tryed to push using adb and fastboot but it doesn't work so how did you push tose? Was it by flashin some other thing with odin, please try to remember i realy am trying to get this thing available to other samsung's high end phones, i'm trying to get it working with any phone brand so i really need to get in the hart of the thing to make a few changes, i already (think) i got a way to do it, sorry to trouble you mate you already did someting awsome thanks
Sent from my SM-N9300 using Tapatalk
PTHugo said:
Okay it is a custom binary but still write protected shows anther firmware version, now i miss something and coz the beginning of the thread was deleted i'm not quite sure what is i mean is rooted (at least i think it is coz the binary now shows custom), now the deal is there must be or should be some kind of file manager or su manager on the watch i already tryed to push using adb and fastboot but it doesn't work so how did you push tose? Was it by flashin some other thing with odin, please try to remember i realy am trying to get this thing available to other samsung's high end phones, i'm trying to get it working with any phone brand so i really need to get in the hart of the thing to make a few changes, i already (think) i got a way to do it, sorry to trouble you mate you already did someting awsome thanks
Sent from my SM-N9300 using Tapatalk
Click to expand...
Click to collapse
I'll rack my brain to try to remember....but from what i do remember it wasn't like root for a phone.....no su app (tizen os) ...just able to execute admin commands via adb.
If you were to load android os well then su will probably be available.
I'll look back through my files, looking for any guides when i get a chance.
Sent from my SM-G950U using Tapatalk
louforgiveno said:
I'll rack my brain to try to remember....but from what i do remember it wasn't like root for a phone.....no su app (tizen os) ...just able to execute admin commands via adb.
If you were to load android os well then su will probably be available.
I'll look back through my files, looking for any guides when i get a chance.
Sent from my SM-G950U using Tapatalk
Click to expand...
Click to collapse
Thanks mate, i've still got trouble to get adb to list i eventry on download mode (we now that's only for odin) i read somewhere that some samsung devices do work that way (well i don't think they do coz download mode puts the device listening only) anyway coz we are always learning something i gave that a shot has we already knew nop it doesn't go, so thanks once more for your help it's very important and welcome, i'm very grateful for your effort...
Sent from my SM-N9300 using Tapatalk
Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
{
"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"
}
dvegaman said:
Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
Click to expand...
Click to collapse
I have a pair of the FPV Drone Edition. Have side loaded a few apps. Haven't rooted since Galaxy S3 ( back on iPhone now) am interested to get this going
Hi !
It seems the rooting of intel devices follow the scheme:
-get bootimg
-patch it
-allow oem bootloader (voiding warranty and endangering future updates)
-flash the patched bootimg and pray
Is this correct or did i oversimplify or generalize too much or am i plain wrong, anyone ?
Greetings,
Ender
P.S. Greetings dvegaman
Bump.
Well, BUMP, goddamn
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
jdiegmueller said:
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
Click to expand...
Click to collapse
Bumping this one up. Have a new pair and looking to root to wake them up some.
Sent from my Moto Z (2) using Tapatalk
This may seem easy to others but I figured out how to do a factory data reset using ADB... something that would've helped when my BT-300 went into a boot loop last weekend...
***DO AT YOUR OWN RISK! NOT RESPONSIBLE FOR BRICKING, ETC..... (but it worked fine for me).
1. Install "minimal_adb_fastboot_v1.4.2_setup.exe" (google it and grab at your own risk) on your Windows PC.
2. Go to the BT-300 and:
a. Under Security allow unknown sources
b. Under Developer Options allow USB debugging and unlock bootloader.
3. Connect same powered up BT-300 to PC via USB cable.
4. Start up that minimal ADB program. It will open in command prompt.
5. Check connection by typing "adb devices"
Should see "EMBT3C device" on PC
6. Now type, "adb reboot recovery" and wait for android with triangle/exclamation point to appear after device reboots. You will notice the physical buttons flash purple too.
7. Press and hold power button. Also press Vol Up, then release Vol Up and finally release Power button.
You should now see the recovery menu including "wipe data/factory reset", cache clear, and so on...
NOW... if I could get recovery.zip image to restore if I "kill" it to reload with ADB... THEN I'd try root. There must be a way. I just want GApps 5.1.1 on the thing for starters.
Still struggling with rooting... No dice so far. I've never rooted any Android... Once rooted can we then save the original factory ROM someplace safe, or do I need that first from another source? Newbie questions . I know just enough to be dangerous! LOL.
I got the factory image
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Erodros said:
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Click to expand...
Click to collapse
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Erodros said:
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Click to expand...
Click to collapse
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
chuck1026 said:
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Erodros said:
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Click to expand...
Click to collapse
You trashed it? What did ya load after root to crash it?
chuck1026 said:
You trashed it? What did ya load after root to crash it?
Click to expand...
Click to collapse
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Erodros said:
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Click to expand...
Click to collapse
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
chuck1026 said:
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
Click to expand...
Click to collapse
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
PS - Ok, I figured out how to restore the original recovery loader and it recovered fine. It must be something in this hacked version of twip that isn't applying the ota correctly. Going to try to build a version of twip just for this
Erodros said:
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
Click to expand...
Click to collapse
You are not. I am the noob trying to figure out the whole root process and I don't even know how to backup the existing bootloader and ROM so I can restore it with ADB if I screw it all up in root..... I feel clueless and know just enough to be dangerous... yet for some reason, I'm not afraid, just need to learn.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Whew! I did it. First I took the instructions from here as a start:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
In fact, if you can "almost" follow the instructions verbatim. The problem is that the data drive is encrypted and the default android password didn't work so I had to modify the boot.img to not encrypt the data partition then do a wipe. supersu installed fine then.
As for gapps, that was tricky. You have to manually install google webview apk as the built in one is garbage.
Still working on the vr settings. Camera has issues with scaling as I think good believes it to be a widescreen when its a 4.3.
Once I get it down, I will make a boot.img and recovery.img that should just work.