Develop Bugs

LG G4 H815 frozen on LG logo after attempting root/TWRP

Attempted to root phone use ADB and fastboot.
during process noticed difficulty in getting recovery mode open manually and had to use adb reboot recovery, whereupon android recovery picture was there but no menu options.
Could not install TWRP conventionally thus attempted the method shown here.
"NSTALL TWRP
Make sure you have ADB and Fastboot installed.
I always put TWRP.img in the ADB folder - so if I want to boot into TWRP with out installing it this is what I do:
make sure you open a command prompt in the ADB folder "VERY IMPORTANT" and type:
adb reboot bootloader <enter>
fastboot boot TWRP.img <whatever your TWRP image is called in your ADB folder><enter> dont forget the .img at the end
That will re-start your phone straight into TWRP - You can transfer files to and from your computer while in recovery.
If you want to install TWRP permanently, copy your TWRP image to your mobile "while you are in TWRP RECOVERY mode" then press install, then select images, then select recovery NOT BOOT, then swipe to flash. This method does not install TWRP app on your phone, all you need is a reboot app from the play store that will re-boot you into recovery. "
Flashed both twrp image and super-su within the TWRP booted from pc through adb (as shown in the previously mentioned method).
Upon reboot phone has hung at LG symbol. LED is flashing. ADB recognises device as connected however won't respond to reboot requests.
How do i fix this?

GhostlessShell said:
Attempted to root phone use ADB and fastboot.
during process noticed difficulty in getting recovery mode open manually and had to use adb reboot recovery, whereupon android recovery picture was there but no menu options.
Could not install TWRP conventionally thus attempted the method shown here.
"NSTALL TWRP
Make sure you have ADB and Fastboot installed.
I always put TWRP.img in the ADB folder - so if I want to boot into TWRP with out installing it this is what I do:
make sure you open a command prompt in the ADB folder "VERY IMPORTANT" and type:
adb reboot bootloader <enter>
fastboot boot TWRP.img <whatever your TWRP image is called in your ADB folder><enter> dont forget the .img at the end
That will re-start your phone straight into TWRP - You can transfer files to and from your computer while in recovery.
If you want to install TWRP permanently, copy your TWRP image to your mobile "while you are in TWRP RECOVERY mode" then press install, then select images, then select recovery NOT BOOT, then swipe to flash. This method does not install TWRP app on your phone, all you need is a reboot app from the play store that will re-boot you into recovery. "
Flashed both twrp image and super-su within the TWRP booted from pc through adb (as shown in the previously mentioned method).
Upon reboot phone has hung at LG symbol. LED is flashing. ADB recognises device as connected however won't respond to reboot requests.
How do i fix this?
Click to expand...
Click to collapse
use you variant KDZ file and flash it with LGUP.

raptorddd said:
use you variant KDZ file and flash it with LGUP.
Click to expand...
Click to collapse
That worked very well. Thankyou raptorddd.
Praise him. Praise him with great praise.

Applying OTA while running Magisk and a custom kernel

Hello everyone,
So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)?
If someone has an idea on the process to do this please let me know.
Thanks!

ilatimer1 said:
Hello everyone,
So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)?
If someone has an idea on the process to do this please let me know.
Thanks!
Click to expand...
Click to collapse
Kernel, TWRP and Magisk get overwritten by the OTA. You need to reinstall.
Also I'd recommend to disable all Substratum themes before flashing - for me this led to a Bootpool...

ilatimer1 said:
Hello everyone, So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)? If someone has an idea on the process to do this please let me know. Thanks!
Click to expand...
Click to collapse
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.

v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
What's the difference between this step and sideloading the OTA?
Edit: nevermind. Realized you'd flash-all without the -w if you have TWRP.

peoplesindian said:
What's the difference between this step and sideloading the OTA?
Edit: nevermind. Realized you'd flash-all without the -w if you have TWRP.
Click to expand...
Click to collapse
Yes, OTA's fail to execute if you have modified the boot or system partition. An OTA is an incremental only update that selectively writes certain files and is (usually) much, much smaller. This is appropriate for a stock, unmodified device. Lots of people get tired of waiting for the OTA to come, and so they just update manually by sideloading the OTA through the stock recovery (over adb). Nothing wrong with that, and it this will sometimes bring a phone back from bootlooping or other serious problems like FC's and crashing.
A full image contains the full partition images and they are written to the device fully and unconditionally via fastboot. You can only flash a full image if your bootloader is unlocked. It essentially erases the partitions by overwriting the entire contents from beginning to end. Some would argue this more "complete" method is less likely to result in errors, or corrupt files. Removing the -w switch from the batch file script prevents the script from overwriting the userdata partition where all your media, user apps and settings are. Some call this "dirty" flashing.

