Related
I've noticed that everytime I restore a backup or flash a new kernel i lose both the supersu root and my busybox install. This wouldn't be a huge issue but, It is very difficult to get busybox installed, most times it just crashes my device or says install failed.
Anyone else having issues like this?
ChasedMonkey said:
I've noticed that everytime I restore a backup or flash a new kernel i lose both the supersu root and my busybox install. This wouldn't be a huge issue but, It is very difficult to get busybox installed, most times it just crashes my device or says install failed.
Anyone else having issues like this?
Click to expand...
Click to collapse
Flashing a kernel should for sure not overwrite system. If you are using cwm use twrp as it is far superior. Do not wipe system.
123421342 said:
Flashing a kernel should for sure not overwrite system. If you are using cwm use twrp as it is far superior. Do not wipe system.
Click to expand...
Click to collapse
I haven't been wiping system. It doesn't exactly remove supersu, it just breaks it. It asks to update, then the update fails and forces me to re flash.
I am on a stock rom, rooted with twrp. I downloaded the 4.4.3 update ota but when rebooting it went to twrp and I did not know how to proceed so I booted to system. The update did not apply and I am still on 4.4.2
Now I cannot download the update again as it says I have the latest version.
Please tell me how I can get 4.4.3
Thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
goodboy1 said:
I am on a stock rom, rooted with twrp. I downloaded the 4.4.3 update ota but when rebooting it went to twrp and I did not know how to proceed so I booted to system. The update did not apply and I am still on 4.4.2
Now I cannot download the update again as it says I have the latest version.
Please tell me how I can get 4.4.3
Thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
First make sure you have the latest twrp, then boot into it, flash the ota zip from inside twrp, the ota zip is located in /cache...be sure to wipe cache and dalvik before restarting.
Many thanks for the prompt response. Unfortunately, when I try and install the update I get a message
Unexpected Content in system/app/iWnnIME.apk
Many thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
Me too!
I am having the exact same problem. I got a notice that an update was available but when i did the update via TWRP, it rebooted and i was still on 4.4.2. It thinks i already updated so say's I am already up to date when i check for updates again..
So i downloaded the 4.4.3 update zip file from somewhere and put in on my SDcard. Then went into TWRP to install it and it complains that /system/app.Videos.apk has unexpected contents - WTF??? Then aborts. Why is a simple update so damn problematic?
Am i out of luck? I don't want to have to wipe my tablet and start over.
James
goodboy1 said:
Many thanks for the prompt response. Unfortunately, when I try and install the update I get a message
Unexpected Content in system/app/iWnnIME.apk
Many thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
brandypuff said:
I am having the exact same problem. I got a notice that an update was available but when i did the update via TWRP, it rebooted and i was still on 4.4.2. It thinks i already updated so say's I am already up to date when i check for updates again..
So i downloaded the 4.4.3 update zip file from somewhere and put in on my SDcard. Then went into TWRP to install it and it complains that /system/app.Videos.apk has unexpected contents - WTF??? Then aborts. Why is a simple update so damn problematic?
Am i out of luck? I don't want to have to wipe my tablet and start over.
James
Click to expand...
Click to collapse
Both of you modified /system, you must dirty flash your stock system.img then flash the ota. Additionally, if you are using a custom kernel, you will probably have to flash the stock boot.img as well.
And both if you, don't forget to do a nandroid first!
By dirty flash if you mean wipe Dalvik and cache, i did that and then tried reflashing the update but it failed again.
James
brandypuff said:
By dirty flash if you mean wipe Dalvik and cache, i did that and then tried reflashing the update but it failed again.
James
Click to expand...
Click to collapse
No, what I mean is you need your system.img (and boot.img if you use a custom kernel) from the stock rom, then you need to flash that over your /system and /boot respectively, then flash the OTA, then wipe cache and dalvik.
And both if you, don't forget to do a nandroid first!
Updated!
Bought my Nexus recently and it was android 4.3 [Dad bought it in US and forgot to check the version)
I got the OTA update to 4.4.2 a few days back but it didnt install though it finished downloading. After trying all methods, i decided to do it with Nexus Root Toolkit. But to my surprise, NRT had the 4.4.3 stock img already! I flashed it and my Tablet is smooth. No problems noted till now. If you want me to check whether a particular app is working in 4.4.3 properly or not, let me know. I will test it and tell you
mdamaged said:
No, what I mean is you need your system.img (and boot.img if you use a custom kernel) from the stock rom, then you need to flash that over your /system and /boot respectively, then flash the OTA, then wipe cache and dalvik.
And both if you, don't forget to do a nandroid first!
Click to expand...
Click to collapse
Hmm..I don;t remember removing video.apk but i may have done some house cleaning awhile back. i know i don't have a backup of it anywhere. Since I'm not running a custom kernel, i just need to flash razor-kot49h-factory-ebb4918e.tar, wipe dalvik and cache and then the update and then the update should work ok? will i lose any of my installed apps after flashing the factory image? I'm assuming this puts it back to the original out of the box OS.
Actually, if that's the case that I will lose everything, why can't i just flash the factory image 4.4.3 (KTU84L) directly?
James
brandypuff said:
Hmm..I don;t remember removing video.apk but i may have done some house cleaning awhile back. i know i don't have a backup of it anywhere. Since I'm not running a custom kernel, i just need to flash razor-kot49h-factory-ebb4918e.tar, wipe dalvik and cache and then the update and then the update should work ok? will i lose any of my installed apps after flashing the factory image? I'm assuming this puts it back to the original out of the box OS.
Actually, if that's the case that I will lose everything, why can't i just flash the factory image 4.4.3 (KTU84L) directly?
James
Click to expand...
Click to collapse
No, no, no, extract system.img from this zip, then fastboot flash them.
i.e.:
fastboot flash system system.img
...then flash the OTA, then wipe cache and dalvik.
This process will revert system to stock, thus allowing the update to work. It will not wipe data, but any changes you made to /system will be gone, you will have to reapply those changes.
You did not ask, but I use MultiROM, and I will flash a new version to a secondary, then use titanium on app data, then boot into the new secondary, make whatever changes I need to, once I am fine with how it works, I then migrate my data to it, then use the swap ROM function in MultiROM. The whole OTA thing is a PITA when you modify too much of the system.
mdamaged said:
No, no, no, extract system.img from this zip, then fastboot flash them.
i.e.:
fastboot flash system system.img
...then flash the OTA, then wipe cache and dalvik.
This process will revert system to stock, thus allowing the update to work. It will not wipe data, but anychanges you made to /system will be gone, you will have to reapply those changes.
Click to expand...
Click to collapse
Thank you very much!
I will try this.
James
I fought with the Nexus 7 {2013} 4.4.3 update for a good day and a half. Tablet rooted with xposed modules , etc. Same messages you got.
Found that this method works very easily and preserves all data. Takes a few minutes to accomplish, then just one minute to reroot. Try this, it works:
http://nexus5.wonderhowto.com/how-t...ndroid-4-4-3-without-losing-any-data-0155334/
sucess
OK, I was able to update successfully.
I copied down the factory razor 4.4.2 kot49h image from google and extracted the tar file using cygwin's tar because winzip was giving me errors reading the tar file. Once i extracted the contents, i used ext4_unpacker to extract the system folder. I then copied videos.apk to the system\app directory using a the File Manager App and provided the correct RW attributes.
I tried the upgrade again but got an error this time about system\bin\app_process. I searched the web and realized that i need to uninstall the Xposed framework. Then i tried the upgrade again. this time it worked. I wiped dalvik/cache and rebooted. However, now I've lost root and need to remember how i rooted initially.
Thanks all.
James.
brandypuff said:
OK, I was able to update successfully.
I copied down the factory razor 4.4.2 kot49h image from google and extracted the tar file using cygwin's tar because winzip was giving me errors reading the tar file. Once i extracted the contents, i used ext4_unpacker to extract the system folder. I then copied videos.apk to the system\app directory using a the File Manager App and provided the correct RW attributes.
I tried the upgrade again but got an error this time about system\bin\app_process. I searched the web and realized that i need to uninstall the Xposed framework. Then i tried the upgrade again. this time it worked. I wiped dalvik/cache and rebooted. However, now I've lost root and need to remember how i rooted initially.
Thanks all.
James.
Click to expand...
Click to collapse
Just download the newest SuperSU and flash it from recovery. Then install busybox from playstore.
I had to uninstall xposed, re enable all apps. Recovery, install update in cache, wipe cache dalvik, reboot, reboot to recover flash su, boot, install supersu, reboot to TWRP and boot then reinstall xposed.
Yep if you're unlocked and rooted it can be done without a computer but it's way slower!
Sent from my Nexus 7 using Tapatalk
Thank you everyone. I used the nexus toolkit suggested a few posts back and everything works.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I am having a similar issue where the error that pops up for me says "/system/bin/app_process has unexpected contents". I tried uninstalling xposed and gravity box but that didn't help. Help?
mccartad said:
I am having a similar issue where the error that pops up for me says "/system/bin/app_process has unexpected contents". I tried uninstalling xposed and gravity box but that didn't help. Help?
Click to expand...
Click to collapse
How did you uninstall xposed? If you did so the way you normally uninstall apps, you did it the wrong way. You should have uninstalled it from within xposed. I think you can still fix it by reinstalling xposed and doing it the right way.
mdamaged said:
How did you uninstall xposed? If you did so the way you normally uninstall apps, you did it the wrong way. You should have uninstalled it from within xposed. I think you can still fix it by reinstalling xposed and doing it the right way.
Click to expand...
Click to collapse
Holy shnikies it worked! Thanks so much!
mdamaged said:
No, no, no, extract system.img from this zip, then fastboot flash them.
Click to expand...
Click to collapse
can anyone please confirm that this is a flashable .zip of a full stock Kit Kat 4.4.3. or can anyone point me to one. - thanks :cyclops:
I have the AT&T version, but I did S-Off, converted to the Dev Edition (CID BS_US002) and now have the stock recovery back on because I'm trying to apply the OTA update which provides a patch to the GPS.
I've applied a previous OTA successfully (after I went back to a stock recovery, of course).
But this time, it fails partway through and shows the red triangle with exclamation point. I was able to boot the phone to Recovery and do a Vol+ & Power which enabled me to select a handful of different options, chose to do the option of installing an OTA .zip file. Anyways I browsed to the OTA file in internal phone storage, executed it and it stops and fails on the following message: "cimext9.odex has unexpected contents". I am stumped because Google couldn't help. But, something similar happened to another person and they had installed Adaway which must have changed system files. I did have AdblockPlus installed for a while but uninstalled it - so could ABP be the culprit, and now what are my options that would enable this OTA to get installed on my phone?
Thanks in advance. Still learning, appreciate the help this board has provided me so far.
I had the same issue with this update, even though previous ones had installed fine. I didn't have adaway installed and never found out what was causing my issue, in the end I flashed a clean .3 and done the update, which installed fine. Then I used Helium to install all my app data and rooted it after that. Had to setup all my root apps again but now running .4
It looks like I'm going to have to flash the stock ROM again because something apparently isn't stock anymore.
Can I do this but keep the apps installed, contacts, music/files, etc? Or does it go back to factory reset?
When I done it i had to install all my apps and stuff again but there might be a way of saving all your stuff, someone else might be able to help you with that, I haven't had an android device that long
oaklandm said:
I had the same issue with this update, even though previous ones had installed fine. I didn't have adaway installed and never found out what was causing my issue, in the end I flashed a clean .3 and done the update, which installed fine. Then I used Helium to install all my app data and rooted it after that. Had to setup all my root apps again but now running .4
Click to expand...
Click to collapse
Thanks. This will show my ignorance, but by flash the .3, do you mean get the .3 OTA and flash that in the stock recovery, or do you mean grab a .3 nandroid backup?
oaklandm said:
I had the same issue with this update, even though previous ones had installed fine. I didn't have adaway installed and never found out what was causing my issue, in the end I flashed a clean .3 and done the update, which installed fine. Then I used Helium to install all my app data and rooted it after that. Had to setup all my root apps again but now running .4
Click to expand...
Click to collapse
oaklandm said:
When I done it i had to install all my apps and stuff again but there might be a way of saving all your stuff, someone else might be able to help you with that, I haven't had an android device that long
Click to expand...
Click to collapse
Yeah I do not have THAT much, but I've done this a few times and have things just the way I like them. Oh well.
us3rnotfound said:
Thanks. This will show my ignorance, but by flash the .3, do you mean get the .3 OTA and flash that in the stock recovery, or do you mean grab a .3 nandroid backup?
Click to expand...
Click to collapse
I meant grab the nandroid backup, don't know if just a factory restore from the menu would do the job. I just thought that if I'm starting from scratch then I might as well flash .3 : )
D85120G-Untouched_Stock_Restore.zip
Flash Full Stock (system/kernel/modem/recovery) No Root, No Mods, 100% Stock
Thanks.
Since this is the full rom, not OTA, has anyone successfully twrp from stock rooted 20e and then SuperSU and kept root? Will TiBu frozen system apps stay frozen as well? TIA
What exactly is this rom?
cenwesi said:
What exactly is this rom?
Click to expand...
Click to collapse
The name of the zip file and first post tells you what it is.
LG G3 D851, Pac-Man ROM, Tapatalk 4.9.5
do we flash it through TWRP? or any other custom recovery?
Yes, just as you would w/ any other ROM. Perform a full wipe beforehand, excluding both internal and external storage. And if you want to retain root and recovery, make sure to flash those immediately after (add them to the queue in TWRP).
Just flash this rom.. Everything works fine..
Sent from my A1-840FHD using XDA Free mobile app
This may be a stupid question but I flashed this and it says I'm still vulnerable to stagefright, isn't this suppose to patch it.
Sent from my LG-D851 using Tapatalk
I flashed the same 20g ROM, and according to the Lookout Stagefright Detector app, my device is not vulnerable to Stagefright.
works but
Followed these instruction using twrp
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
I had to reset phone after flashing and setting up. Because the phone was no functioning correctly.
Unfortunately Stagefright CVE-2015-6602 is still vulnerable according to
Zimperium Stagefright detector app.
Lookout Stagefright Detector will not detect the latest Version 2.0 vulnerabilities of Stagefright and make it clear in there app description.
"This app does not support detection of Stagefright 2.0 vulnerabilities. "
So here we go again in the waiting game.
Wouldn't it be better if google took Stagefight out of the rom, so it can could be updated in play store?
painless
Wiped cache & Dalvik cache, flashed the OP update zip then flashed TWRP custom recovery and finally SupurSU.
Tested using Lookout Stagefright Detector and all is well.
side note: needed to regain writing privileges for my external SD
Thanks core720!
Works Great
AndroidUzer said:
Wiped cache & Dalvik cache, flashed the OP update zip then flashed TWRP custom recovery and finally SupurSU.
Tested using Lookout Stagefright Detector and all is well.
side note: needed to regain writing privileges for my external SD
Thanks core720!
Click to expand...
Click to collapse
Thanks bro,
Did exact same steps as you suggest and it worked great. Just in case anyone needs them....
Here is Super Su:
https://www.androidfilehost.com/?w=...b6cc0224f97f975b25bd6fd089dffab48899dd59ac9fc
ANd here is TWRP:
https://www.androidfilehost.com/?w=...9a65ee4397109b889147c21f3bf0e48037fffad3bccb3
fc3211 said:
Thanks bro,
Did exact same steps as you suggest and it worked great. Just in case anyone needs them....
Here is Super Su:
https://www.androidfilehost.com/?w=...b6cc0224f97f975b25bd6fd089dffab48899dd59ac9fc
ANd here is TWRP:
https://www.androidfilehost.com/?w=...9a65ee4397109b889147c21f3bf0e48037fffad3bccb3
Click to expand...
Click to collapse
Thanks for the two links. Very helpful
Anyone do it dirty, no wipes? From 20e to 20g? -Cuz restoring apps and settings is "such fun". Thanks.
skipaaa said:
Anyone do it dirty, no wipes? From 20e to 20g? -Cuz restoring apps and settings is "such fun". Thanks.
Click to expand...
Click to collapse
I landed here because I tried the 20e to 20g update and got the "unexpected version" error via twrp. Responding to my own post cuz I got bold and did it anyways.
...So, I had TWRP 2.8.7.0 D851 installed. Did full backups with Titanium paid version and TWRP. Started with STOCK rooted d85120e, left it rooted, and used TRWP to install
1) STOCK d95120g from top of this thread,
2) TWRP d851 2.8.7.0 found elsewhere (above link is 2.8.6.0), and
3) the SuperSU zip from link found just above.
Rebooted system without any wipes. A few minutes to update apps on first reboot and mostly good to go. Had to update SupserSU binaries via normal mode, and reinstall busybox. Busybox froze on black screen on multiple attempts during it's startup check, so on next attempt, I didn't let it finish the check, just told it to install, and has been bliss all day. So far, so stable. Better have the backups and not need them than need them and not have them. Settings show D85120G and Lookout shows NOT vulnerable to stagefright.
Sitting pretty. Hope this helps others who couldn't use the 20E to 20G update method to keep stock roms with optional root.
Wiped everything as stated and flashing reboots TWRP, anyone know why this happens?
Thank you! Works - rooted 20e to 20g
AndroidUzer said:
Wiped cache & Dalvik cache, flashed the OP update zip then flashed TWRP custom recovery and finally SupurSU.
Tested using Lookout Stagefright Detector and all is well.
side note: needed to regain writing privileges for my external SD
Thanks core720!
Click to expand...
Click to collapse
I was on rooted 20e and did what you said. Works like a charm, I have 20g now without any problems. Thank you everyone! :]
I finally came out of lurk mode to say thanks. This untouched ROM has saved me from 2 soft bricks. Works flawlessly.
it has no sound please help
Hello everyone,
As I'm sure everyone knows, Niantic has blocked rooted phones from playing with the most current update 0.37. I'm wondering if anyone has been able to find a ROM that will work on our phones and we can install magisk to be able to play with the latest update. If not, is there any other possible solution to play with the use of magisk or without giving up root completely. I'm currently running PaulPizz and have not tried any of the possible methods I have found from fear of losing root permanently. I'm open to any suggestions or ideas.
Thank you.
Try going to the Samsung Note 4 international section.. I just flashed a Note 7 port to my wife's phone and it rocks..
Could you possibly link to which one? Is it this one? Xerrum525 N7 FullFramework PortedRom for SM-N910C / SM-N910H
Also did you use magisk with it to use pokemon go?
Tricil said:
Hello everyone,
As I'm sure everyone knows, Niantic has blocked rooted phones from playing with the most current update 0.37. I'm wondering if anyone has been able to find a ROM that will work on our phones and we can install magisk to be able to play with the latest update. If not, is there any other possible solution to play with the use of magisk or without giving up root completely. I'm currently running PaulPizz and have not tried any of the possible methods I have found from fear of losing root permanently. I'm open to any suggestions or ideas.
Thank you.
Click to expand...
Click to collapse
I'd like to know too.
What I did was install PaulPizz. Once it finished I deleted the SuperSU folder via TWRP.
It booted up fine, I still had the SU app in my drawer, I did full unroot via SU. I then flashed the uninstall for Xposed and now I can play pogo.
I Haven't been able to get Magisk to work... I get unable to detect boot image. I'm unrooted for now on PaulPizz and can play PoGo 0.37
Tricil said:
Hello everyone,
As I'm sure everyone knows, Niantic has blocked rooted phones from playing with the most current update 0.37. I'm wondering if anyone has been able to find a ROM that will work on our phones and we can install magisk to be able to play with the latest update. If not, is there any other possible solution to play with the use of magisk or without giving up root completely. I'm currently running PaulPizz and have not tried any of the possible methods I have found from fear of losing root permanently. I'm open to any suggestions or ideas.
Thank you.
Click to expand...
Click to collapse
I downloaded an older version of the app from http://www.apkmirror.com/apk/niantic-inc/pokemon-go/.
I uninstalled the new version. Reinstalled the older. Ran fine. I've heard they'll force an update sooner or later but its good for now.
I also made sure to turn off auto app updated in settings.
I did find a solution using PaulPizz and magisk. It relatively follows most other tutorials. Plus I found a way to toggle magisk with tasker, if anyone is interested. I'll post a step by step tomorrow or possibly later tonight. Sorry to make everyone wait.
So this is how I got it work with PaulPizz ROM for Verizon Note 4 retail converted to Dev edition.
I take no credit for the creation of the files required for this install, but I kind of muttled my way through this installation and got the files from different posts so credit is to go to the creators of these files, I am just redistributing. If someone feels the need to take credit for these please feel free to let me know.
Make sure to download all apks and zips before and place on sd card before hand to save time. I have also included the uninstaller for magisk version of xposed if you would like, do not use this one during the installation of magisk to remove xposed though.
Only flash xposed and install apk if you still want xposed, if not you can skip those files.
1. Do a full backup of phone using TWRP
2. Go into SuperSU settings and do full unroot
3. Reboot into recovery and mount system partion
4. Go to advanced in recovery and select File explorer
5. Navigate to system and delete .supersu file
6. Flash xposed-uninstaller-20150831-arm.zip and reboot system
7. Install pokemon go 0.37 and make sure it works at this point
8. Reboot into recovery again and flash Magisk-v6.zip, 1473968610260_phh-superuser-17-magisk.zip, and 1473980489208_xposed-v86.5-arm-alt-sdk23-topjohnwu.zip
9. Clear dalvik and cache and reboot system
10. After apps optimize install Magisk manager and Xposed Installer
11. Reboot and enjoy playing the new update. Just use Magisk Manager to turn root on/off at will before or after playing.
I'm going to create the tasker profile tomorrow and post instruction on that once completed to automatically activate Magisk when opening pokemon go.
If there are any questions, I will do my best to answer.
Tricil said:
So this is how I got it work with PaulPizz ROM for Verizon Note 4 retail converted to Dev edition.
I take no credit for the creation of the files required for this install, but I kind of muttled my way through this installation and got the files from different posts so credit is to go to the creators of these files, I am just redistributing. If someone feels the need to take credit for these please feel free to let me know.
Make sure to download all apks and zips before and place on sd card before hand to save time. I have also included the uninstaller for magisk version of xposed if you would like, do not use this one during the installation of magisk to remove xposed though.
Only flash xposed and install apk if you still want xposed, if not you can skip those files.
1. Do a full backup of phone using TWRP
2. Go into SuperSU settings and do full unroot
3. Reboot into recovery and mount system partion
4. Go to advanced in recovery and select File explorer
5. Navigate to system and delete .supersu file
6. Flash xposed-uninstaller-20150831-arm.zip and reboot system
7. Install pokemon go 0.37 and make sure it works at this point
8. Reboot into recovery again and flash Magisk-v6.zip, 1473968610260_phh-superuser-17-magisk.zip, and 1473980489208_xposed-v86.5-arm-alt-sdk23-topjohnwu.zip
9. Clear dalvik and cache and reboot system
10. After apps optimize install Magisk manager and Xposed Installer
11. Reboot and enjoy playing the new update. Just use Magisk Manager to turn root on/off at will before or after playing.
I'm going to create the tasker profile tomorrow and post instruction on that once completed to automatically activate Magisk when opening pokemon go.
If there are any questions, I will do my best to answer.
Click to expand...
Click to collapse
I still get unable to detect boot image :/
reggaeton1991 said:
I still get unable to detect boot image :/
Click to expand...
Click to collapse
When are you getting that, when you flash the zip or install the apk? I'm guessing that's when you flash the included Magisk_6.zip. You are rooted using the retail to dev on an N910V model? I would maybe backup your current system and restore from before you unrooted and try again possibly.
Tricil said:
When are you getting that, when you flash the zip or install the apk? I'm guessing that's when you flash the included Magisk_6.zip. You are rooted using the retail to dev on an N910V model? I would maybe backup your current system and restore from before you unrooted and try again possibly.
Click to expand...
Click to collapse
Yes rooted from retaill to dev on a N910V and yea, I get that when flashing Magisk_6.zip.
I'm factory resetting the rom. Going to ensure I have root from PaulPizz. and then try again. Thank you.
reggaeton1991 said:
Yes rooted from retaill to dev on a N910V and yea, I get that when flashing Magisk_6.zip.
I'm factory resetting the rom. Going to ensure I have root from PaulPizz. and then try again. Thank you.
Click to expand...
Click to collapse
After clean install (wipe data, cache, system)
It says after mounting system
Mounting /system(ro), /cache, data
Device platform arm
unable to detect boot image
error 1
idk what to do
reggaeton1991 said:
I still get unable to detect boot image :/
Click to expand...
Click to collapse
reggaeton1991 said:
Yes rooted from retaill to dev on a N910V and yea, I get that when flashing Magisk_6.zip.
I'm factory resetting the rom. Going to ensure I have root from PaulPizz. and then try again. Thank you.
Click to expand...
Click to collapse
Also, this is my setup, if it helps at all. Please let me know if any of this helps, or if you find another way that works for you. Thank you.
Tricil said:
Also, this is my setup, if it helps at all. Please let me know if any of this helps, or if you find another way that works for you. Thank you.
Click to expand...
Click to collapse
Thanks again, it looks like the only difference was that I was on CPF3.r-2.
I tried going back to CPD1 and still no luck.
I appreciate you letting me know.
I used the Kyubi rom and uninstalled root with supersu and installed all of the magisk stuff and it works like a charm. All of the xposed modules work good too with the system less xposed. It takes a while to boot up after flashing magisk and clearing cache but worth it. The buddy system is pretty cool lol
Anyone else only able to MAYBE play on WiFi?
Tricil said:
So this is how I got it work with PaulPizz ROM for Verizon Note 4 retail converted to Dev edition.
I take no credit for the creation of the files required for this install, but I kind of muttled my way through this installation and got the files from different posts so credit is to go to the creators of these files, I am just redistributing. If someone feels the need to take credit for these please feel free to let me know.
Make sure to download all apks and zips before and place on sd card before hand to save time. I have also included the uninstaller for magisk version of xposed if you would like, do not use this one during the installation of magisk to remove xposed though.
Only flash xposed and install apk if you still want xposed, if not you can skip those files.
1. Do a full backup of phone using TWRP
2. Go into SuperSU settings and do full unroot
3. Reboot into recovery and mount system partion
4. Go to advanced in recovery and select File explorer
5. Navigate to system and delete .supersu file
6. Flash xposed-uninstaller-20150831-arm.zip and reboot system
7. Install pokemon go 0.37 and make sure it works at this point
8. Reboot into recovery again and flash Magisk-v6.zip, 1473968610260_phh-superuser-17-magisk.zip, and 1473980489208_xposed-v86.5-arm-alt-sdk23-topjohnwu.zip
9. Clear dalvik and cache and reboot system
10. After apps optimize install Magisk manager and Xposed Installer
11. Reboot and enjoy playing the new update. Just use Magisk Manager to turn root on/off at will before or after playing.
I'm going to create the tasker profile tomorrow and post instruction on that once completed to automatically activate Magisk when opening pokemon go.
If there are any questions, I will do my best to answer.
Click to expand...
Click to collapse
Well I have magisk installed but I dont know if the xposed went through entirely it says it flashed ok but according to the installer I don't have xposed installed? What's going on did I do something wrong
Did you remove the old xposed app after the flag and install the new xposed apk also? I think mine did the same, because I forgot to also install the xposed app after flashing the systemless xposed framework.
I was able to full unroot, delete the super su file in twrp. when I flash the Xposed uninstaller it removes the framework but leaves the APk in a form that I can't delete.
If I flash magisk and all the other stuff it goes through fine, but when I try to toggle root off in magisk it turns itself back on within a few seconds. I'm assuming this is because i didn't get Xposed all the way off?
Any ideas? Thanks in advance for the help.
Magisk will refuse to unroot while xposed is still there in the system form. Even a piece of it.
Well now I got Xposed off using tibu before I unroot. Everything installed, systemless Xposed registered as being active, but when I try to toggle root in magisk I get the same thing with it turning itself back on. If I try to request root privileges from an app I am told i have no root.
Ideas?