Hi guys!
Update: Posted the complete guide! Follow it carefully. Read 2-3 times before doing anything.
I am able to temporarily root LG K420 DS w/Android 6.0.
What does it mean for other models of LG K10? You can root your phone if your phone has dirtycow vulnerability.
Debugging Tools:
You need android-ndk installed in your computer.
(1) DirtyCow Vulnerability Test Tool: Download here (Ubuntu only)
How to run it: sudo ./vul_test.sh.x
(2) If you don't have the android ndk compiler installed.
Phone Info Data Tool: Click here (Ubuntu Only)
How to run it: sudo ./phone_info.sh.x
Send me the info.data file it produced. It is encrypted. I will analyse it and reply you back.
Click to expand...
Click to collapse
COMPLETE these steps before continuing: Click Here
Download this dirtyc0w temporary root shell tool: Click Here
Click to expand...
Click to collapse
(1) Unzip the root_tool.zip
(2) Connect your phone. Make sure you have "USB Debugging" enabled in "Developer Options".
(3) Run run_for_arm_devices.bat file. Wait for it to dirtc0w the shell.
(4) Type "id". You get something similar to this screenshot:
{
"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"
}
(5) Type "cd data/local/tmp".
(6) Now run "./a.out /init ./init". It replaces the original init file with my patched init file. (But I tried it many times, in Android 6.0, the shell context is not enough to replace init. While in Android 5.1.1, I could replace the patched init but restarts just after replacing the original init with my patched init. This time it was toolbox context).
(7) Open another command window. Type "adb logcat". Look for audit messages that the patched sepolicy is replaced with your phone's sepolicy.
-----------------------------------------------------------------
Notes:
(1) My Phone's Security Patch : 2016-10-01.
(2) The security patches from December 2016 & January 2017 can't use this root method because "dirtycow" is patched. Will post a detailed guide on what you can do if you upgraded to the latest update for your phone.
If you have already upgraded to a newer version having dirtyc0w patched, flash a ROM which predates to November/December. I flashed a ROM having security patch date has mentioned above!
(3) The root is just limited to deleting few files and viewing other folders inside '/'. It is because of SELinux Enforced. I patched the init and sepolicy file. Thanks to @matteogeniaccio for helping me out with patching.
(4) A bonus for MTK owners! You need not unlock bootloader and install TWRP and achieve "ROOT". This method can help you achieve root without unlocking bootloader and without losing warranty!
as MTK owner this news brings me happiness but how is the real question here
You made my day brother but I have already updated to January security patch. Should I be to install Marshmallow?
Kazryu said:
as MTK owner this news brings me happiness but how is the real question here
Click to expand...
Click to collapse
Wait for the details bro I am working on it!
sammessi10 said:
You made my day brother but I have already updated to January security patch. Should I be to install Marshmallow?
Click to expand...
Click to collapse
Wait for the details.
This is awesome, I'm glad I left my K425 variant sitting disconnected from the world.
It's still on the 2016-09-01 security patch, software v. K42511i.
I'll gladly experiment if you need one, it's the crap phone I grabbed when I started service before my V20 got unlocked from T-Mo, so if I end up without it, no big deal.
I shall sit here waiting patiently, as I'm sure many of has have been doing for a while. :fingers-crossed:
botenredwolf said:
This is awesome, I'm glad I left my K425 variant sitting disconnected from the world.
It's still on the 2016-09-01 security patch, software v. K42511i.
I'll gladly experiment if you need one, it's the crap phone I grabbed when I started service before my V20 got unlocked from T-Mo, so if I end up without it, no big deal.
I shall sit here waiting patiently, as I'm sure many of has have been doing for a while. :fingers-crossed:
Click to expand...
Click to collapse
Sent you a message.
entonces solo el modelo ds trae MTK o cuales dispositivos lo traen?
en mi caso mi modelo es k430y
chemaesquivel88 said:
entonces solo el modelo ds trae MTK o cuales dispositivos lo traen?
en mi caso mi modelo es k430y
Click to expand...
Click to collapse
No matter which ever phone it is it is going to work.
I got the lg ms428 (metro pcs)
It will work?
---------- Post added at 02:51 AM ---------- Previous post was at 02:49 AM ----------
Tbh I'm looking forward to this, finally some great news and thanks for ure hard work pvineeth97
ItzTropic said:
I got the lg ms428 (metro pcs)
It will work?
---------- Post added at 02:51 AM ---------- Previous post was at 02:49 AM ----------
Tbh I'm looking forward to this, finally some great news and thanks for ure hard work pvineeth97
Click to expand...
Click to collapse
It does'nt matter which ever phone it is. Its important that your Security-Patch-Date is not older than November.
we have in lg g4 forum need you bro
Does this phone e happen to have a y similarities to the LG Tribute HD? I'm just curious if this will work on that phone as well. Those guys have been trying to find a root method for so long now! Thanks in advance for any answers.
Chief_Nodnarb said:
Does this phone e happen to have a y similarities to the LG Tribute HD? I'm just curious if this will work on that phone as well. Those guys have been trying to find a root method for so long now! Thanks in advance for any answers.
Click to expand...
Click to collapse
This root method is based of Linux Kernel vulnerability not on any phone. If your phone is not patched with dirtycow then you can root it.
pvineeth97 said:
This root method is based of Linux Kernel vulnerability not on any phone. If your phone is not patched with dirtycow then you can root it.
Click to expand...
Click to collapse
pvineeth97 said:
It does'nt matter which ever phone it is. Its important that your Security-Patch-Date is not older than November.
Click to expand...
Click to collapse
How can I check if my phone is not patched with dirtycow or if my Security-Patch-Date is not older than November? With X-ray or Drammer perhaps or how?
If it's phone independent, would the same process and files that worked when I blew open my V10 (H901)/V20 (H918) work? Could fastboot and any related binaries/scripts also then be injected in somehow to allow for the bootloader to be unlocked? Also, my V10 had the 12-01-2016 patch and still let me in, unsure if that means much or not, or if I'm just bat sh*t crazy.
unknown404 said:
How can I check if my phone is not patched with dirtycow or if my Security-Patch-Date is not older than November? With X-ray or Drammer perhaps or how?
Click to expand...
Click to collapse
Compile this: https://github.com/timwr/CVE-2016-5195
make root
Type id when you see the shell.
Output should be similar to this: uid=0(root) gid=0(root) groups=0(root),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),3009(readproc) context=u:r:shell:s0
botenredwolf said:
If it's phone independent, would the same process and files that worked when I blew open my V10 (H901)/V20 (H918) work? Could fastboot and any related binaries/scripts also then be injected in somehow to allow for the bootloader to be unlocked? Also, my V10 had the 12-01-2016 patch and still let me in, unsure if that means much or not, or if I'm just bat sh*t crazy.
Click to expand...
Click to collapse
It depends on which method you are using. If that method is replacing init and sepolicy, you need to patch it for your own phone. Other phone's init and sepolicy might not work for your phone.
pvineeth97 said:
It depends on which method you are using. If that method is replacing init and sepolicy, you need to patch it for your own phone. Other phone's init and sepolicy might not work for your phone.
Click to expand...
Click to collapse
Will this ever enable us to remove preinstalled bloatware on our phones? What exactly is this root method useful for, and how limited it is really?
Fobos531 said:
Will this ever enable us to remove preinstalled bloatware on our phones? What exactly is this root method useful for, and how limited it is really?
Click to expand...
Click to collapse
It is limited to shell context. I tired replacing init in Android 6.0 it was not allowing me to dirtycow it. But when I tried replacing it in Android 5.1.1 the phone restarted.
Related
Hi!
This is the newest root method for LG lollipop devices.
Try this method if the original guide or the original one-click guide don't work for you.
Features:
This is a script for Send_Command.exe. Newest LG stock roms hate shell scripts.
With a trick, I found a new way to remount /system in new roms as read-write.
It will install SuperSU without flash nor override any device partition (means: no TWRP nor kitkat stack bootloader in this script).
Tested with LG G3 D855P (20B). But may work with others LG lollipop devices.
Advises:
This method is for lollipop ONLY!
Don't try to run this script if your device is already rooted!
TRY AT YOUR OWN RISK!
Pre-requisites:
LG drivers installed.
A lollipop stock rom.
Unencrypted device.
Usb cable.
Confirmed devices:
LG G2
D802 (30D)
D805 (30A)
LG G3
D850 (21Q 21R)
D851 (20E 20G)
D852 (20F 20G)
D855 (20G 20H 20I 20M 20P 20S 20T 20U 21A)
D855K (20F)
D855P (20B 20C)
D858HK (20D)
F400K (20I 20N)
F460S (20M)
VS985 (24B)
LG GPAD
8.0 V490 (20A)
At the moment, not working with:
LG G3
AS990 (20A)
F460K (20J)
LG G4
H815
H815P
My device isn't in the "Confirmed devices" list. Can I try anyway?
Since you are using lollipop, there is no big risk for your device.
But, in the worst case (if your device doesn't boot), you can enter in Download Mode and flash your rom again using the LG Flash Tool. And with the "Normal Flash" option you won't lose any personal data in your device.
Using this root method, there is *NO RISK* (in theory) of your device lose the Download Mode. So, go ahead and try it! And please, don't forget to tell us your feedback! :fingers-crossed:
Ok.... Let's go!
First method: Using the easy way with one-click script.
Script and zipfile maitained by @NBreunig3. Questions about this method should be directed to him.
Download and extract the zip file: http://bit.ly/1Ln9FKB
Then, exec the root.bat script.
Second method: Using the classic way.
Enable ADB debugging
Go to Settings > About Phone > Software Information and tap build number until you are presented with "You are now a developer".
Back to Settings screen.
In Developer Options, enable USB Debugging.
Insert the USB cable
Send the required files to the device
Code:
adb.exe push busybox /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
{
"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"
}
Go to Download Mode
Disconnect the USB cable.
Power off the device.
Hold volume up and insert the USB cable.
Find which COM port your device is connected
Look for the DIAG port.
Code:
ports.bat
Run the root installer script
Change the COMx with the correct port number of the DIAG port.
Code:
Send_Command.exe \\.\COMx < root
Send_Command.exe \\.\COMx < reboot
Feedbacks are welcome! :good:
Credits:
@Chainfire for SuperSU
@Unjustified Dev for original guide
@avicohh for original one-click guide
@high247 for ports.bat
@NBreunig3 for one-click script
is this TWRP also direct installed ?
Ports.bat doesn't seem to be included in the zip file? Should I be obtaining it from elsewhere?
eidt* I got it from the previous archive. After trying 4 different root methods, this one finally worked for me! Doesn't include TWRP but I just used autorec from the play store.
Many thanks!
Tested and working for D855 20P, thanks a lot.
Working on D855 v20i-eur.
Superb job. Thanks
GREAT!!!! It worked perfectly on a D855 with V20g
Thanks!!!
I'm having problems with root on v20i using virtualbox on Mac windows 8.1 after root command just stops
Thanks
Sent from my LG-D855 using XDA Free mobile app
kingas969 said:
I'm having problems with root on v20i using virtualbox on Mac windows 8.1 after root command just stops
Thanks
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
Maybe a issue in serial protocol between virtualbox and your mac.
Please, if you can, try again using a windows machine.
Thank you guys for your feedbacks!
Confirmed Devices has been updated! :good:
can confirm working for D852 on v20f. Thanks a lot!
Work perfect for D855 20i! All other methods are not worked. Thanks a lot! <3
---------- Post added at 08:04 AM ---------- Previous post was at 08:02 AM ----------
kingas969 said:
I'm having problems with root on v20i using virtualbox on Mac windows 8.1 after root command just stops
Thanks
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
This method works on my D855 v20i like a charm. Try use a normal Windows laptop. Good luck
Has someone tried this on Korean variant?
glowarmy said:
can confirm working for D852 on v20f. Thanks a lot!
Click to expand...
Click to collapse
marfioso said:
Has someone tried this on Korean variant?
Click to expand...
Click to collapse
Hello guys!
I don't know. But I encourage you to be the first to try it!
Since you are using lollipop, there is no big risk to your device.
But, in the worst case (if your device doesn't boot), you can enter in Download Mode and flash your rom again using the LG Flash Tool. And with the "Normal Flash" option you won't lose any data in your device.
Using this root method, there is *NO RISK* to your device lose the Download Mode. So, go ahead and try it!
Please, don't forget to tell us your feedback!
Don't work on LG G4 LG H815
Thanks anyway
I can confirm it works on D855 v20g. Thanks a lot!
Does not work with LG-AS99020a 5.0.1
Gosh, I was so excited to try it 'cause a lot of people had success with this :|
Great Job! It works on D855 v20h-HKG!!!
Thx!
Thanks buddy! Finally rooted my Hong Kong D855 (stock 20h)!
I don't know why LG has made it so difficult to root their phones . I've been trying every thing for the last week without success.
D855 w/v20i-EUR confirmed (again)
thanx a lot !!!
the only issue observed so far was with LGBackup. it started to update immediately on phone reboot but stopped with service failure. i don't really care about it but maybe it's worth to mention.
antoniomistretta said:
Don't work on LG G4 LG H815
Thanks anyway
Click to expand...
Click to collapse
Of course not. This is for LG G3. LG G3 root methods use an exploit where you can unmount and remount system/write. LG G4 had patched that. Check out the LG G4 section of XDA and see if they have a new root method.
Tonight i receive new update on my moto x xt1058 AT&T carrier
The system version is 222.201.1
Build number LPAS23.12-21.7-1
I installed it some performance bugs was cleared and battery was also optimised as i assumed
Phone was now faster than before
Now another thing there is no root the developers have another challenge to patch this firmware also
Because AT&T have locked bootloader
Anyone who install this update
please share your experience also
Here is snaps
{
"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"
}
Br
Shahzaib Jahangir
Shabby The Dev said:
Now another thing there is no root the developers have another challenge to patch this firmware also
Because AT&T have locked bootloader
Anyone who install this update
please share your experience also
Click to expand...
Click to collapse
I wonder if this root security patch affects those of us with unlocked bootloaders? (Probably not)
Also I hope the full image is released soon...
squaremoogle said:
I wonder if this root security patch affects those of us with unlocked bootloaders? (Probably not)
Also I hope the full image is released soon...
Click to expand...
Click to collapse
I got the same update notification and installed it. Motorola support has NO CLUE what this update is about. What is it?
I just got the notification too. I'm running a Chilean provider (Movistar) ROM, but the update just says 'en.CL'. I unlocked my bootloader a long time ago though via Motorola code IIRC, and to tell the truth I don't remember what precautions to take when receiving an OTA.
Moto X AT&T 2016-04-01 update ready
Not found any changelog for this update
Anyone found the changelog so please share it
Corsario_Negro said:
I just got the notification too. I'm running a Chilean provider (Movistar) ROM, but the update just says 'en.CL'. I unlocked my bootloader a long time ago though via Motorola code IIRC, and to tell the truth I don't remember what precautions to take when receiving an OTA.
Click to expand...
Click to collapse
My moto x xt1058 has also unlocked bootloader and i install this update without any issues
Shabby The Dev said:
Not found any changelog for this update
Anyone found the changelog so please share it
My moto x xt1058 has also unlocked bootloader and i install this update without any issues
Click to expand...
Click to collapse
Did you lose root after updating? Did you have to 'put bloatware back in' like the sticky says?
No my phone was not rooted
Anyway if bootloader was unlocked so you also can easily downgrade your moto x with 21.7 firmware
But be carefully
Backup your data first
I don't backup any data even contacts and update it [emoji2] and i m lucky
Br
Shahzaib Jahangir
Shabby The Dev said:
Not found any changelog for this update
Anyone found the changelog so please share it
My moto x xt1058 has also unlocked bootloader and i install this update without any issues
Click to expand...
Click to collapse
I don't follow... How is it that your bootloader is unlocked, but you are unable to root?
You can still flash a system app and root that way, correct?
I am updating from 222.26.7.ghost_att.ATT.en.US and the zip includes several system library updates and a new modem firmware.
I have an unlocked bootloader and a rooted phone, so to install:
* Boot to recovery (TWRP) and make a backup copy of update zip (/cache/Blur_Version.222.26.7.ghost_att.ATT.en.US.zip) at /sdcard (aka /data/media/0).
* Flash system and recovery to stock firmware in bootloader
* Install the update using stock recovery
* Reflash TWRP and reinstall SuperSU and Xposed
squaremoogle said:
Shabby The Dev said:
Corsario_Negro said:
Did you lose root after updating? Did you have to 'put bloatware back in' like the sticky says?
Click to expand...
Click to collapse
No my phone was not rooted
Click to expand...
Click to collapse
I don't follow... How is it that your bootloader is unlocked, but you are unable to root?
You can still flash a system app and root that way, correct?
Click to expand...
Click to collapse
Shabby means his phone was not rooted prior to applying the update, not he lost root or was unable to root.
I would happily take it if it means better battery life root is useless in its current state.
Just got the update notification on the XT1060.
I'm trying to learn how to root this thing, as I've never done so on an Android device. Should I hold off on updating this until after I've rooted?
My brother's wife got this update and now her phone is not connecting to their wifi network, even after several resets and different configurations.
Hopefully the old root methods will be adapted to this update.
Please chime in if you have a similar problem or a solution.
---------- Post added at 05:26 PM ---------- Previous post was at 05:21 PM ----------
MortimerR said:
Just got the update notification on the XT1060.
I'm trying to learn how to root this thing, as I've never done so on an Android device. Should I hold off on updating this until after I've rooted?
Click to expand...
Click to collapse
Definitely consider rooting/unlocking your bootloader as an alternative to official releases. You just have so many more options once you've made custom roms available to yourself.
Installed in on my dev edition and haven't noticed any difference.. Probably not a significant update.
cipsaz said:
Installed in on my dev edition and haven't noticed any difference.. Probably not a significant update.
Click to expand...
Click to collapse
Did you use this OTA on a rooted device? If so, did it impact your root?
bobo-the-drunk said:
Did you use this OTA on a rooted device? If so, did it impact your root?
Click to expand...
Click to collapse
The device is not rooted.
Does anybody have the stock zip for this update or know where they're usually located? I've been researching the method CrashXXL used to add root/Xposed/remove bloat, but then Moto dropped this update and I have to start from scratch.
lpjunior999 said:
Does anybody have the stock zip for this update or know where they're usually located? I've been researching the method CrashXXL used to add root/Xposed/remove bloat, but then Moto dropped this update and I have to start from scratch.
Click to expand...
Click to collapse
@iscaela posted the instructions to get update.zip file in the first page read but for this you need rooted phone
Don't Ever update your rooted moto X to the latest firmware via OTA specially verizon xt1060
My friend update a rooted xt1060 via OTA to the latest firmware and now his phone doesn't booted anymore Stuck on fastboot with an error of system failure
Now no firmware available right also fail to downgrade waiting for new update firmware
another thing this update have only SECURITY PATCH not any changing but i think patched the root privileges
Shabby The Dev said:
@iscaela posted the instructions to get update.zip file in the first page read but for this you need rooted phone
Click to expand...
Click to collapse
You also need an unlocked bootloader, which I don't have.
Android Recovery Emulator
{
"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"
}
The android recovery emulator is a utility that allows you to emulate the android recovery.
Most options are supported and you can flash zips and roms with this, wipe data/factory reset, clear cache etc, this is basically a virtual device.
Download here
REVIEW:
Like, Share and subscribe for more programming tutorials!
Supported syntax -
(#) comments
(ui_print) printing
(package_extract_file) extracting files
(package_extract_directory) extracting directories
(block_image_update) updating blocks
(run_program) execution
(delete) deleting
(delete_recurive) recursive deleting
(abort) aborting installation
(format) formatting
(mount) mounting
(set_perm) setting permissions
(set_perm_recursive) setting permissions recursively
(set_metadata) setting metadata
(set_metadata_recursive) setting metadata recursively
(symlink) symlinking
(show_progress) showing progress
Supported error output -
Checks for non existing files
Checks for non existing directories
Outputs possible errors for files or directories not embedded in zip
etc.
Remember to say thanks.
XDA:DevDB Information
Android Recovery Emulator, Tool/Utility for all devices (see above for details)
Contributors
Ricky Divjakovski
Version Information
Status: Stable
Current Stable Version: V1.0.0.0
Stable Release Date: 2017-04-16
Created 2017-04-16
Last Updated 2017-04-18
Okay... I could use something like this but, just 2 questions.
1) Will the results from the Emulator also reflect those results from a TWRP Recovery?
2) For the CWM that this Emulator is based upon, are the results based upon for the last known release version or for all release versions?
Thanks!
Ibuprophen said:
Okay... I could use something like this but, just 2 questions.
1) Will the results from the Emulator also reflect those results from a TWRP Recovery?
2) For the CWM that this Emulator is based upon, are the results based upon for the last known release version or for all release versions?
Thanks!
Click to expand...
Click to collapse
The GUI is merely a theme, based on latest recoveries
So could this be used to flash ROMs onto an unrootable device? Not "unrootable", but USB debugging doesn't work on it so I can't root it but there are ROMs for it
Beasty244 said:
So could this be used to flash ROMs onto an unrootable device? Not "unrootable", but USB debugging doesn't work on it so I can't root it but there are ROMs for it
Click to expand...
Click to collapse
No this is just an emulator, it doesn't do anything to a real device
Where was that Years ago? I'm alomst 24 and My whole Life was wasted on testing ZIPs... Could You please give Me back My Time? lol
Thanks a lot for that! You're a true Hero for Me dear OP. Keep it Up! :angel:
Great work as alawys.
I have idea on my mind several months ago!
Can you make twrp theme emulator so we can test themes on the run.
Or you can make this open source so I can make it my self.
Very nice. If the ability to emulate aroma installers could be added it would be really cool.
@Ricky Divjakovski , does this support the legacy environment? Like using update-binary? Shell?
BTW: works starts in Ubuntu 16.04 with mono.
But if these created subdirs with backslashes will really work? IDK
Hello there, just noob question, I used it with a stock ROM with supersu and dualrecovery ( I have stock z1 compact ) and this is what I get, why that errors ?
http://imgur.com/a/BmSNw
VERY GOOD , but it doesn't ''like'' magisk
could this be fixed or bypassed somehow, so be able to continue flashing and reach to the end ?
mohammad.afaneh said:
Great work as alawys.
I have idea on my mind several months ago!
Can you make twrp theme emulator so we can test themes on the run.
Or you can make this open source so I can make it my self.
Click to expand...
Click to collapse
Im going to add TWRP option in next version
jrkruse said:
Very nice. If the ability to emulate aroma installers could be added it would be really cool.
Click to expand...
Click to collapse
im already on it
will take about a week to properly implement
veez21 said:
@Ricky Divjakovski , does this support the legacy environment? Like using update-binary? Shell?
Click to expand...
Click to collapse
at the moment it only checks if the script exists via "run_program" and parsing the first arguement to the program that then checks if the file exists, if it doesnt it throws a possible error, shell support will eventually be added, but for now the basics
ranf said:
BTW: works starts in Ubuntu 16.04 with mono.
But if these created subdirs with backslashes will really work? IDK
Click to expand...
Click to collapse
i will be compiling this for linux aswell when i get some free time
JIJOK said:
Hello there, just noob question, I used it with a stock ROM with supersu and dualrecovery ( I have stock z1 compact ) and this is what I get, why that errors ?
http://imgur.com/a/BmSNw
Click to expand...
Click to collapse
thats because theres a second zip file inside your zip, thats not supported yes
logosA said:
VERY GOOD , but it doesn't ''like'' magisk
could this be fixed or bypassed somehow, so be able to continue flashing and reach to the end ?
Click to expand...
Click to collapse
seperate zip file? i will add the functionallity for that next build
Ricky Divjakovski said:
thats because theres a second zip file inside your zip, thats not supported yes
Click to expand...
Click to collapse
yes, saw that happened , flashed rom successfully but second zip (magisk) inside the rom made that error appears.
---------- Post added at 10:48 AM ---------- Previous post was at 10:45 AM ----------
Ricky Divjakovski said:
seperate zip file? i will add the functionallity for that next build
Click to expand...
Click to collapse
almost all the latest roms in Samsung galaxy Note 2 these days, include magisk as default root method.
This is a second zip inside the rom zip, which as I understood creates that error
logosA said:
yes, saw that happened , flashed rom successfully but second zip (magisk) inside the rom made that error appears.
---------- Post added at 10:48 AM ---------- Previous post was at 10:45 AM ----------
almost all the latest roms in Samsung galaxy Note 2 these days, include magisk as default root method.
This is a second zip inside the rom zip, which as I understood creates that error
Click to expand...
Click to collapse
im working on a fix for that now so maybe tonight or tommorow when i get free time i will release
That really will be a tremendous help for us, who flash roms all day long and got stuck in bootloops and errors.
This way , we will be able to test before actually try.
Thank you very much OP.
Excellent, original work !
@Ricky Divjakovski this so needed emulate zip installer... I wish i could have found this years back. Great work.
A video review has been published.
Remember to follow me on youtube for programming tutorials, guides and reviews!
This is the Pixel's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Finally i got a solution for Nexus and Pixel Factory Image flash, now it works perfectly
Nice looking tool.
I'm surprised by the lack of comments on this thread. I'm looking at getting a Pixel 2 5". Is it this easy to just plug in and use this tool to root?
typhoonikan said:
Nice looking tool.
I'm surprised by the lack of comments on this thread. I'm looking at getting a Pixel 2 5". Is it this easy to just plug in and use this tool to root?
Click to expand...
Click to collapse
I'm surprised too, I do not know the reason sincerely
neat, been in debate on flashing but it doesnt seem like theres anything besides recovery and kernels. Wonder why the pixels have such a low rom rate. Even my pixel c doesnt have a root/rom option still.
tevil said:
neat, been in debate on flashing but it doesnt seem like theres anything besides recovery and kernels. Wonder why the pixels have such a low rom rate. Even my pixel c doesnt have a root/rom option still.
Click to expand...
Click to collapse
Perhaps because the cost has become excessive? Or maybe because there is no more reason to do modding? There are no more a rom like CyanogenMod
thank you!! :good::good::good::good: i have been hoping for something like this to be released. been missing the nexus toolkit. hopefully its working well. :fingers-crossed:
I'm interested in trying to see if this will actually unlock my bootloader
---------- Post added at 09:09 AM ---------- Previous post was at 09:05 AM ----------
My OEM unlocking has been greyed out and I haven't been able to unlock bootloader so I can root. Could this help me?
BrianMDenby said:
I'm interested in trying to see if this will actually unlock my bootloader
---------- Post added at 09:09 AM ---------- Previous post was at 09:05 AM ----------
My OEM unlocking has been greyed out and I haven't been able to unlock bootloader so I can root. Could this help me?
Click to expand...
Click to collapse
You need to enable oem unlock in developer options and then you will able to unlock your bootloader
mauronofrio said:
You need to enable oem unlock in developer options and then you will able to unlock your bootloader
Click to expand...
Click to collapse
Oh okay, I still can't do that. Always greyed out.
BrianMDenby said:
Oh okay, I still can't do that. Always greyed out.
Click to expand...
Click to collapse
If it's greyed out, then u have to do a factory reset. However, it still wont unlock it.
I had the same problem when I was trying to unlock my phone's bootloader, but it failed every time, so I'm just waiting if anyone is able to unlock it.
My phone's (Pixel 2) Android version is 8.1.0 and patch level is March 5, 2018.
Let me know if it works out for you.
Thanks
ahmadhas said:
If it's greyed out, then u have to do a factory reset. However, it still wont unlock it.
I had the same problem when I was trying to unlock my phone's bootloader, but it failed every time, so I'm just waiting if anyone is able to unlock it.
My phone's (Pixel 2) Android version is 8.1.0 and patch level is March 5, 2018.
Let me know if it works out for you.
Thanks
Click to expand...
Click to collapse
Sounds like you guys got the Verizon model Pixels?
Sent from my Pixel 2 using Tapatalk
BrianMDenby said:
Oh okay, I still can't do that. Always greyed out.
Click to expand...
Click to collapse
Verizon phone?
usernametaken53 said:
Verizon phone?
Click to expand...
Click to collapse
Yes, sadly, lol
usernametaken53 said:
Verizon phone?
Click to expand...
Click to collapse
BrianMDenby said:
Yes, sadly, lol
Click to expand...
Click to collapse
Verizon branded can't get their bootloaders unlocked at all :/
My phone is carrier locked, if I unlock it, can I enable oem? I'm on ee
Connor1744 said:
My phone is carrier locked, if I unlock it, can I enable oem? I'm on ee
Click to expand...
Click to collapse
I don't know it, but maybe it can work
Hi all,
Did any1 tried to downgrade security patch using this tool??? (Pixel 2)
There once was a window...
BrianMDenby said:
Yes, sadly, lol
Click to expand...
Click to collapse
Connor1744 said:
My phone is carrier locked, if I unlock it, can I enable oem? I'm on ee
Click to expand...
Click to collapse
There was a brief period of time where a bunch of us got our VZW Pixel 2's bootloaders unlocked, the mega thread is here https://forum.xda-developers.com/pixel-2/help/maybe-stupid-question-verizon-pixel-2s-t3726294/post74983838#post74983838, but from what I've read the firmware was patched in February that closed this window/loophole. Also carrier unlocked != bootloader unlocked, it just means you can use it on any carrier's network. Has nothing to do with OEM Unlock in Developer Options. Hope that helps.
With the new update a i make a new recovery flasher option for devices with project treble. Test it and told me if it works
Hi, can anyone confirm the oreo update appeared on FF for European version?
Was-lx1c432b321-log (8.0.0.321)
If yes, is it for p10 lite single sim or dual sim?
Thanks
I'm downloading it right now.
I noticed that it contains the main update package and the secondary ones that is supposed to work with both ds and ss versions
Anyway i think that is Oreo but maybe a beta?
Ra2rd said:
I'm downloading it right now.
I noticed that it contains the main update package and the secondary ones that is supposed to work with both ds and ss versions
Anyway i think that is Oreo but maybe a beta?
Click to expand...
Click to collapse
How did it go anything new ?
'nuff said
{
"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"
}
西村大一 said:
'nuff said
Click to expand...
Click to collapse
How do u update it. I try trought DNS from FF but it gives me error that it's not approved
西村大一 said:
'nuff said
Click to expand...
Click to collapse
Can you run the "getprop ro.treble.enabled" command in terminal (or ADB if you prefer)? Would be nice to see if it's supported.
With skill. Find it yourself. There is a way to force install ANY update. For free. But you have to have some brain to first find it, to be sure that you have, again, enough brain to not brick your device. I will not link anything. Until you acknowledge you will do AS INSTRUCTED, NO OTHER STEPS.
---------- Post added at 23:04 ---------- Previous post was at 23:02 ----------
Trixanity said:
Can you run the "getprop ro.treble.enabled" command in terminal (or ADB if you prefer)? Would be nice to see if it's supported.
Click to expand...
Click to collapse
Code:
HWWAS-H:/ $ getprop ro.treble.enabled
true
HWWAS-H:/ $
this is what the device says
西村大一 said:
this is what the device says
Click to expand...
Click to collapse
Thanks.
Nice.
How does it run on the P10 lite ?
Any noticeable diffrence ?
AymZ12 said:
How does it run on the P10 lite ?
Any noticeable diffrence ?
Click to expand...
Click to collapse
There is the UI smoothness because it is a fresh install, Project Treble is enabled, and all around it is more polished than EMUI 5.
西村大一 said:
There is the UI smoothness because it is a fresh install, Project Treble is enabled, and all around it is more polished than EMUI 5.
Click to expand...
Click to collapse
Nice
Thanks bro
西村大一 said:
There is the UI smoothness because it is a fresh install, Project Treble is enabled, and all around it is more polished than EMUI 5.
Click to expand...
Click to collapse
いいね！thanks for info
there is no compatible twrp recovery for this rom. can't root
Do you know if Oreo has released for WAS-LX3605B?
西村大一 said:
With skill. Find it yourself. There is a way to force install ANY update. For free. But you have to have some brain to first find it, to be sure that you have, again, enough brain to not brick your device. I will not link anything. Until you acknowledge you will do AS INSTRUCTED, NO OTHER STEPS.
---------- Post added at 23:04 ---------- Previous post was at 23:02 ----------
Code:
HWWAS-H:/ $ getprop ro.treble.enabled
true
HWWAS-H:/ $
this is what the device says
Click to expand...
Click to collapse
1. Unlock bootloader
2. Flash nocheck recovery or something like that.
3. put the update.app into a folder on the sd card.
4. Boot into eRecovery and apply the update
Right ? I only had HTC and Nexus devices so I don't really know how the update process works on Huawei devices with 2 recovery's
Eurofighter_ty said:
1. Unlock bootloader
2. Flash nocheck recovery or something like that.
3. put the update.app into a folder on the sd card.
4. Boot into eRecovery and apply the update
Right ? I only had HTC and Nexus devices so I don't really know how the update process works on Huawei devices with 2 recovery's
Click to expand...
Click to collapse
Sort of. But it's pretty difficult to do it yourself. There is a script out here that will do that for you automagically.
西村大一 said:
Sort of. But it's pretty difficult to do it yourself. There is a script out here that will do that for you automagically.
Click to expand...
Click to collapse
This one ?
https://forum.xda-developers.com/p10-lite/development/hwota-huawei-p10-lite-t3776186
Eurofighter_ty said:
This one ?
https://forum.xda-developers.com/p10-lite/development/hwota-huawei-p10-lite-t3776186
Click to expand...
Click to collapse
Bingo.
西村大一 said:
Bingo.
Click to expand...
Click to collapse
Can I lock the bootloader ? TWRP is removed after I ran the script ?
Eurofighter_ty said:
Can I lock the bootloader ? TWRP is removed after I ran the script ?
Click to expand...
Click to collapse
Gonna test the bootloader relock, but the TWRP is indeed removed after. But be careful, that script can't revert the update since the Oreo update changes the partitions' structure....
geeklynx said:
Gonna test the bootloader relock, but the TWRP is indeed removed after. But be careful, that script can't revert the update since the Oreo update changes the partitions' structure....
Click to expand...
Click to collapse
Yep, it is removed. I ran the script and everything works great even VoLTE for Orange Romania !
I don't really want to downgrade because it's pretty stable for me