Database Users

[Help] Every thing wiped, now what?

So here's my story:
I was kinda sick of the stock ROM, so I wanted to try out the Open Kang Projekt's ICS. And in order to do that I need to install Clockworkmod on my devise, and I did. But instead of installing the official CWM (which is version 4.0.0.4), I tried this: [Recovery] ClockworkMod - 5.5.0.4 - (Update: 03/18/12), I think it has the latest ICS kernel included or something (I'm not sure, that's what he said). And then I installed Kang's ICS ROM. Everything worked out just fine, except for the fact that it takes me every time about 5 minutes to boot, which is really a pain 'cause my tab crashes alot, and there are other bugs as well. So I decided to have a stable ROM instead of an unofficial ICS. But now I can't install any other ROM. I tried CLEAN ROM, team Overcome's ROM etc. but there's no luck, I'm always stuck at boot (Yes, I did wiped anything I could in CWM).
So now, what can I do?
I have wiped everything and flashed the official CWM 4.0.0.4 with Odin onto my tab, and I think that's the only thing I have on my tab now.
If I want to install Overcome's ROM now, what do I need. Do I need to install a bootloader? A kernel? What kind/version do I need. Shall I install the kernel first and then the ROM or the other way round?
And if I want to go back to stock, what do I have to do? Can I do that with Kies?
Really need some advice here. Hope you guys can help me.
BTW, my devise is Galaxy Tab 10.1 Wifi only.

Whenever I change my ROM, I always follow the steps outlined in S0ckM0nk3y's guide (stickied in the development section).
1. Use Odin to flash stock ROM
2. Boot into stock recovery and do a factory reset (I do it 3 times cuz I'm anal), also wipe the cache too
3. Now you should be back to stock ROM.
Make sure to thank S0ckM0nk3y for his very helpful post!!
Sent from my GT-P7510 using XDA Premium HD app

Do you mean the root and unroot thread? I don't really think that's what I need but I'll try to flash the stock from via Odin as you said. Thank you for your advises.

Yes, the root/unroot thread. Doing what I posted will get you to stock ROM. From there, you can try to load another ROM. I personally recommend task14 ROM. Make sure you read all instructions thoroughly as many times as necessary so that you fully understand the steps before you go on and flash anything. Task's page is pretty straightforward.
Sent from my GT-P7510 using XDA Premium HD app

Thank you. Everything's fine now. After installing the stock rom via odin I still got stuck at boot, but then I flashed the stock recovery (the 3e one) and did a factory reset with it, everything is back to normal now. I'm on stock rom again. Thank you very much for your replies.

That's quite the process. Not sure what went wrong for you in the first place (sounds like you've never done this before, from the wording of your questions), but all I do when I flash a new ROM is wipe (dalvik, then full wipe) and then flash. Never had to use ODIN except to flash CWM (and I've only done that twice, once when I got the tab and again a few weeks ago when the CM9 team released their variant).

slack04 said:
That's quite the process. Not sure what went wrong for you in the first place (sounds like you've never done this before, from the wording of your questions), but all I do when I flash a new ROM is wipe (dalvik, then full wipe) and then flash.
Click to expand...
Click to collapse
That's what I meant when I said "I wiped everything I could". I did wipe dalvik cache, full wipe with CWM recovery 5.5.0.4 but somehow that did not work.
But now everything's fine again, after I wipe data/factory reset with the stock recovery instead of CWM.
I'm not sure of what went wrong either, but since everything is back to normal now, I think I'll leave it this way, no more custom rom.

