Kali NetHunter with Custom Bootimage - BLU R1 HD Guides, News, & Discussion

I was looking at how close my Nexus 5 really is to my R1 HD, and besides the obvious Qualcomm MTK thing they are amazingly similar.
I took the official Hammerhead NetHunter 3.0 Marshmallow zip and put it on my external and card.
I then did a factory reset including dalvik and cache in TWRP.
Installed SuperSU and booted my phone. I then installed Busybox Pro and rebooted back into TWRP.
Once in TWRP I clicked install and chose my saved nethunter-hammerhead-marshmallow-3.0.zip
It will open the Aroma installer. On the first screen click everything except the RF Analyzer, MAKE SURE YOU HAVE THE OLDER VERSION OF SUPERSU CHECKED TO INSTALL AS WELL.
On the next screen click everything but custom boot screen and custom wallpaper.
Click next and be patient while it installs everything, extracts the chroot image, and verifies the extract. Took about 10-12min till it completed to 100%.
A funny side note.....when running this on My Nexus 5 it would always freeze between 90-93? and after about an hour of being frozen I would do a hard reboot. On a Nexus 6 I would install it on, same thing but if I didn't wait 90+min I couldn't later manually install chroot or any metapackages.
After install finishes reboot your phone. Once rebooted I opened up From Toolbox Pro and used Root Browser to open the Hammerhead install zip. Once opened I extracted bootanimation.zip from system/media and Hammerheadwallpaper from wallpaper.
Go to Boot Animations in Rom Toolbox Pro, choose local and you can either install bootanimation.zip as it is, or choose resize and change the framerate up to 40.
Then open wallpaper chooser from your desktop and choose Hammerheadwallpaper from your extracted folder.
Finally open the NetHunter app and click install chroot. Once it verifies it already is then choose install metapackage. I always choose the forensics package.
Once that is installed go ahead and reboot your newly modded phone with a working Kali Linux install on it.

So does this mean that other ROMs meant for the Nexus 5 could more or less function on the R1?

wh00p said:
So does this mean that other ROMs meant for the Nexus 5 could more or less function on the R1?
Click to expand...
Click to collapse
I'm not a kernel person and that's the only thing that didn't work, was Kali dirty kernel changing.
I honestly can't answer that but seems plausible to me if someone can figure out the kernel thing.
Sent from my BLU R1 HD using XDA Labs

wh00p said:
So does this mean that other ROMs meant for the Nexus 5 could more or less function on the R1?
Click to expand...
Click to collapse
this isnt a rom it's a linux system you flash ON TOP of the n5 stock rom, so no

This is incredible, thank you for sharing!

I had my hopes up at first, but now I'm getting skeptical. If a kernel port wouldn't work, how can this boot considering the differences between mediatek and Qualcomm?
Unless that just doesn't even matter at all, considering its like a virtual machine computer-inside-a-computer

jasonmerc said:
I had my hopes up at first, but now I'm getting skeptical. If a kernel port wouldn't work, how can this boot considering the differences between mediatek and Qualcomm?
Unless that just doesn't even matter at all, considering its like a virtual machine computer-inside-a-computer
Click to expand...
Click to collapse
There is a universal kernel option in setup. Like I said though it didn't flash the kernel to kalidirty kernel. Everything else worked though. With the views I'm sure someone else can verify they got it working as well.

blu kernel source, binaries available?
Are the blu kernel source, binaries available to try and create a custom ROM?

That's a nice option!
I was actually looking at https://www.pwnieexpress.com/products/pentesting-community-editions yesterday which may be another cool alternative to this one, to see if there was a way to build this for the Blu.
I don't think the Nexus 5 image will work out of the box but there are detailed instructions on how to build a custom rom too, maybe when the device-tree etc is working for CM we will be able to give it a try.
(also the lack of USB OTG will be very detrimental)

emc2cube said:
That's a nice option!
I was actually looking at https://www.pwnieexpress.com/products/pentesting-community-editions yesterday which may be another cool alternative to this one, to see if there was a way to build this for the Blu.
I don't think the Nexus 5 image will work out of the box but there are detailed instructions on how to build a custom rom too, maybe when the device-tree etc is working for CM we will be able to give it a try.
(also the lack of USB OTG will be very detrimental)
Click to expand...
Click to collapse
have you done anymore looking into the AOPP ?

wfandreas said:
have you done anymore looking into the AOPP ?
Click to expand...
Click to collapse
Yes, but no success so far.

HeeyMaan said:
I was looking at how close my Nexus 5 really is to my R1 HD, and besides the obvious Qualcomm MTK thing they are amazingly similar.
I took the official Hammerhead NetHunter 3.0 Marshmallow zip and put it on my external and card.
I then did a factory reset including dalvik and cache in TWRP.
Installed SuperSU and booted my phone. I then installed Busybox Pro and rebooted back into TWRP.
Once in TWRP I clicked install and chose my saved nethunter-hammerhead-marshmallow-3.0.zip
It will open the Aroma installer. On the first screen click everything except the RF Analyzer, MAKE SURE YOU HAVE THE OLDER VERSION OF SUPERSU CHECKED TO INSTALL AS WELL.
On the next screen click everything but custom boot screen and custom wallpaper.
Click next and be patient while it installs everything, extracts the chroot image, and verifies the extract. Took about 10-12min till it completed to 100%.
A funny side note.....when running this on My Nexus 5 it would always freeze between 90-93? and after about an hour of being frozen I would do a hard reboot. On a Nexus 6 I would install it on, same thing but if I didn't wait 90+min I couldn't later manually install chroot or any metapackages.
After install finishes reboot your phone. Once rebooted I opened up From Toolbox Pro and used Root Browser to open the Hammerhead install zip. Once opened I extracted bootanimation.zip from system/media and Hammerheadwallpaper from wallpaper.
Go to Boot Animations in Rom Toolbox Pro, choose local and you can either install bootanimation.zip as it is, or choose resize and change the framerate up to 40.
Then open wallpaper chooser from your desktop and choose Hammerheadwallpaper from your extracted folder.
Finally open the NetHunter app and click install chroot. Once it verifies it already is then choose install metapackage. I always choose the forensics package.
Once that is installed go ahead and reboot your newly modded phone with a working Kali Linux install on it.
Click to expand...
Click to collapse
Which supersu did you install ?

HeeyMaan said:
I was looking at how close my Nexus 5 really is to my R1 HD, and besides the obvious Qualcomm MTK thing they are amazingly similar.
I took the official Hammerhead NetHunter 3.0 Marshmallow zip and put it on my external and card.
I then did a factory reset including dalvik and cache in TWRP.
Installed SuperSU and booted my phone. I then installed Busybox Pro and rebooted back into TWRP.
Once in TWRP I clicked install and chose my saved nethunter-hammerhead-marshmallow-3.0.zip
It will open the Aroma installer. On the first screen click everything except the RF Analyzer, MAKE SURE YOU HAVE THE OLDER VERSION OF SUPERSU CHECKED TO INSTALL AS WELL.
On the next screen click everything but custom boot screen and custom wallpaper.
Click next and be patient while it installs everything, extracts the chroot image, and verifies the extract. Took about 10-12min till it completed to 100%.
A funny side note.....when running this on My Nexus 5 it would always freeze between 90-93? and after about an hour of being frozen I would do a hard reboot. On a Nexus 6 I would install it on, same thing but if I didn't wait 90+min I couldn't later manually install chroot or any metapackages.
After install finishes reboot your phone. Once rebooted I opened up From Toolbox Pro and used Root Browser to open the Hammerhead install zip. Once opened I extracted bootanimation.zip from system/media and Hammerheadwallpaper from wallpaper.
Go to Boot Animations in Rom Toolbox Pro, choose local and you can either install bootanimation.zip as it is, or choose resize and change the framerate up to 40.
Then open wallpaper chooser from your desktop and choose Hammerheadwallpaper from your extracted folder.
Finally open the NetHunter app and click install chroot. Once it verifies it already is then choose install metapackage. I always choose the forensics package.
Once that is installed go ahead and reboot your newly modded phone with a working Kali Linux install on it.
Click to expand...
Click to collapse
what command it that last pic?

