Develop Bugs

Motorola Defy Mini XT320 all-in-one script

Motorola Defy Mini XT320/XT321 all-in-one script/utility
I've ported mattlgroff's DROIDRAZR all-in-one Script to the Motorola Defy Mini XT320/XT321. This will make life easier and it will do it for you.
Make sure you have fastboot mode if not please refer to this guide for fastboot but there is a fastboot checker in option 6 but it won't install fastboot for you.
Link: http://forum.xda-developers.com/showpost.php?p=36199694&postcount=3
Options available:
1. Root your Motorola Defy Mini XT320/XT321
2. Install 2nd-init/TWRP Recovery
3. Overclock installation
4. Unroot Device
5. Wipe Data/Factory Reset
6. Fastboot checker.
7. Exit Utility
Instructions:
NEW PACKAGE & instructions
1. Download the EXE file at http://www.mediafire.com/?c81fnrtrki65e9i
2. Double click on the exe.
3. Choose an option by entering a number from 1 to 7
OLD PACKAGE & instructions
1. Download package at [REMOVED OLD LINK]
Please Download the fixed package at http://www.mediafire.com/?krxtemrthsz5ier
EXE Version: http://www.mediafire.com/?0kwmx4whjj1ua8c
2. Extract the zip file making sure all the files are in the same place.
3. Click on the batch file named 'DefyMiniUtility.bat'
4. Choose an option by entering a number from 1 to 7.
Credits to:
- Bernd.Defy for overclock module and Guitwo2 for init.d script
- Guitwo2 and jkkk88 for TWRP and aweosomeabhjeet for 2nd-init
- DoOMLoRD for unroot script
- Mattlgroff for the original DROID RAZR all-in-one script
If anyone knows if I missed a member for the credits, please PM me. Thanks
Make sure press thanks if it works
Guys please don't repost it as your own work, otherwise I'll report it and you will get banned from XDA.
NOTE: If you have previously used the old EXE to install TWRP then please remove the old folders by using these instructions using cmd before using updated exe to install TWRP;
1.
Code:
adb shell
2.
Code:
su
3.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock11 /system
4.
Code:
rm -R /system/bootmenu
Then use the updated exe to install TWRP.
NOTE: If you don't like TWRP, you can download Guitwo2's Permanent CWM at http://forum.xda-developers.com/attachment.php?attachmentid=1875373&d=1365682716
Temporary CWM Recovery: http://forum.xda-developers.com/attachment.php?attachmentid=1875299&d=1365680458
2nd-init does NOT work in CWM Recovery
Thanks to @Guitwo2 for CWM Recovery.
Instructions on how to install Permanent CWM Recovery:
1. Make sure stericson-busybox is installed
2. Put XT320_bootmenuV2.zip in the root of your sdcard
3. Reboot into fastboot mode by typing this command in cmd:
Code:
adb reboot bootloader
4. Then type this command in cmd:
Code:
fastboot boot recovery.img
5. Then use volume keys to navigate and power button to select option. Select install zip from sdcard, then select XT320_bootmenuV2.zip and select yes to install the zip file
6. Then reboot device by selecting reboot device now.
CWM 6 has a bug where it asks you to 'disable recovery flash' when you select reboot system now make sure you select NO or you will soft brick your device.
Changelog:
-v2 No need to mount /sdcard in CWM Recovery. Fixed TWRP installation issues.
-v2.0.1 Released an .exe version of script, to simplify installation
-v2.0.1.1 Fixed bootmenu.zip

This can install a custom recovery?

This can install a custom recovery?

Thank you
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD

same problem... someone can fix it? please

fca.sjc said:
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD
Click to expand...
Click to collapse
sfoot13 said:
same problem... someone can fix it? please
Click to expand...
Click to collapse
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.

Thanks
rootdefyxt320 said:
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.
Click to expand...
Click to collapse
Ty for the quickly answer.
Btw, my gsm network wasnt working after the root process. If the same thing happens to someone else, just do a master reset and it will work again.

pull command is working now
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .

fca.sjc said:
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .
Click to expand...
Click to collapse
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.

