Related
I am a proud owner of OP One and SuperSu Pro. Currently i am using http://forum.xda-developers.com/oneplus-one/development/daily-stock-unofficial-cm12-builds-t2948099 ROM (as of today 15-12 build).
I installed SuperSU through TWRP 2.8 and used to work fine, untill i updated to a new CM12 build. Then i was promted to grand permissions to an app, but i could not press "grant", later opened the SuperSU app and got a message that there is no binary installed, so i tried to reflash the zip noumerous times, but it seems that TWRP is unable to flash the zip.I can flash other zips like new versions of the ROM, GAPPS etc.
It seems like TWRP is not able to flash the SuperSu zip, even though i get a "succesful" message while flashing. I tried cleaning Cache and Dalvik. Also i can't find the log created by TWRP which is suposedly created in data/media/0 so i can't post detailed info about it.
Super Su
There is no Su binary installed and SuperSu cannot install it. This is a problem.
...
Click to expand...
Click to collapse
I recently started playing pokemon go and I am getting really frustrated while playing because it lags soo much and my phone is generally quite slow now. I have been told rooting and installing a good ROM can help with this and I have never attempted this, could someone please explain what rooting and ROMs are and their benefits and a how to guide for this phone and also the best ROM?
I know there are loads of threads on this but if someone could link me best threads I would be eternally gratefull!!
First of all, which variant of LG L90 is your phone (D4xx)? And could you go to Menu > General > About Phone > Software Information and tell me your "version" (v10x or v20x)?
Root is the ability for the user to take total control of his phone, from doing as little as automate 3G activation when an app is open to instaling custom ROMs, which are custom firmwares that you can install in your device, just like the stock one you're currently in, but with some modifications made by its creators. As for advantages, with root you have more freedom over your device, and with Custom ROMs you have some tweaks, which change depending on the ROM you choose to install, going from just porting newer firmwares to older devices to being an entire new OS (Operational System, in case you don't know).
Hyoretsu said:
First of all, which variant of LG L90 is your phone (D4xx)? And could you go to Menu > General > About Phone > Software Information and tell me your "version" (v10x or v20x)?
Root is the ability for the user to take total control of his phone, from doing as little as automate 3G activation when an app is open to instaling custom ROMs, which are custom firmwares that you can install in your device, just like the stock one you're currently in, but with some modifications made by its creators. As for advantages, with root you have more freedom over your device, and with Custom ROMs you have some tweaks, which change depending on the ROM you choose to install, going from just porting newer firmwares to older devices to being an entire new OS (Operational System, in case you don't know).
Click to expand...
Click to collapse
Thank you soo much for your reply and sorry about my late reply. My variant is LG-D405n and software version is V20c-234-30. I think I understand what Root and ROM is thx.
So could you link me to the best method to root and install ROM on my phone?
And what is the best ROM for my device to free up the RAM and CPU used on my device to increase my phone speed?
First of all, install these required apps:
http://king.myapp.com/myapp/kdown/img/NewKingrootV4.9.6_C151_B309_en_release_2016_08_18_105203.apk (For rooting)
https://play.google.com/store/apps/details?id=com.cgollner.flashify (For flashing the Custom Recovery)
https://play.google.com/store/apps/details?id=jackpal.androidterm (For terminal emulation)
Custom Recovery:
TWRP: http://forum.xda-developers.com/devdb/project/dl/?id=18679&task=get
Personally recommended Custom ROM, CyanogenMod (Ports Android updates to older phones plus some tweaks) and Gapps (Google Apps, it's needed to have things like calculator, play store, etc):
CM13: https://download.cyanogenmod.org/get/jenkins/175208/cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J8-w7.zip
Gapps: http://opengapps.org/ (Go to this link, select ARM in platform, 6.0 in android and Nano in variant, then just click the download image button)
Put the TWRP img, the CM13 rom img and gapps on microSD or internal storage. Open Kingroot and click on the green button after the 3 introduction images. After a few minutes, your device will be rooted. Grab this file: http://forum.xda-developers.com/lg-...0w7xxshoxx-t2826150/post54358527#post54358527 (D405n_v20a_patched_aboot, don't worry, it's okay if you flash a different software version aboot as long as it's the same device as yours. The only "problem" you can have is to have your software version changed to v20c, which if I remember correctly, can be fixed using Bootstacks), transfer it to your phone and open Terminal Emulator. Then input the following commands:
su
dd if=(aboot.bin storage directory) of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Then, go to flashify and flash your custom recovery image (TWRP or CWM) in the flash recovery img option. After this, reboot into recovery by pressing Volume Down + Power and when you see the LG Logo, let go of the Power button and press it again. Then select yes two times with the volume keys for selection and power button to actually select the options (Don't worry, your device won't be factory resetted if you successfully installed custom recovery). Then, if you want, make a backup of your entire phone (recommended, just in case something goes wrong or if you just want your apps back when the process is done) in the Backup section and then do a factory reset through the Wipe option (Don't select anything, just swipe the bar). Select the Install option and select your ROM zip. After this, do the same process as the ROM installation but this time with Gapps zip. There you go, now you have CM13 installed. If you want root again, you don't have to install Kingroot again this time, as CM13 has built-in root, just enable Developer options and activate root and you're ready to go. Also, if you want the apps you had before the installation, just restore your backup (ONLY THE DATA PARTITION, otherwise CM13 will be uninstalled and replaced with stock ROM). If something goes wrong and you accidentally brick your device, just reply and I'll help you fix it. (If helped, click the Thanks! button)
Hyoretsu said:
Grab this file: http://forum.xda-developers.com/lg-...0w7xxshoxx-t2826150/post54358527#post54358527 (D405n_v20a_patched_aboot, don't worry, it's okay if you flash a different software version aboot as long as it's the same device as yours. The only "problem" you can have is to have your software version changed to v20c, which if I remember correctly, can be fixed using Bootstacks), transfer it to your phone and open Terminal Emulator. Then input the following commands:
su
dd if=(aboot.bin storage directory) of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
Click to collapse
Hi, thank you so much, I finally rooted my device but I am having problems with the script part of the terminal emulator.
I wrote upto msm_sd and then this happen automatically:
View attachment 3865360
View attachment 3865361
View attachment 3865362
View attachment 3865363
I don't know what to do here..
EDIT: Also am I meant to have the SuperSU/SuperUser app installed once rooted? Then get a popup in the terminal emulator for permission for its root access?
Firebird3334 said:
Hi, thank you so much, I finally rooted my device but I am having problems with the script part of the terminal emulator.
I wrote upto msm_sd and then this happen automatically:
View attachment 3865360
View attachment 3865361
View attachment 3865362
View attachment 3865363
I don't know what to do here..
EDIT: Also am I meant to have the SuperSU/SuperUser app installed once rooted? Then get a popup in the terminal emulator for permission for its root access?
Click to expand...
Click to collapse
You have to change "(aboot.bin storage directory) with the directory in which aboot.bin is stored. And no, you don't need SuperSU, when you use the su command, a KingRoot window will open, just say yes.
EDIT: Wahay! It works! Thank you soo much for your help!
EDIT 2: I can't seem to find the option to edit my recent button in settings. What can I do?
Firebird3334 said:
EDIT: Wahay! It works! Thank you soo much for your help!
EDIT 2: I can't seem to find the option to edit my recent button in settings. What can I do?
Click to expand...
Click to collapse
If it's the menu button, I don't know of any way to change them, as Android updates change them. For example, my phone in KitKat used the home button for recent apps, in Lollipop it used the menu button for recent apps, and when I installed CM13, it used the home button again.
EDIT: Browsing LG L90 xda, I found this: http://forum.xda-developers.com/lg-l90/themes-apps/mod-button-remaps-l90-t3145146
Hyoretsu said:
If it's the menu button, I don't know of any way to change them, as Android updates change them. For example, my phone in KitKat used the home button for recent apps, in Lollipop it used the menu button for recent apps, and when I installed CM13, it used the home button again.
EDIT: Browsing LG L90 xda, I found this: http://forum.xda-developers.com/lg-l90/themes-apps/mod-button-remaps-l90-t3145146
Click to expand...
Click to collapse
You have helped me out so much already! Thank you so much!
But just one more thing though, could you explain how to install magisk and xposed in layman's term so I can use Android Pay?
I don't know what magisk is nor layman's term, but to install Xposed just go to this thread: http://forum.xda-developers.com/showthread.php?t=3034811, download both Xposed installer apk and xposed zip. Install xposed apk and flash xposed zip
Hello,
Help me please I'm getting Error 7 and after twrp reflash Error executing updater binary in zip
I did all the previus steps phone LG L90 d405n is rooted and bootloader is unlocked and rom downgraded to KK v10b
Now I want to flash CM or RR rom but I simply can't!
First I was getting error 7 when flashing I found out that I need TWRP 2.8.7 build 2 to flash so I found it and flashed. Now I'm getting ''error executing updater binary in zip twrp'' and I can't flash any rom.?*
I tried deleting first assert lines in updater-script from this?*thread?*but It didn't helped in any way...
Any ideas? Why the hell it is so ****ing complicated to flash custom on this ****ty device? Can't it work like Nexus4 or any other normal device??*
Thanks in advance for any tips&trics
PS. I can't open new thread dunno why...
amonlb said:
Hello,
Help me please I'm getting Error 7 and after twrp reflash Error executing updater binary in zip
I did all the previus steps phone LG L90 d405n is rooted and bootloader is unlocked and rom downgraded to KK v10b
Now I want to flash CM or RR rom but I simply can't!
First I was getting error 7 when flashing I found out that I need TWRP 2.8.7 build 2 to flash so I found it and flashed. Now I'm getting ''error executing updater binary in zip twrp'' and I can't flash any rom.?*
I tried deleting first assert lines in updater-script from this?*thread?*but It didn't helped in any way...
Any ideas? Why the hell it is so ****ing complicated to flash custom on this ****ty device? Can't it work like Nexus4 or any other normal device??*
Thanks in advance for any tips&trics
PS. I can't open new thread dunno why...
Click to expand...
Click to collapse
First of all, you don't need to use that TWRP build, you can use the latest one. To fix the only errors that should appear (Updater error 7 and 6), delete the first lines of updater-script until you reach the ui_print part (the first line of your file should be "ui_print("Target: 1471683591");"). Also, delete any double spaces that exist (there should be two, one before "abort" at line 27 and the other before "abort" at line 30). If it still gives the same error, try wiping Cache, data, system and dalvik-cache partitions, try to install the ROM, it'll give the error. Now, reboot your phone and try to install without wiping anything. (To properly see the line indications, open the file using Notepad++)
Recently got a kindle fire 7" and wanted to root it and flash a rom onto it, but having troubles with that part.
Using this guide https://forum.xda-developers.com/amazon-fire/general/root-t3471289
Rom:
https://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714
Usb debugging/install from unknown sources/kingroot done
Process:
Stock firmware (5.3.1) after amazon recovery tool
Kingroot root
Supersu-me
Update su
Tried once with and without rebooting
Rootjunky super tool, installed google play store
Install Flashfire (from play store) ver. .55
Also tried with an apk file ^ (ver. .53)
Set up a wipe for (dalvik, system, 3rd party)
Tried with and without mounting
Crashes after and starts a boot loop going into the amazon logo only
I'm new in regards for rooting, sorry if I'm a bit slow with this.
Thanks in advance for the help!
Check the rom you downloaded is not corrupted, verify hash value. Store it on the tablet not an sd card when flashing.
Reboot the tablet after you install supersu and flashfire. Before you flash the rom, make sure you remove the usb cable.
Don't use auto mount. Make sure you follow the flashfire instructions below. Make sure to move wipe to top of the order !
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Mr McBoatface said:
Check the rom you downloaded is not corrupted, verify hash value. Store it on the tablet not an sd card when flashing.
Reboot the tablet after you install supersu and flashfire. Before you flash the rom, make sure you remove the usb cable.
Don't use auto mount. Make sure you follow the flashfire instructions below. Make sure to move wipe to top of the order !
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Click to expand...
Click to collapse
Still nothing, leads me into another boot loop.
New things:
Rebooted after installing flash fire
Verified the hash
Move the rom onto the internal drive (flashed from there)
No Automount
Any other ideas?
IIRC, I had similar issues when first installing a ROM onto my Fire, but that was many months ago, and my memory is a bit fuzzy... IIRC, it had to do with the location of the ZIP. I believe I had to put the zip on my SD card, and then when I wiped my system, I also wiped my data volume. Speaking of wiping...
Shugumi said:
Process:
Stock firmware (5.3.1) after amazon recovery tool
Kingroot root
Supersu-me
Update su
Tried once with and without rebooting
Rootjunky super tool, installed google play store
Install Flashfire (from play store) ver. .55
Also tried with an apk file ^ (ver. .53)
Set up a wipe for (dalvik, system, 3rd party)
Click to expand...
Click to collapse
Maybe I'm reading this wrong, but are you saying you're installing the zip, and THEN wiping the system? That's going to erase the installation you just flashed. You should be wiping the system, and THEN flashing the zip. The original instructions are here:
ggow said:
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Click to expand...
Click to collapse
IIRC, if you put the ZIP onto the internal storage, it puts it in the Data volume, which is then going to be wiped. FF wipes the data, and then can't find the zip (because it just deleted everything...). Does that make sense?
crazyates said:
IIRC, I had similar issues when first installing a ROM onto my Fire, but that was many months ago, and my memory is a bit fuzzy... IIRC, it had to do with the location of the ZIP. I believe I had to put the zip on my SD card, and then when I wiped my system, I also wiped my data volume. Speaking of wiping...
Maybe I'm reading this wrong, but are you saying you're installing the zip, and THEN wiping the system? That's going to erase the installation you just flashed. You should be wiping the system, and THEN flashing the zip. The original instructions are here:
IIRC, if you put the ZIP onto the internal storage, it puts it in the Data volume, which is then going to be wiped. FF wipes the data, and then can't find the zip (because it just deleted everything...). Does that make sense?
Click to expand...
Click to collapse
Had the zip on storage and wiped before flash, nothing :/
Was kingroot fully removed and SuperSU correctly installed ? Are you using the latest nexus ROM dated Feb 2017 ?
Try again this time use fire flash 0.53 included in super tools. Don't install play store or upgrade SuperSU, use the SuperSU included in super tools. Again make sure you restart the tablet after installing SuperSU and after installing fire flash.
With flashfire 0.53 make sure automount is deselected. Include wipe cache options too.
So wipe System data, 3rd party apps, Dalvik cache and cache , flash the nexus ROM. Again make sure before you hit the flash button the wipe action is moved to the top of the list. Make sure no USB cable connected to the device too
In my experience 0.53 flashes really quick , 0.55.1 "can" show a black screen, you might think its failed but it's working in the background but might take 5 mins to flash.
0.53 sometimes fails to open and crashes but i have only seen that when it was used on a device with a custom ROM already flashed on it. It should be fine for flashing on the fire OS system.
Mr McBoatface said:
Was kingroot fully removed and SuperSU correctly installed ? Are you using the latest nexus ROM dated Feb 2017 ?
Try again this time use fire flash 0.53 included in super tools. Don't install play store or upgrade SuperSU, use the SuperSU included in super tools. Again make sure you restart the tablet after installing SuperSU and after installing fire flash.
With flashfire 0.53 make sure automount is deselected. Include wipe cache options too.
So wipe System data, 3rd party apps, Dalvik cache and cache , flash the nexus ROM. Again make sure before you hit the flash button the wipe action is moved to the top of the list. Make sure no USB cable connected to the device too
In my experience 0.53 flashes really quick , 0.55.1 "can" show a black screen, you might think its failed but it's working in the background but might take 5 mins to flash.
0.53 sometimes fails to open and crashes but i have only seen that when it was used on a device with a custom ROM already flashed on it. It should be fine for flashing on the fire OS system.
Click to expand...
Click to collapse
I might disagree with a few things you said there...
You only have to remove KingRoot if you're using v5.0 or newer. If you can use 4.9.6 to root, which I believe is what the SuperTool uses, then you can download SuperSu from the play store, update SU binary, then uninstall KingRoot with no issues.
As far as FF is concerned, the ROM developer says 0.55.1 is required, so I wouldn't stray from that.
The only other thing I would recommend is using the not-newest version of the ROM. For the last 6 months, the ROM has been based on a 5.3.2 boot.img, and recently switched to a 5.1.4 boot.img. Maybe the newer firmwares don't like the downgrade? I would try the Feb-2-2017 version of the ROM and try again.
Steps:
Restore to stock 5.3.2 (NOT 5.3.2.1)
SuperTool to install KingRoot 4.9.6 & GPlay
Kingroot to root
Install SuerSU (newest) & FF (newest) from Gplay
Use SuperSu to update SU binary
Put Feb-2-2017 zip on SD card
Use FF to wipe System, Data, Cache, Dalvik, 3rd party apps, & then install zip from SD.
Let sit for 5-10 minutes & do it's thing.
Having 2 root managers is not a good idea.
Kingroot uses it's own su binaries which may cause problems and clash with SuperSU. Using the script in supertools is a better option as it replaces the superuser su binary with a SuperSU compatible one.
The version of flashfire shouldn't matter, but he is having issue so best to rule it out. The behavior of 0.53 is different to 0.55.1 . it flashes a lot quicker and is fine to use. I've used it several times in the last fortnight with the latest ROM.
The current ROM is fine, boot image and binary change won't cause the issue experienced here. The older ROMs are broken , in so far as either the camera or screen cast won't work. The latest ROM with the proven and stable binary is a better option, everything works
EDIT , also there are reports of several users losing supersuser seemingly random after upgrading to the latest SuperSU , hence why I suggested sticking with the current one on supertools.
I also suggested wiping cache, just incase an amazon update has downloaded while rooting and attempts to install at the same time at the nexus ROM is being flashed.
I have a Fire running Nexus Fire ROM (2/8/17), and my fiance has a Fire running stock 5.1.2 with root, OTA updates disabled, Nova Launcher, and Gplay Store. I wanted to flash hers from Stock to Fire Nexus, and ran into the same issues I had before.
FF was supposed to Wipe System Data, 3rd party apps, Dalvik, and Cache, then install zip, then inject SuperSU. When it did the wipe, it deleted the ZIP on the Internal Store, so FF sat there for 15 minutes not doing anything, and I didn't have a system to reboot into anymore.
I had to do a sideload recovery of 5.1.2, root, install FF, and do all the same steps as above, but this time install the zip from an SD card. Worked great.
Mr McBoatface said:
Kingroot uses it's own su binaries which may cause problems and clash with SuperSU. Using the script in supertools is a better option as it replaces the superuser su binary with a SuperSU compatible one.
Click to expand...
Click to collapse
I used the SuperTool to root, and this is what I did also. Afterwards, I used the Gplay to update the SuperSU, which updated to the newest binary. I haven't seen any problems as of yet.
Unless internal storage was selected that shouldn't have happened, unfortunate that it did for you. The only time I've seen FF hang was when wipe was in the wrong order or when the USB cable was connected..... Don't know why the USB cable has that effect but I've seen it on 2 devices, other people have not had any problems.
Not seen the issue with SuperSU myself but read plenty of reports about it.
It seems users are affected by several random issues even if following the same instructions.
@Shugumi any update ?
Been swapping out roms and trying each suggestion but its been giving me the same boot loop.
So, I returned the kindle fire, and am waiting to try it on the new coming device :/, but thanks to everybody that replied to this thread. Even though we didn't get to root my kindle, it was great help! Thanks everybody.
So I have everything required to install SuperSU, i even got the Config just in case
and when i flash the zip file using TWRP it says that the installation was completed with no errors
when i reboot i find out that my devices isn't rooted.
So i tried again with flashing the config, same issue
Then I installed the SuperSU app from google play, then tried flashing the zip file and when i reboot, the app was deleted and same thing. No Root
Need help
Hello everybody.
I've read that 18.1 supports 4.2+ so I've tried to install in two MTK6589T devices I've. One running 4.2, the other running 4.4
CMW/TWRP gave an error mounting system, so I mounted system manually and it started flashing. Firstly it detected old root installed and disabled the old root. But when it tried to find the boot, installation was aborted because installator claims cannot find the boot on both phones.
Then I though, okay, lets reboot back to android, I will try to install a few days later, maybe its buggy now, but both phones cannot boot.
I can easily fix them by flashing rom again I guess, but I would like to know where's the issue and also post it for more people could face the same problem.
Any idea where's the problem/how to fix without rom reflashing? I've tried magisk uninstaller but after mounting system in recovery it is also giving error.
Thanks
UPDATE: For now, if no other solution is found, bootloop can be bypassed by dirty installing the rom again. But it has to be an easier workaround...
We know now that the problem is caused because of two factors merging:
1- Using Magisk.zip installer through custom recovery
2-In the case that the custom recovery CMW/TWRP installed in the phone is very old (for instance, CMW automade for MTK6589X or TWRP 2.5.0).
While installing, Magisk tries to send commands to the custom recovery that cant be understood by it, leaving the installation incomplete after some modifications in /system (read below recovery log).
Acording to the recovery, it seems that Magisk did some modifications without running correctly survival script - Adding addon.d survival script ("Unrecognized option '-Xnodex2oat'") and .zip installer is not designed to revert actions in this case.
Also, Magisk couldn't reach the boot modification step, so boot is not damaged, therefore workarounds for restoring boot won't work.
Using Magisk Unistaller.zip is also not possible as the uninstaller is mainly designed for boot backup restoration, and again, this is not the case.
Currently needed: Find what's wrong in system due to the incomplete Magisk installation to revert it back to the original state (before faulty magisk.zip installation).
Recovery log:
************************
* Magisk v18.1 Installer
************************
- Mounting /system, /vendor
- Target image: /dev/bootimg
- Device platform: arm
- Removing system installed root
- Constructing environment
- Adding addon.d survival script
Unrecognized option '-Xnodex2oat'
up!
I' also having the same problem. My Samsung J2 Prime stuck at logo after updating to 18.1. Any tips on how to fix it without resetting my phone? Thanks.
Update: Bootloop fixed. I used TWRP to restore boot image. I then update Magisk by flashing zip file from TWRP. Everything went back to normal. Hope this help.
trol_sg said:
Hello everybody.
I've read that 18.1 supports 4.2+ so I've tried to install in two MTK6589T devices I've. One running 4.2, the other running 4.4
CMW/TWRP gave an error mounting system, so I mounted system manually and it started flashing. Firstly it detected old root installed and disabled the old root. But when it tried to find the boot, installation was aborted because installator claims cannot find the boot on both phones.
Then I though, okay, lets reboot back to android, I will try to install a few days later, maybe its buggy now, but both phones cannot boot.
I can easily fix them by flashing rom again I guess, but I would like to know where's the issue and also post it for more people could face the same problem.
Any idea where's the problem/how to fix without rom reflashing? I've tried magisk uninstaller but after mounting system in recovery it is also giving error.
Thanks
Click to expand...
Click to collapse
If you have a backup of your boot image, you can just restore it using TWRP. But in case that you have no backup of boot image, you can try to get boot image from the internet and restoring using it. In my case, this is what I did.
1. Go to TWRP and then make backup of boot image of the faulty phone*. (Folder 1)
2. I used another J2 prime to create a boot image backup. (Folder 2)
3. Once that is done, copy and replace the files inside the Folder 2 into Folder 1.
4. Reboot to TWRP again then use that to restore the boot image on my stuck J2.
Tips: make backup in SD card so you can easily swap it in between the bad and good phone.
*This is to create a folder of the backup file. I did tried to directly copy and paste the backup boot image file from another good phone but TWRP didn't detect it. So this is the workaround that I come with. And it worked for me.
Thanks for your answer but I doubt your case is mine. Your device is much newer than mine and according to your comment, you've sucesfully installed previous version of Magisk without issues. This is not a problem while updating, as Magisk v. earlier than 18.1 was not compatible with android 4.2+. I think Magisk is not compatible with MT6589T even if they run 4.2 or 4.4.
I think that it cannot be a boot problem as TWRP/CWM displayed msg 'Boot cannot be found' while installing Magisk, so that I don't think boot was replaced or modified in any ways. Moreover, the bootloop is not in the boot loading, as phone can pass boot image without any problem, but it is stuck in android loading image. I'm thinking in some script or root modification that Magisk did before trying to unpack the boot, however I'm not that deep into the Magisk install to find the proper workaround.
I can restore boot backup and also I can take boot file from the original rom and flash, because in Mediatek-based devices, boot.img is inside de zip, but I dont think it will solve the problem. Anyhow I'll get back ASAP with the answer.
Any more ideas??
Nothing, boot/uboot restoration or flashing again just the boot won't fix the problem, so it's something that Magisk installator touch in /system or /data I guess, but what?
trol_sg said:
Nothing, boot/uboot restoration or flashing again just the boot won't fix the problem, so it's something that Magisk installator touch in /system or /data I guess, but what?
Click to expand...
Click to collapse
Have you read/tried this?
didgeridoohan(dot)com/magisk/MagiskIssues
Ato09 said:
Have you read/tried this?
didgeridoohan(dot)com/magisk/MagiskIssues
Click to expand...
Click to collapse
Yes, I've read them before I made the post. I've also looked for a solution in some of the threads and using search, but couldn't find a way.
Here I attach recovery.log if someone is interested to see the detailed problem.
Also, here below I attach the lines concerning the installation. All other is uninstallation tries and so on:
************************
* Magisk v18.1 Installer
************************
- Mounting /system, /vendor
- Target image: /dev/bootimg
- Device platform: arm
- Removing system installed root
- Constructing environment
- Adding addon.d survival script
Unrecognized option '-Xnodex2oat'
dalvikvm: [options] class [argument ...]
dalvikvm: [options] -jar file.jar [argument ...]
The following standard options are recognized:
-classpath classpath
-Dproperty=value
-verbose:tag ('gc', 'jni', or 'class')
-ea[:<package name>... |:<class name>]
-da[:<package name>... |:<class name>]
(-enableassertions, -disableassertions)
-esa
-dsa
(-enablesystemassertions, -disablesystemassertions)
-showversion
-help
The following extended options are recognized:
-Xrunjdwp:<options>
-Xbootclasspath:bootclasspath
-Xcheck:tag (e.g. 'jni')
-XmsN (min heap, must be multiple of 1K, >= 1MB)
-XmxN (max heap, must be multiple of 1K, >= 2MB)
-XssN (stack size, >= 1KB, <= 256KB)
-Xverify:{none,remote,all}
-Xrs
-Xint (extended to accept 'ortable', ':fast' and ':jit')
These are unique to Dalvik:
-Xzygote
-Xdexopt:{none,verified,all,full}
-Xnoquithandler
-Xjniopts:{warnonly,forcecopy}
-Xjnitrace:substring (eg NativeClass or nativeMethod)
-Xstacktracefile:<filename>
-Xgc:[no]precise
-Xgc:[no]preverify
-Xgc:[no]postverify
-Xgc:[no]concurrent
-Xgc:[no]verifycardtable
-XX:+DisableExplicitGC
-X[no]genregmap
-Xverifyopt:[no]checkmon
-Xcheckdexsum
-Xincludeselectedop
-Xjitop:hexopvalue[-endvalue][,hexopvalue[-endvalue]]*
-Xincludeselectedmethod
-Xjitthreshold:decimalvalue
-Xjitcodecachesize:decimalvalueofkbytes
-Xjitblocking
-Xjitmethod:signature[,signature]* (eg Ljava/lang/String\;replace)
-Xjitclass:classname[,classname]*
-Xjitoffsetffset[,offset]
-Xjitconfig:filename
-Xjitcheckcg
-Xjitverbose
-Xjitprofile
-Xjitdisableopt
-Xjitsuspendpoll
Configured with: debugger profiler hprof jit(armv7-a-neon) smp show_exception=1
Failed to initialize runtime (check log for details)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/dev/bootimg]
No boot image magic found!
! Unable to unpack boot image
- Unmounting partitions
E:Error executing updater binary in zip '/sdcard/Magisk-v18.1.zip'
Error flashing zip '/sdcard/Magisk-v18.1.zip'
@trol_sg I'm gonna guess it's got to do with the absolutely ancient TWRP you're using. It just can't handle everything that the Magisk installation script is trying to do...
Your best bet (if Magisk will work at all on your device) is to patch the boot image with the Magisk Manager and then flash the patched image manually. There are new and shiny installation instructions available here: https://topjohnwu.github.io/Magisk/
Didgeridoohan said:
@trol_sg I'm gonna guess it's got to do with the absolutely ancient TWRP you're using. It just can't handle everything that the Magisk installation script is trying to do...
Your best bet (if Magisk will work at all on your device) is to patch the boot image with the Magisk Manager and then flash the patched image manually. There are new and shiny installation instructions available here: https://topjohnwu.github.io/Magisk/
Click to expand...
Click to collapse
Thank you so much for your answer. So it's the recovery, but can't find newer ones, sadly. Too old phones I know, but just curious if I could make Magisk working on them, lol.
I was going into the boot modification manually right now, but in order to patch the boot I need manager installed first, and phone couldn't boot so I did dirty flash of the rom to be able to boot into it again.
Lets see what happens then. I'll be right back.
Anyhow, this is not a solution to fix the problem of bootloop that I am requesting help in case someone could face the same and did not make a backup of the phone and didn't want to make dirty re-flash. Any idea?
Update: After I did dirty flash of the rom, and now Jiayu g3s android 4.4 booted.
UPDATE: So, after patching manually boot and installing (using restore in TWRP 2.5 as image flash is not yet implemented AFAIK), phone booted and yes Magisk is working.
Magisk installation .zip through a very old recovery is making the bootloop. So that, a thing learnt now.
But, for other people facing this bootloop, can we do a research to find what magisk.zip did to the phones to leave them in bootloop? Maybe we can revert without rom flashing easily if we knew what's the issue...
Thanks in advance!
Doing a bit more tests I found that magisk.zip did something in /system so that it is left in bootloop, but still no idea why/whats causing that...
There are delay complete boot like 4 5 second in j7 prime. I didn't love this version
any more help?? up!!
trol_sg said:
Yes, I've read them before I made the post. I've also looked for a solution in some of the threads and using search, but couldn't find a way.
Click to expand...
Click to collapse
Try this.
Quote:
Originally Posted by void74
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
Quote:
Originally Posted by Mangraviti
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
-------------
Original post. https://forum.xda-developers.com/apps/magisk/bootloop-magisk-update-t3836904
Hope it help.
Ato09 said:
Try this.
Quote:
Originally Posted by void74
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
Quote:
Originally Posted by Mangraviti
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
-------------
Original post. https://forum.xda-developers.com/apps/magisk/bootloop-magisk-update-t3836904
Hope it help.
Click to expand...
Click to collapse
Hello, thanks
This method won't work in my case as in the step:
- installed magisk uninstall = gives error
Note 5 is much newer phone with a recent recovery TWRP that allows all Magisk.zips commands, but unluckyly not this case.
Also, this method is for wrong boot installation/damaged boot. In my case what Magisk damage is /system, not boot.
I wish it could be boot, because that is very easy to fix (flashing through fastboot/SP Flash tools in the case of MTK, recovering boot twrp "backup" even if you didn't make backup...) as you mentioned.
Hope someone have a great idea to revert system to origin, then we could post the solution for those who would like to install Magisk in 4.2+ old phones, and instead of doing boot flash manually, they try to flash magisk.zip and they got bootloop.
Main post updated with all thread information. Up!
Nothing?? Up!!
trol_sg said:
Hope someone have a great idea to revert system to origin, then we could post the solution for those who would like to install Magisk in 4.2+ old phones, and instead of doing boot flash manually, they try to flash magisk.zip and they got bootloop.
Click to expand...
Click to collapse
The only part of the Magisk installation that actually touches /system is if it installs the addon.d survival script. The log you posted earlier shows that it's trying to do this, for some reason, and failiing. I'd start looking there...