wfandreas said:
Which supersu did you install ?
Click to expand...
Click to collapse
Originally I installed the one off the Google play store and then pro off the store as well.
Once installing nethunter I used the older supersu that comes in the zip.

wfandreas said:
what command it that last pic?
Click to expand...
Click to collapse
That's the bootup from vnc. You have to go set your passwords and boot into it.

HeeyMaan said:
That's the bootup from vnc. You have to go set your passwords and boot into it.
Click to expand...
Click to collapse
thank you, I did the same install, works well.

Related

[ROM][KANG] CherryKANG 0.9.4 1512max 384min [CM9] synced [11/04] Now supports goo.im!

Hi guys..
I just want to say thanks to the cm team for bringing ics to our touchpads. None of the work in this rom is my own.. I have just used the great tutorials and stuff I've picked up before to compile this. All credit to everyone who put work into this!
This rom includes cherry-picks from http://review.cyanogenmod.com such as the fixes below
A wifi fix -- review.cyanogenmod.com (Although some people are reporting wifi issues still. I recommend a full wipe)
I have also compiled my own kernel into this.. which I set the default CPU speed to 1.5ghz and the default governor to ondemand. I also added HAVS support. Although I don't know if we really need it on a tab. Maybe it will help slightly with battery life?
These are settings that I like and normally run. So don't flame me!
I am looking for pointers too.. for what to do next. I would like to add the webOS style recent apps mod next. Also ROMControl would be nice from here .. some pointers on how to include would be helpful. Any help greatly appreciated
So.. please remember.. I made this for myself... to teach me something.. someone just said I should post it!All credit goes to the people that contribute to cyanogenmod.
Cheers and enjoy
Buy me a beer if your a fan! Hit donate!
IN THIS BUILD
0.9.4 --- UPLOADING AS WE SPEAK!! Check back in an hour
Hopefully now has Goo.im app support for ease of updates
Not much else (synced 11/04)
managed to put this quick one together in the midst of everything.. so not had much chance to test. let me know how it is.
DOWNLOADS
http://goo-inside.me/devs/philicibine/ Thanks for hosting! Loving the download numbers here guys .. thanks for the support
http://www.cherrykang.mythreed.com/CherryKANG/ Big thanks to @Jedipottsy for this one.
Thanks for all the support from everyone!
Gapps are not included
My antutu benchmarks have been over 6000 btw
Hit the thanks button!
Previous Builds
0.9.3
Now with 4.0.4 inside!!
New Cyanogenmod boot animation!! I left this in coz it looks cooool
Min CPU clock is 384 (No more SoD's!)
Synced 31/03
Lots of new commits so YOU MUST FLASH GAPPS AGAIN!
0.9.2
Min CPU clock is 245 now.
Synced 10/03
Lots of new commits so YOU MUST FLASH GAPPS AGAIN!
0.9.1
Synced 08/03
Netflix and YouTube HD FIXED -- Thanks to wtogami for his cherry-pick script.
0.9
Synced 07/03
Now has stylus input merged
unsure if netflix works yet (please test) and.. nope! It doesn't :'-(
CherryKANG-Bricked
AS REQUESTED -- No changes.. just a bricked kernel thanks to show-p1984
0.8.9
At last it works! Lol
Synced 28/02 should have Netflix - edit - doesn't
Wifi fix
120 dpi - see post 2 for market fix
CherryKANG wallpaper - awesome!
0.4.8a
Kernel rebaked into it. should be lots smoother now
0.4.4a
kernel and wifi fixed
nothing else changed just wanted to get back to a working state
0.4.1a
re-done kernel as last build compiled with standard cm kernel
0.4a
Removed 270 degree rotation coz it derped the bootup :-/
Recompiled the kernel and increased min cpu to 245 (sleep issues)
0.3a First CherryKANG named build! lol =D
270 degree rotation
dpi set to 132 (Requires fixed market apk)
wifi scan interval increased
0.2a
Novalauncher - hope its OK?!
Scrolling cache fix - for smoother scrolling in the browser and other apps. (Kanged from aokp github) credits to them
And a pretty tasty boot animation! From MindSplit - thanks!
Hope you likey
REMEMBER ... This is now 120 dpi. You will either need to download LCD Density Pro from the market, or see below for a free alternative!
Posted by Hockey4life0099 thanks!
or you can use the free version (or dpi changer) to modify the dpi back to 160
---------- Post added at 02:15 AM ---------- Previous post was at 02:03 AM ----------
I wrote this. It looks more complicated than it is cause i broke it down step by step. Ignore my cracked out numbering scheme, i didnt feel like shifting all the numbers down when i added more info.
1. If you dont already have it, download es file explorer
1b. go to the application settings and clear the data for the market
1c. download dpi changer and change dpi to 135(dont reboot yet)
2. go into the options on there and check the root explorer option and the mount option
3. download to TP
http://www.sundergaming.com/downloads/tabletmarketdpiunlocked.apk
4. rename the file Vending.apk
5. long press to copy the file (in ES file explorer)
6. click the star in top right corner (favorites)
7. Choose the phone (/)
8. navigate to system/app
9. paste the app
10. find the app in there called marketupdater.apk or something similar and rename it marketupdater.apk.bak
11. reboot
12. see if you can download an app like flash player. If you cant go to next step
12b. get back to system/app and click the Vending.apk and let it install.
You can mess around with the dpi if you want, but also remember that if the text is small, you can change the default text size in the settings.
The issue i encountered with this method is sometimes the fix stops working, but all you need to do to get the apps to download once again is clear your market data in the application settings. It is obviously much easier to download the app mentioned in the op, but this is for the cheapskates. your only other option is download dpi changer and just switch the dpi back to 160. That is painless but you loose out on some app compatibility and some screen real estate. I myself change the dpi to 138 and change the font size to large. Everything seems to be perfect. Best balance out there IMO.
nevertells2 said:
Do not install CM9 over CM7. Some have gotten away with it and others like yourself run into trouble. Do a clean install, that means running ACMEUninstaller. Here are some instructions I created just for an occasion such as this:
Since the release of CM9, it has become abundantly clear to me that one
needs to do a clean install of the rom to avoid all the little
nagging issues that so many folks are reporting. Whether you are
installing for the first time, upgrading from CM7 or installing
an update of CM9, one really needs to do a clean install.
Since the advent of the official CM9 nightlies, installing
the rom and the Gapps files via CWM seems to be much more
reliable. You still need to wipe the cache and Dalvik cache
before you reboot after installing any rom. If you run into
trouble after an install via CWM, then read on.
Those who know how to do it otherwise and are comfortable with that
feel free to deviate from this document.
For first time installers, you can skip this part. First thing
you need to do is a nandroid backup of your current install and
copy it over to your PC for safe keeping. Next you should backup
your apps using either Titanium Backup or My Backup Root. This will
allow you to restore all your apps after you are done with this
update. If the install goes South, you can always restore your
nandroid backup.
For the first time installers, if you have not already prepared
your PC for this project, you need to download the following:
1. ACMEInstaller2
2. ACMEUninstaller
3. Moboot 0.3.5.zip
4. ClockworkMod.zip(CWM)
5. update-cm-9.0.0-RC0-Touchpad-alpha2-fullofbugs.zip
6. UniversalNovacomInstaller.jar
7. The latest Gapps.zip
The ACME files, Moboot, CWM and the Alpha2.zip can all be found
on the OP for Alpha2 at:
http://rootzwiki.com/topic/18843-releasealpha2-cyanogenmod-9-touchpad/
The universal novacom installer and Gapps files can be found by doing a Google
search on the names above and you will find the download page. I found
the novacom installer here:
http://universal-novacom-installer.googlecode.com/files/UniversalNovacomInstaller.jar
You should download the latest Gapps.zip which
the last time I checked at the link below was 20120317:
http://wiki.rootzwiki.com/Google_Apps
First thing, open the run box on your PC and browse to the novacomInstaller
file. This is a Java executable, so treat it just like any .exe file.
However, since it does not end in .exe, when you browse to find it,
you will have to tell the browser to show "All Files." Once it is in
the run box, click on OK and the Novacomd drivers will be installed,
the Palm,inc folder will be created and the novacom.exe will be placed
in that folder. Next if the ACME files you downloaded are zips, unzip
them both into the Palm, Inc folder which you will find in the Program
files folder. If not zipped, copy both into the Palm, Inc folder. Now
your PC is prepared for installing CM9, so everything applies to first
installers and upgraders from this point forward.
First timers boot into WebOS, upgraders can do the same or boot into
your current install of Android. Connect your TouchPad to your PC
with the usb cable and open Windows Explorer on your PC. You should
see either the TouchPad as a drive, or cm_tenderloin if you are already
running a version of CM9. If you have not already created a cminstall
folder on your TouchPad do so now. Also create a folder named ICS
Install.
Next you need to copy Moboot 0.3.5 and ClockworkMod(CWM) into the
cminstall folder on your TouchPad. Now copy the rom.zip and the
Gapps.zip file into the folder you created named ICS Install. It's up
to you which rom and Gapps file you use if you are installing something
different from what is listed above. If you are copying files to the
Touchpad drive, you now need to right click the drive letter and eject
the drive when you are done. If you are copying files to cm_tenderloin,
you can just close Windows Explorer and both of you disconnect the usb cable.
Upgraders, now you need to run ACMEUninstaller and when it is done, your
TouchPad will reboot back into WebOS. Now both of you need to reboot while
holding down up volume to put the TouchPad into WebOS recovery or bootie
mode. You will know you succeeded if you see a large white usb symbol.
Now plug the usb cable back in and you should hear the PC beep indicating
the TouchPad is connected. You will not be able to see the TouchPad in
Windows Explorer, so don't try. On your PC click "RUN" and type in CMD.
This opens the command window. First timers type in the following in the
command window:
cd/ and press enter. You will see C:\
Now type cd program files and press enter. You will see C:\program files
Now type cd Palm, Inc and press enter. You will see C:\ program files\Palm, Inc
Upgraders, your novacom.exe may be in a different folder, so go browse to that folder.
Both of you enter novacom boot mem:// < ACMEInstaller2 in the command window and
hit enter. After a few seconds, you should see what is fondly called the "Double Penguin" on
the Touchpad. When the install is done, the TouchPad will boot to Moboot. Tap
the volume on the TouchPad to stop the 5 second countdown if you see one. Now
select CWM using the Home button, then Install zip file from SD card and use the
volume rocker to move down to the ICS Install folder. Select that and move to the
Alpha2.zip and select that. Start the install. When it is done, use the go back
selection to go back to the main CWM screen and select reboot.
Once Android is booted up(be patient, it takes a couple of minutes the first time),
play around with the browser, set up wifi, just to make sure your install was
successful. Now reboot back to CWM and do the same procedure to install the Gapps.zip
you copied to the ICS Install folder earlier. You're done with a clean install.
Upgraders, you know what to do, first timers, I hope you have friend around to show
you the ropes or you own an Android phone and already know the ropes. Good Luck!
P.S. I strongly suggest you make a nandroid backup of your new installation right now.
First timers, one makes a nandroid backup using CWM. Boot to CWM, select "Backup and
Restore" and select "Backup".
Click to expand...
Click to collapse
Sent from my cm_tenderloin using xda premium
what's the wifi fix ?
This one http://review.cyanogenmod.com/12342
Sent from my cm_tenderloin using xda premium
Does this have Gapps cooked into it?
No sorry... I'm using v11 though
Sent from my cm_tenderloin using xda premium
Ok thanks...
If we have CM7 installed do we do a factory reset/wipe of the caches and then install the zip directly?
dtwconsulting said:
If we have CM7 installed do we do a factory reset/wipe of the caches and then install the zip directly?
Click to expand...
Click to collapse
Yep.. I think so. I think you can also flash without a wipe.. but wouldn't recommend.. and if you do.. flash the latest gapps
Sent from my cm_tenderloin using xda premium
Cheers mate
hi, whats the webOS style recent apps mod you mention in the OP?
Drop Box link already dead
Any one have a mirror?
Thanks!
MatthewYiu said:
Any one have a mirror?
Thanks!
Click to expand...
Click to collapse
Still working for me as of 10:40am. But.... here's a mirror just in case.
http://www.mediafire.com/?q60g82098q1vh16
Gapps v11:
http://goo.gl/u9s8g
For additional related files and mods, see sprice's thread here:
http://forum.xda-developers.com/showthread.php?t=1452324
f_padia said:
hi, whats the webOS style recent apps mod you mention in the OP?
Click to expand...
Click to collapse
When u hold home.. the apps come across the screen horizontally. Looks like the card feature of webOS.
Its in AOKP so I might have a look at their github later.
Sent from my HTC Vision using xda premium
tapout27 said:
Does this have Gapps cooked into it?
Click to expand...
Click to collapse
Read much?
how about hw acceleration?
mercado79 said:
Still working for me as of 10:40am. But.... here's a mirror just in case.
http://www.mediafire.com/?q60g82098q1vh16
Gapps v11:
http://goo.gl/u9s8g
For additional related files and mods, see sprice's thread here:
http://forum.xda-developers.com/showthread.php?t=1452324
Click to expand...
Click to collapse
flashing now! =)
Hello,
is the wifi fix included in the kernel? if so, is it possible to make a only a kernel-package to flash with CWM over the standard CM9-0.6?
Thanks
Not quite sure how to do that just yet. Will look at some other kernels tomorrow
Sent from my cm_tenderloin using xda premium
coolineho said:
how about hw acceleration?
Click to expand...
Click to collapse
This is just a kang. I lack the knowledge to even attempt looking into that!
Its working the same as cm
Sent from my cm_tenderloin using xda premium

[Q] rw mounting help

Hey im sure im one of many who have asked this but I looked around I couldnt find a solution that worked for me
My goal is only to change my lock ring softkeys and glowdots simple right? It always was until recently...
Ive tried a few roms and I installed busybox completely its updated and everythimg I do have root acess
My bootloader is indeed unlocked. And everything is done correctly
I am running 4.4.2 a custom somy z1 rom on nexus 4 16gb
I have tried both zipthemer and metamorph and
Metamorph claims rw is not mounted
On some roms I was able to chamge softkeys in some cases and not be able to do lock rings though
My questions are can you lead me to mounting and it would be lovely if someone can explain to me how this works and why I could change one but not the other.
Thank you
KrisLovesTacos said:
Hey im sure im one of many who have asked this but I looked around I couldnt find a solution that worked for me
My goal is only to change my lock ring softkeys and glowdots simple right? It always was until recently...
Ive tried a few roms and I installed busybox completely its updated and everythimg I do have root acess
My bootloader is indeed unlocked. And everything is done correctly
I am running 4.4.2 a custom somy z1 rom on nexus 4 16gb
I have tried both zipthemer and metamorph and
Metamorph claims rw is not mounted
On some roms I was able to chamge softkeys in some cases and not be able to do lock rings though
My questions are can you lead me to mounting and it would be lovely if someone can explain to me how this works and why I could change one but not the other.
Thank you
Click to expand...
Click to collapse
What's the problem with zipthemer? Never fails me so far.
arffrhn said:
What's the problem with zipthemer? Never fails me so far.
Click to expand...
Click to collapse
Can you give me your directions I used to always use it
But sometimes itll only make some mods work and Some not
KrisLovesTacos said:
Can you give me your directions I used to always use it
But sometimes itll only make some mods work and Some not
Click to expand...
Click to collapse
1. Make sure you are rooted.
2. Download the lockring you want and copy it into your phone (or just download it using phone).
3. Install zip themer app.
4. Update edify (make sure you have the rom zip which you are currently using saved in your phone storage).
5. Choose theme and select the previously downloaded lockring.
6. Create it.
7. Note the new zip file created for the lockring.
8. Reboot into recovery. Flash the newly created zip.
9. Reboot into system and that's it.
More detailed steps here. http://forum.xda-developers.com/showpost.php?p=39572221&postcount=18
arffrhn said:
1. Make sure you are rooted.
2. Download the lockring you want and copy it into your phone (or just download it using phone).
3. Install zip themer app.
4. Update edify (make sure you have the rom zip which you are currently using saved in your phone storage).
5. Choose theme and select the previously downloaded lockring.
6. Create it.
7. Note the new zip file created for the lockring.
8. Reboot into recovery. Flash the newly created zip.
9. Reboot into system and that's it.
More detailed steps here. http://forum.xda-developers.com/showpost.php?p=39572221&postcount=18
Click to expand...
Click to collapse
Didnt work

[GUIDE] Get Xposed working on your deodexed TouchWiz based Lollipop ROM! 2015/08/17

DISCLAIMER
The process of flashing a custom recovery/kernel/firmware may and will trigger your device's Knox Counter. Neither XDA nor I can be held responsible for your actions. Proceed with caution. During this process you will lose all your settings and apps. As long as you follow the instructions, your device's storage, internal and external, won't be touched​
Still not compatible with x64 systems! Not compatible with Samsung 5.1.x (sdk22) ROMs!
Hello, Ladies and Gentleman
Many people seem to have a hard time to understand how all of this here on XDA works. I constantly get PM's from users, asking how to do the most basic stuff like flashing a .zip or stock firmware via Odin. Usually, I don't even read them and just hit delete. I know it's not ok to deny people help, so I decided to show you how you can get Xposed working on your TW based stock or custom ROM since it's the most frequently asked question I get.
It's nothing you couldn't do if you'd just....
We're going to use @arter97's customized Xposed Framework as the one made by @darkera13 needs the user to manually modify and replace files which may be too complicated for some.
Preparation
-READ EVERYTHING OVER AND OVER AGAIN.
-A custom recovery System like TWRP or CWM (PhilZ or Stock)
-A deodexed ROM. It's the only way to go. YOU NEED A DEODEXED ROM. If your ROM is not deodexed and you flash the framework, you'll end up in a bootloop. To deodex your existing ROM carefully follow Post #2
Here are a few made by XDA Senior Member @_alexndr
Stock deodexed for SM-N9005 Galaxy Note 3 International Qualcomm.
Stock deodexed for SM-G900F Galaxy S5 International Qualcomm
-And the framework itself from here
[UNOFFICIAL] Xposed for Samsung Lollipop by arter97
-Flash a custom recovery system of your choice. This is listed under preperation on purpose since this guide is about getting Xposed on your TW Lollipop device. A guide on how to get a custom recovery system is most certainly available in your device's forum.
-Store the ROM and the Framework in an easy to find folder, which we're gonna call "folder x". It doesn't matter where you store it (ext. SD or int. SD)
The Fun Part
-Boot into your custom recovery and make a full wipe:
TWRP users: "Wipe>Advanced Wipe> Tick System, Data, Cache, Dalvik Cache> Slide to format.​CWM users: "Mounts and Storage> hit Format /System; hit Format /Data; hit Format /Cache.​
-Still in recovery system, install, or flash the files we put in folder x;
TWRP users: "Install> Navigate to folder x and choose the ROM file first> Add Zip> now choose the Xposed Framework from folder x> Slide to flash.​CWM users: "Install Zip> Choose zip from /sdcard if folder x is on internalt storage or /storage/sdcard1 if folder x is on ext. storage (SD-Card)>​choose the ROM file first> -Yes - install ROMXY.zip.​Do the same with the Xposed Framework zip file.​
-Still in recovery system, reboot device and wait for it to boot. It can take up to 20 minutes. Enjoy Xposed on your Samsung TouchWiz Lollipop ROM.
-Stuck in a bootloop? Try this and repeat the process.
XDA Senior Member @Honzze kindly pointed out to keep following in mind; You have to start JoelDroid Lollipop Batch Deodexer with Admin permissions. Otherwise this error might return "path variable" of Java "is not set".
Deodexing your existing ROM without having to flash an entire ROM
As the title says, with this awesome guide by XDA Senior Member @townsenk you don't have to reflash an entire new ROM to your device. Instead, youll just deodex those parts of your System which need to be modified in order to get Xposed working. You don't necessarily have to perform a full wipe if you do it this way. But if you encounter fc's or end up in a bootloop, you know what to do
Guide for this guide:
Regarding point 1: "...launch a DOS shell..." just means, you need to open the so called "CMD" programm in Windows. To "launch a DOS shell" or CMD from within a folder, you simply have to hold down the shift key and right click in that folder. The context menu will show an entry "open command window here". And that's it! (Windows XP users may have to search the internet for another solution)
For Galaxy S5 and Note 3 users: If ADB returns "device offline" or an empty line after "List of devices attached" make sure your using a USB 2.0 data cable on a USB 2.0 port
townsenk said:
How to DeOdex YOUR (...) Rom.
I would like to note that I appreciate all the work that developers have put forth in creating and maintaining modified Roms. there are some awesome feature rich implementations available. My intentions are not to be critical of any specific Rom or mod. Without the developers we would have nothing.
(...)
This method is very common knowledge I thought I'd just explain it in an easy to understand way.
Here is what you need.
A stock (...) ROOTED configurated phone. Debloat as needed. Set the phone up exactly how you like it with apps and such.
Make sure it's stable. (If you have issues before DeOdexing they will be there afterward!)
Here's the files you may need to make this happen
LBD2.4.zip
7-Zip
Installer template (at end of post)
1> Make sure ADB is working on your computer. USB debugging turned on. Create a folder to store your soon to be download system files and launch a DOS shell from that working folder. Working folder name should NOT contain spaces. With the phone hooked up you should be able to type adb shell and get a prompt.
2> Type these commands
adb pull /system/app app/
adb pull /system/priv-app/ priv-app/
adb pull /system/framework framework/
This will take awhile and you will be left with three folders
Create a new folder named "system" and place these three folders inside.
3> Extract and launch LBD2.4 (This is the DeOdexer and is AWESOME). Point it at your recently created "system" folder and let it do it's thing.
I'll assume this will occur without errors as I have never had any.
4> At this point you can manually apply modded apk's to the system folder but I don't really recommend it. They can be applied afterward using the seperate installer zips.
5> with 7-Zip installed open the provided Installer template. Do not Extract it. Just open it in the 7-Zip file browser using the right click context menu in windows.
Drag-Drop the contents of your system folder into the empty system folder in the 7-Zip browser It should be the three folders previously created but now they are Deodexed. Close the 7-zip file manager and select Yes if it asks you to save.
Note: The provided installer template has been modified to only wipe and replace the three system directories.
6. Copy the created installer to your sdcard and install with recovery. Wipe cache and Dalvik before rebooting.
Go have lunch. You will sit at a boot screen for about 10 minutes. Then another 20 to rebuild caches. Time varies.
7. Your system will now be Deodexed! At this point you can install your mods one at a time, I recommend this so you can test your system between installs to determine if a specific mod is creating problems.
This method has so far removed ALL of my stability issues.
Click to expand...
Click to collapse
Since I no longer own this device, I'm retiring from this thread as of now. Hope I could help you.
Don't know if someone can help me as you stated that you're retired from this thread.
I did every step you do mentioned here (for self deodexing existing rom)
I did everything successfully and deodexed my files with 2.5 deodexer, putted files in the system folder to the 7zip folder and sent to my device and flashed zip, cleaned cache and dalvik and it stuck on booting for about 15 minutes. I know, it takes alot time during rebuildup of cache, but guys, it's 15 minutes! for me, if i cleanup cache and the dalvik/art cache, it just takes 1minute on boot screen to show up the image of each apps cache, but i just sat there with lots of patient for 15 minutes or a bit more and still same, stuck in same crappy booting logo.
I did restore my system files, now i'll try to retry it and send it again. Im suspicious of the zip file being corrupted during trasmitting to Device, however install was a big success so im very sure it wasnt corrupted. I'll do 2nd test and see it again if it's happening again.
If it does, i'll most likely try to figure out other ways to deodex as there is already deodexed roms out there, so they must have done is somehow.
Thanks, hope someone can help me out with this.
P.S: My adb works fine, i got usb drivers for my device, i got usb debug on, i got lots of space on phone, i got TWRP recovery which got very high compatibility when it comes to install anything from zip via recovery where almost all roms do work stable with TWRP.
omg brilliant @nitrous² ! thanks so much! its been days i keep trying to deodex with others tool...
Sachitoge said:
Don't know if someone can help me as you stated that you're retired from this thread.
I did every step you do mentioned here (for self deodexing existing rom)
I did everything successfully and deodexed my files with 2.5 deodexer, putted files in the system folder to the 7zip folder and sent to my device and flashed zip, cleaned cache and dalvik and it stuck on booting for about 15 minutes. I know, it takes alot time during rebuildup of cache, but guys, it's 15 minutes! for me, if i cleanup cache and the dalvik/art cache, it just takes 1minute on boot screen to show up the image of each apps cache, but i just sat there with lots of patient for 15 minutes or a bit more and still same, stuck in same crappy booting logo.
I did restore my system files, now i'll try to retry it and send it again. Im suspicious of the zip file being corrupted during trasmitting to Device, however install was a big success so im very sure it wasnt corrupted. I'll do 2nd test and see it again if it's happening again.
If it does, i'll most likely try to figure out other ways to deodex as there is already deodexed roms out there, so they must have done is somehow.
Thanks, hope someone can help me out with this.
P.S: My adb works fine, i got usb drivers for my device, i got usb debug on, i got lots of space on phone, i got TWRP recovery which got very high compatibility when it comes to install anything from zip via recovery where almost all roms do work stable with TWRP.
Click to expand...
Click to collapse
Same happened to me.... Did you solved this problem?
Maurizio1953 said:
Same happened to me.... Did you solved this problem?
Click to expand...
Click to collapse
Nope, i ended up using CM12 (at that time, right now i got cm13 update).
Well i had to deodex apps to get xposed on TouchWiz, but i failed and didn't get headache because of the Xposed modules being not really well compatible on TouchWiz, so i jumped to CM, i find it more stable, and the CM13 is insane because it saves so much battery at stand by, compared to lollipop, the Android 6.0.1 Marshmallow is the biggest update in android history, that saves hell lot of battery (it can be also maybe because i don't have Xposed Framework in recent rom).
Anyway, im tired of it, and i don't need to hassle with Link2Sd because of Android Marshmallow offering to mount the SD Card, in the end, all my needs are being offered in this (for me) huge, best android update, being Marshmallow.
Try it i would say, so amazing.
Ok i would like to go to cm13 as you but i stil need the support to the gear s smartwatch so i decided to stay with touchwiz without xposed.