rootdefyxt320 said:
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.
Click to expand...
Click to collapse
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)

sfoot13 said:
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)
Click to expand...
Click to collapse
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.

rootdefyxt320 said:
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.
Click to expand...
Click to collapse
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu

sfoot13 said:
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu
Click to expand...
Click to collapse
I've released an .exe version of my script. This should work now .
Link: http://www.mediafire.com/?0kwmx4whjj1ua8c

Thank u bro and sorry but i can't overclock it to 700 =/

i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?

OFF TOPIC.
Congrats on your well deserved mention on the portal.

sfoot13 said:
i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?
Click to expand...
Click to collapse
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233

rootdefyxt320 said:
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233
Click to expand...
Click to collapse
:good: Working! Thank u so much, now i have CWM working on my defy mini, i'm really thankful, thanks again

Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!

sfoot13 said:
Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!
Click to expand...
Click to collapse
Looks like 97bootmenu deleted itself, please reinstall the CWM zip again and it should work.

A request to official/unofficial TWRP developers

Hi All!
As plenty of people know by now that the latest modified twrp that we have does not work with encrypted storage when flashing official nougat oos. And there must be many people like me who due to reasons dont have time to copy n move everything back or don't want to decrypt their storage. So me and all of op3 community would appreciate if anyone can take some time out of their schedule and build an updated twrp version so that we can flash official nougat without screwing with storage or encryption. Because nougat is the future now and we'll start receiving nougat update from now onwards. And its a shame tha such an active dev device like op3 does not even have an updated twrp version. Thanks!

+1

A reason for this issue is probably OnePlus not releasing any Kernel Source code yet.
https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996/issues/27
eng.stk was releasing a couple twrp mods but doing so is a pita with users on your back who constantly want 247 support.

AcmE85 said:
A reason for this issue is probably OnePlus not releasing any Kernel Source code yet.
https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996/issues/27
eng.stk was releasing a couple twrp mods but doing so is a pita with users on your back who constantly want 247 support.
Click to expand...
Click to collapse
Totally agree to that. I was also assuming that an updated kernel sources are required to build a compatible twrp recovery for nougat. Waiting eagerly for the same. And considering the feedback of people on official OOS, i don't feel it's really a must have update as of now.
I also agree to the point about users. People need to stop taking developers for granted, and give them their space to release updates, and they should understand the dev is doing this in his/her free time not as a full time job. I hope we'll see an updated TWRP soon. Until then, MM is serving me well. No hurry

He is only asking, stop crying dude
To many ladies with balls here

fanbogo said:
He is only asking, stop crying dude
To many ladies with balls here
Click to expand...
Click to collapse
Sorry for the confusion what is it intended for me?

TWRP password, please help.
As first i wasn't able to flash any twrp files at all as after flashing it shows some black screen so not even from the official TWRP site the files were helpful, then after ages of serching I found some thread in XDA where a guy posted the link to this twrp https://forum.xda-developers.com/on...nity-build-t3461648/post68691560#post68691560, then I was able to successfully install it and boot into TWRP recovery.
So here I am now stuck with the ****** password to decrypt data and I simply want to root my OP 3 but due to this situation I am unable to so any solutions on this will be much helpful and any way to remove the dumb password for the TWRP.
Thanks.

Dude even if twrp shows encrypted you can still flash supersu. Just mount the /system partition in Mount options and flash supersu via otg.

Dude that is a mess n upon that I don't have otg, and really isn't there any way for this to encryption to get decrypt ?

samyj22 said:
Dude that is a mess n upon that I don't have otg, and really isn't there any way for this to encryption to get decrypt ?
Click to expand...
Click to collapse
You can flash SuperSU without TWRP being able to decrypt your DATA partition:
- Boot into TWRP
- cancel the password prompt
- push the supersu.zip to your phone via adb push supersu.zip / (notice the blank between zip and /!).
- go to INSTALL, navigate to the root directory and flash it
- reboot
Worked without issues on my device.

