Database Info

clean rom

Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?

chibra said:
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
Click to expand...
Click to collapse
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.

Clean ROM is freaking amazing! Seriously just do it I love the mods I can make for it too! Can't wait till I get my volume long press seek mod done! Love this device!
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend

tobdaryl said:
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Click to expand...
Click to collapse
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail

chibra said:
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
Click to expand...
Click to collapse
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.

oryhight sullivan
tobdaryl said:
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
Click to expand...
Click to collapse
i m going to give twrp another shot...

i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop

chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
I'm sorry it is hard to tell since you have chosen an older twrp to install. The current is five versions later and was updated as the kernels were updated to account for changes. The rom you are flashing is based on 10.4.4.25.

chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.

What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!

sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
Wise words. Nobody likes to listen to me so im glad someone else suggested it!

elesbb said:
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
Click to expand...
Click to collapse
Updated the TWRP to the version you mentioned still stuck in boot loop.

sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running

chibra said:
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
Click to expand...
Click to collapse
If you are coming from cm10.1 you will definitely need to do a full wipe as it is non stock. It does say this in the first post. You only do a dalvik and cache wipe when upgrading from the same ROM or in CROMI's case from stock.
Do a data wipe in recovery, make sure you have a titanium backup or equivalent if you want to restore apps.

Success!!!
It worked perfectly fine after i install the back up i did before i flashed my 1st costume rom,
I rooted made a back up at stock/rooted... It just would not install from a full wipe,
it install fine once i flashed that specific backup and dirty flashed then wiped dalvik and cache before booting.

[Q] Katkiss 4.3 - AOSP keyboard has stopped after flashing

Help, I'm slowing going out of my mind. I've been trying to figure out the problem but no joy here so far.
I think I've successfully upgraded to KissKat 4.3 from EOS 118 . Everything loads, asks me to set up tablet etc but I keep getting the " AOSP keyboard has stopped" so I can't actually finish the set up or see if I've actually upgraded properly.
I use TWRP 2.5 version, all the Gapps and version 20 from the 1st page. I've reflashed and rebooted many times changed the keyboard settings but ended up the same message. I also get the google text to speech has stopped as well and I've disable that as well.
Any suggestions would be appreciated. :good:

I am pretty sure there is an issue with the GAPPS not being loaded properly. Boot to recovery, wipe cache & davilk, flash GAPPS then wipe caches again. It should boot fine.
If that does not work, try downloading the GAPPS from the first post again. Using any other GAPPS could cause issues.

frederuco said:
I am pretty sure there is an issue with the GAPPS not being loaded properly. Boot to recovery, wipe cache & davilk, flash GAPPS then wipe caches again. It should boot fine.
If that does not work, try downloading the GAPPS from the first post again. Using any other GAPPS could cause issues.
Click to expand...
Click to collapse
Hi frederuco, I actually followed your guide but I'll try the gaps once more. If that doesn't work then I'll try ver 19.

frederuco said:
I am pretty sure there is an issue with the GAPPS not being loaded properly. Boot to recovery, wipe cache & davilk, flash GAPPS then wipe caches again. It should boot fine.
If that does not work, try downloading the GAPPS from the first post again. Using any other GAPPS could cause issues.
Click to expand...
Click to collapse
GMTN said:
Hi frederuco, I actually followed your guide but I'll try the gaps once more. If that doesn't work then I'll try ver 19.
Click to expand...
Click to collapse
LOL. I can tell you I've done that 4 different times with 4 different download all from the 1st page but it worked on this 4th and I'm not sure why.
Now to see tomorrow if this ROM lives up to all the troubles ( 3 hours worth ) and praise . Thanks for your guides by the way.

Glad it is sorted. I hope you find it worth your time.

[Q] Urgent CM 12.1 Issue!

Hey everyone,
Thank you all for reading this...
Today, I wanted to update my phone from cm-12.1-20150429-NIGHTLY-bacon.zip to cm-12.1-20150502-NIGHTLY-bacon.zip and after optimizing all 199 applications the lock screen appeared and everything seemed fine. However a second later, a pop-up appeared delivering the crash of the google play services. After pressing on "ok" (the only option), the phone switched off and began optimizing the apps again and again, showing the boot sequence in-between. After a while, I tried to install the update again through TWRP and I failed again. Then I tried to restore my backup from the 19th April I had probably made with Nandroid Backup (not exactly sure) and I failed again. Now I have turned off my phone entirely so that it won´t get too hot.
Does anybody know how to fix this issue (preferably without wiping)? And do you think, should I stay with the nightlies or switch to Cyanogen OS 12 (how?)
Best regards from the android newbie,
George (ambach10)

Try reflashing slim's gapps package.
Edit: Link to thread: http://forum.xda-developers.com/oneplus-one/themes-apps/gapps-modified-slim-gapps-calkulin-t3082242

Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.

