Develop Bugs

[Q] No ROMs taking, keep getting no MD5 message, phone close to bricked.

I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.

gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient

MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?

I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.

theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.

spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?

gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.

theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?

gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).

theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.

No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.

gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.

flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?

[Q] No Network or IMEI number, :-S

Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?

shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!

Gandicela said:
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!
Click to expand...
Click to collapse
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.

shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
Mate, firstly this is the hard way of recovering from "Unknown Baseband" issue. Finally the simple solution was only to download and install an app called SELinux Mode Changer from PlayStore. Then using that app, change SELinux from Enforcing to Permissive resolved everything related to IMEI, EFS, and Unknown Baseband. So hard way I did; i didn't know any better then.
By the way the link is correct. Start from the procedure from the line that says "Installation Instruction [Mobile odin is now have support for NOTE2]"
You must be in download mode (Vol Down, Home, & Power button all pressed together) to flash the Stock ROM using Odin. But where is your status now? If in recovery, can you re-install a ROM? If u r able to reboot back up to OMNI, just install the SELinux app and u will be good to go.
Cheers!

shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!

shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
karlonicolas said:
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
Click to expand...
Click to collapse
Nice, thanks!
For all others that might face "unknown baseband" with 4.3 to 4.4 flashing of ROMS, SELinux Mode Changer app from Playstore will fix that problem. Install the app and set SELinux from Enforcing to Permissive.

i hope your problem is fixed.
i'm not too familiar with CM roms, as i have been using stock since gingerbread. but you have to first do a full wipe before flashing from CM to stock. did you do that? perhaps you can go to recovery, do a full wipe, include Dalvik and Cache. Then go to bootloader and flash your rom.
by the way, my chipset is qualcomm yours may be exynos. if so, then i'm not confident about this solution because i have tried this several times, but only on note 2 LTE.
good luck!

[Q] I need a little guidance... (I'm desperate)

Hello everyone. I'm quite new to this whole fiddling with my S3 thing. I mean, I successfully flashed a previous version of Danvdh's Dandroid ROM a few months ago but was not pleased when it would not pick up ANY GPS satellites even after 20 minutes of waiting to get a fix. Of course I tried everything from tightening screws (none of my screws were loose) to that aGPS patch (for which it gave me the wrong location even after trying what the notes suggest).
Having said that, yesterday, I tried flashing other ROMs (like Beanstalk) in hopes of getting better GPS. Now Beanstalk worked fine and gave me GPS, but with that I then ran into problems mounting and formatting a new SD card. So then I flashed the newest version of Dandroid and successfully mounted the SD card, but it still gave me GPS problems, at which point I was kind of disheartened and decided to give saranhai's StockMOD ROM a try.
I ran into all kinds of problems.
1. I'm sure this isn't the dev's fault, but my CWM version 6.0.3.7 (is that old?) won't recognize any kind of change in my internal SD card since late yesterday. My desktop and ES file explorer both register the same files and folders, but CWM still sees old files like the zip files for Beanstalk and Dandroid which don't appear on my computer??? And it won't see any new files??? What did I do wrong? Therefore, I flashed things from my external SD card from there. (Was that wrong to do?) Also, every time I try to reboot through CWM, it says root access may have been lost and asks if I want to try and fix it. I say no because my SuperSU still works?
2. After FIRST flashing Dandroid 5.1 I noticed Wi-Fi wasn't working. A post from the Dandroid thread said to flash a kernel "or update to the newest bootloaders." I flashed the kernel he provided and found out too late that it was for T999L or something and my phone is T999. I'm kinda surprised my phone didn't brick then. Anyway, I got Wi-Fi, but whenever I tried to turn on mobile data, it said to insert a SIM card?? I'm sure it's because I flashed that wrong kernel. When I go into Settings > About Device it says the Baseband version is unknown and the Kernel version is as follows:
3.0.31-1804024
[email protected]
Sat Oct 5 00:13:48 KST 2013
and the build number: JSS15J.T999UVUEMJC
EDIT: I FOUND OUT MY PHONE WAS ACTUALLY T999L NOT T999. Currently trying to fix things. I'll get back to the thread.
3. So hoping saranhai's StockMOD ROM would give me the fresh start I so desperately needed, I followed his instructions step by step from flashing the right modem FIRST then flashing the ROM, but alas, the same "Insert SIM card...." error still plagued me. You would not believe how sad I got. (I'm still pretty sad.) At that point I tried REALLY hard to familiarize myself with what I was doing, reading the thread carefully, looking through that glossary thread to help me keep up with the techie terms, and searching for instructions on how to get it fixed, but I couldn't find anything and I was stuck.
4. This morning I flashed the Insecure kernel the StockMOD ROM thread provided and I still get the error.
5. I tried to restore from a backup I made last week on CWM, but it kept saying "checking MD5 files" and them giving me an error about not being able to restore.
As you all can see, I probably made a HUGE mess out of my phone and it might come as a huge surprise that I haven't bricked it completely. I'm extremely desperate at this point and I've admitted that I don't know what I'm doing. :crying:
It's come to the point where I just want a stable handset that will give me the services I want (GPS, mobile data, Wi-Fi, etc.) and I'm beginning to think this root lyfe isn't for me. I searched for guides on how to return to stock and unroot, but all the guides are different and I'm so confused and overwhelmed as to what I should do at this point. Please, please, please! A little guidance would be GREATLY appreciated!
Thanks for your time!

