Related
in the subsequent posts below, you will find all the info you need for not only the device but the ROMs I have had my hands in.
each person who I pulled the files from will get a thanks in the posts as necessary
NonSense 1.04
Disclamer: these files are meant specifically for the HTC Desire 510. Use these files at your peril, you assume any responsibility for loss or damage that may result from use of these files or procedures. what has been included in this tutorial is for the HTC Desire 510
You have been warned.
note: from now on CRI signifies cricket, and B-S signifies sprint/boost if those signifiers aren't used, it applies to both type of this phone
now to the goodies.....
List of supplies:
1. Phone (HTC Desire 510)
2. USB cord that syncs with the PC
3. USB drivers installed for the phone
4. the zip files from this location. click here
4.1 there are 2 different versions of the same ROM, but the *1.04-lean.zip is US only (refer to changes to see why).
4.2 CRI for cricket/att, B-S for boost/sprint
5. read these instructions completely before attempting
before we get started make sure you have supersu (which can be downloaded from here), and NonSense1.04.zip copied to the root of your external SD card
NETWORK UNLOCK (I.E. switching services)
as this phone is LTE compatible, it takes a SIM card no matter the service to receive calls and data. so it stands to presume all you need to do is network unlock the device (Sprint calls it UICC unlock, others it's the Network Unlock Code)
the phone needs to be network (SIM) unlocked in order to switch it from cricket to sprint, or from sprint to virgin mobile, etc.
to network unlock the phone:
1. make sure you are on stock ROM (the one that came with the phone, not the one listed in this post nor CM)
2. call the respective original service provider of the phone (i.e. cricket, sprint, etc.) and tell them that you are leaving the country (like to Australia) and you want to unlock the SIM so you can use your device for service down there.
2.1 if you bought the phone second-hand or don't have service on it, you will have to find a reputable unlock service online
2.2 for sprint customers, your account HAS to be at least 6 months old before they will give you the UICC(SIM unlock) code
2.3 for boost customers, your account HAS to be at least a year before they will give you the UICC(SIM unlock) code
3. once you have the SIM unlock code, pull battery from phone, remove the original SIM, put your services respective SIM in (i.e. originally a cricket phone now running a T-Mobile SIM), put in battery, boot phone, and enter the unlock code where it asks.
4. once your back into device, you'll notice you will have no data.
4.1 what needs to be done is to program the APN (google will be your best friend here - for example sprint lte apn settings, or T-Mobile lte apn settings).
5. now that you have the APN settings, you can program them into the phone.
5.1 APNs can be found in the device by going to settings, then mobile data, clicking on access point names. in there in the upper right hand corner should be 3 dots that are verticle. click on that and then on new APN.
5.2 add the respective settings, click save and then make sure it has a green dot next to it.
6. sit back and enjoy the fruits of your labor
APNs for this device can only be written once the phone has been UNLOCKED and the original (cricket) service providers SIM is NOT inserted, and your using another service Provider ( sprint, T-Mobile, etc.) SIM.
UNLOCKING BOOTLOADER
1. for the drivers, use the ones contained here in the HTCDrivers.zip and extract them to the desktop
1. extract and use the file contained in adb.zip to flash unlock token
2. follow this tutorial and choose all other supported devicess when it asks about device.
INSTALLING TWRP AND KERNEL
in the adb file you should notice a file called recovery.img. that is TWRP recovery for the device
there is also a file called boot.img. this will allow read/write permissions at the System level once root is obtained
if you have either the sprint, boost or another service provider's variety of this phone, try flashing their respective kernel after you install the ROM or before you root (no guarantees that flashing the respective kernel will work. as I have the cricket variety of this phone, I am only developing for that one)
1. from home screen, go to settings and scroll down to power and then scroll all the to the bottom of that and uncheck "fast boot"
2. shut down phone completely
3. go back into fastboot (vol down + power)
4. Select fastboot from the menu list and press the power button.
5. open command prompt and use the CD command to get it to the root of the adb folder (CD C:/users/sky/desktop/adb).
6. plug in device and wait for it to say fastboot USB
7. type in command prompt "fastboot flash recovery recovery.img' (should complete within 4 seconds)
8. in the same command window type "fastboot flash boot boot.img" (should complete within 4 seconds)
8.1 step 8 can be skipped if your just flashing *NonSense1.04*.zip
9. pull battery once that is completed and put it back in.
10. power device on (skip this step if rooting)
OBTAINING ROOT (can be skipped if installing NonSense1.04 as it's already rooted)
1. re-enter fastboot mode and choose recovery. press power to select it
2. once in recovery select install and go to external SD and select the supersu update package.
3. once selected, you should see a slider on the bottom of the screen that says swipe to confirm. do so
4. once package is installed you should see a button that says reboot device. do so
5. wait for it to fully load
INSTALLING NonSense 1.04
1. re-enter fastboot mode and choose recovery. press power to select it
2. once in recovery select install and go to external SD and select the NonSense1.04.zip.
3. once selected, you should see a slider on the bottom of the screen that says swipe to confirm. do so
3.1 beware, it may take a bit to install. just be patient, it's working.
4. once package is installed you should see a button that says reboot device. do so
5. wait for it to fully load. be forewarned, it may take about 15 minutes to load
CHANGES
CRI versions
1. DEODEXed the ROM
2. added external SD support into the ROM
3. fixed FC on clock app (switched clock/alarm from stock worldclock.apk to AOSP clock)
4. changed bootanimation.zip, boot sound, and stock ringtones and sounds.
5. added more stable kernel to flash file.
6. added Pandora (no-ads vers. 5.5), SpiritUL (FM radio support), Facebook, RootBrowser, Adobe reader, Adobe flash player, and Viper4android (DSP/equalizer)
6.1 all apps that have been listed in 6 can be uninstalled without the need for root
7. root and SU have been added and are up to date in this rom as of 11:45PM MST on 3/1/215
8. added apns-conf.xml from CyanogenMod
9. got native APP2sd support thanks to pattyboi's kernel
B-S versions
1. mostly DEODEXed the ROM
2. fixed FC on clock app (switched clock/alarm from stock worldclock.apk to AOSP clock)
3. changed bootanimation.zip, boot sound, and stock ringtones and sounds.
4. added more stable kernel to flash file.
5. added Pandora (no-ads vers. 5.5), SpiritUL (FM radio support), Facebook, RootBrowser, Adobe reader, Adobe flash player, Wifi Tether, and Viper4android (DSP/equalizer)
5.1 all apps that have been listed in 5 can be uninstalled without the need for root
6. root and SU has been added
*1.04-lean
list of removed apps
1. Dropbox (can be found in playstore)
2. Google plus (can be found in playstore)
3. Hangouts (can be found in playstore)
4. HTC Dot View(can be found in playstore)
5. keyboard language packs for Arabic, Chinese, English UK, French, German, Greek, Italian, Portuguese, Russian, and Spanish (not in play store) if needed, flash language.zip found here
6. VPN dialogs (not in play store) if needed, flash missing.zip found here
7. HTC Zoe (can be found in playstore)
BUGS
CRI versions
1.USB internet pass-through not working
2.WiFi direct (miracast) not working
3. want to get rid of annoying volume too loud warning
B-S versions
1. native hotspot says internet when connected to win 7 machine, but will not allow it to go through. Have included wifi tether as a workaround until the issue can be resolved
THANKS
CRI versions
I thank wolfaas12345 for his awesome tutorial on bootloader unlocking, pattyboi for providing a more stable kernel, and chainfire for providing a great solution to provide the SU binary and app for rooted devices. and of course, CraviingCritic for providing the original ROM in which this wouldn't be possible
B-S versions
I thank wolfaas12345 for his awesome tutorial on bootloader unlocking, pattyboi for providing the current kernel, and chainfire for providing a great solution to provide the SU binary and app for rooted devices. and of course, LarryBoyG for providing the original ROM in which this wouldn't be possible
please feel free to let me know if there's any issues with this release and i will fix them as they are found for now as this device is the one i primarily use as of right now.
I will also be keeping the links updated for as long as I own the device (being that my HTC Desire 510(Cricket) is network unlocked, that may be a long time - or until I get a better device).
UPDATES
for those of you who have downloaded the ROM since first release, I will include an CRI_NSupdate.zip or B-S_NSupdate.zip file found here. it will include the changes I have made to the rom since it's initial upload.
the file by the name of NSupdate.szip will include update that pertain to both the CRI and B-S ROMS
to install the updates, just put the update file onto the root of the SD card, reboot into recovery, choose install, pick the update file, swipe the blue button on the bottom, reboot and enjoy.
EDITING THE BOOTUP
location of files mentioned is in /system/customize/resource
to change boot animation
1. find your favorite boot animation
2. rename it to AIO_bootup.zip
3. copy/move and overwrite the original with a root explorer to /system/customize/resource
to change the boot sound
1. find a sound file you like and want to hear every time the phone boots (can be changed at any time)
2. convert it to wav (the file has to be wav in order for the phone to recognize it)
3. rename it to CRICKET_LOGO_24bit28k_STEREO.wav
4. copy/move and overwrite the original with a root explorer to /system/customize/resource
reboot and enjoy...
THINGS NOTICED WHILE CREATING ROMs
1. both (cricket and boost/sprint) phones are exactly the same except for the boost/sprint ones contain a CDMA chipset.
1.1 the only things I had to change from the cricket rom to the boost rom was apns.xml in framework-res, apns-conf.xml, and the preferred network type in build.prop.
2. all kernels work for both (US) versions
3. the same recovery is used on both (US based) devices
so essentially, if we develop for the boost/sprint version of the device, change a few things, it will be ready to roll for the cricket version as well
TO FIX NATIVE TETHER ON B-S VERSIONS
1. Install Script Manager – SManager app from the Play Store.
2. Open the app and grant it root access when prompted.
3. Now, navigate to /system/etc/init.d and tap “tether” script.
4. Click on SU and Boot (Android skull and gear icons, respectively)
5. Click on Run and Save options.
The issue should be fixed now. Reboot and enjoy!
thanks goes to qwerty6532 and LarryBoyG for the fix. now to add that permanently to the ROMs and then they'll be absolutely stable enough for me to be happy and start working on CM11
CM11
I will be building CM11 for the device for both the cricket and boost models. look for the info here as I update it a I need
****edit**** ok so I figured out some of the issue with CM11 not wanting to install apps. I got the internal memory pulling the 1.1 gbs but now I need to symlink the external memory where it goes.
****edit**** so I have figured out what needs to be done...... the kernel for CM11 needs to be built from the ground, up (or one needs to be built that is compatible with it). i'll upload the current one that fixes the memory error (look in downloads).
reserved
so as i have not been actively developing on the phone i will no longer supply updates. all flash files are up to date as of 8 months ago and should be working with out an issue.
again, reserved
same to you...
This would have to be one of the most comprehensive tutorials I have read. 10 out of 10 and kudos. Pity I have a 64 bit device and can't use most of it lol.
Burtrum57 said:
This would have to be one of the most comprehensive tutorials I have read. 10 out of 10 and kudos. Pity I have a 64 bit device and can't use most of it lol.
Click to expand...
Click to collapse
if I had a 64-bit version for this device, I would have it out as soon as I could. and thanks
Great job. Off and running now
I'm not sure how to add the tether fix to the ROM. Not really a developer more of a tester.. Wish I could get into developing don't really know where to start lol.
If you need any help testing or working on CM11 for Boost shoot me a PM I'd be glad to help
Sent from my 0PCV1 using XDA Free mobile app
Question to you Schizoidd......If I install the new 1.04lean over the previous build, do I still need to flash that update or is is already included in 1.04lean. I already falshed that some time ago when you first put it out, so I'm just not sure if its needed again or not. Thanks bro.
CSP III said:
Question to you Schizoidd......If I install the new 1.04lean over the previous build, do I still need to flash that update or is is already included in 1.04lean. I already falshed that some time ago when you first put it out, so I'm just not sure if its needed again or not. Thanks bro.
Click to expand...
Click to collapse
When you flash the new one, wipe the system partition and then use an explorer to remove v4a from the user apps. Which is located in /data/apps and reboot
qwerty6532 said:
I'm not sure how to add the tether fix to the ROM. Not really a developer more of a tester.. Wish I could get into developing don't really know where to start lol.
If you need any help testing or working on CM11 for Boost shoot me a PM I'd be glad to help
Sent from my 0PCV1 using XDA Free mobile app
Click to expand...
Click to collapse
Well it's added to it. It just needs to be activated for now until I can figure out how to add it to automatically start from the first run of the Sprint/boost ROM
schizoidd said:
When you flash the new one, wipe the system partition and then use an explorer to remove v4a from the user apps. Which is located in /data/apps and reboot
Click to expand...
Click to collapse
Sorry, not following "wipe the system partition" ???
CSP III said:
Sorry, not following "wipe the system partition" ???
Click to expand...
Click to collapse
if you in recovery, go to wipe and then advance wipe and check system. wipe it like u would as if ur doing a factory reset
schizoidd said:
if you in recovery, go to wipe and then advance wipe and check system. wipe it like u would as if ur doing a factory reset
Click to expand...
Click to collapse
Yeah, I figured as much. Should have been clearer with my ? Is that before or after I flash the new lean. I though if I did it after, that it would set me back to square one. As in having to start fresh setting everything up again, which I really dont want to have to do. Apologies for my unclearness.
CSP III said:
Yeah, I figured as much. Should have been clearer with my ? Is that before or after I flash the new lean. I though if I did it after, that it would set me back to square one. As in having to start fresh setting everything up again, which I really dont want to have to do. Apologies for my unclearness.
Click to expand...
Click to collapse
it'll leave ur data alone, just delete the OS. do not touch internal memory, davlik, data, or cache and ur stuff will be safe. I have done it and my stuff is fine
schizoidd said:
it'll leave ur data alone, just delete the OS. do not touch internal memory, davlik, data, or cache and ur stuff will be safe. I have done it and my stuff is fine
Click to expand...
Click to collapse
Right on buddy. I'll take you at your word on it. I've never had to do that before so it naturally made me a little nervous. Not that I couldnt have just restored a backup, but still . Many thanks.
Problems
System UI force closes and power button doesn't turn the screen back on when I flash the latest cricket version.
schizoidd said:
I
for those of you that build the kernels, do you think u can build one that is AOSP and compatible with the device for android 4.4.4?
Click to expand...
Click to collapse
we cant really do a "aosp" kernel because of htc's modifications to the board and pins,and they have their own dtb issues...im 99% sure mine works with android 4.4.x because of larry using it in gpe,just repack the ramdisk the zimage and it should be okay
Bobby060 said:
System UI force closes and power button doesn't turn the screen back on when I flash the latest cricket version.
Click to expand...
Click to collapse
If you're going from bone stock to this, you need to do a factory data reset. Just make ssure you back up your data and use nandroid manager to pull it data back into the new ROM
FIRST OF ALL
This isn't my work all credits goes to nexmon team for patched firmware and libs Github
And for @chrisk44 for Hijacker App Github, XDA
Tested on Galaxy s6 MM and should work on every android device with BCM4358.
Requirement:
-BCM4358
-Root SuperSU
-BusyBox
Downloads:
-Download Hijacker App From Here.
-Download Patched Firmware From Here (there's two files, .patched and .original in case you didn't backup yours) or you can go to nexmon git and get the file from there.
Installation:
-Rename the firmware from "bcmdhd_sta.bin.patched" to "bcmdhd_sta.bin"
-Copy the renamed file to "/system/etc/wifi" (Backup the original first) set permission to 644 (rw,r,r)
-Create empty file in "/vendor/firmware/" and name it "fw_bcmdhd.bin"
-Open Hijacker app follow the installation instruction (if you got an error "Your device is not supported ... bcm4339 ... bla bla bla." Long click the install button)
-REBOOT
Everything should be working fine now, open Hijacker app and test it.
[Disconnect from all the network or turn your wifi off for Hijacker app to work]
Bugs:
-Your WiFi will sometimes restart itself (Phone restart will fix this)
-Others? I don't know you tell me.
Working/Not Working:
-See Nexmon and Hijacker Git Repo.
Thank them for the work then thank me if you find this is useful, thank you.
Screenshots:
Hijacker includes a patched firmware for the BCM4339. Overriding the check and installing it on a different chipset can be dangerous. I only implemented the override in case you are on BCM4339 but the detection doesn't work.
chrisk44 said:
Hijacker includes a patched firmware for the BCM4339. Overriding the check and installing it on a different chipset can be dangerous. I only implemented the override in case you are on BCM4339 but the detection doesn't work.
Click to expand...
Click to collapse
Hijacker check the firmware in /vendor/firmware but samsung wireless firmware is in /system/etc/wifi so the hijacker app wont override anything except the empty file created in /vendor/firmware.
Edit: I will remove your app from my post if you want.
What happens when you click "find firmware" when installing nexmon?
Keep in mind that "nexmon" is not a firmware... it's a project which creates firmwares for some chipsets. You shouldn't use a firmware that is intended for an other chipset.
chrisk44 said:
What happens when you click "find firmware" when installing nexmon?
Keep in mind that "nexmon" is not a firmware... it's a project which creates firmwares for some chipsets. You shouldn't use a firmware that is intended for an other chipset.
Click to expand...
Click to collapse
I know that nexmon is a project, and the firmware installation is happening manually not by nexmon app.
Ok let me start again. The project "nexmon" has released patched firmwares to support monitor mode for various chipsets, including BCM4339 and BCM4358. Hijacker includes only the firmware for BCM4339 because I don't have a device with 4358 and I can't include the other firmware without testing it. Hijacker includes the firmware for BCM4339 and installs it wherever the firmware is. The fact that your firmware is located in /system/etc/wifi is not because of chipset or samsung, it's because of android 6 and the app defaults for android 7. Clicking "find firmware" will find it and clicking instalm will install it ONLY if it is for BCM4339. Overriding this will result in the firmware for 4339 being installed on a device with 4358. Do you see the problem here? There shouldn't be reboots or wifi restarts with these firmwares, they are actually very well written.
You can use the app if you want but you will have to install the firmware manaully, which means:
Download the firmware as a binary file,
copy the old firmware somewhere for backup,
copy the new file over the old one in system,
restart wifi to load the new firmware,
install the nexutil program (binary file) in /su/xbin or /su/bin or /system/bin (not recommended) to manage monitor mode
and you're done. Hijacker should work immediately.
chrisk44 said:
Ok let me start again. The project "nexmon" has released patched firmwares to support monitor mode for various chipsets, including BCM4339 and BCM4358. Hijacker includes only the firmware for BCM4339 because I don't have a device with 4358 and I can't include the other firmware without testing it. Hijacker includes the firmware for BCM4339 and installs it wherever the firmware is. The fact that your firmware is located in /system/etc/wifi is not because of chipset or samsung, it's because of android 6 and the app defaults for android 7. Clicking "find firmware" will find it and clicking instalm will install it ONLY if it is for BCM4339. Overriding this will result in the firmware for 4339 being installed on a device with 4358. Do you see the problem here? There shouldn't be reboots or wifi restarts with these firmwares, they are actually very well written.
You can use the app if you want but you will have to install the firmware manaully, which means:
Download the firmware as a binary file,
copy the old firmware somewhere for backup,
copy the new file over the old one in system,
restart wifi to load the new firmware,
install the nexutil program (binary file) in /su/xbin or /su/bin or /system/bin (not recommended) to manage monitor mode
and you're done. Hijacker should work immediately.
Click to expand...
Click to collapse
Okay, this is what written above. Since its working, I decided to share it with galaxy s6 owners... that's it. I don't know why are you repeating and telling me what your app does, I fully understand this plus i didn't say that "oh man! this is my work" and I told you I know what nexmon is and what it does, if you dont want your app to be here in my thread I will remove it.
I didn't say anything like that, plus my app is already here. I'm just pointing out that you are suggesting to galaxy s6 owners to use a firmware that is not intended for their device. Especially when there IS a correct firmware out there. I'm really not obligated to way in here, I'm just trying to prevent damages.
---------- Post added at 18:59 ---------- Previous post was at 18:04 ----------
Anyway, I'll include it in the next release and hope for the best...
chrisk44 said:
I didn't say anything like that, plus my app is already here. I'm just pointing out that you are suggesting to galaxy s6 owners to use a firmware that is not intended for their device. Especially when there IS a correct firmware out there. I'm really not obligated to way in here, I'm just trying to prevent damages.
---------- Post added at 18:59 ---------- Previous post was at 18:04 ----------
Anyway, I'll include it in the next release and hope for the best...
Click to expand...
Click to collapse
Okay that's kind.
Wait a second, do you have frame injection using the 4339 firmware? Do aireplay, mdk and reaver work?
chrisk44 said:
Wait a second, do you have frame injection using the 4339 firmware? Do aireplay, mdk and reaver work?
Click to expand...
Click to collapse
As it says in nexmon git page, no.
Hi guys, is there still wip regarding injection mode?
is there. any chance of nexmon working galaxy note 4 or 3
Quick question. I had come across the Nexmon app before finding Hijacker. My question is sorta this, I'm assuming then that Nexmon doesn't have to be installed to make Hijacker work? Because Hijacker is hit or miss for me. Sometimes it works and sometimes it doesn't.
Chuck
Boahen said:
is there. any chance of nexmon working galaxy note 4 or 3
Click to expand...
Click to collapse
It works on Note 3 AOSP rom, same wifi chipset as nexus 5
digitalchaos1980 said:
Quick question. I had come across the Nexmon app before finding Hijacker. My question is sorta this, I'm assuming then that Nexmon doesn't have to be installed to make Hijacker work? Because Hijacker is hit or miss for me. Sometimes it works and sometimes it doesn't.
Chuck
Click to expand...
Click to collapse
You can manually run binary files from any terminal, by executing LD_PRELOAD=/path of libfakeioctl.so
Then execute nexutil -m2 to turn on monitor mode, you're ready to go now.
Sent from my SM-G950F using Tapatalk
daoudedy said:
It works on Note 3 AOSP rom, same wifi chipset as nexus 6
You can manually run binary files from any terminal, by executing LD_PRELOAD=/path of libfakeioctl.so
Then execute nexutil -m2 to turn on monitor mode, you're ready to go now.
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
OK thanks, that actually helps me. I had stumbled upon this whole setup when I came across the Nexmon app in the Play Store. I've been wanting a device that has a chip that can support monitor mode for a long time so naturally when I saw the app I was excited. I had installed it but didn't quite know exactly how to use the "firmware" part of the app to install the firmware. Did a Google search and came across your post and installed Hijacker and followed the post to a T. But it would only work when it wants to. I have another spare S6 that I just installed Hijacker to and followed the instructions for that as well. Both phones are hit or miss really but I notice that if I open Nexmon and start monitor mode there first then open Hijacker then it works but when I go to "crack" it looks like it's doing something but I'm under the impression I should see some sort of progress being displayed on the bottom half of the app. Is this correct? I am a power user and know my way around the file system well but don't have a whole lot of experience with this type of thing. And just as a disclaimer, I am using this on my own router and Moderators if I have said anything crossing a line PLEASE let me know and I will edit my content! I don't want to violate any rules talking about these apps the wrong way. Thank you
Chuck
digitalchaos1980 said:
OK thanks, that actually helps me. I had stumbled upon this whole setup when I came across the Nexmon app in the Play Store. I've been wanting a device that has a chip that can support monitor mode for a long time so naturally when I saw the app I was excited. I had installed it but didn't quite know exactly how to use the "firmware" part of the app to install the firmware. Did a Google search and came across your post and installed Hijacker and followed the post to a T. But it would only work when it wants to. I have another spare S6 that I just installed Hijacker to and followed the instructions for that as well. Both phones are hit or miss really but I notice that if I open Nexmon and start monitor mode there first then open Hijacker then it works but when I go to "crack" it looks like it's doing something but I'm under the impression I should see some sort of progress being displayed on the bottom half of the app. Is this correct? I am a power user and know my way around the file system well but don't have a whole lot of experience with this type of thing. And just as a disclaimer, I am using this on my own router and Moderators if I have said anything crossing a line PLEASE let me know and I will edit my content! I don't want to violate any rules talking about these apps the wrong way. Thank you
Chuck
Click to expand...
Click to collapse
Go to nexmon git page and read the instructions, s6 has a bcm4358
Sent from my SM-G950F using Tapatalk
daoudedy said:
Go to nexmon git page and read the instructions, s6 has a bcm4358
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
Thank you, I will check that out. I do know what chip it has, I just hadn't found a page about Nexmon. I will find that page and read, read, read lol. Thank you
Chuck
digitalchaos1980 said:
Thank you, I will check that out. I do know what chip it has, I just hadn't found a page about Nexmon. I will find that page and read, read, read lol. Thank you
Chuck
Click to expand...
Click to collapse
https://github.com/seemoo-lab/nexmon
Sent from my SM-G950F using Tapatalk
Hello, i had read many things at the forum but i still very confused. .please in a simple answer, which one is the correct and the download link. .please i can damage my cel.
Hgt45 said:
Hello, i had read many things at the forum but i still very confused. .please in a simple answer, which one is the correct and the download link. .please i can damage my cel.
Click to expand...
Click to collapse
Hello,
first i am not sure that u are in the right forum section.
About your demand, you haven't mention the CPU arch of your phone and have you reboot in custom recovery to flash the downloaded zip ?
Rom said:
Hello,
first i am not sure that u are in the right forum section.
About your demand, you haven't mention the CPU arch of your phone and have you reboot in custom recovery to flash the downloaded zip ?
Click to expand...
Click to collapse
Hello Lyon, hope everything happy... well, i don't know if its the right fórum,, here the info:
SYSTEM: SDK versión 6.0.1 ID:MMB29M OS name: Linux OS versión:3.10.40-9120850 Dalvik VM versión: 2.1.0
DEVICE: Model: SM-N910P Product: trltespr Board:APQ8084 Brand: Samsung Fingerprint: Samsung/trltespr/trltespr:6.0.1/MMB29M/N910PVPS4DQD1:user/reléase-keys
CPU: Name: ? Current freq.: 1958.4MHz Max freq.: 2649.6MHz Min freq.: 300MHz Cores: 4
Architecture: 7 BogoMIPS:38.40 Hardware: Qualcomm APQ8084 Revisión: 1
Serial #:0000000000000000
Memory
Total:2845492kbB Free:97792kB Inactive:896648kB
I haven't reboot in custom recovery to flash the downloaded zip XposedInstaller_by_dvdandroid.apk because of the warning its shows ( i send the pictures ).. i don't want to damage my note 4.. its the righ one ?
If you or anyone can help me to easy way to do it..
1- is,, XposedInstaller_by_dvdandroid.apk ? safe to run in custon recovery ? i Yes, how to, if No, which one to download it.
Regards.
H.
Hgt45 said:
Hello Lyon, hope everything happy... well, i don't know if its the right fórum,, here the info:
SYSTEM: SDK versión 6.0.1 ID:MMB29M OS name: Linux OS versión:3.10.40-9120850 Dalvik VM versión: 2.1.0
DEVICE: Model: SM-N910P Product: trltespr Board:APQ8084 Brand: Samsung Fingerprint: Samsung/trltespr/trltespr:6.0.1/MMB29M/N910PVPS4DQD1:user/reléase-keys
CPU: Name: ? Current freq.: 1958.4MHz Max freq.: 2649.6MHz Min freq.: 300MHz Cores: 4
Architecture: 7 BogoMIPS:38.40 Hardware: Qualcomm APQ8084 Revisión: 1
Serial #:0000000000000000
Memory
Total:2845492kbB Free:97792kB Inactive:896648kB
I haven't reboot in custom recovery to flash the downloaded zip XposedInstaller_by_dvdandroid.apk because of the warning its shows ( i send the pictures ).. i don't want to damage my note 4.. its the righ one ?
If you or anyone can help me to easy way to do it..
1- is,, XposedInstaller_by_dvdandroid.apk ? safe to run in custon recovery ? i Yes, how to, if No, which one to download it.
Regards.
H.
Click to expand...
Click to collapse
I don't see your CPU arch in your details, you are in the wrong forum section and on Android 5.0+ you must flash your zip in custom recovery.
Rom said:
I don't see your CPU arch in your details, you are in the wrong forum section and on Android 5.0+ you must flash your zip in custom recovery.
Click to expand...
Click to collapse
Thank you ROM,,for answer me, sorry I'm not an experienced tech... . and I'm afraid to flash zip in custom recovery mode if is not the right one,, in other words, I haven't did before, I just install framework in my S4 with no problems before. ..
I find out CPU arch: ARMv7-A Qualcomm APQ8084 ,,etc,, see attachment.
Please could you please tell me and help me ?....
If someone move these Thread to the right place. .
Sorry if I'm bothering
Regards
H.
Hgt45 said:
Thank you ROM,,for answer me, sorry I'm not an experienced tech... . and I'm afraid to flash zip in custom recovery mode if is not the right one,, in other words, I haven't did before, I just install framework in my S4 with no problems before. ..
I find out CPU arch: ARMv7-A Qualcomm APQ8084 ,,etc,, see attachment.
Please could you please tell me and help me ?....
If someone move these Thread to the right place. .
Sorry if I'm bothering
Regards
H.
Click to expand...
Click to collapse
Hello,
Apparently your CPU is an arm32 bits processor, so dl the last zip from this page:
http://dl-xda.xposed.info/framework/sdk23/arm/
And flash it via custom recovery.
After flash the zip, reboot in classic mode and check again by opening XPosed Installer app.
Rom said:
Hello,
Apparently your CPU is an arm32 bits processor, so dl the last zip from this page:
http://dl-xda.xposed.info/framework/sdk23/arm/
And flash it via custom recovery.
After flash the zip, reboot in classic mode and check again by opening XPosed Installer app.
Click to expand...
Click to collapse
Hello Rom, wishing your are very happy...
look the picture and see what is happening..
Overall Status: Congratulations! This device has root access!
Feedback
Stage 1 - Superuser App: Installed
Installed: SuperSU by Chainfire - version 2.82
Stage 2 - Superuser Binary Files: Installed
Standard System-less Location
Command: ls -l /su/bin/su
Result: -rwxr-xr-x root root 75352 2017-09-22 16:39 su
Version: 2.82:SUPERSU
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard System Location
Command: ls -l /system/bin/su
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard System Location
Command: ls -l /system/xbin/su
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Command: ls -l /sbin/su
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/sbin/su
Result: /system/sbin/su: No such file or directory
Analysis: File /system/sbin/su does not exist.
Alternative Location
Command: ls -l /system/xbin/sudo
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Command: ls -l /magisk/.core/bin/su
Result: /magisk/.core/bin/su: No such file or directory
Analysis: File /magisk/.core/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /vendor/bin/su
Result: /vendor/bin/su: No such file or directory
Analysis: File /vendor/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /su/xbin/su
Result: /su/xbin/su: No such file or directory
Analysis: File /su/xbin/su does not exist.
Stage 3 - Root User Account: Success
Root user id: uid=0(root)
Root group id: gid=0(root) groups=0(root)
Root SELinux context: context=u:r:init:s0
Optional - ADB Shell User
Status: Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional - Google SafetyNet Status
SafetyNet Status: False
Google evaluates hardware and software against Android specifications
Additional - System Environment PATH
System Environment PATH: /su/bin /sbin /vendor/bin /system/sbin /system/bin /su/xbin /system/xbin
Results provided for your SM-N910P - Android 6.0.1 device by Root Checker Pro version 6.1.5 from joeykrim in Google Play - http://goo.gl/NcnHn
thanks..
h.
Hgt45 said:
Hello Rom, wishing your are very happy...
look the picture and see what is happening..
Overall Status: Congratulations! This device has root access!
Feedback
Stage 1 - Superuser App: Installed
Installed: SuperSU by Chainfire - version 2.82
Stage 2 - Superuser Binary Files: Installed
Standard System-less Location
Command: ls -l /su/bin/su
Result: -rwxr-xr-x root root 75352 2017-09-22 16:39 su
Version: 2.82:SUPERSU
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard System Location
Command: ls -l /system/bin/su
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard System Location
Command: ls -l /system/xbin/su
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Command: ls -l /sbin/su
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/sbin/su
Result: /system/sbin/su: No such file or directory
Analysis: File /system/sbin/su does not exist.
Alternative Location
Command: ls -l /system/xbin/sudo
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Command: ls -l /magisk/.core/bin/su
Result: /magisk/.core/bin/su: No such file or directory
Analysis: File /magisk/.core/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /vendor/bin/su
Result: /vendor/bin/su: No such file or directory
Analysis: File /vendor/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /su/xbin/su
Result: /su/xbin/su: No such file or directory
Analysis: File /su/xbin/su does not exist.
Stage 3 - Root User Account: Success
Root user id: uid=0(root)
Root group id: gid=0(root) groups=0(root)
Root SELinux context: context=u:r:init:s0
Optional - ADB Shell User
Status: Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional - Google SafetyNet Status
SafetyNet Status: False
Google evaluates hardware and software against Android specifications
Additional - System Environment PATH
System Environment PATH: /su/bin /sbin /vendor/bin /system/sbin /system/bin /su/xbin /system/xbin
Results provided for your SM-N910P - Android 6.0.1 device by Root Checker Pro version 6.1.5 from joeykrim in Google Play - http://goo.gl/NcnHn
thanks..
h.
Click to expand...
Click to collapse
Hello,, any sugestion. ?
Have a great day.
H.
: (
Sent from my SM-N910P using Xposed Modules
Hgt45 said:
: (
Sent from my SM-N910P using Xposed Modules
Click to expand...
Click to collapse
Read fully, gather resources, install prerequisites on PC and study before proceeding AND only with confidence, considering all risks. Steps are generally in order but start with verifying reactivation lock is not enabled at Settings/Security while phone is booted.
I'd also recommend that you begin with fingerprints removed and no encryption. Make backups frequently in TWRP recovery beginning with suggested stock backup on ext sdcard as explained along the way.
Note: remember, before making any backups that fingerprints should be removed. Fingerprints do not restore from custom backups and don't work as expected even restored in a backup. Problematic!
Steps may contain redundant reminders and links because I've reiterated important things more than once.
Begin here when prerequisites, explained, are installed and gathered. The SuperSU zip and Wanam unofficial Xposed can be downloaded to phone's internal memory or retained for safe keeping on your micro sdcard. Just remember where downloaded to find when flashing in recovery. Always verify md5 of zips before extracting or flashing (as applies) where available. Sanity check to be safe.
USB driver will be installed on PC as executable; Odin will be extracted to Odin folder; your user files are good location to place this folder with extracted files; the exe file is an Odin application launcher executable with dependencies. The TWRP img.tar file will be downloaded to PC to install with Odin as explained along the way.
You can use the 3.1.1 Xposed Installer apk but your Xposed framework is going to be an unofficial one from Wanam for touchwiz lollipop and marshmallow.
Wanam also has an Xposed module suggested for touchwiz marshmallow: XTouchWiz (found with download search in Xposed Installer application when successful in installing all that I've given guidance for) . You might try that one first for SM-N910P; (other likened Xposed modification modules may not be as compatible as this Wanam module-- not too be confused with Wanam unofficial framework zip for recovery flashing to install Xposed framework). Note the differences.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
The file you'll eventually find is Wanam unofficial Xposed framework for SDK 23 arm.
https://www.androidfilehost.com/?fid=529152257862685344
I don't believe you're rooted. It also appears you're trying to flash custom zips with stock recovery? Are you familiar with TWRP recovery by Team Win? You'll need that to backup your ROM and flash custom zips like SuperSU zip and unofficial Xposed framework by Wanam. (Bootloader is already unlocked on SM-N910P; please make sure that is your model number because that's what I'm recommending files for).
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
The file above is latest custom recovery for SM-N910P or any Qualcomm Note 4. Recently, the TWRP recovery became unified by processor but common mistakes users of Qualcomm Note 4 make is not knowing which to flash and what's required for Odin install and how to properly flash in Odin. What's Odin? It's a utility made for flashing custom tar files and stock tar updates for rooted users. There are many updates and untrusted sources (beware of adware or malware!) but basically it's installed on a PC as an executable file. But you'll also need the official USB driver to help the PC discover your phone when placed in download mode to flashed with Odin. What will you flash? The tar.img file above.
To get started download USB driver and Odin. Install USB on PC with its exe file.
http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
Latest Odin trusted download is below. Unzip or extract contents in a folder named Odin
https://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
If you have Samsung Smart Switch or Samsung KIES installed on PC, you need to ensure all process and apps sessions are closed before using Odin. Also note that launching Odin exe on Windows 8 and below requires to launch with administrative permission (right click the executable file and select launch with administrative permission). Windows 10 does not require administrative mode at launch.
Are you familiar with launching download mode? Power Off, pull battery after charging to at least 80% (general rules for flashing in Odin download mode- never use a "boot to download mode" shortcut from system booted state; actually, that necessity applies to flashing full stock tar but remember that; make it a practice is my suggestion to avoid catheter csc errors with full stock tar flashes with Odin-- that's how rooted users update). Reinstall battery and press hold volume down, home and power button until it vibrates or launches. Read the prompt on phone* this is important because flashes are always a risk. Launch Odin on PC and goto options tab and uncheck auto restart and return to to log tab. While watching "COM" field with USB cable connected (must be data USB type cable- original Samsung Note 4 is recommended), follow prompt* I believe it's volume up to continue. Read your phone's state and see that COM field populated with your device (likely a port or device number unique to your PC where phone USB cable is connected or your phone* it only populates when you accept/commit download mode with phone and PC connected via USB with data support). Do not proceed until verifying your phone display shows Odin fast mode and that reactivation lock is disabled or inactive. If that is a go, load the img.tar in AP slot. You still see the file name fill that slot when you navigate to it on your PC and select it. The install button will be at bottom of Odin screen, I believe. Begin when all is verified.
If all above is a go, just remember that you're looking for a green field that fills and says SUCCESS! Happens quickly and stops (if you setup as directed). Wait until you see Odin log file state that "1 passed, 0 failed". Give it a minute to declare "disconnected" or just wait one minute before proceeding. Since auto reboot was unchecked, you'll have to remove USB and pull battery manually (wait at least 30 seconds after pulling battery before reinstalling). And close Odin after each flash session; you're actually done with the PC for this directive. IMPORTANT: If you fail to go directly to recovery mode after reinstalling the battery, stock recovery will restore itself and you'll have to do the Odin flash of TWRP again. To do this, press and hold volume up, home and power simultaneously until it vibrates; TWRP recovery should launch. You're now ready to backup your stock un-rooted ROM. I recommend backing up to ext SD Card (micro sdcard).
To familiar yourself with TWRP install and use, there's a support thread for that. There's also an official TWRP recovery application in Google Play. Search it there. Note the thread hasn't reflected latest update or developer notes since the official TWRP recovery app launched in Google Play but many unique questions are answered there. Ignore any suggestions to use an older TWRP version or any specific update or Android version. Suggestions like this change over time and may not be relevant at present.
https://forum.xda-developers.com/no...ility-twrp-2-8-1-0-teamwin-t2915591?nocache=1
After backup, I'd recommend installing SuperSU zip with TWRP recovery.
https://forum.xda-developers.com/showpost.php?p=68475511&postcount=1
Make a rooted TWRP backup before applying Xposed and label accordingly, saving to ext sdcard. You can edit the generalized title of backup as you prefer. Rather than the extended fine stamp, shorten to include your description.
Then you can install the Xposed Installer apk (install by sideload method not recovery- you may have already done this) and Wanam unofficial Xposed zip. Follow this thread; I've already linked the zip above but usually you're looking for the highlighted download link and browse to marshmallow SDK 23 arm.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
All threads referenced are your support threads for files referenced. Understand before flashing that there risks you assume yourself. Never a guarantee that you'll be successful or the inevitable happens from followed instructions offered by me or anyone else I've linked you to.
Again, make sure you haven't set reactivation lock in phone's Settings/Security tab before beginning and verify the phone display and Odin states before flashing. Not following could result in phone activating a factory reset protection mode. Not sharing to warning while flashing TWRP recovery may only refuse to flash due to reactivation lock enabled and may state such when using recent Odin releases. But that message may be only abbreviated and cause question of its intent.
Only flash when familiar and confident with instructions. Better to ask than risk misunderstood direction. There may recent demo videos to follow but avoid using suggested older files, noting date of your video; they're not necessarily scripture to live by. Best to use recent files and direction because unlike a certain BOOK, updates and time changes with Samsung, touchwiz and Note 4 development.
There's also some custom ROMs to consider if you follow the road map of XDA links for Sprint Note 4 at top of thread: Note 4 development, rather than Note 4 original development where TWRP support thread. Updates for TWRP can be found in the official TWRP recovery app but I've linked you latest recommended release for flashing in Odin.
Questions? Ask away or read the support threads to familiarize yourself. Many questions are answered there.
Sent from my SM-N920P using Tapatalk
---------- Post added at 10:28 PM ---------- Previous post was at 09:59 PM ----------
Final result on my SM-N910P Note 4. See screenshots.
I'm using a couple of non Xposed modules to compliment modification outside of Xposed. Since compatible modules and applications are sometimes limited, I'll include those for clarification. Both linked below by Google Play link. Strictly optional. Both contain back to kill foreground app shortcuts but may be premium only features- I'm not sure on both or whether one or the other would be ideal. I sort of discovered these apps by recommendation and haven't tried eliminating one or the other.
https://play.google.com/store/apps/details?id=flar2.homebutton
https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontrol
Sent from my SM-N920P using Tapatalk
samep said:
Read fully, gather resources, install prerequisites on PC and study before proceeding AND only with confidence, considering all risks. Steps are generally in order but start with verifying reactivation lock is not enabled at Settings/Security while phone is booted.
I'd also recommend that you begin with fingerprints removed and no encryption. Make backups frequently in TWRP recovery beginning with suggested stock backup on ext sdcard as explained along the way.
Note: remember, before making any backups that fingerprints should be removed. Fingerprints do not restore from custom backups and don't work as expected even restored in a backup. Problematic!
Steps may contain redundant reminders and links because I've reiterated important things more than once.
Begin here when prerequisites, explained, are installed and gathered. The SuperSU zip and Wanam unofficial Xposed can be downloaded to phone's internal memory or retained for safe keeping on your micro sdcard. Just remember where downloaded to find when flashing in recovery. Always verify md5 of zips before extracting or flashing (as applies) where available. Sanity check to be safe.
USB driver will be installed on PC as executable; Odin will be extracted to Odin folder; your user files are good location to place this folder with extracted files; the exe file is an Odin application launcher executable with dependencies. The TWRP img.tar file will be downloaded to PC to install with Odin as explained along the way.
You can use the 3.1.1 Xposed Installer apk but your Xposed framework is going to be an unofficial one from Wanam for touchwiz lollipop and marshmallow.
Wanam also has an Xposed module suggested for touchwiz marshmallow: XTouchWiz (found with download search in Xposed Installer application when successful in installing all that I've given guidance for) . You might try that one first for SM-N910P; (other likened Xposed modification modules may not be as compatible as this Wanam module-- not too be confused with Wanam unofficial framework zip for recovery flashing to install Xposed framework). Note the differences.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
The file you'll eventually find is Wanam unofficial Xposed framework for SDK 23 arm.
https://www.androidfilehost.com/?fid=529152257862685344
I don't believe you're rooted. It also appears you're trying to flash custom zips with stock recovery? Are you familiar with TWRP recovery by Team Win? You'll need that to backup your ROM and flash custom zips like SuperSU zip and unofficial Xposed framework by Wanam. (Bootloader is already unlocked on SM-N910P; please make sure that is your model number because that's what I'm recommending files for).
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
The file above is latest custom recovery for SM-N910P or any Qualcomm Note 4. Recently, the TWRP recovery became unified by processor but common mistakes users of Qualcomm Note 4 make is not knowing which to flash and what's required for Odin install and how to properly flash in Odin. What's Odin? It's a utility made for flashing custom tar files and stock tar updates for rooted users. There are many updates and untrusted sources (beware of adware or malware!) but basically it's installed on a PC as an executable file. But you'll also need the official USB driver to help the PC discover your phone when placed in download mode to flashed with Odin. What will you flash? The tar.img file above.
To get started download USB driver and Odin. Install USB on PC with its exe file.
http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
Latest Odin trusted download is below. Unzip or extract contents in a folder named Odin
https://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
If you have Samsung Smart Switch or Samsung KIES installed on PC, you need to ensure all process and apps sessions are closed before using Odin. Also note that launching Odin exe on Windows 8 and below requires to launch with administrative permission (right click the executable file and select launch with administrative permission). Windows 10 does not require administrative mode at launch.
Are you familiar with launching download mode? Power Off, pull battery after charging to at least 80% (general rules for flashing in Odin download mode- never use a "boot to download mode" shortcut from system booted state; actually, that necessity applies to flashing full stock tar but remember that; make it a practice is my suggestion to avoid catheter csc errors with full stock tar flashes with Odin-- that's how rooted users update). Reinstall battery and press hold volume down, home and power button until it vibrates or launches. Read the prompt on phone* this is important because flashes are always a risk. Launch Odin on PC and goto options tab and uncheck auto restart and return to to log tab. While watching "COM" field with USB cable connected (must be data USB type cable- original Samsung Note 4 is recommended), follow prompt* I believe it's volume up to continue. Read your phone's state and see that COM field populated with your device (likely a port or device number unique to your PC where phone USB cable is connected or your phone* it only populates when you accept/commit download mode with phone and PC connected via USB with data support). Do not proceed until verifying your phone display shows Odin fast mode and that reactivation lock is disabled or inactive. If that is a go, load the img.tar in AP slot. You still see the file name fill that slot when you navigate to it on your PC and select it. The install button will be at bottom of Odin screen, I believe. Begin when all is verified.
If all above is a go, just remember that you're looking for a green field that fills and says SUCCESS! Happens quickly and stops (if you setup as directed). Wait until you see Odin log file state that "1 passed, 0 failed". Give it a minute to declare "disconnected" or just wait one minute before proceeding. Since auto reboot was unchecked, you'll have to remove USB and pull battery manually (wait at least 30 seconds after pulling battery before reinstalling). And close Odin after each flash session; you're actually done with the PC for this directive. IMPORTANT: If you fail to go directly to recovery mode after reinstalling the battery, stock recovery will restore itself and you'll have to do the Odin flash of TWRP again. To do this, press and hold volume up, home and power simultaneously until it vibrates; TWRP recovery should launch. You're now ready to backup your stock un-rooted ROM. I recommend backing up to ext SD Card (micro sdcard).
To familiar yourself with TWRP install and use, there's a support thread for that. There's also an official TWRP recovery application in Google Play. Search it there. Note the thread hasn't reflected latest update or developer notes since the official TWRP recovery app launched in Google Play but many unique questions are answered there. Ignore any suggestions to use an older TWRP version or any specific update or Android version. Suggestions like this change over time and may not be relevant at present.
https://forum.xda-developers.com/no...ility-twrp-2-8-1-0-teamwin-t2915591?nocache=1
After backup, I'd recommend installing SuperSU zip with TWRP recovery.
https://forum.xda-developers.com/showpost.php?p=68475511&postcount=1
Make a rooted TWRP backup before applying Xposed and label accordingly, saving to ext sdcard. You can edit the generalized title of backup as you prefer. Rather than the extended fine stamp, shorten to include your description.
Then you can install the Xposed Installer apk (install by sideload method not recovery- you may have already done this) and Wanam unofficial Xposed zip. Follow this thread; I've already linked the zip above but usually you're looking for the highlighted download link and browse to marshmallow SDK 23 arm.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
All threads referenced are your support threads for files referenced. Understand before flashing that there risks you assume yourself. Never a guarantee that you'll be successful or the inevitable happens from followed instructions offered by me or anyone else I've linked you to.
Again, make sure you haven't set reactivation lock in phone's Settings/Security tab before beginning and verify the phone display and Odin states before flashing. Not following could result in phone activating a factory reset protection mode. Not sharing to warning while flashing TWRP recovery may only refuse to flash due to reactivation lock enabled and may state such when using recent Odin releases. But that message may be only abbreviated and cause question of its intent.
Only flash when familiar and confident with instructions. Better to ask than risk misunderstood direction. There may recent demo videos to follow but avoid using suggested older files, noting date of your video; they're not necessarily scripture to live by. Best to use recent files and direction because unlike a certain BOOK, updates and time changes with Samsung, touchwiz and Note 4 development.
There's also some custom ROMs to consider if you follow the road map of XDA links for Sprint Note 4 at top of thread: Note 4 development, rather than Note 4 original development where TWRP support thread. Updates for TWRP can be found in the official TWRP recovery app but I've linked you latest recommended release for flashing in Odin.
Questions? Ask away or read the support threads to familiarize yourself. Many questions are answered there.
Sent from my SM-N920P using Tapatalk
---------- Post added at 10:28 PM ---------- Previous post was at 09:59 PM ----------
Final result on my SM-N910P Note 4. See screenshots.
I'm using a couple of non Xposed modules to compliment modification outside of Xposed. Since compatible modules and applications are sometimes limited, I'll include those for clarification. Both linked below by Google Play link. Strictly optional. Both contain back to kill foreground app shortcuts but may be premium only features- I'm not sure on both or whether one or the other would be ideal. I sort of discovered these apps by recommendation and haven't tried eliminating one or the other.
https://play.google.com/store/apps/details?id=flar2.homebutton
https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontrol
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Hello Samep, I'm impressed and thankful on how you describe everything, I know its takes lon time and dedication to write,, THANKS A LOT, I know these will be the most comprehensive for many many users... I will try to do what you explained. ..
Also thanks to Rom and others for your suggestions and help.
Have a great weekend.. all the best wishes for all.
Regards
Herm.
slm note 4
note 4 I am using n910c 6.0.1. I have installed the device rooted twrp but I do not know which xposed i will install. I write armv7l in the kernel.
I do not know how many sdk I have to help you rejoice
Updated version of this ROM: [ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]G930TUVU4CRI2
ROM last updated: 10/30/2018
Introduction:
HUGE thanks to the guys that got this going like root & figuring out hybrid stocks! This ROM is a complete rewrite of my ROM [ROM][TMOBILE][S7_SM-G930T][Oreo Rooted] That ROM doesnt have WifiCalling & I couldn't get it to work for the life of me, so I rewrote it. I started with stock, and slowly stepped back making changes, reinstalling each time, confirming it still worked. About 200 installs later & 1000s of changes, this is the result. Yes, it took a LONG time. Hope you enjoy it! Don't forget to say Thanks so I know it is actually helpful to others, and continue doing this!
Description:
Stock Tmobile Oreo 8.0 modified (G930TUVU4CRF1)
EXTREMELY debloated! Nearly bare minimum, while still retaining hardware functionality. Eg, Samsung Gallery & Camera exist so we get 4k recording, and there aren't errors when we pull up the Gallery to edit, etc. Yes, this means NO Samsung or Android Pay. There could be more apps to debloat but Im out of time for now! (Please provide suggestions if interested)
Everything possible I replace Samsung with Google
Solid ROM. It was actually kind of slow for me, but I'm curious how this works for others.
Xposed is part of the guide, which will give you infinite customization & tweak-ability
If you hate Samsung SW and just want a solid working ROM with very few install options to get you up and running this is for you.
This will delete all of your data on the phone! (Not external SD card) This is the only way so don't ask. Backup your data!
Features:
Tmobile Wifi Calling works, along with Visual Voicemail & Mobile Hotspot
Many Aroma Installer app options
(Optional) KevinsFavorites option in Aroma. I'm not sure I'd recommend it due to my tastes. If you're looking for some good common apps tho, it includes: Amazon, AmazonMusic, AquaMail, Gmail, GoogleDrive, GoogleKeep, GooglePhoto, Hangouts, IFTTT, Pandora, RootBrowserClassic, TitaniumBackup, Uber, & Wink (If you install these and want to remove them later, use TitaniumBackup (or similiar) to uninstall
Root Features: See Downloads->Recommended Root Zip & say Thanks!
Debloated
De-Knoxed
Decrypted /data/ partition
OTAs disabled
Speed & Build Prop Tweaks
Dual speaker
Ruthless Launcher
Apps
AdAway
AOD Clock Face Themes
CPUSpy
DisableService
Kernel Adiutor
Samsung Video Editor and Trimmer
Xposed
Many more...
Download Links:
Base.7z & Oreo_Kevin71246Modded_v3.#.#.zip
Installation:
This will delete all of your data! If you continue, you acknowledge that the Author is NOT responsible for anything that happens to your phone!
Summary (for Pros)
Flash Oreo stock
Root
Flashfire
Oreo_Kevin71246Modded_v3.1.##, Auto-mount, Mount /system read/write Option
Go through Aroma setup. When finished, it should boot to Recovery (if not do this). Do a "Wipe data/factory reset"->Reboot
Detailed Steps
Install Stock Oreo:
Download mode & Setup
Make sure you have latest device drivers setup on your PC
Enable USB Debugging on phone in Developer Settings
Boot phone into Download Mode:
Turn off your device
Press and hold Volume Down + Home + Power button
When you see the warning screen, release buttons & press Vol UP. Phone should say "Downloading..."
Download and unzip Base.7z to PC (This contains stock Oreo, ODIN, & root)
ODIN
Open ODIN on PC (\Base\Odin_313.exe)
Connect USB from PC to phone. ID:COM in Odin should turn Blue with a COM port
Select AP, BL, CP and CSC files from the \Oreo_Stock\Base\ folder for corresponding files
Select HERO2QLTE_USA_VZW.pit
Select Start
Finished: Phone will reboot & show Carrier screen for 3-5mins. Wait until Setup screen & go through quickly (bare minimum) since you'll wipe it again. Once in Android, go to Settings->Display->Screen resolution->WQHD->Apply
Root Instructions: (+Flashfire, SuperSU)
Reboot phone into Download mode
Odin
AP: Select \Base\Root\AP_SM_G930_OREO_ENG_BOOT.tar
Start-> Wait for phone to boot to Android OS
Root
Double-click \Base\Root\cmd-here.exe & Type: root.bat [enter]
Option: 1 (Install Root No tweaks) (Or pick whatever you want)
*Note: With this system root, do not update su binary. Disable notifications for SuperSU app. Don't flash any superuser zips in recovery that are not made by jrkruse
Install Custom Hybrid ROM & Xposed
Download & copy Oreo_Kevin71246Modded_v##.zip to phone
Flashfire
Open Flashfire on phone
Red + symbol->Flash Zip or OTA->Oreo_Kevin71246Modded_v#, Auto-mount, Mount /system read/write Option->Check mark
Click Lighting bolt at bottom-> OK
Phone will reboot to Aroma. Go through setup. (See above for what's in KevinsFavorites)
When finished, allow Aroma to exit.
It should reboot into Recovery (If not, do this: immediately hold Vol-Up btn+Home btn until you see recovery on screen. If you missed it, try again: hold Vol-Down+Pwr btn ~10sec until phone restarts & immediately hold Vol-Up btn+Home btn until you see recovery on screen.)
In recovery: Factory Reset->Yes->Restart phone
*Wait 5-10min on loading screens
Go thru Android setup. Ignore "Xposed Installer has stopped" error
Followup-Steps:
Set Dialer: Phone Settings->Apps->Menu->Default Apps->Calling App->Select Phone
Recommendations:
Xposed
Setup Xposed: Xposed Installer app:Install framework option & restart phone
Xposed Installer app: Settings button (3 lines)->Download->Search "GravityBox [O]"->Click it->Versions tab->Download->Install->Back arrow (upper left)->Settings->Modules->Check box next to GravityBox [O]->Restart phone
GravityBox [O] Tweaks: (Open GravityBox app)
Battery indicator: Statusbar tweaks->Battery settings->Turn on Master switch->Battery indicatory style: None->Battery percent text...->Back
Clock: Statusbar tweaks->Clock settings->Turn on Master switch->Center clock...
Firefds Kit [O] Tweaks: (Install same way as Gravity box)
This is a supplement to Gravitybox. Things of note: Advanced power menu, call recording, & disable bluetooth toggle popup, etc
Known Issues:
Visual Voicemail may fail to register, but restart phone and give it a few hours. It works eventually.
RCS (Rich Communication Services/AdvancedMessages/Chat) texts don't show up in Android Messages & Textra, etc apps (This is an issue on stock as well!!)
Fix: (Use Samsung Messages)
How to Install Samsung Messages via ADB (Easiest way though is just reinstall!):
Download Messaging_SEP81.zip, unzip, & manually copy apk to phone via usb/Windows My Computer
adb shell (Get into shell to run beow commands)
su (Run as root)
mount -o rw,remount /system (Mount system read/write since default it read-only)
chmod 755 /system/priv-app/Messaging_SEP81 (Set permissions on folder)
chmod -R 644 /system/priv-app/Messaging_SEP81 (Set permissions on apk file)
ls -l /system/priv-app/Messaging_SEP81 (Check permissions - Should be: -rw-r--r-- 1 root root - not sure what 1 & 2 is)
ls -l /system/priv-app | grep "Messaging" (Check permissions - Should be: drwxr-xr-x 2 root root)
reboot (Reboot device)
Changelog:
Version 3.1.32: First stable build
Ver 3.1.36:
-Disabled encryption on /data/ partition to resolve "Bluetooth paired devices deleted after reboot" issue & so mods play nicer with ROM
-Fixed "Device not supported" error on Google Phone app
Ver 3.1.37:
-Added most of the apps I replaced or added as options in Aroma Installer now
Credits:
- @jrkruse & @klabit87 for Root
- @partcyborg for helping jrkruse
- @jrkruse for his similar ROMs as guides & help
- @Lanc-City for assistance in ROM modding
- @gustco for eng boot.img
- @Raymonf for modified odin
- @amarullz for Aroma Installer
- @Chainfire for FlashFire & SuperSU
- @rovo89 for Xposed
- @JaeKar99 for the cool & colorful boot animation
- @mrRobinson for AdAway ADAway.org
- Brandon Valosek for CPUSpy
- WangQi for DisableService
- Willi Ye for Kernel Adiutor
- @shubby for Ruthless Launcher
- @Craz Basics for Dual Speaker Mod
...
- Please PM me if you were forgotten!
Some screenies:
Saved2
Saved3
Well nice job!
jrkruse said:
Well nice job!
Click to expand...
Click to collapse
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
kevin71246 said:
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
Click to expand...
Click to collapse
Is this Ufirm firmware?
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
I have so many FW packages on my PC at this point, from so many places that I used while trying to get this to work, but I think it might be a package from one of your threads(?) Since I'm not exactly sure what you're asking regarding "Ufirm FW", I'll elaborate hoping that answers your question. (Tho I'm thinking you mean the U variation/unlocked. So based on these stock files below I guess the answer is no.) If you're question is really, "is it possible to get tmobile wifi calling to work on a U model #", then I'd have to really think about that. But at this point I don't have an answer. I can tell you a million dependencies about it tho! (I seriously have hundreds of revisions I made while testing, & notes. The symbolic & meta links in Aroma initially broke it, as I found out after a week or so of testing - wish I knew a bit more about them, and why they're all there, then I'd know what was wrong about them...)
High-level process:
1)Flash Base/Stock/Oreo Rom:
- AP_G930TUVU4CRF1.tar
- BL_G930TUVU4CRF1.tar
- CP_G930TUVU4CRF1.tar
- CSC_TMB_G930TTMB4CRF1.tar
- HEROQLTE_USA_VZW.pit
2)Root with your method
3)Flash Xposed framework & my ROM (it's a "start with stock then remove what we don't want" type of Aroma/Edify script)
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
kevin71246 said:
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
Click to expand...
Click to collapse
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
It works perfectly!!
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
charredchar said:
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
Click to expand...
Click to collapse
I believe I know what the issue is, I'm testing a fix (for THIS ROM) as we speak. Stay tuned. Maybe tomorrow if I have time and it works I'll update the OP. BTW, this ROM and my other ROM are TOTALLY different. Thanks for the feedback!
FranMLG said:
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
Click to expand...
Click to collapse
What do you mean by this? "but if you do not pull them, let me know"
And tell me more about Viper4Android, and if it works solid for you on this ROM...then I'll consider adding it. Thanks!
New version, see change log in OP for details.
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
jrkruse said:
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
Click to expand...
Click to collapse
Hi, why you have to flash this - HEROQLTE_USA_VZW.pit on 930t, is it ROM specified? if I do and don't then what are pro and cons?
---------- Post added at 01:36 PM ---------- Previous post was at 01:26 PM ----------
josh2020glacier said:
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
Click to expand...
Click to collapse
since bootloader is locked you can't use TWRP so you have to use Flashfire to install this ROM, as you know flashfire required root so you have to setup the base per OP and then root the base then install the ROM and then root it again, read the first page I don't think you will get a instructions more detailed then his
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Alkan3 said:
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Click to expand...
Click to collapse
Nauseating rainbow? LOL. Sorry. This is much more of a general question though, that wouldn't exactly pertain to this ROM specifically. And given I don't have an answer, I'd try searching BootAnimation How-Tos to get this customized. The ONLY thing I did regarding this was replaced the existing files with the rainbow ones. That's it. Apologies in advance.
Just discovered an issue: RCS (Rich Communication Services / Chat) texts don't show up in Android Messages app. See "Known Issues" in OP for a solution. BTW I posted a new ROM version a few days back that allows many choices in Aroma Installer. Make sure to pick Samsung Messages (instead of Google), so you get RCS chat text messages!
See post #3 for in depth guide !
->insert usual general disclaimer of liability
Required:
Odin3_v3.14.1 flash tool
Samsung USB Driver installed
Frija or something else, to download stock files
7zip or similar
1: Unlock bootloader (will wipe your precious data, void warranty, break Knox e-fuse and who knows what else !)
-unlock dev option (just harass your Build number in settings)
-be connected to the internet (WiFi or 5g)
-allow USB debugging
-OEM unlock
-be warned that this might cause WWIII
-Power off your device. Press Volume Up + Volume Down THEN plug your Tablet lnto a PC to boot into download mode.
-Release buttons immediately when the blue screen shows itself.
-Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
-Go through the initial setup.
-Skip through all the steps except wifi or 5g
-sign into your Google or Samsung account
-Enable Developer options & USB debugging
-reboot
-You have an unlock bootloader and have control over your device, (it is unfair that this voids your warranty as you should be able to use your hardware as you please).
2: Root install:
-Install Magisk
-use frija or something else to get the latest file according to your device and your CSC :
-patch the whole AP file with magisk (transfer of big files can be tricky, using SD card to transfer file from computer to tablet and vice versa seems like one if the easiest way)
-use odin to flash AP (the patched one), CP, BL and CSC (will wipe once again and reboot)
-Open magisk to finish install (reboot)
-You have root
3: Root update:
-use Frija or something else to get the latest file according to your device and your CSC :
-patch the whole AP file with magisk
-use Odin to flash AP (the patched one), CP, BL and Home_CSC (using CSC will wipe)
-Press and hold Vol-down and Power let go of all buttons once the screen turn on.
-You have root, data kept and update
Please let me know if something should be added or edited.
Hi @Vinsang! Thanks for the nice post. I'd like to suggest you edit the type of thread this is and make it a "How To Guide" instead of "Question" thread. That will help it stand out, especially if anyone uses the Quick Filters at the top of the list of threads in this section.
Edit: Thanks for changing it. Cheers!
How to Root (or update an already-rooted device)Prereqs
Install the USB driver from https://developer.samsung.com/android-usb-driver
Get the latest Odin from https://odindownloader.com/category/download and unzip it
Get the latest Frija from https://github.com/SlackingVeteran/frija/releases and unzip it
Start Frija and begin downloading the latest firmware for your Model and CSC:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Model Numbers
S8 Ultra 5G: SM-X906
S8 Ultra Wifi: SM-X900
S8+ 5G: SM-X806
S8+ Wifi: SM-X800
S8 5G: SM-X706
S8 Wifi: SM-X700
CSC: Settings > About Tablet > Software Information > Service provider software version
Step 1 - Prepare your Tablet (only necessary for first install on unrooted device)
While Frija is downloading the firmware, prepare your device by doing the following:
Settings > About Tablet > Software Information > Click Build Number 7 times quickly
Developer Options (just below About Tablet on the left column)
Turn on USB Debugging
Turn on OEM unlocking
NOTE: If the OEM Unlocking option doesn't appear, connect the device to the internet, wait a few minutes, then try again
Power tablet completely off (Hold volume down + power button if you haven't changed the Bixby settings)
While holding volume up and volume down, plug the tablet into your PC via USB
Let go of volume keys as soon as the blue-green screen shows up
Press and hold volume up for 5 seconds, the screen will change to a confirmation prompt
Press volume up again to confirm, the tablet will reboot
Unplug your tablet from USB
Go through initial setup. Don't bother copying files or installing anything.
Skip signing in to your Google account and Samsung account. You won't be using them for this step.
Settings > About Tablet > Software Information > Click Build Number 7 times quickly
Developer Options (just below About Tablet on the left column)
Turn on USB Debugging
Reboot the tablet
Step 2 - Patch the stock firmware to make it rooted
Frija should have finished downloading by now, unzip the file (remember where you unzipped it to)
Plug your tablet in to your computer via USB and click Allow if it prompts to allow data access
If this is your first install / you're rooting the tablet for the first time:
Download Magisk-vXX.XX.apk from the topmost release at https://github.com/topjohnwu/Magisk/releases
Copy the Magisk-vXX.XX.apk and the AP_xxx_xxx_tar.md5 from the zip file Frija downloaded to:
This PC > Galaxy Tab S8 Ultra > Internal Storage > Download
Open the My Files app on the tablet and browse to Downloads
Click the Magisk-vXX.XX.apk and it will prompt you to click Settings
In Settings, turn on My Files, then it will give you a prompt to Install
When Magisk is done installing, click Open
If your tablet was already rooted, and you're just updating:
Copy the AP_xxx_xxx_tar.md5 from the zip file Frija downloaded to:
This PC > Galaxy Tab S8 Ultra > Internal Storage > Download
After the file is done copying, unplug your tablet from USB
In Magisk, click Install in the top Magisk area, then the option for Select and Patch a file
Click My Files > Downloads, select the AP_XXX_XXX.tar.md5 file and click Done at the bottom
Click Lets Go -> After a few moments, it should display this (ignore 'Installation failed' at the top, it always does that):
Step 3 - Apply the rooted firmware
Plug your tablet back in to USB, then on your PC, go back to This PC > Galaxy Tab S8 Ultra > Internal Storage > Download and copy the magisk_patched-xxx.tar file back to the folder where you unzipped the zip file from Frija
After the copy is finished, unplug your tablet from your PC and completely power off your tablet
While holding volume up and volume down, plug the tablet into your PC via USB
Let go of volume keys as soon as the blue-green screen shows up
Click volume up (the side of volume nearest the power) briefly (don't hold it) to go into download mode
Start Odin and accept the disclaimer prompt
Click BL and select the BL_XXX_XXX.tar.md5 file where you unzipped the zip file from Frija
Click AP and select the magisk_patched-XXX.tar file
If this is your first install / you're rooting the tablet for the first time (this WILL wipe your data):
Click CSC and select the CSC_XXX_XXX.tar.md5
If your tablet was already rooted, and you're just updating (this WILL NOT wipe your data):
Click CSC and select the HOME_CSC_XXX_XXX.tar.md5
Odin should now look like this:
Click Start. When it's finished, Odin will display "PASS!" and the tablet will automatically reboot.
Step 4 - Verify and finalize
Go through the normal setup, signing in to your Google and Samsung accounts this time
Click on Magisk that is now pre-installed, and go through the Settings step to allow it to install again
It should prompt you that your device needs additional setup and one more reboot, click OK
After rebooting, your device should be fully rooted. Use a root checker app if you want to verify.
Step 5 (optional) - Get Netflix (and banking apps etc) working with root
Install https://github.com/Fox2Code/FoxMagiskModuleManager/releases and run it
Search for Universal Safetynet Fix by kdrag0n and install it
In Magisk settings click Systemless hosts, turn on Zygisk, turn on Enforce Denylist
Click Configure Denylist, then the 3 dot menu and Show System Apps
Search for Google Play Store, click it, check the check and turn on all options underneath
Search for Google Play Services, click it, turn on .gms and .gms.unstable ONLY
Search for Netflix, click it, check the check and turn on all options underneath
(optional) Add your bank / pay app, etc here if you'd like
In Settings > Apps, search for Google Play Services and Google Play Store and clear all data (not just cache) for each
Reboot
NOTE - This is currently only passing Widevine level 3, so Netflix is limited to SD. I'm still trying to figure out how to get L1 / full HD.
Is there currently any way to make nandroid backups without TWRP since there isn't a build of it for the Tab S8 line yet?
SavXL said:
Is there currently any way to make nandroid backups without TWRP since there isn't a build of it for the Tab S8 line yet?
Click to expand...
Click to collapse
Not you can't make a full nandroid back up without TWRP for the moment. You can use Swift backup or something similar to backup some things in particular, Google backup is also pretty convenient.
Anyone work out how to get Netflix working with root yet? Also, is Magisk manager showing any modules to download in the Magisk app for you guys? I can install from file, but the downloading functionality doesn't seem to be working.
Dunno about Netflix, but this worked for banking apps:
Add this module : https://github.com/kdrag0n/safetynet-fix
Zigisk and enforced denylist on and add Netflix (or other) in the deny list. Reboot and tryout.
It seemed that the download section isn't there anymore on the latest magisk, same on other devices. You gotta download them separately.
skrowl said:
Anyone work out how to get Netflix working with root yet? Also, is Magisk manager showing any modules to download in the Magisk app for you guys? I can install from file, but the downloading functionality doesn't seem to be working.
Click to expand...
Click to collapse
Not sure when, but somewhere in an update, the ability to download modules from magisk directly was removed. You can download them using an app called Fox's Magisk Module Manager. You can search for modules just like you could on Magisk, and they'll be added once you install them and reboot. Also, for the netflix thing, your device may not be passing safetynet. Checking this was also remove in an update, but you can check it with YASNAC.
Edit: I just did this with my rooted Tab S7+, but it should work with the S8+ and S8U as well. Doing this should let you pass safetynet and be able to use Netflix.
1. Enable Zygisk in Magisk settings, then reboot.
2. Enable Enforce DenyList in Magisk settings, then go to Configure DenyList.
3. Enable show system apps with the menu on the top-right, then search "google play services".
4. Enable DenyList for com.google.android.gms & com.google.android.gms.unstable, then reboot.
5. Open YASNAC to run safetynet attestation, you should be passing basic integrity but failing cts profile match.
6. Download and install the latest version of the safetynet fix for zygisk module, then reboot.
7. Check YASNAC again, you should now be passing basic integrity and cts profile match.
8. Go to settings > apps, find google play service & google play store, clear data for both of them, reboot.
9. Go to the play store > settings, play protect certification should now say "device is certified".
10. Open Magisk > Configure DenyList, search for Netflix (enable show system apps if you need to), enable DenyList for everything, reboot.
11. Update Netflix if it's not up to date. If the play store is allowing you to update Netflix at all, then you're good to go.
Now you have Netflix running on your rooted tab!
Edit 2: Accidentally saved my first edit before I finished the instructions, my bad.
skrowl said:
Prereqs
Install the USB driver from https://developer.samsung.com/android-usb-driver
Get the latest Odin from https://odindownloader.com/category/download and unzip it
Get the latest Frija from https://github.com/SlackingVeteran/frija/releases and unzip it
Start Frija and begin downloading the latest firmware for your Model and CSC:View attachment 5574197
Model Numbers
S8 Ultra 5G: SM-X906
S8 Ultra Wifi: SM-X900
S8+ 5G: SM-X806
S8+ Wifi: SM-X800
S8 5G: SM-X706
S8 Wifi: SM-X700
CSC: Settings > About Tablet > Software Information > Service provider software version
Step 1 - Prepare your Tablet
While Frija is downloading the firmware, prepare your device by doing the following:
Settings > About Tablet > Software Information > Click Build Number 7 times quickly
Developer Options (just below About Tablet on the left column)
Turn on OEM unlocking
Turn on USB Debugging
Power tablet completely off (Hold volume down + power button if you haven't changed the Bixby settings)
While holding volume up and volume down, plug the tablet into your PC via USB
Let go of volume keys as soon as the blue-green screen shows up
Press and hold volume up for 5 seconds, the screen will change to a confirmation prompt
Press volume up again to confirm, the tablet will reboot
Unplug your tablet from USB
Go through initial setup. Don't bother copying files or installing anything.
Skip signing in to your Google account and Samsung account. You won't be using them for this step.
Settings > About Tablet > Software Information > Click Build Number 7 times quickly
Developer Options (just below About Tablet on the left column)
Turn on USB Debugging
Reboot the tablet
Step 2 - Patch the stock firmware to make it rooted
Frija should have finished downloading by now, unzip the file (remember where you unzipped it to)
Plug your tablet in to your computer via USB and click Allow if it prompts to allow data access
If this is your first install / you're rooting the tablet for the first time:
Download Magisk-vXX.XX.apk from the topmost release at https://github.com/topjohnwu/Magisk/releases
Copy the Magisk-vXX.XX.apk and the AP_xxx_xxx_tar.md5 from the zip file Frija downloaded to:
This PC > Galaxy Tab S8 Ultra > Internal Storage > Download
Open the My Files app on the tablet and browse to Downloads
Click the Magisk-vXX.XX.apk and it will prompt you to click Settings
In Settings, turn on My Files, then it will give you a prompt to Install
When Magisk is done installing, click Open
If your tablet was already rooted, and you're just updating:
Copy the AP_xxx_xxx_tar.md5 from the zip file Frija downloaded to:
This PC > Galaxy Tab S8 Ultra > Internal Storage > Download
Open Magisk
In Magisk, click Install in the top Magisk area, then the option for Select and Patch a file
Click My Files > Downloads, select the AP_XXX_XXX.tar.md5 file and click Done at the bottom
Click Lets Go ->. After a few moments and it should give you a screen like this:View attachment 5574199
Step 3 - Apply the rooted firmware
On your PC, go back to This PC > Galaxy Tab S8 Ultra > Internal Storage > Download and copy the magisk_patched-xxx.tar file back to the folder where you unzipped the zip file from Frija
After the copy is finished, unplug your tablet from your PC and turn the tablet off
While holding volume up and volume down, plug the tablet into your PC via USB
Let go of volume keys as soon as the blue-green screen shows up
Click volume up briefly (don't hold it) to go into download mode
Start Odin and accept the disclaimer prompt.
Click BL and select the BL_XXX_XXX.tar.md5 file where you unzipped the zip file from Frija
Click AP and select the magisk_patched-XXX.tar file
If this is your first install / you're rooting the tablet for the first time:
Click CSC and select the CSC_XXX_XXX.tar.md5
If your tablet was already rooted, and you're just updating:
Click CSC and select the HOME_CSC_XXX_XXX.tar.md5
Odin should now look like this:View attachment 5574201
Click Start. When it's finished, Odin will display "PASS!" and the tablet will automatically reboot.
Step 4 - Verify and finalize
Go through the normal setup, signing in to your Google and Samsung accounts this time
Click on Magisk that is now pre-installed, and go through the Settings step to allow it to install again
It should prompt you that your device needs additional setup and one more reboot, click OK
After rebooting, your device should be fully rooted. Use a root checker app if you want to verify.
Edit - Thanks OP, but I don't think of this as a better guide. I just took really careful notes of what I was doing, so that I'd be able to reproduce it in 6 months when my brain had completely forgotten all the buttons!
Click to expand...
Click to collapse
Excellent guide. I just had my OOBI this morning & I forgot about having to change the date to an earlier one, check for a software update, etc before being able to see OEM unlock in developer settings. But that's a one & done.
skrowl said:
Anyone work out how to get Netflix working with root yet? Also, is Magisk manager showing any modules to download in the Magisk app for you guys? I can install from file, but the downloading functionality doesn't seem to be working.
Click to expand...
Click to collapse
To download magisk modules use this app; https://github.com/Fox2Code/FoxMagiskModuleManager
To hide root you can try this:
1. Magisk -> Settings -> Hide the Magisk app (It will get a new random package name so other apps won't see that it's actually Magisk and additionally you can choose a new name for the app as well.)
2. Open the newly created magisk app, install extra files when prompted and tab will reboot automatically.
3. Flash MagiskHide Props Config https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/releases
4. Reboot
5. Flash Universal Safetynet Fix https://github.com/kdrag0n/safetynet-fix/releases
6. Reboot
7. Add any app you want to hide root from to DenyList: Google Play Store, Google Play Services, Google Services Framework, Netflix, banking apps etc.
8. Enforce DenyList MUST stay turned off!
9. Flash Shamiko module to hide root properly.
Releases · LSPosed/LSPosed.github.io
Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.
github.com
10. Reboot
After checking Frija, found that an update was available fro my SM-X906B EUX, Just updated to X906BXXU1AVCD/X906BOXM1AVCD/X906BXXU1AVCD using step 3 of the guide without issue (root and data kept).
Is there a way to be notify when an update is out ? Or do i have to manually check every month?
Do we have changelog or something similar?
Vinsang said:
After checking Frija, found that an update was available fro my SM-X906B EUX, Just updated to X906BXXU1AVCD/X906BOXM1AVCD/X906BXXU1AVCD using step 3 of the guide without issue (root and data kept).
Is there a way to be notify when an update is out ? Or do i have to manually check every month?
Do we have changelog or something similar?
Click to expand...
Click to collapse
Someone else had given the link to this site (for your model) https://samfw.com/firmware/SM-X906B.
No automatic notifications, but I use a Windows program that checks sites for updates (https://samfw.com/firmware/SM-X900 for my model, which won't arrive for another 12 days).
Might also be able to use https://www.sammobile.com/firmwares/
Somewhere on this site might occasionally be generic changelogs https://www.sammobile.com/news/galaxy-tab-s8-ultra-february-2022-security-update-released/#
Samsung Galaxy Tab S8 Ultra
Introduction Samsung is making no secret of the fact that it wants to offer the best Android tablet on the market. ...
www.sammobile.com
Samsung Galaxy Tab S8+
Introduction Prior to the Galaxy Tab S8 series, the
www.sammobile.com
Samsung Galaxy Tab S8
Introduction Samsung's flagship tablet lineup was due for a major refresh and the company came through with the Galaxy Tab S8 ...
www.sammobile.com
Quick question. If another software update were to come out, could I update it and still have magisk and root access afterwards? My Tab S8+ says its device status is official, and it doesn't tell me that my device is rooted when I connect to the server to check for updates. So, if I updated this way, would that remove the whole patching the AP file with magisk and flashing it with Odin thing? It'd be awesome to have the latest updates and such while maintaining root access.
To keep root and your data while updating, follow the step 3 of the guide in post #1( it requires that you look manually for updates).
I wouldn't advise to update via OTA while rooted. I don't even think you'll get the prompts.
Vinsang said:
To keep root and your data while updating, follow the step 3 of the guide in post #1( it requires that you look manually for updates).
I wouldn't advise to update via OTA while rooted. I don't even think you'll get the prompts.
Click to expand...
Click to collapse
That's odd because I got the prompt to update on my rooted Tab S7+ (it also says the device status is official) when the OneUI 4.1 update came out for it. I haven't tested to see if that would change anything, but since the S7+ has TWRP, I can just restore a backup Incase something doesn't turn out well.
Hi all. I purchased a SM-X900 from the Samsung website(UK). I am having a serious problem with getting the OEM unlocking option to display in the developer options menu. I have tried the known workarounds (change date/disable automatic updates, etc) but had no success. Does anyone have any other methods/ideas? I previously had the tab s7+ and had no problems with this.
Any tips would be much appreciated!
brunosilvauk said:
Hi all. I purchased a SM-X900 from the Samsung website(UK). I am having a serious problem with getting the OEM unlocking option to display in the developer options menu. I have tried the known workarounds (change date/disable automatic updates, etc) but had no success. Does anyone have any other methods/ideas? I previously had the tab s7+ and had no problems with this.
Any tips would be much appreciated!
Click to expand...
Click to collapse
I've had some issues where after enabling OEM Unlocking and going through the process, after Unlocking and resetting, the option disappears, but OEM is still unlocked. Not sure what causes this, but after rebooting for some root-required things and checking again, the option was there and changeable. I actually went throught the normal initialization process on my Tab S7+ and Tab S8+ (wifi, clock, samsung account, etc) and never had any issues. Maybe try either factory resetting again or flashing latest stock firmware (you can flash official firmware even if oem is locked). YMMV though. This specific issue of the option not showing up at all never happened for me, so I'm not sure how much help my suggestions will be.
SavXL said:
I've had some issues where after enabling OEM Unlocking and going through the process, after Unlocking and resetting, the option disappears, but OEM is still unlocked. Not sure what causes this, but after rebooting for some root-required things and checking again, the option was there and changeable. I actually went throught the normal initialization process on my Tab S7+ and Tab S8+ (wifi, clock, samsung account, etc) and never had any issues. Maybe try either factory resetting again or flashing latest stock firmware (you can flash official firmware even if oem is locked). YMMV though. This specific issue of the option not showing up at all never happened for me, so I'm not sure how much help my suggestions will be.
Click to expand...
Click to collapse
Thanks, in my case, I have not seen this OEM option at all, since I received the device. I have not been able to root it.
brunosilvauk said:
Thanks, in my case, I have not seen this OEM option at all, since I received the device. I have not been able to root it.
Click to expand...
Click to collapse
Well, something I can recommend is downloading the latest firmware update for your specific device (use either frija or samfw), going into download mode by holding vol+ and vol- while connecting the device to a PC, and flashing it with Odin, or you can update officially since your device hasn't been rooted yet. Maybe the current version you're on is affecting it somehow? No clue man. This issue is brand new to me.
SavXL said:
Well, something I can recommend is downloading the latest firmware update for your specific device (use either frija or samfw), going into download mode by holding vol+ and vol- while connecting the device to a PC, and flashing it with Odin, or you can update officially since your device hasn't been rooted yet. Maybe the current version you're on is affecting it somehow? No clue man. This issue is brand new to me.
Click to expand...
Click to collapse
No joy, have no idea how to fix this. Thank you for your input anyway! Maybe someone else has any other ideas?