[V4A] Viper4Android I/O Error (Driver Installation Failure) [FIX]

Hey everyone! I seem to have found put together 3 methods of installing/bypassing the V4A App on android. These methods include:
Regular Installation, and 2 Error bypasses/fixes.
If you get the error "superuser manager doesn't allow app to access su or you don't have root at all. fix this to use this selinuxmodechanger!", then you've come to the right place.
Requirements: ROOT, (maybe) TWRP (or anything you can flash the zip onto your phone with. With this tutorial I'll be using TWRP.)
If you don't have TWRP, here's the link to that \\ https://twrp.me/Devices/
Type in/select your device, click download, and flash it to your phone.
====================================================================================
Regular installation:
1.) Download V4A from Google Play Store \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
2.) Open, and grant root permission.
3.) Install drivers, and reboot phone. DONE!
==================================================================================================
V4A SuperSU Manager Error:
1.) Download V4A from Google Play Store (the newest one) \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
Open it, grant permissions, click "install drivers" <- just get through the driver menu. This is a troubleshoot test. If it fails, keep going on with the tutorial. If not, You're A-Okay.
2.) Download V4A Flashable ZIP from here \\ https://drive.google.com/file/d/0By-5wpCgi7OHMjFZRU1PYXljbDQ/view
Drag and drop from your computer onto your phone in your "Downloads" folder.
3.) Open TWRP and click "Install" and navigate to your "Downloads" folder where you Installed the V4A Flashable ZIP (Viper4AndroidMM_v2.4.0.1.zip)
Install the ZIP in TWRP, and reboot.
4.) Open your apps/app menu, navigate to the new (it's an older version, but it's newly installed) V4A. It should be a purple logo instead of a blue logo. At this point in the tutorial, you should have both the Google Play Store APK, and the TWRP Flashed APK. Open the PURPLE V4A, and Install drivers now.
5.) Reboot phone, go to the NEW (blue logo) V4A, and install drivers on that one too.
The rest is clean-up. You may now delete the older version of V4A (purple logo).
========================================================
Bypass/fix #2, The SELinuxModeChanger issue:
1.) Download V4A (newest version) from \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
2.) (Grant root access) Attempt to install drivers. If this succeeds, then Idk why you're still here.
3.) Download SELinuxModeChanger APK from \\ http://forum.xda-developers.com/devdb/project/dl/?id=12506
4.) Open it, grant root access, and click "Permissive".
5.) Re-boot phone, and open V4A when done.
6.) Install drivers!
Sources/credit go to:
https://forum.xda-developers.com/showthread.php?t=2524485
^ SELinuxModeChanger
https://forum.xda-developers.com/lg-g3/themes-apps/app-viper4android-v2-4-0-1-lg-g3-t3311403
^ Driver install failure/ Disc I/O error/"superuser manager doesn't allow app to access su or you don't have root at all. fix this to use this selinuxmodechanger!" error
https://twrp.me/about/
^ Team Win
https://forum.xda-developers.com/member.php?u=7249915
^ Me, I contributed very small amounts, that's why I'm last (I guess I contributed some common sense .. ?)
what if you already have permissive kernel , and still get i\o error during driver install?
using android auto 7.1.1 head unit.
masri1987 said:
what if you already have permissive kernel , and still get i\o error during driver install?
using android auto 7.1.1 head unit.
Click to expand...
Click to collapse
Follow this guide for installation if already permissive
https://forum.xda-developers.com/moto-x-2014/themes-apps/mod-viper-4-android-oreo-tested-t3700287
For i\o error you should do step No.8
zahidm said:
Follow this guide for installation if already permissive
https://forum.xda-developers.com/moto-x-2014/themes-apps/mod-viper-4-android-oreo-tested-t3700287
For i\o error you should do step No.8
Click to expand...
Click to collapse
my head unit doesn't have vendor/etc or the audio effects configuration file....
Thanks
I had the Viper.apk from their website and the Google play version loaded also and I was getting the I/O error when trying to load the driver and the Google Play version didn't work at all. I did try to load SuperSU and busybox before attempting to load the driver again and it still didn't work. I don't know about permissive kernel, I'm running Resurrection ROM on a Rooted Note 3. The way I got this to work was to uninstalled the V4A Viper APK version that I had retrieved and loaded from their website. Next I booted into TWRP recovery and installed the V4A Flashable ZIP from the link that I found here. Next I ran the flashed version and granted SU permissions when asked during the install driver process. The driver finally loaded and bingo it works now.
Viper4android
Hi I have installed viper4android fx but in Driver status it shows no processing my phone(samsung j700f) is rooted with Supersu and using Wycked custom Rom nougat based I have done All the method like rename audio_effect.conf file but nothing to happened. All are waste of time.i spend too much time on xda site for solution but not found any solution...can anybody help me please?...Sorry for my bad English.. Thanx in Advance
Banty448 said:
Hi I have installed viper4android fx but in Driver status it shows no processing my phone(samsung j700f) is rooted with Supersu and using Wycked custom Rom nougat based I have done All the method like rename audio_effect.conf file but nothing to happened. All are waste of time.i spend too much time on xda site for solution but not found any solution...can anybody help me please?...Sorry for my bad English.. Thanx in Advance
Click to expand...
Click to collapse
Follow simple steps, first Rename file.bak
Then flash V4A,
Than open V4a it will ask to install driver
Just hit install and wait, it freez for sometime.. and it will say done
Reboot
zahidm said:
Follow simple steps, first Rename file.bak
Then flash V4A,
Than open V4a it will ask to install driver
Just hit install and wait, it freez for sometime.. and it will say done
Reboot
Click to expand...
Click to collapse
But I did it already many times but U tell me little bit different you said rename it before flashing but I did it After flashing .I flashed the zip file and after that rename than open Viper4android fx...ok I will try it...Thanx
Banty448 said:
But I did it already many times but U tell me little bit different you said rename it before flashing but I did it After flashing .I flashed the zip file and after that rename than open Viper4android fx...ok I will try it...Thanx
Click to expand...
Click to collapse
You have to rename file before opening V4A app for the first time, now you rename it before or after flashing no matter,
Sent from my Nokia 5.1 Plus using Tapatalk
0
zahidm said:
You have to rename file before opening V4A app for the first time, now you rename it before or after flashing no matter,
Sent from my Nokia 5.1 Plus using Tapatalk
Click to expand...
Click to collapse
I already told u that I did it before opening the v4a
Banty448 said:
0
I already told u that I did it before opening the v4a
Click to expand...
Click to collapse
The error you are saying it never been seen, please try again
Sent from my Nokia 5.1 Plus using Tapatalk
zahidm said:
The error you are saying it never been seen, please try again
Sent from my Nokia 5.1 Plus using Tapatalk
Click to expand...
Click to collapse
I have done it many times but nothing happened. I tired to install this so now I install Devinebeats it's working fine.Thanx for us replies?
Banty448 said:
I have done it many times but nothing happened. I tired to install this so now I install Devinebeats it's working fine.Thanx for us replies[emoji106]
Click to expand...
Click to collapse
You didn't followed this guide?
https://forum.xda-developers.com/mo...od-viper-4-android-oreo-tested-t3700287/page2
Sent from my Nokia 5.1 Plus using Tapatalk
When I install drivers for ViPER4Android FX I get "Driver installed, please reboot your device." and when I reboot, I'm asked to install drivers again. Did anyone figure out how to successfully install these drivers? I saw fixed around the forum, but they don't seem to work for me.
My phone huawei p10 lite rom Resurrection Remix OS Beta 3!

