Database Develop

Unable to install latest Mokee build properly

Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?

isketch93 said:
Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?
Click to expand...
Click to collapse
I had 70% similar scenario ,but different error. i could boot into mokkee rom but crashed during initial setup ,below were the steps i used to fix it
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
got perfectly working Mokee ROM in MI3

bluethilak said:
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
Click to expand...
Click to collapse
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?

A nandroid backup is to be used in case of failure (and as a backup... but you should have backups anyway so data loss isn't the end of the world) - an app backup is so you can reinstall the apps with settings in Mokee.

isketch93 said:
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?
Click to expand...
Click to collapse
Nandroid backup is nothing but a complete backup of both Rom and Data.It will in a zip format ad gets saved in your internal memory
[Clockworkmod for CWM/TWRP for TWRP recovery]
http://www.makeuseof.com/tag/what-is-a-nandroid-backup-and-how-exactly-does-it-work/
Let me tell you How I handle my backup plans for my device because at least per week i will be changing the ROM.
1) I always save my contacts in Google contacts(So a normal sync will do)
2)I backup all app data and Message data using EasyBackup
:good::good:

I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?

bluethilak said:
...got perfectly working Mokee ROM in MI3
Click to expand...
Click to collapse
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps

isketch93 said:
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps
Click to expand...
Click to collapse
Dude banks gapps latest is for 5.1.0 lolipop ,mokkee is still in 5.0.x try other gapps ,PA or MInimal or get old Bank Gapps of correct lolipop version.:good:
---------- Post added at 10:06 AM ---------- Previous post was at 09:59 AM ----------
isketch93 said:
I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?
Click to expand...
Click to collapse
Clear some space at least 2gb temporarily in you Internal Memory ,Since you will be backing up your App Data,it definitely requires a lot of space .

Boot takes too much time. Also wiped everything. Questions of what to do now...

Ok so i had 5.02 rooted kitkat. Obviously unlocked bootloader. It says 3. And twrp 2.8something...
For the previous months every time i rebooted the phone it took like 10 minutes to boot for some reason. But it worked. It was laggy these days so i thought i will wipe everything and install CM12.1.
So i downloaded the rom and gapps. Then i wiped delvik, cache, system, internal memory and data. I also did format data.
I dont really understand, obviously, how android works. So i had the zips on external card and pressed install on from twrp menu. Then wiped cache and delvik cache. Tried to reboot and says 'Warning no OS found'. I say okay and then it says that it wants to root. I say ok again.
Now the PROBLEM is that it does nothing. It justs stucks on motorola boot logo for too much time. I am not sure if this is because i already had a problem with booting taking too much time or because of what i have wiped. I also tried updating bootloader again. Not sure if this changed anything
Long story short, how do i continue now? Is there a way to really delete everything i have done on the phone, then install fresh twrp and then CM12.1? And how do i fix the booting taking too much time problem...
Any help will be valueable. I just dont get how things work because nowadays there are too many things, kernels, roms, bootloaders, recoveries etc... Can i just flash the CM rom from my computer via usb? I tried something like that by ?sideload? only to get a problem about requiring 1.0.32 version. I tried to download new SDK but again i have 1.0.31 version of adb...
Thanks!
P.S. Yes, i am totally lost. But i have desire to understand...

