Develop Bugs

[Q] Help Updating Rooted Epic

I have a rooted Epic on Froyo with CWM. No custom mod or kernel.
I got the OTA Update, and it failed.
I downloaded the Zip and tried CWM to install it. And it fails with this message :
Code:
I:Update location: /sdcard/update.zip
Opening update package...
Installing update...
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 775 4090
1: 1023 4089
2: 1053 4088
3: 2879 4087
4: 2894 4086
5: 2944 4085
6: 3446 4084
MountFn : RFS File System, location : system
mount: failed to mount /dev/block/stl9 at /system: Device or resource busy
Verifying current system...
file "/system/bin/recovery" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/bin/recovery", "f729fa2bfefbcd4cc31428ad35078d910bbaa369", "1c924ddea21616379df7c7ac4445eb2e54e5b11d")
assert failed: apply_patch_check("/system/bin/recovery", "f729fa2bfefbcd4cc31428ad35078d910bbaa369", "1c924ddea21616379df7c7ac4445eb2e54e5b11d")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Do I have to do a full flash and wipe my phone to get to GB? Can I unroot & try?

You need to use the search function.
But here, let me say this again. YOU CANNOT GET THE OTA UPDATE WHILE ROOTED.
You either need to revert back to STOCK and update or manually install GB yourself.. which you CAN do while Rooted.
You're probably going to ask how to do both, so I'll provide these for you as well.
If you want to update this manually while rooted, follow this link:
http://forum.xda-developers.com/showthread.php?t=1337453
If you want to revert back to stock, follow this:
http://forum.xda-developers.com/showthread.php?t=1052813
then follow part 2 (For Stock) in the link that was provided for manual update.
Any other questions?

marschmellau said:
You need to use the search function.
But here, let me say this again. YOU CANNOT GET THE OTA UPDATE WHILE ROOTED.
You either need to revert back to STOCK and update or manually install GB yourself.. which you CAN do while Rooted.
You're probably going to ask how to do both, so I'll provide these for you as well.
If you want to update this manually while rooted, follow this link:
http://forum.xda-developers.com/showthread.php?t=1337453
If you want to revert back to stock, follow this:
http://forum.xda-developers.com/showthread.php?t=1052813
then follow part 2 (For Stock) in the link that was provided for manual update.
Any other questions?
Click to expand...
Click to collapse
Hey, I am sure a billion other people are asking this same question left and right, but do you know if any roots are available yet for the 2.3.5 gingerbread update? I am well aware that it takes a while for one to be developed. I am currently rooted with the 2.2.1 froyo and love it so I don't mind waiting for the new root. I just wasn't sure how the headway is going with it. Also, the revert back to stock link you posted, is that to unroot the phone? I'm sure all will be explained for us in due time, unrooting the 2.2.1... installing the 2.3.5... rooting to gingerbreak... yada yada yada...
But yeah, any advice would be great.

I was told be 2 Epic users & Best Buy sales rep, you can get OTA update if you are rooted. But I've also heard that you can't aswell. Hence the question.
So can you unroot without losing data?

infyrno676767 said:
Hey, I am sure a billion other people are asking this same question left and right, but do you know if any roots are available yet for the 2.3.5 gingerbread update? I am well aware that it takes a while for one to be developed. I am currently rooted with the 2.2.1 froyo and love it so I don't mind waiting for the new root. I just wasn't sure how the headway is going with it. Also, the revert back to stock link you posted, is that to unroot the phone? I'm sure all will be explained for us in due time, unrooting the 2.2.1... installing the 2.3.5... rooting to gingerbreak... yada yada yada...
But yeah, any advice would be great.
Click to expand...
Click to collapse
Yes, there is a root available. I'm currently rooted & running ACS ICS v4.
Take a look at this video: http://www.youtube.com/watch?v=KesCXPpa3cI
DjFarout said:
I was told be 2 Epic users & Best Buy sales rep, you can get OTA update if you are rooted. But I've also heard that you can't aswell. Hence the question.
So can you unroot without losing data?
Click to expand...
Click to collapse
Preeeetty sure you cannot get OTA with Root, you need to manually install or flash back to Stock. There are lots of threads about this, with the same answer. Also, Best Buy doesn't know a thiiiing. A friend of mine works there, and she's pretty damn stupid.
Well, since you're rooted.. you should probably invest in Titanium Backup. It can backup your data (contacts, messages, apps. you name it) and restore this all as well. Once you back up all of your data, revert to Stock, upgrade to the OTA, root it, then install Titanium Backup & you'll have it all back.
https://market.android.com/details?id=com.keramidas.TitaniumBackup&hl=en (free)
https://market.android.com/details?...iY29tLmtlcmFtaWRhcy5UaXRhbml1bUJhY2t1cFBybyJd (paid)

