NO PiT Partition - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

NO PiT Partition - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

Hello guys im in need of some help I currently have the note 7 but have to go back to my note 4 due to the recall. The problem is that sprint sent an update to my note 4 that I guess it didnt like. I was only able to access downlaod mode. I attempted to flash the N910PVP assuming that was correct im at a lost any help would be greatly appreciated.

Whenever I press vol up power and home I get a message saying mmcread failure in smll print and then firmwre update encountered a issue please select recovery mode in kies but I cant kies wont recognize my phone.

The title of thread- no PIT partition- is that what happens when trying to flash full stock tar in Odin?
If so, The Sprint variant PIT can be found in the Sammobile forums. It's not acceptable to post competitive external forum links so you need to Google search it *Sammobile PIT Note 4* (without asterisks) will find the thread. There's a Note 4 thread with PIT by model number listed. Make sure you know the actual model of your phone; you can use Phone Info for Samsung in Google Play to verify that. Sprint model # is SM-N910P.
If you don't know how to partition with PIT, you should ask how to for Sprint variant in that forum. TBH, I don't know and I don't advise risky procedure steps when I'm not familiar with them. I've been fortunate not to experience this but update is one of the primary theories that causes this.
From what I've read, your problem may be terminal with eMMC failing you. IMO, it's unknown if eMMC is lacking durability, updates corrupt partitions and can't be overwritten or bad battery plays a role? But I'd recommend a fresh new battery- fully charged to be installed before attempting this recovery method.
If you get lasting resolution from this condition, please share. There's been a number of failures that later lead to permanent inability to boot to system, recovery or download mode. Some users didn't share relevant updates until asked about it, later.
Sent from my SM-N910P using Tapatalk

Related

[Q] Changing IMEI on Samsung Nexus S legitimate reason, read on please.

I'm quite new to Odin but have spent the last 2 days researching it and its uses..
The problem I have, is that I flashed a ROM from over at Samsung Nexus S forum along with about another 25-100 people, the ROM in question re-wrote the IMEI numbers on all the phones to the same number, causing some networks in some country to deny access and in other countrys not causing any imidiate problems, but that could change anytime.
I've read that if I flash back to stock with Odin with a .pit file and Re-Partition ticked, that Odin will cause the phone to re-write all partitions and correct this.
NOW PLEASE CORRECT ME IF I'M WRONG. or point me in another direction if you know of one.
I've got the correct ROM for my region but cant find the Samsung Nexus S .pit file anyware.
Can someone tell me if I have to use a specific .pit file for the Samsung Nexus S and if so where I can download it from.
Many thanks in advance.

check this site ull have to register through
samfirmware. com

i had to make a space between "dot" and "com" because of the sites new members politicy

Need Help with Note2 root problems

http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=32466314
I followed the directions outlined in the topic I linked to above to root my Samsung Galaxy Note 2.
However once the rooting process was done my phone came back on and it was completely unable to read the sim card.
Not only that it wouldn't stay on. After 5 minutes the screen would go black however the power would still be on as I can see my led light flashing that I'm receiving messages and alerts.
To hopefully fix this I went ahead and unrooted my phone using the same application in the topic linked to above and the results are that it still won't read my sim and it the power issue is the same.
Can someone please help me out with this and provide the instructions I need to return my phone back to what it once was.
Then can someone also provide a reliable way of rooting the Samsung Galaxy Note 2 that won't cause my phone to become unresponsive.
Thanks

http://forum.xda-developers.com/showthread.php?t=1896696
Follow the link above, this is the most comprehensive guide to all member.
Make sure your devices model is n7100.
Good luck.
---------- Post added at 07:59 PM ---------- Previous post was at 07:54 PM ----------
If I were you, I will check my model number and go www.sammobile.com download the relative stock rom and flash it thru pc odin before proceed to rooting process.
Dont worry all member here are willing to give help. My time already 3am morning..gonna sleep. If you have any problem you can pm me or post your question here, other member would be helping you.
Good luck mate.
Sent from my GT-N7100 using xda premium

My model number is Samusng - SGH - I317.
I don't believe that I'm in the correct area can someone please point me in the right direction.
Also to avoid creating another topic if I am in the wrong area can someone move this topic there please.
Thanks

ebobbylee said:
http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=32466314
I followed the directions outlined in the topic I linked to above to root my Samsung Galaxy Note 2.
However once the rooting process was done my phone came back on and it was completely unable to read the sim card.
Not only that it wouldn't stay on. After 5 minutes the screen would go black however the power would still be on as I can see my led light flashing that I'm receiving messages and alerts.
To hopefully fix this I went ahead and unrooted my phone using the same application in the topic linked to above and the results are that it still won't read my sim and it the power issue is the same.
Can someone please help me out with this and provide the instructions I need to return my phone back to what it once was.
Then can someone also provide a reliable way of rooting the Samsung Galaxy Note 2 that won't cause my phone to become unresponsive.
Thanks
Click to expand...
Click to collapse
first be sure about the make of your phone n7100 / n7102 or n7105 / T889 than flash the specific root file and yes the stock rom can be flashed just to be sure if it start detecting sim card again and do even chk ur sim on other device if it wrking on dat.

Hopefully you haven't lost your imei no.
Sent from my GT-N7100 using xda premium

