Develop Bugs

[Q] Cache Issue When Wiping Using CWM & SuperWipe

I was running CM9 and then went to MIUI and then back to CM9. Ever since I have not been able to do a proper update to the CM9. Got fed up with it and tried to roll it back to one of the Nandroid backups. It got stuck for hours. Pulled the battery. Tried to go through the process of installing CM9 again fresh. Used Darkside SuperWipe and it kept freezing on "Wiping Cache" and the same thing when I use CWM (v6.0.1.4)! I have attached two screen shots. It reads:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
Then when I ask it to format the cache it get frozen.
How can I fix the cache? I cannot boot into CM9 or anything for that matter. I just get the awesome little Cyan Dude and the warp background flying at me continually until I pull the battery. Can anyone help? Is there any way to get ADB to work with out turning on USB Debugging on the phone?

Same issue with Clockworkmod Recovery
Sorry to say I can't answer your question, but actually just downloaded cm9 and was trying to factory reset in order to prepare to flash it and ran into the same cache issue. I tried everything and still couldn't get around it, almost bricked my phone, got stuck in a loop. Hadn't even done anything yet, except download the cm9 Rom. Also freezes when trying to wipe cache and when trying to restore a backup when it gets to the cache. I'll be keeping an eye on your post, and Ill let you know if I figure anything out as well.

I hate to say it but... use TWRP. It looks and works better. Trust me.
Sent from my SGH-T989 using xda app-developers app

whatiznt said:
I hate to say it but... use TWRP. It looks and works better. Trust me.
Click to expand...
Click to collapse
I trust you but on the Team Win Recovery Project's changelog you can see that it has not been updated in almost a year! CWM is updated much more frequently and also I enjoy having the touch version! Very convenient.

I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).

jalight27 said:
Just downloaded cm9 and was trying to factory reset in order to prepare to flash it and ran into the same cache issue. I tried everything and still couldn't get around it, almost bricked my phone, got stuck in a loop. Hadn't even done anything yet, except download the cm9 Rom. Also freezes when trying to wipe cache and when trying to restore a backup when it gets to the cache. I'll be keeping an eye on your post, and Ill let you know if I figure anything out as well.
Click to expand...
Click to collapse
Thank you my friend. What you describe is exactly what happened to me. Tell me, what version of CWM Recovery do you have? Were you coming from stock? Which CM9 was it? Nightly, stable?

mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
Please pardon my ignorance as I am relatively new at all this. How do you downgrade CWM? I am unable to boot the phone into the ROM. Can it be done through Recovery? ODIN?

I've looked around but I can't find a download for 5.0.2.7-- at least not one that's labeled specifically for our phone. It can be done in many different ways, flashing via recovery or Odin would definitely work, just need to find the right file.