browy said:
That's what I meant when I said "I wiped everything I could". I did wipe dalvik cache, full wipe with CWM recovery 5.5.0.4 but somehow that did not work.
But now everything's fine again, after I wipe data/factory reset with the stock recovery instead of CWM.
I'm not sure of what went wrong either, but since everything is back to normal now, I think I'll leave it this way, no more custom rom.
Click to expand...
Click to collapse
I was actually referring to Swammy's process. No big deal. I can't imagine using a stock ROM at this point (especially since I've been using ICS for over a month now), but to each his own.

The only reason I go through that whole ordeal is because I hate all the cluttered folders on my sd, and cwm won't clean up any of that after a wipe. I admit, my method is a bit anal...but I do always go to stock, then wipe, then install cwm and load a fresh ROM. Is there a better method that I a unaware of? I am open to suggestions!
Sent from my GT-P7510 using XDA Premium HD app

Swammy1979 said:
The only reason I go through that whole ordeal is because I hate all the cluttered folders on my sd, and cwm won't clean up any of that after a wipe. I admit, my method is a bit anal...but I do always go to stock, then wipe, then install cwm and load a fresh ROM. Is there a better method that I a unaware of? I am open to suggestions!
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
I just use storage analyser from the market and occasionally clean house manually. Takes 2-3 minutes, and forces me to stay aware of how the storage is used (I do the same thing on my windows computer, though it takes much longer!). I probably have some useless directories but, honestly, there's no advantage to having the vanilla folder structure. But, if that's your purpose, I don't know another way. I just pointed that out because noobs will read this thread and since your post is the first response, I'm just playing damage control...

slack04 said:
I just use storage analyser from the market and occasionally clean house manually. Takes 2-3 minutes, and forces me to stay aware of how the storage is used (I do the same thing on my windows computer, though it takes much longer!). I probably have some useless directories but, honestly, there's no advantage to having the vanilla folder structure. But, if that's your purpose, I don't know another way. I just pointed that out because noobs will read this thread and since your post is the first response, I'm just playing damage control...
Click to expand...
Click to collapse
Good call!
Sent from my GT-P7510 using XDA Premium HD app

sdcard/0/0/0/ - layering of subdirectories?

Forgive me if this question has been raised before but I haven't found anything relevant on a search.
Everytime I reset my Nexus 7 it seems to create a new layer of directories. I've had the N7 for a week and I've already got three layers of subdirectories. Files that have been downloaded might be in sdcard/0/download, or sdcard/0/0/download, or sdcard/0/0/0/download. I have to manually reset the directory for Titanium Backup, etc.
What's causing this and, more importantly, what can I do fix/stop it?
Thanks,
Ted.

this happens to me to. idk what causes it

Did you flash a custom room? If so did you upgrade your recovery to the latest version? If not that will be your problem.
Sent from my Nexus 7 using Tapatalk 2

How are you resetting? I have two users, power off occasionally, and have never had more than one level zero.
Sent from my Nexus 7 using xda app-developers app

leelaa said:
Did you flash a custom room? If so did you upgrade your recovery to the latest version? If not that will be your problem.
Click to expand...
Click to collapse
I'm running CM10 with ClockworkMod Recovery 6.0.1.0.
If I install the latest version of CMR it won't automatically clean up the directory structure, will it? What's the easiest/best way to deal with this?

Well this o file was holding 5 GB of space and I want to know why it happened? I had to reflash the stock ROM because of a bad kernal
Sent from my Nexus 7 using xda premium

Sounds like this does not apply to people running the stock rom at all.
Somehow we need a disclaimer on threads like this, so all the folks with unmodified Nexus 7's don't freak out.

Most likely if u are on xda your rooted and running some type of mod or ROM.
And mine is stock just rooted
sent from a galaxy far away

jetbruceli said:
Most likely if u are on xda your rooted and running some type of mod or ROM.
And mine is stock just rooted
sent from a galaxy far away
Click to expand...
Click to collapse
Maybe back in the old days - but XDA has outgrown it's modest beginnings.
I would love to see some real figures, but my guess would be no more than 10 percent of XDA members are running a custom rom.
That is based on just reading posts on the Nexus forums.
Like you - I am stock and rooted. I would need to see a real benefit to put a custom rom on - and stock is pretty good.

rmm200 said:
Maybe back in the old days - but XDA has outgrown it's modest beginnings.
I would love to see some real figures, but my guess would be no more than 10 percent of XDA members are running a custom rom.
That is based on just reading posts on the Nexus forums.
Like you - I am stock and rooted. I would need to see a real benefit to put a custom rom on - and stock is pretty good.
Click to expand...
Click to collapse
Stock on the nexus is awesome with nova launcher but as soon as aokp is running 4.2 I am going to run it. I use it on my s3 and makes it so much better.
Again though this O file came from re flashing the stock ROM which has never happened to me
sent from a galaxy far away

rmm200 said:
How are you resetting? I have two users, power off occasionally, and have never had more than one level zero.
Click to expand...
Click to collapse
I'm talking about a full wipe with factory reset from ClockworkMod Recovery, not just powering down.

rmm200 said:
Sounds like this does not apply to people running the stock rom at all.
Somehow we need a disclaimer on threads like this, so all the folks with unmodified Nexus 7's don't freak out.
Click to expand...
Click to collapse
I suspect you're right. This probably only applies to users have installed a custom recovery and/or custom ROM. I certainly never had the problem before I installed CM10.
As far as "freaking out" goes, why would anyone be concerned if they DIDN'T have multiple "0" directories? There are hundreds of posts on XDA about people having problems with their devices, but if you don't have that problem why would you be concerned?

Apparently the problem has to do with upgrading to Android 4.2. There is a lengthy discussion at http://forum.xda-developers.com/showthread.php?t=1999214.
I had upgraded with the OTA 4.2 then flashed CM10 (which is 4.1.2), went back to 4.2 and then re-flashed CM10. I think the easiest solution may be to back up internal storage /sdcard/, reformat internal storage, full wipe/factory reset, reflash 4.2, and finally restore files selectively. After that the problem should be solved. Maybe.

I had 10gb of stuff that after flashing a 4.2 rom (I think it was cleanrom 2.5)got sent into a 0 folder and then it was as if it set up its own file structure again as if all the folders that come stock it were there (empty) and then a 0 folder with all my previous stuff but all downloads and pictures that are taken on the new rom with this new folder setup get stored in the new folders and not the 0 folder. I'm running the latest twrp so that shouldn't be the problem and when I wipe I always do cache, dalvik, factory reset, and system (full wipe) so yeah. Hope this adds a little insight
Sent from my EVO using Tapatalk 2

Update your recovery to 6.0.1.9, You will face this problem if on older clockwork mod.

sahshah said:
Update your recovery to 6.0.1.9, You will face this problem if on older clockwork mod.
Click to expand...
Click to collapse
Could be then and my only issue was the double data it was using. I just deleted it.
I noticed this file when I was flashing a zip file and the selection for files in cwm was wierd and my downloads were in file O
Sent from my Nexus 7 using xda premium

OK so the O file is because now we have multiple users. When u flash over an existing ROM it makes the admin file 0 and when u add more users it gives them thier own file structure. This would be good for someone who wants to share their n7 but only give them certain rights!!
sent from a galaxy far away

/0/ is a user
if you were to add multiple users there would also be a /1/, /2/ etc
/0/ is the primary user, if you were to wipe and reflash with a custom recovery that didn't wipe all of the /sdcard/ too then it will probably get confused (unless the recovery was new and fixed this 'bug') and then create a /0/0/ etc.

Lennyuk said:
/0/ is a user
if you were to add multiple users there would also be a /1/, /2/ etc
/0/ is the primary user, if you were to wipe and reflash with a custom recovery that didn't wipe all of the /sdcard/ too then it will probably get confused (unless the recovery was new and fixed this 'bug') and then create a /0/0/ etc.
Click to expand...
Click to collapse
Nit: Second user is /10, not /1. Third user is /20 - I think.

4.4.2 ROMs D801 T-Mobile Cause Colored Horizontal Lines

I'm pretty sure this is a common problem (I hope) but can't find an answer. After I flash a 4.4.2 ROM on first boot the phone unlocks fine. Once it turns off I try to turn it back on and I get horizontal colored lines and can't unlock the phone. Anyone know what my problem is? Thanks.

zone23 said:
I'm pretty sure this is a common problem (I hope) but can't find an answer. After I flash a 4.4.2 ROM on first boot the phone unlocks fine. Once it turns off I try to turn it back on and I get horizontal colored lines and can't unlock the phone. Anyone know what my problem is? Thanks.
Click to expand...
Click to collapse
Yup, common problem with the new TMO G2's. There's a workaround:
I'm assuming the ROM you're trying is something like CloudyFlex? Anyways, here's what you'll have to do.
1) Install this ROM: http://forum.xda-developers.com/showthread.php?t=2664652 (It takes a LONG time to flash, 5-10 mins but be patient!)
2) DO NOT REBOOT device after it installs. Instead, wipe data and cache then flash your desired ROM, CloudyFlex for example.
3) Then flash SuperSU. (DO NOT FORGET THIS PART <<<< Very important part or else you're stuck with that ROM)
4) Then reboot phone and enjoy ROM.
Doing this way you lose recovery but you can gain it back by using this simple to use app. http://forum.xda-developers.com/showthread.php?t=2715496
P.S. This whole procedure only applies to LG KK ROM's, if you wish to flash AOSP ROM's like CM11, the regular procedure that you're used to is fine.
If you have any other questions, let me know. Good luck!