ebobbylee said:
My model number is Samusng - SGH - I317.
I don't believe that I'm in the correct area can someone please point me in the right direction.
Also to avoid creating another topic if I am in the wrong area can someone move this topic there please.
Thanks
Click to expand...
Click to collapse
your answer lies here flash the file found here http://forum.xda-developers.com/showthread.php?t=2159652 for i 317 and search for your custom rom here http://forum.xda-developers.com/forumdisplay.php?f=1870 and after rooting just to be on the safer side do efs backup http://forum.xda-developers.com/showthread.php?t=1922473 and if you are doing it through toolkit it must be option 51 for 4.1.1 and option 52 for 4.1.2 Jb

I am not very advanced at all when it comes to flashing and rooting.
It's hard for me to just go and flash my phone that's why I had used that simple program that I linked to in the OP.
I just looked in the settings on my phone it it says
Mobile Network Type = Unknown
Service State = Out of service
My phone number = Unknown
IMEI = Unknown
IMEISV = Unknown
Device Status = Modified
I could really use some exact instructions on what stock rom for the note 2 is best and step by step instructions on how I flash it on.
I could also use some help with finding step by step instructions on how to root my note 2 successfully without running into this problem again.
Thanks

ebobbylee said:
I am not very advanced at all when it comes to flashing and rooting.
It's hard for me to just go and flash my phone that's why I had used that simple program that I linked to in the OP.
I just looked in the settings on my phone it it says
Mobile Network Type = Unknown
Service State = Out of service
My phone number = Unknown
IMEI = Unknown
IMEISV = Unknown
Device Status = Modified
I could really use some exact instructions on what stock rom for the note 2 is best and step by step instructions on how I flash it on.
I could also use some help with finding step by step instructions on how to root my note 2 successfully without running into this problem again.
Thanks
Click to expand...
Click to collapse
there is no huge process just get a stock rom which is compatible for your device make sure usb debugging is enabled in device then open odin,
get your phone in download mode and connect to pc , on the PDA search for .tar file you downloaded and make sure the odin detects your device and start flashing.
search in youtube there are many videos too.

So I followed the instructions http://forum.xda-developers.com/showthread.php?t=2052779 there to try and un-root my phone however I am still with the same results.
The phone reads my IMEI number as unknown and it still cannot read my sim card at all. My power comes on but once it goes inactive it stays off and to turn it back on I have to take the battery out, replace it, then power back on only for it to do the same thing and the process to be repeated once more.
I could really use some step by step instructions say for instance is there another way I can go about restoring stock ware on the phone. If so where are the links to the programs I need to download and what is the sequence I use those programs exactly to restore my phone back to stock. What commands and instructions need to be done within those programs.
I would like to root my phone once it's been returned back to a working functioning status as I cannot make calls or anything right now. I was looking at putting Cyaneogen Mod on it however if there is a better software I would appreciate if you could point it out. What programs do I use and how do I use those programs exactly so that I don't end up with the same result that I have right now where I
m unable to do anything with my phone.
I really hope someone helps me at the level I'm asking. I know it's a lot but I will be really grateful for the assistance.

Hey guys new here..need some help.

I attempted to root my Galaxy S3 (SCH-530M) From Metro PCS. I used odin and follow instructions carefully. I have rooted other phones this is my first problem I have ever stumbled upon this problem. I used a toolkit which allowed me to ROOT my phone but now I only get "Galaxy S3" logo and then screen turns black. I can boot into "safe mode" it shows clear cache, factory reset, ect.
I tried to follow instructions here:http://forum.xda-developers.com/showthread.php?t=2219755
Here are errors I received:
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
"Secure Check Fail" Sbl1 message. shows on my phone.
I am little frustrated been at this since 10am it is now 5PM. I can boot into recovery mode, phone turns on starts and everything but it stays on black screen and my led on top left side flashes bright blue.
Any info is a major thank you. I wish I can here to contribute but sadly I am in this bind.....I attached a screenshot from my desktop to show you guys what errors say.

The first thing you need to know is not all S3's are the same. Never flash anything not for your model phone.
The second is yours is an older metro model from when they were tied to Sprint I think it was. What this means is that it's a variant of Sprints model, and so you will be better off using their forum for future flashes and help. Do not flash anything you find here. They are not compatible.
Third is I don't recommend the toolkit. It's usually out of date and while it was helpful to some in the beginning, it now seems to cause more problems than anything. If you want root, search for root66 firmware in the Sprint forum. He may have your version there as well.
Finally, I didn't read the thread you linked, but 95% of the time, a factory reset will solve the hanging at boot.
I also highly recommend reading the stickies threads. Lots of great info you should know about and there are several methods to gain root.
For the Odin problem. Makes sure kies is NOT installed, try different cables and different usb ports.
Sent from my SCH-I535 using Tapatalk 4