NUKE1989 said:
Ok so i had 5.02 rooted kitkat. Obviously unlocked bootloader. It says 3. And twrp 2.8something...
For the previous months every time i rebooted the phone it took like 10 minutes to boot for some reason. But it worked. It was laggy these days so i thought i will wipe everything and install CM12.1.
So i downloaded the rom and gapps. Then i wiped delvik, cache, system, internal memory and data. I also did format data.
I dont really understand, obviously, how android works. So i had the zips on external card and pressed install on from twrp menu. Then wiped cache and delvik cache. Tried to reboot and says 'Warning no OS found'. I say okay and then it says that it wants to root. I say ok again.
Now the PROBLEM is that it does nothing. It justs stucks on motorola boot logo for too much time. I am not sure if this is because i already had a problem with booting taking too much time or because of what i have wiped. I also tried updating bootloader again. Not sure if this changed anything
Long story short, how do i continue now? Is there a way to really delete everything i have done on the phone, then install fresh twrp and then CM12.1? And how do i fix the booting taking too much time problem...
Any help will be valueable. I just dont get how things work because nowadays there are too many things, kernels, roms, bootloaders, recoveries etc... Can i just flash the CM rom from my computer via usb? I tried something like that by ?sideload? only to get a problem about requiring 1.0.32 version. I tried to download new SDK but again i have 1.0.31 version of adb...
Thanks!
P.S. Yes, i am totally lost. But i have desire to understand...
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 try to restore to stock

I am trying to do this but i dont have some files like boot.img or logo.bin etc.... Where can i download those? There is a link about mfastboot is not working. I am using linux btw so i guess the fastboot i already have is okay
EDIT: Ok i am obviously stupid. The files are on the zip ROM. Okay i am doing this. Now the question i have is, cant i install CM12.1 using fastboot like this ROM?

Okay and it worked. It booted stock rom and this time it booted in a minute or two (considering it was the first time booting i think its awesome).
Now i have to try CM rom. At least i know how to return the phone back if anything happens. Thank you very very much!

NUKE1989 said:
Okay and it worked. It booted stock rom and this time it booted in a minute or two (considering it was the first time booting i think its awesome).
Now i have to try CM rom. At least i know how to return the phone back if anything happens. Thank you very very much!
Click to expand...
Click to collapse
Glad to help
now just copy the rom you want to install and the gapps, install the latest TWRP, wipe: Cache, Dalvik Cache, Data and System and just flash the zips

Many thanks I managed to install CM12.1. Thought i think i failed to flash most of gapps for some reason i dont really care.
I only have one severe bug. 3G is not working for some reason. So i dont have gsm internet except the slow one...

upgrading to Nougat, trouble replacing old kernel

Apologies for duplicating this post but the original forum was apparently the wrong spot for this.
I need either some pointers or a reference to a how-to, if you please.
My Nexus 6 is currently running Pure Nexus 6.0.1-2060821-official, security patch 8/5/2016 with ElementalX kernel 3.10.40-ElementalX-N6-3-20.
I've updated Pure Nexus before through TWRP and all went well, but those efforts never involved updating the kernel too. I've attempted to flash the new kernel, the rom and the google apps, but the phone goes into a never ending boot effort and it's a tussle getting back to recovery mode as it tends to boot loop. The flashes are preceded by clearing Delvik and cache and cleared again after the flash.
Is the order of flashing off or perhaps not enough clearing of other items such as system? Or is a factory reset needed?
Kind of lost on this one and can't seem to string together enough search terms to find help specific to the problem.
Any help would be appreciated.

The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.

zelendel said:
The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.
Click to expand...
Click to collapse
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?

jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?
Click to expand...
Click to collapse
You are doing a full wipe right? Wiping system and data before flashing?
Also encryption could be an issue. If your device in encrypted or the kernel did not remove the force encryption flag. That could take awhile as well.

jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215
Click to expand...
Click to collapse
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?

Pkt_Lnt said:
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?
Click to expand...
Click to collapse
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.

Needs Nougat bootloader and latest radio--flash in TWRP. This allows flashing N ROMs while will still work with all MM or even 5.1 ROMs
http://batakang.com/ftp/devs/mhous33/shamu/bootloaders/shamu_bootloader_moto-apq8084-72.01.zip
http://batakang.com/ftp/devs/mhous33/shamu/7.1.1/shamu_baseband_D4.01-9625-05.44+FSG-9625-02.115.zip

jlfesslerkc said:
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.
Click to expand...
Click to collapse
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.