I Odined back to stock, ran the update.zip, Odined a recovery, flashed su and then started flashing roms to test. I save my messages with mms backup & restore, but other than that, most of the things I use save to sd. I like a really clean install so I know where my problems are coming from.

marschmellau said:
You need to use the search function.
But here, let me say this again. YOU CANNOT GET THE OTA UPDATE WHILE ROOTED.
You either need to revert back to STOCK and update or manually install GB yourself.. which you CAN do while Rooted.
You're probably going to ask how to do both, so I'll provide these for you as well.
If you want to update this manually while rooted, follow this link:
http://forum.xda-developers.com/showthread.php?t=1337453
If you want to revert back to stock, follow this:
http://forum.xda-developers.com/showthread.php?t=1052813
then follow part 2 (For Stock) in the link that was provided for manual update.
Any other questions?
Click to expand...
Click to collapse
Thanks for breaking my phone and costing me HUNDREDS OF DOLLARS to get a new phone, because you linked me (and everyone) to that very old thread. In there, it is telling us to check everything in Odin and now cuz of you, a lot of people have broken phone.

ThunderOKC said:
Thanks for breaking my phone and costing me HUNDREDS OF DOLLARS to get a new phone, because you linked me (and everyone) to that very old thread. In there, it is telling us to check everything in Odin and now cuz of you, a lot of people have broken phone.
Click to expand...
Click to collapse
You're very welcome!
This isn't very hard to understand. You do your research, you follow directions, and you'll have success. If you decide not to do it correctly and break your phone, that is on YOU. You broke your phone simply because you did not read. That is your own stupidity.
Also, you don't check everything in ODIN. You obviously do not know what you are doing, so I suggest reading some things before attempting this again.
Both guides worked for me, without any issue. The same goes for many others as well.

ThunderOKC said:
Thanks for breaking my phone and costing me HUNDREDS OF DOLLARS to get a new phone, because you linked me (and everyone) to that very old thread. In there, it is telling us to check everything in Odin and now cuz of you, a lot of people have broken phone.
Click to expand...
Click to collapse
Seriously? You're *****ing at this person because you failed to take the time and research these forums. I spent an entire day reading threads and watching QBKing77's videos to gather all the necessary information and files before doing anything. Also, spare me with any replies to you not having enough time to do so.
Hope you walk away from this with a new found respect for doing research.
Edit: You even posted in the "Everything EI22" thread in the General forum where I gave a typed out how-to for a clean install, or full ODIN to Froyo then the upgrade to Gingerbread. You could've simply scrolled up on page 10 to this post. (Seeing as your post created page 11 of that thread.)

marschmellau said:
You're very welcome!
This isn't very hard to understand. You do your research, you follow directions, and you'll have success. If you decide not to do it correctly and break your phone, that is on YOU. You broke your phone simply because you did not read. That is your own stupidity.
Also, you don't check everything in ODIN. You obviously do not know what you are doing, so I suggest reading some things before attempting this again.
Both guides worked for me, without any issue. The same goes for many others as well.
Click to expand...
Click to collapse
No, you are in the wrong. You're out to brick as many phones that you can. Everyone in the chat told me that the thread/instruction is very old and all wrong. The picture used was wrong. Everyone told me that I did nothing wrong and that I followed everything right.
Warning to everyone, don't try his link to revert back to stock. It will immediately show a red fail in the first box, then your phone will never, ever...not now, not ever...turn back on. Then expect to shell out hundreds for a new phone.
This isn't funny. Not one bit.