DocHoliday77 said:
The first thing you need to know is not all S3's are the same. Never flash anything not for your model phone.
The second is yours is an older metro model from when they were tied to Sprint I think it was. What this means is that it's a variant of Sprints model, and so you will be better off using their forum for future flashes and help. Do not flash anything you find here. They are not compatible.
Third is I don't recommend the toolkit. It's usually out of date and while it was helpful to some in the beginning, it now seems to cause more problems than anything. If you want root, search for root66 firmware in the Sprint forum. He may have your version there as well.
Finally, I didn't read the thread you linked, but 95% of the time, a factory reset will solve the hanging at boot.
I also highly recommend reading the stickies threads. Lots of great info you should know about and there are several methods to gain root.
For the Odin problem. Makes sure kies is NOT installed, try different cables and different usb ports.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Thanks for advice but I think you missed a few things I pointed out. I am using a Metro PCS S3 the model you linked me too for root66 .tar is for Verizon S3 not Metro PCS. Verizon is i535 and mines is R530M would that also mess up my phone even more? I HAVE tried factory reset and cache wipe. Nothing is working phone stays stuck on black screen AFTER boot logo.
I went o sprint forums they told me my phone is NOT the same as theirs. I am aware of various S3 models it was many said to use ODIN and it caused me a world of problems right now.

