IPTables - Moto G5 Questions & Answers

I'm considering getting a Moto G5 and from what I have seen it looks easy enough to root and install a recovery but I was wondering if any of the roms support iptables. My current phone is an old Galaxy S2 but it's started rebooting randomly and it will often just sit at the Galaxy S2 start screen and won't actually boot any further unless I restore from a CWM backup.
EDIT: I'm used to having droidwall or android advanced firewall+ on my phone which is a front end to iptables, which is why I'm enquiring about support.

Related

[Q] Samsung Galaxy Tab i9000 failed to boot and not showing any user screen

Hi Guys,
I was trying to install a custom rom on my galaxy tab.I downloaded Rom Manager from market and was trying to take backup by booting my phone and tried to take Nandroid backup but not able to find that when I rebooted my tab.So i tried to find a app on market by searching "nandroid" and found 3 apps as a search result and I downloaded 3rd app from market.
After that I rebooted my tab and It is not coming up.It is showing samsung startup screen and then screen is active but not showing anything and keep on vibrating in every few seconds.I am not able to see anything on my screen now but I can get reboot screen with options like:-
reboot
clear cache data
wipe out all data
Please let me know what should I need to do to get my tab up and running... Its very urgent...
Thanks in advance
I'm having the same issue w/ my HTC Thunderbolt (ADR6400). I followed the directions and used the files referenced in the forums here. This is the "Easy Flash" app method. I did have the 605.6 software on the device stock from HTC. I was initially not able to get past step one (it would not actually write the files. After trying it about 5 times, it finally flashed and rebooted on its own and installed the old 1.03.605.10 software. It took a long time to finally boot back up, and now every time I try to connect it via USB w/ Debugging Mode on to do steps 2 and 3 it crashes the device and like Survivor's Tab situation, gets stuck w/ the boot-up screen
Is there a way to either A) get around this crashing-on-debugging-mode issue to finish the rooting, or B) restore it to its original firmware? At least it turns on, but I posted in this thread since the solution for him is probably the same as for me (whatever that might be). I've rooted other Linux-derived OSes before (Ie, WebOS 1.4x), and didn't have these kinds of issues. Any ideas would be most helpful to both of us.

Not bricked but won't get past initial start up screen

Hi.
My son's Galaxy Nexus (Verizon) is having some serious issues. HE has been crack flashing everything under the son (Just like his data) and recently he tried a 4.3 rom (Not sure which one). He started to get random crashes so he flashed back to one of the 4.2.2 rom. Then the phone started crashing all the time so I hooked it up the the Nexus toolkit (I assume it is the one everyone uses) and decided to do a full wipe. The phone was basically two folders and would not boot past the Google logo.
When I hooked it up to the tool kit software it was recognized and I flashed the stock (VZ) rom, no root. When I booted the phone it would go to the start screen looking for WiFi and when I tried to go through the start up process the phone would lock up and reboot. I cannot get past this point to do any troubleshooting.
So is this a hardware issue (The phone is toast) or am I missing something as far as doing a complete wipe to get back to bone stock?
Thank you for your help. (I have as well as my son have been trolling this site and others looking for answers but since I can boot up most did not apply, I think)
mlfca said:
Hi.
My son's Galaxy Nexus (Verizon) is having some serious issues. HE has been crack flashing everything under the son (Just like his data) and recently he tried a 4.3 rom (Not sure which one). He started to get random crashes so he flashed back to one of the 4.2.2 rom. Then the phone started crashing all the time so I hooked it up the the Nexus toolkit (I assume it is the one everyone uses) and decided to do a full wipe. The phone was basically two folders and would not boot past the Google logo.
When I hooked it up to the tool kit software it was recognized and I flashed the stock (VZ) rom, no root. When I booted the phone it would go to the start screen looking for WiFi and when I tried to go through the start up process the phone would lock up and reboot. I cannot get past this point to do any troubleshooting.
So is this a hardware issue (The phone is toast) or am I missing something as far as doing a complete wipe to get back to bone stock?
Thank you for your help. (I have as well as my son have been trolling this site and others looking for answers but since I can boot up most did not apply, I think)
Click to expand...
Click to collapse
Right off the bat, do NOT use toolkits anymore. Please. You need to learn how to use Fastboot.
The best thing to do is start completely fresh. Download latest Galaxy Nexus factory images and fastboot them.
If you have no idea how to use fastboot, I suggest going to this thread and reading up my man: [GUIDE]New To Adb And Fastboot Guide
Any other questions or help I can gladly answer.

