[Q] Kali Nethunter on galaxy tab s2 - Galaxy Tab S2 Q&A, Help & Troubleshooting

I have the permissive t710 kernel flashed that was required for rooting. I am wondering if anyone has had success running kali nethunter on thier galaxy tab s2. I tried to flash the oneplus one nethunter v3 after flashing CM 12.2 on to my tab s2. At the end of the process there were many lines of red text describing "partition" or some other file path that was missing. I restored to my stock ROM after those errors and never tested it. I have since read about those errors maybe not being the death nail in the coffin for a kali nethunter install that I thought they were. Does anyone know which version would work best and if it could be flashed successfully on the stock ROM with the permissive kernel? Thanks to anyone who has any experience with this or any information!

From the above mentioned state I flashed the latest (20160418) CM 12.1 then gapps, rebooted and then flashed kali nethunter v3 for lollipop. I got the same errors as above; but kept going and it appears to be functioning to some degree. Using TWRP recovery for this. I upgraded to 3.0.5 via the internal nethunter upgrader successfully. I need a y cable to test fully. No word yet on how functional this is; but it looks relatively promising.

i had nethunter 3 installed on samsung galaxy tab a. all features worked except dsploit which kept crashing when identifing vunrabilities, besides that a y cable got my alfa card fired up and injecting in no time

Related

Problem with HyperDrive Rom on Safe Strap ME7

Im having a bit of an issue with the HyperDrive rom on my Safe Strapped Galaxy S4. I've verified the hash so the error is probably not coming from an invalid hash. When I was using 9.1.0 I had no problems installing it and running after Flashing the ME7 modules. However when i attempted to flash the 10.0.0 Update it installed with no problems however i get a black screen upon booting. I never see the Boot animation apart from Safe Strap's menu on startup. If anyone could help me that would be fantastic.

[Q] What to do?

This is a Samsung Galaxy Ace newbie user. I've previously owned a Galaxy Y and have successfully flashed many roms, bricked, unbricked, etc. many times.
Now I upgraded to a hand me down galaxy ace from my mom. I started trying out roms. I followed this tutorial:-
h t t p : / /w w w .android .gs /update - galaxy - ace - android-4-4-2-cm11 - firmware
{Remove the spaces. I'm new here so I can't add URLs. Forgive the cheating}
I used CWM 6.0.4.6
Now my phone works properly but I can't add a google account. Everytime I try It shows connection error whereas the internet works just fine when I use the browser. I am unable to fix it by flashing a gapps package.
The CWM recovery is unable to install the gapps package.
Somehow I installed root explorer using terminal emulator. I installed another google play but it also doesn't work. The problem continues.
The root explorer asked for downloading some extra utilities(optional) so I confirmed but it doesn't download. I thought about changing the ROM but the CWM doesn't install it.
I tried down-grading the CWM but the upgraded one doesn't do that. It aborts the installation.
I can't get the stock roms so I can flash using odin.
I don't know ANYTHING about programming. I'm 14. Please help
Hi Shikharmn.
From your current recovery, you could flash the Mardon's last Recovery CWM 6.0.4.7
http://forum.xda-developers.com/showpost.php?p=49997664&postcount=143,
from that recovery you could flash 5.0.2.6 recovery and then custom roms.
Cheer. Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted

Need help to flash custom OS S4 active