Vepar_S said:
Thanks for advice but I think you missed a few things I pointed out. I am using a Metro PCS S3 the model you linked me too for root66 .tar is for Verizon S3 not Metro PCS. Verizon is i535 and mines is R530M would that also mess up my phone even more? I HAVE tried factory reset and cache wipe. Nothing is working phone stays stuck on black screen AFTER boot logo.
I went o sprint forums they told me my phone is NOT the same as theirs. I am aware of various S3 models it was many said to use ODIN and it caused me a world of problems right now.
Click to expand...
Click to collapse
I couldn't be sure if mrRobinson had made the root66 firmware for your model or not. If he did it would've most likely been in Sprints or maybe Verizon's root66 threads. All I meant was for you to check their threads to see if your variant was there. In ours, for example, there is also the T999V firmware, which is related to our T999, but is different.
What I am fairly sure of is your model is a CDMA device, like Sprints and Verizon's. T-Mobile and AT&T are GSM. When T-Mobile bought metro they stopped offering the R530, and replaced it with the T999N. Prior to this several people asked me for help with their R530M, and the best I could do was direct them to Sprints forum where others had posted about that model.
I suggested going there because there are people with the same model and they may have run into similar issues. And even if they haven't the rest of the info in that forum would be more relevant to your device than what you find here.
I'm not sure why you are having trouble with Odin. I've seen in other models forums where sometimes you may need something more, or something different than just the stock firmware. I don't know if that could help you or not, so I'm just trying to get you pointed in the direction where you might find someone who can.
There are some issues that are universal with things like Odin, but usually it ends up being a problem with the computer, the usb cable, bad/corrupted downloads, etc. Which is why I mentioned those. But you mentioned an error that showed on your phone, an sbl1 secure boot error or something like that. To my knowledge none of the GSM devices have ever shown this. Not that I remember anyway. But it may have something to do with a locked boot loader like Verizons, or it could be something entirely different. But again, you'd likely have better luck finding similar problems in the others forums.
If you can verify some roms that will work on yours, you may consider flashing CWM or TWRP using Odin. Then try flashing the Rom from recovery, factory reset and reboot. May not help, but it's something to try. Also, make sure you downloaded the latest firmware for your model and try it again.
If I get a chance I'll try to help find out more for you. But for now I hope that helps clarify what I was saying before and helps get you pointed in the right direction.
This would be a bit of a long shot, but you could go to your local store and see if they will offer some sort of trade for the T999N. (Doubtful, but it can't hurt to ask) Now that metro is with T-Mobile, you're likely to get better service with it, unless they've got something worked out where devices like yours can still use Sprint towers/networks.
Sent from my SCH-I535 using Tapatalk 4

[Q] Bricked T999L Failed Bootloader update

Hi! I need some serious help. I accidentally bricked my phone while updating the Bootloader.
It's a Samsung Galaxy S3 SGH-T999L (T-Mobile, but it works with my Vodaphone SIM)
Absolutely nothing on the screen, no boot, no recovery mode (just installed CWM), no download mode. Just a red LED when plugged in via USB.
Device Manager shows this: "QHSUSB_DLOAD"
I live in Egypt so there's no such thing as 'insurance' or 'warranty'.
I tried the instructions here: http://forum.xda-developers.com/showthread.php?t=2439367
Didn't work.
Is this the end? Or is there yet hope for it?

Need to know the details of what you flashed and what steps you followed.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Need to know the details of what you flashed and what steps you followed.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I just installed the CWM custom recovery via Android Toolkit, and was preparing to flash Cyanogen. It said that an S3 needed a Bootloader update to install Cyanogen versions greater than 10.1, So I followed the links and I think I accidentally flashed the Bootloader for SGH-T999 (not the T999L).
CWM said it succeeded, rebooted the phone (did not fix root when it asked), and it just never turned on since (it's been a while)

P.s: Idk if this even matters when its as deep as the Bootloader, but the phone had been rooted for months before.
Oh, and I found this and am downloading the latest T999L in case I need it if ODIN can help: http://forum.xda-developers.com/showthread.php?t=2439367
And from yet more Google I found these drivers, but it won't let me post outside links
But Device Manager says "Driver is not intended for this platform."
That's all I got so far, will keep looking for a good driver and check this thread as often as I can

This is gonna probably sound stupid, but I tried an emergency recovery with Kies, but it needed me to get it in Recovery Mode.
No change so far. Any help finding the right drivers would be very helpful.

Kygies27 said:
This is gonna probably sound stupid, but I tried an emergency recovery with Kies, but it needed me to get it in Recovery Mode.
No change so far. Any help finding the right drivers would be very helpful.
Click to expand...
Click to collapse
YAY! Found working drivers here: http://forum.xda-developers.com/showthread.php?t=1536354&page=4
By: richardlibeau
ATTACHED FILES
File Type: zip QHSUSB_Drivers_(x64).zip - [Click for QR Code] (72.3 KB, 568 views)
File Type: rar qhsusb_dload_Drivers.rar - [Click for QR Code] (56.0 KB, 584 views)

More Google (Where is everybody?)
Found this: http://forum.gsmhosting.com/vbb/f824/karbonn-a9-dead-qualcomm-hs-usb-qdloader-9008-how-fix-1740061/
It seems if I can just find the corresponding hex files, etc, this could work.
Or I could somehow reprogram my CPU and make things even worse...
I'm really stuck now.
P.s: I've ofc by now seen nearly everyone go for a JTAG repair. I will check the shops around here when they open, but I don't know if they can do anything about it.

Jtag should be able to repair that kind of brick. Unfortunately, when its due to flashing a different devices firmware, our device methods won't usually work.
You can try the d ebrick method we have posted in development, but just don't expect much. (You never know though, you might get lucky).
I doubt following this instructions will work as they are for a different device. Big risk to try it imo. Might make it non-recoverable by any means. (The process might work, I don't know, but you'd likely need specific files for your device).
Jtag is probably your best option. And in the future, stay away from the toolkit! Its bricked a number of devices and the dev just ignores support requests, even from those who buy it...
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Jtag should be able to repair that kind of brick. Unfortunately, when its due to flashing a different devices firmware, our device methods won't usually work.
You can try the d ebrick method we have posted in development, but just don't expect much. (You never know though, you might get lucky).
I doubt following this instructions will work as they are for a different device. Big risk to try it imo. Might make it non-recoverable by any means. (The process might work, I don't know, but you'd likely need specific files for your device).
Jtag is probably your best option. And in the future, stay away from the toolkit! Its bricked a number of devices and the dev just ignores support requests, even from those who buy it...
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yeah, shops open soon so hopefully I can see what can be done.
I figured not to bother with the qualcomm tools, messing with things I didn't quite understand was how I got in this trouble in the first place.
But just to clarify something, the Android Toolkit wasn't what bricked it, I tried to install the firmware from a .zip on my SDcard viz CWM recovery, but it was the wrong one (I was so damn sure I was T999, not T999L).
Thank you guys for all the help, I'll post if the guy fixes it!

I know, I only mentioned it because you mentioned using it. Just warning you for the future is all.
Good luck!

Looking for PIT files for SM-N910P

I'm looking for the PIT files for Sprint's Note 4. Or does anyone know if the PIT for SM-N910F will work. Is the (F) version compatible in all of the Sprint versions. I.E. when looking for Sprint programs there is no SM-N910(P) but always a SM-N910(F). Is it safe to use the F version? Or is there a safe way to update/redo the bootloaders? I flashed some bad files with Odin right around the BOB7 udate and my device has been spinning in circles around that since. Even if I go full stock and Odin the latest firmware my device is set back to that period from a protected file that is in between bootloaders. I can't touch it. The closest I can get is with a terminal command from TWRP [/sbin/recovery] I can then chmod the files and erase or do whatever with them but they are restored in cold boot. Even after flashing the official firmware it reverts to the files from BOB7. What's really crazy is I'm running stock firmware so can not use xposed but if I mount data and system wipe and then run uberwipe my device will boot with xposed apps functional. It is as if I am running two ROMS one that can not be removed or changed. I can see it happening but not from where exactly. In cold boot it loads the RO biuld from /dev/block/platforms/msm_scc1.by_name/hidden. I can find everything but the hidden. In the stock recovery logs it says the command to fix it is wipe_data_crypto but I can't accomplish it. Any suggestions?

PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk

samep said:
PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
Yes I'm getting ready to flash bootloaders big AF. I will two the pit files first but if that doesn't work I've got a list. Involves downgrading to kit kat, rooting with auoto root (can't screw me thrice) running triangle away to lose the warranty bit, installing xposed and wanam so as to make it read official. Once samsungs stuff isn't all a scared anymore I delete the /dev/block/platform/msm1_byname/hidden/rape the dumbass that used to trust developers he didn't know until he knew better and the rape was done.
I'm not really looking to flash boot loaders per say. I realized that you can only install a newer version and I TiVo I'm out of updates if I need a new bootloader. Just went to erase the obtrusive piece of poo hidden in between the 2 bootloaders. I'm not even sure theres supposed to be 2 bootladers. I look at samsuny stock firmware it's nothing like the billithera of extra stuff I have on my device. Can't say for sure who caused it because I did some retarded stuff when I was even greener than I am now. But whether it be auto root or srs unlock that super su is obtrusive as it gets. The purpose of root was flee me the user to gain access tip everything. The whole limiting the user and granting permission to every creepy fook on this planet to stock me and my kids is not what I had in mind. These people are so adamant about their creepy stalking not only is my devices esp network cut by 90% they do dangerous stuff like hidden robuilds that has a value of 1 where the radio don't shut off I airplane mode.

samep said:
PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
I appreciate the advice. I hope to avoid allot with the PIT. That's what flashfire back up says it needs. Shutting the phone of is a good idea. The recovery log was actually making fun of me for not. Along with the simple command I needed to open /sbin/recovery then wipe cane and data crypto. The /sbin/recovery was an eye opener (try it from the emulator in twrp to see if root has crippled you. The thing is most of us use a universal supersu update to reinstall and that is not good. That is written to take out the marines if that's what it takes to accomplish root. Remember the food old days when superuser binary was a line compatible with your cu?
Anyways another good command people don't know is if odin fails don't pull the battery. I put am s4 tip sleep forever that way. volumedwn home and power reatart the bootloader and wipe the cache for the software out is rejecting.
Yes I'm getting ready to flash bootloaders big AF. I will two the pit files first but if that doesn't work I've got a list. Involves downgrading to kit kat, rooting with auoto root (can't screw me thrice) running triangle away to lose the warranty bit, installing xposed and wanam so as to make it read official. Once samsungs stuff isn't all a scared anymore I delete the /dev/block/platform/msm1_byname/hidden/rape the dumbass that used to trust developers he didn't know until he knew better and the rape was done.
I'm not really looking to flash boot loaders per say. I realized that you can only install a newer version and I TiVo I'm out of updates if I need a new bootloader. Just went to erase the obtrusive piece of poo hidden in between the 2 bootloaders. I'm not even sure theres supposed to be 2 bootladers. I look at samsuny stock firmware it's nothing like the billithera of extra stuff I have on my device. Can't say for sure who caused it because I did some retarded stuff when I was even greener than I am now. But whether it be auto root or srs unlock that super su is obtrusive as it gets. The purpose of root was flee me the user to gain access tip everything. The whole limiting the user and granting permission to every creepy fook on this planet to stock me and my kids is not what I had in mind. These people are so adamant about their creepy stalking not only is my devices esp network cut by 90% they do dangerous stuff like hidden robuilds that has a value of 1 where the radio don't shut off I airplane mode.