samyj22 said:
Dude that is a mess n upon that I don't have otg, and really isn't there any way for this to encryption to get decrypt ?
Click to expand...
Click to collapse
Connect your phone to your pc, boot TWRP via fastboot from the PC and flash SuperSu via adb under advanced in TWRP.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

AcmE85 said:
You can flash SuperSU without TWRP being able to decrypt your DATA partition:
- Boot into TWRP
- cancel the password prompt
- push the supersu.zip to your phone via adb push supersu.zip / (notice the blank between zip and /!).
- go to INSTALL, navigate to the root directory and flash it
- reboot
Worked without issues on my device.
Click to expand...
Click to collapse
Didn't knew that at all part from ya we can push files via side load, but just to confirm my internal storage shows as 0mb as it is encrypted n even if I push the files to internal storage so just wanted to make sure will it show up in two file manager?
Next thing so if I have any ROM files to flash can they be pushed as well with the command adb push file.zip /right?
N yah I have to enter sideload mode for this right.

samyj22 said:
Didn't knew that at all part from ya we can push files via side load, but just to confirm my internal storage shows as 0mb as it is encrypted n even if I push the files to internal storage so just wanted to make sure will it show up in two file manager?
Next thing so if I have any ROM files to flash can they be pushed as well with the command adb push file.zip /right?
N yah I have to enter sideload mode for this right.
Click to expand...
Click to collapse
I just booted into twrp, canceled the password prompt and pushed the file while being in the main menu.
The file will be stored in your devices root folder, not "internal storage" or "sdcard".
So when you go to "install", you have to go all the way up your folder structure. This is were you will find the supersu.zip.

AcmE85 said:
You can flash SuperSU without TWRP being able to decrypt your DATA partition:
- Boot into TWRP
- cancel the password prompt
- push the supersu.zip to your phone via adb push supersu.zip / (notice the blank between zip and /!).
- go to INSTALL, navigate to the root directory and flash it
- reboot
Worked without issues on my device.
Click to expand...
Click to collapse
Can we perform an adb sideload rather than adb push to directly flash SuperSU zip? Or does sideload only works for rom zips?

AcmE85 said:
I just booted into twrp, canceled the password prompt and pushed the file while being in the main menu.
The file will be stored in your devices root folder, not "internal storage" or "sdcard".
So when you go to "install", you have to go all the way up your folder structure. This is were you will find the supersu.zip.
Click to expand...
Click to collapse
Just a little confusion, as the internal storage is the same as root directory or the one level back to the SD card is the root directory?

abhibnl said:
Can we perform an adb sideload rather than adb push to directly flash SuperSU zip? Or does sideload only works for rom zips?
Click to expand...
Click to collapse
Yes you can directly sideload.

Bro just need confirmation on the commands for the push and sideload as well correctly, that will be really helpful...... ?

samyj22 said:
Bro just need confirmation on the commands for the push and sideload as well correctly, that will be really helpful......
Click to expand...
Click to collapse
Mount system in recovery,
adb sideload sample.zip
adb push <source-path> <target-path>
If file is in the adb folder already, then
adb push sample.zip /system or whatever path you want to send it to.
Edit: While pushing, make sure you mount system as RW first. But i guess when you mount system in TWRP, it's automatically in RW mode. But please do check with someone who has done it or an expert. I have limited knowledge, so sharing as far as i know

abhibnl said:
Mount system in recovery,
Click to expand...
Click to collapse
Hello thank you, but in twrp i can't mount /system
in mount i can select system but i have
Decrypt data
Select Storage
Disable/enable MTP.

acetone802000 said:
Hello thank you, but in twrp i can't mount /system
in mount i can select system but i have
Decrypt data
Select Storage
Disable/enable MTP.
Click to expand...
Click to collapse
Do you have all those 3 options in the mount menu? I don't think that should be there. I'm sorry, your statement is a bit unclear actually.

[G4][UNOFFICIAL][ALPHA] EFIdroid for the LG G4

