Database Develop

[HOW-TO] [PICTURES] ADB Working On the Google Chromecast

Hey everyone,
I got the Android Debugging Bridge (ADB) working on the Google Chromecast.
A video is currently uploading. A how-to will follow shortly after.
Videos have been uploaded!
Thanks!
Part 1:
http://www.youtube.com/watch?v=vYICywxdUfM
Part 2:
http://www.youtube.com/watch?v=mjedUnv7tkM
Logcat made in Part 2:
http://pastebin.com/WZtHzrak
[Prerequisites]
A Rooted Chromecast (I recommend tvall's image..Here).
PuTTY or another Telnet Client
Android SDK
Active internet connection
Chromecast's IP Address
[How To]
Full Gallery here: http://imgur.com/a/ORiL0#0
Assuming you already have a rooted Chromecast and it is ON;
Open your preferred Telnet client, I prefer PuTTY.
{
"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"
}
Type in your Chromecast's IP Address and choose telnet as the connection type (I won't tell you how to get this, hint: check your router).
Click open and you should now see a black terminal window.
Type:
Code:
mount -o rw,remount /
and press enter
Then type:
Code:
setprop service.adb.tcp.port 5555
and press enter
Next type:
Code:
busybox vi default.prop
Press the letter 'i' on the keyboard for 'insert'
Use the arrow keys on your keyboard to navigate.
Change:
Code:
ro.secure=1
to
Code:
ro.secure=0
Change:
Code:
ro.debuggable=0
to
Code:
ro.debuggable=1
Press the 'ESC' key on your keyboard so VI goes back to accepting commands
Type ':wq' without the quotes and with the colon....Press enter.
You should now be back at the / # prompt..
Type
Code:
busybox wget http://goo.gl/TnbG99 -O adbd
and press enter
Type
Code:
chmod 777 adbd
and press enter
Type
Code:
./adbd &
It may not say anything and drop back to the prompt, this is normal
Type
Code:
ps | grep 'adbd'
and press enter to make sure adbd is running
Open a command prompt and cd to the SDK's platform-tools folder
Your path will be different than mine.
Type
Code:
adb devices
and press enter
It will probably not list any devices; this is normal. We just need to tell adb what device to connect to over wifi.
Type
Code:
adb connect X.X.X.X
where X.X.X.X is the IP Address of your Chromecast
Press Enter
Should say
Code:
Connected to X.X.X.X:5555
where X.X.X.X is the IP of your chromecast.
Type:
Code:
adb devices
and press enter
It should list your chromecast by its IP Address.
Type:
Code:
adb shell
and press enter
You should be greeted with a # prompt.
Congratulations! You now have ADB access to your chromecast.
Please note that this DOES NOT survive across reboots.

Reserved
Update:
[08/15/13 2:40PM CST] Videos Posted
[08/16/13 2:05PM CST] How-To Posted with Pictures

Awesome!

Just to clarify, this really doesn't do much yet.
As of right now you can't make persistent changes to the filesystem, because they revert after a reboot.
Heck you can't even remount the /system partition as RW at this point. Not sure why, but not too worried about it at the moment

/system is squashfs, a compressed readonly fs. Not difficult to modify, but requires reflashing the while partition (like gtvhackers image)
Sent from my Evo V 4G using Tapatalk 2

tvall said:
/system is squashfs, a compressed readonly fs. Not difficult to modify, but requires reflashing the while partition (like gtvhackers image)
Sent from my Evo V 4G using Tapatalk 2
Click to expand...
Click to collapse
Awesome. I'm assuming it just unpacks the system after every reboot, I mean since the system seems to revert to not having any added items unless its in the image tahat was flashed?

death2all110 said:
Awesome. I'm assuming it just unpacks the system after every reboot, I mean since the system seems to revert to not having any added items unless its in the image tahat was flashed?
Click to expand...
Click to collapse
You can't modify the filesystem without reflashing it. Squashfs is read only.
Sent from my Evo V 4G using Tapatalk 2

tvall said:
You can't modify the filesystem without reflashing it. Squashfs is read only.
Sent from my Evo V 4G using Tapatalk 2
Click to expand...
Click to collapse
Right. Sorry. Long day.
Anyway, is there a way to modify the boot image?

OP Updated

Thx m8

great!
adb push works well,
I suppose you could make persistent changes to /cache (this partition is mounted rw!)