TheMadScientist420 said:
by chance i got one of these thats only in qloader9008 you got any ideas on that i am downloading the debrick img from sammobiles rite now. aint really ever had this issue on a samsung only lgs
thanks in advance man
Click to expand...
Click to collapse
You may have discovered this thread. I haven't had the issue or tried fixing one bricked but marked this thread because of all the theories, examples and links, it seemed a place to start for answers but I couldn't know without experiencing an issue, myself. What works? Don't know.
http://forum.xda-developers.com/showpost.php?p=63848150&postcount=1
It's probably a starting point but nothing new if you've devoted time with success in finding methods to try. It suggests also it could be the eMMC failing which is all too common for Note 4. Either way, if it's just bricked, maybe you recover it. If it's component failure, main board replacement should fix it. Main boards can be found on eBay and Amazon but I think they're all used or remanufactured boards. Samsung repair may be an alternative if you're not to inconvenienced by waiting. Just recently, I got a quote from my local uBreakItIfixIt and the guy said it's not a fixed estimate store to store but he'd only charge $10 to replace a main board in store.
Best wishes for timely procedure or economical repair.
Sent from my SM-N930P using Tapatalk

I never could find the files. The link was valid, samep, it just refused to let me have them. It turns out it is easier to get them off your own device and I've zero doubt they are for the 32gb Sprint Note 4. At least mine anyways. I tried the down grade to kitkat which would have worked because it downgrades you boatloader at least according to the page. I got a failed md5. So it wouldn't supirise me if these pit files are different than what the stock one was. Hard to tell what you have, for sure, when you are a flash junk that trusts random people on the inter web. At least I was/did. I gave myself this when it was brand new. It was hard to get it going again. I back up worked with plasma kernel then on the next official it was right again, well almost, I've had this problem almost two years now. I went without root for a while so didn't notice.
I
I hope this fixes it. If not I'll find the right files for the kk downgrade. It would be sweet to go back anyways. I'll leave a link in the next thread for the pit.

TheMadScientist420 said:
i dont know the problem seems to have been in a update.. playing with it for a while it started charging and turned on and finished a update....
i got a s6 active did the same thing to me just started working i run it for like 6 months no probs
of coarse its on sprints black list just found out due to non payment of ezpay. but ill deal with that on my own as such talks are downed and frowned upon.
man i got this thing for 20 bucks.... even if nothing else my buddy needs a screen for one in his shop. but most def thank you for responding..
too further your post i do all my own repairs ussually the cheapest route currently behind the wheel of a unrootable verizon note 5 and a lgg4 which is rooted but no twrp method available. each i have very little invested in.
Click to expand...
Click to collapse
Did you fix it? Your right totally worth it for the screen. You can unlock the imei. I only did it once just because some people are so adamant you can't. I like to believe anything is possible. I don't feel bad about getting those non paid because the phone companies are the thieves. Especially in the US. They bury a lot of people locking you down to have a phone and the policy on being to stupid to fix anything is raw. With two kids I paid out a lot of dead phones. It takes rooting one phone to have bested the entire knowledge of tech at sprint. That's the hard part. If they sold parts it would be nothing.
TheMadScientist420 said:
by chance i got one of these thats only in qloader9008 you got any ideas on that i am downloading the debrick img from sammobiles rite now. aint really ever had this issue on a samsung only lgs
thanks in advance man
Click to expand...
Click to collapse
Sent from my SM-N910P using XDA-Developers mobile app