[GUIDE] Root and/or install a GSI on razer phone 2 and pass safety net (For Windows)

YOUR WARRANTY IS NOW VOID! I am not responsible for anything that could happen, dead sd card, bricked phones, you name it. You chose to install this software and you face the risk of any bugs that may affect you. This is just a warning incase anything goes wrong
ISSUE: FASTBOOT Might not work on windows 10 version 2004, a solution is to use a Linux virtual machine to use fastboot commands. Test it out first as you might be lucky and it could work for you.
A complete guide on how to either just root the razer phone 2 and/or install a gsi with everything working.
The sections are: Basics - Installing TWRP - Rooting - Installing a GSI + Root - Passing safety net to use baking apps, certain games etc.
Basics: (You will have to factory reset if you have not unlocked your bootloader before)
Download this and this file, un zip them both and move them to a known directory such as C:\ADB
Then on your phone, go into developer options and enable OEM/Bootloader unlocking, and after that reboot into the bootloader by holding POWER + VOL DOWN and plug the phone into your pc (I recommend you connect it to a USB 2.0 port, as USB 3.0 might give you issues with the fastboot commands)
Then we need to install bootloader drivers onto our phone, so open device manager, click the drop down menu next to Android Device, right click on Android and select Update Driver, then select Browse my computer for driver software, Let me pick from a list of available drivers on my computer, Show all devices, Have disk and navigate to your folder where you extracted the .zips (in my case C:\ADB) and open the usb_driver folder and select android_winusb.inf. In the next menu select Android Bootloader Interface, proceed through the warning and install it.
To unlock the bootloader open a cmd window in the directory of your platform-tools folder, which in my case would be C:\ADB\platform-tools (type cd C:\ADB\platform-tools in cmd) and run two commands: fastboot flashing unlock (after each one select yes on your phone and let it reboot - it might take a while) and fastboot flashing unlock_critical
To install the arter97 kernel/TWRP: (keep your phone in the Bootloader and plugged into the pc)
Download both the .zip and .img file from this link (i am using r12 intentionally as it causes less issues) and download this zip file as well
Move both .zip files onto your phones SD CARD (important) and rename the .img file on your PC to Boot.img and place it into your platform-tools folder (C:\ADB\platform-tools in my case)
Open a command prompt window and like before change the directory to the platform-tools folder, then run two commands: fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
Now using the volume keys select the Recovery Mode option in the bootloader and press the power key to select it, if it asks for a decryption password cancel it, and if it asks to allow system modifications swipe to allow it
Go to the Install section and navigate to external_sd and navigate to the arter-r12.zip you installed, then click it and swipe to flash, after that flash the f2fs zip and after it's complete back out to the main menu, click reboot and select recovery
Once you are back in recovery, go to Wipe and select Format Data (this will not erase your sd card if it is set as external storage) and type yes
If you don't want to root then to reboot to system go into Reboot and select System, TWRP will ask you if you want to install their special app, DO NOT INSTALL IT, CLICK ON DO NOT INSTALL.
Now you are ready to proceed to the next step(s) (these are short now don't worry)
To just root and stay on the stock ROM:
Download magisk 20.1 (works better) from here and move it onto your phone sd card by going to the main TWRP menu, selecting Mount then SD card and you should be able to transfer the file onto the sd card directly from your PC
Then simply flash the magisk 20.1 zip in TWRP as we did before and you can now reboot system (make sure to not install the TWRP app)
Magisk Manager will prompt you to update magisk, DONT do it. You can however install the latest magisk manager update
To install a GSI and Root: (lineageOS is what i have linked here, however this is not the only one you can use, make sure you NEED gapps before flashing it incase they are included anywhere)
Firstly, to have bluetooth working go to Mount and select Vendor, go back, select Advanced then File Manager then navigate to /vendor/overlay/ and delete both BluetoothResCommon.apk and RazerAuraBluetoothRes.apk
Then download the latest arm-64-bvN .img file from here, unzip it on your computer and move the .img file to your phone. If you also want gapps (google apps) download this file and move it onto your SD card as well
Now, head to the TWRP Install section, at the bottom select Install Image, select the downloaded lineageOS (or your own gsi) .img file, in the next screen select System Image and swipe to flash it.
Once it has flashed back out to the main screen and click on Wipe, then select Advanced Wipe, then select System, Repair or change file system, and finally press Resize and swipe to do it, if it fails then re do this step
Then go back into the Install section and flash the opengapps zip file and after that the magisk zip file
Now you can reboot to system (might take a couple minutes) and set up the phone.
If you notice it is running slowly go into settings > Phh treble settings (might have to force close app once for it to appear) > Misc Settings > Force FPS > and select the 120.00001 at the bottom (top numbers are 1080p and bottom numbers are 1440p)
Finally, to pass safetynet:
Head into magisk manager, go to its settings and enable Hide Magisk, then call it Manager and allow it to reinstall itself, after that enable Magisk Hide in the settings aswell (hide your banking apps with this or any game that wont boot due to ROOT)
Then go into the magisk downloads section and search for the ArCore module, install this, reboot and your safetynet will pass on a gsi
This is my first xda post so my formatting may be bad but i hope it can help some people if you have any questions drop a comment and please like the post if it helped you for more people to see it.
Have a good day
Usyless said:
YOUR WARRANTY IS NOW VOID! I am not responsible for anything that could happen, dead sd card, bricked phones, you name it. You chose to install this software and you face the risk of any bugs that may affect you. This is just a warning incase anything goes wrong
A complete guide on how to either just root the razer phone 2 and/or install a gsi with everything working.
The sections are: Basics - Installing TWRP - Rooting - Installing a GSI + Root - Passing safety net to use baking apps, certain games etc.
Basics: (You will have to factory reset if you have not unlocked your bootloader before)
Download this and this file, un zip them both and move them to a known directory such as C:\ADB
Then on your phone, go into developer options and enable OEM/Bootloader unlocking, and after that reboot into the bootloader by holding POWER + VOL DOWN and plug the phone into your pc (I recommend you connect it to a USB 2.0 port)
Then we need to install bootloader drivers onto our phone, so open device manager, click the drop down menu next to Android Device, right click on Android and select Update Driver, then select Browse my computer for driver software, Let me pick from a list of available drivers on my computer, Show all devices, Have disk and navigate to your folder where you extracted the .zips (in my case C:\ADB) and open the usb_driver folder and select android_winusb.inf. In the next menu select Android Bootloader Interface, proceed through the warning and install it.
To unlock the bootloader open a cmd window in the directory of your platform-tools folder, which in my case would be C:\ADB\platform-tools (type cd C:\ADB\platform-tools in cmd) and run two commands: fastboot flashing unlock (after each one select yes on your phone and let it reboot - it might take a while) and fastboot flashing unlock_critical
To install the arter97 kernel/TWRP: (keep your phone in the Bootloader and plugged into the pc)
Download both the .zip and .img file from this link (i am using r12 intentionally as it causes less issues) and download this zip file as well
Move both .zip files onto your phones SD CARD (important) and rename the .img file on your PC to Boot.img and place it into your platform-tools folder (C:\ADB\platform-tools in my case)
Open a command prompt window and like before change the directory to the platform-tools folder, then run two commands: fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
Now using the volume keys select the Recovery Mode option in the bootloader and press the power key to select it, if it asks for a decryption password cancel it, and if it asks to allow system modifications swipe to allow it
Go to the Install section and navigate to external_sd and navigate to the arter-r12.zip you installed, then click it and swipe to flash, after that flash the f2fs zip and after it's complete back out to the main menu, click reboot and select recovery
Once you are back in recovery, go to Wipe and select Format Data (this will not erase your sd card if it is set as external storage) and type yes
If you don't want to root then to reboot to system go into Reboot and select System, TWRP will ask you if you want to install their special app, DO NOT INSTALL IT, CLICK ON DO NOT INSTALL.
Now you are ready to proceed to the next step(s) (these are short now don't worry)
To just root and stay on the stock ROM:
Download magisk 20.1 (works better) from here and move it onto your phone sd card by going to the main TWRP menu, selecting Mount then SD card and you should be able to transfer the file onto the sd card directly from your PC
Then simply flash the magisk 20.1 zip in TWRP as we did before and you can now reboot system (make sure to not install the TWRP app)
Magisk Manager will prompt you to update magisk, DONT do it. You can however install the latest magisk manager update
To install a GSI and Root: (lineageOS is what i have linked here, however this is not the only one you can use, make sure you NEED gapps before flashing it incase they are included anywhere)
Firstly, to have bluetooth working go to Mount and select Vendor, go back, select Advanced then File Manager then navigate to /vendor/overlay/ and delete both BluetoothResCommon.apk and RazerAuraBluetoothRes.apk
Then download the latest arm-64-bvN .img file from here, unzip it on your computer and move the .img file to your phone. If you also want gapps (google apps) download this file and move it onto your SD card as well
Now, head to the TWRP Install section, at the bottom select Install Image, select the downloaded lineageOS (or your own gsi) .img file, in the next screen select System Image and swipe to flash it.
Once it has flashed back out to the main screen and click on Wipe, then select Advanced Wipe, then select System, Repair or change file system, and finally press Resize and swipe to do it, if it fails then re do this step
Then go back into the Install section and flash the opengapps zip file and after that the magisk zip file
Now you can reboot to system (might take a couple minutes) and set up the phone.
If you notice it is running slowly go into settings > Phh treble settings (might have to force close app once for it to appear) > Misc Settings > Force FPS > and select the 120.00001 at the bottom (top numbers are 1080p and bottom numbers are 1440p)
Finally, to pass safetynet:
Head into magisk manager, go to its settings and enable Hide Magisk, then call it Manager and allow it to reinstall itself, after that enable Magisk Hide in the settings aswell (hide your banking apps with this or any game that wont boot due to ROOT)
Then go into the magisk downloads section and search for the ArCore module, install this, reboot and your safetynet will pass on a gsi
This is my first xda post so my formatting may be bad but i hope it can help some people if you have any questions drop a comment and please like the post if it helped you for more people to see it.
Have a good day
Click to expand...
Click to collapse
Thank you excellent post just what I needed.
eedwin101 said:
Thank you excellent post just what I needed.
Click to expand...
Click to collapse
I'm glad it helped you
Usyless said:
I'm glad it helped you
Click to expand...
Click to collapse
If you don't mind what other GSI ROMs have you tried that worked well with this phone I am particularly interested in the Google pixel Android 11. Thanks again you have extended the life of this phone for me.
eedwin101 said:
If you don't mind what other GSI ROMs have you tried that worked well with this phone I am particularly interested in the Google pixel Android 11. Thanks again you have extended the life of this phone for me.
Click to expand...
Click to collapse
I know that phhussons AOSP works on this phone with no issues aswell, you might have to use securize to get safety net to pass tho.
android 11 will boot on this phone however iirc you won't be able to hear and other people won't hear you in phone calls.
havoc gsis I believe works but I haven't tested it and I have only heard of one person using it.
BLISS/LOSQ/CAOS don't work on this phone at all.
and after that I don't think there really is many more GSIs that work as they just won't boot for bizarre reasons
How about text messaging. Currently i have not been able to get SMS to work with any GSI on Android 10. Are you able to send and receive text messages? Did you have to do anything to get it working? If so, let me know because i have been having a heck of a time with it.
_Sherrif said:
How about text messaging. Currently i have not been able to get SMS to work with any GSI on Android 10. Are you able to send and receive text messages? Did you have to do anything to get it working? If so, let me know because i have been having a heck of a time with it.
Click to expand...
Click to collapse
oh this issue... are you on T-Mobile by any chance as if you are there is no fix yet and you will have to wait for official lineageOS.
I am on three (UK) and everything works perfectly.
Usyless said:
oh this issue... are you on T-Mobile by any chance as if you are there is no fix yet and you will have to wait for official lineageOS.
I am on three (UK) and everything works perfectly.
Click to expand...
Click to collapse
No AT&T.
_Sherrif said:
No AT&T.
Click to expand...
Click to collapse
you might be able to use this fix (it's a magisk module) as it is made for AT&T https://t.me/razer_phone/14202
its called a volte fix but it should help with sms, if it doesn't work you can just remove the module, reboot then delete some qualcomm.ims app (should be shown in your app list)
_Sherrif said:
No AT&T.
Click to expand...
Click to collapse
or you could try this: https://t.me/razer_phone/12949
install instructions shown in the message
Usyless said:
you might be able to use this fix (it's a magisk module) as it is made for AT&T https://t.me/razer_phone/14202
its called a volte fix but it should help with sms, if it doesn't work you can just remove the module, reboot then delete some qualcomm.ims app (should be shown in your app list)
Click to expand...
Click to collapse
Aight! Definitely worth a try. Tried everything else.
Thank you!
Thanks!! Excellente guide, very important your note : "I recommend you connect it to a USB 2.0 port", with usb 3 doesn't work bootloader commands.
frannet said:
Thanks!! Excellente guide, very important your note : "I recommend you connect it to a USB 2.0 port", with usb 3 doesn't work bootloader commands.
Click to expand...
Click to collapse
Thanks
It doesn't necessarily not work with usb 3.0, for some people (and for me) it works with a usb 3.0 port however for a lot of people they have issues with it.
I will add it tho.
Usyless said:
Thanks
It doesn't necessarily not work with usb 3.0, for some people (and for me) it works with a usb 3.0 port however for a lot of people they have issues with it.
I will add it tho.
Click to expand...
Click to collapse
It's strange. With my razer blade it has not worked (usb 3) but with a Dell Precision with a one port usb 2, work fine. I was going crazy.
frannet said:
It's strange. With my razer blade it has not worked (usb 3) but with a Dell Precision with a one port usb 2, work fine. I was going crazy.
Click to expand...
Click to collapse
Yeah I remember I helped somebody else root their phone and it didn't work with their razer blade either, they had to use some very old laptop.
Usyless said:
Yeah I remember I helped somebody else root their phone and it didn't work with their razer blade either, they had to use some very old laptop.
Click to expand...
Click to collapse
Guys, sorry for the off-topic, is available the dark mode for razer menu? i can't find it
frannet said:
Guys, sorry for the off-topic, is available the dark mode for razer menu? i can't find it
Click to expand...
Click to collapse
What do you mean razer menu? if you mean settings then it's a MAYBE.
on a gsi, dark mode is available
on stock android 9 it is possible. you need to use smali patcher to enable signature spoofing and then use swift theme installer alpha (substratum themes won't theme the settings)(you need to contact the developer to get the alpha version as others wont work)
Usyless said:
What do you mean razer menu? if you mean settings then it's a MAYBE.
on a gsi, dark mode is available
on stock android 9 it is possible. you need to use smali patcher to enable signature spoofing and then use swift theme installer alpha (substratum themes won't theme the settings)(you need to contact the developer to get the alpha version as others wont work)
Click to expand...
Click to collapse
Yeah I talk about the settings menu. I thought dark mode was available for all android versions ??
frannet said:
Yeah I talk about the settings menu. I thought dark mode was available for all android versions ?
Click to expand...
Click to collapse
yeah tbh idek, all the android fanboys were saying at how long it took apple to make a dark mode but it was implemented in android 10 later than ios 12 I swear ?
but as you are rooted you should be able to get a dark mode, just do as I said with smali patcher and the swift installer alpha
i
Usyless said:
yeah tbh idek, all the android fanboys were saying at how long it took apple to make a dark mode but it was implemented in android 10 later than ios 12 I swear ?
but as you are rooted you should be able to get a dark mode, just do as I said with smali patcher and the swift installer alpha
Click to expand...
Click to collapse
Hahaha, yeah, If I'm honest, dark mode in iOS work fine, very fine, normally I use my iPhone 11 and I play with android devices for.. for play with the OS and develoment OS, and as second andriods phone for maybe.... I go to check the gsi mode, thanks guy!!

Categories

Resources