Try reverting to stock
Install stock firmware using adb

TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.

jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
Hi... Save your internal storage before processing. Just in case... TWRP 2.8.5.0 is pre nougat and incompatible.

jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
You should really update the bootloader/radio to the latest once you update the TWRP. Updating the bootloader/radio will not affect your internal storage.

Pkt_Lnt said:
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.
Click to expand...
Click to collapse
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?

jlfesslerkc said:
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?
Click to expand...
Click to collapse
yup
Item 1.8 and 1.9 here

Pkt_Lnt said:
yup
Item 1.8 and 1.9 here
Click to expand...
Click to collapse
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?

jlfesslerkc said:
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?
Click to expand...
Click to collapse
That is what Titanium Backup (and Restore) does, yes.

Reverting to MIUI from decrypted LOS/AICP etc

I remember I tried this a few months back flashing EPIC (coming from Resurrection Remix) and was unaware that MIUI would try encrypting. It tried (and failed) to encrypt on first boot and I was forced to wipe the whole data partition. Luckily I had everything backed up and just needed to copy it back, even though it took hours.
Question is, can I flash MIUI (specifically one of the weekly releases) and block it from trying to encrypt? I read that flashing Magisk disables encryption by default, but I just wanted to check first. Also, I have data/cache switched to F2FS, so I'll be flashing the Psychedelic kernel immediately after MIUI for compatibility as AFAIK MIUI doesn't support F2FS.
Is MIUI > Psy > Magisk enough or do I need to flash one of those no-verity/encrypt/lazyflasher zips too? I still have the important stuff backed up but I'd rather not have to take hours copying ~200GB of media back to data if it goes haywire.
Cheers.
EDIT: So I went with MIUI > Psy > no-verity-opt-encrypt-6.0 > Magisk. I got the same 'encryption failed - reset device' message as I did before which mean data must be wiped to proceed. I rebooted into TWRP and formatted data, then flashed the same sequence as before. This time it booted normally and it didn't try to encrypt. I don't know why it tried the first time (forcing me to wipe everything) but the second time it didn't bother. I'm done with my quarterly return to MIUI - back to AICP for me.

gavin19 said:
I remember I tried this a few months back flashing EPIC (coming from Resurrection Remix) and was unaware that MIUI would try encrypting. It tried (and failed) to encrypt on first boot and I was forced to wipe the whole data partition. Luckily I had everything backed up and just needed to copy it back, even though it took hours.
Question is, can I flash MIUI (specifically one of the weekly releases) and block it from trying to encrypt? I read that flashing Magisk disables encryption by default, but I just wanted to check first. Also, I have data/cache switched to F2FS, so I'll be flashing the Psychedelic kernel immediately after MIUI for compatibility as AFAIK MIUI doesn't support F2FS.
Is MIUI > Psy > Magisk enough or do I need to flash one of those no-verity/encrypt/lazyflasher zips too? I still have the important stuff backed up but I'd rather not have to take hours copying ~200GB of media back to data if it goes haywire.
Cheers.
EDIT: So I went with MIUI > Psy > no-verity-opt-encrypt-6.0 > Magisk. I got the same 'encryption failed - reset device' message as I did before which mean data must be wiped to proceed. I rebooted into TWRP and formatted data, then flashed the same sequence as before. This time it booted normally and it didn't try to encrypt. I don't know why it tried the first time (forcing me to wipe everything) but the second time it didn't bother. I'm done with my quarterly return to MIUI - back to AICP for me.
Click to expand...
Click to collapse
Well that sucks, to much work for me, thats why I wont go back to MIUI even tho im curious with all the new updates on MIUI..... Im good with a AICP custom rom

Ultraman666 said:
Well that sucks, to much work for me, thats why I wont go back to MIUI even tho im curious with all the new updates on MIUI..... Im good with a AICP custom rom
Click to expand...
Click to collapse
I just installed epic coming from AICP it wasn't a big deal for me, it's all in the OP

