Develop Bugs

[Q] Stuck samsung screen even after odin stock

Hey guys hopefully you can help me. I was rooted for like 3 or 4 months now and have had not many problems or not anything I couldn't fix my self. My phone gets stuck on the Samsung Galaxy s4 screen anytime I reboot. I have tried different roms, different kernels, I even odin back to stock. I was using TWRP 6.0 then reverted back to TWRP 5.2 to see if that was causing the problem. Still have problems. I am going to re download the stock tar to see if it was a bad download but Odin checks the md5 and says it was good. Odin says passed every time also. Odin version is 3.07.
I get a error before and when trying to wipe dalvic cashe. I can wipe reg cash no problem. I think my phone is not mounting the internal storage when it reboots. I could be way off but need help asap. If I format super wipe with twrp then restart twrp and then factory reset I can install or restore a rom some times but still cant restart the phone. Any hope would be greatly appreciated.

EDIT
I wanted to edit my previous commet. LiquidSmooth seems to be running fine. So TW roms and GE roms **** up on my phone when I restart. so is it the internal systems when I have TW roms. I think it has something to do with partictions messing around maybe.
I like TW roms and want to continue to use them... Thank you

Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you

I got this problem a few days ago and found some topic including this one. You should check it out.
Well, what worked for me was Odin to stock firmware, root again, install recovery then custom rom. Now it's working fine. Try to downloading it again to see if it works. I downloaded mine from here, rooted and recovery it using this one.