First off don't get disheartened. You did demonstrate a genuine attempt to help yourself and try your best on your own. Yes mistakes happen. We all do that. For what its worth, no one is born knowledgeable in these areas. We all learn.
Ok so what do we do next ? Lets start with a clean slate and put that all behind you. Yes your current recovery CWM is indeed dated and that's the reason for some of the issues you have.
Follow these steps.
1. Take UVDMD5 version of Root66 from here. Use ODIN to flash it to your phone. If you need a guide on how to use ODIN, read this thread carefully.
2. Once that Stock firmware has been updated and your phone boots fine, check if you have GPS and all the other features working to your satisfaction. Given your problems with GPS, I strongly recommend taking a GPS fix at this time.
3. Once that's working fine, flash the latest CWM Touch Recovery (version 6.0.4.5 for D2TMO). You can use Rom Manager from Play store.
4. Take a Nandroid before proceeding. When you do, uncheck the generate MD5 and enable Compression.
5. Now its your choice. You could flash Saranhai's Stock Mod or Danvdh's Dandroid. Both are good Roms and its your call. Check the GPS working after you flash Rom of your choice.
If you do choose to go after Saranhai's Rom and get into the Wi-Fi Problems, post here before you try any solutions. With Danvdh's Rom, there are certain steps to enable Root. You can't just flash SuperSU and hope to gain Root.

Perseus71 said:
First off don't get disheartened. You did demonstrate a genuine attempt to help yourself and try your best on your own. Yes mistakes happen. We all do that. For what its worth, no one is born knowledgeable in these areas. We all learn.
Ok so what do we do next ? Lets start with a clean slate and put that all behind you. Yes your current recovery CWM is indeed dated and that's the reason for some of the issues you have.
Follow these steps.
1. Take UVDMD5 version of Root66 from here. Use ODIN to flash it to your phone. If you need a guide on how to use ODIN, read this thread carefully.
2. Once that Stock firmware has been updated and your phone boots fine, check if you have GPS and all the other features working to your satisfaction. Given your problems with GPS, I strongly recommend taking a GPS fix at this time.
3. Once that's working fine, flash the latest CWM Touch Recovery (version 6.0.4.5 for D2TMO). You can use Rom Manager from Play store.
4. Take a Nandroid before proceeding. When you do, uncheck the generate MD5 and enable Compression.
5. Now its your choice. You could flash Saranhai's Stock Mod or Danvdh's Dandroid. Both are good Roms and its your call. Check the GPS working after you flash Rom of your choice.
If you do choose to go after Saranhai's Rom and get into the Wi-Fi Problems, post here before you try any solutions. With Danvdh's Rom, there are certain steps to enable Root. You can't just flash SuperSU and hope to gain Root.
Click to expand...
Click to collapse
Thanks so much for your detailed reply!
After a little bit of browsing the forum, I found that my IMEI seems to be missing and simply flashing the correct modems/kernels/whatever you call them does not fix it. I will go through your instructions and then report the results.
I read on here that sometimes it just happens randomly after flashing 4.3 ROMs? Well I certainly hope I get back my IMEI and hope it's not blacklisted :/ Apparently I can't access signal or data without it.
Thank you again!
EDIT: Does an "Unknown" IMEI mean I've totally lost it?
EDIT 2: Okay now I know God hates me. I downloaded the Root66 file and Odin will NOT let me flash it onto my phone. Keeps giving me aboot (???) errors no matter what port I use! I know I took a risk tinkering with my phone but I don't think I deserve this!
Honestly now I don't want anything to do with rooting and custom ROMs anymore. I think I'm too stupid for this. I think I just want it back to the way it was when I bought it. Could you please help me to do that?
I'm done with this root stuff, I can't do it anymore.
Sorry, I honestly don't mean to come off as whiny or ungrateful, I've just spent two days trying to figure this stuff out and it's getting me VERY tired and VERY irritated.