EFIDroid
A UEFI based Android bootloader.
EFIDroid provides an easy Installer, good looking Material Design user interfaces and uses very dynamic code.
Homepage: efidroid.org
Take over control before loading the Operating system.
EFIDroid attempts to make it easy for both users and developers to control their boot experience.
Multiboot
Install and boot any number of operating systems and recovery tools.
Boot plugins
Change the boot behavior without modifying ROM's. Swapping internal/external memory, overclocking or modifying the ramdisk. Live and without any permanent modifications.
UEFI Apps
EFIDroid uses UEFI in the background which means that you can boot other bootloaders like GRUB or rEFInd and even small games
Download
see Installation section
Requirements
The main OS (that one you currently use) must be rooted to use the efidroid app.
You may be able to install magisk later in a secondary ROM (never tried it though)
Hint:
lineageos root add-on works (tested on LOS 15.1) and magisk will NOT work. Use supersu.
TWRP / FlashFire installable ZIP:
Stable: supersu-stable
Beta: supersu-beta
Latest: supersu
At the moment the only TWRP which is working for efidroid is: twrp-3.1.1 - any newer TWRP release will fail with a ramdisk size error which is not due to a missing kernel patch. It's a known issue for efidroid and one of the reasons for the efidroid rewrite
I maybe find a workaround to get newer TWRP versions installed.. we will see..
So if you have a newer version of TWRP installed currently: upgrade/downgrade to that version first.
Installation
A full howto with screenshots can be found here
Unlock your device! This will NOT work with a locked bootloader (you know about UsU?)
Download the EFIDroid Manager from Google Play Store - Has been removed..
Efidroid manager download: main efidroid thread
Download the latest version by opening the "Downloads" tab of this thread (requires to open this thread in a browser)
Activate my efidroid OTA server:
Option 1 (permanent): modify /system/build.prop
Boot to TWRP
Make a backup (including system partition)!
Mount System partition in TWRP
enable the efidroid OTA server:
Code:
adb shell
echo "efidroid.server_url=https://raw.githubusercontent.com/steadfasterX/efidroid_ota_lgg4/master" >> /system/build.prop
reboot
verify that the efidroid server URL has been set properly:
Code:
adb shell getprop efidroid.server_url
Option 2 (will be lost on reboot): using setprop
Set the efidroid OTA server:
Code:
adb shell
setprop efidroid.server_url https://raw.githubusercontent.com/steadfasterX/efidroid_ota_lgg4/master
verify that the efidroid server URL has been set properly:
Code:
adb shell getprop efidroid.server_url
Open EFIDroid Manager
HINT: If you see an error like "cannot load device info, please check your connection : no value for lge/H815" then the above OTA url has not been set or is set wrong.
Go to Install/Update
Click Install --> HINT: THIS WILL MOVE YOUR BOOT AND RECOVERY PARTITION CONTENT
This means
1. from now on EFIDroid will boot each time u power on the device.
2. the recovery partition gets backed up and you will see it in EFIDroid again as (if TWRP): TWRP (internal).
3. you can still boot your main ROM by just choosing it from the list --> your ROM name - (internal)
If you don't like this you can install EFIDroid to either: recovery or boot partition only. But this is a manual process and when you upgrade with EFIDroid Manager it may overwrite your changes.
Install a custom ROM
A full howto with screenshots can be found here
Open EFIDroid Manager
Open the menu "Operating Systems" and click the FAB (Floating Action Button) at the bottom
Choose in the screen /data/media/0/multiboot as location.
Enter a name for the ROM
Optional: Choose another icon for the ROM
You can leave the partitions as they are (Schema LoopSystem + BindOther) Press the tab "PARTITIONS" and choose "LoopAll". You will see that the data partition is quite big (the g4 internal storage is just 23 GB so you choose a smaller size for each ROM to fit all your ROM slots).
Tip "data" and select GB in the drop down. Choose a proper size (i.e. 2 GB) depending on what you wanna do with that ROM and how many you wanna install (each ROM will take 4 GB for system + the data size you choose here)
In the tab "REPLACEMENTS" click the floating plus button and add a new cmdline override:
Code:
Name = androidboot.selinux
Value = permissive
press the tick in the top right corner to finish the setup
Now you can see your newly created ROM slot in the list
Reboot
Once you are in the efidroid, you can navigate around with volume down to go down, volume up to go up and the power button to confirm your selection.
To flash a ROM to the new empty slot, select TWRP (Internal) , press power and select the slot name with power again
At the moment the system partition is just empty and needs to be formatted before you can use it!
In TWRP:
select WIPE -> Advanced Wipe -> select "system" and "cache", then swipe to wipe.
select WIPE -> "Format Data" button
Reboot -> System. When you see efidroid again choose TWRP and select the new ROM slot again to boot TWRP again.
Install your ROM of your choice.
Hint: If you get an error regarding device detection you have to remove the assert line(s) within the ROM zip first
Supported devices
Any LG G4 model which can be unlocked (yea even UsU ones but that still requires some more work to detect them properly)
Known Issues
The Operating System list in the EFIDroid Manager is empty just upgrade to the latest EFIDroid manager app..
after installing a ROM it may bootloop under some circumstances
AROMA installer flickers extremely. Workaround: press power to turn off screen then turn it on again. It still flickers but u can see and use the installer at least.
As we need to use TWRP 3.1.1 (see requirements) UsU devices get not detected correctly!
The state of this project is ALPHA so expect issues and even data loss is possible (so do a TWRP backup often)
Booting a secondary ROM and working in a secondary ROM may feel slower (that's by design)
if a ROM has set selinux to enforcing it will not boot! --> If you setup the ROM slot properly (see above REPLACEMENTS tab) you do not need to care about.
Without that adjustment in the efidroid manager you have to modify the boot.img of every ROM:
change the cmdline from
androidboot.selinux=enforcing
to
androidboot.selinux=permissive
I started a while ago to make selinux policies for efidroid but it's not that easy and so atm no ROM which has selinux set to enforcing will boot.
Credits
@m11kkaa for EFIDroid
@J0SH1X for bringing a first port for the G4
@steadfasterX for being steadfast and optimizing efidroid
XDA:DevDB Information
EFIDroid for the LG G4, Tool/Utility for the LG G4
Contributors
steadfasterX, @m11kkaa, @J0SH1X
Source Code: https://github.com/steadfasterX/efidroid_device_lge_g4
Version Information
Status: Alpha
Created 2017-04-14
Last Updated 2018-12-17

Workarounds for known issues
1) random app crashes, settings do not persist on reboot
The reason is that file permissions get not set correctly on the bind mounted data partition.
So nothing can be stored there (or what get stored will be stored with the wrong perms).
When creating a new ROM slot it is important (atm) that you choose LoopAll .
This would create a data partition image with 23 GB which is way too much so you need to touch the data partition in the partitions tab and set the size to GB and choose e.g. 2 GB.
2) no WiFi
First boot TWRP internal / primary slot
Code:
adb shell cp /data/misc/wifi/config /external_sd/data_misc_wifi_config
Then for each slot you created you must reboot TWRP in its slot and:
Code:
adb shell cp /external_sd/data_misc_wifi_config /data/misc/wifi/config
adb shell chown system.wifi /data/misc/wifi/config
adb shell chattr +i /data/misc/wifi/config