Same version as you've got. Was actually coming from Jedi Mind Trick v8 and was going with the nighty. I loaded a backup of my stock ICS, which of course froze during the restore once it got to the cache, but I let it sit for like 15 min or so and then reset it and surprisingly it loaded up fine despite the fact that I had to reset it during the restore. I'm trying to follow up with the advice these two guys gave me on my post (really the same thing they've told you). With my extremely limited knowledge in this field I'm still working it all out and trying to make sure I ask the stupid questions so as not to mess anything up, well at least not too bad, lol.

mintharis said:
I've looked around but I can't find a download for 5.0.2.7-- at least not one that's labeled specifically for our phone. It can be done in many different ways, flashing via recovery or Odin would definitely work, just need to find the right file.
Click to expand...
Click to collapse
Go into rom manager and scroll down to previous versions

VoiD_Dweller said:
Go into rom manager and scroll down to previous versions
Click to expand...
Click to collapse
I don't have ROM manager installed. Does it provide a tar that can be flashed via Odin?

Newer Recovery
Clockworkmod 6 doesn't need the Darkside tools anymore. I had a similar problem but it was causing my phone to lock up. Just try using the regular cache wipe and dalvik cache wipe and see if that works for you.

mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
I can confirm this, I have a samsung galaxy S II and I was having HUGE problems with the newer version of CWM. Cache would not clear at all even with darksides super wipe. My CM9 was stuck in a boot loop because I had forgotten to clear my cache and factory reset, and I was not able to do this at all, so i thought i was screwed.
However what i did was flash an older version of CWM (5.0.2.7) through odin, and BAM I was able to clear all my data with no problem and reflash CM9. Works perfectly now.

Pugnap00 said:
I can confirm this, I have a samsung galaxy S II and I was having HUGE problems with the newer version of CWM. Cache would not clear at all even with darksides super wipe. My CM9 was stuck in a boot loop because I had forgotten to clear my cache and factory reset, and I was not able to do this at all, so i thought i was screwed.
However what i did was flash an older version of CWM (5.0.2.7) through odin, and BAM I was able to clear all my data with no problem and reflash CM9. Works perfectly now.
Click to expand...
Click to collapse
Can you please provide a link for the 5.0.2.7 tar you flashed?

mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
CWM v6.0.1.4 has pretty much made my phone useless. When in Recovery I can't even scroll down or up. I even tried restarting my phone to downgrade but I have no response from my MENU, HOME, BACK or SEARCH button.
WORD OF ADVICE. PLEASE STAY AWAY FROM CWM v6.0.1.4.

EdwardLThompson said:
I was running CM9 and then went to MIUI and then back to CM9. Ever since I have not been able to do a proper update to the CM9. Got fed up with it and tried to roll it back to one of the Nandroid backups. It got stuck for hours. Pulled the battery. Tried to go through the process of installing CM9 again fresh. Used Darkside SuperWipe and it kept freezing on "Wiping Cache" and the same thing when I use CWM (v6.0.1.4)! I have attached two screen shots. It reads:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
Then when I ask it to format the cache it get frozen.
How can I fix the cache? I cannot boot into CM9 or anything for that matter. I just get the awesome little Cyan Dude and the warp background flying at me continually until I pull the battery. Can anyone help? Is there any way to get ADB to work with out turning on USB Debugging on the phone?
Click to expand...
Click to collapse
Simple Solution is that the Cache in your device is large, it has to be cleaned, For this use Darkside cache wipe. It Solves the problem.

suffuciently hungeom
mintharis said:
Can you please provide a link for the 5.0.2.7 tar you flashed?
Click to expand...
Click to collapse
Here you go,
Look at step 6, it will have links to the tar based on your carrier. Its actually 5.0.2.6, works just the same though.
http://theunlockr.com/2011/12/01/how-to-root-the-samsung-galaxy-s-ii-all-versions/
I hope this helps you!

That happened to me as well when I was going to update to CM10. The faq for CM10 says you need to update to a Touch version of CWM which ROM Manager really wanted to install the Touch version. CWM shows it's version 6 and the menus were different but when I was finally able to get a ROM to boot in Safe Mode it reported CWM as being version 5.x. I could not mount or dismount the Cache in CWM. ODIN brought it back to stock but I messed around with the partition checkbox and hard bricked it. Otherwise it looked as tho things would have been ok after using ODIN to start over.
Darkside's wipe wouldn't work (either version) in this case.

screw cwm im going to twrp
ok same thing happened to me..but there are files i need in the phone and i dont think i want to use cwm after this...so can i use odin to flash it to twrp and recover my files through the twrp usb mount?
(lol nvm, i flashed a older version of cwm through odin and then recovered my files then got twrp)

mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
Like I said in my earlier post had your exact problem and did exactly what was recommend here, and it worked beautifully. Solved all my problems, no residual effects to speak of. Now I can flash my roms in peace.

[Q] Need help with flashing roms Galaxy s3

I tried flashing two different roms (synergy and chemistry) on my sprint galaxy s3. It turns on but then wont go past the "galaxy s III" logo. I just restored my backup and all is well but I really want to get multi window on this thing so I could really use some help as to what is not letting me boot up all the way. The last thing i messed around with rooting was my DroidX and with that it really mattered a lot which version of android you were flashing from. I have 4.1.2 the most recent update. Is that why these roms are not working? Any help would be much appreciated I am very excited to get a killer rom on this bad boy.

Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway

CNexus said:
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
Click to expand...
Click to collapse
I boot into recovery after i put the rom on to my sd card. Then wipe the factory data, cache partition, and delvik cache. I do those steps twice, then install the rom. The install seems to go fine, it always says successful at the end, it just wont go past that screen. Does it mater which version of clockworkmod I use?

You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"

CNexus said:
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
Click to expand...
Click to collapse
Thank you so much for your quick response. As far as I can tell, I am wiping everything I should be. I use clockwork recovery mod version: and the choices it gives you are: Wipe data/factory reset, wipe cache partition, and wipe dalvik cache. From all the instructional threads I've read, those are the only things you need to clear out before the install. My clockwork version is v5.5.0.4 which i think might be really old. Could that be my issue? Does it matter how I rooted it? I just tryed to put jellybomb v14 on it and it didn't even give me the galaxy s III logo. Luckily it booted back into recovery though. I really don't want to hard brick this thing.

Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.

A-Shin said:
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
Click to expand...
Click to collapse
clockworkmod v5.5.0.4

cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
Make the switch to TWRP v2.3.1.0 (newer ones I've heard have problems) but you will be thanking me later. It's way easier and much better than CWM... just an FYI for ya!

cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
I suggest trying a flash with TWRP. If you are unsure how to install TWRP, just download the Goomanager app, then choose install Open Recovery Script. But, before you install or change anything, look around a bit on how to install it. Make sure you follow directions step by step. After you have installed TWRP, try flashing again. Good luck!

Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?

cchrisrollins said:
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
Click to expand...
Click to collapse
Samsung bootloaders come unlocked by default, so yes
Easiest way to switch is to download Goo manager from the Play Store and have it install TWRP for you
Generally speaking, CWM is great on most devices, but for the S3 it's TWRP that's the best and easiest to use
And when flashing new roms, make sure to always format system, it prevents corrupted files from showing up because you would be installing the new system right on top of the old one if you don't

So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app

cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you made a nandroid backup in TWRP (I'd recommend to put it on the external memory, but that's just me), you should be good to try any ROM you want (only Sprint ROMS). Just follow CNexus's post (linked for posterity). Wipe system as well as factory reset, cache, and dalvik, prior to installing the ROM.

cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you've already rooted, re-rooting isn't going to fix anything, so no need to go there.
As previously explained and detailed, do a full system wipe, and you'll be good to go.

Thank you guys so much for your very quick responses, thank you for bearing with my noobishness too haha. I am going to tryn reflash jellybomb tonight, I'll post on this thread how it goes (hopefully good).

So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!

cchrisrollins said:
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
Click to expand...
Click to collapse
It took me like 4-5 months to personally figure out that the problem was the kernel. You need to flash a kernel right after you flash the ROM. Either the stock kernels or better kernels like Anthrax will do. I know that for jellybomb, there's a kernel included in the Rom but for some reason,it got stuck on the gs 3 logo if I didn't flash another kernel.

Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app

cchrisrollins said:
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
No prob, just hit dat thanks button do you know where to get the kernels?

Zin0 said:
No prob, just hit dat thanks button do you know where to get the kernels?
Click to expand...
Click to collapse
I tryed the KT47 AOSP Jellbean kernel after flashing jelly bomb and it did the same thing it did before, black screen after flashing the samsung logo
Now I did go into fix permissions and it did say failed, is that abnormal?
This is my exact procces:
1. boot into TWRP
2. factory reset
3. system wipe
4. cache wipe
5. Dalvik wipe
6. Install from external SD: jellybomb v14
7. Wipe cache/Dalvik
8. Install Kt47 kernel
9. Wipe cache/Dalvik
Anything wrong there?

[Q] Help - Phone Only Boots into CWM Recovery

So I just an hour ago booted my phone and used FreeGee to unlock the bootloader and install ClockworkRecovery. I factory reset, cleared the cache and the Dalvik cache, and flashed the latest stable Cyanogenmod no problem. Ever since then, however, my phone will only boot into Clockwork, and not a single thing I do is helping. Is there anyone here who can help me with this?

Altamont_Wolfe said:
So I just an hour ago booted my phone and used FreeGee to unlock the bootloader and install ClockworkRecovery. I factory reset, cleared the cache and the Dalvik cache, and flashed the latest stable Cyanogenmod no problem. Ever since then, however, my phone will only boot into Clockwork, and not a single thing I do is helping. Is there anyone here who can help me with this?
Click to expand...
Click to collapse
Try this. Not sure if this is the same situation
http://forum.xda-developers.com/showthread.php?t=2523807&page=2
Check all of the threads but their unique solution is on the last post.

im having this problem too except im on Phill's recovery. @jimi_pooh thanks for the help but it's kind of vague. Im still confused on what the fix is. Is their a flashable cwm or twrp? I cannot find Madmack's hacked twrp either.

Altamont_Wolfe said:
So I just an hour ago booted my phone and used FreeGee to unlock the bootloader and install ClockworkRecovery. I factory reset, cleared the cache and the Dalvik cache, and flashed the latest stable Cyanogenmod no problem. Ever since then, however, my phone will only boot into Clockwork, and not a single thing I do is helping. Is there anyone here who can help me with this?
Click to expand...
Click to collapse
which version of CWM do you ave?

bor3d2damax said:
im having this problem too except im on Phill's recovery. @jimi_pooh thanks for the help but it's kind of vague. Im still confused on what the fix is. Is their a flashable cwm or twrp? I cannot find Madmack's hacked twrp either.
Click to expand...
Click to collapse
I'm on Philz too but not the updated one. That one seems to be having problems. I also see Esimon311 helped you out. Did that work? If not try using the first version of Philz recovery assuming you already had a lokied version of CWM running before this happened. It can be found in the General Section. The information I posted before was for ADB commands. I would not suggest that if you are not familiar with ADB.

jimi_pooh said:
I'm on Philz too but not the updated one. That one seems to be having problems. I also see Esimon311 helped you out. Did that work? If not try using the first version of Philz recovery assuming you already had a lokied version of CWM running before this happened. It can be found in the General Section. The information I posted before was for ADB commands. I would not suggest that if you are not familiar with ADB.
Click to expand...
Click to collapse
I was able to fix it. I found a download to madmack's hacked recovery and flashed beanstalk. Booted perfectly!
Sent from my LG-E980 using XDA Premium 4 mobile app

4.3 General wiping and preparatory instructions - Sprint Galaxy Note 2 L900 all ROM's

I was happy as a lark with TWRP. But 4.3 happened and it is a new process. There are variations, here is one way to get your phone and 4.3 to play nice together. I'm on Sprint Galaxy Note 2 and if you are coming to a 4.3 or 4.4 for the first time, or having trouble. Try this first! I give credits Below, but it's for all ROM's. "Google process stopped" is a common sign that this wasn't done. Or if it just hangs on the samsung screen... Btw it does seem like an eternity sometimes. Lol
General theory: skip to the next paragraph if you dont care. I've Googled and read. You should too. We are trying to clean and prepare your phone for 4.3. "Wipe" is not the same as "format. " We need to remove all the little pieces of data that may still be there from before. We need to start fresh. Also, the partitions sizes are different in 4.3. In general we need to clean.
PROCESS A is this link. Billard412 This is back to stock, completely cleaning your phone. It requires odin and a computer. If you want to try procees B alone, you can skip A and just do "process B" and see if that works. If you still have trouble, you know you need to do the full thing. Just a note, you might think it works, but then your nandroids don't restore.. Time for process A. Back to stock. It's good to do this once in a while to start fresh, also.
http://forum.xda-developers.com/showthread.php?t=2086769
Then install USE PHILZ recovery 6.07.9 (link below)
-Install philz. Some people have luck with TWRP , i didn't. I don't think TWRP works with 4.3
There is a newer Philz version, not sure all the bugs are worked out, use 6.07.9
One thing that might be confusing, the process A restore from billard recommends TWRP and I'm recommending Philz recovery. So best advice, although possibly confusing, is install TWRP, billard restore, then flash Philz. It's not any more work really. The back to stock will put you in a stock recovery. So you have to flash something. I was a TWRP fan too, but Philz has had less problems in 4.3.
1. You can follow billard 's instructions
2.there is a YouTube if you want to follow that in billards thread
or3 . Jlmancuso provided this to try and simplify the process:
a. Boot into download/bootloader mode.
b. Connect to pc and use odin to flash TWRP. Make sure you uncheck reboot and flash twrp in the pda slot.
c. Once flashed pull battery and disconnect from pc.
d. Press vol+ menu power buttons while inserting battery (yes it is difficult but can be done)
e. Now in recovery perform factory reset.
f. Flash this http://forum.xda-developers.com/showthread.php?p=36388145
g. Now reboot it will act/look weird but dont worry this is normal. It will reboot and take a long time to boot.
Now you are on stock mc2 (no knox anymore). Root using cf autoroot http://forum.xda-developers.com/showthread.php?p=33278464
Now use odin once again and flash your recovery again, this time Philz. Now you are rooted and have a custom recovery. Oh and you have a working phone again.
PROCESS B.
This is done before any ROM install and before any nandroid restore.
Preparation: BACK UP INTERNAL IF DESIRED, I WILL RECOMMEND WIPING IT in the next steps . NOT REQUIRED, BUT RECOMMENDED. You can move it to external, external doesn't need to be wiped.
In PHILZ recovery 6.07.9 (link below)
1. Mounts and Storage
Format / system​Format / cashe​Format / data​ Recommended optional. Format internal SD card
Format / data and /data /media (/sdcard) ALL INTERNEL SD CARD DATA IS LOST.​PREVIOUS IS NOT EXTERNAL, EXTERNAL IS "SDCARD1" which i would not recommend
2. Power Options > reboot recovery
3. Wipe cashe partition
4. Advanced > Wipe dalvik cashe
5. Wipe data / factory reset > Wipe data / factory reset
6. Wipe data / factory reset > clean and install new ROM
I would stick with 4.3 and Philz backed up things. Don't restore something from before. Neither a 4.2 rom or a TWRP backup. Once you know you have got this process down, then try / do those sorts of things. Philz is supposed to be able to do that, but let's keep it simple until you have this figured out.
If you want to try process B first only , it may be all you need. But if it doesn't work, do all of it.
I hope this helps - LINKS & CREDITS in next post

4.3 general wiping and preparatory instructions
LINKS
same as above Billard412 back to stock - http://forum.xda-developers.com/showthread.php?t=2086769
alternate back to stock - Rwilco http://forum.xda-developers.com/showthread.php?t=2591898
Philz Recovery Thread - http://forum.xda-developers.com/showthread.php?t=2552653
On the Philz recovery site the "L900" looks more like "l900" and is confusing - so here is a more direct link - select 6.07.9 http://goo.im/devs/philz_touch/CWM_Advanced_Edition/l900
TWRP http://teamw.in/project/twrp2/117
To get root- one option is CF Autoroot-
[SPH-L900] CF-Auto-Root
http://forum.xda-developers.com/showthread.php?t=1956180
WIFI FIX just in case. Flash in the PDA tab of Odin http://d-h.st/6qX
If you want to change modems i use this (not required / optional) - http://forum.xda-developers.com/showthread.php?t=2537713
General
I am not trying to take credit for anything. Notice how none of this is my work. Just hoping to pull together and clarify this process. Others my post different ways, and you can try other ways, but if it doesn't work, use this process exactly. It works for many. If you want to post that you tried another way and it didnt work, you are welcome to, but then my reply will be to try it this way...or i wont reply. I just had to keep typing this over and over to many, and i figured I would put out a detailed version. This works. (you know the drill, its your phone, not my responsibilty, of course)
CREDITS AND ROMS
I picked up a lot of this process from Lorjay589's thread. His OP pointed me at the Billard412 back to factory
jlmancuso has posted refined and explained this process 100 times as well.
this is for SMOOTHEST ROM, CUSTOM ROM, SYNERGY ROM, DIGIBLUR ROM, FTW ANNIHILATION, ROM AND MANY OTHERS.
therfore jlmancuso, chaz187, ianmb, digiblur, lorjay589, rwilco12, phil3759, fryingpan0613, jimmydene84, cbucz24, wwjoshdew, agent soap AND MANY OTHERS.

constructive criticism is always welcome i have a tough skin, just be nice and don't hold back to let me know. i am not that knowledgeable, this is my first thread. Just been following some 4.3 threads for a while and saw a recurring problem.

Very nice guide Cole
Sent from my SPH-L900 using Tapatalk

Reserved

Darn it I want a reservation too!!
Thanks now I have a thread to link to instead of a single post.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Very nice tutorial. U nail all that we need to do for a smooth install
Thanks
SGNote2

Any reason why we should not use the latest version of Philz Recovery version 6.15.4?

justppc said:
Any reason why we should not use the latest version of Philz Recovery version 6.15.4?
Click to expand...
Click to collapse
Some people have just had some problems when using the new version, therefore the previous version is more reliable. Better chance of everything working. Once you have your phone running smoothly using this process, you are welcome to try it. If you have problems... Revert back.
Start with post 87 of the Philz thread, if you like.
http://forum.xda-developers.com/showthread.php?t=2552653

Thanks, this resolved an issue with 'Inconsistent System UIDs"

KNOX with options A/B
Will this process A or B or both, untrip your knox and reset everything to stock? Or does it just get you closest to stock as you can, with KNOX still tripped?
Thanks

Dedline said:
Will this process A or B or both, untrip your knox and reset everything to stock? Or does it just get you closest to stock as you can, with KNOX still tripped?
Thanks
Click to expand...
Click to collapse
Process A completely wipes your phone and resets it to stock. B is just general wiping process when flashing a new rom. You shouldn't have a Rom on your phone when you are done with either. (other than the one backed on you external sd)
Head on over the the Ballard thread to read more about process A

justppc said:
Thanks, this resolved an issue with 'Inconsistent System UIDs"
Click to expand...
Click to collapse
This hasn't worked for me. I've repeated this several times with no luck. I also can't install gmail. Any suggestions?

mr.pope said:
This hasn't worked for me. I've repeated this several times with no luck. I also can't install gmail. Any suggestions?
Click to expand...
Click to collapse
You could try to start all the way over by using ODIN to install stock MA7, then root it and take it from there.

justppc said:
You could try to start all the way over by using ODIN to install stock MA7, then root it and take it from there.
Click to expand...
Click to collapse
alas, I have tried that as well. I finally made some headway and think I have it. I had to fix permisions for all apps using Rom Toolbox Lite Looks like that has fixed it. Flashing forward as I type.

Just a bump to keep this where everyone can see it.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Gotta try this on my note 2
K
Sent from my SPH-L710 using xda app-developers app

Just a reminder

Hello,
I ended up getting a replacement phone from Best Buy and I ended up flashing a older version of twrp before trying the latest 2.7.0. I did a few backups just to have a stock rom to return to if all failed. Somehow after I tried flashing the new mk4 roms, I lost my 4g LTE in the process of flashing different ROMS and none of my back ups for twrp would work so I ended flashing Philz recovery and then Digiblur just to get my phone working again.
I ended up requesting another replacement so I can have my 4g LTE again. My question is. Is it possible to wipe a 4g LTE key when rooting and also is Philz the way I should of went when I rooted to make a stock backup if everything fails? Anything I should make sure to back up in particular to make sure I dont wipe nothing important. I just want to be extra careful this time around.
The phone was already updated to MK4 when I received it. Any help is appreciated!

Lyvewire said:
Hello,
I ended up getting a replacement phone from Best Buy and I ended up flashing a older version of twrp before trying the latest 2.7.0. I did a few backups just to have a stock rom to return to if all failed. Somehow after I tried flashing the new mk4 roms, I lost my 4g LTE in the process of flashing different ROMS and none of my back ups for twrp would work so I ended flashing Philz recovery and then Digiblur just to get my phone working again.
I ended up requesting another replacement so I can have my 4g LTE again. My question is. Is it possible to wipe a 4g LTE key when rooting and also is Philz the way I should of went when I rooted to make a stock backup if everything fails? Anything I should make sure to back up in particular to make sure I dont wipe nothing important. I just want to be extra careful this time around.
The phone was already updated to MK4 when I received it. Any help is appreciated!
Click to expand...
Click to collapse
Philz is the only way to go when choosing a recovery. Twrp will not backup or restore mk4 properly and wont woek correct with 4.4 aosp either. When ypu do your first backup choose custom backup and backup everything but Efs. When that is done go back into custom backup and only backup efs (it must be done by itself). I would then suggest copying both backups to a pc or cloud storage for safe keeping.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Samsung Galaxy Note 4 Inaccurate Touchscreen, Can't Flash ROMs

touch screen bugging out
Ok so my phone for some reason can't click on the exact location i seem to want to press
idk i was trying to flash the silly roms you guys have around here. for stock galaxy note 4 spr
i've been flashing for a while
and it seems none of them work anymore
i use the latest TWRP even used the other one CWM or something like that
i used odin even up to .10 from 1.85 even lower and still can't
even when i install (seems to be the only rom i can cm12)
the locations i press on my screen are buged out. so i have to press higher than i should to even get a click and its hard to text or anything.
i did factory resets, cashe wipes. deleted partitions.. what am i doing wrong ??
why can't this annoying this go away what am i missing guys ???
and why is it only 1 rom can flash on my phone ?? and i can't go back to any lollipop or anything ??
(i also tried flashing a superSU from the tWRP .. when i used CM 12 and it all successed but still
i have this thing where i can't click anywhere im on my phone directly i have to try and feel it out.. please help

1)what software version are you on now?
2)what rom are you trying to flash?
Note4 Rocking a Hybrid Rom

Not long ago, it was discovered flashing the wrong recovery will mess up the lock-screen.
Some were solved with KIES firmware restore; no root, straight to dialer type *#2663# and then TSP FW update. If KIES won't update it, power down, pull battery 30 seconds, Odin stock tar and boot then the dialer code and update.
Do that after you determine which stock tar or KIES update is recommended from Your response above.
Sent from my SM-N910P using Tapatalk

schlepprock said:
1)what software version are you on now?
2)what rom are you trying to flash?
Note4 Rocking a Hybrid Rom
Click to expand...
Click to collapse
I am using
Cyanogenmod version
12.1-20150814-nightly-trltespr 5.1.1
kernel 3.10.40-gef59855
baseversion
N910PVPU4COG5
GALAXY NOTE 4 SPRINT
How ever im trying to flash back to stock evrything.
so that i can flash a rom that uses stock fetures of note 4 (windows mode etc)
the cm 12 does not utilize these and i need those badly.
so i tried to go back even factory reset wipe all cashes
but some reasn during all those fails my system UI says fail. and my touchscreen is not in sync correctly.
i heard of wiping system cache not sure if i done that but with TWRP i wipe everything but SD