ThunderOKC said:
No, you are in the wrong. You're out to brick as many phones that you can. Everyone in the chat told me that the thread/instruction is very old and all wrong. The picture used was wrong. Everyone told me that I did nothing wrong and that I followed everything right.
Warning to everyone, don't try his link to revert back to stock. It will immediately show a red fail in the first box, then your phone will never, ever...not now, not ever...turn back on. Then expect to shell out hundreds for a new phone.
This isn't funny. Not one bit.
Click to expand...
Click to collapse
They see me trollin'..
You're obviously an idiot. I used the method to return to stock just last week. It's not my fault that you can't comprehend simple instructions. That is not the wrong picture, btw. ODIN looks like that.
Also, Out of oh.. I don't know, all of the people I've linked this to, you're the only one who had any issue. It's damn near obvious that you were the one who screwed up.
Do some damn research before you even post anything else.
Oh! And, if you actually used the search function you would learn how to get your phone into download mode so you can reflash stock rom.
I think this is pretty hilarious, btw.

Incorrect!
In the picture, it shows everything checked. Everyone in the chat room informed me that its wrong.

@ThunderOKC,
I live in the OKC area. I imagine you are from here. If you need hand holding help, PM me. I've been around snooping the forums since January. I am now confident enough to answer questions, troubleshooting, and also start producing my own mods. There is always someone willing to help.

I can do this. It just been a long time since I've messed with this.
I just realized the title of that linked thread "How to Restore a semi-brinked Epic..." and this thread is most likely not proper for those with phones being just fine and all they want is to revert back to stock. I"ve searched for the real thread on reverting back to stock, but I can't find it. Nothing stays stickied on here for long. When I get access to my comp, everything there is bookmarked.
For now, don't check all the options as it says. lol

ThunderOKC said:
Thanks for breaking my phone and costing me HUNDREDS OF DOLLARS to get a new phone, because you linked me (and everyone) to that very old thread. In there, it is telling us to check everything in Odin and now cuz of you, a lot of people have broken phone.
Click to expand...
Click to collapse
The only people with the broken phones are the ones who haven't the slightest clue on what to do. Just because you know how to download odin, doesn't mean you should use it. Btw, your phone is soft bricked and its your own fault. Send it to me, ill have it working in 5 minutes fool.
Sent from my Ei22 Epicaladocious

ThunderOKC said:
Incorrect!
In the picture, it shows everything checked. Everyone in the chat room informed me that its wrong.
Click to expand...
Click to collapse
Well then, the picture itself is wrong. Don't rely on pictures for a guide, half the time they aren't correct. Next time, follow it step by step from the directions, not pictures.
b16flybye said:
The only people with the broken phones are the ones who haven't the slightest clue on what to do. Just because you know how to download odin, doesn't mean you should use it. Btw, your phone is soft bricked and its your own fault. Send it to me, ill have it working in 5 minutes fool.
Sent from my Ei22 Epicaladocious
Click to expand...
Click to collapse
Lol, Pretty much what has been said.
Also, ThunderOKC. You do realize that to fix the "soft brick" on an epic means returning it to STOCK. So yes, you idiot, you can use that thread to return to stock without it having a soft brick.
like I said, do some more research

ThunderOKC said:
I can do this. It just been a long time since I've messed with this.
I just realized the title of that linked thread "How to Restore a semi-brinked Epic..." and this thread is most likely not proper for those with phones being just fine and all they want is to revert back to stock. I"ve searched for the real thread on reverting back to stock, but I can't find it. Nothing stays stickied on here for long. When I get access to my comp, everything there is bookmarked.
For now, don't check all the options as it says. lol
Click to expand...
Click to collapse
Funny thing is that thread works for everyone but you. No one has cried about it semi-bricking the phone or that they can no longer afford to get the breast implants, or whatever the surgery was you claimed you couldn't get to because you had to buy a new phone. That statement alone showed your mentality and level of competence. The Red fail means your stock cable is a piece of crap and you should spend $2 of your surgery money to get a good cable. If you just red through the thread instead of running your mouth everywhere you would have seen that is common for Odin and stock cables.
---------- Post added at 05:57 PM ---------- Previous post was at 05:52 PM ----------
ThunderOKC said:
No, you are in the wrong. You're out to brick as many phones that you can. Everyone in the chat told me that the thread/instruction is very old and all wrong. The picture used was wrong. Everyone told me that I did nothing wrong and that I followed everything right.
Warning to everyone, don't try his link to revert back to stock. It will immediately show a red fail in the first box, then your phone will never, ever...not now, not ever...turn back on. Then expect to shell out hundreds for a new phone.
This isn't funny. Not one bit.
Click to expand...
Click to collapse
Actually it is funny. Your level of incompetence shows you should not be rooting or messing with your phone. You are very rude and have no gratitude for people trying to help you. Stay out of the love connection chat rooms asking for help with your phone.