Reserved

I tried to install Efidroid on my LG G4 (H815, bootloader unlocked, ResurrectionRemix 5.8.2). I install the App and modify the build.prop with the efidroid url, but every time i start the app i get the error-massage:
Error. Can't load device info. Please check your connection. No value for lge/h815.
Could you help me fixing this?

jokuu said:
I tried to install Efidroid on my LG G4 (H815, bootloader unlocked, ResurrectionRemix 5.8.2). I install the App and modify the build.prop with the efidroid url, but every time i start the app i get the error-massage:
Error. Can't load device info. Please check your connection. No value for lge/h815.
Could you help me fixing this?
Click to expand...
Click to collapse
Oh damn. I forgot to update the OTA for the other devices..
There is nothing you can do on your site atm.. Sorry I will fix it asap and let you know..
.
Sent from my LG-H815 using XDA Labs

still hard at it heck yea

jokuu said:
I tried to install Efidroid on my LG G4 (H815, bootloader unlocked, ResurrectionRemix 5.8.2). I install the App and modify the build.prop with the efidroid url, but every time i start the app i get the error-massage:
Error. Can't load device info. Please check your connection. No value for lge/h815.
Could you help me fixing this?
Click to expand...
Click to collapse
ok done. please try again
.

steadfasterX said:
ok done. please try again
.
Click to expand...
Click to collapse
Now it works. Thank you! :good:

ok .. im able to boot a LL based ROM now (Imperium ROM).. but only ONCE. lol..
Well I can boot into it again after booting in the TWRP version of that ROM and doing a factory reset from within TWRP...
Cleaning /data, /cache and dalvik cache manually does NOT work.. interesting. <-- I tested with a special (FIsH) TWRP version which does not WIPE but RM only.. Once I switched to a regular TWRP it is still strange but at least behaves the same now: When I wipe /data and /cache I can boot (but only when wiping both).
Update:
Keeping strange:
When I wipe /data only -> no boot
When I wipe /cache only -> no boot
When I wipe both -> boot ok .. wtf.?!
I will look into /misc - maybe the reason can be found here!
.

I just booted a second rom successfully using efi on my h811
My primary rom: lineage nougat
My secondary rom: resurrection remix (mm)
First boot was slow, second a little less slow, third and so on boot at normal speed.
Anyone else with an h811 care to try it coz @steadfasterX thinks mine booted coz i have an h811.
So if anyone else with an h811 can test it, that would help.
Btw, you all jelly? :victory:

Update: i have a complex sort of bootloop.
I decided to flash gapps.
Now when i try to boot the rom, i get the optimizing apps screen, then starting apps, then the boot logo, then again starting apps, and again boot logo and it goes on like that.
If i clear cache and dalvik i get the optimizing apps again, then the circle continues.
Maybe its gapps?
Or maybe its coz you all were too much jelly

tanveer7652 said:
Update: i have a complex sort of bootloop.
I decided to flash gapps.
Now when i try to boot the rom, i get the optimizing apps screen, then starting apps, then the boot logo, then again starting apps, and again boot logo and it goes on like that.
If i clear cache and dalvik i get the optimizing apps again, then the circle continues.
Maybe its gapps?
Or maybe its coz you all were too much jelly
Click to expand...
Click to collapse
heat

kevp75 said:
heat
Click to expand...
Click to collapse
Heat? What do you mean

tanveer7652 said:
Heat? What do you mean
Click to expand...
Click to collapse
I believe he thinks you have the ilapo because he don't know what efidroid is.
have you tried to wipe /data as mentioned (on IRC) ?
.

tanveer7652 said:
Heat? What do you mean
Click to expand...
Click to collapse
steadfasterX said:
I believe he thinks you have the ilapo because he don't know what efidroid is.
have you tried to wipe /data as mentioned (on IRC) ?
.
Click to expand...
Click to collapse
LOL I have a good idea with efidroid is
Everytime you wipe cache/dalvik your device has to rebuild the dalvik.
When your device rebuilds dalvik it has to work.. and work hard... as a result of the device working harder than normal, it generates heat. if it gets too hot, it will reboot.
I sometimes get it on a plain ol' stock rom

@steadfasterX im back to work on it just bought a new g4 today and currently im in unlock progress

J0SH1X said:
@steadfasterX im back to work on it just bought a new g4 today and currently im in unlock progress
Click to expand...
Click to collapse
Congrats. Please remember some of us poor guys when u buy another g4 ?
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
kevp75 said:
LOL I have a good idea with efidroid is
Everytime you wipe cache/dalvik your device has to rebuild the dalvik.
When your device rebuilds dalvik it has to work.. and work hard... as a result of the device working harder than normal, it generates heat. if it gets too hot, it will reboot.
I sometimes get it on a plain ol' stock rom
Click to expand...
Click to collapse
But it doesn't get hot.

