Related
I rooted my GS4 yesterday and had no issues at all until i tried to flash a MOD to obtain wireless hotspot, but what i didnt notice was the MOD was for a Sprint version GS4. I know know if thats exactly what made my phone brick but im pretty positive because it was during the reboot that the phone got stuck on the TMO screen and apparently remaining soft-bricked. I spent the rest of the night and all of today reading and researching how to fix it myself before coming here to ask for help, so please bare with me.
I have already attempted to flash the official stock firmware using Odin, but it displays an error everytime saying it failed and something about AUTH. Sorry if im sounding vague, i am on a back up phone to use the internet and forgot to right down the exact message.. Anywho, i tried wiping everything and redoing the process and i even tried to flash the appropiate PIT file that i found but it still displays an error and says failed because of some AUTH or SEC problem.
Ive been at this diligently for almost 12 hours. My brain is filled with all these suggestions and methods that i have tried to use to restore my phone back to factory, but none of them have worked. I can still get into recovery and all that, so im assuming that there is still good chance i could fix the problem?
Also i am starting to get myself more and more confused about whether the firmware i downloaded is the right one i need for my phone, it seemed so at first but now i see theres TONS of region codes that can determine the firmware version?
Sorry if im all over the place, but i just dont know which step to take next..
I appreciate any help that is given, and im even willing to pay (some) bucks or maybe even (btc) for someone to walk me through what i need to do or what im doing wrong.
Thanks in Advance
Have you followed every single thing in the return to stock thread? Including updating your drivers, using the USB cable that came with your phone, running Odin as admin, etc?
Toleraen said:
Have you followed every single thing in the return to stock thread? Including updating your drivers, using the USB cable that came with your phone, running Odin as admin, etc?
Click to expand...
Click to collapse
No i havent tried that threads strategy, although i have done the same exact steps but only difference i see is that the firmware file name is:
M919UVUAMDL
While the one i was trying to use earlier was:
I9505XXUAMDM
This is where im getting very confused because i cant find a cut and dry way of knowing which firmware is the correct one..
koolbreez12 said:
No i havent tried that threads strategy, although i have done the same exact steps but only difference i see is that the firmware file name is:
M919UVUAMDL
While the one i was trying to use earlier was:
I9505XXUAMDM
This is where im getting very confused because i cant find a cut and dry way of knowing which firmware is the correct one..
Click to expand...
Click to collapse
You do have the T-Mobile SGS4, correct? Any files with I9505 in the name are for the international version, which is what you flashed (not the right file). All of ours will mention SGH-M919, M919, or jfltetmo in the file name. Pull the one in the thread I linked above and push that.
Crossing your fingers while doing so couldn't hurt...
Edit: I'd recommend using the "Download UVUAMDL Official TAR" in that thread as well, not the "stock tar (original)", since the MDL is official.
Toleraen said:
You do have the T-Mobile SGS4, correct? Any files with I9505 in the name are for the international version, which is what you flashed (not the right file). All of ours will mention SGH-M919, M919, or jfltetmo in the file name. Pull the one in the thread I linked above and push that.
Crossing your fingers while doing so couldn't hurt...
Edit: I'd recommend using the "Download UVUAMDL Official TAR" in that thread as well, not the "stock tar (original)", since the MDL is official.
Click to expand...
Click to collapse
Thanks so much, i feel stupid for not realizing the difference between the two haha. Im d/l the firmware from the thread you referenced as we speak so i definitely will keep my fingers crossed and let you know how it turns out!
Thanks again. Im not sure how to give a thanks on here or credit for you help but your help is definitely appreciated.
error post
If you can get into download mode i would suggest flashing stock with that then rerooting that way the program downloads all of the nessacary stuff on its own.
koolbreez12 said:
Thanks so much, i feel stupid for not realizing the difference between the two haha. Im d/l the firmware from the thread you referenced as we speak so i definitely will keep my fingers crossed and let you know how it turns out!
Thanks again. Im not sure how to give a thanks on here or credit for you help but your help is definitely appreciated.
Click to expand...
Click to collapse
Welcome!
Sent from my SGH-M919 using xda premium
I kinda got confused yesterday between using updated T999 bootloaders or update I747 bootloaders because I had re ODIN'ed my my whole phone via Samsung Provided Bins and that bin contained T999 bootloaders and modem that worked and booted properly on my I747 without any problems. Thing is I decided to update that bootloader and modem to the newest version for T999 which in turn caused my dead GS3. So I'm guessing the problem would be a corrupted bootloader? I have the MSM8960 hex and the MSM8960 BIN, but when I try to program these to my SG3 which is in QHUSB mode, it says the "Cookie (If Present) not received error (QPST 2.7 Build 402). I've been up studying partitions etc etc but I just can't seem to do it. I think I need the partition_boot.xml and the rawprogram0.xml and or patch0.xml IF those were needed (I'm kinda glitchy right now, no sleep -_-) all I need to do is get my phone into regular odin mode so I can flash all the files back to my baby again (Dropbox 50GB +Nandroid TWRP FTW) (And by files, I mean the proper CSC, Bootloaders, Modem, Platform and Partition files I got from Samsung for my unlocked and modded S3.
I'll add the attachments I've used up until now, Including the odin files I've used for turning my phone into an T999 (Should NEVER update that Bootloader with a new T999 one, just a new I747 one LESSON LEARNED)
Dropbox :http://www.dropbox.com/sh/9hpjjj95dtxxx74/acPHV3XqL_
T999_UVDMD5_firmware_v4 is what bricked my phone, I have the flash the files inside this shared dropbox folder (Also in the BOOTLOADER zip of course, before I can get her running again.
Any help getting to rewrite the bootloaders and or getting into ODIN mode? I'm bringing my phone back from hell, really, If I can manage to solve this problem as well, I want to make this into an AIO so everyone who went through the same mistake by off chance can fix this as well.
Any help would be appreciated, I would JTAG, but I don't have the money for it, they aren't hiring 17 year olds around state right now -_- So I guess this would be the opprotunity to help me further my tech knowledge ( I want to do Tech Development like this when I go to college in 2 years )
Thanks
Jtag is the only way I know of, if it's truly hard bricked.
Really?
mrhaley30705 said:
Jtag is the only way I know of, if it's truly hard bricked.
Click to expand...
Click to collapse
I did alot of research and seen that it can possibly be done, but it shows up in QHUSB mode where I heard it's difficult, yet possible to fix, with a few file to make it boot as a USB drive
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
kennyglass123 said:
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
Thank you, I sort of considered it something to work on, instead of it being a question for me to ask, I see otherwise now.
[Q&A] [Firmware] [Odin] [Official] Firmware / Kernel / Modem / Recovery [N910VVRU1AN
Q&A for [Firmware] [Odin] [Official] Firmware / Kernel / Modem / Recovery [N910VVRU1ANJ5]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Firmware] [Odin] [Official] Firmware / Kernel / Modem / Recovery [N910VVRU1ANJ5]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
NJ5 Gear VR?
Is anyone able to confirm whether or not NJ5 stock works with the Gear VR on DE?
So would it be a bad idea to update just using the software update in the phones settings menu? Or should I do it by running odin? What actual difference does this make? Will this cause me issues once we do have a root method for this device?
would like to know, do I need to use a full firmware or partial firmware to update to lollipop?
Clarify instructions
Hello,
I'm fairly new to Android. That being said, I'm also new to flashing using Odin. I've searched for quite awhile for "detailed" instructions of Odin, but can't seem to find any. I did find a few things here and there but I would like to know what each and every entry does in the program. If someone can point me to the full instructions (link), I would greatly appreciate it.
Beyond that, the reason I'm posting here is that I'm a little confused by the directions given to use Odin in this thread. Line #5 states... "Add the *.tar.md5 file to AP / PDA". Looking at Odin 3.09, I don't see any "PDA" section anywhere. Is the reference to "PDA" simply something that AP used to be called before and is now not present in Odin 3.09?
Keep in mind that newbies like myself can get confused by small things. We don't want to make any mistakes we'll regret later. I hope you can relate and understand.
Attached a photo of what I'm asking about.
Thanks!
nahoku said:
Hello,
I'm fairly new to Android. That being said, I'm also new to flashing using Odin. I've searched for quite awhile for "detailed" instructions of Odin, but can't seem to find any. I did find a few things here and there but I would like to know what each and every entry does in the program. If someone can point me to the full instructions (link), I would greatly appreciate it.
Beyond that, the reason I'm posting here is that I'm a little confused by the directions given to use Odin in this thread. Line #5 states... "Add the *.tar.md5 file to AP / PDA". Looking at Odin 3.09, I don't see any "PDA" section anywhere. Is the reference to "PDA" simply something that AP used to be called before and is now not present in Odin 3.09?
Keep in mind that newbies like myself can get confused by small things. We don't want to make any mistakes we'll regret later. I hope you can relate and understand.
Attached a photo of what I'm asking about.
Thanks!
Click to expand...
Click to collapse
Sorry I can't answer the first part of your question. The answer to the second part is use AP. And yes AP was called PDA in previous versions. :good:
Update: Don't ask me why this post editor keeps removing the spaces between my sentences here.
Update 2: Stupid &^%*ing website!!
Update 3: Well I guess the spacing thing is only on my computer. It's fine on my phone. Go figure. ?
Thank you for the information. Now all I have to do is work up the guts to revert!
nahoku said:
Thank you for the information. Now all I have to do is work up the guts to revert!
Click to expand...
Click to collapse
Well if it makes you feel any better, I've never had a problem from an Odin flash. But I'm very thorough about getting all the info I need. Notice my signature. ☺
Sent from my SM-N910V DE
Remember: Read twice - Flash once
I still don't understand the ".pit" file, is it necessary? I was planning do downgrade to NI1
bond32 said:
I still don't understand the ".pit" file, is it necessary? I was planning do downgrade to NI1
Click to expand...
Click to collapse
No it's not.
Sent from my SM-N910V DE
Remember: Read twice - Flash once
Had to restore and need to make sure I have the right firmware...Please help
It has been a very long time since I have posted to the threads. I have been with android since the very beginning and have flashed and done the custom rom thing quite a bit. I am stumped with this one though and I cannot find any information on it after searching for two days. I have the developer edition Note 4 and I had to do a restore on it because I did not like lollipop. I don't know if I have the right firmware. Even though everything is working alright, it just doesn't feel right. I am listing my firmware stuff below. Please tell me if I am right. I also don't know why my build number is NK5 and my baseband is NJ5. The way that I restored was flashing the stock NJ5 and then the nj5 to nk5 like for the lollipop update. The only difference is that I stopped there and loaded TWRP and root. Any help is much appreciated.
This is what I have currently:
BASEBAND: N910VVRU1ANJ5
KERNEL: 3.10.0
BUILD NUMBER: KTU84P.N910VVRU1ANK5
Is this correct?
Thanks!
---------- Post added at 09:45 PM ---------- Previous post was at 09:01 PM ----------
dustenbartley said:
So would it be a bad idea to update just using the software update in the phones settings menu? Or should I do it by running odin? What actual difference does this make? Will this cause me issues once we do have a root method for this device?
Click to expand...
Click to collapse
Only if you have a developer edition. You DO NOT want to update the developer edition with the updater in the phone or you will lock your bootloader. Otherwise I dont see a reason not to update with the phone. These files here are if you brick your phone and need to do a restore.
stueycaster said:
Well if it makes you feel any better, I've never had a problem from an Odin flash. But I'm very thorough about getting all the info I need. Notice my signature.
Sent from my SM-N910V DE
Remember: Read twice - Flash once
Click to expand...
Click to collapse
I pulled the trigger and all went well. I did get into three bootloops but pulled the battery each time until it finally gave in and booted up into KK. Not sure what went on there. Once I got through, I powered down, entered into the root menu, cleared cache/wiped data and restarted again. All is good, so it worked! Back in KK!
Lollipop does seem to run faster/smoother... and colors are nice... but I disliked the interface.
1) The notification panel is lighter blue in LP than in KK and so contrast is diminished. Old people have a hard time with contrast issues... and I'm OLD!
2) Don't like that LP phone number pad has no separators. No biggie but I like KK better.
3) Don't like how they added a floating icon in LP in contacts. It blocks some of my contact's info, so I have to scroll just to read it. Also, the icon makes the interface look "cheesy". Bad move in my opinion.
4) There are other things I dislike, but forgot what they were since I'm back to KK!!!!
Thanks for the help and reassurance!:good:
thanks
sir, what can i say .... in short i loose hope for upgrading into lollipop but your uploading help me
thanks sir please upload latest update
N910VVRU1BOAF Firmware
Hello,
I have a N910VVRU1BOAF that got updated to Lollipop but needs to go back to KitKat. I downloaded the Full Firmware from the first post and followed instructions from post #3. The flash runs without errors and shows PASS at the end, but when the phone reboots no changes have been made to it and its still running Lollipop. It looks like if all I did to the phone was just rebooting it. Sorry for the noob question. Any help will be appreciated.
Thanks
My bad. Just found out what I missed. N910VVRU1BOAF is lollipop, so I just need to flash N910VVRU1ANJ5.
Thanks to all.
usmc_jd said:
It has been a very long time since I have posted to the threads. I have been with android since the very beginning and have flashed and done the custom rom thing quite a bit. I am stumped with this one though and I cannot find any information on it after searching for two days. I have the developer edition Note 4 and I had to do a restore on it because I did not like lollipop. I don't know if I have the right firmware. Even though everything is working alright, it just doesn't feel right. I am listing my firmware stuff below. Please tell me if I am right. I also don't know why my build number is NK5 and my baseband is NJ5. The way that I restored was flashing the stock NJ5 and then the nj5 to nk5 like for the lollipop update. The only difference is that I stopped there and loaded TWRP and root. Any help is much appreciated.
This is what I have currently:
BASEBAND: N910VVRU1ANJ5
KERNEL: 3.10.0
BUILD NUMBER: KTU84P.N910VVRU1ANK5
Is this correct?
Thanks!
Click to expand...
Click to collapse
Your Baseband, and Kernel match my verizon retail note 4 that is still running KK as delivered from the factory. My Build number is KTU84P.N910VVRU1ANJ5 though (i.e., Baseband and Build are both ...J5).
Good evening everyone. I am now the proud owner of a Vzw Note 4 Developer edition I had got this phone rooted and ROMd running NI1 firmware and Beanstalk rom 5.0.2 and kernel version 3.10. I've been roaming and searching for help trying to backup my Efs(ABOOT). I've tried using EFS pro tool several times and having no luck with it working. While creating a new setup as described in the efs pro guide for this device, i set three names for file, description, and device, click on read pit(pit shows up) click save and refresh manage button, select my created list but nothing shows up on the pit description to backup so i am unable to make a efs backup. Ive tried also with the terminal emulator method but both pc and note 4 cannot detect device.... Su works fine and have Superuser 2.46 and busybox current installed , I've granted permission and given remember this sync key. I just have 2 question' pertaining to my story since i can't find anything helpful with the ni1 firmware/baseband. 1) do i need to unroot and use stock restore for NI1 to get back to full stock rom and firmware than update to nj5 firmware in order to get efs pro to work with my note 4 or can i just follow the single step update to OAF firmware from the NI1 firmware if i want to go to Mod57s pac rom 5.1? 2) if someone would be so kind to explain the order of operation of updating for firmware and rom.. (i. E) flash firmware before rom or rom before firnware? I only see mention of firmware updating losing custom recovery and root but not which order needed to be flashed? I apologize for the long trip but without having a backup of my aboot or efs i don't want to chance doing something the wrong way. Thank you all so much for your time
Sent from my SM-N910V using Tapatalk
Note 4 Retail Version Root
I have seen some post stating that this is for Developer version ONLY. Simple question. Can I use these root files on Verizon Samsung Note 4 Retail version? I just upgraded from an S4. Would really like to root my NOTE. If so, i will document step by step on what I do and share with the community. - Thanks in advance - Jamey
How do I upgrade from CPD1 to CPF3? My bootloader is already unlocked. Will I need to unlock again?
Sent from my SM-N910V using Tapatalk
I have same question, only Im going from BPA1 to CPD1. Have TWRP installed already. Could someone please answer this question? Thank You
JOSHSKORN said:
How do I upgrade from CPD1 to CPF3? My bootloader is already unlocked. Will I need to unlock again?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
I'm having spotty cellular connection and I'd like to try a different modem or two and see if another one works better.
I'm running CM14 on a retail edition (rooted obviously), can I just flash the modems only? Any knowledge of them working with CM14?
Thanks in advance.
[Q&A] [ROM] [5.02] Samsung Galaxy S3 [d2sp-SPH-L710][OFFICIAL] [Nightly][01-18-2015]
Q&A for [ROM] [5.02] Samsung Galaxy S3 [d2sp-SPH-L710][OFFICIAL] [Nightly][01-18-2015][VANIR]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [5.02] Samsung Galaxy S3 [d2sp-SPH-L710][OFFICIAL] [Nightly][01-18-2015][VANIR]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Can't Call or Text
I've asked this question in two other LP Q&A's so far (Unofficial CM and LiquidSmooth), but nobody seems to be able to answer, so I'll apologize in advance for sounding like a broken record. After a seemingly successful ROM flash following the steps above, I'm unable to make calls or send SMS (the "send" button is grayed out and can't even be pressed). About|Phone lists my baseband correctly, but the APN menu is blank, and a manual edit doesn't seem to do anything. I also haven't found an APN-fix ZIP that does anything at all. So, while the ROM looks to be functioning correctly (and pulls data great over WiFi), it's otherwise non-functional.
Can anyone shed light on this for me? Thanks!
weriov said:
I've asked this question in two other LP Q&A's so far (Unofficial CM and LiquidSmooth), but nobody seems to be able to answer, so I'll apologize in advance for sounding like a broken record. After a seemingly successful ROM flash following the steps above, I'm unable to make calls or send SMS (the "send" button is grayed out and can't even be pressed). About|Phone lists my baseband correctly, but the APN menu is blank, and a manual edit doesn't seem to do anything. I also haven't found an APN-fix ZIP that does anything at all. So, while the ROM looks to be functioning correctly (and pulls data great over WiFi), it's otherwise non-functional.
Can anyone shed light on this for me? Thanks!
Click to expand...
Click to collapse
Hi There , did you get some help ? You have sprint phone I take it . What recovery and did you come from stock ? Maybe your baseband is wrong , meaning your modem version . It sounds like maybe that could be your problem . You need to be on a specific modem version which ends with ND8 I think . At the worst if you are sprint you might have to one click a stock restore back onto the phone then get your data , telephony and GPS all working and then reflash .The reclick will update your phone to the right version and is easy . if you need a link to it let me know . You also might be able to get by with just flashing the radio . I'm here to help . Don't be discouraged . Holler back .
MonstaDriva said:
Hi There , did you get some help ? You have sprint phone I take it . What recovery and did you come from stock ? Maybe your baseband is wrong , meaning your modem version . It sounds like maybe that could be your problem . You need to be on a specific modem version which ends with ND8 I think . At the worst if you are sprint you might have to one click a stock restore back onto the phone then get your data , telephony and GPS all working and then reflash .The reclick will update your phone to the right version and is easy . if you need a link to it let me know . You also might be able to get by with just flashing the radio . I'm here to help . Don't be discouraged . Holler back .
Click to expand...
Click to collapse
Thank you!! I REALLY appreciate the response. I'm on MD4; I haven't tried to update for two reasons. First, the OP of the first Lollipop ROM I tried (Unofficial CM12) threw up a screenshot of service working on MD4, but I couldn't get it to work for me. Second, I'm a little leery of updating to a Knox-based modem, because I've never had it on my device to this point.
I'm coming from CM11 (haven't had stock in over a year) with TWRP 2.8.1.0. And yes, I have a Sprint phone (the original, not the new triband)
weriov said:
Thank you!! I REALLY appreciate the response. I'm on MD4; I haven't tried to update for two reasons. First, the OP of the first Lollipop ROM I tried (Unofficial CM12) threw up a screenshot of service working on MD4, but I couldn't get it to work for me. Second, I'm a little leery of updating to a Knox-based modem, because I've never had it on my device to this point.
I'm coming from CM11 (haven't had stock in over a year) with TWRP 2.8.1.0. And yes, I have a Sprint phone (the original, not the new triband)
Click to expand...
Click to collapse
Ok well I got my used phone a while back that likely took the ND8 update , not sure whether it originally came with ND8 but I don't think the knox really matters . Your phone under warranty ? I haven't heard of any issue regarding knox whatsoever .
MonstaDriva said:
Ok well I got my used phone a while back that likely took the ND8 update , not sure whether it originally came with ND8 but I don't think the knox really matters . Your phone under warranty ? I haven't heard of any issue regarding knox whatsoever .
Click to expand...
Click to collapse
No, not under warranty - I've had it for over two years, but I'm not worried about that. I'll take a look into updating the radio - hopefully that will work.
Thanks again!!
weriov said:
No, not under warranty - I've had it for over two years, but I'm not worried about that. I'll take a look into updating the radio - hopefully that will work.
Thanks again!!
Click to expand...
Click to collapse
Yeah I think thats why your baseband is dead . From what I know and am told you have to be on ND8 . I'm pretty sure if you just update the radio and are on the custom rom then you'll probably have to reprovision the phone and you most likely won't be able to do that . You can try but be prepared to one click it and get activated , get your gps working and everything else and then your good to start flashing and profiting . This is the link to the one click I personally like . I've used it and know it works well . http://forum.xda-developers.com/showthread.php?t=2755793 Holler back if you need anything and good luck .
edited
Thanks for the info, but how come it says I lost root and I can't boot into my recovery unless I manually do it. By the way I was on the Wicked S5 Experience when I flashed this ROM,just trying to give more information to get fixes for me,I'm going to try ur fix and see what happens. Thanks again.
Sent from my SPH-L710 using XDA Free mobile app
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->.
Sent from my SPH-L710 using XDA Free mobile app
su issue
So I just flashed the build of Exodus from the 26th and only flashed the ROM and gapps. Upon boot and setup, I found I didn't have root. It seems that it may not actually be in the current build yet. I just flashed a SuperSU package that I had already and it gave root access.
Shadehawke said:
So I just flashed the build of Exodus from the 26th and only flashed the ROM and gapps. Upon boot and setup, I found I didn't have root. It seems that it may not actually be in the current build yet. I just flashed a SuperSU package that I had already and it gave root access.
Click to expand...
Click to collapse
Sorry for the late reply , just found this . Actually it is built in . Here's how you get it going and it's pretty simple . go to Security then privacy and flip the toggle on and off on privacy guard . No need to leave it on . Next go to developer options and under root access flip it from adb + apps to something else then exit that menu and go back in and flip it back to adb+apps . The 2nd step I just mentioned might be enough . Seriously, its just that easy and then privacy guard su will work . If you already flashed SU I would remove it . It's been built in for about 2 weeks and the confusion was in that sometime it pops right up and sometimes you have to trigger it as I described . Holler back if you need any addtional help but that should take care of it . Works like a champ on all 3 roms .
MD
I really like this rom. (I tried other LP roms, and exodus tops them all).
I only need a fix for LTE at the moment (I know it doesn't exist, but hoping that a fix, or an update will fix this issue)
Keep up the good work!
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