Oops I think I forgot to mention that you will have to put the phone in Download mode before you plug it in for ODIN. In order to get into Download mode you turn off the phone and press Volume Down AND HOME AND POWER simultaneously. If you are doing it for the first time, it may seem hard. Be patient.
Yes I suspected you to be "Missing IMEI". That's why suggested going to Stock. Your Call & Data problems come from there.
My steps do take you back to Stock.

[Q] Older MD4 NAND backup applied to MK3 or ND8 phone

Question for those of you who may know more than I do.
I have…well had, a Sprint Samsung Galaxy S3 that got a shower over the weekend. The USB port is definitely fried, and who knows what other damage may have occurred, but the phone still turns on and works fine. I decided to buy a used S3 to replace mine rather than try to fix the port not knowing if that was the only problem.
Now my question, my phone was rooted at the L710VPBMD4 OTA level, I have 4.2.2 CM v10.1.2 installed on the phone, and would like to keep it that way till I make sure everything is working the way I had it.
If the new (used) phone I receive has received either the L710VPUCMK3 or L710VPUCND8 OTAs will I have any problems loading my NAND backup and TB backups to recover my phone to the point it was wet?
(luckily the phone still had enough battery power to get these done)
Added: I also used CWM Recovery v6.0.3.0 for My NAND backups, do I have to continue to use this version to recover properly from, or will it work with Philz Recovery?
If there is a problem just straight loading my backups to the phone, is there anything I can do to make it work?
I know there is a root method difference for the L710VPUCMK3 or L710VPUCND8 OTAs, I’m just concerned about being able to recover my backups at the level they are at. Right now I don’t want to have to upgrade CM until I make sure everything is right, even then I will probably only upgrade to 10.2.1, as CM11 doesn’t seem quite ready…at least from what I’ve experienced on other phones/tablets.
Thanks in advance….

n00bhackin said:
Question for those of you who may know more than I do.
I have…well had, a Spring Samsung Galaxy S3 that got a shower over the weekend. The USB port is definitely fried, and who knows what other damage may have occurred, but the phone still turns on and works fine. I decided to buy a used S3 to replace mine rather than try to fix the port not knowing if that was the only problem.
Now my question, my phone was rooted at the L710VPBMD4 OTA level, I have 4.2.2 CM v10.1.2 installed on the phone, and would like to keep it that way till I make sure everything is working the way I had it.
If the new (used) phone I receive has received either the L710VPUCMK3 or L710VPUCND8 OTAs will I have any problems loading my NAND backup and TB backups to recover my phone to the point it was wet?
(luckily the phone still had enough battery power to get these done)
If there is a problem just straight loading my backups to the phone, is there anything I can do to make it work?
I know there is a root method difference for the L710VPUCMK3 or L710VPUCND8 OTAs, I’m just concerned about being able to recover my backups at the level they are at. Right now I don’t want to have to upgrade CM until I make sure everything is right, even then I will probably only upgrade to 10.2.1, as CM11 doesn’t seem quite ready…at least from what I’ve experienced on other phones/tablets.
Thanks in advance….
Click to expand...
Click to collapse
Well.....as long as the bootloader and modem weren't backed up you should be able to restore the CM11 as long as you use the same recovery......that being said you won't be able to restore the stock rom cause i believe the bootloader and modem get backed up with that one. Also it could come with the NJ3 update in which case you won't be able to root at all. I also wan't to add that i have no faith in TB for restoring app data cause that will cause problems with your phone.