Hi
I`m helping a friend rooting and flashing a custom os to his S4 active I9295
I have previous rooting experience with htc legend/desire, nexus 5 and galaxy tab.
I have done the following:
Method 1:
Flashed CWM with odin
Entered CWM trying to flash SuperSU, but here I failed.
Error message, and no supersu installed.
method 2:
Flashed CF auto root through ODIN
SuperSU installed and root access OK
Entered CWM
Full wipe
Trying to flash CM12 nightly latest build, but here I fail.
Error message and no Cyanogenmod installed.
Phone reboots with stock samsung OS automatically
can anyone point me in the right direction here?

[Solved] Rom setup blocked, Tab S2, T813 blocked!

Hi dear developers,
I just got my new Galaxy Tab S2, T813. Updated it to Nougat, firmware T813XXU2BQD1_T813OXA2BQD1_DBT. I rooted it via Chainfire's autoroot and worked perfectly fine. I installed the latest TWRP (twrp-3.1.1-1-gts210vewifi), advance wiped in twrp (like tens of times before with Galaxy S5, Galaxy S7, Redmi 4, ZUK Z2, Xiaomi Mi 5s, LG G2 etc.). I flashed Lineage 14.1 (Lineage-14.1-20170516-nightly-gts210vewifi) but when I rebooted the phone Lineage setup would not start. I went back and advance wiped again and installed an older Lineage version but again the same. I advance wiped again and installed Omni (Omni-7.1.2-20170521-gts210vewifi-weekly), but here again setup would not start. I reformatted the data in twrp and reinstalled Lineage 14.1 but again the same. So I went back and flashed via Odin3_v3.12.3 the stock firmware (for Germany) T813XXU2BQD1_T813OXA2BQD1_DBT. Odin command was pass and i though everything was fine. When the original firmware rebooted i have the same problem, the setup would not start and starting apps would crash. I entered recovery (of course stock recovery because twrp has been wiped by odin), but it says "no command".
Smart Switch would not support my device although it actually should.
I tried to flash via odin also on my second PC but again the same problem. Both PCs are running Windows 10.
I never faced something like this before. And after hours of search I found nothing. Please help me solve my problem so that i can install at least one firmware (no matter which one: Stock, Lineage, Omni etc.).
When you flashed lineageOS or omni rom, did you also flash gapps?
musashiken said:
When you flashed lineageOS or omni rom, did you also flash gapps?
Click to expand...
Click to collapse
First time flash:
+ clean advanced wipe
+ lineage
+ gapps (ARM64, Android 7.1, Pico)
+ addonSU
other times flash:
+ clean advanced wipe
+ lineage
or
+ clean advanced wipe
+ omni
I believe either flashing Chainfire Autoroot file or flashing TWRP might have caused the problem and might have deleted something or maybe i deleted something during first time wipe via twrp.
Is there a patch or aboot or something to flash via Odin prior to flashing the stock firmware to correct the problem with stock rom setup blockade?
Ok, I'm not sure what went wrong with how you did stuff but let's not use Chainfire's autoroot again. The best way to root is to do it manually.
Anyway, firstly you should be able to go back to stock samsung firmware by using Odin and flashing the full tar file. I'm not sure why that is not working for you as that's the only way to reset and fix your tablet.
Please check how to flash the full firmware via Odin again.
- ensure you downloaded the correct nougat firmware file. Latest LineageOS should require the EU version of the nougat firmware. I think it is T813XXU2BQD3. Not the firmware you used.
Once you are able to load a fresh samsung firmware, then come back again. I'll see if I can guide you through the TWRP and rooting process again.
musashiken said:
ensure you downloaded the correct nougat firmware file. Latest LineageOS should require the EU version of the nougat firmware. I think it is T813XXU2BQD3. Not the firmware you used.
Click to expand...
Click to collapse
Thanks fo the tip with the new version of firmware. I installed the firmware ...QD3 via Odin...
Closed per OP request

Tab S2 SM-T810 boot loop with Nougat ROMs

Hi,
I have am (still) running the vanilla 5.1.1 firmware, rooted, with a lollipop permissive kernel and TWRP 3.1.0. I am trying for some time now to install LineageOS 14.1 or other nougat ROMs, and I always run into a boot loop at the first "Samsung Galaxy Tab S2" screen. I tried installing different Nougat kernels with the Roms, but to no avail. Any help would be highly appreciated, because I still love this tablet but I'd really like to have a more up to date ROM...!
Nevermind, I got it figured out: I had to upgrade the stock firmware to 7.0 first. Now installing Nougat ROMs works.

Categories

Resources