PIT_SM_N910P
https://mega.nz/#!cJREFYqS
Sent from my SM-N910P using XDA-Developers mobile app

planb234 said:
Did you fix it? Your right totally worth it for the screen. You can unlock the imei. I only did it once just because some people are so adamant you can't. I like to believe anything is possible. I don't feel bad about getting those non paid because the phone companies are the thieves. Especially in the US. They bury a lot of people locking you down to have a phone and the policy on being to stupid to fix anything is raw. With two kids I paid out a lot of dead phones. It takes rooting one phone to have bested the entire knowledge of tech at sprint. That's the hard part. If they sold parts it would be nothing.
Sent from my SM-N910P using XDA-Developers mobile app
Click to expand...
Click to collapse
Y3a it just decided it was gonna start workin heck yea.
The battery is trashed on it. Im gonna order one here soon
Ive flashed a few roms on it. Rooted. But everytime i restart it the bat percentage is totally diffrent.. thank you. I got a s6 once same way
Wouldnt do nothing. Plyin with it and decided to boot up.
Again i know talks of bad imeis are not good conversation. But i use cdma workshop and basicly took a old sammy i had that was junk and destroyed it. Took the sticker and rewrite a new iemi. Havent done it yet but. When i get there i know i can.
Ofcoarse now i cant unlock it even if i follow all the guides. Ive tried and tried.

TheMadScientist420 said:
Y3a it just decided it was gonna start workin heck yea.
The battery is trashed on it. Im gonna order one here soon
Ive flashed a few roms on it. Rooted. But everytime i restart it the bat percentage is totally diffrent.. thank you. I got a s6 once same way
Wouldnt do nothing. Plyin with it and decided to boot up.
Again i know talks of bad imeis are not good conversation. But i use cdma workshop and basicly took a old sammy i had that was junk and destroyed it. Took the sticker and rewrite a new iemi. Havent done it yet but. When i get there i know i can.
Ofcoarse now i cant unlock it even if i follow all the guides. Ive tried and tried.
Click to expand...
Click to collapse
There's a couple of ways to calibrate the battery. the easiest is a root app in Play "Battery Calibrator" it resets the stats at 100% Another is *#0228# I believe you calibrate it then let it run all the way dry then charge it to full with the system off. Not too hard to find if you want to give it a shot. It's hard to say what the problem is. I just got a new one because the old was dying at 30%. I use both and they take turns on which one is weak. Neither is a problem with out root. I probably have too much working Or to much stuff in the background.
I've heard that about changing the sticker. i only change the sticker if I used another phone for the screen. It matches what is in the board that way, If you take it in the store to get it activated they may be a little less confused.
I took an S4 that was compiled of 3 previous ones and my daughters that just stoppede working to get activated at sprint. Of course he couldn't. His story the same "When you work on them .. . He was pretty adamant that as it. I couldn't figure out how that affected both of them. So i took it home and activated it myself. Turns out the S4 is a dual band so he generally has a 50% succes rate it will turn on in the mode.
The sticker definitly won't get it activated. I've got an LG3 that was given to me by some who did't care about sprint anymoe that was Imei locked out activated. It was $100 bucks for the server. The server was. It unlocked a s5 also that a jerk sold me was clean. It unlocked it too. It was through verizon so i never activated it. I was trying to flop it to sprint when it disappeard .I unloced my note 4 with it to. The SIM so the APNs aere never locked altough I'm not positve it could have been GTidonetehapp that did it. I did' know what I ws doing, I just like plaing with them. No real reason to unlock a phone you own. Well ther is the hotspot. I'm pretty sure that's how I crumbed up my note and my puter to. I dropped exec files in my win 32 folder and flashed in something with a crazy odin to get my phone unlocked. But again not positive, thier stuff workied so it was just to give my equiment herepes.

planb234 said:
PIT_SM_N910P
https://mega.nz/#!cJREFYqS
My bad. I did not know that there has to be a key for mega. This one should do better.
Fwd: https://www.dropbox.com/sh/b0b3ywj5rbiec7h/AAAUM9TvOLUCDPJXXZTZBd_Ea?dl=0
Click to expand...
Click to collapse