v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
did exactly this, and all is fine.

otonieru said:
did exactly this, and all is fine.
Click to expand...
Click to collapse
Same

trim81 said:
Same
Click to expand...
Click to collapse
Interesting that Google seems to claim that updating with the OTA should create less problems with this January update:
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/

xclub_101 said:
Interesting that Google seems to claim that updating with the OTA should create less problems with this January update:
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/
Click to expand...
Click to collapse
That article is quite dubious with no source about google confirming the issue :silly:

v12xke said:
Then just execute that file from a fastboot prompt.
Click to expand...
Click to collapse
REALLY dumb question, but how do you execute a .bat from fastboot? Or do you mean with the phone in bootloader/fastboot mode, run the modified .bat?
EDIT: Never mind... put the phone in Bootloader/fastboot mode. Ran the modified .BAT from command prompt within the Platform-tools folder.

I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot

v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
I followed this and everything is installed perfectly with root.
Thank you ??

sn0warmy said:
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
Click to expand...
Click to collapse
Slow internet here, you mind uploading the boot and dtbo.img?

sn0warmy said:
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
Click to expand...
Click to collapse
I like this idea better than the flash all, but forgive me as I haven't flashed any Android 8.1 devices yet.
Is dtbo the new name for what used to be called system?

Help rooting Huawei Watch

Hi,
I'm a noob trying to root my Huawei Watch (to be able to read BTLE messages). I used egalite_kernel_HW_dffc4c0-2.0 which should be rooted (and indeed I see su.sh and busybox.sh script in the /setup folder)
I did the following:
sudo adb reboot bootloader
sudo fastboot reboot-bootloader
# Unzip TWRP_3.1.1.-0_Unofficial-Sturgeon.zip => recovery.img
sudo fastboot boot recovery.img
#In the phone, using TWRP, set to ADB sidleoad (wipe data and wipe cache)
sudo adb sideload negalite_kernel_HW_dffc4c0-2.0.zip
TWRP loaded fine and the rom installed fine to, but when opening the "Advanced Settings" it says that the phone is not rooted.
Any hint of what I did wrong?
Thanks

ruscull said:
Hi,
I'm a noob trying to root my Huawei Watch (to be able to read BTLE messages). I used egalite_kernel_HW_dffc4c0-2.0 which should be rooted (and indeed I see su.sh and busybox.sh script in the /setup folder)
I did the following:
sudo adb reboot bootloader
sudo fastboot reboot-bootloader
# Unzip TWRP_3.1.1.-0_Unofficial-Sturgeon.zip => recovery.img
sudo fastboot boot recovery.img
#In the phone, using TWRP, set to ADB sidleoad (wipe data and wipe cache)
sudo adb sideload negalite_kernel_HW_dffc4c0-2.0.zip
TWRP loaded fine and the rom installed fine to, but when opening the "Advanced Settings" it says that the phone is not rooted.
Any hint of what I did wrong?
Thanks
Click to expand...
Click to collapse
You keep saying your phone. Are you trying to root a phone or a watch? I'll assume you're talking about your watch.
adb sideload is for applying OTA updates. What you want to do is flash that zip.
While in TWRP, do the following:
sudo adb push [path to kernel zip] /sdcard
In the TWRP menu, select install. Navigate to /sdcard and select the zip. Install it.
If you can't get that working, just flash the supersuwear.zip I've attached to this post using TWRP: https://forum.xda-developers.com/hu...aw-1-5-build-m9e42c-to-downgrade-2-0-t3607859
Also, use the advanced wear settings from the play store. I've had issues with the one that negaman includes in his thread.

TheSt33v said:
You keep saying your phone. Are you trying to root a phone or a watch? I'll assume you're talking about your watch.
Click to expand...
Click to collapse
Yes! I just want to root the watch.
Thanks, for the reply. I'll try it and report back

