Database Info

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?

Xposed, BusyBox and AdAway not installed with SuperMan ROM

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.

[HELP] Bass Loss After Uninstalling Viper4Android

Hello,
I have a rooted Samsung J2 2016. I thought of getting Viper4Android and when I tried to install the drivers it just said drivers installed reboot your phone. I rebooted it 2 times but still it said driver 0.0.0.0 and would ask for permission for updating drivers again. Fed up of this I went to Link2SD app and uninstalled the app. As I had flashed the zip file for Viper, it erased the sound drivers(I think) and I couldnt get any audio through the ear phones so I decided to do a factory reset of the phone by flashing the latest firmware update(This usually removes all apps, TWRP and root from my phone). After I did the factory reset I noticed that all the apps that I had before were still thereconfused I ignored it and plugged in my headphones only to find a complete loss in bass. I tried to tweak the inbuilt equalizer but nothing came out of it. After restarting, bass would enable for a few seconds and then it would disable again. I dont know what to do now. How can I get back my deleted drivers(if they got deleted)?
P.S. I had taken a complete backup but it got erased from the SD card after I formatted it as portable storage( I had it enabled for adoptable storage through root essentials. This might be the reason why the phone didnt factory reset) :crying:
Sorry for the long post. Im a beginner at this. Any help would be appreciated. Thank you
Edit- I tried different earphones and different music players but no success

darshan1504 said:
Hello,
I have a rooted Samsung J2 2016. I thought of getting Viper4Android and when I tried to install the drivers it just said drivers installed reboot your phone. I rebooted it 2 times but still it said driver 0.0.0.0 and would ask for permission for updating drivers again. Fed up of this I went to Link2SD app and uninstalled the app. As I had flashed the zip file for Viper, it erased the sound drivers(I think) and I couldnt get any audio through the ear phones so I decided to do a factory reset of the phone by flashing the latest firmware update(This usually removes all apps, TWRP and root from my phone). After I did the factory reset I noticed that all the apps that I had before were still thereconfused I ignored it and plugged in my headphones only to find a complete loss in bass. I tried to tweak the inbuilt equalizer but nothing came out of it. After restarting, bass would enable for a few seconds and then it would disable again. I dont know what to do now. How can I get back my deleted drivers(if they got deleted)?
P.S. I had taken a complete backup but it got erased from the SD card after I formatted it as portable storage( I had it enabled for adoptable storage through root essentials. This might be the reason why the phone didnt factory reset) :crying:
Sorry for the long post. Im a beginner at this. Any help would be appreciated. Thank you
Edit- I tried different earphones and different music players but no success
Click to expand...
Click to collapse
You probably needed to make sure you had SELinux set to permissive mode, then V4A would probably install the driver and reboot correctly without having to do it again.
You have 2 options:
1) reflash your stock firmware or your custom ROM, whichever one you're using. This will replace what was removed when you flashed V4A zip.
Or
2) enable permissive mode and try V4A again.
Or if you'd like, you can flash your stock or custom ROM just to get things back to a clean start and then try installing V4A again in permissive mode and see if it works right this time.
By the way, when flashing with Odin, it doesn't erase user data unless what you're flashing includes an upgraded/downgraded bootloader. When flashing exactly what you had, it leaves your data intact.
This time, when you flash stock firmware via Odin, boot the device to recovery and factory reset from within recovery, this will wipe user data, then connect to Odin and flash firmware. This should return everything to like it came out of the box.
By the way, in android, the term "factory reset" does not mean flashing stock firmware, that's called "factory restore".
In android, the term factory reset is something completely different, in android, it means wiping user data and leaving only the stock software.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
You probably needed to make sure you had SELinux set to permissive mode, then V4A would probably install the driver and reboot correctly without having to do it again.
You have 2 options:
1) reflash your stock firmware or your custom ROM, whichever one you're using. This will replace what was removed when you flashed V4A zip.
Or
2) enable permissive mode and try V4A again.
Or if you'd like, you can flash your stock or custom ROM just to get things back to a clean start and then try installing V4A again in permissive mode and see if it works right this time.
By the way, when flashing with Odin, it doesn't erase user data unless what you're flashing includes an upgraded/downgraded bootloader. When flashing exactly what you had, it leaves your data intact.
This time, when you flash stock firmware via Odin, boot the device to recovery and factory reset from within recovery, this will wipe user data, then connect to Odin and flash firmware. This should return everything to like it came out of the box.
By the way, in android, the term "factory reset" does not mean flashing stock firmware, that's called "factory restore".
In android, the term factory reset is something completely different, in android, it means wiping user data and leaving only the stock software.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Thank you for replying. The problem is that I am running the stock touchwiz samsung ROM so SELinuxModeChanger doesn't work for me. I would like to go with the second option but I can't find any other method to make it permissive. Can you please help me with this? I dont want to do a factory reset cause talking the phone back to how it is will be a real pain and time consuming. Will just flashing the Viper file again do the job in any way?

Droidriven said:
You probably needed to make sure you had SELinux set to permissive mode, then V4A would probably install the driver and reboot correctly without having to do it again.
You have 2 options:
1) reflash your stock firmware or your custom ROM, whichever one you're using. This will replace what was removed when you flashed V4A zip.
Or
2) enable permissive mode and try V4A again.
Or if you'd like, you can flash your stock or custom ROM just to get things back to a clean start and then try installing V4A again in permissive mode and see if it works right this time.
By the way, when flashing with Odin, it doesn't erase user data unless what you're flashing includes an upgraded/downgraded bootloader. When flashing exactly what you had, it leaves your data intact.
This time, when you flash stock firmware via Odin, boot the device to recovery and factory reset from within recovery, this will wipe user data, then connect to Odin and flash firmware. This should return everything to like it came out of the box.
By the way, in android, the term "factory reset" does not mean flashing stock firmware, that's called "factory restore".
In android, the term factory reset is something completely different, in android, it means wiping user data and leaving only the stock software.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Also sir I found an old complete titanium backup on my laptop. So can it have the original drivers? If yes can I restore them using titanium and how?
I am sorry for asking so many questions but listening to music is what I do most of the times and I am feeling guilty for screwing up something that I like the most and that I can not restore it :crying:

darshan1504 said:
Also sir I found an old complete titanium backup on my laptop. So can it have the original drivers? If yes can I restore them using titanium and how?
I am sorry for asking so many questions but listening to music is what I do most of the times and I am feeling guilty for screwing up something that I like the most and that I can not restore it :crying:
Click to expand...
Click to collapse
What you need wouldn't be in a Titanium Backup file unless you backed up system apps and their data.
If you had a TWRP backup from before you installed V4A then you could use that. Otherwise than that, you'll have to flash stock firmware or at least manually reinstall the stock sound app and it's resources.
Best option to be sure you fix it without having to dig through anything is to flash stock firmware and start over and do it correctly the next time.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
What you need wouldn't be in a Titanium Backup file unless you backed up system apps and their data.
If you had a TWRP backup from before you installed V4A then you could use that. Otherwise than that, you'll have to flash stock firmware or at least manually reinstall the stock sound app and it's resources.
Best option to be sure you fix it without having to dig through anything is to flash stock firmware and start over and do it correctly the next time.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
The titanium backup is a complete system backup. I had chosen the backup all apps and system data option in Titanium and when I went through the backup files, I found the Sound Alive files in it. Those files were different from the ones which I currently have. So this is what I have in the end. If this is useful then fine. Otherwise there's no other option left I guess

darshan1504 said:
The titanium backup is a complete system backup. I had chosen the backup all apps and system data option in Titanium and when I went through the backup files, I found the Sound Alive files in it. Those files were different from the ones which I currently have. So this is what I have in the end. If this is useful then fine. Otherwise there's no other option left I guess
Click to expand...
Click to collapse
No, it's not a complete system backup because Titanium Backup can't do a complete system backup, the only part of system it can backup is system apps and their app data, it doesn't backup anything else from system. TWRP can make a complete system backup but Titanium Backup can't.
If you backed up the system apps themselves then yes, you can restore them but I wouldn't restore any of the app data that goes with those system apps.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
No, it's not a complete system backup because Titanium Backup can't do a complete system backup, the only part of system it can backup is system apps and their app data, it doesn't backup anything else from system. TWRP can make a complete system backup but Titanium Backup can't.
If you backed up the system apps themselves then yes, you can restore them but I wouldn't restore any of the app data that goes with those system apps.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I did a factory reset through TWRP and flashed it again. That did the trick. Thank you for all the help

Black Screen Blue LED

I just unlocked my boootloader today after waiting the 14 days. First thing I did was install twrp recovery, had no problem there. Then I downloaded unofficial lineage os 14 rom, and the newest open gapps.
I was able to fastboot boot into twrp recovery, I then wiped dalvik, system, data, and cache. then proceeded to install lineage os rom, no problem, when I tried to install gapps, it just hung on detecting device and rom. which I had to reboot. then it came up to black screen with blue led. again I rebooted into twrp recovery, wiped again, and this time just installed lineage os rom, and reboot,same thing black screen with blue led. did I miss a step somewhere?

If you were on stock mm or below s244 stock then it's normal to see this..
Sent from my Lenovo P2 using Tapatalk

FireLord said:
If you were on stock mm or below s244 stock then it's normal to see this..
Click to expand...
Click to collapse
+1
Install s244 firmware and then install los.

In trying to fix my own problem I may have screwed it up more. I changed the file system of the Systema nd Data partitions. I changed it to EXT4, however that did not help. I would like to change them back to whatever they were before, but I dont know what they were before, can anyone help me?

actionxp said:
In trying to fix my own problem I may have screwed it up more. I changed the file system of the Systema nd Data partitions. I changed it to EXT4, however that did not help. I would like to change them back to whatever they were before, but I dont know what they were before, can anyone help me?
Click to expand...
Click to collapse
Stock is f2fs, if I'm not wrong

I have this same issue but it solved , i change my data partition to ext4 and also changed another partition to ext4 i didnot remember which partition is that, i think it is system partition (not sure)

actionxp said:
In trying to fix my own problem I may have screwed it up more. I changed the file system of the Systema nd Data partitions. I changed it to EXT4, however that did not help. I would like to change them back to whatever they were before, but I dont know what they were before, can anyone help me?
Click to expand...
Click to collapse
Don't messup with system partition plax..

I had the same issue. Try an other Gapps pack. I picked a smaler one and it worked.
Yes it was that easy

So i installed the S244 Firmware, installed twrp and even got stock rom+magisk root to work. I passed safetynet test. But i can't flash custom roms+gapps. It freezes in twrp.
I already tried alls opengapps versions, from pico until micro. None of them worked. My system partition is ext4, same as data.
My twrp version is 3.1.1-1

Stuck on boot after trying to install original play store as system app through Lucky Patcher

Is there a way to fix this, I got twrp and root access still, I just can't boot into system? If not, is there a way to backup full app data via twrp since I still have root access?
I tried flashing gapps pico and nano but both came out with error as no sufficient space on system partition.

Try flashing your OOS zip in recovery and see if that fixes it.

@soka said:
Try flashing your OOS zip in recovery and see if that fixes it.
Click to expand...
Click to collapse
Yeah that's exactly what I've done to fix it couple days ago, thanks anyways