Xposed, BusyBox and AdAway not installed with SuperMan ROM - Samsung Galaxy S7 Questions and Answers

I selected all of these things to be installed with the SuperMan ROM, But they weren't installed when I got to the home screen after installing the ROM, I know it worked because I have edge on a regular S7. help please. Also sorry for the amount of things I have posted if you have seen any.

Spooky11 said:
I selected all of these things to be installed with the SuperMan ROM, But they weren't installed when I got to the home screen after installing the ROM, I know it worked because I have edge on a regular S7. help please. Also sorry for the amount of things I have posted if you have seen any.
Click to expand...
Click to collapse
Hi
did you try to re flash them again from aroma , no wipe?

MAX 404 said:
Hi
did you try to re flash them again from aroma , no wipe?
Click to expand...
Click to collapse
No I haven't tried that, but I am worried, as I went and installed Xposed, I feel as if I should back up and wipe but I can't do either of those things it always says it fails through TWRP.

Spooky11 said:
No I haven't tried that, but I am worried, as I went and installed Xposed, I feel as if I should back up and wipe but I can't do either of those things it always says it fails through TWRP.
Click to expand...
Click to collapse
Hi mate
1 what errors you get and when , flashing xposed , what xposed file did you use?
2 TWRP is working ok? can you flash with it, did you wipe data during its installation?

1 of these 2 messages appear
1) failed to mount storage (appeared while wiping once and anotherwhilst installing rom.
2) /data failed (something) along these lines while wiping device
I wasn't ableto wipe device it wont let me no matter what.
Even tried when installed stock rom through smartswitch and still had all my stuff.

TWRP works fine and I will check what file I used when I get home in a few hours.

Related

I have a custom rom, no Gapps, no root. please help

So my cousin had the this tablet she hadn't us for a while and she asked to to fix it up. Root it put some apps on it blah blah blah. So i rooted it using this: http://forum.xda-developers.com/showthread.php?t=1681155/
Everything was fine and it went smoothly, I had root access, TWRP recovery that it came with and it was working fine.
I wanted to put a ROM on it for my cousin to match her phone so I found this: http://forum.xda-developers.com/showthread.php?t=2584265
So, I flashed the Rom and it was fine. Then I flashed the Gapps and it said that the system partion didn't have enough space.
Here is where I screwed up (I think). TWRP said that I lost root access and i had to fix it BUT i had to swipe a bar at the bottom to fix it. My dumbass pressed the button in the middle of the screen which was to ignore it. I didn't see what i was doing and i messed up
So I lost root or something and when i turn on the device and try to boot into recovery by holding the Power + Vol Down keys it does not work!
Now I have a tablet with android 4.4.3, no Gapps, no root, no recovery. I have tried to factory reset it but the one in settings do not work.
I'm stuck and I need help from someone smarter. Thank you for anything.
Id start again, sounds like something in recovery got messed up if it thinks the system partition is not big enough for gapps
Flash TWRP with Easyflasher
http://forum.xda-developers.com/showthread.php?t=1688012
Download ROM & Gapps to MicroSD Card
I suggest KatKiss #29 & Gapps from this link
http://forum.xda-developers.com/showthread.php?t=2592890
Factory reset & Wipe everything except External Storage from TWRP
Flash ROM
Flash Gapps
Wipe Cache & Dalvik Cache
Reboot
Nothing more nothing less is needed, so if it doesn't work by doing the above, there are other problems
ok so i installed the drivers it easyflasher was asking for and now it asks whether the device is SBK1 or SBK2, how do i find out whether the device is B70 or above... I feel dumb again... It also asks if its in APX mode... i need help again
ok i figured out the easyflasher and i get the recovery but, when im done flashing all the files and boot the device it says that i have to repair root, like before and even if i say to do so i lose the recovery every time meaning i have to go and put the recovery back onto it and do everything again.....
alrighty so ive got the recovery to stick, and i got the KitKatKiss rom which is actually really nice, however i don't have root, i keep trying to flash the supersu file but it does not work. thanks for everything already. it would be nice to have it rooted.......
RoughRunner said:
alrighty so ive got the recovery to stick, and i got the KitKatKiss rom which is actually really nice, however i don't have root, i keep trying to flash the supersu file but it does not work. thanks for everything already. it would be nice to have it rooted.......
Click to expand...
Click to collapse
KatKiss is already rooted by default, you should not flash an additionnal supersu zip.
Just Flash the rom then gapps from the KatKiss thread
wipe cache + dalvik-cache
then reboot.
If you're coming from another rom version, a full wipe / factory reset is recommended before flashing too.
RoughRunner said:
alrighty so ive got the recovery to stick, and i got the KitKatKiss rom which is actually really nice, however i don't have root, i keep trying to flash the supersu file but it does not work. thanks for everything already. it would be nice to have it rooted.......
Click to expand...
Click to collapse
QUOTE:
Nothing more nothing less is needed, so if it doesn't work by doing the above, there are other problems
--
As Tim says, and as I said, if you had just followed my instructions and not tried adding your own section of the process, you would have had no problems
timduru said:
KatKiss is already rooted by default, you should not flash an additionnal supersu zip.
Just Flash the rom then gapps from the KatKiss thread
wipe cache + dalvik-cache
then reboot.
If you're coming from another rom version, a full wipe / factory reset is recommended before flashing too.
Click to expand...
Click to collapse
ok thanks theres the problem all fixed thanks