james1089 said:
I just installed epic coming from AICP it wasn't a big deal for me, it's all in the OP
Click to expand...
Click to collapse
AICP to MIUI/Epic is no different than anything else. You just flash it. The challenge comes from trying to keep the unencrypted status when doing so without having to transfer all your media off/onto the phone.

gavin19 said:
AICP to MIUI/Epic is no different than anything else. You just flash it. The challenge comes from trying to keep the unencrypted status when doing so without having to transfer all your media off/onto the phone.
Click to expand...
Click to collapse
Well as far as I know I'm still unencrypted

gavin19 said:
I remember I tried this a few months back flashing EPIC (coming from Resurrection Remix) and was unaware that MIUI would try encrypting. It tried (and failed) to encrypt on first boot and I was forced to wipe the whole data partition. Luckily I had everything backed up and just needed to copy it back, even though it took hours.
Question is, can I flash MIUI (specifically one of the weekly releases) and block it from trying to encrypt? I read that flashing Magisk disables encryption by default, but I just wanted to check first. Also, I have data/cache switched to F2FS, so I'll be flashing the Psychedelic kernel immediately after MIUI for compatibility as AFAIK MIUI doesn't support F2FS.
Is MIUI > Psy > Magisk enough or do I need to flash one of those no-verity/encrypt/lazyflasher zips too? I still have the important stuff backed up but I'd rather not have to take hours copying ~200GB of media back to data if it goes haywire.
Cheers.
EDIT: So I went with MIUI > Psy > no-verity-opt-encrypt-6.0 > Magisk. I got the same 'encryption failed - reset device' message as I did before which mean data must be wiped to proceed. I rebooted into TWRP and formatted data, then flashed the same sequence as before. This time it booted normally and it didn't try to encrypt. I don't know why it tried the first time (forcing me to wipe everything) but the second time it didn't bother. I'm done with my quarterly return to MIUI - back to AICP for me.
Click to expand...
Click to collapse
That's about the same for me will use it for a week then go back to AICP.

james1089 said:
Well as far as I know I'm still unencrypted
Click to expand...
Click to collapse
If you go into Settings > Security and it says 'Encrypt Phone' then you're still unencrypted.

gavin19 said:
If you go into Settings > Security and it says 'Encrypt Phone' then you're still unencrypted.
Click to expand...
Click to collapse
I'm still unencrypted, epic flashed everything I didn't do anything. It flashed dm-verity and SuperSU.

Question A12 having issues flashing updated custom rom - not sure what to do

Okay sorry for coming here with this, but I've searched for a way to resolve this on my own and can't seem to be able to.
I'm using Octavi Rom on my Redmi Note 10 Pro, and I recently tried to do the update from 3.0 to 3.2. I use TWRP custom recovery, and ofc no device decryption, so I had issues wiping dalvik/cache. I already assume I did something wrong because everyone else was able to install fine. My device didn't boot loop but from the first time it loaded, I had issues logging in because my settings crashed, system crashed, my phone is very slow, and I have no idea what to do to fix it. https://hastebin.com/osihiyibal This is the log I get when the settings crashes.
Can someone give advice on what I can do? I can't open device settings *at all*. I can't wipe data or do a factory reset. I would just like some help because my phone is pretty unusable sometimes in this state, and not sure if I can wait for A12 decryption to be a thing. Thanks in advance.

If you are okay with losing everything and just want a clean install and use the device you can try the following. If you already have TWRP installed but are getting the decryption error, Go into TWRP go to Wipe, Format data, Type yes, then click the blue check mark. It should clear the decryption and you can do a fresh install of whatever operating system you want to install.

Thank you so much! You're a life saver. I was able to reinstall the rom with no issues by wiping the data. Everything is working great too. Like having a new phone all over again, but I don't care. So much better than the crashing and slowness. <3 Thank you!