mackster248 said:
Yup, common problem with the new TMO G2's. There's a workaround:
I'm assuming the ROM you're trying is something like CloudyFlex? Anyways, here's what you'll have to do.
1) Install this ROM: http://forum.xda-developers.com/showthread.php?t=2664652 (It takes a LONG time to flash, 5-10 mins but be patient!)
2) DO NOT REBOOT device after it installs. Instead, wipe data and cache then flash your desired ROM, CloudyFlex for example.
3) Then flash SuperSU. (DO NOT FORGET THIS PART <<<< Very important part or else you're stuck with that ROM)
4) Then reboot phone and enjoy ROM.
Doing this way you lose recovery but you can gain it back by using this simple to use app. http://forum.xda-developers.com/showthread.php?t=2715496
P.S. This whole procedure only applies to LG KK ROM's, if you wish to flash AOSP ROM's like CM11, the regular procedure that you're used to is fine.
If you have any other questions, let me know. Good luck!
Click to expand...
Click to collapse
Thanks a lot!
Edit:
I did see AutoRec but wasn't sure I needed to do that.

Does this create problems in going back to 4.2.2 ROMs?
Do I have to do step #1 every time I flash a 4.4.2 ROM or just the first time?
Can I still restore a backup from recovery?

zone23 said:
Does this create problems in going back to 4.2.2 ROMs?
Do I have to do step #1 every time I flash a 4.4.2 ROM or just the first time?
Can I still restore a backup from recovery?
Click to expand...
Click to collapse
No on your first question. Pertaining to your second question, this whole process is only needed if you wish to use any of the LG KitKat ROM's such as CloudyFlex, CloudyPro, Lightning ROM, etc etc.