planb234 said:
There's a couple of ways to calibrate the battery. the easiest is a root app in Play "Battery Calibrator" it resets the stats at 100% Another is *#0228# I believe you calibrate it then let it run all the way dry then charge it to full with the system off. Not too hard to find if you want to give it a shot. It's hard to say what the problem is. I just got a new one because the old was dying at 30%. I use both and they take turns on which one is weak. Neither is a problem with out root. I probably have too much working Or to much stuff in the background.
I've heard that about changing the sticker. i only change the sticker if I used another phone for the screen. It matches what is in the board that way, If you take it in the store to get it activated they may be a little less confused.
I took an S4 that was compiled of 3 previous ones and my daughters that just stoppede working to get activated at sprint. Of course he couldn't. His story the same "When you work on them .. . He was pretty adamant that as it. I couldn't figure out how that affected both of them. So i took it home and activated it myself. Turns out the S4 is a dual band so he generally has a 50% succes rate it will turn on in the mode.
The sticker definitly won't get it activated. I've got an LG3 that was given to me by some who did't care about sprint anymoe that was Imei locked out activated. It was $100 bucks for the server. The server was. It unlocked a s5 also that a jerk sold me was clean. It unlocked it too. It was through verizon so i never activated it. I was trying to flop it to sprint when it disappeard .I unloced my note 4 with it to. The SIM so the APNs aere never locked altough I'm not positve it could have been GTidonetehapp that did it. I did' know what I ws doing, I just like plaing with them. No real reason to unlock a phone you own. Well ther is the hotspot. I'm pretty sure that's how I crumbed up my note and my puter to. I dropped exec files in my win 32 folder and flashed in something with a crazy odin to get my phone unlocked. But again not positive, thier stuff workied so it was just to give my equiment herepes.
Click to expand...
Click to collapse
I do my own i jusf activate sim cards the sticker is basicly for my refrance i sell a lot of phones but i keep ones like this for myself. So theres no issues i just swap sims all the time so no need for activations

planb234 said:
I never could find the files. The link was valid, samep, it just refused to let me have them. It turns out it is easier to get them off your own device and I've zero doubt they are for the 32gb Sprint Note 4. At least mine anyways. I tried the down grade to kitkat which would have worked because it downgrades you boatloader at least according to the page. I got a failed md5. So it wouldn't supirise me if these pit files are different than what the stock one was. Hard to tell what you have, for sure, when you are a flash junk that trusts random people on the inter web. At least I was/did. I gave myself this when it was brand new. It was hard to get it going again. I back up worked with plasma kernel then on the next official it was right again, well almost, I've had this problem almost two years now. I went without root for a while so didn't notice.
I
I hope this fixes it. If not I'll find the right files for the kk downgrade. It would be sweet to go back anyways. I'll leave a link in the next thread for the pit.
Click to expand...
Click to collapse
I do believe you have to sign into Sammobile to download files.
The PIT can also be found in the first stock tar for each OS update; the developer I linked says that the PIT hasn't changed. I've seen methods to extract PIT from phone but they don't match md5 when checked. I checked your linked PIT in the post above and it doesn't match either. I wouldn't recommend using that one.
If your phone has ever updated beyond OB7, you can't Odin full stock KitKat tars or OB7 stock tar. The bootloader will block the Odin flash.
Not looking at your phone, it's hard to say what's going on. But I hope the feedback helps. Ask if you have further questions; I'll try to reply, but I haven't experienced what you've having issues with. Best wishes for resolution.
Sent from my SM-N910P using Tapatalk

samep said:
I do believe you have to sign into Sammobile to download files.
The PIT can also be found in the first stock tar for each OS update; the developer I linked says that the PIT hasn't changed. I've seen methods to extract PIT from phone but they don't match md5 when checked. I checked your linked PIT in the post above and it doesn't match either. I wouldn't recommend using that one.
If your phone has ever updated beyond OB7, you can't Odin full stock KitKat tars or OB7 stock tar. The bootloader will block the Odin flash.
Not looking at your phone, it's hard to say what's going on. But I hope the feedback helps. Ask if you have further questions; I'll try to reply, but I haven't experienced what you've having issues with. Best wishes for resolution.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Yeah it didn't work . It just shut down . I'll explain what has going on. Thank you for this post. It's good to know there's more options.
I actually did take a note 4 and s4 back. It dependes on how they upgraded. The bootloader doesn't change in an fota. I could do the s4 again now.
Thanks again for the awesome info.

TheMadScientist420 said:
I do my own i jusf activate sim cards the sticker is basicly for my refrance i sell a lot of phones but i keep ones like this for myself. So theres no issues i just swap sims all the time so no need for activations
Click to expand...
Click to collapse
You don't have to unlock the SIM or anything? Even if you do that's a lot less than getting the imei forgot about. Don't you have to get an msl from a comany. I know it's very possible send easy in free countries but i live in murica. You pay and pay here and the still put a cap on the data. If we're not careful we may use up all that data and then there would be no way to watch us 24-7 just we might go rogue.
A sticker that changes the sim? Details please.