I followed the instructions exactly. In the picture AND in the instructions, say to check it all. Stupid kids, learn how to read and understand. Not my fault. Hell, even had the whole chat room support laughing at how wrong the thread was.
I fixed it on my own. Grow up, kids.

@ ThunderOKC
It's your choice to hack your phone. With that choice comes the responsibility to do proper research beforehand and make educated decisions based upon that research. Otherwise you will likely end up with a paper weight. That is the inherent risk of hacking the phone.
You've been posting all over this forum complaining, and the tone has been down right rude. Welcome to the ignore list.

ThunderOKC said:
I followed the instructions exactly. In the picture AND in the instructions, say to check it all. Stupid kids, learn how to read and understand. Not my fault. Hell, even had the whole chat room support laughing at how wrong the thread was.
I fixed it on my own. Grow up, kids.
Click to expand...
Click to collapse
This is why your stupid. You rely on a picture, and whatever chat room you have laughing at xda devs, are just as idiotic as you are. Your not welcome here douche. Good luck in the future. I think your dumbass should stick with what sprint gave ya.
Sent from my SPH-D700 using XDA App

[Q] Unlocking my SGH-T999 with Jellybean 4.1 Update

Hey all,
I have NEVER tried to unlock or root a phone before, but I have the desire to try it now.
I have the T-mobile SGH-T999 with the new Android Jellybean 4.1.1 (Build Number JRO0L.T999UVDLJA)
I want to try to root my phone, but I would like to keep as much of the the new update (Jellybean) as possible instead of reverting to ICS. What I'm wondering is, what should I do to root the phone, and what programs are preffered, etc. Also, I was wondering how to back up my current build in case I want to set it back to default in case of warranty issues that I had to return it.
I am sure others have asked... maybe this would be a good sticky, I don't know... but I am hoping someone will take the time to point me in the right direction.
I need to know
a.) What I need to backup pre-root
b.) What software is best to root
c.) Any special instructions for rooting that may be specific for this build or this phone
d.) How to un-root in case I need to return the phone.
Any help would be appreciated, and apologies in advance if this is a repeated question. I just figured I'd ask because of the new update.
Thanks!
Skot in Seattle

sekellas said:
Hey all,
I have NEVER tried to unlock or root a phone before, but I have the desire to try it now.
I have the T-mobile SGH-T999 with the new Android Jellybean 4.1.1 (Build Number JRO0L.T999UVDLJA)
I want to try to root my phone, but I would like to keep as much of the the new update (Jellybean) as possible instead of reverting to ICS. What I'm wondering is, what should I do to root the phone, and what programs are preffered, etc. Also, I was wondering how to back up my current build in case I want to set it back to default in case of warranty issues that I had to return it.
I am sure others have asked... maybe this would be a good sticky, I don't know... but I am hoping someone will take the time to point me in the right direction.
I need to know
a.) What I need to backup pre-root
b.) What software is best to root
c.) Any special instructions for rooting that may be specific for this build or this phone
d.) How to un-root in case I need to return the phone.
Any help would be appreciated, and apologies in advance if this is a repeated question. I just figured I'd ask because of the new update.
Thanks!
Skot in Seattle
Click to expand...
Click to collapse
I would think the easiest is to use the root injected rom from this forum: http://forum.xda-developers.com/showthread.php?t=1771687
It is what I did and I have full root access and stock rom with no counter tripped. Backup preroot will be difficult but as long as everything is set up with google, you should be able to get all of your contacts back but not settings. Once rooted, you can use titanium backup. Great program. If you want to unroot you can use the same method you used to root but you can just odin back to the original rom again. If you like my response please click on Thanks.