I installed TWRP_3.1.1.-0_Unofficial-Sturgeon and then I tried to install negalite_kernel_HW_dffc4c0-2.0.zip
sudo adb push negalite_kernel_HW_dffc4c0-2.0.zip /sdcard
and Installed using TWRP.
Unfortunately I got the error below:
--
set_perm: some changes failed
Updaterrocess ended with ERROR:
Error installing zip failed
--
Trying to fix the problem I started wiping parts and I screw-up and delete the system. Wonderful.
I then tried to find ROMs and finally I found Huawei-Rom-NX-v2.7.zip and successfully installed (with Root)
https://forum.xda-developers.com/hu...-negalite-huawei-rom-nx-root-bb-v1-6-t3406813
Unfortunately I find out I need a specific build NWD1.171016.002 (Stock ROM from December 2017).
Any idea were to find it?
Or shall I open a new thread?

ruscull said:
I installed TWRP_3.1.1.-0_Unofficial-Sturgeon and then I tried to install negalite_kernel_HW_dffc4c0-2.0.zip...
Click to expand...
Click to collapse
Why do you need that? You're running a rooted rom, right? Wasn't that the goal?
If your goal is actually to be on a rooted rom AND be on the latest system software, I think it would probably be best to start from scratch since you've done so much flashing and I'm really not sure what state your watch is in at this point. This is how you do that:
1. Download this factory image: https://www.androidfilehost.com/?fid=745425885120748838
2. Extract output.tar from that package. If you need software to do this, I recommend 7zip.
3. Extract the contents of output.tar.
4. Copy flash-all.sh, image-sturgeon-m6e69f.zip, flash-all.bat and bootloader-sturgeon-m6e69f.img to the same folder where you have installed fastboot.exe.
5. Boot your watch in bootloader mode (aka fastboot mode), connect it to the computer and double click on flash-all.bat. This will bring your watch to a 100% stock state.
6. Setup the watch and keep taking OTAs until you are on NWD1.171016.002 (there should only be 1 or 2 that you have to take).
7. Boot into bootloader mode and do one of the following steps:
If you want to keep the stock recovery menu and only use TWRP temporarily, perform the command fastboot boot [path to TWRP image].
If you want to have TWRP permanently installed on your watch, replacing the stock recovery menu, perform the command fastboot flash recovery [path to TWRP image]. Then select reboot to recovery in the bootloader menu.
8. Download the supersuwear.zip package that I linked to in my previous post.
9. While in TWRP, adb push [path to supersuwear.zip] /sdcard
10. Install supersuwear.zip using TWRP menu.
And there you go. Latest firmware version, rooted. Download advanced wear settings from the play store if you want it.

Youre the man.
TheSt33v said:
Why do you need that? You're running a rooted rom, right? Wasn't that the goal?
If your goal is actually to be on a rooted rom AND be on the latest system software, I think it would probably be best to start from scratch since you've done so much flashing and I'm really not sure what state your watch is in at this point. This is how you do that:
1. Download this factory image: https://www.androidfilehost.com/?fid=745425885120748838
2. Extract output.tar from that package. If you need software to do this, I recommend 7zip.
3. Extract the contents of output.tar.
4. Copy flash-all.sh, image-sturgeon-m6e69f.zip, flash-all.bat and bootloader-sturgeon-m6e69f.img to the same folder where you have installed fastboot.exe.
5. Boot your watch in bootloader mode (aka fastboot mode), connect it to the computer and double click on flash-all.bat. This will bring your watch to a 100% stock state.
6. Setup the watch and keep taking OTAs until you are on NWD1.171016.002 (there should only be 1 or 2 that you have to take).
7. Boot into bootloader mode and do one of the following steps:
If you want to keep the stock recovery menu and only use TWRP temporarily, perform the command fastboot boot [path to TWRP image].
If you want to have TWRP permanently installed on your watch, replacing the stock recovery menu, perform the command fastboot flash recovery [path to TWRP image]. Then select reboot to recovery in the bootloader menu.
8. Download the supersuwear.zip package that I linked to in my previous post.
9. While in TWRP, adb push [path to supersuwear.zip] /sdcard
10. Install supersuwear.zip using TWRP menu.
And there you go. Latest firmware version, rooted. Download advanced wear settings from the play store if you want it.
Click to expand...
Click to collapse
Bro Thanks!!!!!

magisk instructions

guys please give me noob friendly instructions for installing magisk latest ver on my lenovo p2 15.1 latest build .

Same