mackster248 said:
No on your first question. Pertaining to your second question, this whole process is only needed if you wish to use any of the LG KitKat ROM's such as CloudyFlex, CloudyPro, Lightning ROM, etc etc.
Click to expand...
Click to collapse
OK I think I get now.

zone23 said:
OK I think I get now.
Click to expand...
Click to collapse
Awesome. Can't hurt to ask questions though, good luck!
Just remember to NEVER EVER forget flashing the SU part. I made that mistake and paying for it, so I'm making sure no one else makes the same mistake lol.

Biggins Rom

Hello- I am wondering if you can help me, yestyerday I had to reinstall the stock firmware for my note 3 on NC4 (thanks to Beantown's 106) after having great difficulty with the Biggins Rom ("unfortunately messagres has stopped, along with contacts and occasional android has stopped), I was unable to use the phone obviously let alone be able to explore this really cool rom. While trying to reset the phone, remove sache, dalvik, data etc. it did get to a point where the phone was stuck on the red Verizon Splash screen all the while Safestrap was still intact and by the end of the night after finding the stock firmware I was able to restore the phone to factory. The only issiue that I think would have caused these is finding and checking the boxes already set in 'root explorer' as opposed to what all the other apps are set to or possibly partitioning the new sd card but I doubt would cause an issue. I installed the rom the night before last and tried to fix the issue yesterday but was unable to which took most of last night to fix before I got it back up and running with the stock firmware. I would like to know how to get this rom back on without issues. Any advice would be great.

tjmethod said:
Hello- I am wondering if you can help me, yestyerday I had to reinstall the stock firmware for my note 3 on NC4 (thanks to Beantown's 106) after having great difficulty with the Biggins Rom ("unfortunately messagres has stopped, along with contacts and occasional android has stopped), I was unable to use the phone obviously let alone be able to explore this really cool rom. While trying to reset the phone, remove sache, dalvik, data etc. it did get to a point where the phone was stuck on the red Verizon Splash screen all the while Safestrap was still intact and by the end of the night after finding the stock firmware I was able to restore the phone to factory. The only issiue that I think would have caused these is finding and checking the boxes already set in 'root explorer' as opposed to what all the other apps are set to or possibly partitioning the new sd card but I doubt would cause an issue. I installed the rom the night before last and tried to fix the issue yesterday but was unable to which took most of last night to fix before I got it back up and running with the stock firmware. I would like to know how to get this rom back on without issues. Any advice would be great.
Click to expand...
Click to collapse
What firmware are you on? Were you OTA KK or MJE? (I know you said NC4, but was it OTA or did you use beans' .tar file?)

shaggy_kobain said:
What firmware are you on? Were you OTA KK or MJE? (I know you said NC4, but was it OTA or did you use beans' .tar file?)
Click to expand...
Click to collapse
Hi no OTA, I am on the KK NC4, which is how it came- it's an insurance replacement that I just received last week.

tjmethod said:
Hi no OTA, I am on the KK NC4, which is how it came- it's an insurance replacement that I just received last week.
Click to expand...
Click to collapse
Ok, so what they did was sent you a replacement with the KK OTA already on it.
Coming from NC4
1. Root with TowelRoot HERE[URL="https://towelroot.com/"]
[/URL]2. Install Busy Box from Play Store -Open App and Install
3. Install SuperSU- Open App and Install
4. Install SafeStrap 3.75 B04 HERE -Open App and Install
5. Reboot into SafeStrap, Wipe (Factory Reset) Stock Slot
6. Install BigginsRom
7. Reboot into Download Mode FROM WITHIN SAFESTRAP
8. Odin (AP slot) Updated NC2 Firmware for NC4 OTA users HERE
9. Reboot
----DONE----
**SOME USERS HAVE HAD TO DL SUPERSU AND FLASH THE ZIP AFTER FLASHING THEIR ROM***
Only IF you run into any issues after running SuperSU after installing in Step #3.

tjmethod said:
Hi no OTA, I am on the KK NC4, which is how it came- it's an insurance replacement that I just received last week.
Click to expand...
Click to collapse
To properly run most KK roms you need to flash the NC2 kernel. Instructions and download can be found here. You will only need to flash the kernel. If you are following the step by step instructions you can substitute any supported rom for the stock rom.

shaggy_kobain said:
Ok, so what they did was sent you a replacement with the KK OTA already on it.
Coming from NC4
1. Root with TowelRoot HERE[URL="https://towelroot.com/"]
[/URL]2. Install Busy Box from Play Store -Open App and Install
3. Install SuperSU- Open App and Install
4. Install SafeStrap 3.75 B04 HERE -Open App and Install
5. Reboot into SafeStrap, Wipe (Factory Reset) Stock Slot
6. Install BigginsRom
7. Reboot into Download Mode FROM WITHIN SAFESTRAP
8. Odin (AP slot) Updated NC2 Firmware for NC4 OTA users http://www.androidfilehost.com/?fid=235016813585512618. Reboot
----DONE----
**SOME USERS HAVE HAD TO DL SUPERSU AND FLASH THE ZIP AFTER FLASHING THEIR ROM***
Only IF you run into any issues after running SuperSU after installing in Step #3.
Click to expand...
Click to collapse
Thank you for the instructions- I will give it a go, but first verizon instructed me to take the phone to best buy to see if there's a problem with data since it somehow ate up 96% of my 2 gbs yesterday while I had problems- of course I didn't tell them I was rooted- dofood you know if there's a way to tell if the nc4 was an OTA or it was installed that way or does it even matter?
Thanks again

tjmethod said:
Thank you for the instructions- I will give it a go, but first verizon instructed me to take the phone to best buy to see if there's a problem with data since it somehow ate up 96% of my 2 gbs yesterday while I had problems- of course I didn't tell them I was rooted- dofood you know if there's a way to tell if the nc4 was an OTA or it was installed that way or does it even matter?
Thanks again
Click to expand...
Click to collapse
It doesn't matter since you can use TowelRoot to get root access. :good:

kinstre11 said:
To properly run most KK roms you need to flash the NC2 kernel. Instructions and download can be found here. You will only need to flash the kernel. If you are following the step by step instructions you can substitute any supported rom for the stock rom.
Click to expand...
Click to collapse
Hi thanks for the info- how would you suggest I save the stock rom if I need to go back to it or do I need to reinstall the firmware like I did last night?

tjmethod said:
Hi thanks for the info- how would you suggest I save the stock rom if I need to go back to it or do I need to reinstall the firmware like I did last night?
Click to expand...
Click to collapse
If you are already rooted you don't need to change anything with you rom. Just flash the NC2 kernel found in the link from my previous post using Odin. The kernel is not the bootloader img, You are already on the NC4 bootloader and can not go back, but flashing the NC2 kernel will leave you with the so-called Unified firmware (NC2/NC4). This is what is needed for most KK roms.

kinstre11 said:
If you are already rooted you don't need to change anything with you rom. Just flash the NC2 kernel found in the link from my previous post using Odin. The kernel is not the bootloader img, You are already on the NC4 bootloader and can not go back, but flashing the NC2 kernel will leave you with the so-called Unified firmware (NC2/NC4). This is what is needed for most KK roms.
Click to expand...
Click to collapse
Ok but is there a way to save the stock rom? when I root again and have any issue and need to go back to stock or I will need to DL the firmware again since I will have had the unified firmware on. Also since I like the stock rom besides the Samsung lag, I saw a rom that is based on stock but I think alot better from what I read and is deodexed, do you know what that means?
Thanks you!

tjmethod said:
Ok but is there a way to save the stock rom? when I root again and have any issue and need to go back to stock or I will need to DL the firmware again since I will have had the unified firmware on. Also since I like the stock rom besides the Samsung lag, I saw a rom that is based on stock but I think alot better from what I read and is deodexed, do you know what that means?
Thanks you!
Click to expand...
Click to collapse
Assuming you have Safestrap installed as it is the only way to flash a custom rom on retail Note 3, all you need to do is boot into Safestrap and make a backup. It will be stored on your external SD card and if you want to revert back to it simply wipe the stock rom slot in Safestrap then restore your backup. As you are on NC4 you won't be able to use a rom slot in Safestrap other than the stock slot, and you always want to wipe system, dalvik, cache, and data before installing any new rom.
Odex/Deodex is how the system stores and reads apps. Standard out of the box is usually (perhaps always) odex. This method breaks the apps into 2 parts. It allows for faster loading and searching of the system. Deodex keeps the apps as one entity. This means that the initial loading of the system will take longer but in the end we get easier customization/tweaking. Xposed framework needs a Deodex rom to run (I believe). I'm fairly sure most developers that make custom roms deodex their roms. (My understanding of Odex/Deodex may be flawed but this is a basic explanation, for more info you can always Google, or search these forums).

kinstre11 said:
Assuming you have Safestrap installed as it is the only way to flash a custom rom on retail Note 3, all you need to do is boot into Safestrap and make a backup. It will be stored on your external SD card and if you want to revert back to it simply wipe the stock rom slot in Safestrap then restore your backup. As you are on NC4 you won't be able to use a rom slot in Safestrap other than the stock slot, and you always want to wipe system, dalvik, cache, and data before installing any new rom.
Odex/Deodex is how the system stores and reads apps. Standard out of the box is usually (perhaps always) odex. This method breaks the apps into 2 parts. It allows for faster loading and searching of the system. Deodex keeps the apps as one entity. This means that the initial loading of the system will take longer but in the end we get easier customization/tweaking. Xposed framework needs a Deodex rom to run (I believe). I'm fairly sure most developers that make custom roms deodex their roms. (My understanding of Odex/Deodex may be flawed but this is a basic explanation, for more info you can always Google, or search these forums).
Click to expand...
Click to collapse
Hi thanks and yes I'll be googling more before doing. Do you have any idea while the phone was stuck on the verizon splash screen yet SS still worked, why the phone was sucking up huge amounts of data while on the Higgins Rom while it had issues and while trying to reinstall stock firmware?
Thanks again! I can't seem to find the "Thanks" button?

tjmethod said:
Hi thanks and yes I'll be googling more before doing. Do you have any idea while the phone was stuck on the verizon splash screen yet SS still worked, why the phone was sucking up huge amounts of data while on the Higgins Rom while it had issues and while trying to reinstall stock firmware?
Thanks again! I can't seem to find the "Thanks" button?
Click to expand...
Click to collapse
The splash screen freeze could have been caused by the rom not being compatible with the NC4 kernel combined with possibly wiping system via safestrap. Safestrap is not wiped when you wipe the system it remains installed separately (this is what allows us to wipe and install.
The data drain may also be linked to the incompatibility, however I would be unable to answer that as I have never experienced such an issue nor have I read about it on any forums.
Once you are set up with the proper firmware, I would suggest doing a factory reset before flashing any further roms. You may need to reroot and reinstall busybox and safestrap afterwards but it will reset any residual system alterations that may be left from the previous biggins problem.

tjmethod said:
Ok but is there a way to save the stock rom? when I root again and have any issue and need to go back to stock or I will need to DL the firmware again since I will have had the unified firmware on. Also since I like the stock rom besides the Samsung lag, I saw a rom that is based on stock but I think alot better from what I read and is deodexed, do you know what that means?
Thanks you!
Click to expand...
Click to collapse
I made a full backup of my stock nc4 rom before I flashed biggins rom and flashed nc2 kernel. I restored my stock rom to see if it would run on the nc2 kernel and it froze at the red Verizon splash screen. The nc4 kernel will need to be reflashed after going back to stock. However, biggins rom is basically perfect so I have no real intentions on going back anytime soon.

kinstre11 said:
To properly run most KK roms you need to flash the NC2 kernel. Instructions and download can be found here. You will only need to flash the kernel. If you are following the step by step instructions you can substitute any supported rom for the stock rom.
Click to expand...
Click to collapse
Thanks or that important point, I'm back up and running with the unified firmware on Biggins- very cool but the battery seems to lack a bit.

shaggy_kobain said:
It doesn't matter since you can use TowelRoot to get root access. :good:
Click to expand...
Click to collapse
hi thanks alot for all your guidance- I'm finnaly back on with biggins but the batterry seems a little less in performance than stock. Any idea as to how to improve this or know of a rom that is has better battery stats? I reall like the Biggins though

tjmethod said:
hi thanks alot for all your guidance- I'm finnaly back on with biggins but the batterry seems a little less in performance than stock. Any idea as to how to improve this or know of a rom that is has better battery stats? I reall like the Biggins though
Click to expand...
Click to collapse
First, you are welcome. Second, did you flash in Stock Slot or a ROM Slot?
Generally, performance on any ROM for battery life is measured after the ROM has time to "settle". It was about 48 hours after I flashed Biggins that I noticed my battery life increase significantly. I can't say that for other ROMS, as I have only been on Biggins, but it seems to be the general consensus all in all.
I do know that if you flashed on a ROM Slot, that for some reason battery consumption is drastic. Again, some have reported otherwise, but in general that seems a culprit to some.
However you flashed the ROM, 3 things will help
1) Let the ROM settle. After 48 hours if you see that the battery is still suckus, then switch to alternate (Stock Slot or whichever)
2) Check your Wakelocks. There is an app in the playstore that you can dl that will measure what is running in the background and then you can shut it down using Greenify
3) Always Greenify
Greenify is a lifesaver to some, and added with a ROM that already has ridiculous battery life (that was meant in a good way ) then you can push about 2 days on one full charge.
Hopefully this helps, if not, then you know where to find me :good:

shaggy_kobain said:
First, you are welcome. Second, did you flash in Stock Slot or a ROM Slot?
Generally, performance on any ROM for battery life is measured after the ROM has time to "settle". It was about 48 hours after I flashed Biggins that I noticed my battery life increase significantly. I can't say that for other ROMS, as I have only been on Biggins, but it seems to be the general consensus all in all.
I do know that if you flashed on a ROM Slot, that for some reason battery consumption is drastic. Again, some have reported otherwise, but in general that seems a culprit to some.
However you flashed the ROM, 3 things will help
1) Let the ROM settle. After 48 hours if you see that the battery is still suckus, then switch to alternate (Stock Slot or whichever)
2) Check your Wakelocks. There is an app in the playstore that you can dl that will measure what is running in the background and then you can shut it down using Greenify
3) Always Greenify
Greenify is a lifesaver to some, and added with a ROM that already has ridiculous battery life (that was meant in a good way ) then you can push about 2 days on one full charge.
Hopefully this helps, if not, then you know where to find me :good:
Click to expand...
Click to collapse
Great I'm at the 48 hr. mark so maybe I'll see some improvement- I will check out Geenify, I recently heard about and am using Clean Master- have you checked it out?... seems like a good utility widget. Yes I did the stock slot since I was told before installing Baja which actually had really good battewry performace but I just wasnt crazy about the rom.
I dont see a thanks button?