it seems this has been a common issue the word we are looking for is calibration issues
it seems it happens to this person exactly how it is happening to me
there was a solution at the bottom but those buttons do not work for galaxy note 4 spr
does anyone know the codes for doing so ?
source:
http://forum.xda-developers.com/note-4-tmobile/help/touch-screen-issues-root-t2986883

Did you see post 3?
I suspect you need to flash OG5 first. Use KIES or Odin. I would suggest wiping all but ExtSdCard and factory reset or format data partition, then power off; pull battery 30 seconds prior to stock tar or KIES recovery.
There's a guide you can follow as well as the OP in this post/thread. But see the steps on post 3, this thread. Boot into stock right after stock flash to try to recover your touch screen. If your touch screen is OK, then follow the guide below to root stock.
http://forum.xda-developers.com/showthread.php?p=62241991
Sent from my SM-N910P using Tapatalk

NatsarYAhu said:
I am using
Cyanogenmod version
12.1-20150814-nightly-trltespr 5.1.1
kernel 3.10.40-gef59855
baseversion
N910PVPU4COG5
GALAXY NOTE 4 SPRINT
How ever im trying to flash back to stock evrything.
so that i can flash a rom that uses stock fetures of note 4 (windows mode etc)
the cm 12 does not utilize these and i need those badly.
so i tried to go back even factory reset wipe all cashes
but some reasn during all those fails my system UI says fail. and my touchscreen is not in sync correctly.
i heard of wiping system cache not sure if i done that but with TWRP i wipe everything but SD
Click to expand...
Click to collapse
I recommend you flash this rom. Mostly stock but very stable,and the developer is working on some goodies.
http://forum.xda-developers.com/showthread.php?p=62336588
I recommend that you back up everything you want to keep because you need to wipe everything EXCEPT external SD card. Wipe cache, dalvik , system, and data three times. Then factory reset three times and then flash this rom.
Note4 Rocking a Hybrid Rom