6th_Hokage said:
Well.....as long as the bootloader and modem weren't backed up you should be able to restore the CM11 as long as you use the same recovery......that being said you won't be able to restore the stock rom cause i believe the bootloader and modem get backed up with that one. Also it could come with the NJ3 update in which case you won't be able to root at all. I also wan't to add that i have no faith in TB for restoring app data cause that will cause problems with your phone.
Click to expand...
Click to collapse
I will be restoring a CM10.1.2 mod, not CM11, if that makes a difference.
So I will need to use CWM 6.0.3.0, and can not use Philz Recovery. .. Just verifying.
I’m not worried about using my old stock rom backup, I can get a new one with the new phone, my old one never had anything on it, as I loaded CM the day I got the phone new.
How can I tell if the Boot loader/Modem are a part of the NAD backup? The files I have in the NAND are:
boot.img 10,240 KB <--- would this be the boot loader?
cache.ext4.tar 0 KB
cache.ext4.tar.a 54, 238 KB
data.ext4.tar 0 KB
data.ext4.tar.a 976,563 KB
data.ext4.tar.b 976,569 KB
data.ext4.tar.c 728,600 KB
nandroid.md5 1 KB
recovery.img 10,240 KB
system.ext4.tar 0 KB
system.ext4.tar.a 350,522 KB
Is NJ3 a Sprint released OTA? It was not in their list, ND8 was listed as current. The phone I’m getting should be a sprint phone, but I won’t know what level the phone is at till it gets here Wednesday.
As for TB restore, I shouldn't have to since my NAND is current, but so far I’ve been lucky with TB.

@bilgerryan do you have any advise for this person i have reached the limit of the help i can give with the experience that i have on this version of the phone....

Thanks for your help, I'm trying to get as much information as I can on this before I get my "new" phone and brick it with what I am trying to do.
Once I have the phone it may not be an issue if it hasn't received OTAs, the best scenario is that is at the MD4 level, but I doubt I will be that lucky. I expect it has been updated to MK3 or ND8, which is why I am asking what I'm asking.
OK, my guess is that boot.img is not the boot loader, as I see that file in CM ROM zip files, and CM ROMs do not contain a boot loader, can anyone confirm that this is correct?

n00bhackin said:
Thanks for your help, I'm trying to get as much information as I can on this before I get my "new" phone and brick it with what I am trying to do.
Once I have the phone it may not be an issue if it hasn't received OTAs, the best scenario is that is at the MD4 level, but I doubt I will be that lucky. I expect it has been updated to MK3 or ND8, which is why I am asking what I'm asking.
OK, my guess is that boot.img is not the boot loader, as I see that file in CM ROM zip files, and CM ROMs do not contain a boot loader, can anyone confirm that this is correct?
Click to expand...
Click to collapse
no problem and if anyone can help you more then me it's Ryan since he still has the Sph-L710 and he's a Developer.....while i have the newer Sph-L710T and im on Boost Mobile

Few follow-up questions:
1) Will CWM 6.0.3.0 work fine with the phone has been updated to MK3 or ND8?
2) If not, can I restore a backup made on CWM 6.0.3.0 with CWM 6.0.4.5? (seems to be the latest version)
3) If the “new” phone is on MK3 or ND8 can you still use a previous android version, like 4.2.2? (This is basically what I will be doing, but using a NAND backup to restore the phone)
4) Will a NAND backup contain the boot loader or modem? How can I tell if mine does?
This would prevent me from being able to recover with my NADN backup, from what 6th_Hokage said, and from what other information I’ve read on this. It would brick.
Still hoping I can using my NAND backup from MD4 phone to recover to a phone that may be at a higher level. So far from all the reading I am doing on this I should be able to, as long as I don’t try to flash the firmware back to MD4. Which isn’t an issue if my NAND will work, if it won’t then I’ll just be forced to rebuild from scratch, which I am REALLY hoping to avoid.

