Related
{
"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"
}
Requirements:
Flashtool by @Androxyde
XZDualRecovery 2.6 RELEASE or newer.
Current FW version: 10.3.1.A.2.67, maybe others too, let me know!
Special features:
SuperSU integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.7.43 BETA (CWM & PhilZ Touch & TWRP) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
For both locked and unlocked bootloaders!
The C6503 ROM is based on the FTF provided by @Androxyde in this thread. Thanks dude
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
How to update to 10.4.B.0.569:
Files:
For C6502: Download C6502.flashable.10.4.B.0.569.zip (Bittorrent: 807MB) and C6502_10.4.B.0.569_Stripped.ftf (18MB)
For C6503: Download C6503.flashable.10.4.B.0.569.zip (Bittorrent: 778MB), SuperSU_fix.zip (1.1Mb) and C6503_10.4.B.0.569_Stripped.ftf (18MB)
For C6506: Download C6506.flashable.10.4.B.0.569.zip (Bittorrent: 778MB) and C6506_10.4.B.0.569_Stripped.ftf (18MB)
Save them somewhere you remember;
Put 'C650X.flashable.10.4.B.0.569.zip' on (the external) SDcard1;
Put 'C650X_10.4.B.0.569_Stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C650X.flashable.10.4.B.0.569.zip' in TWRP (after flashing the ROM also flash 'SuperSU_fix.zip', needed only when using the C6503 package)
do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C650X_10.4.B.0.569_Stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone.
As I do not have a ZL, @Bird40 tested this release prior to creating the thread, so I know it works fine
Enjoy! :laugh:
DE-ODEX your ROM! (Read the NOTE below this guide before flashing!)
AFAIK you can use this deodex package on the C6502 and C6506, as the base apps and framework are the same.
Make sure you have the flashable ROM installed before you do this.
Download C6503_deodex.10.4.B.0.569.zip (Bittorrent: 383MB), save it somewhere you remember;
Put 'C6503_deodex.10.4.B.0.569.zip' on (the external) SDcard1;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6503_deodex.10.4.B.0.569.zip' in recovery, do not reboot but go back to the main menu;
Clear dalvik-cache ONLY;
Reboot to system.
The first boot after flashing this you will see Android optimizing the apps on your phone, this might take a while... but should be just fine
NOTE: There are some issues with the deodexed ROM, it sometimes causes a FC, specifically if you go to keyboard & language settings through the settings app. I'm not able to find why it does this but my guess is that it's a bug in the Sony ROM that surfaces with deodexing it... There is a work around for this one though: Open any keyboard driven app (text editing/entering box), tap '12!?' and then tap the tools button on the right of the space bar. This will take you to the app to modify your keyboard settings.
Known XZDualRecovery Issues:
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a /system ONLY using any means you are familiar with so you can try again.
Root it using [Z][ROOT] DooMLoRD Easy Rooting Toolkit.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
thanks!!! testing
It works perfect! Thanks a lot
will it work on c6502 .569 fw?
[NUT] said:
As I do not have a ZL, @Bird40 tested this release prior to creating the thread, so I know it works fine
Click to expand...
Click to collapse
All is well.
Thank you.
So we can't install busybox on this?
LiLTrippz said:
So we can't install busybox on this?
Click to expand...
Click to collapse
Whenever I try to open root explorer it doesn't work, as if I don't have root perms, it's like superuser is denying everything but in root checker it says i have root access???
LiLTrippz said:
Whenever I try to open root explorer it doesn't work, as if I don't have root perms, it's like superuser is denying everything but in root checker it says i have root access???
Click to expand...
Click to collapse
ok same problem and i cant boot into recovery as well
root checker : this device does not have proper root access
demonicjas said:
ok same problem and i cant boot into recovery as well
root checker : this device does not have proper root access
Click to expand...
Click to collapse
Well I just fixed it, my problem was fixed by going into supersu and i just made the settings to always grant.
LiLTrippz said:
Well I just fixed it, my problem was fixed by going into supersu and i just made the settings to always grant.
Click to expand...
Click to collapse
i have to do everything all over again ..
back to .244 and headed from there now
edit : done .
all good
If you run into the superuser 'grant all' issue, look up the app in the settings and clear all its cache and user settings.
That should fix that problem.
i have a problem.....
when i give root acces to a app (like root explorer or unnistaller root) before the update, i have no problems with root access after the update.... but if i do this after update, i mean, install a root app after update, i have not root access for that app, even if i have the supersu app and recovery.
any idea about how to resolve it????
MY PRINCIPAL PROBLEMS IS WITH XPOSED
There is one problem, Xposed Framework doesn work I installed the last version but still when I reboot phone, it still shows me framework is not installed yet and tells me I need to reboot again, but still it doesn work.
Anyone got this issue?
someone is having trouble with ADB after updating with this method?
Enviado de meu C6503 usando Tapatalk
felipeacydc said:
i have a problem.....
when i give root acces to a app (like root explorer or unnistaller root) before the update, i have no problems with root access after the update.... but if i do this after update, i mean, install a root app after update, i have not root access for that app, even if i have the supersu app and recovery.
any idea about how to resolve it????
MY PRINCIPAL PROBLEMS IS WITH XPOSED
Click to expand...
Click to collapse
batrian said:
There is one problem, Xposed Framework doesn work I installed the last version but still when I reboot phone, it still shows me framework is not installed yet and tells me I need to reboot again, but still it doesn work.
Anyone got this issue?
Click to expand...
Click to collapse
xposed issue is known .. Rovo89 is already working on it
any other root app have the same problem..... it doesnt apear the messege requesting root access.
[NUT] said:
If you run into the superuser 'grant all' issue, look up the app in the settings and clear all its cache and user settings.
That should fix that problem.
Click to expand...
Click to collapse
felipeacydc said:
any other root app have the same problem..... it doesnt apear the messege requesting root access.
Click to expand...
Click to collapse
.....
fixed.... my bad!
i just grant root access without request, just to all, and it works perfect.
I'm trying to find a solution to this... Luckily we have a working recovery to restore it any way we can
bug from busybox!!!
tnx for rom
I spent a lot of the weekend trying to root my Zenwatch (on 4.4.2w), or get a custom recovery working. Here's what I have tried and found out so far. They locked it down pretty damn well.
Unlocking bootloader and accessing recovery
Go to Settings -> About -> Press Build Number 7 times -> Swipe right, Developer Options now shows under About.
Theres a few different options including an Asus utility to check sensors and such.
To get into recovery or fastboot, you need to active ADB Debugging, unplug the watch than plug it back in, then run "adb reboot recovery" or "adb reboot fastboot"
To unlock bootloader, you need to push the reset button on the back to select.
In recovery, swipe right to left to show screen, up and down to select, and left to right to select.
My Findings so far
The kernel source and ROM source are not available anywhere.
There is no way that I can find to get root. I even went as far as loading towelroot onto the watch through adb install, but it just hangs and eventually closes.
There is no way I have found to build a custom recovery with CWM or TWRP.
There is no way I have found to dump the boot or recovery partitions.
There is no su binary preinstalled. Attempting to link a su binary has come up null.
dump_image binary is not installed, nor can you get it to install.
Trying to install any packages through stock recovery gives signature error.
Trying to use dd command to dump boot or recovery ends with "permission denied"
Trying to use "fastboot oem saveprt2sd recovery -n recovery.img -a" ends with "invalid page size". Same with trying to dump boot in this fashion.
Trying to boot either the LG G Watch or Samsung Gear Live unsecured boot images comes back with "(remote) dtb not found" (No surprise here, but it was worth a shot)
fstab is root only.
/dev tree is root only.
all init.asus scripts are root only.
You can install packages with "adb install" but all the standard root gaining apps stall or force close. Towelroot seems to try, but locks up after hitting "make it r4in." trying to change the modstring on v3 (with triple tap title) does not provide a field to change.
Kernel command line is root only.
I browsed EVERY file on my watch hoping to find a hole that I could build off of, but alas, I had failed.
Even trying to do "adb backup" results in "Confirm on Device," and closes immediately afterwards, with no confirm.
I believe that unless they release either the kernel source or the full ROM source, we are unable to root or modify any options.
Which really sucks, because the "OK Google" screen is REALLY F****** BRIGHT.
if anyone has success, please share
I thought I'd try installing one of my own apps and see what happened. It installs okay, but it crashes immediately. I'm guessing it's because I'm using something that's not supported, probably sound or Webkit (the app displays an HTML tutorial the first time it's run). I haven't had time yet to run it from the debugger and see what's going wrong.
I haven't bothered to even watch the video yet but presumably this shows how to root Wear devices and includes links to a Wear compatible supersu, although no custom recovery for the Zenwatch yet. There are links to TWRP for other major watches so I'm guessing it's just a matter of time.
http://www.xda-developers.com/android/root-android-wear-5-0-1-xdatv/
dgjenkins said:
I haven't bothered to even watch the video yet but presumably this shows how to root Wear devices and includes links to a Wear compatible supersu, although no custom recovery for the Zenwatch yet. There are links to TWRP for other major watches so I'm guessing it's just a matter of time.
http://www.xda-developers.com/android/root-android-wear-5-0-1-xdatv/
Click to expand...
Click to collapse
To build a custom recovery, you need to pull the existing recovery or boot partition off of the device and pull partition information (fstab, which is not readable by user on this device) and the build.config information (which is also not readable by user), or pull the fstab.anithias and build.config from the running system (which again is not accessible to the standard user account).
Without that information, you can't build a custom recovery. I've been attempt this for almost 2 weeks now, and its locked down pretty well. The G Watch and Gear Live allowed access to the needed files, but Asus did not with the ZenWatch.
If anyone is willing to risk bricking their watch (by getting past the dtb error when trying to boot the LG G Watch or Samsung Live recovery images, which is a long shot in itself) to get the openRecovery/CWM/TWRP to install and work to the point of getting ADB working through recovery mode, I can do the rest to build the recovery.
I just dont want to risk bricking mine quite yet, as the google play store was out of stock the last time I checked to purchase a "testing" watch.
@z3nful - I just found this. Is it useful?
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_ZenWatch/kernel_3_13_0_10.zip
CSX321 said:
@z3nful - I just found this. Is it useful?
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_ZenWatch/kernel_3_13_0_10.zip
Click to expand...
Click to collapse
Kernel source code
Sent from my SM-G900P
@z3nful And an ota? Would it be usefull?
OTA LWX48S
I haven't had a chance the last week to work on this with the holiday season going on and having to run my store. When I get a chance to get back to it, I'll let you guys know what I come up with
I started trying to build the kernel yesterday, but I'm not getting far yet. I've been a developer for over 30 years, but most of my Linux/other UNIX experience was over 10 years ago, and I've forgotten a lot.
I've tried a couple of different compiler versions, but I'm pretty quickly running into different issues with either one. I'm not sure what version Asus used, but it's apparently not either of the ones I've tried. Also not entirely sure what configuration to use. I'm using the 8226 configuration now, because there's no 8026 configuration in the source archive. I don't know if that's suitable or not.
All-in-all, I may not be out of my depth, but I'm out of my area of experience, at least. Any tips, @z3nful?
Edit...Is there any useful information in the OTA zip file? It's available. Partition info or a boot image or something?
@z3nful and @CSX321 - Any luck moving forward on this? I'm not a programmer, but I'd be glad to offer any assistance if needed!
btonetbone said:
Any luck moving forward on this?
Click to expand...
Click to collapse
No progress here, I'm afraid. I think I just don't know enough about this environment to do it, without devoting a lot more time to learning.
I've also lost some motivation, because there doesn't really seem to be anything I need root for on the watch. About the only thing I would do if I had it is delete a couple of apps, but since Mini Launcher lets me hide apps, I don't care so much about actually deleting them.
Has anyone had success with adb push? It seems the system is read only and doesn't allow for pushing files. Is root required?
Asus is good at locking down their devices, requiring you to register it with them to get an app to unlock it (you also acknowledge that by downloading the app you are voiding your warranty). I really wouldn't be surprised if they did the same thing with this watch and just haven't released the unlock app yet.
I am kinda disappointed to see this sort of thing from a device licensed by Google. It's like the exact opposite of the Nexus line.
@z3nful Just some helpful links, thought I could help a wear user out (I have the G Watch)
Kernel --> https://android.googlesource.com/kernel/msm/+/android-msm-anthias-3.10-lollipop-wear-release
Also, Gohma ROM for gwatch includes a boot img that auto roots android wear. (http://forum.xda-developers.com/g-watch/development/rom-gohma-2-0-12-15-2014-t2974052) Named rboot.img, I think it might be worth a shot to run "fastboot boot rboot.img" to see if it does anything.
Has anybody been brave enough to try booting rboot.IMG like frap129 suggested?
-Andy
Sent from my Etch a Sketch.
I tried, no luck.. Gave the same "dtb not found" error.
Here is a thread related to DTB in boot images: XDA Topic 2428117
Attached is the rboot.img if anyone wants to see if they can modify it to pass whatever DTB issue is making it fail, if that's even possible. I will dig a little bit deeper once I get out of the office.
The error message:
{
"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"
}
rboot.img, zipped:
View attachment rboot.zip
Ignore my sig, it is several years out of date
Regards,
weasel5i2
Doc Ames said:
Has anybody been brave enough to try booting rboot.IMG like frap129 suggested?
-Andy
Sent from my Etch a Sketch.
Click to expand...
Click to collapse
For those that picked up a TMobile GPad F 8.0 recently, here's a good thread to ask questions until we either get a separate forum or get enough info to move over to the General.
Root
Kingroot works well following the instructions here: All you need for LG GPad 8.0 [LG v490] thread. Once rooted, replace it with SuperSu using this method.
It is best to use KingRoot 4.1 or earlier to root, replacing it as soon as possible. 4.5 is very difficult to uninstall, although you can purchase SuperSUMe on Google Play to attempt it.
OS
Stock OS is the only option at the moment. There is a system update available which fixes the stagefright bug. It can still be rooted.
Recovery
Thanks to @Rashed97 and @KAsp3rd a beta TWRP is available here. This is not a zip, so use Flashify, TWRP Manager or equivalent to flash zips. Hooking up a USB mouse also works well for in-recovery navigation.
Kernel
Similar to LG stock ROM on their phones, the kernel has some adjustable features accessible through Kernel Aduitor or Trickster.
Xposed
Xposed installs and runs well. G3TweakBox has the ability to adjust some extra settings.
ADB driver
I got one as part of the Father's Day promotion as I needed to upgrade my mobile internet hotspot. I would like to migrate from a Nexus 7 2013 and needed the ADB driver for restore using Helium. Has anyone come across a working ADB driver for this GPad?
I was able to root with Kingroot 4.1 and then replace Kinguser and su binaries to SuperSU using this method:
http://forum.xda-developers.com/showpost.php?p=60669196&postcount=1&nocache=1&z=4065499287098646
---------- Post added at 11:45 AM ---------- Previous post was at 11:39 AM ----------
These are the USB drivers I used . Got them from this thread: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
nicknc said:
Anyone else had performance issues without rooting?
Click to expand...
Click to collapse
There are performance issues without root as well.
FYI I just unlocked this tablet. Doesn't give 4G LTE on AT&T though, only HSPDA+
To Unlock this model, access the Hidden Menu:
1) From Home screen,Touch the “ Contact”
2) Touch the “ Search Contact
3) You can see the “Keyboard” after Touch the “ Search Contact”
4) Touch the “＋ “ icon after Dialer 2945#*496#
5) Touch Network Lock, you only have 3 attempts to enter the correct Unlock Code which you can get from any online vendors.
6) Press Unlock
Rooted with Kingroot & replaced it with SuperSu using this script. No computer required just make sure you have Terminal Emulator installed!
Download the file attached and extract it
Put the mrw folder on the root of the sd card
Open Terminal Emulator and type:
Code:
su
grant terminal emulator root access
Next type:
Code:
sh /sdcard/mrw/root.sh
The script should then run and work it's magic. After it's completed SuperSU should open up and prompt you to update the binaries. Update the "Normal" way and reboot afterwards.
And that's it! :good:
Post 1000, hooray.
VRAM seems to be on by default and is eating up about 256K according to Kernel Aduitor. Disabling that helped performance some after I did a factory reset. The LTE radio is stronger than my G3, but that might just be a longer antenna.
the 'replace kingroot...' script didn't work for me. Anybody having issues with root not working after reboot? i have to re-root with kingroot every time. going to try the adb method now
sinshiva said:
the 'replace kingroot...' script didn't work for me. Anybody having issues with root not working after reboot? i have to re-root with kingroot every time. going to try the adb method now
Click to expand...
Click to collapse
Which KingRoot version did you use?
nicknc said:
Which KingRoot version did you use?
Click to expand...
Click to collapse
KingRoot-4.1.0.524.apk
[edit/]
I think they must have updated something on their end because now the same kingroot apk is working - root correctly persisting across reboots
You Are The Man {Works Like A Charm}
xoxo_xdagirl91 said:
Rooted with Kingroot & replaced it with SuperSu using this script. No computer required just make sure you have Terminal Emulator installed!
Download the file attached and extract it
Put the mrw folder on the root of the sd card
Open Terminal Emulator and type:
Code:
su
grant terminal emulator root access
Next type:
Code:
sh /sdcard/mrw/root.sh
The script should then run and work it's magic. After it's completed SuperSU should open up and prompt you to update the binaries. Update the "Normal" way and reboot afterwards.
And that's it! :good:
Click to expand...
Click to collapse
{
"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 followed your instructions to the "T"! Your method for rooting with Kingsroot 4.1 English version, and replaced it with SuperSu
works like a charm! My suggestion to everybody, do everything in the internal storage area! Don't use your external SD Card using the above instructions! I'm making phone calls on this baby to via WiFi and LTE, sweet!
now just need to get roms
kinda makes me want to try and make my own.. I've never developed before. lol!
Which custom recovery we use?
Rican2008 said:
Which custom recovery we use?
Click to expand...
Click to collapse
Nothing out there yet that I've seen. It'll come-- the v500 has had TWRP for about 9 months now. This one has only been out a couple of weeks.
Rican2008 said:
Which custom recovery we use?
Click to expand...
Click to collapse
I got a CM recovery to build using the stock kernel source from LG, but I'm super hesitant to flash it, until I can verify the LG Updater software works for me. I don't have a Windows box ATM, so it'll take a bit more effort. I'll post here with results once I'm willing to flash.
Now that we have the root, has anyone tried to adjust the color of a panel? It is way too warm compared to my other devices (viewing my DSLR pics almost makes me think thr wirte balance was off).
northantara said:
I got a CM recovery to build using the stock kernel source from LG, but I'm super hesitant to flash it, until I can verify the LG Updater software works for me. I don't have a Windows box ATM, so it'll take a bit more effort. I'll post here with results once I'm willing to flash.
Click to expand...
Click to collapse
Well, I flashed it, and things went, err, poorly. I'm done trying. Turns out, it's not actually possible to recover from download mode with LGMobile Support Tool, at least until an update is made available online.
Thanks for trying. I assume the bootloader is locked on this too, meaning we will need to bump any flashable zips anyway.
The step to replace KingRoot with Supersu failed half way for me. Apparently there's a typo in the script >.< Now KingRoot thinks that the tablet is rooted even though it isn't... stuck with broken root...
That is not good news, if this baby has a locked boot loader I am taking it back. Left AT&T for locking the boot loaders of their devices.
Hello folks!
It's been a while since last time I spent in this forum section (when the method for flashing Poland MM KDZ was published), but suddenly I decided to check the current development and it was great do discover that developers found a way to unlock bootloader! Then, I tried to do the procedures, found some adversities around the path, flashed stock KDZ for my device A LOT and finally managed to obtain a fully working LP stock with root and TWRP for my model: H442F (Dual SIM) ("LG Volt 4G" in Brazil).
The thing is: although a lot was done regarding the Spirit LTE, I found near zero information specifically for my device variant. Since I tried a lot of paths and eventually achieved an interesting result, I decided to write a full tutorial, with a lot of instructions and pictures for "novices" who desire learn all the steps but gives up at the high learning curve. Finally, I also wrote this tutorial in Brazilian Portuguese, which I believe will help at least some comrades (you can download the PDF in portuguese HERE).
Needed files:
LG Drivers (remove old ones if already instaled)
LG Flash Tool 2014 (credits to @quangnhut123 from this thread)
Brazilian H442F10a Firmware (this is a low speed server, I can upload to a better one if someone asks)
Android SDK Tools (for Windows users; Linux ones just install the package android-tools-adb)
Kingroot (or download here: www.kingroot.net)
Latin America Patched Aboot (credits to @pvineeth97 , for more info check this thread)
TWRP (or download here: https://twrp.me/lg/lgspiritlte.html)
Flashfy (or download here: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en)
SuperSU (or download here: http://www.supersu.com/)
Finally, if you prefer, you can download a full pack in this link (except for KDZ), however, I did prefer to keep isolated links for better credits and referrals
Step-by-step
Download all needed files
Install drivers, SDK and unpack Flash Tool
Save all files in the same folder, but keep KDZ file inside Flash Tool folder
Put your phone in download mode (power off, hold vol+, plug usb in pc, keep holding until download icon appears)
Wait a little for Windows completely detects device and load all drivers
Verify in Device Manager if your pc detects phone as "LG Mobile USB Serial Port (COM#)"
{
"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"
}
Open LG Flash Tool as admin
Select KDZ file
Choose the downloaded H442F10a_03.kdz file
Choose CSE Flash
Click START
Then, "Clear phone software update registry"
You'll see a warning
Then, OK (no need to change country)
Another app will open for the flashing. If you are offline, it is possible to show just a "?" character. Wait patiently...
In about 5min it will finish
After some reboots, you'll see the phone starter screen. Just move forward (no need to configure anything right now, maybe wifi, but not google account)
Enable Developer Options going to Settings/General/Common/Software Information and tap some simes in Build Number until the "You are a developer" message appears
Go back to Settings/Developer Options and turn on USB Debugging
With Debugging on, choose MTP (for Windows) or PTP (Linux), and when asked, allow the computer
Now, make sure you installed (and know how to use, since I will cover just a few commands here) the Android Debugging Bridge (adb). It will be essential for some steps, as well for entering Recovery Mode (I will show some Linux screenshots because I do not use Windows - for this tutorial, just for KDZ flash - but with a working adb the commands are the same)
Open a command prompt (Windows: right click in start menu) or a terminal (Linux) and run "adb devices" to see if the device was detected. If not, run again and check if phone are asking permissions (and grant it)
Go (cd) to the folder with all downloaded files and write the commands (some names may be different if you downloaded individual files from official links)
adb push aboot_5120_patched.bin /sdcard/
adb push twrp-3.2.1.0-cn70n.img /sdcard/
adb push SuperSU-v2.82-201705271722.zip /sdcard/
adb install Flashify_1.9.2.apk
adb install KingrootV5.3.1.apk
At whit point, make sure your internet is fully working (3-4G or WIfi), then, open Kingroot and root the device
After a well successful root, go back to adb and run "adb shell" and then "su". The phone will ask root permission. Grant it and in adb again run "cd /sdcard"
Now we arrived a critical step. Make sure to type the command as is show, because an error may result brick. We will copy the modified aboot into the respective phone partition (check code, check picture, and double check!)
If everything occurs all right, will appear this message
Great! Now you have an unlocked bootloader! What we have to do now is fhash a custom recovery (in this case, TWRP).
Open Flashify, give root rights, then go into Flash/Recovery Image/Choose a file/File explorer/sdcard/[downloaded file]. When asked to flash click "YUP!" and then "Flash More" (as we do not want the phone to reboot right now)
An extra step I prefer to do is remove Kingroot, since it installs a lot of services and keep device substantially slow. If you prefer Kingroot over SuperSU, you are DONE!
Case you prefer SuperSU... Open Kingroot/.../Settings/Uninstall Kingroot
It will prompt if you are sure. Just click Continue/OK
Go back to prompt/terminal and run "adb reboot recovery"
Phone will enter TWRP!
Now, just a few steps!
Go to Install and flash SuperSU
Go to Wipe and do a Factory Reset
Go to Settings and disable TWRP app installer (optional)
And finally go to Reboot and choose System
DONE!!!
Now you have a phone with an unlocked bootloader, a recovery capable of doing a lot of stuff (sideload, wipe cache, backups), and rooted as well.
A really good job, I'm sure a lot of your fellow countryman will find this very useful!
Korelev said:
A really good job, I'm sure a lot of your fellow countryman will find this very useful!
Click to expand...
Click to collapse
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!
Valeeeu dms irmao, ajudou dmss
Ninloth said:
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!
Click to expand...
Click to collapse
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Hi!
Well, unfortunately I don't know. I made the procedure, wrote the tutorial, and 2 months later changed my phone for a new one. Can't test anymore.
Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Yes, it should be compatible with any custom rom as long as your phone is Lg spirit LTE( snapdragon variant ).
So, i was the first to provide the update for this beauty. 6 and 6 pro.
This file will allow you to have ROOT on yout device, extracted with some tools, Terminal/adb typing, etc.
JUST TWO STEPS!
Step 1: Flash the Magisk package on Terminal, CMD or whatever (fastboot flash boot.img) www.mediafire.com/u6weyjcf7edg/igjva0go25fgtcy/magisk_patched-25200_8b9nH.img
Step 2: Download Magisk.apk and that's all!!!!!!
-----
&&&&&&&&&&
Workaround:
- computer doesnt detect phone:
Install this and double click! https://forum.xda-developers.com/t/tool-windows-adb-fastboot-august-2022.3944288/
-¿hou can Y Flass Both.IMGG?
- https://forum.xda-developers.com/t/tutorial-how-to-flash-a-new-boot-img-via-fastboot.1752270/
- I brake my phony please jelp:
Flash RAW or, Flash EDL.
- How do I preseve root with OTA UPDATE?
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
3. Tap "Download and install" or local update if OTA from ASUS WEBSITE
4. Wait until you are prompted to reboot - DO NOT REBOOT NOW!
5. Open Magisk Application
a. Select the Install option.
b. Use Install to inactive slot
{
"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"
}
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !
Thank you for this guide!
Is there a way to go from CN to WW without root?
insideoft said:
Thank you for this guide!
Is there a way to go from CN to WW without root?
Click to expand...
Click to collapse
You don't need root. You can just flash the RAW file. But you MIGHT not be able to update it because updater won't recognize WW update zip file if you don't change that COUNTRY file.
Hello. Is there a link for the OPEN BL?
i searched google but cant find any links for it from the asus side.
i dont really want to install the ones belonging to the older generation of the ROG Phone.
Thanks
BaronBeef said:
Hello. Is there a link for the OPEN BL?
i searched google but cant find any links for it from the asus side.
i dont really want to install the ones belonging to the older generation of the ROG Phone.
Thanks
Click to expand...
Click to collapse
Yes! I don't know if they really work from you, maybe gets you error. But those are in Asus Website as well.
insideoft said:
Thank you for this guide!
Is there a way to go from CN to WW without root?
Click to expand...
Click to collapse
No, you need BL unlock to flash things.
And... "Root is temporary, rom is forever"
So, you can stay without root NOT FOLLOWING the latest'step.
Moderator Information
Dear all,
Two points on the current discussion: 1. give proper credit and 2. follow XDA rules on sharing other's works.
A refresher:
XDA-Developers FORUM RULES
BaronBeef said:
Hello. Is there a link for the OPEN BL?
i searched google but cant find any links for it from the asus side.
i dont really want to install the ones belonging to the older generation of the ROG Phone.
Thanks
Click to expand...
Click to collapse
insideoft said:
Thank you for this guide!
Is there a way to go from CN to WW without root?
Click to expand...
Click to collapse
YOU MAY NOT UNLOCK YOUR BL AFTER YOU UNLOCKED IT ONCE AND RELOCK IT! NOT VERIFIED ON ROG 6 SO PROCEED WITH CAUTION.
The link in step one doesn't work.
williamcll said:
The link in step one doesn't work.
Click to expand...
Click to collapse
FXD!
How to unroot after rooting? Do i need to extract the current boot.img & re flash it to unroot it?
Therazorsedge said:
Hi, I see a lot of threads, so, I open my own.
This is a tutorial of how you can have root permanently AND updates (root+updates) on this beauty.
And also, you can switch to CN (more battery, but less features -> themes, stuff) or WW ROM.
First of all, there's this files you should download on your computer or your beauty:
(A) Log by Google: MOD EDIT: LINK REMOVED, please provide proper credits when sharing others' work
(B) Download OPEN BL from Asus website, the APK to open it.
(C) Root the Asus (Fastboot flash boot on CMD) with a GOOD CABLE (**** cables doesn't work, sorry.) AND with the LATERAL PORT. You need PLATFORM TOOLS AND/OR MINIMAL ADB (GOOGLE IT AS EVERYTHING...) TO RUN...
(D) "Buy" the root explorer APK on play store, don't think for a minute you can find that on Google, or you can find it, I don't know
(E) Install Magisk APK check everything works as ROOT ENVIROMENT SUCCESFULLY INSTALLED.
(F) On ROOT EXPLORER APK press on the ‘ROOT‘ tab to access the root storage of your phone. Navigate to the ‘/Vendor/Factory‘ folder and find the file with the name ‘COUNTRY‘. Tap on the file and open it with the ‘Text Editor‘. put there CN if you want China (capital letters) or, WW if you want global, reset phone.
(G) Go to the big 4GB file you first downloaded and search the FLASH ALL AFT bat, (extract it first); then, put the phone to BL with power+vol. UP until you see in GREEN Start. Put cable on side port, and double click on FLASH ALL. Voila! You have your phone converter and -it can eat updates.
(H) To update it search for updates on Asus; rog 6 firmware on Google.
Troubleshooting
If your phone isn't detected use another cable go to device manager and check for ASUS ADB INTERFACE TO SHOW if not, change cable and/or download ADB drivers on XDA the .exe file.
The magisk image is to root the phone Fastboot flash boot .IMG (put it on CMD window)
Bonus:
To remove HARDWARESTUB download Notifications off root on play store and install it.
(10) The last step of this very good and awesome tutorial; to keep root after update; download the file, put on root directory; let it update DONT DONT DONT reboot; go to Magisk,
a. Select the Install option.
b. Use Install to inactive slot
Reboot, done.
I'm not asking for donation but; you can "donate" me more "Freely" through subscribing to my YT channel if you really want is the same and it's indeed, Free. https://youtube.com/channel/UCRFpKkKvIOrkFY5eDUG_VBg
Click to expand...
Click to collapse
Thank you for the instructions.
My phone's product code has been changed to "WW_AI2201" and could be updated the firmware from ASUS site once. However, after update the product code returned "CN_AI2201". Could you please help me to keep it "WW"?
And also please tell how to change the fingerprint from "CN" to "WW", if you know.
finallau said:
How to unroot after rooting? Do i need to extract the current boot.img & re flash it to unroot it?
Click to expand...
Click to collapse
To unroot you can just go into magisk and click uninstall, but then you probably also want to relock your bootloader MAKE SURE YOU FACTORY RESET AND HAVE STOCK ROM BEFORE YOU RELOCK YOUR BOOTLOADER!!!
Code:
fastboot oem lock
#OR
fastboot flashing lock
Then you probably also want to go to settings -> developer mode afterwards and disable -> 'OEM Unlocking'
I can't get root explorer to mount R/W on root to get COUNTRY file changed from CN to WW..
Though I could save the file but device info HW shows my fingerprint is still CN..
unable to perform manual update as fingerprint is still CN..
Had my root checker checked, running latest magisk as well..
Tried multiple root explorer versions & other file manager with root access..
Some file manager showed "file is read-only"
anybody having the same issue? any solution?
PiPpikachu said:
Thank you for the instructions.
My phone's product code has been changed to "WW_AI2201" and could be updated the firmware from ASUS site once. However, after update the product code returned "CN_AI2201". Could you please help me to keep it "WW"?
And also please tell how to change the fingerprint from "CN" to "WW", if you know.
Click to expand...
Click to collapse
I'm having the same issue too.. looks like it wasn't R/W but R/O only in root explorer hence it's the cause you won't permanently change the COUNTRY file..
Did a fingerprint check using device info HW app still shows my fingerprint as CN...
hi how i can look boot
nadeer88 said:
hi how i can look boot
Click to expand...
Click to collapse
fastboot oem lock
Or
fastboot flashing lock
AzimBahar said:
fastboot oem lock
Or
fastboot flashing lock
Click to expand...
Click to collapse
I have tried but it always doesn't go through..
I use:
adb devices and it I can see it reads my phone.. but when I type adb reboot bootloader, it doesn't continue after this for me to be able to use the commands that you gave.
Is there any way that I am doing wrong? Kindly help me lock my phone again.
Thank you!
PiPpikachu said:
Thank you for the instructions.
My phone's product code has been changed to "WW_AI2201" and could be updated the firmware from ASUS site once. However, after update the product code returned "CN_AI2201". Could you please help me to keep it "WW"?
And also please tell how to change the fingerprint from "CN" to "WW", if you know.
Click to expand...
Click to collapse
Same as me! Just update zip once, then 2n update will be fail, but i saw the country file show WW in root explorer .....any method can flash zip directly?
iMoc said:
You don't need root. You can just flash the RAW file. But you MIGHT not be able to update it because updater won't recognize WW update zip file if you don't change that COUNTRY file.
Click to expand...
Click to collapse
I bought the version with 12GB Ram and 128GB SSD, and I think that's what happens to mine, because I can´t update it OTG, what steps should I follow? What risk do I run that I already have a root and the seller did, and I don't know by what method he did or what he did to pass it from CN to WW