samep said:
Did you see post 3?
I suspect you need to flash OG5 first. Use KIES or Odin. I would suggest wiping all but ExtSdCard and factory reset or format data partition, then power off; pull battery 30 seconds prior to stock tar or KIES recovery.
There's a guide you can follow as well as the OP in this post/thread. But see the steps on post 3, this thread. Boot into stock right after stock flash to try to recover your touch screen. If your touch screen is OK, then follow the guide below to root stock.
http://forum.xda-developers.com/showthread.php?p=62241991
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Ok so this stock actually went through will get with you shortly to let you know if sync is fixed,
edit: still not synced correctly but phone does finally work how i want just the main problem is bugged trying the link with *#2663# now
Edit: IT WORKED !!! big UPS BRO thank you !!!

i have same problem after install twrp and flash custom firmware phone working fine but touch won't work
i tried that *#2663# but not working on custom rom any solution to solve touch problem on custom firmware
thanks

imeicodes said:
i have same problem after install twrp and flash custom firmware phone working fine but touch won't work
i tried that *#2663# but not working on custom rom any solution to solve touch problem on custom firmware
thanks
Click to expand...
Click to collapse
Odin stock tar and try again.
There's also an update to CFAR (Chainfire auto root) for Note 4. After you fix your touchscreen, root with it and make a TWRP backup once that is installed. A TWRP restore plus full un-root in SuperSU may make OTA possible; CFAR backs up stock recovery.
You can use Flashify to install custom recovery. You may have installed the wrong recovery to have the touch screen out of cal like it is.
Sent from my SM-N910P using Tapatalk