Ok, after reading as much as I could last night…my head hurts…
But it looks like I can do what I hope to do, if the planets and stars align.
Best case scenario, the “new” phone I get is at MD4 and is the SPH-710 variant. (doubt I can get that lucky)
If the phone is the SPH-710T – It goes back and I’m out of luck, as it’s a crap shoot buying a used phone when they don’t make a distinction between the 710 and 710T (Thanks 6th_Hokage, when you mentioned the 710T and on Boost Mobile, I figured it was a variant for them and VM, not for sprint, I’ve found out it is a sprint branded phone too)
If the phone is a 710 variant and even if it has been upgraded to MK3 or ND8 I should still be able to use my NAND backup to recover my old ROM (4.2.2 CM v10.1.2).
I should be able to use either CWM 6.0.3.0 or CWM 6.0.4.5 on the new phone to restore my NAND that was made with CWM 6.0.3.0… even if the phone is at MK3 or ND8.
My NAND should not contain the boot loader or modem, but I’m not sure how to tell. If it does, I’ll need to figure out how to make a NAND that exclude them. How can I tell if my NAND contains these? (because if it does and I restore, it will brick, if on MK3 or ND8)
If anyone can provide some insight on this that would be great.
Thanks,

Next on the list of my research findings.
I have found conflicting information, in one post I found that I would get an asset error if I try to install CM 10.1.2 (or I think any 10.x version) when on either MK3 or ND8. Then in another port I read that there should not be a problem installing any version of CM when on MK3 or ND8.
Can anyone confirm either post? Can CM10x work on MK3/ND8? Or will an assert error get thrown?
If an assert error is thrown only during install, I wonder if I bypass this by using a NAND restore like I plan, since the “install” of CM has already occurred, and I am just restoring a backup.
You may ask yourself why I am going through all this to recover an older version of CM. Well my phone was completely stable where it was, it did everything I needed to without error. While I’ve considered upgrading, that always seems to introduce issues, and I needed a smooth working phone over some of the stated benefits of CM11.

n00bhackin said:
My phone was rooted at the L710VPBMD4 OTA level,
I have 4.2.2 CM v10.1.2 installed on the phone
and would like to keep it that way till I make sure everything is working the way I had it.
If the new (used) phone I receive
has either the
L710VPUCMK3
or
L710VPUCND8 OTAs
will I have any problems loading my NAND backup and TB backups to recover my phone to the point it was wet?
(luckily the phone still had enough battery power to get these done)
Thanks in advance….
Click to expand...
Click to collapse
Yes, I was able to restore the NAND backup with my S3.
I had a NAND backup of
CyanogenMod 10.2.1
that was on MD4 before
on my Sprint S3 SPH-L710.
I was able to restore
the NAND backup of
CyanogenMod 10.2.1
that was on a MD4 modem before
on my S3
with the new
ND8 modem update
using
TWRP 2.8.1.0

Great to hear it will work, now just have to hope they didn't send me a 710T variant...Will know tomorrow.
Hopefully it will work the same with CWM, as that is what my backup was made by, I've read that CWM and TWRP backups are not compatible.

n00bhackin said:
I've read that CWM and TWRP backups are not compatible.
Click to expand...
Click to collapse
Correct, not to mention TWRP doesn't mount or storage correctly anyway. I suggest using Philz, it's a zero issue recovery.

Will Philz correctly restore a CWM backup?
If not I'll have to stick with CWM until I get everything back working.

n00bhackin said:
Will Philz correctly restore a CWM backup?
If not I'll have to stick with CWM until I get everything back working.
Click to expand...
Click to collapse
Well PhilZ is literally a touchscreen CWM and every time I made a backup with it the folder where the backup was is called "Clockworkmod" or "CWM" I can't remember the exact wording cause I've been using a beta TWRP made for the L710T