TheAxman said:
Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you
Click to expand...
Click to collapse
+1 to what he said. I bet if you go into the stock recovery after odin flashing it will say something like cannot mount /data partition. Factory reset there, and it should fix that and make it mountable. (Its important to use the stock recovery factory reset after the odin, don't flash a custom recovery right after flashing)

This was incredibly helpful. I had the same issue. Thank you.
This is also applicable to the Verizon Wireless model.

Samsung GS3 (d2att) not booting but have TWRP Recovery available

Hello all-
I was just recently running CM 10.2 RC1 but had to do an install of the correct gapps as it was randomly rebooting. Well the device now is stuck on the Samsung Galaxy S3 screen with the BLUE cyanogen. I have access to TWRP and am able to reflash the .zip file for CM 10.2 RC1 yet it still won't boot? I did the wipe of dalvik, cache, data and system but still no luck? The device is NOT recognized in Odin. I just want to get the phone up and running again, even if it means root is lost.
Please help!!

DroidJay123 said:
Hello all-
I was just recently running CM 10.2 RC1 but had to do an install of the correct gapps as it was randomly rebooting. Well the device now is stuck on the Samsung Galaxy S3 screen with the BLUE cyanogen. I have access to TWRP and am able to reflash the .zip file for CM 10.2 RC1 yet it still won't boot? I did the wipe of dalvik, cache, data and system but still no luck? The device is NOT recognized in Odin. I just want to get the phone up and running again, even if it means root is lost.
Please help!!
Click to expand...
Click to collapse
Do you have it put into Download Mode before you plug it into the computer for Odin to recognize it? If I had it plugged in before I put mine in download mode Odin would not want to pick it up.'
Mr. Rageface

Mr.Rageface said:
Do you have it put into Download Mode before you plug it into the computer for Odin to recognize it? If I had it plugged in before I put mine in download mode Odin would not want to pick it up.'
Mr. Rageface
Click to expand...
Click to collapse
Yes it is recognized once in Download mode...sorry about that. What can I do to get it up and running? I am not new to flashing, etc so it's got me really upset that I cant get it to boot. What could possibly go wrong?

Get a sd card>download a new rom and put the rom in the sd card and flash like a normal ROM

http://fs1.d-h.st/download/00023/E5R/I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 You can download that file and put it in the PDA section once you run Odin and run it from there. This will put your phone back to the Stock Rom 4.1.1 and you can restart from there if you want.
Mr. Rageface

xXFl4sh said:
Get a sd card>download a new rom and put the rom in the sd card and flash like a normal ROM
Click to expand...
Click to collapse
I do have an sd card. Phone isn't recognized in Windows so Im not familiar with how I can get the ROM file onto the card from the computer? Can I download the latest AT&T Stock ROM and flash it via Odin?
What your saying is flash a ROM from the external SD card?

DroidJay123 said:
I do have an sd card. Phone isn't recognized in Windows so Im not familiar with how I can get the ROM file onto the card from the computer? Can I download the latest AT&T Stock ROM and flash it via Odin?
What your saying is flash a ROM from the external SD card?
Click to expand...
Click to collapse
No, with the file I told you to download you do not need to have a SD card because you can't boot into the rom you have Windows will not recognize the phone like normal to drag and drop to it. So with this file you can save it to your computer, Open Odin, put your phone into Download Mode, plug it into the computer so that Odin detects it. Then Click PDA and browse to the file you downloaded and tell it to use that file and then Run the process and it will install the original rom onto your phone.
Mr. Rageface
Edit: Sorry I did not realize your previous comment was to xXFl4sh.

Mr.Rageface said:
No, with the file I told you to download you do not need to have a SD card because you can't boot into the rom you have Windows will not recognize the phone like normal to drag and drop to it. So with this file you can save it to your computer, Open Odin, put your phone into Download Mode, plug it into the computer so that Odin detects it. Then Click PDA and browse to the file you downloaded and tell it to use that file and then Run the process and it will install the original rom onto your phone.
Mr. Rageface
Edit: Sorry I did not realize your previous comment was to xXFl4sh.
Click to expand...
Click to collapse
Ok I did the process with the file you referenced. Everything succeeded in Odin with no errors. It's still stuck on just showing the Samsung Galaxy SIII screen but now without the blue cyanogen? What is wrong with this phone??

DroidJay123 said:
Ok I did the process with the file you referenced. Everything succeeded in Odin with no errors. It's still stuck on just showing the Samsung Galaxy SIII screen but now without the blue cyanogen? What is wrong with this phone??
Click to expand...
Click to collapse
Can you get into recovery mode by any chance? If you can do that then it should be possible to do a factory reset from within Recovery Mode and possibly get you past the boot screen. If that doesn't help let me know and I will see what else I can find out for you. Also what all did you have checked and unchecked when you Ran Odin to reinstall the Stock Rom? If you had any of them other than Auto-Reboot on that may also have caused a problem http://forum.xda-developers.com/showthread.php?t=1722686 here is a forum that will show you how to use Odin. I apologize for not remembering about telling you what to check and uncheck. But try recovery mode first and do a factory reset and if that does not work, redo the odin install this time only having Auto-Reboot checked.
Mr.Rageface

Mr.Rageface said:
Can you get into recovery mode by any chance? If you can do that then it should be possible to do a factory reset from within Recovery Mode and possibly get you past the boot screen. If that doesn't help let me know and I will see what else I can find out for you. Also what all did you have checked and unchecked when you Ran Odin to reinstall the Stock Rom? If you had any of them other than Auto-Reboot on that may also have caused a problem http://forum.xda-developers.com/showthread.php?t=1722686 here is a forum that will show you how to use Odin. I apologize for not remembering about telling you what to check and uncheck. But try recovery mode first and do a factory reset and if that does not work, redo the odin install this time only having Auto-Reboot checked.
Mr.Rageface
Click to expand...
Click to collapse
Thanks man! I went back into Recovery and did a factory reset/wipe data and it finally got past that screen. Thanks again for your guidance and help. Any ideas as to what could have possibly caused the issue in the first place? I do want to re-root the device again and I am assuming my best bet is to flash a Stock ROM like you referenced with ROOT injected? What order should I follow, flashing a Stock w/Root injected...and then the Recovery of choice? Or vice-versa? What do you recommend?
Again, your timely responses were greatly appreciated. Was really worried I would have to take it to ATT.

DroidJay123 said:
Thanks man! I went back into Recovery and did a factory reset/wipe data and it finally got past that screen. Thanks again for your guidance and help. Any ideas as to what could have possibly caused the issue in the first place? I do want to re-root the device again and I am assuming my best bet is to flash a Stock ROM like you referenced with ROOT injected? What order should I follow, flashing a Stock w/Root injected...and then the Recovery of choice? Or vice-versa? What do you recommend?
Again, your timely responses were greatly appreciated. Was really worried I would have to take it to ATT.
Click to expand...
Click to collapse
It could have been several things that could cause the ROM to do that. I recommend that you make sure that your Bootloader is up to date and then go from there. Download the newest CWM, do a backup of your current rom so that you can flash back to it if you phone messes up. Then when you try to install a new ROM make sure you Wipe: Data then Cache, then Dalvik Cache in Advanced then Format /System. Then from there Install the new Rom, then install the correct GApps, then wipe Cache and Dalvik cache then Reboot into System. It takes messing up a few times to get it right but as long as you follow the guides pretty close and keep a good backup that you know works or keep the knowledge of how to Inject the Stock Rom to your phone when it messes up you shouldn't have much to worry about.
Mr. Rageface

Mr.Rageface said:
It could have been several things that could cause the ROM to do that. I recommend that you make sure that your Bootloader is up to date and then go from there. Download the newest CWM, do a backup of your current rom so that you can flash back to it if you phone messes up. Then when you try to install a new ROM make sure you Wipe: Data then Cache, then Dalvik Cache in Advanced then Format /System. Then from there Install the new Rom, then install the correct GApps, then wipe Cache and Dalvik cache then Reboot into System. It takes messing up a few times to get it right but as long as you follow the guides pretty close and keep a good backup that you know works or keep the knowledge of how to Inject the Stock Rom to your phone when it messes up you shouldn't have much to worry about.
Mr. Rageface
Click to expand...
Click to collapse
Sounds good. Thanks for the info. Obviously the device is not currently rooted or did the Factory Rom file you gave me have root injected? Do you have a recommended way of achieving Root with the Samsung SG3? Just installing a custom Recovery won't achieve Root, correct?
Thanks!

DroidJay123 said:
Sounds good. Thanks for the info. Obviously the device is not currently rooted or did the Factory Rom file you gave me have root injected? Do you have a recommended way of achieving Root with the Samsung SG3? Just installing a custom Recovery won't achieve Root, correct?
Thanks!
Click to expand...
Click to collapse
BTW, how can I confirm I have the most recent bootloader version? It looks like my phone's current baseband version is i747UCDLK3. I did download the boot_CWM_i747UCDMG2.zip file and put it on the internal storage. Do I just want to flash that file to update my bootloader?
Thanks again!
-Jay

Yea that is the newest baseband and yea you just flash it. As far as rooting the phone and everything I recommend this forum. http://forum.xda-developers.com/showthread.php?t=1725839 It has just about everything you could need to know!
Mr.Rageface

Mr.Rageface said:
Yea that is the newest baseband and yea you just flash it. As far as rooting the phone and everything I recommend this forum. http://forum.xda-developers.com/showthread.php?t=1725839 It has just about everything you could need to know!
Mr.Rageface
Click to expand...
Click to collapse
Thanks for the information. The phone that has been all screwed up and the reason I posted a thread in the first place is my gf's GS3. I have her's rooted again and running. I am going to update her baseband version and then install a custom ROM so she's up to 4.3.1. As far as mine goes, I have been fine. I myself also still have the outdated bootloader version. Is it ok to just flash that update for the bootloader without it doing anything wrong? I'm asking this since I'm rooted and running a custom ROM with no current problems. In other words, I don't want to end up saying "it wasn't broke, why did I mess with it" ? I did bookmark that thread you referenced in your last message. Damn that thread is LOADED with just about everything one would possibly need to know about Android and making it their own.
So my g/f accepted the OTA update today (not knowing obviously) and she got updated to 4.3 via AT&T, unfortunately!! I attempted to flash the latest Liquid Smooth ROM and I continue to get a FAILED message during installation. It mentions a bunch of bootloader numbers ( I am assuming the only ones this ROM is compatible with?) So is there any way to roll the bootloader back to a compatible one or just go a different route for the custom ROM?
Also, I attempted flashing the file to update my baseband yet when I so into the device, it doesn't show as having the updated version? Is there a different way of doing it or maybe a different file?

I'm not to sure about the troubles that may come about since your gf went with the 4.3 OTA but If I am not mistaken it will need to be downgraded before you try doing anything else to it and if it is not showing that you updated your bootloader on your phone I recommend grabbing the App called Root Checker to double check then look for another file, tho unless it failed it should have updated it or messed up your phone one.

[Q] Can not flash any custom rom to GT-P5210

Hello,
I can not flash any ROM to my GT-P5210 Tab anymore.
I was on BinDroid ONE P5210 LITE V3.0.0, but since it is discontinued
and 2 other ROMs rolled out over the past days I wanted to give it a try.
- went back to stock with official firmware from "sammobile" for my device,
- flashed TWRP with Odin 3.07
- flashed ROOT with Odin
- went to recovery did factory reset + dalvik/cache (
- flashed new ROM (neither ROM Pimpdroid or Grievous is working)
after flashing Tab goes into a bootloop to recovery. First boot after flash takes some time in the Galaxy Tab3 Logo but in the end it reboots into TWRP. I have tried CWM too with the same results.
I am not totaly new to flashing, did it with my I9000 and now with my I9300 int. but with this Tab3 now I am lost.
Any ideas are much appreciated.
regards and sorry for my english its not my native tongue

zerodv8 said:
Hello,
I can not flash any ROM to my GT-P5210 Tab anymore.
I was on BinDroid ONE P5210 LITE V3.0.0, but since it is discontinued
and 2 other ROMs rolled out over the past days I wanted to give it a try.
- went back to stock with official firmware from "sammobile" for my device,
- flashed TWRP with Odin 3.07
- flashed ROOT with Odin
- went to recovery did factory reset + dalvik/cache (
- flashed new ROM (neither ROM Pimpdroid or Grievous is working)
after flashing Tab goes into a bootloop to recovery. First boot after flash takes some time in the Galaxy Tab3 Logo but in the end it reboots into TWRP. I have tried CWM too with the same results.
I am not totaly new to flashing, did it with my I9000 and now with my I9300 int. but with this Tab3 now I am lost.
Any ideas are much appreciated.
regards and sorry for my english its not my native tongue
Click to expand...
Click to collapse
did u try root check app to c if u r truly rooted? is ur su updated? if so try reflashing the recovery...n the root file. do u have the stock kernel?

THink I Got a fix
This worked for me. The TWRP does NOT actually wipe anything. go to settings in whatever rom you are running, and do a factory data reset from there. Let it wipe all app data and EVERYTHING. Then go through the steps to install whichever ROM you want. It worked for me!! Post back and let me know if it worked for you too. I tried for 3 days to install anything, and this is the only thing that worked.:victory:

Tquarter said:
This worked for me. The TWRP does NOT actually wipe anything. go to settings in whatever rom you are running, and do a factory data reset from there. Let it wipe all app data and EVERYTHING. Then go through the steps to install whichever ROM you want. It worked for me!! Post back and let me know if it worked for you too. I tried for 3 days to install anything, and this is the only thing that worked.:victory:
Click to expand...
Click to collapse
ok did read your post before trying to flash. i lost my back up and as well as my emmc. so i need a stock firmware only problem I now have is downloading one. Three quarter of links r dead and the three i have tried have had errors. Can you help me anyone with a google drive or box download of an unknown region stock firmware so I can breathe light in t o my brick please

https://db.tt/63atdfRZ Here ya go!
I'm uploading a stock firmware that can be flashed using ODEN. I have not tried this file, I just downloaded it, before I flashed anything, in case something went wrong. I'll post the link when it finishes uploading. Good luck! Post back and let us know how it went.

solved
Tquarter said:
This worked for me. The TWRP does NOT actually wipe anything. go to settings in whatever rom you are running, and do a factory data reset from there. Let it wipe all app data and EVERYTHING. Then go through the steps to install whichever ROM you want. It worked for me!! Post back and let me know if it worked for you too. I tried for 3 days to install anything, and this is the only thing that worked.:victory:
Click to expand...
Click to collapse
I tried your method and it worked. Another thing that works is first thing when you enter TWRP check if system is mounted, if not tick mount and then wipe the way installation of the rom suggests. This worked for me too. Thanks for ur time and the fish

Oh cool, I'm glad to help. I also tried to manually mount system, but untill I got that first ROM installed, it just un-mounted itself again. I hope these problems will be sorted out. Both recoveries act choked down somehow. (TERP, CWM) Looks like "source manifest CM 10.2 "thread is making exciting progress. I can't stop watching it. Most of it is over my head, but google helps me, in trying to grasp what they are saying.

Tquarter said:
Oh cool, I'm glad to help. I also tried to manually mount system, but untill I got that first ROM installed, it just un-mounted itself again. I hope these problems will be sorted out. Both recoveries act choked down somehow. (TERP, CWM) Looks like "source manifest CM 10.2 "thread is making exciting progress. I can't stop watching it. Most of it is over my head, but google helps me, in trying to grasp what they are saying.
Click to expand...
Click to collapse
can someone recommend a clean rom for gt-p5210

OMG HELP! Bootloop, download modes works, flashed with Kies and STILL bootlooping

I have the SGH-M919
I've rooted my phone and was running a GE rom
Everything was fine for MONTHS
Got in my car and plugged my AUX cable to my phone for music and the phone froze.
Force rebooted the phone and it started boot looping.
Rebooted to recovery (TWRP) and TRIED to wipe dalvik and cache and it FAILED, said it couldn't mount dalvik
Rebooted to recovery again and wiped all partitions and this time it worked so I proceeded to re-install GE rom, still bootlooping
Came home and tried to use ODIN to flash M919UVUAMDL and it failed.
Tried ODIN to flash M919UVUEMK2, also failed (sorry don't have the error messages right now)
Rebooted phone into download mode again and phone said there was an issue and to use Kies to recover
Installed Kies and started emergency recovery and that went through fine and the phone finished and STILLLLLLL BOOT LOOPS !!!!!!!!!!!
Copied the file that Kies downloaded (M919UVUFNB4) and tried ODIN again to flash that and it flashes fine but STILLL BOOT LOOPS
Obviously my Knox warranty flag is tripped and I don't have the money for the insurance right now.... so PLEASE FOR THE LOVE OF BOB does anyone have any other diagnostic tips or tricks to help me figure out why the F this phone is boot looping.

53 views and no replies.... come on people... someone HAS to have something that might help..
Anyone know if ANY possible way to reset the knox warranty void flag ?

avelis26 said:
53 views and no replies.... come on people... someone HAS to have something that might help..
Anyone know if ANY possible way to reset the knox warranty void flag ?
Click to expand...
Click to collapse
Only Samsung can reset your Knox flag. You can't expect instant responses here. People read and answer the questions they know how to. Not doing a full wipe before installing a different ROM often causes soft bricks and bootloops. I would start there although that doesn't explain why you couldn't mount Dalvik. Try a different recovery. Many people have had trouble with TWRP. Philz Touch works well if you haven't already tried it.
Sent from my SGH-M919 using xda app-developers app

I literally just had the exact same problem as you. I googled and found http://forum.xda-developers.com/showthread.php?t=2265477, then googled some more and found my .tar file for my phone, then odined back to stock 4.2.2. It took 20 min.

lalec said:
Only Samsung can reset your Knox flag. You can't expect instant responses here. People read and answer the questions they know how to. Not doing a full wipe before installing a different ROM often causes soft bricks and bootloops. I would start there although that doesn't explain why you couldn't mount Dalvik. Try a different recovery. Many people have had trouble with TWRP. Philz Touch works well if you haven't already tried it.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
1. Samsung WON'T reset my flag... they won't even TOUCH the phone in any way shape or form. I spent almost two hours dealing with them and being honest about the situation. And they STILL won't do anything at all. The rep I was speaking too even said the first thing they do is check that flag and if its popped, they put it back in the box and send it back with no further action. So I will not buy form Samsung ever again.
2. I'm not expecting instant responses at all and nothing I said should have been interpreted at such. I made the comment of 53 views in 4 hours and not a single reply ... I was hoping for a better ratio of responses than that.
3. Where are you getting "Not doing a full wipe before installed a different ROM..." I never said that I didn't... and if you read what I took the time to organize neatly, I specifically state that full wipe was what I tried BEFORE re-installing the SAME rom.
4. Can't try a different recovery if I can't even get the stock factory image to do an initial boot.

cybervyrus8587 said:
I literally just had the exact same problem as you. I googled and found http://forum.xda-developers.com/showthread.php?t=2265477, then googled some more and found my .tar file for my phone, then odined back to stock 4.2.2. It took 20 min.
Click to expand...
Click to collapse
Which one did you flash ?
M919UVUFNB4
M919UVUEMK2
M919UVUAMDL
M919UVUAMDB
I've tried #3 but it gives me an auth failure....

Just ODIN philz on there. TWRP has given me issues on this phone off and on. Philz will let screw around in there. Your phone isn't dead, it just needs some love

TigerDNA said:
Just ODIN philz on there. TWRP has given me issues on this phone off and on. Philz will let screw around in there. Your phone isn't dead, it just needs some love
Click to expand...
Click to collapse
lol ummm ok I'm glad to hear that but how would flashing a recovery fix the fact that the factory stock image won't even work Not being a ****... I really do want to know

avelis26 said:
lol ummm ok I'm glad to hear that but how would flashing a recovery fix the fact that the factory stock image won't even work Not being a ****... I really do want to know
Click to expand...
Click to collapse
Post deleted
☞ Sent from here ☜

baseballfanz said:
Post deleted
☞ Sent from here ☜
Click to expand...
Click to collapse
Sooooo umm what ?
Anyway... I flashed PhilZ on my phone, did full wipe, tried installing the same GE rom I was using... didn't work.
Tried installing stock rom, didn't work.
Tried flashing M919UVUFNB4 via ODIN... and it flashes fine but again, first boot wont work.

Ok so .... I guess installing PhilZ... then full wipe, then flashing M919UVUFNB4 TWICE back to back did the trick.... no freaking clue how but it worked

I spoke too soon. Went through first boot. Got all the way to the end setup and then it rebooted on its own ... and now its stuck in a boot loop again

avelis26 said:
Sooooo umm what ?
Anyway... I flashed PhilZ on my phone, did full wipe, tried installing the same GE rom I was using... didn't work.
Tried installing stock rom, didn't work.
Tried flashing M919UVUFNB4 via ODIN... and it flashes fine but again, first boot wont work.
Click to expand...
Click to collapse
Since your using philz, choose install new ROM, then go to advanced and wipe dalvik, THEN go to mounts and select the one close to the bottom, wipe SD/data or something..... This will wipe your internal SD, OK so then install your rom and reboot.....
I am starting to think you flashed a non GE kernel and didnt realize it You just got to give the phone some love, thats all. It knows when your upset you know.

TigerDNA said:
Since your using philz, choose install new ROM, then go to advanced and wipe dalvik, THEN go to mounts and select the one close to the bottom, wipe SD/data or something..... This will wipe your internal SD, OK so then install your rom and reboot.....
I am starting to think you flashed a non GE kernel and didnt realize it You just got to give the phone some love, thats all. It knows when your upset you know.
Click to expand...
Click to collapse
lol
The weirdness continues
sooo it started boot looping again. Then I rebooted to recovery (which obviously after flashing NB4, its no longer PhilZ) and did factory reset. Now its working again with latest firmware.
Also I flashed the GE rom from HERE in XDA and used it for like 2 or 3 months then it suddenly stopped working so I don't think the kernal was the issue... I'm so freaking confused

avelis26 said:
lol
The weirdness continues
sooo it started boot looping again. Then I rebooted to recovery (which obviously after flashing NB4, its no longer PhilZ) and did factory reset. Now its working again with latest firmware.
Also I flashed the GE rom from HERE in XDA and used it for like 2 or 3 months then it suddenly stopped working so I don't think the kernal was the issue... I'm so freaking confused
Click to expand...
Click to collapse
Flash something else, GE is boring, Flash something crazy like Slim or something, that might work... Possibly it could be a bootloader issue, did you ever get on the MK2? Maybe you got one of the female phones. Sammy made some by mistake. they can be real finicky every now and then, like they work just fine most of the time, but about once a month or so they just crap out. Could be that too.

TigerDNA said:
Flash something else, GE is boring, Flash something crazy like Slim or something, that might work... Possibly it could be a bootloader issue, did you ever get on the MK2? Maybe you got one of the female phones. Sammy made some by mistake. they can be real finicky every now and then, like they work just fine most of the time, but about once a month or so they just crap out. Could be that too.
Click to expand...
Click to collapse
No never got MK2... went straight to NB4
And I LIKE GE lol...
Well whatever happened it seems stable again now currently on stock NB4
Next thing to check is if the knox warranty flag is still tripped... Do you know how to do that ?

Yea your Knox flag is tripped alright, you have zero chance if ever getting back to 0x0.... Nobody knows how to do that brother.
Sent from my GT-I9505G using xda app-developers app

avelis26 said:
No never got MK2... went straight to NB4
And I LIKE GE lol...
Well whatever happened it seems stable again now currently on stock NB4
Next thing to check is if the knox warranty flag is still tripped... Do you know how to do that ?
Click to expand...
Click to collapse
Just put the phone in download mode. Power off then volume up, home and power. You'll see it when you get into download mode.

TigerDNA said:
Just ODIN philz on there. TWRP has given me issues on this phone off and on. Philz will let screw around in there. Your phone isn't dead, it just needs some love
Click to expand...
Click to collapse
Philz's and TWRP both had small glitches on the GS4 4.2.2 Stock Rom.
I downloaded and installed the OUDHS-Recovery-jfltetmo-1.0.3.3.tar and have it all PERFECT now! You can search using exactly that filename and download it for your use. IT IS THE flashable Recovery Version.
I can, using Rom Manager, NAME THE BACKUP before booting into recovery, and it makes the backup just as I named it!
I can also recover using Rom Manager, and visually select what backup file I want to restore to, again, before booting into recovery!
CWM type backups take longer then TWRP backups to complete, but I have not had any instance that a backup I made couldn't be restored.
I did have that problem using "TWRP" and "On Line Backup". (No longer do I trust using those)
Hope this info helps your decision!
Good Luck and Aloha!

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