[Q] bricked S2 d710 w/Odin-OC ???

Just purchased a display model Sprint Epic Touch D710 and decided to root it with Odin-OC. It appeared to go flawlessly (PASSED) but when restarted several times only comes up to home screen enter pass code and home screen does not respond to anything - locks up at this point and reboots. My actual model is MV SAM710BK if this makes any difference. It came with Sprint FreedomPop. I should have backed it up before rooting but did not. Should I try to unroot it and go back to stock? Can I just reverse the rooting? Thanks in advance - Bill
Fixed problem - phone back working better than ever!
Hopefully this will help someone else who does the same thing. First BACKUP!!! before rooting or changing ROM I know this is basic but I messed up and its scary not knowing if your device will ever work again or not. If you need to "goback" like me well you cant since there was no backup so what I did was load the latest stock rom - no erase data - that WAS also rooted. I guess the worst that could have happened was I would have wiped the device and gone back to stock. Go to this web site:
http://www.rwilco12.com/downloads.p...ung Galaxy S2 (Sprint) (SPH-D710)/Stock ROMs/
and get the latest ROM available in my case it was Odin GA10_818252_Rooted_Nodata and once installed it will open Odin3Excution v1.81 interface where you connect and download with basically one click. The Update or whatever you want to call it is better than the stock one I received with bloatware gone and things working better than original. Awesome resource RWilco12's web site!

Looking for a specific backup method (LOS 18)

Hi there guys
Using LOS 18 on a Galaxy A70.
Android 9 on a Galaxy S8+ (Stock ROM)
And Android 6 on a Galaxy S5. (Stock ROM)
I have made a few tweaks where I have enabled call recording and tweaked mic volume as per the very useful guides here. Tis applied to all phones mentioned above.
Ideally it would be good to have those configurations backed up in a complete system backup.
The phones are all rooted and it would be good to have a backup done of the phones being fully rooted and just have EVERYTHING in the EXACT same state put back (if I were to one day reset the phone or whatever)
For example lets say I fully erase it and want the phone back to how it was... fully rooted with all my configured XML files and apps in their same place along with root enabled to be back how it was.. Is this possible? If so, how is it done and what app?
If such a thing is possible from what I mentioned above then will it be a matter of a ZIP file being flashed in TWRP and the whole lot being put in its original state?
Thanks.

Problems with rooting Galaxy S9 (Android 10 Exynos SM-G960F)