[Q] TWRP 2.8.5.0 mount cache error

GALAXY NOTE 4 EDGE ...installed twrp latest version,just like in the op in the development dection says to do...everything went well really..but once i flashed the twrp tar file via odin,,and made my first back up of stock system,in red letters it read cannot mount cache the back up says finished sucssefully..but i erased it..flashed the super su lastest zip file,and this time i checked cache,boot,system,data to back up to see if would finish sucseefully,and i wanted a backup that included being rooted..it did not work,failed this time..so this time i unchecked backing up cache and it worked but idk if it will restore sucssfully..anyone know whats wroung with my recovery??
lucky_515 said:
GALAXY NOTE 4 EDGE ...installed twrp latest version,just like in the op in the development dection says to do...everything went well really..but once i flashed the twrp tar file via odin,,and made my first back up of stock system,in red letters it read cannot mount cache the back up says finished sucssefully..but i erased it..flashed the super su lastest zip file,and this time i checked cache,boot,system,data to back up to see if would finish sucseefully,and i wanted a backup that included being rooted..it did not work,failed this time..so this time i unchecked backing up cache and it worked but idk if it will restore sucssfully..anyone know whats wroung with my recovery??
Click to expand...
Click to collapse
Did you try wiping the caches from TWRP then reboot to recovery? I have had the same trouble a couple times with this phone with TWRP and wiping fixed it both times
THANKX
belveder69 said:
did you try wiping the caches from twrp then reboot to recovery? I have had the same trouble a couple times with this phone with twrp and wiping fixed it both times
Click to expand...
Click to collapse
.................ive done switched to cwm..waas developed for this phone..works flawless...but ive allways been a ywrp user..so when i do go back to it i will do what you said
belveder69 said:
Did you try wiping the caches from TWRP then reboot to recovery? I have had the same trouble a couple times with this phone with TWRP and wiping fixed it both times
Click to expand...
Click to collapse
Thanks buddy, I had this problem and you just saved me !
JF-GINO said:
Thanks buddy, I had this problem and you just saved me !
Click to expand...
Click to collapse
Anytime, glad I could help

Blu Pure XL Help