tjmethod said:
Great I'm at the 48 hr. mark so maybe I'll see some improvement- I will check out Geenify, I recently heard about and am using Clean Master- have you checked it out?... seems like a good utility widget. Yes I did the stock slot since I was told before installing Baja which actually had really good battewry performace but I just wasnt crazy about the rom.
I dont see a thanks button?
Click to expand...
Click to collapse
Great, you should see some improvement soon enough :good: Yes I have heard about CM, I use it on a regular basis
If you are using Tapatalk, it'll be a "thumbs up" at the top. If not, then I dunno lol.... no worries, i'm sure you'll find it eventually :laugh:.

shaggy_kobain said:
Great, you should see some improvement soon enough :good: Yes I have heard about CM, I use it on a regular basis
If you are using Tapatalk, it'll be a "thumbs up" at the top. If not, then I dunno lol.... no worries, i'm sure you'll find it eventually :laugh:.
Click to expand...
Click to collapse
I dl'd in on the phone but haven't used it yet- I'm going to dl in here too ( wifi note 2014 10.1)- ya so last night roughly 8 or soon after I had 38% the night before 15% around same time so its getting better battery. The other day I saw carbon rom, have you seen that? you can minimize apps like pages on windows while running multiples but one sight said our note 3 isnt compatable yet a couple other carriers versions are. Another site said it is but I can't find it- it seems like the rom of all roms…