Hi, this is My first post here, so be gentle.
My old Oneplus died and I bought a used Samsung Galaxy S9. I tested the phone with an original OS and it worked fine.
Yesterday I decided to root it (there are a few features that need root and I need those features almost daily). I searched for information about the procedure (this wasn't My first root) and found a few threads where this guide was suggested:
How to Root Samsung Galaxy S9 and Galaxy S9 Plus (Exynos)
Do you want to root your Galaxy S9/S9 Plus flagship? Well, you just landed in the right place for the job. This tutorial will help you install TWRP recovery and root Samsung Galaxy S9 and Galaxy S9…
www.thecustomdroid.com
Long story short: I followed those instructions and managed to root my S9. It booted up as it should and everything was working fine. I used Magisk V25.0 and root checker informed that the phone was rooted successfully.
Today I decided to debloat it and after that, I would start to use it as my main phone.
I ran across many threads that suggested using the "ADB + Fastboot" method for debloading the device. At this point, I started to feel uncomfortable because I had some issues with ADB back in the day when I was rooting my Oneplus. I decided to try it and guess what - it didn't work. I still don't know why, but ADB fastboot wasn't able to find my S9. I double-check that everything was as it should be, usb-debugging was ON and my PC did see my phone when connected to the PC via USB cable.
So I gave up on that and decided that maybe I'll just shut those unwanted apps down from the phone's settings (settings ---> apps etc).
At this point, I power off the phone. Just a basic thing to me when sleeping or something like that.
Now, the phone is in bootloop.
I can boot in the TRWP mode and flash magisk/wipe data etc. but nothing seems to help. It won't boot to OS. I've tried to root it again with the instructions above and everything went fine, but bootloop stays. I've wiped cache partition and performed a factory reset - did not help.
Can someone help me...? Is there a way to flash stock OS or somehow get the device work again? My experience with rooting is low, but I've successfully rooted five phones before this. I've experienced a few bootloops before, but those were my mistakes that were fixed with re-flashing magisk or something similar. Now I simply don't know what is the issue. =(
PS. This is a great forum and I've found tons of help from the XDA forum. Thank you to everyone, who has shared his/her information and helped with smartphones in the past! Great society.
Slerba said:
Hi, this is My first post here, so be gentle.
My old Oneplus died and I bought a used Samsung Galaxy S9. I tested the phone with an original OS and it worked fine.
Yesterday I decided to root it (there are a few features that need root and I need those features almost daily). I searched for information about the procedure (this wasn't My first root) and found a few threads where this guide was suggested:
How to Root Samsung Galaxy S9 and Galaxy S9 Plus (Exynos)
Do you want to root your Galaxy S9/S9 Plus flagship? Well, you just landed in the right place for the job. This tutorial will help you install TWRP recovery and root Samsung Galaxy S9 and Galaxy S9…
www.thecustomdroid.com
Long story short: I followed those instructions and managed to root my S9. It booted up as it should and everything was working fine. I used Magisk V25.0 and root checker informed that the phone was rooted successfully.
Today I decided to debloat it and after that, I would start to use it as my main phone.
I ran across many threads that suggested using the "ADB + Fastboot" method for debloading the device. At this point, I started to feel uncomfortable because I had some issues with ADB back in the day when I was rooting my Oneplus. I decided to try it and guess what - it didn't work. I still don't know why, but ADB fastboot wasn't able to find my S9. I double-check that everything was as it should be, usb-debugging was ON and my PC did see my phone when connected to the PC via USB cable.
So I gave up on that and decided that maybe I'll just shut those unwanted apps down from the phone's settings (settings ---> apps etc).
At this point, I power off the phone. Just a basic thing to me when sleeping or something like that.
Now, the phone is in bootloop.
I can boot in the TRWP mode and flash magisk/wipe data etc. but nothing seems to help. It won't boot to OS. I've tried to root it again with the instructions above and everything went fine, but bootloop stays. I've wiped cache partition and performed a factory reset - did not help.
Can someone help me...? Is there a way to flash stock OS or somehow get the device work again? My experience with rooting is low, but I've successfully rooted five phones before this. I've experienced a few bootloops before, but those were my mistakes that were fixed with re-flashing magisk or something similar. Now I simply don't know what is the issue. =(
PS. This is a great forum and I've found tons of help from the XDA forum. Thank you to everyone, who has shared his/her information and helped with smartphones in the past! Great society.
Click to expand...
Click to collapse
I manage to solve this all by my self.
I flashed to stock firmware using frija and odin. After flashing updated all the apps and rebooted couple of times (just to be sure that phone works). After that flashed TWRP with odin, rebooted to recovery and rooted with Magisk (followed step-by-step guide fron xda forum).
Now this works like a dream.

Categories

Resources