Hello, i rooted my phone today using the http://forum.xda-developers.com/showthread.php?t=3269447 post.
After i did this i tried installing the xposed framework. I downloaded a bunch of different ones and they didn't work so i pressed wipe cache/dalvik and then when i rebooted it, it just shows the first boot screen, just the white one. And it just stays there.
I can still enter recovery and boot loader. Can someone please help me with this?
do you have twrp 2.8 or 3 installed?
3 has issues with wipes and partitions... did you let it finish or did you stop it in middle of wipe (3.0 takes FOREVER, and if you stop it, it corrupts partitions)
so 1st step is install twrp 2.8 if you are using 3+... use this one:
http://forum.xda-developers.com/pure-xl/development/twrp-twrp-blu-pure-xl-allview-x2-xtreme-t3269596
then load this nandroid:
http://forum.xda-developers.com/pure-xl/general/rom-blu-pure-xl-stock-rom-t3382722
if that doesnt work...
http://forum.xda-developers.com/pure-xl/help/guide-unbrick-softbricked-blu-pure-xl-t3371981
sp flash is the hardcore fix it no matter what factory new route... read THE WHOLE thread if the BLU nandroid doen't fix it for you...
Also as far as Xposed goes, you'll want the latest SDK 22 version that's ARM64. I don't usually clear cache after I install Xposed, works fine.
@tbirdguy Hey man long time no see. There's a flaw in your response... Lol jk
Thanks for the help but I fixed it I just flashed the boot recovery and system part of the allure rom. And after that it still didn't work so I flashed the whole rom. Now it works fine
Ashalinia said:
Also as far as Xposed goes, you'll want the latest SDK 22 version that's ARM64. I don't usually clear cache after I install Xposed, works fine.
Click to expand...
Click to collapse
If you don't mind can you please share a link to the download? I've downloaded 9 different Xposed zip files and none of them worked.
This is the one I use.
http://dl-xda.xposed.info/framework/sdk22/arm64/xposed-v86-sdk22-arm64.zip
Ashalinia said:
This is the one I use.
http://dl-xda.xposed.info/framework/sdk22/arm64/xposed-v86-sdk22-arm64.zip
Click to expand...
Click to collapse
Just curious, but, will any of these Xposed modules fix the Sim card detection issue I'm having right now?

new guy thread help for fulmics g3