OK partial success, significant failure.
New phone received, it was an SPH-710 model, but was at ND8. But from what people have commented and what I read this wasn’t going to be a problem.
SO I rooted the device, all went well.
Restored my NAND backup, all went well.
Restored back to stock for activation, trouble started. IMEI information is gone !!
Restored back to CM10.1.2, IMEI information is there, but it contains the previous owner’s phone number.
I am able to activate the phone, everything seems to go fine.
I reboot and get data, I can receive data. I rejoiced.
I tried a text, fail.
I tried a call, fail…the rejoicing ended.
Checking phone status the person’s old phone number is still associated with the phone.
Normally this would be taken care of in stock by doing a profile reset. So Im not at a loss..
I need to see if I can recover the IMEI information in CM and transfer to Stock to do a reset on the phone to get it to activate right.
Any Ideas? I'm going to start a new thread just on this question, as this one was more about recovering my old phone to the new one.

n00bhackin said:
OK partial success, significant failure.
New phone received, it was an SPH-710 model, but was at ND8. But from what people have commented and what I read this wasn’t going to be a problem.
SO I rooted the device, all went well.
Restored my NAND backup, all went well.
Restored back to stock for activation, trouble started. IMEI information is gone !!
Restored back to CM10.1.2, IMEI information is there, but it contains the previous owner’s phone number.
I am able to activate the phone, everything seems to go fine.
I reboot and get data, I can receive data. I rejoiced.
I tried a text, fail.
I tried a call, fail…the rejoicing ended.
Checking phone status the person’s old phone number is still associated with the phone.
Normally this would be taken care of in stock by doing a profile reset. So Im not at a loss..
I need to see if I can recover the IMEI information in CM and transfer to Stock to do a reset on the phone to get it to activate right.
Any Ideas? I'm going to start a new thread just on this question, as this one was more about recovering my old phone to the new one.
Click to expand...
Click to collapse
I'm glad you were able to restore your
NAND backup of
CyanogenMod 10.2.1!
+ev

indigofilipino said:
I'm glad you were able to restore your
NAND backup of
CyanogenMod 10.2.1!
+ev
Click to expand...
Click to collapse
Not exactly, while I was able to restore the NAND backup, it was not usable, I could not activate the phone because in stock all the IMEI information was blank. I was able to recover from that. So now I am trying just to load a fresh CM10.2.1 onto the phone, but it's giving me issues. Starting HERE at post #1848.

Note 4 Help!

Like many other sprint users, I experienced serious problems with 5.1.1. This resulted in battery pulls and even a downloading boot. I starting looking into a fix. After flashing about every ROM for sprint N910P on this website, I either result in bootloop or the same problems persist. The problems are as follows:
-Can't boot, so I have to wait ~5 minutes to try again
-Boots straight to downloading, mmc read fail
-Boots fine
-Crashes to black screen around 80-90% battery (back to problem 1)
I cannot figure how to use odin anymore because it fails on nearly every rom I attempt. My reactivation lock is OFF.
I'll try to provide as much detail as I can, but I'm at my wits end with this phone.
Thanks!

If you can Odin OK1 stock tar, there is another root alternative: root stock with Chainfire Auto Root. CFAR has been updated for Android 5.1.1 Note 4
http://forum.xda-developers.com/showpost.php?p=55865442&postcount=3
Custom ROMs will take longer than 5 minutes to boot initially after flash. TWRP has been known to fail to flash or not properly flash after trying repeatedly to flash wrong tar with Odin or flash with reactivation locked. Which, if any, apply to you? I hope it's not hardware failure...
Sent from my SM-N910P using Tapatalk

Chainfire was going to be my next option. I think the first time I attempted using chainfire through odin, it ended in a bootloop. I haven't tried the update version though. I'll give that a shot.
Is there any way to fix this problem with TWRP (delete it and reflash)?
I'm starting to think its a hardware failure, which would suck because knox is tripped and warranty expired a few days ago anyway I believe.

I downloaded the updated CFAR last night to verify it was updated. It's bundled with Odin 3.10.6 Use the defaults with that for stock OK1 tar.
You should know that CFAR is primarily for rooted stock.
If you want a custom ROM, you may have to use Philz CWM touch recovery for Note 4. TWRP just gets inoperative for some time for some users when tars fail in repeated attempts. Philz' seems to flash where TWRP doesn't if that's the case.
http://downloadandroidrom.com/file/GalaxyNote4/CWM/philz_touch_6.59.0-trlte.tar
Sent from my SM-N910P using Tapatalk