Thanks!
I took a look at the thread you sent me, and have contacted the original member to get step by steps, just to make sure I dont screw it up.
Hopefully it will work as desired.
Thanks for your help and response!

sekellas said:
I took a look at the thread you sent me, and have contacted the original member to get step by steps, just to make sure I dont screw it up.
Hopefully it will work as desired.
Thanks for your help and response!
Click to expand...
Click to collapse
The person who wrote the thread may or may not have time to give a more detailed run-through.
I used that thread to root my phone - honestly, all the instructions have already been given in it. I have never done anything like this and I just followed the instructions as given - the process is covered completely. I'm not sure what more they could tell you.
Not trying to be rude. Just understand that they have already provided a full guide and it might be more considerate to ask questions to the open forum about any step that is troubling you - that way anyone who has free time can answer.

Ok
Pennycake said:
The person who wrote the thread may or may not have time to give a more detailed run-through.
I used that thread to root my phone - honestly, all the instructions have already been given in it. I have never done anything like this and I just followed the instructions as given - the process is covered completely. I'm not sure what more they could tell you.
Not trying to be rude. Just understand that they have already provided a full guide and it might be more considerate to ask questions to the open forum about any step that is troubling you - that way anyone who has free time can answer.
Click to expand...
Click to collapse
Thanks for that, I guess I just wanted to make sure I wasn't leaving anything to chance. Since the phone is a pretty penny, I didn't want to be screwed if I tried to root and somehow screwed up the phone.
I'll see if he responds in the next few days, if not, I'll give it a go.
thanks again!

sekellas said:
Thanks for that, I guess I just wanted to make sure I wasn't leaving anything to chance. Since the phone is a pretty penny, I didn't want to be screwed if I tried to root and somehow screwed up the phone.
I'll see if he responds in the next few days, if not, I'll give it a go.
thanks again!
Click to expand...
Click to collapse
It's so easy, you'd be hard pressed to screw it up.
Step 1): Download the Samsung USB Drivers from their site
Step 2): Download the pre-rooted stock firmware from the previously listed link here at xda(make sure you get the 4.1 with root)
Step 3): Download ODIN
Step 4): Plug phone into PC and launch ODIN
Step 5): Click "PDA" and then browse to the firmware you downloaded
Step 6): Hit Flash.
Step 7): Wait, wait some more. Wait more.
Step 8): Watch phone reboot and sweat manically as its your first time and you think you've bricked your phone.
Step 9): Tinker like a madman when your phone comes back and you see its rooted.
Step 10 through ifiniti): Continue to tinker, eventually find rom manager and aftermarket roms. some good, some bad.
PM me if you want and I can walk you through it via IM or something. I can even throw you my rom, which is essentially stock with all the tmobile BS removed.

Awesome (Easy) walkthrough
osbosb said:
It's so easy, you'd be hard pressed to screw it up.
Step 1): Download the Samsung USB Drivers from their site
Step 2): Download the pre-rooted stock firmware from the previously listed link here at xda(make sure you get the 4.1 with root)
Step 3): Download ODIN
Step 4): Plug phone into PC and launch ODIN
Step 5): Click "PDA" and then browse to the firmware you downloaded
Step 6): Hit Flash.
Step 7): Wait, wait some more. Wait more.
Step 8): Watch phone reboot and sweat manically as its your first time and you think you've bricked your phone.
Step 9): Tinker like a madman when your phone comes back and you see its rooted.
Step 10 through ifiniti): Continue to tinker, eventually find rom manager and aftermarket roms. some good, some bad.
PM me if you want and I can walk you through it via IM or something. I can even throw you my rom, which is essentially stock with all the tmobile BS removed.
Click to expand...
Click to collapse
Hey osbob, thanks for that walkthrough... I wanted to make sure I was using the right pre-rooted stock firmware... would it be the
New! - October 2012 - 4.1.1 JellyBean
Note: This is based off of the stock image TMO T999UVDLJA
Perm Mirror: Download - root66_TMO_T999UVDLJA.7z
Click to expand...
Click to collapse
?
And then, if I need to send it back, I'd have to unroot the phone too, so I wanted to make sure I saved whatever I needed to. As for using yoru version without the bloatware, the bloatware doesn't bother me, since I use the Visual Voicemail, and the My Account features to manage the account for my wife and I. I just want to make sure I'm injecting the right stuff.
Thanks a lot for your help and the walkthrough above
Skot