HI i installed fulmics rom and it did not work , now it will not allow me to install a rom because twrp says "done" almost instantly , how can i delete fulmics. I have 855 international version. THanks
stupify007 said:
HI i installed fulmics rom and it did not work , now it will not allow me to install a rom because twrp says "done" almost instantly , how can i delete fulmics. I have 855 international version. THanks
Click to expand...
Click to collapse
When you boot to TWRP, choose the "Wipe" option, on the next screen, choose "Advanced Wipe", then on the next screen, choose "system" and "data" partitions(do not choose any of the other partitions). Then slide the slider at the bottom to wipe, then tap the home button in TWRP and choose the "Install" option and flash your RIM like you normally would, then after it flashes, wipe cache and Dalvik/ART cache, after it wipes the caches, select reboot and you're done.
Sent from my SCH-I535 using Tapatalk
Didn't Work
hi, that didn't work, it says it has done but then it boots straight back up into fulmics. Any other ideas.
Droidriven said:
When you boot to TWRP, choose the "Wipe" option, on the next screen, choose "Advanced Wipe", then on the next screen, choose "system" and "data" partitions(do not choose any of the other partitions). Then slide the slider at the bottom to wipe, then tap the home button in TWRP and choose the "Install" option and flash your RIM like you normally would, then after it flashes, wipe cache and Dalvik/ART cache, after it wipes the caches, select reboot and you're done.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
hi, that didn't work, it says it has done but then it boots straight back up into fulmics. Any other ideas.
stupify007 said:
hi, that didn't work, it says it has done but then it boots straight back up into fulmics. Any other ideas.
Click to expand...
Click to collapse
There is probably something wrong with your recovery. They flashing an older or newer version of TWRP for your model number, then try flashing a different ROM.
If your recovery was working correctly then the steps to wipe that I told you about should have wiped your system partition, if it had done that properly then you wouldn't have anything to boot to at this point if your new ROM didn't flash. Since you booted to the ROM you tried to wipe then it didn't wipe.
Also, make sure that you still have root before you flash another recovery, use the root checker app, if you don't have root, try flashing SuperSU.zip in TWRP, then try flashing the new ROM.
Droidriven said:
There is probably something wrong with your recovery. They flashing an older or newer version of TWRP for your model number, then try flashing a different ROM.
If your recovery was working correctly then the steps to wipe that I told you about should have wiped your system partition, if it had done that properly then you wouldn't have anything to boot to at this point if your new ROM didn't flash. Since you booted to the ROM you tried to wipe then it didn't wipe.
Also, make sure that you still have root before you flash another recovery, use the root checker app, if you don't have root, try flashing SuperSU.zip in TWRP, then try flashing the new ROM.
Click to expand...
Click to collapse
I never faced this issue before, I had installed roms before and was able to flash a new rom , so could the recovery really be the issue.
stupify007 said:
I never faced this issue before, I had installed roms before and was able to flash a new rom , so could the recovery really be the issue.
Click to expand...
Click to collapse
Just try another recovery and eliminate that possibility, you're not gonna cause any issues with the new recovery unless you use the wrong one.
Sent from my SCH-I535 using Tapatalk
stupify007 said:
I never faced this issue before, I had installed roms before and was able to flash a new rom , so could the recovery really be the issue.
Click to expand...
Click to collapse
Try advanced wipe including everything. then flash stock rom or any official ones. If you got qualcomm device then use QFIL or Qualcomm Flash Tool
hi i just tried that and it didn't do anything, once again it says done but it didn't do anything, I think it may be the recovery as suggested by Droidriven. I am going to try and flash a different version of TWRP or maybe clockworkmod recovery , I will keep you updated. But do you guys have any suggestions to what may have caused this, Fulmics never worked for me.
Droidriven said:
Just try another recovery and eliminate that possibility, you're not gonna cause any issues with the new recovery unless you use the wrong one.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
[[QUOTING MY POST SO YOU CAN SEE]]
.hi i just tried that and it didn't do anything, once again it says done but it didn't do anything, I think it may be the recovery as suggested by Droidriven. I am going to try and flash a different version of TWRP or maybe clockworkmod recovery , I will keep you updated. But do you guys have any suggestions to what may have caused this, Fulmics never worked for me.
Also guys , i installed TWRP using my OS and now it doesnt work so what is the alternative, I have all pc drivers?
stupify007 said:
Also guys , i installed TWRP using my OS and now it doesnt work so what is the alternative, I have all pc drivers?
Click to expand...
Click to collapse
It sounds to me like you flashed something that was not made for your model number. Find the correct stock firmware and flash that, then start over and find something different for your device this time.
Sent from my SCH-I535 using Tapatalk
quick story. I reinstalled of the same version (2.8) and the problem is still here, I am going to try to install a different version.
Sorry to keep posting but I tried a factory reset using TWRP and it says failed. Could that mean something.
Actually guys, IT says failed underneath for everything but in the console it shows no signs of failure.
SOrry guys for being a noob, this can now be shut down as i have fixed the problem by unchecking simulate actions.
stupify007 said:
SOrry guys for being a noob, this can now be shut down as i have fixed the problem by unchecking simulate actions.
Click to expand...
Click to collapse
How in the world did that setting get changed, it should have been set to what you needed by default.
Sent from my SCH-I535 using Tapatalk

Boot Loop after uninstalling Viper4Android FX