Note 3 shuts down and needs a battery pull to turn back on!? (logcat inside)

Hi. My note 3 has Aryamod 8.1 flashed on it but i think there is a app causing this but i can't figure which one is causing it!
My phone runs normally but suddenly it totally blacks out and i need to do a battery pull out just to get it back on!
Here is the logcat after the issue happened and rebooted:
https://mega.nz/#!6VIwmTwC!1gz0eVIAZaPTqhNCgHFYFCLCBWz8ZrwduB5uN_Tj04s

been using the same ROM for more than an year!
joluke said:
Hi. My note 3 has Aryamod 8.1 flashed on it but i think there is a app causing this but i can't figure which one is causing it!
My phone runs normally but suddenly it totally blacks out and i need to do a battery pull out just to get it back on!
Here is the logcat after the issue happened and rebooted:
https://mega.nz/#!6VIwmTwC!1gz0eVIAZaPTqhNCgHFYFCLCBWz8ZrwduB5uN_Tj04s
Click to expand...
Click to collapse
I've been using AryaMod form v5.3. Did you flash the BL and CP before installation? Also did you flash stock before installing Arya if youre coming from other ROM?

nijom said:
I've been using AryaMod form v5.3. Did you flash the BL and CP before installation? Also did you flash stock before installing Arya if youre coming from other ROM?
Click to expand...
Click to collapse
Yes, did flash BL and CP but didn't flash the totally stock rom before installing Arya since i didn't had these issues in the past (before Audax 34)
The logs don't show anything?
Maybe tomorrow i'll download the stock rom, flash it, flash twrp on it and do a full wipe and test but i did a full wipe a week ago, and previously was in another rom where the same exact issue happened:
Audax 34!
Any ideas? I seriously doubt flashing the stock rom will solve it since i did a full wipe and i do never restore data from a previous rom... always configure everything from scratch
PS: Every single update to a rom, i always do a full wipe

joluke said:
Yes, did flash BL and CP but didn't flash the totally stock rom before installing Arya since i didn't had these issues in the past (before Audax 34)
The logs don't show anything?
Maybe tomorrow i'll download the stock rom, flash it, flash twrp on it and do a full wipe and test but i did a full wipe a week ago, and previously was in another rom where the same exact issue happened:
Audax 34!
Any ideas? I seriously doubt flashing the stock rom will solve it since i did a full wipe and i do never restore data from a previous rom... always configure everything from scratch
PS: Every single update to a rom, i always do a full wipe
Click to expand...
Click to collapse
I don't know to read log files
I used to follow whats in OP and have been successful in all installs. I came to Arya from CM11S, I flashed a stock 5.0 in between, just to install Arya over it

nijom said:
I don't know to read log files
I used to follow whats in OP and have been successful in all installs. I came to Arya from CM11S, I flashed a stock 5.0 in between, just to install Arya over it
Click to expand...
Click to collapse
I will try to flash the stock rom, though i suspect flashing persist, BL and CP it way more then enough to get the rom working properly!
If i continue to have this issue i will full wipe and install my apps, one by one and get some tests going so see if i find the culprit!
Anyway i'll be waiting for more help around here