Greetings:
When I attempt to download "busybox" from "Goo", it comes back with: server returned error: HTTP/1.1 404 not found !!
Any input/help is much appreciated.
Thank you.

samteeee said:
Greetings:
When I attempt to download "busybox" from "Goo", it comes back with: server returned error: HTTP/1.1 404 not found !!
Any input/help is much appreciated.
Thank you.
Click to expand...
Click to collapse
@samteeee Try it now. url should be fixed.

Hi,
i have a question, it's possible to have adb with chromecast if this one is not root?
Thanks,

labiba said:
i have a question, it's possible to have adb with chromecast if this one is not root?
Click to expand...
Click to collapse
Sorry, no.

Hello,
i don't now if i'm in the good forum to ask for help.
I have a GTV100 de netgear that i routed. after a problem of the remote i did a hard reset and after my device don't work.
in the beginin i have the trace in the uart that all go fine, But now i have the message :
NAND: Read mkbootimg header error!
FATAL ERROR! There is no bootable image on this machine!
tbdzz---- Img_Ld_And_Start error! Spinning now!
[109]I(SM): SM starts, enters warmup state!
[112]I(SM): begin to run tasks
there is any solution to write another bootable image?
thanks for your help

ChromeCast mapping memory
Hello,
I have a chromecast and i want to show its mapping memory.
the objectif is to verify when the chromecast play a video if its buffer is secure or not ?
and how can where the kernel do the allocation for memory?
can you help me please ?
thanks :good:

When I attempt to download "busybox" from "Goo", it comes back with: server returned error: HTTP/1.1 404 not found !!
Any input/help is much appreciated.

[GUIDE] [NEW] Root All L90 Varients with Latest updates [EASY]

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.

L90 D415 New update 12/13/14

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.

[BETA] [G890A] KeyRoot v0.2 [DOESN'T WORK] [USE OTHER THREAD]

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.​KeyRoot​By 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

Disable System Update ?

Last night I downgraded from B360 to B185 . Everything is very good but I always get some notification about the new B360 version which I downgraded from . I disabled system update notifications , cleared data/cache , disabled access to Phone , internet , wi-fi and etc . And after all that I still get update screen to allow update to use phone permissions and etc . I want to disable/remove system update . Is it possible without root ?

yes..
you can skip skip at the Setup screen (after clean flash or full wipe).. and cut the Internet once posible.
Then go to System, System Update 3 poinst above and Update settings. Then: Dissable Auto update and AutoDownload over Wifi.
And you will be let alone.

gxg said:
yes..
you can skip skip at the Setup screen (after clean flash or full wipe).. and cut the Internet once posible.
Then go to System, System Update 3 poinst above and Update settings. Then: Dissable Auto update and AutoDownload over Wifi.
And you will be let alone.
Click to expand...
Click to collapse
That worked . Thanks a lot !

Revengebg said:
That worked . Thanks a lot !
Click to expand...
Click to collapse
You're welcome.
But frankly ... I'll let Oreo for a while. One new update is on the way.. and also .. I belive soon 8.1 will come.

rooted device
if you users want to stop the system update notification u just need an rooted phone and this tool
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

murasio3 said:
if you users want to stop the system update notification u just need an rooted phone and this toolView attachment 4744084
Click to expand...
Click to collapse
Hi. What's the tool name please?
I feel like smashing the phone every morning.

Is there a way to disable system update without root yet? I cant find package disabler on the app store. I have a note 8 . Can somone pplease help

You don't need root nor TWRP.
You must enable hidden Developer options in Settings, and enable there ADB debugging over USB.
Install ADB on the PC - search on XDA for Minimal ADB and Fastboot tool
Use the adb command from PC
Code:
adb shell pm disable-user com.huawei.android.hwouc
In Settings, Apps, enable Show system services and you will see that System update is disabled - when you want it back, just enable
Use apps like AppInspector or DevCheck (from Playstore) to find package name for any (system) app you want to disable

zgfg said:
You don't need root nor TWRP.
You must enable hidden Developer options in Settings, and enable there ADB debugging over USB.
Install ADB on the PC - search on XDA for Minimal ADB and Fastboot tool
Use the adb command from PC
Code:
adb shell pm disable-user com.huawei.android.hwouc
In Settings, Apps, enable Show system services and you will see that System update is disabled - when you want it back, just enable
Use apps like AppInspector or DevCheck (from Playstore) to find package name for any (system) app you want to disable
Click to expand...
Click to collapse
It works for now.
Huawei P30 PRO.
Thank you.