After several failed attempts, I am beginning to doubt if this exploit works.
HOWEVER! There is still hope! If you still have 5.0.2, please try this method: KeyRoot -- PingPong version.KeyRootBy PeregrineX
{
"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"
}
Introducing KeyRoot! The first (POSSIBLE) root exploit for the G890A!
THE EXPLOIT THIS USES MAY NOT WORK! FOR TESTING PURPOSES UNTIL PROVEN WORKING!
Features:
Uses ADB to push the exploit to a runnable location, and chmods it.
Runs the exploit through an ADB shell.
(NOT TESTED) If it fails, runs the exploit again.
(NOT TESTED) Automatically installs su binaries
Instructions:
Install the adb for your OS. It's included in the zip
Enable USB debugging on the phone (Settings >> System >> Developer settings* >> Enable USB debugging
Connect your G890A. Make sure that it is the ONLY phone connected!
Double click on KeyRoot.jar, and click the "ROOT ME NOW!" button.
Wait...
*To enable Developer settings, go to Settings >> System >> About and tap on "Build number" 7 times.
KNOWN BUGS (Reply if you find one not on this list!):
Thread error if the exploit returns the error "Quota exceeded."
Download is in the attachments. IF THIS DOESN'T WORK OR RETURNS AN ERROR, LET ME KNOW!
Don't get your hopes up just yet though, this exploit doesn't work with many android devices.
CHANGELOG:
[+] = Added
[*] = Bug fixed
[-] = Removed
v0.1: Initial release
v0.2:
[+] Device listener. If first ADB command fails due to unconnected device, it stops the thread.
[+] ADB installers. I found that people weren't able to start ADB.
[*] Fixed bug where root would always register as "succeeded," and would try to push the su binaries.
I need people to test this out. The more tests, the merrier, right?
When I double click on keyroot.jar there is no root me now button
---------- Post added at 07:00 PM ---------- Previous post was at 06:27 PM ----------
Ok I'm trying to test this for you.. when I click the root me now button I get an error that add was not found... I have all the files in the root of my c directory... also tried in the folder I unzipped. All the files are in both places
oh！it seems that you will be the hero of s6 active.smile~
通过我的 Nexus 4 上的 Tapatalk发言
This is the error I'm getting:
Pushing root exploit to phone...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
Push done!
Running chmod...
error: device '(null)' not found
Chmod done!
Running exploit... This WILL take a while (about 3 hours or more)
error: device '(null)' not found
error: device '(null)' not found
Exception in thread "Root Thread" java.lang.ClassCastException: java.io.BufferedOutputStream cannot be cast to java.io.ByteArrayOutputStream
at me.peregrinex.keyroot.Root$1.run(Root.java:46)
Click to expand...
Click to collapse
Also when you say make sure its the only device connected, do you mean on USB? I have keyboard/mouse and bluetooth dongle.
Just updating you guys. I'm kind of new to rooting so bear with me.
I had to install adb (http://forum.xda-developers.com/showthread.php?p=48915118#post48915118) (duh!) and keep my phone into USB Debugging mode (duhhhh!)
So now I'm getting:
Pushing root exploit to phone...
180 KB/s (100604 bytes in 0.544s)
Push done!
Running chmod...
Chmod done!
Running exploit... This WILL take a while (about 3 hours or more)
uid=2000, euid=2000
Increfing...
Click to expand...
Click to collapse
Keeping my fingers crossed. Going to go have some nice chicken wings and will come back and check on the phone.
zaurav said:
Just updating you guys. I'm kind of new to rooting so bear with me.
I had to install adb (http://forum.xda-developers.com/showthread.php?p=48915118#post48915118) (duh!) and keep my phone into USB Debugging mode (duhhhh!)
So now I'm getting:
Keeping my fingers crossed. Going to go have some nice chicken wings and will come back and check on the phone.
Click to expand...
Click to collapse
Even if it fails the first time around, just try it again. At minimum, try 3 times since some processes interfere with this exploit apperently
eurosport360 said:
Even if it fails the first time around, just try it again. At minimum, try 3 times since some processes interfere with this exploit apperently
Click to expand...
Click to collapse
I've started it now, gonna switch to airplane mode
Anyone have luck with this? I want this guy to get the bounty....
snu69le said:
Anyone have luck with this? I want this guy to get the bounty....
Click to expand...
Click to collapse
I'm running Keyroot. Process seems to take around 3 hours. Still waiting.
No Luck, no matter how many times tried or length waited past 3 hours.
It continuously sat at "Increfing...." Nothing failed. Just sat there like it wasn't doing anything...
"Pushing root exploit to phone...
Push done!
Running chmod...
Chmod done!
Running exploit... This WILL take a while (about 3 hours or more)
uid=2000, euid=2000
Increfing..."
Going to keep trying though...
cynicalinsomniac88 said:
No Luck, no matter how many times tried or length waited past 3 hours.
It continuously sat at "Increfing...." Nothing failed. Just sat there like it wasn't doing anything...
"Pushing root exploit to phone...
Push done!
Running chmod...
Chmod done!
Running exploit... This WILL take a while (about 3 hours or more)
uid=2000, euid=2000
Increfing..."
Going to keep trying though...
Click to expand...
Click to collapse
In the OP's other thread, he said it could take 5+ hours. However, there should be a result if you wait long enough. I'll try it tomorrow too
I'll give it a try once my backup finishes.
GOOD LUCK!
zaurav said:
I'm running Keyroot. Process seems to take around 3 hours. Still waiting.
Click to expand...
Click to collapse
Unfortunately, it didnt work my 1st try:
Pushing root exploit to phone...
180 KB/s (100604 bytes in 0.544s)
Push done!
Running chmod...
Chmod done!
Running exploit... This WILL take a while (about 3 hours or more)
uid=2000, euid=2000
Increfing...
finished increfing
forking...
finished forking
caling revoke...
uid=2000, euid=2000
Unable to chmod /system/xbin: Read-only file system
failed to copy '.\su' to '/system/xbin/su': Read-only file system
Exception in thread "Root Thread" java.lang.ClassCastException: java.io.BufferedOutputStream cannot be cast to java.io.ByteArrayOutputStream
at me.peregrinex.keyroot.Root$1.run(Root.java:46)
Click to expand...
Click to collapse
I'm going to try again.
---------- Post added at 03:38 AM ---------- Previous post was at 03:36 AM ----------
BTW entire process took about 5.5 hours for me.
zaurav said:
Unfortunately, it didnt work my 1st try:
I'm going to try again.
---------- Post added at 03:38 AM ---------- Previous post was at 03:36 AM ----------
BTW entire process took about 5.5 hours for me.
Click to expand...
Click to collapse
If you are going to try again, please use the updated version, as it fixes some bugs.
But if your phone is 5.0.2, please try the PingPong version here.
PeregrineX said:
If you are going to try again, please use the updated version, as it fixes some bugs.
But if your phone is 5.0.2, please try the PingPong version here.
Click to expand...
Click to collapse
Okay. Redownloading. Thanks for letting me know.
I'm on 5.1.1 otherwise I'd have tried the other method. Does the error message I pasted provide any clue for you as to why it is failing?
---------- Post added at 03:48 AM ---------- Previous post was at 03:46 AM ----------
Trying with the v0.2now
zaurav said:
Okay. Redownloading. Thanks for letting me know.
I'm on 5.1.1 otherwise I'd have tried the other method. Does the error message I pasted provide any clue for you as to why it is failing?
Click to expand...
Click to collapse
Nope, all was as it should have been if the root process failed. This update should have fixed that last error though.
Do you get it？
zaurav said:
I'm running Keyroot. Process seems to take around 3 hours. Still waiting.
Click to expand...
Click to collapse
I'm trying it now.
EDIT:
I get this message repeated.
Pushing root exploit to phone
Push done!
Running chmod...
Unable to chmod /data/local/tmp/root. No such file or directory.
Chmod done!
Running exploit...This WILL take a while (about 3 hours or more)
/system/bin/sh: /data/local/tmp/root: not found
cannot stat ".\su": No such file or directory
Running exploit... This WILL take a while (about 3 hours or more)
/system/bin/sh: /data/local/tmp/root: not found
Related
Edited 12/30/11:
Thanks to everyone that helped put this together, and I'm glad people found it useful! However, this guide is now obsolete. I put it together before we could unlock the bootloader and get a permanent root. However, we now have a bootloader unlock, so there's a better way to get root. Please see this thread: http:// http://forum.xda-developers.com/showthread.php?t=1416836. I'll leave this guide here in case somebody has such an occasion to need only a temp root.
-----------------------------------------------------------------------------------------------------------------
Edited 11/11/11, 12:23 EST - V2 of Windows script - check for superuser.apk already installed
Edited 11/11/11, 14:42 EST - Linux/Mac script
Edited 11/11/11, 15:58 EST - V3 of Windows script - updated method for installing su binary to attempt to address it disappearing. Please let me know if the issue persists! (Linux script should be updated to V3 soon)
Ok, so I think we've gotten this process streamlined enough to make it easy, so I wanted to put together a step-by-step easy temproot for people who are confused. It will run zergRush to root your phone, then install busybox and the superuser app & binaries.
I've tested this on AT&T's Vivid, and it seems to work on the Canadian variant. Also, supposedly, if you're bootloader's unlocked, this should give you permroot.
I take no credit for actually developing most of this, I just packaged it up all nice and neat in an easy to run batch file. Both Windows & Linux/Mac versions are attached.
Thanks to:
Revolutianry for zergRush, ChainsDD/androidsu.com for SuperUser, stericson for busybox
arunp44, Jimmy273, DooMLoRD, and cyber_pete for some of the right commands
rpendrick for the Linux/Mac version
STEPS TO ROOT:
0. Install HTC Sync on your computer so that you'll have the proper drives
1. Download Vivid-Root.zip: Windows | Linux/Mac
2. Unzip somewhere on your computer
3. On your phone , enable USB Debugging (Settings > Applications > Development, check USB Debugging) & Unknown Sources (Settings > Applications, check Unkown Sources)
4. Connect your phone to the computer, make sure it's in Charge Only mode
5. Open the unzipped folder, double click RUNME.bat & Follow the prompts
6. Enjoy your root!
If you reboot your phone, just repeat steps 4-6.
Please let me know if you have any problems, questions, or concerns!
DISCLAIMER: I've tested this on my device and it works. However, i provide no guarantees or claim no responsibility for problems it may cause (however unlikely that may be). You know, the usual "please don't blame me for bricks...".
KNOWN ISSUES:
-Occasionally Superuser app won't recognize su binary even though phone has root access
-su binary disappears after a while (V3 attempts to fix this)
-zergRush method unmounts internal phone storage (/sdcard folder). Seems its still accessible from adb shell, and nothing seems wrong, but phone can no longer access it properly
Looks promising. Any possibility to repackage for linux and or Mac?
Sent from my HTC PH39100 using xda premium
drewdatrip said:
Looks promising. Any possibility to repackage for linux and or Mac?
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Absolutely! It'll just take me a little longer, as I only have access to windows machines at the moment. Perhaps later this afternoon I'll have the chance to port it to linux/mac.
Nice work, I just posted the manual version of this on the other temp root forum. Was going to start to automate but you beat me to it. I love it when there are several people all working towards a solution.
cyber_pete said:
Nice work, I just posted the manual version of this on the other temp root forum. Was going to start to automate but you beat me to it. I love it when there are several people all working towards a solution.
Click to expand...
Click to collapse
Yeah, I saw that. I actually have to thank you, because I was having one minor issue of it not recognizing the su binary, but your code got it working! So thanks!
bjg222 said:
Yeah, I saw that. I actually have to thank you, because I was having one minor issue of it not recognizing the su binary, but your code got it working! So thanks!
Click to expand...
Click to collapse
Team work, that's how we are going to get to perm root.
EDIT:
Just used your script, worked perfect. One suggestion. What do you think about adding a check for the SuperUser.apk and if it is already there, skip the install? I already have it installed and got the Failed message, might scare a few people. Anyway just a suggestion, great work.
Nice job man. This will def help out people new to the rooting world.
Question... If I use supercharger v6 to emprove my ram after I reboot will it still. E in effect?
Sent from my HTC PH39100 using xda premium
cyber_pete said:
Team work, that's how we are going to get to perm root.
EDIT:
Just used your script, worked perfect. One suggestion. What do you think about adding a check for the SuperUser.apk and if it is already there, skip the install? I already have it installed and got the Failed message, might scare a few people. Anyway just a suggestion, great work.
Click to expand...
Click to collapse
Sure, I'll work on that and get it up in a bit.
tacotino said:
Question... If I use supercharger v6 to emprove my ram after I reboot will it still. E in effect?
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Having never used the app, I couldn't tell you. But typically on reboot, you lose everything root-related, so my guess would be no.
In-app root
Is anyone working on an in-app temp root app (z4root anyone?)
If I change LCD density while temp rooted, will it survive reboot?
I really am considering this temp root cause I find bloatware annoying.... But if I can switch lcd density while im at it, that will make three decision much easier
Sent from my HTC Vivid using Tapatalk
How long should this process take?? Mine is just showing *daemon started successfully* for a few minutes.
ronj1986 said:
How long should this process take?? Mine is just showing *daemon started successfully* for a few minutes.
Click to expand...
Click to collapse
Should take a few seconds, less than a minute overall.
---------- Post added at 06:55 PM ---------- Previous post was at 06:52 PM ----------
After running this I tried opening Titanium Backup and it said no root. I did try earlier old temp root method without success, could that be the reason?
{
"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"
}
Well it is a good sign that we have temp-root so quick now HTC just needs to stop dragging their feet a bit and get this bootloader unlocked.
My device driver "did not install properly", maybe that's what's causing the *daemon started successfully* Ronj is having
I am hoping installing HTC Sync will fix hat little issue.
It is. I installed HTC Sync, and the problem went away
ronj1986 said:
It is. I installed HTC Sync, and the problem went away
Click to expand...
Click to collapse
figured... the Dell streak had a step like that too.
I am unable to install Titanium Backup:-(((
For those of you that have temp root working, are you losing root after a short amount of time? I keep losing the SU binary, root is still there but I have to repush SU. Really strange. Does anyone know if this is just the nature of temp root or is there something I can do to fix that?
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
The SoupKit
{
"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 SoupKit? At it's heart, SoupKit is for those who are tired of messing around with Windows and are ready to do try something that works. It was created to be "sort of" modular in that after the ADB installer has been installed, other Linux scripts can be installed and run from the command line by just typing the name of the script and without worrying about changing directories or dealing with permissions. It's intended to make the transition from Windows to Linux for Android a little bit easier.
How does it work?
The SoupKit ADB Installer --- FOR ALL KINDLE FIRES
This puts everything where it needs to be, installs any necessary dependencies, installs drivers, configures Linux to run adb and fastboot commands, puts the SoupKit in your $PATH and cleans up after itself, all while taking a fraction of the space needed for the Android SDK. What this means for you is, you will be able open any terminal window and start entering adb or fastboot commands immediately. There's no need to change directories, add sudo commands or certain operators that are confusing to command line newbies ( ./ ). You can enter commands just as you see them in tutorials. No more worrying about “ADB Offline”, “Status Unknown” or “List of devices attached ????????????????”. This alone can make a huge difference for anyone having Kindle Fire problems that can't be fixed in Windows or those who are overwhelmed by the technicalities of configuring Linux for Android.
What you need:
First, you need Linux. Don't worry, it's not as bad as you may think.
Luckily, all Linux distros are free to download and install on your computer. It can also be booted from a USB flash drive so you don't have to wipe out your current OS (although you probably should anyway). You can use a VM, but the only VM that I've found that can detect the Kindle Fire in fastboot mode is Parallels. Vmware won't cut it, and VirtualBox sure as hell won't cut it so don't waste your time with them if you ever need to do anything in fastboot (if you're bricked, you need fastboot).
Probably the best method to get Linux running for a new user is by setting up a Linux LiveUSB.
I'm not going to teach you how to set up a Linux LiveUSB, but there are plenty of FREE programs out there that will not only create a Linux LiveUSB for you, but will download your choice of distro as well, and all you need is a USB flash drive (preferably 8GB or larger). A Google search of “Linux LiveUSB” will offer plenty of choices, although, PendriveLinux seems to be a favorite among most. Just be sure to add plenty of “persistence” (1 or more gigabytes) or you will lose everything every time you reboot. And the better quality of flash drive you can use, the better it will be in the long run. Some flash drives just don't do well and can cause some file system corruption over time (not something you want to be dealing with while you're having Kindle Fire problems).
You'll also have to figure out how to boot your computer from a USB. Check your computer's BIOS manufacturer website for instructions on how to do this.
If you're using a LiveUSB, there is no root/sudo password, just hit enter.
Do not use a USB 3.0 port
Once you have Linux installed and booted, you need to make sure your Internet is working. It may take some configuration on your part but it is necessary for the SoupKit to install properly. Luckily, once you have an Internet connection in Linux, the hard part is over.
Don't put the SoupKit.zip on the USB drive before creating the LiveUSB. Instead, use the web browser to navigate to this page and download it once you have Linux running and your Internet connected. Once it's downloaded, you'll likely find it in your Downloads folder.
SoupKit has been tested extensively on all the latest versions of Ubuntu and Mint, but it hasn't really been tested on anything outside of that. Try other distros if you will, but be warned.
To install:
Right-click the “SoupKit.zip”, select “Extract here” open the SoupKit folder and follow the instructions in the README.
Credits:
Don't worry. I didn't forget about you guys. I'll finish this when I have time. In the meantime, you know who you are, and thank you.
Is that all?
NOPE. What SoupKit would be complete without a little something to go with it? SEE POST #2
Due to recent updates, I've decided to remove the option to install Hashcode's 2nd bootloader. There are too many areas where things can go wrong so I think it would be best to let the user follow the small handful of instructions in the 2nd bootloader thread to get it done. IMO, it is not worth the risk to rely on the user to make sure a downgraded stock bootloader is installed before running the script. Plus I think using a script toinstall the downgraded bootloader gives users a false sense of safety in what is potentially very dangerous to do.
ROOT PLUS for 2nd Generation Kindle Fires
That's right. This works for ALL 2nd generation Kindle Fires.
What does it do?
The screenshot above should answer that question pretty quickly.
What do you need to know?
Since Hashcode's bootloader hack is device specific, you must download the version for your device. Each one has the exact same script but the stack, boot and recovery images are different for each particular device. You must have the SoupKit installed for this to work properly. It installs in the same way as the SoupKit; unzip, double click, run in terminal, blah blah.
Make sure you have ADB enabled under “Security” in the settings.
Anything else?
At any point after installation, if you need to run the utility again, just type "rootplus" in the terminal.
What's next?
I have a few more things in store for you guys and they will all be made for the SoupKit. As packages are installed, just type the name of the package in any terminal to launch them at any point (hence "modular"). Everything will be easy to install, easy to launch, and new user friendly.
Don't be skerrd. Move out of your comfort zone a little and give Linux and SoupKit a try. I'm sure you won't be disappointed.
Credits:
* Bin4ry - of course, for providing the root exploit
* Dees_Troy - for Team Win Recovery
* prokennexusa and his team - for testing this out on all of the second generation devices
* Thepooch - for extensive testing and always being there to lend a hand
Downloads:
SoupKit - http://d-h.st/PbX
RootPlus for all Kindle Fires - http://d-h.st/jOe
Changelog:
04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons. There is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon.
03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error
03-16-2013 - Bugfix: (RootPlus)
* Fixed issue with permissions on the rootplus script
03-10-2013 - Update: (RootPlus)
* Added extra safety measures, including MD5 check on 2nd bootloader install
02-23-2013 - Initial release
I actually wish I needed this because god damn this is a sexy piece of kit.
Thanks soup
Sent from my Amazon Kindle Fire2 using xda app-developers app
Awesome. So glad to see the kf1 devs working for us over here!
I'll probably never need this, but there are MANY who will find this useful.
Thanks soupmagnet!
--
Sent from my Kindle Fire 2, CM 10.1
Wilkinsss said:
this is a sexy piece of kit.
Click to expand...
Click to collapse
Oh, I see what you did there...
soupmagnet said:
Oh, I see what you did there...
Click to expand...
Click to collapse
Well I don't need it I have adb and fastboot running fine on linux already but I still downloaded it anyways, just because I can.
Update 3-10-2013: Added extra safety measures, including MD5 check on 2nd bootloader install
I seem to have installed the soupkit correctly, I followed the instructions. I also installed the root plus in the same manner, but when it installs it just disappears. When I type rootplus in terminal it tells me "permission denied"
It also gives me command not found when I try to open soupkit.sh
thanks
2strokenut said:
I seem to have installed the soupkit correctly, I followed the instructions. I also installed the root plus in the same manner, but when it installs it just disappears. When I type rootplus in terminal it tells me "permission denied"
It also gives me command not found when I try to open soupkit.sh
thanks
Click to expand...
Click to collapse
That sucks...I'll have to fix that. In the meantime you can enter the following in terminal to fix the permissions:
Code:
sudo chmod a+x ~/bin/SoupKit/files/rootplus
Then you should be able to start it by entering "rootplus" in the terminal with no problem.
Sorry for the inconvenience.
[Edit:] There have quite a few downloads since the last update. Has anyone else had this problem?
soupmagnet said:
That sucks...I'll have to fix that. In the meantime you can enter the following in terminal to fix the permissions:
Code:
sudo chmod a+x ~/bin/SoupKit/files/rootplus
Then you should be able to start it by entering "rootplus" in the terminal with no problem.
Sorry for the inconvenience.
[Edit:] There have quite a few downloads since the last update. Has anyone else had this problem?
Click to expand...
Click to collapse
That worked like a charm! Thanks for all you do!
---------- Post added at 02:35 PM ---------- Previous post was at 02:11 PM ----------
I hate to be such a noob, but, I got the thing rooted and now trying to install the bootloader and TWRP, this is as far as I have gotten. Hasn't done anything in about 10 minutes. I've toggled ADB.
Verifying MD5 Checksum...
blaze-stack.img: OK
Checksum matched
Installing stack...
95 KB/s (4096 bytes in 0.041s)
0+1 records in
0+1 records out
4096 bytes transferred in 0.002 secs (2048000 bytes/sec)
Rebooting...
< waiting for device >
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
I exited the terminal and re-ran option 6, this is what it gives me now:
blaze-stack.img: OK
Checksum matched
Installing stack...
93 KB/s (4096 bytes in 0.042s)
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
failed on '/system/etc/install-recovery.sh' - No such file or directory
Rebooting...
< waiting for device >
There may be something off with the timing. In original testing on my KFHD 8.9, that was caused from the script entering the command to reboot too fast. I had the script pause for a second or two before rebooting which seemed to help (or I thought I did). I'll look into it a little further to see if I can make it work better. The error you get on the second time you run the script is because the first time you ran it, that file was renamed so it wouldn't exist the second time around.
[Edit:] Just hold the power button to shut down and then reboot while the script is sitting at "waiting for device"
Hi Soup,
I installed soupkit, I installed rootplus. The terminal just disappears but I assume it installed correctly. What I am trying to figure out is this:
Make sure you have ADB enabled under “Security” in the settings.
I am running Ubuntu Precise. I don't see anything under Settings about Security or about enabling ADB. Can you help me out a bit? Thaks!
[Edit] I had to: sudo chmod a+x ~/bin/SoupKit/files/rootplus too to get a terminal window on rootplus. But it doesn't do anything when I press 1.
[Edit again] Nevermind... was stupid to think that the Security change was in Ubuntu, I found it on the KF.
empoy78th said:
Hi Soup,
I installed soupkit, I installed rootplus. The terminal just disappears but I assume it installed correctly. What I am trying to figure out is this:
Make sure you have ADB enabled under “Security” in the settings.
I am running Ubuntu Precise. I don't see anything under Settings about Security or about enabling ADB. Can you help me out a bit? Thaks!
[Edit] I had to: sudo chmod a+x ~/bin/SoupKit/files/rootplus too to get a terminal window on rootplus. But it doesn't do anything when I press 1.
[Edit again] Nevermind... was stupid to think that the Security change was in Ubuntu, I found it on the KF.
Click to expand...
Click to collapse
Yeah, sorry about that...I'm working to get the permissions fixed now so I can upload a new working version. Barring distractions (yeah right), I should have a new one up within the hour. If nothing else, it will be fixed by the end of the day.
soupmagnet said:
Yeah, sorry about that...I'm working to get the permissions fixed now so I can upload a new working version. Barring distractions (yeah right), I should have a new one up within the hour. If nothing else, it will be fixed by the end of the day.
Click to expand...
Click to collapse
Thanks soup! Just to give you an update (although I think you are working on this already), when I press 1 on root plus, I end up on <waiting for device> although the KF2's finished rebooting. I tried the previous suggestion about holding down the power button and re-launching rootplus, but it didn't resolve it.
I will gladly test your new version. Thanks again!
---------- Post added at 11:39 AM ---------- Previous post was at 11:22 AM ----------
empoy78th said:
Thanks soup! Just to give you an update (although I think you are working on this already), when I press 1 on root plus, I end up on <waiting for device> although the KF2's finished rebooting. I tried the previous suggestion about holding down the power button and re-launching rootplus, but it didn't resolve it.
I will gladly test your new version. Thanks again!
Click to expand...
Click to collapse
Another question if I may:
When you have shell updates, does it use the same folder on the same partition? I am not quite good at Linux yet, so cleaning up previous installations is not my strength at all. Thanks!
empoy78th said:
Another question if I may:
When you have shell updates, does it use the same folder on the same partition? I am not quite good at Linux yet, so cleaning up previous installations is not my strength at all. Thanks!
Click to expand...
Click to collapse
Assuming I understand you correctly,
I write the install script in such a way that updating to a newer version simply replaces what already exists, so there's no need to uninstall anything.
3-16-2013: Fixed issue with permissions on the rootplus script
soupmagnet said:
Assuming I understand you correctly,
I write the install script in such a way that updating to a newer version simply replaces what already exists, so there's no need to uninstall anything.
Click to expand...
Click to collapse
You understood it. Good to know. Thanks!
soupmagnet said:
3-16-2013: Fixed issue with permissions on the rootplus script
Click to expand...
Click to collapse
Do I download both soupkit and rootplus for updates? Sorry for the noob question.
In rootplus, options 1 and 5 worked for me. However, on option 6, I stay at <waiting for device>. Done it twice and also held the power button to no avail.
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.
I booted up my D415 this morning and found a new OTA was ready to install. It was around 275MB. I haven't installed it because I'm running the D415c build rooted with TWRP recovery. I can't seem to find a changelog on T-Mobile or LG's site regarding this new update. Other than loosing root, can anyone tell me what this huge update is about?
Apparently it is an exploit fix. It disables the ability to root with Towelroot.
I ran the update.... So I'm stuck with a stock ROM.
Sent from my LG-D415 using XDA Free mobile app
275mb is a large patch for an exploit.
What is an exploit fix? Do you think that there will be a way to root the phone after installing this update? I haven't installed it yet. I want to root my phone in the future.
It's a rebuilt and repackaged ROM in its entirety. How much is different isn't clear.
Sent from my LG-D415 using XDA Free mobile app
I wonder if only those who were rooted got the OTA? My wife had the same phone but unrooted and she didn't get the OTA yet.
barcodelinux said:
I wonder if only those who were rooted got the OTA? My wife had the same phone but unrooted and she didn't get the OTA yet.
Click to expand...
Click to collapse
I'm rooted and didn't receive the update.
Rooted and haven't received any thing either.
Sent from my LG-D415 using XDA Free mobile app
What about recovery? Maybe it runs an md5sum on the recovery partition? Just tinkling out loud here
D1358531 said:
I'm rooted and didn't receive the update.
Click to expand...
Click to collapse
I got it but lost root...kind of. The binaries are still there, and booting in to download mode still warns of root...but I can't get anything to recognize is other than Superuser by ChainsDD, and even that is of no use. FWIW permissions on /system/xbin/su are 755...so IDK maybe something can be done to get it working. I posted elsewhere that the new update brings no changes other than re-locking and breaking root, but I was wrong; it also brings knock code as a form of pattern unlock.
---------- Post added at 04:03 PM ---------- Previous post was at 03:46 PM ----------
jb3p76 said:
DK maybe something can be done to get it working.
Click to expand...
Click to collapse
FWIW to any observers more knowledgeable than I:
Code:
[email protected]:~$ adb shell
[email protected]:/ $ /system/xbin/su
1|[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]:/ $ su
1|[email protected]:/ $ dd if=/dev/block/platform/msmsm_sdcc..1/by-name/laf of=/storage/external_SD/laf.img
/dev/block/platform/msm_sdcc.1/by-name/laf: cannot open for read: Permission denied
It appears to take root for the duration of the command to do so, but then I am dropped back to a normal shell on the next prompt.
I could use a taste of lollipop sometime soon.
This update enables free gogo flight texting and knock code pattern.
Sent from my SM-N900T using XDA Premium App
jb3p76 said:
I got it but lost root...kind of. The binaries are still there, and booting in to download mode still warns of root...but I can't get anything to recognize is other than Superuser by ChainsDD, and even that is of no use. FWIW permissions on /system/xbin/su are 755...so IDK maybe something can be done to get it working. I posted elsewhere that the new update brings no changes other than re-locking and breaking root, but I was wrong; it also brings knock code as a form of pattern unlock.
---------- Post added at 04:03 PM ---------- Previous post was at 03:46 PM ----------
FWIW to any observers more knowledgeable than I:
Code:
[email protected]:~$ adb shell
[email protected]:/ $ /system/xbin/su
1|[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]:/ $ su
1|[email protected]:/ $ dd if=/dev/block/platform/msmsm_sdcc..1/by-name/laf of=/storage/external_SD/laf.img
/dev/block/platform/msm_sdcc.1/by-name/laf: cannot open for read: Permission denied
It appears to take root for the duration of the command to do so, but then I am dropped back to a normal shell on the next prompt.
Click to expand...
Click to collapse
There's a typeo in your dd commands "if=" parameter.
Code:
if=/dev/block/platform/msmsm_sdcc..1/by-name/laf
should be
Code:
if=/dev/block/platform/msm_sdcc.1/by-name/laf
Although from DD's output, it appears the command ran correctly
Also, if "su" is working as it should, your terminal command prompt should have changed from "$" to "#" after issuing the su command. Which it appears it hasn't.
Thanks for pointing that out. I'll have to try it again; not sure if I typed it like that or messed up the copy/paste because of line-wrap on the limited column width when I am in adb shell. If this doesn't work out I'm going to try flashing back to kdz for version c. I got sick of playing around with windows being in the way, so here's hoping the flash tool runs with wine!
Sent from my LG-D415 using XDA Free mobile app
Just discovered a significant bug in the update: Video recording with stock app is broken. Switching to the video function works OK, but then trying to start recording fails with a toast saying "Unable to record video during call."
What call?
I tried clearing data for the app, force stop, turned off WiFi calling, rebooted, etc etc. Nothing helped. Google camera works fine though, unless you want to HDR.
{
"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 think LG makes the worst Android software.
I am rooted and i received the update notification but will it ruin my custom recovery ? Can i flash SuperSU zip after the update to restore root ?
If yes , then how to disable the update notification in such a way that google services wont drain my battery if uncheck system updates in DisableServices app?
lordnihilusmd said:
I think LG makes the worst Android software.
I am rooted and i received the update notification but will it ruin my custom recovery ? Can i flash SuperSU zip after the update to restore root ?
If yes , then how to disable the update notification in such a way that google services wont drain my battery if uncheck system updates in DisableServices app?
Click to expand...
Click to collapse
It's my understanding that this update fixes the exploit used to root the device. To my knowledge, there is no way to ROOT the new update. Yes, it will remove your custom recovery. No you won't be able to flash SuperSU after the update. I cannot answer your last question as I'm not on stock and haven't been for many months.
Question, is it safe to take update even though rooted with twrp recovery, i know you lose root but worried about it messing up my phone, i see some people posting it did mess up theirs.
Until there is a reliable way to root it, I wouldn't take it. I don't need in-flight texting that bad.
We have 3 lg d415's in the house. 1 rooted w/custom ROM, 1 rooted with stock and 1 completely stock phone. Only the rooted with stock ROM received notice of an update. Luckily he did not take it, now to disable the updater somehow. Any help would be great, he refuses a custom ROM.
I do find it odd that only the rooted phone with stock ROM got the update. I figured the 100% stock non-rooted phone would have too.