ambach10 said:
Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.
Click to expand...
Click to collapse
Follow this steps to first turn on your phone https://forums.oneplus.net/threads/guide-how-to-revert-back-to-cm11s-from-oxygen-guide.290605/
It's CM11S.
Easy way to revert back.

ambach10 said:
Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.
Click to expand...
Click to collapse
I've had this issue before. To fix it, I used these gapps, did a full wipe, then flashed everything all over again and it was working without any problems.
Also, I ended up just switching over to COS12 and am still running that. If you want, you can get that here.

ambach10 said:
Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.
Click to expand...
Click to collapse
Also, make sure you are running latest version of TWRP recovery (or whatever recovery you are using)... there are compression incompatibilities with some of the older versions.

Thanks everybody!
Thank you all for helping me out:
@frieked I have twrp v2.8.5.1. Is that ok and if not how can i update that?
@The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
@Mr hOaX does it also work for cm12.1 nightlies or only for oxygenos?

ambach10 said:
Thank you all for helping me out:
@frieked I have twrp v2.8.5.1. Is that ok and if not how can i update that?
@The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
@Mr hOaX does it also work for cm12.1 nightlies or only for oxygenos?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2766186 Here is the TWRP thread 2.8.6.0 is the latest. You can update using the TWRP Manager app available on the play store.

ambach10 said:
@The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
Click to expand...
Click to collapse
I wiped everything other than Internal Storage, flashed the rom, flashed the gapps, and then rebooted and it booted just fine.

ambach10 said:
Thank you all for helping me out:
frieked I have twrp v2.8.5.1. Is that ok and if not how can i update that?
The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
Mr hOaX does it also work for cm12.1 nightlies or only for oxygenos?
Click to expand...
Click to collapse
It works for all lollipop based ROMs.
I hope now your device is working fine.
Sorry for replying late.

Cyanogen Mod 6.0 for OPPO R7 PLUS

I apologize if this is posted, but we now have an official build of Marshmallow for our Oppo r7 Plus (F) Variant. link attachedhttp://download.cyanogenmod.org/?type=nightly&device=r7plus

Excellent! I am going to test it right now and will report!!!!
Update: I was on ColorOS, flashed cm13 recovery and done factory reset, formatting cache is taking around 8 minutes, is that normal?
Flashing ARM64 opengapps for 6.0 end up with error: E:Installation error in /sideload/package.zip (Status 255) - seems like recovery problem as many people report this issue. I only dont know if TWRP will work with CM13 rom

Personally I'm using a 12.1 recovery at the moment. The 13.0 recovery is still WIP AFAIK.
Gesendet von meinem R7plusf mit Tapatalk

Ok, will try cm12.1 recovery, what about gapps? Which one to use? Btw I have done factory reset again, flashed cm13 rom only, phone rebooted and loading apps (total of 87 I think), then done reboot, then only showing blue android logo for very long time, like 10 minutes followed with another "starting apps" screen with 21 left or so, now another reboot with blue android logo. Is this normal for MM roms? Still not finished.
EDIT: after another 5 minutes same screen appears with saying starting android... 21 apps left, blue android logo when done - seems to be as bootloop as it is going nowhere from here.
CM13 rom flashed fine over TWRP, flashing gaaps now seems to be alright as well (open_gapps-arm64-6.0-mini-20151218).

Very exited, good job

so far I am getting the boot-loop also. will wait to here what Nexus5-32GB will post (if any success with the cyanogen recovery) before reverting back

Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...

Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.

Nexus5-32GB said:
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Click to expand...
Click to collapse
check out my post after this (well before now)

coled3 said:
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Click to expand...
Click to collapse
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it

Nexus5-32GB said:
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Click to expand...
Click to collapse
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone

coled3 said:
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
Click to expand...
Click to collapse
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.

Nexus5-32GB said:
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Click to expand...
Click to collapse
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.

coled3 said:
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
Click to expand...
Click to collapse
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE

coled3 said:
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
Click to expand...
Click to collapse
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..

Nexus5-32GB said:
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Click to expand...
Click to collapse
Well, I took my 12.1 installation without any wipe, went to CM recovery from 12.1, installed my (self compiled at that time) build + opengapps (it's important to install those before booting M for the first time), booted, done. I don't have any /system mods though.
I guess I'll try the nightly and see what happens there. Did anybody of you get a logcat of the failed boot attempts?
Gesendet von meinem R7plusf mit Tapatalk

unni84kollam said:
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Click to expand...
Click to collapse
Just follow this quide with flashing twrp, only instead of twrp flash the stock recovery image. http://forum.xda-developers.com/showpost.php?p=63189590&postcount=5 Sorry, there is only boot command, you should type "fastboot flash recovery stock.recovery.img" - when "stock.recovery.img" is a filename of your stock recovery downloaded on your computer.
No need for wipe when installing recovery. I recon to install stock recovery and then install stock ColorOS from it, let it boot, install twrp later and do what you want then.

Looks like it's broken for everyone. I tried multiple recoverys, full wipes including /system and no joy. Guess we'll just have to wait!

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.