Has anyone attempted to install xposed on the honor 8?
Yes, works. Arm64.
I can confirm, XPosed can be installed...
Albeit it seems to have a "small" bug - for me the dialer did stop working when xposed was installed (could not make any call)
V86 ARM64 xposed by rovio...
will need to investigate further.
Can anyone confirm/deny/did find a workaround?
I have xposed and dialer is working fine. Maybe it's some particular mod you've installed.
I tried installing xposed from this link http://dl-xda.xposed.info/framework/sdk23/arm64/ but I'm always getting a bootloop. Did you use another zip file?
ppalfinger said:
I tried installing xposed from this link http://dl-xda.xposed.info/framework/sdk23/arm64/ but I'm always getting a bootloop. Did you use another zip file?
Click to expand...
Click to collapse
For me, xposed did work using magisk + systemless xposed (material xposed intaller + v86.5); as well as using v86 - i think the version you posted.
I could revert my previous dialer problem by rebooting several times till all files have been treated by xposed as they should have been...
DThought said:
I can confirm, XPosed can be installed...
Albeit it seems to have a "small" bug - for me the dialer did stop working when xposed was installed (could not make any call)
V86 ARM64 xposed by rovio...
will need to investigate further.
Can anyone confirm/deny/did find a workaround?
Click to expand...
Click to collapse
I confirm the 'Dialer' bug you're facing. I have faced the same bug on all of the Honor devices I have owned. Whenever I hit the 'Call' button, the app crashes. A simple reboot does fixes the problem but it soon re-appears. No fix for it though.
DThought said:
For me, xposed did work using magisk + systemless xposed (material xposed intaller + v86.5); as well as using v86 - i think the version you posted.
I could revert my previous dialer problem by rebooting several times till all files have been treated by xposed as they should have been...
Click to expand...
Click to collapse
so how did you do this? i only read quick on the magisk thread but it said to flash magisk on a unrooted newly wiped phone.
is this true or can i flash it on my newly rooted honor 8?
hackslash said:
I confirm the 'Dialer' bug you're facing. I have faced the same bug on all of the Honor devices I have owned. Whenever I hit the 'Call' button, the app crashes. A simple reboot does fixes the problem but it soon re-appears. No fix for it though.
Click to expand...
Click to collapse
is it still possible to accept calls when the dialer is bugged and crashes?
also, which xposed version did you use?
JimZiii said:
so how did you do this? i only read quick on the magisk thread but it said to flash magisk on a unrooted newly wiped phone.
is this true or can i flash it on my newly rooted honor 8?
is it still possible to accept calls when the dialer is bugged and crashes?
also, which xposed version did you use?
Click to expand...
Click to collapse
About magisk,
you have to unroot your device from SuperSU. After that flash the stock boot image if available (unrooting from SuperSU usually suffices but if it doesn't works, it better to flash stock boot image)
About Xposed dialer bug (on EMUI only), yes as far as I know, I never experienced any crashes while accepting calls.
hackslash said:
About magisk,
you have to unroot your device from SuperSU. After that flash the stock boot image if available (unrooting from SuperSU usually suffices but if it doesn't works, it better to flash stock boot image)
About Xposed dialer bug (on EMUI only), yes as far as I know, I never experienced any crashes while accepting calls.
Click to expand...
Click to collapse
i feel extremely stupid here. i'm reading on the magisk thread and i don't understand at all.
i got a honor 8 (FRD-L09) and i've rooted it, like i mentioned earlier.
can you please help me with the steps i need to take to unroot and whatever else i need to do to flash magisk?
i can't find stock rom for my FRD-L09, so what do you suggest? just doing a full factory reset, flashing twrp, flashing magisk, rooting, restoring to the backup i create before doing the factory reset.
what do you think about those steps and in that order? if you think i need to change something or add another step please let me know.
not sure if that's enough to unroot the device, i'm also really uncertain about the correct magisk version/file i need to flash for my device. other xposed versions have different files for arm, arm64 and x86, but here there's only one file. am i missing something or does this work on all versions? or have i misunderstood how it works?
sorry about throwing so many questions at you but i'm really confused about this.
JimZiii said:
i feel extremely stupid here. i'm reading on the magisk thread and i don't understand at all.
i got a honor 8 (FRD-L09) and i've rooted it, like i mentioned earlier.
can you please help me with the steps i need to take to unroot and whatever else i need to do to flash magisk?
i can't find stock rom for my FRD-L09, so what do you suggest? just doing a full factory reset, flashing twrp, flashing magisk, rooting, restoring to the backup i create before doing the factory reset.
what do you think about those steps and in that order? if you think i need to change something or add another step please let me know.
not sure if that's enough to unroot the device, i'm also really uncertain about the correct magisk version/file i need to flash for my device. other xposed versions have different files for arm, arm64 and x86, but here there's only one file. am i missing something or does this work on all versions? or have i misunderstood how it works?
sorry about throwing so many questions at you but i'm really confused about this.
Click to expand...
Click to collapse
Take a complete backup just in case.
Perform a full unroot via SuperSU (find it in Settings). It will restore the modded files with the original ones hence reverting your boot image to the stock one.
Perform a full Factory reset. (remember to backup crucial data before attempting it)
Download B101 FRD-L09 stock ROM from here: http://loadbalancing.modaco.com/download.php?file=dload-honor-8-frdl09-frd-b101.zip
Extract the downloaded zip. There will be two folders, 'Part 1' and Part 2'. On your external SD card, create a folder 'dload'. Copy 'Update.APP' from 'Part 1' to the dload folder in your SD card. Power down the device. Hold Power Button + Volume Up + Volume Down buttons until you see the Honor logo. Your device will now automatically start installing the complete stock ROM. If in case your device boots to TWRP, then follow the below steps:
Download Huawei Update Extractor from here: http://forum.xda-developers.com/showthread.php?t=2433454
Use Huawei Update Extractor to extract RECOVERY from the Update.APP inside 'Part 1'.
Use 'fastboot' to flash the stock recovery.
Now try installing the Update.APP. This time it will work. Repeat the steps for Update.APP inside 'Part 2'
You're now on fresh stock ROM.
Download magisk from http://forum.xda-developers.com/devdb/project/dl/?id=19960&task=get and flash it via TWRP.
hackslash said:
Take a complete backup just in case.
Perform a full unroot via SuperSU (find it in Settings). It will restore the modded files with the original ones hence reverting your boot image to the stock one.
Perform a full Factory reset. (remember to backup crucial data before attempting it)
Download B101 FRD-L09 stock ROM from here: http://loadbalancing.modaco.com/download.php?file=dload-honor-8-frdl09-frd-b101.zip
Extract the downloaded zip. There will be two folders, 'Part 1' and Part 2'. On your external SD card, create a folder 'dload'. Copy 'Update.APP' from 'Part 1' to the dload folder in your SD card. Power down the device. Hold Power Button + Volume Up + Volume Down buttons until you see the Honor logo. Your device will now automatically start installing the complete stock ROM. If in case your device boots to TWRP, then follow the below steps:
Download Huawei Update Extractor from here: http://forum.xda-developers.com/showthread.php?t=2433454
Use Huawei Update Extractor to extract RECOVERY from the Update.APP inside 'Part 1'.
Use 'fastboot' to flash the stock recovery.
Now try installing the Update.APP. This time it will work. Repeat the steps for Update.APP inside 'Part 2'
You're now on fresh stock ROM.
Download magisk from http://forum.xda-developers.com/devdb/project/dl/?id=19960&task=get and flash it via TWRP.
Click to expand...
Click to collapse
thnx. i followed your steps, with a few added ones. i didn't realize that my bootloader would lock up again after flashing stock so i had to unlock it and reflash twrp.
i did wonder about the root since all phones have different root versions and he's offering a one for all version, but i flashed it and i now got working root.
still not done tho, still got to install the magisk manager and xposed
but thank you so much for you help, really felt like i was fumbling in the dark there for a moment before asking you lol
EDIT:
that it let's you turn the root on and off with a switch is ingenious. but what does it mean that google pay is not working while root is on?
JimZiii said:
that it let's you turn the root on and off with a switch is ingenious. but what does it mean that google pay is not working while root is on?
Click to expand...
Click to collapse
Yes, while the root is on, all applications that include the 'SafetyNet' check will refuse to work (such as Android Pay, Pokemon Go). When you switch it off, everything will start to work again.
hackslash said:
Yes, while the root is on, all applications that include the 'SafetyNet' check will refuse to work (such as Android Pay, Pokemon Go). When you switch it off, everything will start to work again.
Click to expand...
Click to collapse
yea that was just me remembering it wrong, thought it said google pay instead of android pay, so when i googled it i didn't really find anything which made me wonder what this mysterious google pay app was lol
but now i googled the correct name and found it right away.
but yea, thnx a lot for you help and time
Does anyone have issues playing videos with magisk installed, and I mean the flashable magisk not just the magisk manager app
Hello
I'm looking for a module which permit to center clock in statut bar .
Someone can help me please ?
Someone has tested Gravity Box ?
Works fine ?
Some features of GravityBox are working, some not.
Changes in statusbar are not working.
Nas42O said:
Hello
I'm looking for a module which permit to center clock in statut bar .
Someone can help me please ?
Click to expand...
Click to collapse
Not a perfect solution but try Flat Style Indicators.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Nas42O said:
Someone has tested Gravity Box ?
Works fine ?
Click to expand...
Click to collapse
There is a rule to check if modules will work flawlessly on your device or not. It's simple. All modules that were designed keeping AOSP in mind will not work. EMUI is a completely different iteration if Android and hence many of the options in Gravity Box will not work on EMUI.
hackslash said:
Not a perfect solution but try Flat Style Indicators.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
There is a rule to check if modules will work flawlessly on your device or not. It's simple. All modules that were designed keeping AOSP in mind will not work. EMUI is a completely different iteration if Android and hence many of the options in Gravity Box will not work on EMUI.
Click to expand...
Click to collapse
Thanks for your answer..
I already tested flat style bar but i got some issues .. :/
Gravity box has many customisations, but if almost all not working.. :s
Related
I read that Exposed Installer has been updated. Does anyone know if it would work with the 5.1.1 Update that Tmo and Metro Stylo got?
Only way to find out is to try. I'll be backing up and trying in a bit.
well it said it installed in twrp, but when i rebooted, it stayed on the lg screen for longer than usual...then it finally went to the metro screen but it just stayed there for a long time so i panicked and pulled the battery.
i was able to restore my backup and i thought i read somewhere that i may need busybox installed...even though i thought busybox got installed when i did the one click root, i went ahead and installed it from the playstore to try again.
again it said it installed in twrp, this time i let it stay on the metro screen even longer but it seemed like it was stuck so i restored a backup...do you think i just need to wait longer? also do i really need busybox installed?
im tempted to restore my 5.02 backup and see what happens if i try to install the 5.0 version...
AP2FTW said:
well it said it installed in twrp, but when i rebooted, it stayed on the lg screen for longer than usual...then it finally went to the metro screen but it just stayed there for a long time so i panicked and pulled the battery.
i was able to restore my backup and i thought i read somewhere that i may need busybox installed...even though i thought busybox got installed when i did the one click root, i went ahead and installed it from the playstore to try again.
again it said it installed in twrp, this time i let it stay on the metro screen even longer but it seemed like it was stuck so i restored a backup...do you think i just need to wait longer? also do i really need busybox installed?
im tempted to restore my 5.02 backup and see what happens if i try to install the 5.0 version...
Click to expand...
Click to collapse
BusyBox is needed so that some things that require root work correctly like Viper4Android, but it's not needed for everything
I had the same problem with it staying on the carrier screen for 30 minutes before I gave up. Seems it just won't work as it currently stands.
v71 is booting on my stock rooted 5.11 metro stylo woot! now to see which modules work...
AP2FTW said:
v71 is booting on my stock rooted 5.11 metro stylo woot! now to see which modules work...
Click to expand...
Click to collapse
get anywhere with it?
yeah i have youtube adaway, xstana and gravitybox running
AP2FTW said:
yeah i have youtube adaway, xstana and gravitybox running
Click to expand...
Click to collapse
cool. youtube adaway and wanam are the two I use. I'm hoping wanam works. where did you get your exposed installer from? the one i found says its for 5.1 it doesn't mention 5.1.1
i read this thread http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
which led me to download this http://forum.xda-developers.com/attachment.php?attachmentid=3441136&d=1439740135
and this http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
AP2FTW said:
i read this thread http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
which led me to download this http://forum.xda-developers.com/attachment.php?attachmentid=3441136&d=1439740135
and this http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
Click to expand...
Click to collapse
ok, that was the thread I was on. thanks
xposed is now updated with official support for LP 5.1 http://forum.xda-developers.com/showthread.php?t=3034811
AP2FTW said:
xposed is now updated with official support for LP 5.1 http://forum.xda-developers.com/showthread.php?t=3034811
Click to expand...
Click to collapse
found these instructions in Italian on how to install without recovery pasting them in English (rough google translation):
ith this tutorial we see how to install Xposed Framework on a phone with Android
Lollipop without recovery!
Cost:
Root
Busybox installed on the device (and also installed files busybox, just open the app)
Terminal Emulator installed on the device
Package XposedLollipop taken from this video.
1- Download the package by pressing the link
2- Unzip
3- Put the contents of the root (in the main memory of the phone,
no subfolders) of the device.
4- Install Xposed (the apk is among the file you just put into the device) BUT do not open it
5- Open the terminal emulator and type "su" after which you type: sh / sdcard / installer
and press enter.
6- 1 and press enter.
7- Wait for the procedure, after restart and you Xposed properly installed
PS: procedure performed perfectly on MEIZU MX4 which as you know does not have recovery mod, works on all phones MA may be different from the path where installed so placed in the root of the file and make sure that it's called "sdcard", should have a other name you have to use that! eg sh / card / installer
link to the video with his links: https://www.youtube.com/watch?v=tDInZYNrEr8 if this does work then us Boost User's can enjoy it too , but i have no idea if it does work
and if it doesnt work? i wouldnt try anything fancy without having twrp to restore a backup (or at least a kdz)...are you gonna try that method?
AP2FTW said:
and if it doesnt work? i wouldnt try anything fancy without having twrp to restore a backup (or at least a kdz)...are you gonna try that method?
Click to expand...
Click to collapse
i'm looking through his links and reading/translating everything from Italian before i try it...and i'm gonna see if ican make it work with the newer official framework
---------- Post added at 02:12 PM ---------- Previous post was at 01:29 PM ----------
AP2FTW said:
and if it doesnt work? i wouldnt try anything fancy without having twrp to restore a backup (or at least a kdz)...are you gonna try that method?
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/development/guide-xposed-boost-stylo-5-1-1-t3192494
ah so you got it working thats awesome...only problem is i think...no wait i know, that i would be way too paranoid to try that without having a way back to stock. thank god i have twrp (and a kdz in case things ever got really messy)
AP2FTW said:
ah so you got it working thats awesome...only problem is i think...no wait i know, that i would be way too paranoid to try that without having a way back to stock. thank god i have twrp (and a kdz in case things ever got really messy)
Click to expand...
Click to collapse
lol yea true but i'm a risk taker lol
Essential one to stock firmware: together rooted system get TWRP 2.8.7.0.
Explain in great detail:
First specify the version of the firmware: Settings - About tablet - see on line Build number, for example, ***.20160216.*** (or 20160307, 20160429). In accordance with the version download the attached files.
From the thread Chainfire download TWRP / FlashFire installable ZIP, any choice - Stable, Beta or Latest. Archive ***-SuperSU-***.zip put in any useful folder in tablet.
Tablet is completely off, certainly from Android, simultaneously pressing power button and both volume "+" and "-" to boot your device in DNX Fastboot Mode (relevant notes on-screen will appear). Connect to computer that is already pre-installed the drivers (see attachment).
On the computer, launch the FLASH.bat from the extracted archive with TWRP. Wait until the script completes, devices disconnect.
In the tablet volume key to select "Recovery Mode" and power button to reboot the device in TWRP.
In TWRP to install the archive with superuser: Install - select the file - Swipe to Confirm Flash - Reboot system.
That's all, folks! © Disney
In addition TWRP installs insecure boot.img with screen density to 280 dpi.
Credits
@Chainfire for superuser;
@mirek190 for permission to use his fantastic flash tool (I changed it a bit for the installation TWRP);
thanks to Dani Basabe for sharing TWRP-2.8.7.0_teclast_x98pro-b2 (details see here)
and thank me for the work done.
Download
Intel drivers
twrp_0216
twrp_0307
twrp_0429
twrp_0531
twrp_remix_1.0.5(v5_7)
twrp_remix_1.0.5(v7)
twrp_0706
twrp_0729
My tablet is 20160324. Which version of twrp must I use?
perama said:
My tablet is 20160324. Which version of twrp must I use?
Click to expand...
Click to collapse
Interesting question. I don't see this firmware version in the official and not official sources. The problem isn't TWRP - it's the same everywhere - but in unlocked boot.img. I'm unable to recommend anything, I have no boot.img 20160324.
Please look at the screen shot from my tablet.
i bought it from GearBest.
Can I try all the versions you have uploaded to find out which one will work? Or I will damage my tablet this why?
perama said:
Please look at the screen shot from my tablet.
i bought it from GearBest.
Can I try all the versions you have uploaded to find out which one will work? Or I will damage my tablet this why?
Click to expand...
Click to collapse
Yes, do you have Onda CH - cht_cr_mrd_w. Take any set, but remove from it the boot.img, install TWRP and make a backup of the boot.img and here put, please.
I have a feeling that the Chinese are a hundred variations of iron made.
Thank you very much for helping me!
You mean, first to delete the file "boot.img" from folder "rom", then to run "flash.bat" to install "TWRP recovery" only and finally to make a backup of my "boot.img" and upload it here?
Without unlocked "boot.img" I can't make my tablet rooted?
perama said:
Without unlocked "boot.img" I can't make my tablet rooted?
Click to expand...
Click to collapse
You can try to flash SuperSU without unlocked boot - I havn't to get root access without changing it. But all of a sudden? I followed the path blazed by Teclast and Cube.
perama said:
You mean, first to delete the file "boot.img" from folder "rom", then to run "flash.bat" to install "TWRP recovery" only and finally to make a backup of my "boot.img" and upload it here?
Click to expand...
Click to collapse
Yes.
I installed TWRP and then booted to recovery. I backed up "boot.img" but then the tablet turned off by its own!
When I tried to turned it on again to Android, it keeps stay to 'Intel" logo for ever!
I don't know what to do! Please help me!
It boots to Windows without problem.
I manage to install the 0531 version using your instructions !
Everything works perfect including the sound!
Now I will try to root my device using your instruction above.
I will let you know... Thank you very much for your help!!!
I manage to root my tablet.
Everything is working fine now!
Thank you very much ViAlexSt! You are a life saver!
Mine has a 20160323 version! I think we are being played with.... Those numbers are a lot of versions!
What should I do? Perhaps the same as perama? I want to do a nandroid backup first, naturally.
Any suggestions?
pouskidis said:
Mine has a 20160323 version! I think we are being played with.... Those numbers are a lot of versions!
What should I do? Perhaps the same as perama? I want to do a nandroid backup first, naturally. Any suggestions?
Click to expand...
Click to collapse
I don't know whether to read this topic anyone else besides me, but I find it difficult to answer unequivocally. If you are not afraid - try to put the firmware 0531. And then TWRP.
I just wanna root the damn thing...
I already got i2c HID Device data failure once, just 2 days after I bought it.
Had to open the case and fix it, so yes, I am prete much afraid...
Is this 0531 version English f/w with no chinese? So, it just needs rooting?
Thanks ViAlexSt for all the help you provide us.
pouskidis said:
Is this version English f/w with no chinese?
Click to expand...
Click to collapse
Here's what Chinese maybe? Here installation packages with the insecure boots and TWRP for the flashing of the SuperSU.
pouskidis said:
I already got i2c HID Device data failure once, just 2 days after I bought it.
Had to open the case and fix it, so yes, I am prete much afraid...
Click to expand...
Click to collapse
The installation package must match the version of existing firmware.
ViAlexSt said:
Here's what Chinese maybe? Here installation packages with the insecure boots and TWRP for the flashing of the SuperSU.
The installation package must match the version of existing firmware.
Click to expand...
Click to collapse
So, you suggest to wait for someone with my frimware to post it?
Also, did you say that v0531 is English with no Chinese programs? Sorry, I did not understand correctly...
pouskidis said:
So, you suggest to wait for someone with my frimware to post it?
Click to expand...
Click to collapse
I don't know what version of firmware you have installed. You can of course try to install the most recent version - 0531, but may lose sound if the modification of iron is not adequate. Look at the serial number on the back cover: if it in the form .....G4V7...... - you can safely install 0531.
pouskidis said:
Also, did you say that v0531 is English with no Chinese programs? Sorry, I did not understand correctly...
Click to expand...
Click to collapse
Firmware version 0531 international, with pre-installed gapps and no Chinese, but firmware is discussed in another topic Here, only the activation of root access.
ViAlexSt said:
I don't know what version of firmware you have installed. You can of course try to install the most recent version - 0531, but may lose sound if the modification of iron is not adequate. Look at the serial number on the back cover: if it in the form .....G4V7...... - you can safely install 0531.
Firmware version 0531 international, with pre-installed gapps and no Chinese, but firmware is discussed in another topic Here, only the activation of root access.
Click to expand...
Click to collapse
I do have a v7 model... So I can proceed I guess. Sorry for the off topic, I just thought I would do a nandroid backup/root first. But installing 0531 from the start somehow seems safer?
Thanks
pouskidis said:
I do have a v7 model
Click to expand...
Click to collapse
G4 or G3 revision? If G4, then any available firmware will do. With G3 harder - there may be issues with wake tablet from sleep.
pouskidis said:
I just thought I would do a nandroid backup/root first. But installing 0531 from the start somehow seems safer?
Click to expand...
Click to collapse
Any firmware version will not make the tablet a brick. The only question is the presence of bugs: sound, sleep, overheating...
Look at the messages of реrama: he set TWRP with no boot, even made a backup, but without unlocking boot, the tablet doesn't start. He had to flash the version 0531, which, however, fit perfectly under his revision of "iron".
I have G4v7 revison. I guess I am good to go. I don't want any overheating problems, like "Throttling Brightness due to Thermal event" problems I had with Onda V919 Air 3G 64GB Intel Z3735F.
I had themal problems and shutdowns and was forced to return the product...
EDIT: I managed to root it after installing the PERFECT 0531 EN firmware.
The tablet is PERFECT now!
Thanks ViAlexSt!
I always get "failed to get partition boot".
I think there is an error in fstab.
When I manage to run TWRP, it fails to mount /data.
Any ideas?
V919 Air CH, 64 GB Android 5.1
oz42 said:
I always get "failed to get partition boot".
I think there is an error in fstab.
When I manage to run TWRP, it fails to mount /data.
Any ideas?
V919 Air CH, 64 GB Android 5.1
Click to expand...
Click to collapse
Hmm, interesting... While no specific ideas. I (and not only) have everything working. What version of firmware? Script when you install TWRP fulfills completely, without any errors? It's possible that not removed the OEM lock. Try to put the checkboxs in "Developers section" in "Settings".
I've taken note of the severely limited amount of organized information available for the Verizon variant of the core prime, (see the amalgamation of posts in the main sm-g360v post...) and I'll attempt to provide what information I do have. Currently no recoveries or custom roms have been made publicly available, to my knowledge. This is a Verizon device after all, don't hold much hope towards unlocking the bootloader of this one. Root on latest firmware, setup for xposed framework, and viper4android setup detailed below in respective order.
Root on latest firmware
*Skip to step 7 if already rooted with supersu, data partition not overwritten to my knowledge, proceed with cation
Backup all data before proceeding. Acknowledge these steps will delete all content of your device. Proceeding with the following steps gives the implied understanding I am not responsible for any data on your device. You are responsible for your own data.
1. Setup Odin and d/l the lollipop stock rom here
2. Backup your data then extract the tar.md5 from the rar archive from above then flash it with odin
3. Setup your accounts with the setup wizard when finished if you'd like, then grab the latest version of kingroot. Either android or pc versions work. May need to attempt multiple times.
4. Once rooted with latest kingroot, (5.0.3 at the time of writing) open kingroot, open the main settings from the menu on the top right, press 'Uninstall Kingroot' press continue, ensure 'leave root backup' is enabled in the next dialog, then wait for uninstall
5. Find a kingroot 4.5 apk and install, disable automatic updates in kingroot main settings, then reroot
6. Using either super sume, or a script replace kinguser with supersu
7. Install flashfire, should work properly if using supersu
8. Go here and d/l latest firmware, move tar.md5 file to device, may need external sd due to little internal storage
9. In flashfire, press the addition symbol, select 'flash firmware package,' locate updated tar.md5, select 'modem firmware' and 'Firmware' in addition to pre-selected partitions, then select the check, when prompted, do not split flashing process. Ensure EverRoot is set to inject SuperSU, then flash, wait patiently for device to update.
When finished, check SuperSU for root, if prompted to manually install, flash first stock and try again
Xposed Framework
1. Get the appropriate zip (ARM for sm-g360v, do not use the ARM64) from here, no issues apparent between versions, latest will most likely work (87.1 at the time of writing, no issues seem thus far)
2. Flash as zip with Flashfire, (See above for root) do not mount /system with flashfire, installer fails.
3. Install this Xposed Framework app when reboot finished (should rebuild system apps)
4. Finished
Viper4Android
1. Get V4A apk, do not install drivers yet
2. Install busybox
3. Get this and this, flash both with flashfire
4. Disable/delete SoudAlive to prevent conflicts
5. Install driver/reboot
6. Finished *I personally installed the 2.5 version, though the above method did work with a little bit of toying with the above
I'm assuming that the Odin tar file is an older firmware version for the device?
Jrhotrod said:
I'm assuming that the Odin tar file is an older firmware version for the device?
Click to expand...
Click to collapse
The first tar is lollipop with a security patch from 2015 for kingroot, the second tar that gets flashed through flashfire can be any of the three available, I believe the 2017 build being latest
WARNING:
DO NOT, I repeat DO NOT flash the updated tar.md5!! I flashed it to my device and I lost all calling and texting functionality, PLUS a very outdated ROM.
Jrhotrod said:
WARNING:
DO NOT, I repeat DO NOT flash the updated tar.md5!! I flashed it to my device and I lost all calling and texting functionality, PLUS a very outdated ROM.
Click to expand...
Click to collapse
Use the latest build, the 2017 build is latest, update your modem partitions when you update. Following the steps PROPERLY and using the proper update package will result in a functional device. Complain to Verizon about the outdated nature of the firmware available, and to yourself about your own mistakes, I have used this procedure for my own device and have not had a single issue.
LeafyDeerVoid said:
Use the latest build, the 2017 build is latest, update your modem partitions when you update. Following the steps PROPERLY and using the proper update package will result in a functional device. Complain to Verizon about the outdated nature of the firmware available, and to yourself about your own mistakes, I have used this procedure for my own device and have not had a single issue.
Click to expand...
Click to collapse
I used the 30.10.2016 firmware (G360VVRU3CPJ1) and that's what gave me the issues. Now that I actually observe, I can see a 2017 firmware that I was actually using before I went back and rooted... I will test it soon.
How long should the final update take? I'm up to 30 mins now on the red Verizon screen (blue light strobing).
Chadtheguru said:
How long should the final update take? I'm up to 30 mins now on the red Verizon screen (blue light strobing).
Click to expand...
Click to collapse
Final update meaning what? An update package flashed via FlashFire? Or something else?
Step 9 in the op root process. I did everything up to that point, downloaded latest update, followed the flashfire steps and got 2 hours of the red Verizon screen. Any ideas?
I'm starting over. I screwed up something else anyhow trying to utilize the sd card for apps.
Okay, I started over from the beginning. I just can't get Flashfire to flash the updated firmware. It sticks on the red "Verizon" screen. I've let it sit for 3 hours and it is genuinely stuck. Help!
Chadtheguru said:
I'm starting over. I screwed up something else anyhow trying to utilize the sd card for apps.
Click to expand...
Click to collapse
I never attempted to update my software. Too risky. Stick with the G360VVRU3BOK2 baseband, there is virtually no difference between that and the new 2017 firmware.
Yeah, I've about come to the same conclusion. The only thing I don't like is the nagging OTA Update Notification. I've tried all these and I'm still getting the notify.
http://www.droidviews.com/disable-ota-notifications-android-devices/
Chadtheguru said:
Yeah, I've about come to the same conclusion. The only thing I don't like is the nagging OTA Update Notification. I've tried all these and I'm still getting the notify.
http://www.droidviews.com/disable-ota-notifications-android-devices/
Click to expand...
Click to collapse
Download the device control app from the Play Store and disable the Verizon "Software updates" app
Hah! That did it. Thanks!
Chadtheguru said:
Hah! That did it. Thanks!
Click to expand...
Click to collapse
Thanks for leaving a thanks :good:
---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------
Jrhotrod said:
Thanks for leaving a thanks :good:
Click to expand...
Click to collapse
For future reference, OTAs are stored in /cache. If you feel like re-enabling the update app, you can let the update download and see if you can flash it with FlashFire. Never tried it myself, but FlashFire does come with an OTA update flasher that attempts to sustain root.
I almost tried that but I couldn't catch it with the OTA downloaded. I may fiddle with it later. Just glad to be rooted for now. Thanks again!
So I've done everything right, and all I've been wanting to install is Xposed. But I've done everything correct up to this point. But I put the framework zip into Flashfire, everything goes fine, until I'm at the Verizon red screen. It just hangs there for hours. Any suggestions?
Sent from my SM-G360V using Tapatalk
iiBootMii said:
So I've done everything right, and all I've been wanting to install is Xposed. But I've done everything correct up to this point. But I put the framework zip into Flashfire, everything goes fine, until I'm at the Verizon red screen. It just hangs there for hours. Any suggestions?
Click to expand...
Click to collapse
Better make sure you have the custom Wanam build.
Download link: https://www.androidfilehost.com/?w=files&flid=37508
Jrhotrod said:
Better make sure you have the custom Wanam build.
Download link: https://www.androidfilehost.com/?w=files&flid=37508
Click to expand...
Click to collapse
I'm pretty sure I'm using the right one. I followed the link, then went 87.1 > Lollipop > xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125.zip
Isn't that correct?
Sent from my SM-G360V using Tapatalk
Hello everyone.
Does anyone know if it is possible to root doogee mix 2 with magisk?
Thanks
I have already opened a post for doogee mix 2 twrp.
For now no answer we have to wait
Doogee mix root
hi can everyone help me to root doogee mix??
THX
Sorry to put this query here. Even i haven't got any place to right it down. I also have a same problem. Rear camera not working. Bought this phone specially for camera specifications. When will be the updates release to make the second rear camera work. Even 8 MP Nokia camera takes better picture than this 16 MP. And there are many bugs. Many apps crashes. And on YouTube I have seen many videos which shows many camera app showing 4k video recording option, but I think that was after update and I still haven't received it.i show that video 1 month back
Solved. I have rooted the doogee mix 2, installed twrp and magisk without any problem. I followed the post
https://forum.xda-developers.com/doogee-mix/development/doogee-mix-2-twrp-recovery-t3727788
Now I just need to be able to install the linage Os 15 and it will be perfect
oritome said:
Solved. I have rooted the doogee mix 2, installed twrp and magisk without any problem. I followed the post
https://forum.xda-developers.com/doogee-mix/development/doogee-mix-2-twrp-recovery-t3727788
Now I just need to be able to install the linage Os 15 and it will be perfect
Click to expand...
Click to collapse
And you forgot xposed
oritome said:
Solved. I have rooted the doogee mix 2, installed twrp and magisk without any problem. I followed the post
https://forum.xda-developers.com/doogee-mix/development/doogee-mix-2-twrp-recovery-t3727788
Now I just need to be able to install the linage Os 15 and it will be perfect
Click to expand...
Click to collapse
Interesting. The TWRP link doesn't work and there are no instructions for Magisk/root.
I don't use xposed.
ironman76 said:
And you forgot xposed
Click to expand...
Click to collapse
Rudolpht said:
Interesting. The TWRP link doesn't work and there are no instructions for Magisk/root.
Click to expand...
Click to collapse
If you had read the post that I posted, you would see that marco.fortuna, has posted the link to download TWRP Recovery Doogee MIx2.img and if that function correctly. It also explains how to install it.
https://drive.google.com/file/d/1UxPcIm4KmZAKtOjDhqPiYF3cRDyYT9Sf/view
I recommend you read some basic adb and fastboot guide. There are also many posts that explain how to install masgisk and configure it.
oritome said:
If you had read the post that I posted, you would see that marco.fortuna, has posted the link to download TWRP Recovery Doogee MIx2.img and if that function correctly. It also explains how to install it.
https://drive.google.com/file/d/1UxPcIm4KmZAKtOjDhqPiYF3cRDyYT9Sf/view
I recommend you read some basic adb and fastboot guide. There are also many posts that explain how to install masgisk and configure it.
Click to expand...
Click to collapse
Thank you. This is partially no one's fault to the extent there isnt's a Doogee MIX 2 forum. having rooted most major manufacturer phones.
So no one else is getting TWRP-loops, like boot loops, only back to TWRP?? Rooted kernel also doesn't seemed loadable from in TWRP or fastboot, though assume not needed for magisk compatible system.
Is supersu also working?
I would go to ROMs and Kernels subforum for a better discussion, but I haven't been able to do an uninstall of magical to install supersu successfully.
Rudolpht said:
I would go to ROMs and Kernels subforum for a better discussion, but I haven't been able to do an uninstall of magical to install supersu successfully.
Click to expand...
Click to collapse
Hi Rudolpht, i also tested without Magisk, only SuperSu.zip flashed in recovery ( without Error), but it's not installed.. but doesn't matter because with Magisk i stay great.
PS. If you need Info for Update, how I did with Sp Tool, so let me know.
ironman76 said:
Hi Rudolpht, i also tested without Magisk, only SuperSu.zip flashed in recovery ( without Error), but it's not installed.. but doesn't matter because with Magisk i stay great.
PS. If you need Info for Update, how I did with Sp Tool, so let me know.
Click to expand...
Click to collapse
If there is a trick to getting SP flash to work, that would be great. I copied the directory about 3 times to get away from the Chinese characters, which helped me ultimately to try moving the img files to sdrom and TWRP install, but an easy way to use the tool would be great.
Rudolpht said:
If there is a trick to getting SP flash to work, that would be great. I copied the directory about 3 times to get away from the Chinese characters, which helped me ultimately to try moving the img files to sdrom and TWRP install, but an easy way to use the tool would be great.
Click to expand...
Click to collapse
yes, only 2 easy steps to do, i will write you later an PN?, because at the moment i'm busy.
ironman76 said:
yes, only 2 easy steps to do, i will write you later an PN?, because at the moment i'm busy.
Click to expand...
Click to collapse
Thanks. At your convenience with many thanks!
I was thinking of TWRP backing up and then going to stock and taking update then TWRP and data restore. Splash would certainly make it easier.
Rudolpht said:
Thanks. At your convenience with many thanks!
I was thinking of TWRP backing up and then going to stock and taking update then TWRP and data restore. Splash would certainly make it easier.
Click to expand...
Click to collapse
thank you too. I did a backup from apps+data with titanium backup, without any problems
Hi!
I'm running into bootloop after an oem unlock and TWRP flash.
Now, the phone starts in TWRP continuously, volume up + power doesn't work anymore.
Has someone a solution for that please?
Thanks.
Hi Friends
My wife by mistake deleted important files. Tried Dr. Fone and others but need to root before doing deepscan to recover. I spend hours and but error all the time at 80% because no root access.
I have no choice but to unlock bootloader without backing up TA neither I know how to do it.
Due to late night no time to manually sideloads, but bought Xperfix to do the job to TWRP/ROOT/DRM
So far twrp installed successfully but not rooted nor installed magisk . Let me pull the usb at 20% and wait twrp to reload after 100% nothing done. Maybe twrp not mounted system properly?
I am also worry now after seeing others saying that unlocking bootloader will effect the camera functions?
But as per xperfix 3.0 it says the problem been solved.
How is this Xperfix does it really work ?
try flashing magisk 16 in recovery and see if you get root.
ofuroinu said:
How is this Xperfix does it really work ?
Click to expand...
Click to collapse
When you bought Xperiafix you also bought support from the developer. Go back to sToRm//'s website and raise a support ticket.
If you include the txt logs found in c:\xperiafix that would be helpful
I have used his tool on my XZ1 compact, so I know it works, but getting the right drivers installed on your Windows machine is a real minefield. Windows chooses the wrong drivers by default when you connect the phone with TWRP running. This sounds like your problem to me. You have to manually add them with the phone connected TWRP on.
Also, you can't just install the drivers in Windows 10 (Windows doesn't tell you it failed to install the drivers, you just can't connect.), you have to go into safe mode and install the drivers with 'driver signing disabled',
There is a lot of helpful advice in the original Xperiafix thread, along with the links to drivers required.
Edit: you have to pull the USB at 20%, go into TWRP yourself (from powered off, hold volume down & power, wait until phone starts, keep volume down for a few more seconds) and swipe to make system partion writeable, then reconnect phone and Xperiafix will do the rest.
appreciate your reply , I have tried many times reflashing with xperifix when twrp reach 20% to restart it wont restart auto I need follow on screen instructions to do and mounted the system untic the and finished to 100% but again no magis and no drm . I copied the magis file from xperifix folder and flashed directly now have rooted already. Only thing why I have been using xperfix because of camera issue and is green. Support no reply yet since yesterday.
Can I manually flash the drm and fix the camera issue ? Please guide me my wife is so sad about this incident.
ofuroinu said:
appreciate your reply , I have tried many times reflashing with xperifix when twrp reach 20% to restart it wont restart auto I need follow on screen instructions to do and mounted the system untic the and finished to 100% but again no magis and no drm . I copied the magis file from xperifix folder and flashed directly now have rooted already. Only thing why I have been using xperfix because of camera issue and is green. Support no reply yet since yesterday.
Can I manually flash the drm and fix the camera issue ? Please guide me my wife is so sad about this incident.
Click to expand...
Click to collapse
you should be able to flash drm fix from xperifix folder. if im right it should be in you Local Disk C folder.
raven213 said:
you should be able to flash drm fix from xperifix folder. if im right it should be in you Local Disk C folder.
Click to expand...
Click to collapse
Hi Raven I can see the DRM Folder with files but which files to flash or if have any instructions somewhere to follow to avoid error.
DRM >
Lib folder
Lib64 folder
sfk application
Or I just need to run sfk app in twrp that's it?
ofuroinu said:
appreciate your reply , I have tried many times reflashing with xperifix when twrp reach 20% to restart it wont restart auto I need follow on screen instructions to do and mounted the system untic the and finished to 100% but again no magis and no drm . I copied the magis file from xperifix folder and flashed directly now have rooted already. Only thing why I have been using xperfix because of camera issue and is green. Support no reply yet since yesterday.
Can I manually flash the drm and fix the camera issue ? Please guide me my wife is so sad about this incident.
Click to expand...
Click to collapse
Can you post the logs from the C:\Xperiafix folder?
Once you have reached the 20% step and gone into TWRP to enable system file write and plug the phone back in, Xperiafix continues if it does nothing then the drivers are wrong.
You will know when the drivers are right as the phone restarts itself once it's been reconnected to Xperiafix.
Read this thread on the original app, everything is explained and the drivers linked
Explanation from sToRm//, help is on the way!
I got it fixed by reinstalling and use WIN10 . Now all set. Appreciate to all my friends on XDA for assisting me.
I want to now after this will I be still getting OTA from Sony can update or need manually update?
How is the battery life after using xperfix?
Hi Friend I am back again with some help need.
I want to know how to install Android Pay on root phone?
My wife said she failed to install because phone is rooted.
ofuroinu said:
Hi Friend I am back again with some help need.
I want to know how to install Android Pay on root phone?
My wife said she failed to install because phone is rooted.
Click to expand...
Click to collapse
Android pay will work if you follow Xperiafix. Magisk will install and if you select 'magisk hide' in the settings you will be able to use android pay. It's ok, you don't have to pretend it's your wife's phone
Hi Mate
Thats what we did but failed with Android Pay at counter.
Also bank applications refuse to install because phone was rooted.
Do banking applications works on rooted phone?
Tapatalk を使用して私の MIX から送信
ofuroinu said:
Hi Mate
Thats what we did but failed with Android Pay at counter.
Also bank applications refuse to install because phone was rooted.
Do banking applications works on rooted phone?
Tapatalk を使用して私の MIX から送信
Click to expand...
Click to collapse
Have you tried to run Safteynet after you have installed Magisk? (on the Magisk start page)
Do you have Xposed installed?
There is no way to hide Xposed and it will fail Safteynet
I have several banking apps that work and one that refuses to install
Nope I did not install xposed.
Here is the problem after clicked start safety net the status all are failed.
ctsProfile:false
basicintegrity:false
Magisk version v.16.0
Installed ver 16.3
Tapatalk を使用して私の MIX から送信
Got is solved by hiding safety check passed.
But still the citibank app refused to run due to rooted phone.
Anyone tried this app if working?
Regarding android pay do I need to run safety net check each time before using it?
Tapatalk を使用して私の MIX から送信
Now we have received notifications of OTA Updates I want update her phone . Do I need to follow exactly as per below link ?
How about settings and data will that remain? Because I use TWRP on my other phones to flash roms which is fast and safe.
Why we dont have same solution for Sony but need use newflasher tools?
https://forum.xda-developers.com/showpost.php?p=72958788&postcount=16