Sorry to be the bearer of bad news, but this is most likely a hardware problem. I've had two Note 4's do exactly this. Flashed the stock rom on both with Odin, problems still persisted. It would just get random restarts and sometimes boot into "panic mode", whatever that is. The quality control on these phones is terrible. I baby them and never rooted any of them, yet two of them messed up like that, and all 3 of course have GPS issues. If it worked like it's supposed to it would be amazing, my friend has had one since my first Note with 0 issues, super jealous.

I hope its ok for me to post this here i couldnt find any threads on this issue and i didnt want to make new one just for this one problem so i figure i post it here since the post doesnt really point out to nothing specific and its on note 4 thread so i know ill get faster response than if i posted it in help thread ,but if i'm in wrong please feel free to delete this post at once . With that out of the way heres my issue and i hope theres an easy fix for it i was on latest pl1 build of 6.0.1 stock rooted i got tired of playing pokemon so i decided i want my themed look back so i restored my backup of 5.1.1 cog5 build ,everything works fine but my wifi ,its grayed out and when i try to turn it on it stays in "turning on " possition but it never does come on it eventualy goes back to " to see the list of networks turn on the wifi" .Now my question is is there any way to fix this wifi without flashing srock 5.1.1 i know there used to be fix for it back when i was on note 3 but this was yeaaaaars ago and i dont have that file any more thanks a million.

bigbabo said:
I hope its ok for me to post this here i couldnt find any threads on this issue and i didnt want to make new one just for this one problem so i figure i post it here since the post doesnt really point out to nothing specific and its on note 4 thread so i know ill get faster response than if i posted it in help thread ,but if i'm in wrong please feel free to delete this post at once . With that out of the way heres my issue and i hope theres an easy fix for it i was on latest pl1 build of 6.0.1 stock rooted i got tired of playing pokemon so i decided i want my themed look back so i restored my backup of 5.1.1 cog5 build ,everything works fine but my wifi ,its grayed out and when i try to turn it on it stays in "turning on " possition but it never does come on it eventualy goes back to " to see the list of networks turn on the wifi" .Now my question is is there any way to fix this wifi without flashing srock 5.1.1 i know there used to be fix for it back when i was on note 3 but this was yeaaaaars ago and i dont have that file any more thanks a million.
Click to expand...
Click to collapse
To fix the WiFi and camera focus, get the bootloader for OG5 from OP in this thread and flash it in Odin.
https://forum.xda-developers.com/showthread.php?p=66352412
The ones labeled firmware are bootloaders. You don't have to flash the whole OG5 stock tar but you still could. Just make sure the flash restores that bootloader and you should be set.
Likewise, you could still restore a MM backup and restore its bootloader.
I think you should backup your keepsakes in internal memory and wipe internal memory before restoring a backup that crosses Android versions. With backups on extSdCard, you could wipe everything but that but I'd think you could factory reset, wipe internal memory plus the Android folder on extSdCard and have a good transition with the bootloader flash. Otherwise, a factory reset would be the minimum step but may leave some residual information you may not need cluttering your memory along with what you want to keep. Seems I recall some having issues coming back to lollipop from MM without wiping internal memory?
Just curious, do you recall what you wiped going back to lollipop?
Sent from my SM-N920P using Tapatalk

Nothing i just go back n forth between lp and mm depending on lvl of interest in pokemon lol i have backups of 6.0.1 and 5.1.1 i just restore backups without wiping it restores fine aside from wifi not turning on i have no other issues
Edit: sorry meant to quote the post above me

bigbabo said:
Nothing i just go back n forth between lp and mm depending on lvl of interest in pokemon lol i have backups of 6.0.1 and 5.1.1 i just restore backups without wiping it restores fine aside from wifi not turning on i have no other issues
Edit: sorry meant to quote the post above me
Click to expand...
Click to collapse
Gotcha. Just an old question in the back of my mind from early days of MM. I researched the TWRP thread, the developers recommended a factory reset.
If you've ever noticed internal memory available seemingly smaller than usual, it could be the extraneous folders.
Thanks.
Sent from my SM-N920P using Tapatalk