samep said:
You may have discovered this thread. I haven't had the issue or tried fixing one bricked but marked this thread because of all the theories, examples and links, it seemed a place to start for answers but I couldn't know without experiencing an issue, myself. What works? Don't know.
http://forum.xda-developers.com/showpost.php?p=63848150&postcount=1
It's probably a starting point but nothing new if you've devoted time with success in finding methods to try. It suggests also it could be the eMMC failing which is all too common for Note 4. Either way, if it's just bricked, maybe you recover it. If it's component failure, main board replacement should fix it. Main boards can be found on eBay and Amazon but I think they're all used or remanufactured boards. Samsung repair may be an alternative if you're not to inconvenienced by waiting. Just recently, I got a quote from my local uBreakItIfixIt and the guy said it's not a fixed estimate store to store but he'd only charge $10 to replace a main board in store.
Best wishes for timely procedure or economical repair.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
I've been trying to reply to this for 2 days. You see it's not the way my phone runs that is the issue it is my network that is completely raped. I can't lose my parasite. I screwed up my bootloader petty bad when I was learning about Samsung. If you ask how to unlock a bootloader the most common answer you get is "you don't, you use auto root". Auto root is as amazing for sure but I can tell there is a lot of people who don't read anything and just do. The the disclaimer is "don't use this with a locked boot loader, you will likely brick your device." As i mentioned I'm a flash junky. I didn't know once you blew the hole in thy boot you only needed a custom recovery forever. I like changing roms so i rooted with it a couple more times. Things for real bad after I ran the kitkat auto root on lollipop. I could use one of my back ups and add plasma kernel for a few months until the next update. Worse than that i flashed a something from an unlock sight with a special version of Odin. I didn't even need to because i had all ready changed the csc to xas so my apns were open. The effects were scary but cool. I got locked out of my phone for awhile except for virtual access on my puter screen. My home network for straight raped after that. I had everything set to home and share because i didn't think there would be even more bored than me so as to waste there life watching my life. There is and they are smart as #. I go in intervals of being angry to amazed. I thought they were gone but no. I was not keen on interweb when i got on here. Now that i could protect myself I can't keep the evil at bay because it lurks in the dark spaces I can't reach. FlashFire says it can remove the seemles. It is incredible to but I don't think so. It definitely can't mine. What's crazy is I've had a couple new bootloaderers since then but it remains. I'm with out root at the moment and am able to look at some of the data and dev were files. I can see the usb files that block adb is in but still no. Even though auto root totally changes the way and where from the device boots, I'm needing to extract or other wise terminate what is probably one card a ftp or smb. I can see in my win logs that if uses a machine to confuse the system in a barrage of security log ins while opening a door for daddy. I had the xml explaing how it's done but then a brand new 125gb card magically went to sleep forever. Some script out there is beyond amazing to me. Virtual net adapters that aren't on top of actual hardware blow my mind. It would have never crossed my mind in a million years they there is going to be a need for antivirus software on hardware like a Bluetooth keyboard.

planb234 said:
You don't have to unlock the SIM or anything? Even if you do that's a lot less than getting the imei forgot about. Don't you have to get an msl from a comany. I know it's very possible send easy in free countries but i live in murica. You pay and pay here and the still put a cap on the data. If we're not careful we may use up all that data and then there would be no way to watch us 24-7 just we might go rogue.
A sticker that changes the sim? Details please.
Click to expand...
Click to collapse
this device had a bad iemi person i got it from said they didnt pay for it on the sprint ezpay.
i checked and that was the truth. so i changed the iemi with another old sammy i had and put the sticker in for my records. so i know what the new iemi is without the device being turned on.
im trying to sim unlock it so i can use it on domestic gsm but no go sofar always invalid sim.
i guess i need to take this dissussion to another thread as so i dont get to far off the orig topic here

@planb234
I'm not following well what you've tried since getting a PIT file. Did you get the PIT file from Sammobile yet? Did you try the latest stock tar? If older ones, which ones fail?
If Odin fails, can you post the log and text on screen?
I believe what you're talking about is not needing to root if flashing a custom ROM. After a stock tar, you could Odin TWRP and flash a custom ROM. Custom ROMs include root and su. If using Chainfire Auto Root for Note 4, make sure to use the right one and latest for Lollipop and Marshmallow. KitKat had its own Auto Root. But the auto root uses a modified stock recovery which may make its use redundant if flashing a custom or even wanting just TWRP for backups if stock rooted.
Some fun facts for you:
The bootloader on Sprint Note 4 is unlocked. Flashing a stock tar will un-root it. Factory reset will cause you to lose systemless root. But flashing a full stock tar successfully will replace the bootloader. If you're trying to flash OB7 or older KitKat stock tar, your bootloader won't be replaced. As far as OTA, it patches existing baseband, bootloader and effected system files and partitions that need patched. Even if it's just a revision number in the update, it gets rolled up to match the update revision. While I feel stock tar updates are full and need no patching, the patching is sequential and should match the Odin'd bootloader and baseband once sequentially rolled up accordingly. So IMO, a patched bootloader is same as newly Odin'd bootloader. I could be wrong about the patching so not necessarily a fact.
I think your problem is unsuccessful flash of full stock tar. A blown eFuse may cause that but from what I've read in past posts of others that had issues back then is that flashing the correct stock tar after full wipe in stock recovery overcomes the flash. It leads me to believe it's only activating reset protection to try to roll the bootloader back to OB7 or KitKat. Maybe I'm wrong but if your phone isn't suffering a hardware issue, you should be able to recover it.
Other bootloaders between OB7 and OG5 like OE1 and OF5 were also exhibiting an inability to downgrade but bootloaders OG5 and up can so far can be downgraded to OG5. I haven't tried downgrading bootloader to OE1 or OF5 though.
I've seen phone info from posters claiming to roll their bootloader back to OB7 or older and they've actually reported a newer bootloader, post OB7.
As far as I know, the only true way to get KitKat ROM to flash and boot is to flash a newer kernel after ROM flash, but prior to initial boot attempt. Currently, I'm only aware of Android 5.1.1 kernel and post OB7 bootloader booting a KitKat ROM after bootloader is updated beyond OB7.
If you're capable of doing otherwise, I'd like to see legit screenshot of phone info or galaxy tools application.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Sent from my SM-N910P using Tapatalk

Develop Bugs

welcome