sekellas said:
Hey osbob, thanks for that walkthrough... I wanted to make sure I was using the right pre-rooted stock firmware... would it be the ?
And then, if I need to send it back, I'd have to unroot the phone too, so I wanted to make sure I saved whatever I needed to. As for using yoru version without the bloatware, the bloatware doesn't bother me, since I use the Visual Voicemail, and the My Account features to manage the account for my wife and I. I just want to make sure I'm injecting the right stuff.
Thanks a lot for your help and the walkthrough above
Skot
Click to expand...
Click to collapse
You can use Odin to return it to stock.
Sent from my SGH-T999 using xda app-developers app

sekellas said:
Hey osbob, thanks for that walkthrough... I wanted to make sure I was using the right pre-rooted stock firmware... would it be the ?
And then, if I need to send it back, I'd have to unroot the phone too, so I wanted to make sure I saved whatever I needed to. As for using yoru version without the bloatware, the bloatware doesn't bother me, since I use the Visual Voicemail, and the My Account features to manage the account for my wife and I. I just want to make sure I'm injecting the right stuff.
Thanks a lot for your help and the walkthrough above
Skot
Click to expand...
Click to collapse
Perm Mirror: Download - root66_TMO_T999UVDLJA.7z <-- that's correct.
You can always run a debloated rom and then reinstall the tmobile specific stuff.

Tab S T707A (AT&T) bricked, can't find ODIN firmware.

Rooted it for a buddy using KingRoot, worked totally fine. Verified that it was working and went about our day. I didn't attempt to install recovery or anything like that because I know the bootloader is locked. For some reason, it is now saying that the software is unofficial, and to take it to a Verizon store for some damn reason. 100% sure this is an AT&T tablet, as it says SM-T707A right on the back panel, and it's on his AT&T plan.
I can't find the flashable software on either AT&T or Samsung's site...does anyone know where I can get it, or what I can do to fix this? I can get into download mode no problem. I've owned many Samsung devices in the past and it's never been as issue if you can get into download mode....but I can't find the damned firmware.

May have figured it out - http://forum.xda-developers.com/galaxy-tab-s/general/stock-kitkat-image-sm-t707a-revert-t3403934
Gonna odin back to Kit Kat and take the OTA if available back to lollipop.
Still dunno why the hell it says Verizon on the error screen though...

Reporting back in case someone finds this via search. This totally worked. It's back up and running.
Wasn't able to do the OTA, but was able to manually update to Lollipop via the zip files posted in the thread I linked above. Worked a treat.

Try this. You'll have to scroll down but it might help.
http://www.androidayos.com/galaxy-tab-s-stock-firmware/

sparkie6point0 said:
Try this. You'll have to scroll down but it might help.
http://www.androidayos.com/galaxy-tab-s-stock-firmware/
Click to expand...
Click to collapse
Thank you for the links, I was able to find the answer, but those links might help someone in the future with this same issue.

Have you looked at updato...

Just found this

No one is reading the thread apparently...
Thanks for the replies though!

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.

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
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

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

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 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.

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

Need some help

I have been into the Android scene since the original Samsung Galaxy S. I couldn't even tell you how many phones I had since then but I was always big into rooting and flashing more ROMs than healthy. I lost the ability to get endless company phones and ended up with locked bootloader phones for a few years. One day I saw a friend with the Pixel 2 and I got the itch again. I got the Pixel 3XL and unlocked the bootloader and rooted it immediately. At the time I didn't realize how much different the process was as far as updating and installing ROMs than it used to be on my older phones like my beloved Nexus phones. Basically I'm paranoid about doing anything because the process sounds extremely complicated to me. Maybe I'm just getting older. I build server and storage solutions every day but this is foreign to me. Sorry for all the rambling. Basically I'm rooted and still on the November 2019 build. I'm starting to get OTA update prompts a lot but I just ignore them. I just really want to update the easiest way and hopefully be able to do more going forward. Thanks for any help anyone can provide.