kevp75 said:
LOL I have a good idea with efidroid is
Click to expand...
Click to collapse
oh that's good
kevp75 said:
Everytime you wipe cache/dalvik your device has to rebuild the dalvik.
When your device rebuilds dalvik it has to work.. and work hard... as a result of the device working harder than normal, it generates heat. if it gets too hot, it will reboot.
I sometimes get it on a plain ol' stock rom
Click to expand...
Click to collapse
tbh I don't think that this is the case here. We have bootloops when something changes in /data. This is not heat related. It is something efidroid related..

J0SH1X said:
@steadfasterX im back to work on it just bought a new g4 today and currently im in unlock progress
Click to expand...
Click to collapse
u like pain do u ?

steadfasterX said:
oh that's good
tbh I don't think that this is the case here. We have bootloops when something changes in /data. This is not heat related. It is something efidroid related..
Click to expand...
Click to collapse
theres software bootloop and hardware bootloop. i only get software when i install something or say remove gapps. or mess with system . flashing rom fix it..

Radio Rom NX563J Android 8.1

You can find latest radio on lineage 15.1 thread

aljoscha81 said:
So here i post new radios when the stock 8.1 will be updated feel free to test.It is maybe not the fact that something is changed in new radio but in changelog it is also point out that not every change from build to build is written in so testing testing testing.............. :fingers-crossed::highfive:
Ps. Sorry for my bad english
Radio v:5.42:https://mega.nz/#!iq5xgSZZ!J6uTZQ39enNcrWrCGIKofVEzxKti75Myb_VhJJVxl0s
Click to expand...
Click to collapse
Android 9? How you did it?

Deleted

Pie

Deleted

Deleted

It was released a new radio update 5.50

Deleted

aljoscha81 said:
Yes i am on latest build arrow os 9 treble rom i got nearly everything working only nfc don't work for me you must be on mokee 81 rooted with magisk 17.1 installed total commander delete with total commander in system/vendor/ lib and lib64 vndk-sp folder with all in it then create in system/vendor a folder called overlay in the overlay folder copy and past the apk from this thred :https://forum.xda-developers.com/pr.../overlay-enable-night-light-adaptive-t3741965
Then from terminal run this command first:
mount -o remount,rw /vendor
Then the command from the thread you got the apk. From
Restart
Then you flash twrp 3.2.3-3 in this forum you can find it
Wipe in advanced wipe everything format data make factory reset restart to twrp
Use otg device with extracted img. Of arrow os and choose img. Install choose system for where to install
After image is installed boot to system
Now you must install open gapps in twrp
The system will run crazy while you are not got a registred device but you can install device id apk. In device id apk tab google service framework tab copy tab on the message your device is not registred on custoum rom link log in with your gmail email and password in the row to put in you past what you before copyed in the id apk. And tab register a few reboots and the messaging will stop now in settings you see you can set up your phone and voila you on android p
Ps for camera is also a fix out there so face unlock also works
Click to expand...
Click to collapse
please share step by step

Deleted

Deleted

aljoscha81 said:
New update
Click to expand...
Click to collapse
Thanks

This should be the last update to come, right? Nubia themselves said they stop developing Android 8+ for Z17. Any luck with GPS tracking on last update (taking ~2 minutes until it can track you properely)?

Deleted

Deleted

Any radio more than 5.52?

Deleted

Deleted

[Guide]Magisk Modules Disabler for Modules gone wrong

Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/showthread.php?t=2239421
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel3xl.img
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
fastboot boot image-newpixel3xlRemove.img
This one should remove magisk and all modules, then reboot and magisk should reinstall itself (ask to install necessary binaries). This is what osm0sis uses to recover from failed flashes. See this post:
https://forum.xda-developers.com/pi...odules-disabler-booting-magisk-t3976625/page2
Images are in this common folder. Pick the appropriate image for your phone.
6-4-20
https://www.androidfilehost.com/?w=files&flid=313291

Looking forward to this, Tulsa. Will be a real lifesaver and game changer.

sliding_billy said:
Looking forward to this, Tulsa. Will be a real lifesaver and game changer.
Click to expand...
Click to collapse
It's official. It works.

