All Credit to @thecubed. Please thanks him on his OP here
This is not my original work.I am just sharing this GUIDE for easy rooting of L90 with latest updated, those are not supported by towelroot.
I have tested this method myself and it is working perfectly for me, but it is also possible that it might not work for you for some reasons, so don't panic, just post your problem or whatever error you are facing (please attach screenshot if possible). I or other thread members will try to troubleshoot it. After resolving the problem I'll update this post, so that other members do not face such problem again
Click to expand...
Click to collapse
PLEASE, USE THIS TUTORIAL AT YOUR OWN RISK, IF SOMETHING WENT WRONG (because of your stupidity) ME OR XDA WILL NOT RESPONSIBLE FOR YOUR LOSS.
I HAVE ONLY TESTED THIS METHOD WITH MY L90 D410 AND IT MUST WORK WITH OTHER VARIENTS:fingers-crossed: . BUT STILL FOLLWO THIS GUIDE AT YOUR OWN RISK
Click to expand...
Click to collapse
First of all Install USB Drivers from following link :-
Click here to download L90 USB Drivers
After installing USB Drivers, download Rootl90.zip file attached to this post below and extract it to C Drive of your PC.
On your phone, Goto Settings -> General -> Developer options and enable USB debugging by ticking the check box.
(If you are unable to find Developer options, then go to About phone -> Common -> Software Information and continuously tap on Build amount for 5 to 6 times, it will enable developer options)
Now Connect your phone with PC in LG Software mode, open device manager and confirm ADB Device listed at the top of the list, as an image attached below:-
{
"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"
}
Now open Rootl90 folder, that you extracted to the C drive in the first step.
In this folder, press and hold shift key on the keyboard, right click on blank place and click on open command window here. The command prompt will start with c:\Rootl90>
Now type following commands one by one in the command window (simply copy, paste and hit enter) :-
Code:
adb reboot --bnr_recovery
adb push start_restore /temp/start_restore
adb push permaroot.bin /temp/start_restore
adb reboot
and match result as shown in following images :-
Command 1
After this phone will reboot into recovery as shown in the image below
Now Proceed to Command 2.
Command 2
Command 3
Command 4
After the last command your device will reboot, congratulations your phone is now rooted. Download and install Supersu form playstore.
reserved
Guys plz reply if worked for other than D410 Model
D410 here, after first command wait til the drivers are installed,
There is a redaction error in your comands, the correct are:
adb reboot --bnr_recovery
adb push start_restore /temp/start_restore
adb push permaroot.bin /temp/start_restore
adb reboot
VainxTheLurker said:
D410 here, after first command wait til the drivers are installed,
There is a redaction error in your comands, the correct are:
adb reboot --bnr_recovery
adb push start_restore /temp/start_restore
adb push permaroot.bin /temp/start_restore
adb reboot
Click to expand...
Click to collapse
Thanks for correction
gdjindal said:
Thanks for correction
Click to expand...
Click to collapse
Aren't these the same commands available in the purpledrake script?
Sent from my LG-D405n using XDA Free mobile app
razoract said:
Aren't these the same commands available in the purpledrake script?
Sent from my LG-D405n using XDA Free mobile app
Click to expand...
Click to collapse
yes it is from purpledrk script.
thanks!
thanks!
I've tried it on D405n and it works. Thank you.
.
LOOOL
Why should i use
Code:
adb reboot --bnr_recovery
adb push start_restore /temp/start_restore
adb push permaroot.bin /temp/start_restore
adb reboot
when i could use simple original purpledrake way. i think you took the files from purpledrake thats all ? or i am wrong ???
Does not work on t-mobile LG L90, D415 with the software version D41510e.
adb reboot --bnr_recovery reboots to a blank screen. Presumably it's still a recovery -- adb connects. But "adb push start_recovery /temp/start_recovery" does not work -- no such file or directory. Changing the destination to /tmp in both adb push commands does push files to the phone but there is no root after reboot.
Looking at the purpledrake script, I also see that the vulnerability tests looks for a process "brd" on the phone but there is no such command in the output of ps.
Any ideas?
LG L90, T-mobile D415 with SW version D41510c also does not work.... same exact issue as described above...
---------- Post added at 10:36 PM ---------- Previous post was at 10:17 PM ----------
voland66 said:
Does not work on t-mobile LG L90, D415 with the software version D41510e.
adb reboot --bnr_recovery reboots to a blank screen. Presumably it's still a recovery -- adb connects. But "adb push start_recovery /temp/start_recovery" does not work -- no such file or directory. Changing the destination to /tmp in both adb push commands does push files to the phone but there is no root after reboot.
Looking at the purpledrake script, I also see that the vulnerability tests looks for a process "brd" on the phone but there is no such command in the output of ps.
Any ideas?
Click to expand...
Click to collapse
You should use TowelRoot app, it roots the phone in like 2 seconds and no reboot is required...
Search in google for "how to root T-mobile LG D415" - first link has few instructions but leads you to the website where to download the tr.apk (if doing from phone) long click on lambda sign and select "save link" ... thank install the app and run it... 2 seconds... done...
996
cardusan said:
LG L90, T-mobile D415 with SW version D41510c also does not work.... same exact issue as described above...
---------- Post added at 10:36 PM ---------- Previous post was at 10:17 PM ----------
You should use TowelRoot app, it roots the phone in like 2 seconds and no reboot is required...
Search in google for "how to root T-mobile LG D415" - first link has few instructions but leads you to the website where to download the tr.apk (if doing from phone) long click on lambda sign and select "save link" ... thank install the app and run it... 2 seconds... done...
Click to expand...
Click to collapse
Towelroot works on the previous SW version (was it D41510c? I don't remember). But there is an update to the version 10e and towelroot does not work on it (at least it did not work yesterday, this was the first thing I tried). Unfortunately, I updated without checking forums and I might have forgotten to turn on survival mode in supersu (although i'm not sure survival mode works).
voland66 said:
Towelroot works on the previous SW version (was it D41510c? I don't remember). But there is an update to the version 10e and towelroot does not work on it (at least it did not work yesterday, this was the first thing I tried). Unfortunately, I updated without checking forums and I might have forgotten to turn on survival mode in supersu (although i'm not sure survival mode works).
Click to expand...
Click to collapse
Towelroot worked fine on my D41510c. I have not updated though, and probably won't as some say nothing really changed with the update.
I have that version and I was able to root with towelroot - it did not even request a reboot or anything... just 2 seconds of my time...
I am now running CM11 and it flies - this phone has just stepped over few models that are considered to be "faster":... not in the CM world
cardusan said:
I have that version and I was able to root with towelroot - it did not even request a reboot or anything... just 2 seconds of my time...
I am now running CM11 and it flies - this phone has just stepped over few models that are considered to be "faster":... not in the CM world
Click to expand...
Click to collapse
Which version do you have 10c or 10e? Is this T-Mobile phone? If it is 10e -- did you just use towelroot straigtforwardly? Was the phone rooted prior to 10e upgrade?
I upgraded rooted phone from 10c to 10e, possibly having forgotten to turn on survival mode in supersu, and lost root. I still have adaway's host file (so ads are blocked, now permanently since I can't go back to the standard host file), I still have supersu files in relevant directories but no root when the phone is running. And towel root says that it can't work on my phone. I was just assuming that the update has a newer kernel that fixes vulnerability exploited by towelroot. I'd love to recover root if I could.
cardusan said:
I have that version and I was able to root with towelroot - it did not even request a reboot or anything... just 2 seconds of my time...
I am now running CM11 and it flies - this phone has just stepped over few models that are considered to be "faster":... not in the CM world
Click to expand...
Click to collapse
Hello!
I would have just a short question about the root. If I make the root with this towelroot am I loosing the guarantee? I mean this procedure is open the bootloader or this is just a "smooth" root?
Thank you!!!!
fynky said:
Hello!
I would have just a short question about the root. If I make the root with this towelroot am I loosing the guarantee? I mean this procedure is open the bootloader or this is just a "smooth" root?
Thank you!!!!
Click to expand...
Click to collapse
Yes, you will lose the guarantee. I believe towelroot just roots your phone.
D1358531 said:
Yes, you will lose the guarantee. I believe towelroot just roots your phone.
Click to expand...
Click to collapse
Thank you for your quick reply.
So if it is just a simple root and in the future I will have some problem with my phone I will be able to put back the original software to the phone without any mark? Because at Samsung phones have a special trick. If you root your phone and the bootloader is open the Knox code (this is the special trick) is jump from 0 to 1 and you will not be able to replace it anymore and you will lose the guarantee forever with it.
I wouldn't like to change the software on my phone I just would like to install programs to the SD card but it is not allowed under the KitKat unless I root my phone. But I think the simple root should be enough for that isn't it?
BTW. Will I need a special program after the root is I want to install to SD card?
Thank you very much!!!!
Before I do this I would like to know if there will be a custom recovery like two? Does this work with the D415? Would I still have my T-mobile connection? I only rooted my Nexus 7 2012 with the Nexus root Toolkit.
Related
Team,
This One-Click Root process will copy over the rooted-update.zip or unroot-update.zip file then reboot your phone. Follow the instructions in the CMD prompt that launches.
Credits:
LeshaK at Samdroid: for the original rooted-update.zip.
gunnarhafdal : for creating the Mac GUI for my app.
This has been tested on stock Android 2.1 Eclair only. If you rooted using another process you can use this process to unroot as long as you didnt load a rom that created links to busybox.
For the following models:
GT-I9000
Captivate SHG-I897
Vibrant SGH-959
GT-I9000M
Epic SPH-D700 (Untested but should work like other phones. Post with your results. This is harmless it will either work or it wont. It copies over 3 files to your existing build.)
Rooting adds the following to your system and unrooting removes them:
/system/xbin/busybox (version 1.17.1)
/system/xbin/su
/system/app/Superuser.apk (version 2.3.1)
and links /system/bin/su to /system/xbin/su
More will follow as they are released. PM me to add your Galaxy S Model.
Warning: I am not responsible for bricked phones, rooting can void your warranty....
PC Instructions:
{
"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"
}
Download the app: GalaxyS_One-Click_Root_All_Models-PC. Or down Below.
Watch the video for the full procedure on The Unlockr.
Video/Procedure Link Click Here
Requirements: Install Link: Dot Net Framework version 4
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. For Windows x86 and x64 systems make sure that the Samsung Drivers are installed. You can get them here.
3. Extract the contents of GalaxyS_Vibrant_One-Click_Root.rar to a folder.
4. Connect your phone to your PC via the USB cable and launch the file "T-Mobile Vibrant One-Click Root.exe" file.
5. Click the "One-Click Root" button. This will launch a command shell follow the instructions in the CMD window.
Mac Instructions:
Download the app: OneClickRootMac. Or Down Below.
It requires Mac OS X 10.5 or higher.
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. Connect the phone to your computer.
3. Click one of the buttons depending on what you want to do.
4. After the phone has rebooted into recovery select "apply sdcard:update.zip" for I9000 and I9000M and choose "Reinstall Packages" for the US models using the volume keys and then press the home button for I9000 and I9000M and the power button on the right top side for US models to start the process.
=====================================================================
Done! You are rooted.
=====================================================================
Un-Rooting Instructions:
To Un-Root follow the same instructions except click on the Un-root button. If you rooted using another process you can use this process to un-root as long as you didnt load a rom that created links to busybox. I would suggest to restore you phone back to stock ROM before even needing to unroot and if you are on stock un-root all you want otherwise what is the point of un-rooting.
=====================================================================
Getting Started with Android After Rooting:
Flash Clockwork Custom Recovery On your phone:
Follow this URL to find fill information on ROM Manager:
http://forum.xda-developers.com/showthread.php?t=734164
Install ROM Manager from Market.
Launch ROM Manager and click on Backup ROM and save you android O/S stock rooted making getting back to stock un-rooted much easier..
the simplest root just got simpler
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..
junkdruggler said:
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..
Click to expand...
Click to collapse
I'd say its easier to not mess up. Faster for sure, if you already have the drivers installed.
This is for our newer brethren or anyone else that want a straight forward root method. And for those having trouble entering recovery from the button presses. ADB is bundled in the rar file so you don't need Android SDK.
Another thing that will help most is when I add unroot to the app which I should have completed tomorrow.
Doon2 asked for it, so here it is.
I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?
s15274n said:
I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?
Click to expand...
Click to collapse
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App
TGA_Gunnman said:
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well all most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
this
I am stoked that someone would take the time to make this program. I dont have immediate access to a PC(I use a mac) but an easy unroot program clinches the decision to root my phone. thank you for taking the time to make this much props
please do it for Mac OS.
best wishes...
Awesome application thanks!
Sent from my SGH-T959 using XDA App
Great, easy app. Works!
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
alsatea said:
please do it for Mac OS.
best wishes...
Click to expand...
Click to collapse
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?
TGA_Gunnman said:
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?
Click to expand...
Click to collapse
If you write it in java, then it will run any OS, right?
Relase src code. I may be able to port to unix/macosx and/or java.
I have Windows 7 installed through Bootcamp and it worked perfectly. Thanks
kelmerp said:
If you write it in java, then it will run any OS, right?
Click to expand...
Click to collapse
Ok Let me see what I can do.
Yeah release the source... Ports will follow if necessary
jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
I know what you mean. I'm still used to holding down the buttons until the recovery screen pops up like on my G1. On the Vibrant, I have to remind myself to let go of the buttons as soon as the "Vibrant" screen comes up.
Yes, the overall process involved to use this program is longer, involves more steps, and, therefore, easier to screw up. Also, the fact that you have to download more than one file increases the chances of messing something up because of the possibility of corrupted files. Also, the "flash in recovery" method is OS agnostic, and technically doesn't even require a computer since you can download and rename the zip file right on your phone if you want to. Still, it's very easy to follow and would appeal to those who are new to rooting and don't feel comfortable with booting into recovery mode.
Updated the app to include unroot. Created a new update.zip file that will remove root. Also fixed the CMD shell launching minimized.
Lets see the java port. or even an APK to do so
jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
Why fuss with button pushes, just enable debugging, plug in your phone, open a command prompt and type the following
Code:
adb reboot recovery
It's easier than messing with those buttons I assure you.
Hey all! This is the new home of the Droid 4 Utility (NOW WITH SAFESTRAP THANKS TO HASHCODE) for Windows/Mac/Linux!
There are (still) no fastboot files as of writing this (2/28/2012) so use Safestrap at your own risk
Once they come out I will be making a full version that includes fastboot restore. For now, the utility is only a few MB compared to a GB+.
From this point forward I will be taking charge of updating the Droid 4 Utility for Windows/Mac/Linux
This way mattlgroff has a little less work on his hands and can focus more on IMPORTANT things like bootloaders, ICS, etc...
MAC/LINUX: Be sure to read the instructions below (or README file) if you are not familiar with using terminal as root or executing bash scripts!
-Changes
~~as of 2/18/ 11:30PM PST
Fixed bug where Superuser.apk was pushed to /data instead of /system/app/
Fixed unroot script to properly remove Superuser.apk
~~as of 2/19 4:30 PM PST
Fixed chmod in root method from 4775 to 6775
~~as of 2/28 6:15PM PST
Added Safestrap recovery!!
~~as of 3/2
fixed script to chmod +x ./files -R so that you can actually run the files on mac and linux (that would be important huh?)
DOWNLOADS
WINDOWS
Size: 7.75 MB
MD5: f82bf8d8a085ff95b696712b8caa0f1b
Link: http://tinyw.in/KKB8
MAC
Size: 7.19 MB
MD5: dc8468d051d59963914a0b8a054b83b8
Link: http://tinyw.in/vx2A
LINUX
Size: 7.26 MB
MD5: 0c082efbff48e614b9d8ebffc7eca3eb
Link: http://tinyw.in/tpt0
Here's how:
Windows:
Simply Unzip the files, and run Droid4Windows.bat as administrator (right click>run as administrator)
Mac/Linux:
Simply extract the zip then
Code:
su
Then enter the root password NOTE: This is not YOUR password, this is the ROOT password. If you dont know it, you can always use
Code:
sudo passwd
to reset the root password
Next run:
Code:
cd /the path to where you extracted the files/
for example, heres what I have to type:
Code:
cd /home/skylar/Desktop/Droid4UtilityLinux/
next run the appropriate bash script:
Code:
bash Droid4linux
OR
Code:
bash Droid4mac
I'm sorry to say I don't actually own a Droid 4, so I'm doing this blind. Please report any problems or bugs you have.
Have fun and I hope you enjoy! [/SIZE]
CLICK HERE TO DONATE
SCREENSHOTS
{
"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"
}
CLICK HERE TO DONATE
I can not get this to unroot.
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
UNROOTING SCRIPT
created by DooMLoRD
based heavily on FlashTool scripts (by Bin4ry and Androxyde)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
Note: This removes superuser from both possible locations
So seeing one error of now finding Superuser is NORMAL!
---------------------------------------------------------------
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
The system cannot find the path specified.
--- TESTING FOR SU PERMISSIONS
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- cleaning
The system cannot find the path specified.
--- pushing busybox
The system cannot find the path specified.
--- correcting permissions
The system cannot find the path specified.
--- remounting /system
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- pushing unroot script
The system cannot find the path specified.
--- correcting permissions
The system cannot find the path specified.
--- executing unroot
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- cleaning
The system cannot find the path specified.
--- rebooting
The system cannot find the path specified.
ALL DONE
Press any key to continue . . .
The system cannot find the path specified.
Please make a selection or hit ENTER to return:
Click to expand...
Click to collapse
prodigyweb said:
I can not get this to unroot.
Click to expand...
Click to collapse
Sounds like you aren't running this inside the folder that also contains the /files/ folder. If you have it by itself of course the path's won't find it...because you moved it or you aren't "cd" into the directory of the utility.
appears after a phone/computer reboot and canceling the ADB process in my tasks it now is rebooting the phone and working. Thanks!
prodigyweb said:
My setup is: http://i.imgur.com/Surbz.png
should it be within the adb package from android itself?
Click to expand...
Click to collapse
Is your USB Debugging Mode enabled and "Unknown Sources" in your application settings?
Hm, I turned on USB Debugging in the settings, but it's not starting up when I plug in a USB cable, and adb can't find the device. ???
highlandsun said:
Hm, I turned on USB Debugging in the settings, but it's not starting up when I plug in a USB cable, and adb can't find the device. ???
Click to expand...
Click to collapse
While your phone is plugged in, see what drivers are in device manager and remove them. Then restart your phone while its still connected through USB. See if that reinstalls all the necessary drivers and try again.
reigndropz said:
While your phone is plugged in, see what drivers are in device manager and remove them. Then restart your phone while its still connected through USB. See if that reinstalls all the necessary drivers and try again.
Click to expand...
Click to collapse
This is Linux, so no device manager. I think I needed to add the Motorola vendorID to my udev rules first, I got it working eventually. Rooted, great. Now to go and fix the character maps so I can fully use Connectbot.
highlandsun said:
This is Linux, so no device manager. I think I needed to add the Motorola vendorID to my udev rules first, I got it working eventually. Rooted, great. Now to go and fix the character maps so I can fully use Connectbot.
Click to expand...
Click to collapse
Ah ok.....how are you with deodexing? I have been trying to deodex the SystemUI but I am not having any success. I add the jars but it keeps going and going and doesnt seem to end. Soon as I get the SystemUI deodexed, I'll throw a battery percent icon here....
reigndropz said:
Ah ok.....how are you with deodexing? I have been trying to deodex the SystemUI but I am not having any success. I add the jars but it keeps going and going and doesnt seem to end. Soon as I get the SystemUI deodexed, I'll throw a battery percent icon here....
Click to expand...
Click to collapse
Hm, haven't done anything with theming tweaks. Dunno, sorry.
You need adb to be enabled at boot time, so you can adb logcat during the startup and see what failed.
By the way, the Linux archive is not immediately usable, you need to chmod +x everything under the files/ subdirectory to make them executable first.
highlandsun said:
Hm, haven't done anything with theming tweaks. Dunno, sorry.
You need adb to be enabled at boot time, so you can adb logcat during the startup and see what failed.
By the way, the Linux archive is not immediately usable, you need to chmod +x everything under the files/ subdirectory to make them executable first.
Click to expand...
Click to collapse
Hey thanks for pointing that out! I didnt notice because they were already executable on my computer. I added
Code:
chmod +x ./files -R
to the script on startup so no one should have to manually do it anymore, sorry about that
prodigyweb said:
I can not get this to unroot.
Click to expand...
Click to collapse
Make sure you have done all of the steps below
Prework
1. Plug in phone to computer.
2. Turn on USB Debugging. Menu -> Settings -> Application -> Development -> USB Debugging
3. Confirm latest Moto driver is installed. Go to Device Manager on Windows while the D4 is plugged into it and confirm you see ADB Interface listed with Mot Composite ADB Interface listed in the group. If you see that, skip #4 & #5. There are other ways to go about this, but this is the simplest and surefire way to confirm the driver is there and compatible.
4. Go get Moto driver and install it: USB and PC Charging Drivers - Motorola Mobility, Inc. USA It is an exe file that must be run and your computer has to restart when completed.
5. Go back into your Device Manager after reboot with the phone plugged in and confirm ADB Interface is there and no error exists.
Done.
I can't get this to root, it appeared to have rooted once since Superuser was installed but TBU said not root access. Now I get message " error more than one device and emulator" when I try to root again or unroot. any idea?
contemplating getting this through a client, any word on fastboot and unlocked updates?
or is the droid 4 destined to be like all other moto phones and lack a soul...
I really wanted the Photon, but dev on it was strangled to death!
Hammerfest said:
contemplating getting this through a client, any word on fastboot and unlocked updates?
or is the droid 4 destined to be like all other moto phones and lack a soul...
I really wanted the Photon, but dev on it was strangled to death!
Click to expand...
Click to collapse
The phone itself is great. Good build quality, fantastic keyboard, fast, etc. I have not heard any news on fastboot files yet. I assume it's just a matter of time but who really knows for sure. Unlock updates? As in unlock the bootloader? I don't ever expect to see that happen, personally.
Despite that, development seems to be coming along nicely with very usable AOSP CM9, AOKP, and Gummy ROMs. The relative ease with which Razr ROMs can be ported to the D4 (due to almost identical internal components) should help on that front as well as Razr development is seems very strong.
Does this Utility still work after the latest update?
I had previously rooted via this utility and had frozen a bit of bloatware w/ TB. I have since unfrozen the bloatware and unrooted. As soon as the install message pops up again I plan to run the update, but was wondering if I will be able to re-root the same way once I do that.
mancowmilitia said:
Does this Utility still work after the latest update?
I had previously rooted via this utility and had frozen a bit of bloatware w/ TB. I have since unfrozen the bloatware and unrooted. As soon as the install message pops up again I plan to run the update, but was wondering if I will be able to re-root the same way once I do that.
Click to expand...
Click to collapse
I've heard people having mixed results trying to re-root using the utility. Some seem to have no problem but others said they had to run the exploit directly. Not sure why.
I just used the Voodoo OTA Root Keeper app to hide root while the update was being applied and then restored root.
kwyrt said:
I've heard people having mixed results trying to re-root using the utility. Some seem to have no problem but others said they had to run the exploit directly. Not sure why.
I just used the Voodoo OTA Root Keeper app to hide root while the update was being applied and then restored root.
Click to expand...
Click to collapse
I installed the upgrade with no issues. I was able to re-root without complication as well. The only message I received was that the Superuser.apk installation "failed" because it was already there. Others have noted that unrooting doesn't delete the file. But, its presence did not stop my upgrade.
This time I installed Voodoo and will go that route for the next OTA.
Is there a mirror link for the Windows Utility? The download keeps timing out on me.
heres a link for an older copy
http://goo.im/apps/mattlgroff/Droid4Utility0.3.zip
Alright, so let's start the fun
These are the steps i did for successfully unlocking my BL.
I can't and won't guarantee that theese steps are going to work for you. please report back here if it worked for you or not and please post also the buy-date of your phone
it might be possible that this works for other firmwares too, please try and report back here thanks
Requirements
- a Linux distro (mine is Xubuntu 12.10, but should work on every Linux OS)
- a working and updated ADB (for installing ADB, search for tuts here on xda )
- a unlockable firmware (preferably ANEUBK)
- be willing to recycle all your warranty papers
- and most important: a brain with the ability to read
The steps
1) charge your phone to 100%
2) connect your phone in LG software mode
3) if you have the path to your adb defined, then goto 3a). if not, then goto 3b)
3a) open a terminal and type
Code:
adb reboot oem-unlock
{
"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"
}
3b) open a terminal and type
Code:
cd ~/android-sdk/platform-tools
(if you've installed the android-sdk in your home directory under "android-sdk". if not, change it to the directory you've installed it)
then type
Code:
adb reboot oem-unlock
4) now you should see this on your phone:
do i wanna unlock it? of course i do so press the vol + button ATTENTION: there is no further warning, your whole /data/ partition will be formatted!!!
5) now you should see this, and your BL is unlocked and your /data/ partition is wiped
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
10) do the harlem shake and be happy about your unlocked BL
and please, don't post "thanks" if i've helped you, just hit the thanks button
Does it applies on 234 devices too? I ll not have access on a linux pc till monday!
Cool dude, thanks.
Do you think its possible to do this with those bootable Linux OS cd (so i dont have to install linux on my hd just for dooing that) ?
Do you loose the unlocked BL if you install another KDZ after the unlocking?
Someone know why not working on every windows?
I have the android sdk installed and the same procedure worked for me without linux.
nikosblade said:
Does it applies on 234 devices too? I ll not have access on a linux pc till monday!
Click to expand...
Click to collapse
i honestly don't know try it, like i've said, give it a try and report back
profyler said:
Cool dude, thanks.
Do you think its possible to do this with those bootable Linux OS cd (so i dont have to install linux on my hd just for dooing that) ?
Do you loose the unlocked BL if you install another KDZ after the unlocking?
Click to expand...
Click to collapse
hmmm, possible? maybe, but this would be extremely slow, cause you've gotta get adb working first and so on. so i'd say it won't work, but not sure.
but some distros have got the ability to install them as a "windows prog", this creates a virtual harddrive where linux can be booted from, so no need for reformatting the hdd just google about it
some users reported that it will not be lost after flashing a kdz. but also here: not sure, cause i haven't tried it myself yet (my BL is now unlocked for about 3h yet )
verlol said:
Someone know why not working on every windows?
I have the android sdk installed and the same procedure worked for me without linux.
Click to expand...
Click to collapse
i guess it is driver related... what firmware do you use? german or euro-open?
laufersteppenwolf said:
View attachment 1861354
Click to expand...
Click to collapse
This "final" screen I can confirm on my 262-000 from Amazon. I used Windows and http://forum.xda-developers.com/attachment.php?attachmentid=1859693&d=1365149301 for the ADB driver but the same method. It takes like 2sec to do! I installed CWM etc. fine afterwards!! Thank you!
Security error
I don't get the screen like in 4)
I just get Security Error, any ideas?
Don't work with ADEUBK 262 000
I can only unlock with the china 20a.
mrlollog said:
I don't get the screen like in 4)
I just get Security Error, any ideas?
Click to expand...
Click to collapse
This is not universal, seems with latest update LG showed some mercy on German users...rest can feel screwed all over again
F*ck you LG retards they are only good if Google screws them good, who's your papa :silly:
On 234 this didn't work with Linux and the leaked 20A.
I might try later to update the phone (GBR) with the official one but I wouldn't hold my breath.
Sent from my Nexus 7 using Tapatalk 2
laufersteppenwolf said:
i guess it is driver related... what firmware do you use? german or euro-open?
Click to expand...
Click to collapse
I use euro-open.
If its driver related, which driver is needed?
I only know of the Google USB Driver for the Android Composite ADB Interface.
Not works (on linux vitural machine ) The pone says ... Lg Security error...
me too
I do not get unlock
tiflao said:
Not works (on linux vitural machine ) The pone says ... Lg Security error...
Click to expand...
Click to collapse
same here, on win or on vm i got this error ...... (262-00)
when you get " Lg Security error..." is the phone bricked or you just need to pull the battery and reboot and than its fine again?
DavidXanatos said:
when you get " Lg Security error..." is the phone bricked or you just need to pull the battery and reboot and than its fine again?
Click to expand...
Click to collapse
The Phone reboots after ~5 secs.
laufersteppenwolf said:
Alright, so let's start the fun
These are the steps i did for successfully unlocking my BL.
I can't and won't guarantee that theese steps are going to work for you. please report back here if it worked for you or not
it might be possible that this works for other firmwares too, please try and report back here thanks
Requirements
- a Linux distro (mine is Xubuntu 12.10, but should work on every Linux OS)
- a working and updated ADB (for installing ADB, search for tuts here on xda )
- a unlockable firmware (preferably ANEUBK)
- be willing to recycle all your warranty papers
- and most important: a brain with the ability to read
The steps
1) charge your phone to 100%
2) connect your phone in LG software mode
3) if you have the path to your adb defined, then goto 3a). if not, then goto 3b)
3a) open a terminal and type
Code:
adb reboot oem-unlock
View attachment 1861346
3b) open a terminal and type
Code:
cd ~/android-sdk/platform-tools
(if you've installed the android-sdk in your home directory under "android-sdk". if not, change it to the directory you've installed it)
then type
Code:
adb reboot oem-unlock
View attachment 1861348
View attachment 1861349
4) now you should see this on your phone:
View attachment 1861353
do i wanna unlock it? of course i do so press the vol + button ATTENTION: there is no further warning, your whole /data/ partition will be formatted!!!
5) now you should see this, and your BL is unlocked and your /data/ partition is wiped
View attachment 1861354
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
View attachment 1861355
10) do the harlem shake and be happy about your unlocked BL
and please, don't post "thanks" if i've helped you, just hit the thanks button
Click to expand...
Click to collapse
Thanks for the tutorial - but can you explain why is this just working on a Linux OS ? I mean what's the difference between trying to unlock the BL on a Win7/8 OS or a Linux OS ?
THanks
DavidXanatos said:
when you get " Lg Security error..." is the phone bricked or you just need to pull the battery and reboot and than its fine again?
Click to expand...
Click to collapse
Sometimes is semi-bricked, specialy after the "morning-call empty"
Don't worry, re-flashing will solve the problem.
Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"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"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}
Hello Nexus Player users. NRT has supported this device for a little while but I never had a dedicated thread.
This device is definitely the most unique of the Nexus lineup - so lets try and keep the posts in this thread specific to this device alone.
Enjoy!
Hello,
Thanks for this great tool.
I tried it last night for a couple of hours and it only seemed to connect to my Nexus Player with the google drivers in step 2.
Also I think it should be noted (sorry if I missed it somewhere) that you need a mouse to complete this root process.
I dont have one and I am now stuck waiting to get one.
I will pick this back up when I get one.
thanks for your effort, Kevin
haeffnkr said:
Hello,
Thanks for this great tool.
I tried it last night for a couple of hours and it only seemed to connect to my Nexus Player with the google drivers in step 2.
Also I think it should be noted (sorry if I missed it somewhere) that you need a mouse to complete this root process.
I dont have one and I am now stuck waiting to get one.
I will pick this back up when I get one.
thanks for your effort, Kevin
Click to expand...
Click to collapse
You don't need a mouse, the root is fully automated in this release.
Sent from my Nexus 5X using Tapatalk
I have installed the drivers , I have unlocked the unit.
I have tried to just root the device and root + flash custom recovery and I get to this screen every time.
Sorry can only link the google pic - https://goo.gl/photos/dCkKYF3j7XpoPojVA
Without a mouse I am stuck and have to repower the nexus player and kill the NRT kit app and start over to no avail.
If I am missing a step please let me know.
(I have seen on other forums that a mouse is needed to get past this step thus my comments and my current experience)
Here is my log where I just ran the root only process again -
Nexus Root Toolkit v2.1.4
Masterlists:
- LatestToolkitFiles.ini 3112
- AndroidDeviceListFull.ini 3112
- AndroidDeviceListFlash.ini 3112
FUGU-FUGU: Android 6.0.1 - Build: MMB29T
Live log initiated [2016-01-19]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
85D1781B device
fastboot devices
Connectivity Status: ADB Device Connected
Rebooting your device into bootloader mode...
adb reboot bootloader
Checking Fastboot Connectivity
fastboot devices
85D1781B fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
Temporarily Booting TWRP...
fastboot boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Recovery_Custom\TWRP\twrp-2.8.7.0-fugu.img"
Checking ADB Recovery Connectivity
adb devices
adb devices
thanks for your help in advance
Kevin
haeffnkr said:
I have installed the drivers , I have unlocked the unit.
I have tried to just root the device and root + flash custom recovery and I get to this screen every time.
Sorry can only link the google pic - https://goo.gl/photos/dCkKYF3j7XpoPojVA
Without a mouse I am stuck and have to repower the nexus player and kill the NRT kit app and start over to no avail.
If I am missing a step please let me know.
(I have seen on other forums that a mouse is needed to get past this step thus my comments and my current experience)
Here is my log where I just ran the root only process again -
Nexus Root Toolkit v2.1.4
Masterlists:
- LatestToolkitFiles.ini 3112
- AndroidDeviceListFull.ini 3112
- AndroidDeviceListFlash.ini 3112
FUGU-FUGU: Android 6.0.1 - Build: MMB29T
Live log initiated [2016-01-19]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
85D1781B device
fastboot devices
Connectivity Status: ADB Device Connected
Rebooting your device into bootloader mode...
adb reboot bootloader
Checking Fastboot Connectivity
fastboot devices
85D1781B fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
Temporarily Booting TWRP...
fastboot boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Recovery_Custom\TWRP\twrp-2.8.7.0-fugu.img"
Checking ADB Recovery Connectivity
adb devices
adb devices
thanks for your help in advance
Kevin
Click to expand...
Click to collapse
Its looking to detect your device while you see that TWRP screen. Your issue is simply driver related. The toolkit should throw you a message at that stage saying it can't find your ADB recovery device - and it provides some tips/suggestions for how to configure it. A simple fix would to be try reinstalling the drivers at this stage, and/or opening your device manager to make sure your device is configured. If nothing is showing up, try unplugging and replugging device.
WugFresh said:
Its looking to detect your device while you see that TWRP screen. Your issue is simply driver related. The toolkit should throw you a message at that stage saying it can't find your ADB recovery device - and it provides some tips/suggestions for how to configure it. A simple fix would to be try reinstalling the drivers at this stage, and/or opening your device manager to make sure your device is configured. If nothing is showing up, try unplugging and replugging device.
Click to expand...
Click to collapse
I have uninstalled drivers and reinstalled 5 times... I can not get it to stay connected.
When I run the driver test and the unit reboots into Fasboot mode then it reboots again and it hangs....the only way I can get it to connect back up again is to go into settings on the nexus and toggle the USB debugging from off to on. The PC then sees the nexus and the script finishes.
I am out of options as to how to get this to connect after it reboots.
EDIT -
I can get the driver script to get to the success without intervention after I have reinstalled the drivers again.
I can not get the past the TWRP screen... as it boots into this screen it disables the ABD connectivity and I am stuck.
Any further help would be appreciated.
thanks for your time
Kevin
haeffnkr said:
I have uninstalled drivers and reinstalled 5 times... I can not get it to stay connected.
When I run the driver test and the unit reboots into Fasboot mode then it reboots again and it hangs....the only way I can get it to connect back up again is to go into settings on the nexus and toggle the USB debugging from off to on. The PC then sees the nexus and the script finishes.
I am out of options as to how to get this to connect after it reboots.
EDIT -
I can get the driver script to get to the success without intervention after I have reinstalled the drivers again.
I can not get the past the TWRP screen... as it boots into this screen it disables the ABD connectivity and I am stuck.
Any further help would be appreciated.
thanks for your time
Kevin
Click to expand...
Click to collapse
Very nice software indeed, thanks WugFresh, had that issue multiple times, when you get the screen that adb doesn't detect device, give it a minute or two and hit continue and it should redetect it. hope it helps. I think installed driver is fine.
confirmed adb doesn't see device once you hit the temporary twrp.
worked really well, thanks for the software!
I had issue initially connecting to the player it took me couple of tries/toggles of adb (developer tools) to get the USB to recognize, and one time of hard boot while unlocking for no reason it just hung there but the device was unlocked.
upsame problem exactly as people above.i can unlock my nexus player but says adb device recovery was not found.and i have android device in device manager working properly.i've tried everything and not new to rooting phones,tablets or any device that can be rooted and romd.
update switched to another pc and worked fine.thanks
Thanks so much for this application! Worked like a charm on Windows 8.1 and Windows 10. Flawlessly installed TWRP after i flashed the purenexus recovery which is bad.. It got stuck after installing the flash for some reason.
twrp 3.0 not available and it wont proceed with out it.. can you help?
yeah, the androidfilehost link for twrp-3.0.0.0-fugu.img is dead, and the official twrp website only goes upto 2.8.7.0
If anyone has downloaded the TWRP v3 fugu img please reup it and share the link
serpentxx said:
yeah, the androidfilehost link for twrp-3.0.0.0-fugu.img is dead, and the official twrp website only goes upto 2.8.7.0
If anyone has downloaded the TWRP v3 fugu img please reup it and share the link
Click to expand...
Click to collapse
Any luck finding the twrp 3.0.0.0 recovery?
unfortunately not, i ended up using SkipSoft toolkit which installed an older TWRP for the latest official rom, seemed to work without issue, and once installed apparantly the twrp recovery can self update itself
Now that twrp is available again, I have a question.
I was having some success using this tool to root when I was interrupted by the lack of recovery image and that's a good thing I think because it gave me time to look into things a bit more. When rooting do I need to be able to navigate the twrp recovery? I ask because the instructions I've seen say a OTG cable and mouse are needed in twrp, which I don't have and I will need to order one online since there don't seem to be any retail stores in my area with one. I'd just hate to get stuck half way through this thing when I'm really just trying to root so I can get my ouya games running on the Nexus player.
EDIT: Have tried again and was unsuccessful. Downloaded the latest TRWP from the other section of the Nexus Player forum and it rejected it as a bad hashcode. Looks like the app will need an overhaul to deal with changes in where files are located before it will continue to be useful. Frustrated. I was under the impression the Nexus line of Android devices were supposed to be easy to root and unlock--so far they've been anything but for me.
Where can I download the file TWRP-3.0.0.0-fugu.img ?
Where can I download the file TWRP-3.0.0.0-fugu.img ?
The file on the twrp site dont work.
I just got it working with the current TWRP-3.0.0.0-fugu.img.
Download "3.0.0-0" from the TWRP site.
Rename the file to "3.0.0.0" (remove that "-").
Copy file to (program path)/Nexus root toolkit/data/Recover_custom/TWRP.
Then run the tool. It'll think it already downloaded the file.
BTW, I had a LOT of issues with the ADB drivers. Easiest fix I found, was delete the driver in device manager, then unplug/plug in device. Didn't think I'd ever get past that first TWRP screen.
Here's the link to download the 3.0 TWRP.img for nexusplayer.
https://dl.twrp.me/fugu/
Hi. Tried to install lineage yesterday (didn't go well at all). After that car crash I did a factory reset to get back to scratch. However, I cannot reinstsll Netflix now. Google play protect seems to be fine so I'm not sure what is wrong now.
Edit: Google pointed me in the wrong direction. I seen to have lost the certification when I tried to install lineage. What do I need to do to fix this?
Is the problem due to me unlocking the bootloader or would cleaning the cache/data on Google play fix this?
Eggstones said:
Is the problem due to me unlocking the bootloader or would cleaning the cache/data on Google play fix this?
Click to expand...
Click to collapse
Play Protect has nothing to do with it. Your Bootloader in unlocked so you are failing Safetynet. Are you on OOS now or LOS? It's not clear in your post because you said you installed LOS and then did a Factory Reset. That would leave you still on LOS. But you also said back to scratch. So are you on OOS or LOS?
Relocking your Bootloader is possible on both OOS or LOS. That fixes the Safetynet issue either way. Or you can use Magisk on either to fix the Safetynet issue too.
Dirk said:
Play Protect has nothing to do with it. Your Bootloader in unlocked so you are failing Safetynet. Are you on OOS now or LOS? It's not clear in your post because you said you installed LOS and then did a Factory Reset. That would leave you still on LOS. But you also said back to scratch. So are you on OOS or LOS?
Relocking your Bootloader is possible on both OOS or LOS. That fixes the Safetynet issue either way. Or you can use Magisk on either to fix the Safetynet issue too.
Click to expand...
Click to collapse
I couldn't install twrp as it didn't recognise the image file so couldn't proceed with lineage. (Have to say the install guide expect the user to really know a heck of a lot of stuff that should be in the guides). Ended up doing a factory reset back to OOS 9.0.5 (I think that is the latest stock version).
So locking the bootloader would fix this issue? It only seems like Netflix is being cranky.
Not rooted so I don't I can use magisk.
Eggstones said:
I couldn't install twrp as it didn't recognise the image file so couldn't proceed with lineage. (Have to say the install guide expect the user to really know a heck of a lot of stuff that should be in the guides). Ended up doing a factory reset back to OOS 9.0.5 (I think that is the latest stock version).
So locking the bootloader would fix this issue? It only seems like Netflix is being cranky.
Not rooted so I don't I can use magisk.
Click to expand...
Click to collapse
Magisk is the root method, and also used to fix Safetynet issues. You would need TWRP installed though.
Locking the Bootloader right now will fix the issue you are having. It will also factory reset your phone again, so be prepared for that.
That said, installing TWRP is easy if you follow the guides carefully and avoid the obvious pifalls, or simply trying to use the wrong TWRP is a common issue.
In case you still want to try LOS:
This TWRP:
Download twrp-3.3.1-0-oneplus3.img
Follow this guide from funkwizard:
Flashing TWRP Recovery
Adjust the following settings on the phone:
{
"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"
}
USB Debugging:
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking:
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option and make sure that from now on, OEM unlocking option is enabled before you reboot. Sometimes, it might get disabled itself.
Enable Advanced Reboot:
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.
Place TWRP image in the Platform Tools folder in C:\adb
Then boot into fastboot/bootloader mode on your phone by holding volume up + power or selecting the reboot to bootloader via advanced reboot options.
Open a new command prompt in the platform tools folder and run the following command:
Code:
fastboot flash recovery (file name).img
Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead unplug your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed, or you can also use the command:
Code:
fastboot boot recovery.img
/Guide.
Just to be clear, when you fastboot flash the TWRP image i linked you to, the command will be:
Code:
fastboot flash recovery twrp-3.3.1-0-oneplus3.img
Make sure your phone is actually in fastboot mode when you do this. Just follow the guide. (On Windows 10 a command prompt window can be opened in the platform tools folder by typing 'cmd' in the Address Bar in that folder, using Windows Explorer).
Once you have flashed TWRP, you do need to boot straight into that Recovery. If you boot into the OS, the stock Recovery will overwrite TWRP again. (follow the guide).
Once you are in TWRP, swipe to 'allow modifications'. (If you decide to go down the custom ROM path you will need to Format /Data and Wipe Partitions, then connect to your PC and transfer any zips you need to install to Internal Storage).
You will have to decide for yourself whether you want to be rooted with Magisk. While it can be used to fix Safetynet issues, it's not needed for that. If you want root access, flash Magisk. If you don't want root, don't. Simple.
Let's say for arguments sake you don't want to be rooted and have sucessfully installed TWRP. Next step would be to install LOS. Assuming you want a stable ROM, it would be LOS 16 you install. So you would flash the latest build of that along with Gapps and the second Zip in this post:
https://forum.xda-developers.com/showpost.php?p=78433987&postcount=3 which is:
https://drive.google.com/open?id=1Yy...2YSyxEXNXWolH5 (sec-patch-2019-08-01.zip)
That zip takes care of one Safetynet problem. (CTS Profile).
Once you have LOS setup you can relock your Bootloader. That then takes care of the remaining Safetynet issue.
Clear Cache/Data on the Play Store App and reboot. Use the 'Root and Safetynet Checker' App to test Safetynet status. Once it shows 'Passed', Netflix and Banking Apps (Including Google Pay) that rely on Safetynet will all work.
Or stay on OOS and relock your Bootloader. Only you know what you want, although it seems that after our previous discussions you are ready to dip your toes into the custom ROM scene. Don't let some early setbacks deter you. You're almost there.
At the moment I'm just trying to get back to where I started. Funk wizards guide is slightly different from the one on the lineage wiki page. I got as far as installing twrp but got only an error message (something on the lines can't load image). Not sure if that's due to adb being wrongly installed or the image being in the wrong folder. Don't think the wiki page mentioned advanced boot mentioned above. Slightly surprised that my banking apps work fine but not Netflix. You would have thought they would be more 'cranky'.
Been trying again today to do this and am failing massively. Everything seemed fine till I tried to do a backup with helium. Helium is not recognising my OnePlus 3t. Tried to install the drivers that comes with the phone but stopped it after the instal had gone on for about 30 minutes.
Tried the ADB route but the command line doesn't recognise the command. Not sure how to check if it is installed prooerly. Can't remember how I did on my old laptop but on my new hp it doesn't seem to have worked. Remember it being very straightforward so don't understand why it has failed this time
ADB was installed using the lineage page's instructions.
Eggstones said:
Been trying again today to do this and am failing massively. Everything seemed fine till I tried to do a backup with helium. Helium is not recognising my OnePlus 3t. Tried to install the drivers that comes with the phone but stopped it after the instal had gone on for about 30 minutes.
Tried the ADB route but the command line doesn't recognise the command. Not sure how to check if it is installed prooerly. Can't remember how I did on my old laptop but on my new hp it doesn't seem to have worked. Remember it being very straightforward so don't understand why it has failed this time
ADB was installed using the lineage page's instructions.
Click to expand...
Click to collapse
Here's a way to test that ADB can connect to your phone:
- open a PowerShell (a more modern version of CMD) session by right-clicking on the folder where you extracted the ADB files (the folder that contains adb.exe).
- type (without the quotes) ".\adb version". That will tell you the version of ADB your running and that you can execute the command.
- connect your phone to your PC then type ".\adb devices" on your PC. You should get a prompt on your phone asking if you want to trust your PC - say yes. Then you'll get the ID of your phone listed on your PC if everything works ok.
If that all works but just typing "adb devices" doesn't, then that means you haven't set up the of environment settings properly on your PC.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Here's a way to test that ADB can connect to your phone:
- open a PowerShell (a more modern version of CMD) session by right-clicking on the folder where you extracted the ADB files (the folder that contains adb.exe).
- type (without the quotes) ".\adb version". That will tell you the version of ADB your running and that you can execute the command.
- connect your phone to your PC then type ".\adb devices" on your PC. You should get a prompt on your phone asking if you want to trust your PC - say yes. Then you'll get the ID of your phone listed on your PC if everything works ok.
If that all works but just typing "adb devices" doesn't, then that means you haven't set up the of environment settings properly on your PC.
Click to expand...
Click to collapse
Sorry but I do not follow. Type where? If I right click on the folder there is nothing opening up where I can write the command in. Only the normal file options show up.
If I search for it using the windows 10 search function I can start it but it doesn't recognise ./adb as a command. So where have I gone wrong?
@Eggstones
Sorry, I meant to say shift-right-click on the folder and then select "Open PowerShell window here" from the menu.
Sent from my OnePlus 3T using XDA Labs
Thanks. That worked. I have version 1.0.41.
So now the question is why isn't it recognising my phone. I can see it when I go into the file explorer and open all subfolders.
Eggstones said:
Thanks. That worked. I have version 1.0.41.
So now the question is why isn't it recognising my phone. I can see it when I go into the file explorer and open all subfolders.
Click to expand...
Click to collapse
What worked?
1. typing "./adb version"
2. typing "adb version"
3. typing "./adb devices"
And please quote my post otherwise I can't tell that you've replied.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
What worked?
1. typing "./adb version"
2. typing "adb version"
3. typing "./adb devices"
And please quote my post otherwise I can't tell that you've replied.
Click to expand...
Click to collapse
Sorry. Yes all of the above. Have now managed to back up the phone (ok didn't get a promt to confirm backup but it seems to have worked). Not sure why I need to write "./adb" to make the commands work but is seems to have done the trick.
Let's see if I can get lineage on the phone now.
And thanks again for your help and patience
Eggstones said:
Sorry. Yes all of the above. Have now managed to back up the phone (ok didn't get a promt to confirm backup but it seems to have worked). Not sure why I need to write "./adb" to make the commands work but is seems to have done the trick.
Let's see if I can get lineage on the phone now.
And thanks again for your help and patience
Click to expand...
Click to collapse
Glad you got it working. But you said that all three commands worked, the second of which had just "adb version", then said you had to use ./adb. If the second one worked then just plain adb should work all the time.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Glad you got it working. But you said that all three commands worked, the second of which had just "adb version", then said you had to use ./adb. If the second one worked then just plain adb should work all the time.
Click to expand...
Click to collapse
For some reason ADB is only recognised as a command if I use ./ In front of it . No idea why but at least it is working. Will try to do the ROM tomorrow.
There might be crying
Eggstones said:
For some reason ADB is only recognised as a command if I use ./ In front of it . No idea why but at least it is working. Will try to do the ROM tomorrow.
There might be crying
Click to expand...
Click to collapse
That means you haven't set up the Windows environment properly.
The setup instructions in https://wiki.lineageos.org/adb_fastboot_guide.html say:
Code:
On Windows 10:
Open the Start menu, and type “advanced system settings”
Select “View advanced system settings”
Click on the Advanced tab
Open the “Environment Variables” window
Select the Path variable under “System Variables” and click the “Edit” button
Click the “Edit Text” button
Append ;%USERPROFILE%\adb-fastboot\platform-tools to the end of the existing Path definition (the semi-colon separates each path entry)
Can you share:
1. What your Windows Path looks like (screenshot?) and
2. The full path of the folder where you installed ADB
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
That means you haven't set up the Windows environment properly.
The setup instructions in https://wiki.lineageos.org/adb_fastboot_guide.html say:
Can you share:
1. What your Windows Path looks like (screenshot?) and
2. The full path of the folder where you installed ADB
Click to expand...
Click to collapse
Will post that later. When I set it up I followed that guide, but wouldn't be surprised if the pathway thing is wrong as it is a bit opaque in my view.
BillGoss said:
That means you haven't set up the Windows environment properly.
The setup instructions in https://wiki.lineageos.org/adb_fastboot_guide.html say:
Can you share:
1. What your Windows Path looks like (screenshot?) and
2. The full path of the folder where you installed ADB
Click to expand...
Click to collapse
I think I know what's gone wrong.
Pathway: C:\platform-tools
I'm guessing that is the line that should be in the environmental variables...
Eggstones said:
I think I know what's gone wrong.
Pathway: C:\platform-tools
I'm guessing that is the line that should be in the environmental variables...
Click to expand...
Click to collapse
I'd be very surprised if C:\platform-tools is the correct path unless that's actually where you put the unzipped folder.
And kjien\adb... is definitely not right (doesn't include a drive name).
If you use Windows Explorer and select the folder that contains the ADB files and then click on the "Copy path" icon in the menu ribbon (next to the Copy and Paste buttons), then the clipboard will have the correct path.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
I'd be very surprised if C:\platform-tools is the correct path unless that's actually where you put the unzipped folder.
And kjien\adb... is definitely not right (doesn't include a drive name).
If you use Windows Explorer and select the folder that contains the ADB files and then click on the "Copy path" icon in the menu ribbon (next to the Copy and Paste buttons), then the clipboard will have the correct path.
Click to expand...
Click to collapse
That is what I did to get the path. So should C:\platform-tools replace kjien\adb to make it work?