Hey all
I've got a weird problem... I've been having some trouble with Viper4Android FX stopping working (sometimes fixed with a reboot). I installed it through Magisk so decided I'd uninstall it and try flashing it through TWRP. I uninstalled and restarted (back to system) but after taking quite some time booting it failed and rebooted back into TWRP...
I've reflashed the stock boot image, then TWRP. I've tried reflashing Viper4Android Via TWRP, as well as Magisk and the kernel I was using (CleanSlate)…
Yet still it tries to boot into system and the animation continues for a while until it fails and reboots into TWRP...
I'm prefer not to loose all my data because TWRP backups never seem to restore properly. I always get a tarFork(255) error or something like that which I've never managed to solve...
Any ideas what's going on here?
Thanks!
Im using the ViPER4Android FX v1.6.9 (2.3.4.0) by viper520, zhuhang, ahrion & zackptg5. works perfectly for me, installed using magisk. btw what viper u r flashed using twrp ? is it from the magisk module ? or just a regular viper zip ?
Azhar_Fahry said:
Im using the ViPER4Android FX v1.6.9 (2.3.4.0) by viper520, zhuhang, ahrion & zackptg5. works perfectly for me, installed using magisk. btw what viper u r flashed using twrp ? is it from the magisk module ? or just a regular viper zip ?
Click to expand...
Click to collapse
I was using 1.6.9 (2.5.0.5) originally as a magisk module - that was the one I uninstalled which started the problem. I just found that the zip I used in Magisk manager was on my internal storage so I tried instillaing 2.3.4.0 and then 2.5.05 again but unfortunately neither of those has solved the issue - I still can't boot into system
I'm wondering how uninstalling a magisk module could possibly soft-brick a phone
debatingrooster said:
I was using 1.6.9 (2.5.0.5) originally as a magisk module - that was the one I uninstalled which started the problem. I just found that the zip I used in Magisk manager was on my internal storage so I tried instillaing 2.3.4.0 and then 2.5.05 again but unfortunately neither of those has solved the issue - I still can't boot into system
I'm wondering how uninstalling a magisk module could possibly soft-brick a phone
Click to expand...
Click to collapse
Well , thats a bit strange. Have you tried reflashing tthe rom ? if i was u , i'm just gonna wipe my entire system , and fresh installed rom. and start everything from 0 again . if u worried wiping the system, well it's just an app, u can re download it again. + u get fresh install rom and a viper that works perfectly. at least the internall data still safe.
Azhar_Fahry said:
Well , thats a bit strange. Have you tried reflashing tthe rom ? if i was u , i'm just gonna wipe my entire system , and fresh installed rom. and start everything from 0 again . if u worried wiping the system, well it's just an app, u can re download it again. + u get fresh install rom and a viper that works perfectly. at least the internall data still safe.
Click to expand...
Click to collapse
Hmmmm unfortunately that looks like it might be the case.. I'm always reluctant about reflashing roms. That means that system partition gets wiped right? does that mean I end up loosing all my settings and any system apps?
Yes, unfortunately.
But you can restore the phone settings after you first sign in on the phone . Something that says "set up as new" and i forgot the other options. but basically it will restore all the settings (ex: screen time out , wifi password etc) , contacts , and much more. As long as u didn't wipe the Internal Storage , ur photo , music etc is still safe.
Some quick tips , before u messing around with the system (magisk, flashing mods etc) , u can backup the system only. and if something goes wrong , u can just restore the system , not the whole rom.
Azhar_Fahry said:
Yes, unfortunately.
But you can restore the phone settings after you first sign in on the phone . Something that says "set up as new" and i forgot the other options. but basically it will restore all the settings (ex: screen time out , wifi password etc) , contacts , and much more. As long as u didn't wipe the Internal Storage , ur photo , music etc is still safe.
Some quick tips , before u messing around with the system (magisk, flashing mods etc) , u can backup the system only. and if something goes wrong , u can just restore the system , not the whole rom.
Click to expand...
Click to collapse
Thanks! is that like a system image or just backup system partition in TWRP?
debatingrooster said:
Thanks! is that like a system image or just backup system partition in TWRP?
Click to expand...
Click to collapse
Anytime bro.
Yes, the system one. not the system image.
hello my friends.
can i replace viper stock app with version 2.7?
debatingrooster said:
Hey all
I'm prefer not to loose all my data because TWRP backups never seem to restore properly. I always get a tarFork(255) error or something like that which I've never managed to solve...
Any ideas what's going on here?
Click to expand...
Click to collapse
Before you start over again, try flashing OOS. Make sure you use the full system version, not the smaller OTA. You'll have to reroot afterward. You might try uninstalling Magisk before that, by flashing the uninstaller, and seeing if that takes care of things. These options would save you from having to wipe things completely and reinstall everything.
If you flash OOS, it's best to flash it, flash TWRP (use the blu_spark version), reboot to recovery, then flash OOS again, reflash TWRP, then boot into system to see if you're live again. Then, flash Magisk. Flashing the operating system twice is a way to get it on both A and B slots.
There are plenty of detailed instructions here on flashing ROMs.
The 255 error on Nandroid backups is related to multiple user accounts, even if you don't have them. Lots of us have run into this problem. There are a couple of threads on XDA about this. Here's one of them.
https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
Nice Necro bump...

Categories

Resources