Tulsadiver said:
It's official. It works.
Click to expand...
Click to collapse
You are going to make a lot of people (who "forget" to disable the modules before update) very thankful.

sliding_billy said:
You are going to make a lot of people (who "forget" to disable the modules before update) very thankful.
Click to expand...
Click to collapse
I'm one of those, lol! Also, with the nutty stuff I try, I will be able to get by without a factory reset all the time

Tulsadiver said:
I'm one of those, lol! Also, with the nutty stuff I try, I will be able to get by without a factory reset all the time
Click to expand...
Click to collapse
This link worked, but the one on the Pixel 3 page results in a Mega decryption key error.

sliding_billy said:
This link worked, but the one on the Pixel 3 page results in a Mega decryption key error.
Click to expand...
Click to collapse
I pasted it again. Hopefully it works now.

Tulsadiver said:
I pasted it again. Hopefully it works now.
Click to expand...
Click to collapse
It works!

Thank you!!!!

Latest magisk canary added an adb command to remove modules if bootlopps happens ?

DvLAx3l said:
Latest magisk canary added an adb command to remove modules if bootlopps happens
Click to expand...
Click to collapse
That's what I heard. Do you know the steps on how it works? You flash a module and you bootloop. What do you do next?

Tulsadiver said:
That's what I heard. Do you know the steps on how it works? You flash a module and you bootloop. What do you do next?
Click to expand...
Click to collapse
Didn't try yet, I was searching on topjohnwu GitHub but I don't find nothing, it's in the changelog but I don't know ?

DvLAx3l said:
Didn't try yet, I was searching on topjohnwu GitHub but I don't find nothing, it's in the changelog but I don't know
Click to expand...
Click to collapse
Well, if it's an ADB fix, a person is going to have to, at the very least, flash boot.img (though probably system images depending on what you flashed), reboot without root. Enable the ADB mode, flash ADB commands, and reboot. Remove bad modules. Then, go back and root again.
Seems simpler to just flash the modded image-new.img, reboot with root, remove modules (with ADB if you like) and reboot.
Edit: what would be cool is an option to patch a boot.img in core-only mode, right from Magisk manager, where the other option is to patch the boot.img. All that would be needed on John's part is an edited init file in that option. That's the only difference.

Thanks for this! I could've really used this image a few times in the past...

Face_Plant said:
Thanks for this! I could've really used this image a few times in the past...
Click to expand...
Click to collapse
You and me both, buddy!

Got in to a bootloop situation with Bromite systemless webview module. I restored stock boot image and patched it with the latest canary build (the one with 'recovery mode' checked under advanced settings) and bootlooped again. I flashed this file, got in with magisk working, disabled the offending module, patched the boot image without recovery mode, then flashed the patched boot image and everything is up and running! Thanks for the help!

Ok thanks for this but after rebooting from home screen even if I disable/remove bad mods from magisk I still get rr's/boot loops. Would I need to uninstall magisk completely then and start fresh or what?

Jiggs82 said:
Ok thanks for this but after rebooting from home screen even if I disable/remove bad mods from magisk I still get rr's/boot loops. Would I need to uninstall magisk completely then and start fresh or what?
Click to expand...
Click to collapse
Can you open magisk manager? If so, uninstall magisk from there.
If not, once booted in core-only mode, unzip the contents of this zip in a folder you can use ADB from and run the bat file. It'll push the .disable_magisk file to the cache folder and totally disable any module activity.

Tulsadiver said:
Can you open magisk manager? If so, uninstall magisk from there.
If not, once booted in core-only mode, unzip the contents of this zip in a folder you can use ADB from and run the bat file. It'll push the .disable_magisk file to the cache folder and totally disable any module activity.
Click to expand...
Click to collapse
Yes I was able to open magisk but even if I uninstalled it I still had this weird bootlloop so before I saw this message I ended up just flashing factory 10 image clean this time just to be sure everything would flash/install successfully and luckily they did lol but thanks anyways and I will hold onto to these files for future references:good:

would the modded boot img that disables modules work for the pixel 3 as well?