Download latest factory image. Extract the boot.img from it and save to your phone. Open magisk manager and patch that boot.img. Save /download/magisk_patched.img to your computer. Disable or remove any magisk modules that you might have running. In bootloader run the flash-all.bat, after editing to remove -w, and boot into system. Reboot to bootloader and run "fastboot flash boot --slot all magisk_patched.img" and you should be good to go. Make sure to back everything up before hand just in case something does wrong. I use a mix of titanium backup, sms backup/restore, export contacts, and manually saving files. There are other ways, but this is what I am comfortable with.

pside15 said:
I have been into the Android scene since the original Samsung Galaxy S. I couldn't even tell you how many phones I had since then but I was always big into rooting and flashing more ROMs than healthy. I lost the ability to get endless company phones and ended up with locked bootloader phones for a few years. One day I saw a friend with the Pixel 2 and I got the itch again. I got the Pixel 3XL and unlocked the bootloader and rooted it immediately. At the time I didn't realize how much different the process was as far as updating and installing ROMs than it used to be on my older phones like my beloved Nexus phones. Basically I'm paranoid about doing anything because the process sounds extremely complicated to me. Maybe I'm just getting older. I build server and storage solutions every day but this is foreign to me. Sorry for all the rambling. Basically I'm rooted and still on the November 2019 build. I'm starting to get OTA update prompts a lot but I just ignore them. I just really want to update the easiest way and hopefully be able to do more going forward. Thanks for any help anyone can provide.
Click to expand...
Click to collapse
Here ya go... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117

Google offers their own flashing update tool. You can find it here, https://pixelrepair.withgoogle.com/carrier_selection.

Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.

pside15 said:
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
Click to expand...
Click to collapse
You will need to wipe data on the upgrade to 10.
You will need to root again after the update. Bootloader will remain unlocked.
Once you have rooted, there is a method to take an OTA, and stay rooted. A description of the procedure is in the forums somewhere.
Again, I would recommend to follow the guide posted by Homeboy76. It will comprehensibly explain all the steps you need to achieve root,update etc. With links to downloads.
Gone are the days of flashing with just your phone. My first rooting experience was with an HTC Amaze. Then an S4 Samsung.
Good luck..
Edit: I stand corrected on data wipe when going to 10. I perhaps was overly cautious, and followed other recommendations.

pside15 said:
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
Click to expand...
Click to collapse
You do not need to wipe data to update to 10. It is perfectly safe, we all did it. And so did all the people with locked bootloaders. You only have to wipe going down. Up is fine.
---------- Post added at 10:53 PM ---------- Previous post was at 10:51 PM ----------
And here is the link to take an ota without losing root.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation).

Anyone tried Google's flashing update tool?

Homeboy76 said:
Anyone tried this?
Click to expand...
Click to collapse
Just a heads up, your link is broken. Looks like the period at the end of the sentence accidentally got included in the hyperlink. The one in spotmark's post works. https://pixelrepair.withgoogle.com/carrier_selection

sliding_billy said:
Just a heads up, your link is broken. Looks like the period at the end of the sentence accidentally got included in the hyperlink. The one in spotmark's post works. https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
It's working now

Homeboy76 said:
The link is in spotmark's quote: How can it be my link?
When I click it it works.
Click to expand...
Click to collapse
It's only if you click the link from your post. You copied the . into the link. It comes up with 'Not Found
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
Look closely at the hyperlink highlighting, and you'll see the . at the end.

sliding_billy said:
It's only if you click the link from your post. You copied the . into the link. It comes up with 'Not Found
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
Look closely at the hyperlink highlighting, and you'll see the . at the end.
Click to expand...
Click to collapse
It's working now

Homeboy76 said:
Read the edited post above yours.
Click to expand...
Click to collapse
Not kidding, it is still not clicking without the . included. When you look at spotmark's post, the dot is black. Yours is blue and part of the hyperlink. I tried it in two browsers.

sliding_billy said:
Not kidding, it is still not clicking without the . included. When you look at spotmark's post, the dot is black. Yours is blue and part of the hyperlink. I tried it in two browsers.
Click to expand...
Click to collapse
@sliding_billy
It's working now

Homeboy76 said:
@sliding_billy
It's working now
Click to expand...
Click to collapse
Winner, winner. Even better when you can't see the link.