First make sure you have USB debugging enabled on your phone, then install ADB on your PC. Connect the phone to the PC and in the installation folder (ADB > platform-tools) shift right click and choose Open command window here. Type adb devices and authorize your PC on the phone. Download the ROM and extract boot.img from it, transfer it to your phone. On the phone install Magisk Manager and patch the boot.img (Install > Patch boot image). Transfer patched_boot.img back onto the PC (to the ADB > platform-tools folder), then boot your phone into fastboot (VOL down and POWER buttons). Repeat the Open command window here step and type fastboot flash boot patched_boot.img. Reboot your phone (fastboot reboot). You are now rooted on custom ROM.

After installing magisk , do I need to install any module to prevent boot loop like f2fs loop module etc .

Check if you can install modules. If you're facing problems, then you will need to change a few things. The "cannot mount magisk_merge.img" issue for example can be solved by patching and flashing boot image from here https://forum.xda-developers.com/lenovo-p2/development/kernel-f2fs-upstreamed-kernel-twrp-t3845976. I tried tinkering with modules for it and ended up bricking my phone. I would also recommend using TWRP from this thread, it got rid of my second problem (which I now forgot).
Just remember that you will need to flash the patched custom kernel after any ROM update.

Rooting 7T without TWRP / Pre-patched Magisk boot.img for 10.0.13.HD65AA (Global)

For those who can't root via TWRP or somehow lost root while updating (like I did), I have a patched boot image to aid others in this endeavor. This is a boot.img from a T-Mobile 7T which I had converted to the Global ROM, extracted and patched by Magisk after applying the latest update (10.0.13.HD65AA). Fully tested and working!
Instructions:
Unzip and place it in a convenient folder (ie, C:/adb/ or whatever's easy to remember.
Open a cmd prompt and navigate to your fastboot/adb folder.
Then run the command
Code:
fastboot boot boot.img
Your phone will be "temp-rooted" once it boots. If you haven't already, install Magisk Manager, then flash Magisk itself (ALWAYS do direct install!).
Don't install any modules yet. Just reboot when prompted after the Magisk flashing process is done.
Profit!
Download from Google Drive
[I dunno where else to upload this that XDA would consider "safe," so GDrive it is, I suppose.]
Spoiler: Process for manually patching the boot.img without TWRP:
Requirements: Stock device with unlocked bootloader only (no other mods), most recent OTA update applied and system rebooted. Fastboot and ADB Windows executables.
1) Enable advanced reboot and usb debugging in developer options.
2) Reboot to bootloader.
Code:
adb reboot bootloader
3) Boot to twrp
Code:
fastboot boot twrp.img
(or whatever you named it).
4) Once booted, enter:
Code:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
exit
5.5) Copy file to the PC:
Code:
adb pull /tmp/boot.img stock_boot.img
6) Reboot phone back to Android.
6.5) Copy boot.img back to phone:
Code:
adb push stock_boot.img /sdcard/boot.img
7) Make sure you have a data connection.
8) Install Magisk Manager.
9) Select option to install Magisk (not the Magisk App). Choose "Select and Patch a File."
10) Point to the boot.img.
11) It will do its thing then come back with a done message. File /sdcard/download/magisk_patched.img will be created.
12) Copy this file to your PC, either using MTP or ADB.
Code:
adb pull /sdcard/download/magisk_patched.img
13) Reboot the phone into bootloader mode again.
Code:
adb reboot bootloader
14) Boot the patched boot from step 12:
Code:
fastboot boot magisk_patched.img
15) Launch Magisk Manager again. You should see the current version available and the installed version below that now. If all is good, choose to install/update Magisk, then "Direct install" and reboot when finished.

I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?

>Akshay< said:
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
Click to expand...
Click to collapse
OH! You're right. I goofed. I'll ask a mod to move it.

This will delete all the data from the phone + bootloader needs to be unlocked?

Brontok said:
This will delete all the data from the phone + bootloader needs to be unlocked?
Click to expand...
Click to collapse
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).

GuyInDogSuit said:
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
Click to expand...
Click to collapse
never mind!
someone already did!
https://forum.xda-developers.com/showpost.php?p=83780229&postcount=12
thanks anyway!

Will this work for 10.0.13 tmobile ? Thanks

gershee said:
Will this work for 10.0.13 tmobile ? Thanks
Click to expand...
Click to collapse
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.

GuyInDogSuit said:
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
Click to expand...
Click to collapse
Thanks!
Worked like a charm.