WARNING: DANGER AHEAD!
Seriously, I want to investigate possibly a miracle un-brick fix for AT&T Note 3 users. If you are on MI9, there is help. For people like me, who chose "remind me later" to the OTA and it installs anyway, (there was no option to deny the update), there IS some mj5 odin floating around, which is hit or miss. Most people seem to report of FC's and such.
For reference, I have not rooted yet. I have rooted every android and jailbroke every iCrap I ever had, many, many times. I am upset there is no option for EFR in Kies 3, no stock Odin from sammobile even, and of course no help from AT&T. I have messaged mobiletechvideos.com about JTAG and have received no response yet either.
So, there is a 'load from external source' option in stock recovery as mentioned by @HookedOnDroids here and here again.
I have responded to his post for the file(s) upload, and even PM'ed for more info. Neither were responded to. I had made a reference to SD CARD mode, which no one seemed interested in, for more info on that see this . Basically you pull stock files/binaries/bootloaders put them on a blank/empty 2GB+? ext sd card, and if the files are correct and probably the 'header' as well and it will write these to your device.
KEY POINTS HERE:
This is untested and very dangerous. Even if you have some of the correct files, it may flash the entire ext sd card to your device regardless and you will be in trouble.
FOR THE BRAVE WHO ARE SOFT/HARD BRICKED: For anyone who may be on MJ5, and wants to give this a try, perhaps even take one for the team before sending it in anyway. I'm in the process of researching exactly what files are recommended. I think we will need someone with a fresh MJ5 rooted, preferably with no changes to /system/.
Additional Info: I believe there are also other options in recovery such as: load from /cache, which i believe is where the OTA .cfg file gets stored and applied after rebooting. There is also another option for 'apply update from sideload', this is interesting, although most people who are soft-bricked can't get a PC to recognize their device or access ADB, but it maybe be useful for flashing boot.img's etc., when and if that option ever becomes available for us N900A people
Please find Samsung .pdf document on flashing JTAG bootloader in THIS post.
Also I'm finding conflicting data, This post states sd card must be same as internal size to mimic partitions..
Also rule #1 after rooting samsung devices is to make 2-3 backups of you /EFS partition, in case you did not know.
For now, let's dicuss this further in this thread, and hopefully get somewhere. Thank You.
reserved. thank you.
You should research the forum
http://forum.xda-developers.com/showthread.php?t=2476353
I do need to research more. I don't have as much time as I used to. I have read this thread, I'm actually the 2nd post, and even linked to it in the OP. I think this is something different. In your instructions you say to put the sdcard with stock files in your device, put battery and boot into download mode. Use stock Odin files to return back to stock. So do we actually use Odin 3 Loader or once booted into download mode, it can detect these stock files and begins the lash automatically?
So from the small amount of data we have I would infer that this 'load from external resource' option in recovery is similar if not the exact same. If you have a full ROM(as mentioned in Adam's thread or as HookedonDroids mentioned), on your extsd, it will be detected and automatically flashed.
This obviously works on MI9, no word on MJ5 or downgrading from MJ5 to MI9. Seems like it should work on MJ5, unless they removed this feature.
Thanks for the help.
Hey there, folks. I'm a noob that managed to get himself into a bind (imagine that). I bought the SGH-i437 from Cricket.
I successfully rooted the phone and attempted several varieties of backups - each of dubious utility since I had no idea what I was doing. I can't use them now, for reasons unclear to me, but certainly due to user error. Not knowing this, and continuing on a foolish trajectory, I went on and flashed CM11-20140829NIGHTLY. It's been working very, very well.
I would have been trouble free, in the clear and happy, but I moved to London and had to change my Cricket service to a local carrier. To do that, I have to unlock the SIM (or rather, network unlock). I have an unlock code. When I go to unlock it, it doesn't work because in CM11 you can't access the debugging screen from the dial pad (those were the instructions sent to me). The kind people helping me unlock my phone suggested I flash back to stock ROM. Then, they tell me, I can follow the instructions. This is where my story stops.
I have a macbook, so I'm using JODIN, and I've installed heimdall on my macbook. I connect, I put the .tar file that I found on the internets into PDA and click start. J ODIN says it needs to find me a PIT file, and it tries but doesn't manage to find one. http: / / pastebin . com / 5DpJjyk8 - Hopefully that will link to the incredible string of code and whatnot generated by JODIN. I put in spaces because XDA won't let me post URLs.
I'm not sure what I need to do, now. Am I supposed to be out there looking for a mysterious PIT file, or doing something different with JODIN? I eagerly await returning to the crappy stock ROM, unlocking the SIM, then returning to the sweet blissful CM11. Please, please can you help me?
SGH-i437
CM11 - JB 4.4.4
(original stock was JB 4.1.2)
Still confusing...
When searching for ".pit file for SGH-i437" I found a thread where a guy with an S4 flashed S3 stuff and was having problems. People directed him to KIES, which I've been trying. Only problem is that Kies doesn't recognize my phone with CM11. So I'm still out to dry, here, with a functioning phone locked to a US carrier. BOOOOO!!!!!! I'm about ready to gravity test this phone over a London high street.
days of research - nothing
I can't find any other discussion of people having a similar problem with ODIN/JODIN! I can't flash my stock ROM because JODIN can't find the PIT file. I'm genuinely troubled by this - please help if you have any notion of what to do!!!
Hello! So this may be a long post, but I don't give a heck. Also, when I say hackers, I mean In a good way, like white hats. So, here is my first inquiry. How do people even find these exploits to put in the root binary? I've read articals about people intentionally crashing devices, which then puts it in a state vulnerable enough to bruteforce the binary in (At least that's what I thought...) I know that android is also based off of java, (Once again, an assumption) and I wonder where and how people get these ideas.
My second question is, As I haven't been able to find anything of this, aren't apps installed into portions of a phone where the normal user isnt able to touch on phones without root? Again, a newbie assumption.
So anyways, I am pretty interested in android development and rooting/custom code/bootloaders, and I'm not to keen on the subject.
I am also pretty bad at understand android right now, sooo, you can laugh at me if you want :silly:
Also I don't know if this is in the right thread
Alright, so I'm not sure about this, but I was thinking about what happened yesterday, and I thought about when I accidentally flashed the wrong CP file in Odin, and then when I tried to boot it, it gave me the "An error has occurred whilst the phone was updating. Please launch the Verizon Software Assistant". I also realized very quickly, that this is just the download screen without the extra information in the top right, and also realized that the download bar shows up also when you use Odin.
To give you my real question, I want to know if the Software Assistant uses any other method that isn't using Odin, and that if that is so, If you could maybe modify where it gets the flashing files to flash files onto the phone, without the phone realizing that they aren't official files?
To also be honest, I'm not an exploit finder, and maybe other people have thought of this, but eh, why not try and ask people about it? :good:
also I don't know if the phone itself will check those files....
also here is the zip with the Software Assistant.
Click here for the Assistant.
Hello,
First, let me preface this by saying that this is not for those who are already technically capable of flashing U firmware from U1 firmware. This will serve as a tutorial for those who are not sure how to go about doing so. This could at least be a means to access U One UI 3.0 firmware, as it will be posted here for for faster download and bypassing decryption process. I've already done that for you.
So I have a N986U(VZW) and wanted to get an early look at Android 11 One UI 3.0. So, I went through the process of flashing U1 firmware, enrolled in Beta Program, and OTA'd up to latest beta (beta 3). Then, I see that carrier locked devices (to date, ATT, TMB, SPR, VZW) have begun receiving the official One UI 3.0 firmware OTA. Now don't get me wrong, I love U1 firmware, no carrier bloat, more features, typically, than what carrier branded have, among so many others. Alas, carrier branded firmware is generally more safe for me.
So, if you are like me, I wanted to have a means to be able to convert back to U firmware, while still remaining on One UI 3.0. Many of us already know how to go about doing so, but some may not, so I figured I'll outline the steps to go from U1 One UI 3.0 to U Carrier Branded One UI 3.0. I've provided links to the firmware and Odin for easy access and I'm always around, in case any of you have questions or have issues with any links.
Now, we have to have the essentials:
1. Odin(3.14.1_3B Patched is what I used)
2. Frija, or at the very least the firmware to convert over to
4. An archive extractor (Winzip, Winrar, 7zip, etc.) I'll explain why we don't want to use Windows Archive Tool in this explanation.
3. Some form of technical aptitude to be able to download and flash firmware using a tool
After you've gathered all of these, we need to ensure that no fingerprints or other forms of security are on the device. The reason we do this is the avoid any FRP (factory reset protection) issues after flashing. The way we do this is by disabling fingerprint unlock from settings. Change your unlock preferences to Swipe No Security. Do not forget to do this, because if you do, you will need to have an internet connection to the device during initial setup to authenticate your google account.
1.Once you've done this, you want to power down your device. For those who have enabled side button power menu, this is pretty self explanatory. Those who haven't, swiping down from your notification tray will reveal your power button. You know what to do from there.
2.Next, you want to press and hold Vol+, Vol-, and plug a USB-C cable into your device and subsequently into an available USB-A port on your PC. Allow Windows a moment to setup your device if your haven't plugged your device into your PC while in Download Mode before. You should see your device boot into Download Mode, and you will be presented with a Vol+ and Vol- and Power option. You will need to press Vol+ to continue into Download Mode.
3.Then, you will need to open Odin. When you do so, you should see a blue bar indicating that your device is recognized (represented by COM). If you don't see this within Odin, try re-inserting your USB cable into your PC, either into another USB port or changing your USB cable for another.
4.Once you are successfully able to see the blue COM indicator in Odin, you are to choose the applicable partitions (BL, AP, CP, and CSC). These will be archived in the firmware downloaded by Frija or link I provided. Each partition is labeled by it appropriate partition. Clicking each label in Odin will direct you to Windows Explorer, where you can browse for the directory where the downloaded files are locally stored.
THIS IS IMPORTANT!!! IF YOU DO NOT HAVE A ATT, TMB, OR SPR, DO NOT CHOOSE A USERDATA PARTITION. THIS IS POINTLESS TO FLASH, AND IT WILL SERVE NO BENEFIT IN THE USE OF THE DEVICE AFTER SETUP.
5.In Odin, you will see three tabs under the COM blue bar, named Log, Options, and PIT. I want to direct your attention to the tab labeled PIT. You will need to apply a PIT file in this tab. This file is located in the CSC partition. I have uploaded this file as well. But, if you want to learn how to extract it from the CSC partition, use the aforementioned Archive Extractors to open the CSC partition, and it should be the second in the list of files. Right click this file and select Extract to... From there, you are able to choose the folder you would like to extract to.
The reason you want to use the extractors I mentioned rather than Windows embedded extractor is due to Windows not being able to handle .md5 or .tar files. You will get an error if you attempt to open these types of files with Windows Extractor.
6. Once you've chosen all the partitions in Odin, you will click Start. It may take some time to complete the flashing process, so be patient. Once it completes, you will see Success in the field above COM, and the COM field will change from blue to green. If it doesn't change to green, and instead changes to red, be sure to let it be known to the thread, so that I can assist in the best way I can.
7. At this time, your device may reboot to recovery. This is fine, it just means that you will need to factory reset. Use Vol- to select Factory Reset. Select the option using the Power button. Upon successfully doing so, your device will reset to the setup screen.
8.Your device will be an Out-of-Box state upon reboot. Setup the device as normal.
9.All done! You are now on U firmware One UI 3.0! Congratulations!
I understand that this is a very lengthy explanation and that some, if not all, of this will be redundant to some users. That is okay. Not all of the users on XDA are educated on how to flash firmware on Samsung devices. I hope that after following this guide, that may soon change.
Below are all the files needed in order to flash what is needed in this guide. If you have any issues with downloading them, let me know. I'll be happy to re-upload them on another file sharing client for you.
Update: I've also uploaded the CTL4 firmware for U1 for those who want the updated unlocked firmware, in case you want to switch back to U1.
Odin:
Odin 3.14.1_3B
Frija:
Frija 1.4.3
N986U One UI 3.0:
N986USQU1CTL2
N986U1 One UI 3.0:
N986U1UEU1CTL4
PIT File for Repartitioning:
PIT C2Q_USA_SINGLE.pit
Just wanted to say "thank you" for posting this! I knew what to do already, however, I just didn't have any links for the zipped update that I needed!
I first had gotten a phone notification (Friday morning) that I could tap on to download the update OTA, however, I was at work so I had dismissed that notification... Unfortunately, after doing so, I was unable to get the update as no available updates even showed up in the settings... So I figured that I'd just need to manually push it through since OTA updates have consistently been skipping my device... Regardless, we're working now! So thanks again for the download links and I hope that you enjoy the holidays!
NippleSauce said:
Just wanted to say "thank you" for posting this! I knew what to do already, however, I just didn't have any links for the zipped update that I needed!
I first had gotten a phone notification (Friday morning) that I could tap on to download the update OTA, however, I was at work so I had dismissed that notification... Unfortunately, after doing so, I was unable to get the update as no available updates even showed up in the settings... So I figured that I'd just need to manually push it through since OTA updates have consistently been skipping my device... Regardless, we're working now! So thanks again for the download links and I hope that you enjoy the holidays!
Click to expand...
Click to collapse
Thanks so much. Just wanted to provide a means for new users a detailed explanation on how to change firmware, preventing the needs for QAs on bricked devices. Even though it's bound to happen eventually.
Just to verify, I have the verizon snapdragon variant and frija does not find the firmware, is the firmware you linked for the verizon snapdragon variant?
j3ffm1ll said:
Just to verify, I have the verizon snapdragon variant and frija does not find the firmware, is the firmware you linked for the verizon snapdragon variant?
Click to expand...
Click to collapse
This version is for anyone who has N986U or N986U1 devices. Bear in mind that this firmware is CTL2, whereas Verizon locked firmware is CTL4. Can confirm that I have a Verizon N20Ultra and am on CTL2 and all features are working except RCS, but even users on CTL4 are having this same error.
Update: I've linked the CTL4 U1 firmware for faster access. When and if I come across U CTL4 VZW firmware, I'll be sure to upload to the file repository. Thanks! Merry Christmas and Happy Holidays!
I am curious as to why you say it is safe for you. I am currently on Sprint/Tmobile. I converted to U1 to get update because I am impatient. What would be the benefits of doing this for me? This is a honest question even though as I reread this, it sounds a-holish. My apologies if it sounds like i am being a jerk. I am not. I do want to know.
sclarktay4 said:
I am curious as to why you say it is safe for you. I am currently on Sprint/Tmobile. I converted to U1 to get update because I am impatient. What would be the benefits of doing this for me? This is a honest question even though as I reread this, it sounds a-holish. My apologies if it sounds like i am being a jerk. I am not. I do want to know.
Click to expand...
Click to collapse
Sure thing. When I say safer, I mean that in an RMA lens. Based on your DID, Samsung knows what your devices CSC, model, and whether your device is U branded or U1 unlocked. There is a chance that your device can be deemed "tampered" with in the case where you send it for repairs and alterations have been made, like firmware. So, only spoken from that perspective. I've would've included this use case scenario, but as you and others can see, this post was extremely wordy to begin with
denson9874 said:
Sure thing. When I say safer, I mean that in an RMA lens. Based on your DID, Samsung knows what your devices CSC, model, and whether your device is U branded or U1 unlocked. There is a chance that your device can be deemed "tampered" with in the case where you send it for repairs and alterations have been made, like firmware. So, only spoken from that perspective. I've would've included this use case scenario, but as you and others can see, this post was extremely wordy to begin with
Click to expand...
Click to collapse
@sclarktay4 This is not true and incorrect info. I have personally Verified multiple times on multiple Samsung devices. I also have some insider info how they verify tampered devices but won't get into that. Even unlocked bootloader went through fine with RMA except once but flashing u1 on u will not cause RMA issues.
As far as this thread is concerned, this information is already posted so you wasted time in writing this wordy thread. Just saying cause no point wasting time in duplicating work and causing confusion to many here who aren't advanced users.
warriorvibhu said:
@sclarktay4 This is not true and incorrect info. I have personally Verified multiple times on multiple Samsung devices. I also have some insider info how they verify tampered devices but won't get into that. Even unlocked bootloader went through fine with RMA except once but flashing u1 on u will not cause RMA issues.
As far as this thread is concerned, this information is already posted so you wasted time in writing this wordy thread. Just saying cause no point wasting time in duplicating work and causing confusion to many here who aren't advanced users.
Click to expand...
Click to collapse
My dear friend, we meet again. I must disagree because I, being a former support technician for a vendor who handled RMA for carriers (Asurion), have seen devices regretted due non-carrier firmware being loaded on them. As a senior user on this forum, it is important to address all possibilities so that users are informed. As I stated in the beginning of my post, this is to serve as a means to educate users on the process, not for those who already know the process, like yourself. I, for one, respect all comments given, but those who come on to the forum to play repeat police, I can't waste time on that. Educating new users, I'll continue to waste my time on. Good holiday, sir.
denson9874 said:
My dear friend, we meet again. I must disagree because I, being a former support technician for a vendor who handled RMA for carriers (Asurion), have seen devices regretted due non-carrier firmware being loaded on them. As a senior user on this forum, it is important to address all possibilities so that users are informed. As I stated in the beginning of my post, this is to serve as a means to educate users on the process, not for those who already know the process, like yourself. I, for one, respect all comments given, but those who come on to the forum to play repeat police, I can't waste time on that. Educating new users, I'll continue to waste my time on. Good holiday, sir.
Click to expand...
Click to collapse
Well then your process was unique at Asurion, even Samsung stores here in NYC dont know about that unique process of yours. All they care about is if there is rooting or water ingress/ physical damage. Your means to educate others is by posting duplicate threads? Please dont be suggestive by saying you respect all comments as if others dont. Repeat police?? LOL ..Stop repeating same things then.. go read and educate yourself bro, if someone is playing repeat police by urging you to not post something twice to avoid confusion that too in the same device forum, same subsection where it was already posted. You want to feel important find other ways (being senior member is not an achievement you are trying to show off here buddy) may be make efforts to help people by posting in cross device forums.
And if we meet again that means you are lucky. Happy Holidays to you too.
warriorvibhu said:
Well then your process was unique at Asurion, even Samsung stores here in NYC dont know about that unique process of yours. All they care about is if there is rooting or water ingress/ physical damage. Your means to educate others is by posting duplicate threads? Please dont be suggestive by saying you respect all comments as if others dont. Repeat police?? LOL ..Stop repeating same things then.. go read and educate yourself bro, if someone is playing repeat police by urging you to not post something twice to avoid confusion that too in the same device forum, same subsection where it was already posted. You want to feel important find other ways (being senior member is not an achievement you are trying to show off here buddy) may be make efforts to help people by posting in cross device forums.
And if we meet again that means you are lucky. Happy Holidays to you too.
Click to expand...
Click to collapse
I prefer to stay in lane and educate on what I know rather than come half-stepped. It is clear we won't see eye to eye, which after our two encounters to this point, I'm glad for that. As long as forums will exists, there will always be users like you and I, quarreling over someone else's IP who make money on the both of us. All of this is beneath us. I wish you well, I truly mean that.
denson9874 said:
I prefer to stay in lane and educate on what I know rather than come half-stepped. It is clear we won't see eye to eye, which after our two encounters to this point, I'm glad for that. As long as forums will exists, there will always be users like you and I, quarreling over someone else's IP who make money on the both of us. All of this is beneath us. I wish you well, I truly mean that.
Click to expand...
Click to collapse
Very well said. Cheers to that. This is amazing and we both agree on. Moving on wishing you well too stay safe and have an amazing holiday season.
Just wanted to say thank you for the easy to follow and use instructions and files. Took only 3 minutes to complete once all was downloaded and extracted as instructed. Cheers and thanks for taking the time to help those of us out who enjoy dabbling but don't really have the know-how to do these things without a great community of people! Thank you good sir and have a great holiday.
ethos7788 said:
Just wanted to say thank you for the easy to follow and use instructions and files. Took only 3 minutes to complete once all was downloaded and extracted as instructed. Cheers and thanks for taking the time to help those of us out who enjoy dabbling but don't really have the know-how to do these things without a great community of people! Thank you good sir and have a great holiday.
Click to expand...
Click to collapse
Glad to see that you were able to find the instructions useful and informative. I hope that you have a happy holidays as well!!!
I am curious about something and hope you can give me an explanation. This is regarding your instructions for flashing the PIT file.
I have been flashing Samsung devices for many years and in all the time I have flashed firmware, I have never extracted and then added the PIT file in Odin. Can you tell me the reasons it is necessary to do that based on the steps you outline? What does flashing the PIT file do that would not be done if you don't flash it that way?
I am not saying it is wrong to flash the PIT file, only that I would like to know the reasons it is necessary. If you can explain that I would really appreciate it.
Thanks
Geekser said:
I am curious about something and hope you can give me an explanation. This is regarding your instructions for flashing the PIT file.
I have been flashing Samsung devices for many years and in all the time I have flashed firmware, I have never extracted and then added the PIT file in Odin. Can you tell me the reasons it is necessary to do that based on the steps you outline? What does flashing the PIT file do that would not be done if you don't flash it that way?
I am not saying it is wrong to flash the PIT file, only that I would like to know the reasons it is necessary. If you can explain that I would really appreciate it.
Thanks
Click to expand...
Click to collapse
Sure, I don't mind providing an explanation. So, essentially, PIT files provide the table or map and allocation size for each partition that Odin require to have a more successful flash process. Think of it as the roadmap for the firmware. This file is included in the CSC file, so extracting is not completely necessary, as it will be accessed during the flashing process. The reason I suggest applying the PIT file along with assigning CSC is for redundancy. Also, for these reasons:
1. To avoid a "Get PIT for mapping" error when flashing.
2. Prevent "Invalid EXT4 image" issues
3. Re-partitioning/NAND Erasing
4. Avoid possible boot loops
5. Proper internal storage allocation (Ensure if you have a 512GB device, you don't end up with 128GB visible.)**
** This is only an issue if you elect to download a PIT file from the web, rather than extracting it from the firmware.
denson9874 said:
Sure, I don't mind providing an explanation. So, essentially, PIT files provide the table or map and allocation size for each partition that Odin require to have a more successful flash process. Think of it as the roadmap for the firmware. This file is included in the CSC file, so extracting is not completely necessary, as it will be accessed during the flashing process. The reason I suggest applying the PIT file along with assigning CSC is for redundancy. Also, for these reasons:
1. To avoid a "Get PIT for mapping" error when flashing.
2. Prevent "Invalid EXT4 image" issues
3. Re-partitioning/NAND Erasing
4. Avoid possible boot loops
5. Proper internal storage allocation (Ensure if you have a 512GB device, you don't end up with 128GB visible.)**
** This is only an issue if you elect to download a PIT file from the web, rather than extracting it from the firmware.
Click to expand...
Click to collapse
Thank you for an easy to understand and complete explanation. Your response is one of the reasons I love XDA - getting these kinds of answers help me and anyone else reading (who doesn't already know) to get a much better understanding of our phones and the way things work.
Thank you very much!
Geekser said:
Thank you for an easy to understand and complete explanation. Your response is one of the reasons I love XDA - getting these kinds of answers help me and anyone else reading (who doesn't already know) to get a much better understanding of our phones and the way things work.
Thank you very much!
Click to expand...
Click to collapse
Well thank you so much. As long as I'm helping someone here, then this thread is serving its purpose. I care a lot about the why as much as I care about the what. This is the reason why I make lengthy post. Maybe a far amount of users don't really care about the details, I think it's important the understand the methodology. I hope that more and more people begin to share that same ethos.