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.
Related
Well, I've asked a mod to lock the other root status thread. It was getting kind of out of hand. After about page 80, people stopped looking at what we had done so far, and trying to help by putting ideas out that already failed.
This is what we know:
Fastboot is locked down in everything but oem-78 mode. You can get to this mode by typing "reboot oem-78" at an adb shell. Fastboot is essentially unlocked, allowing fastboot boot and fastboot flash, only the .img images we try to boot or flash NEED TO BE SIGNED.
Goldcards no longer allow non signed firmware to be loaded, only signed firmware with a different SID.
All known flashing methods require the .img files to be signed by HTC. We do not have the privatekey, nor do we have any way to decrypt the key as it is RSA. Meaning this is a NO GO.
All previous known exploits (asroot2, g1 telnetd, DROID update.zip method) have been patched. They won't work. And there isn't a way around this.
All the partitions except /data are mounted as read only. Meaning, without root access, there is NO way to modify them. In the init.rc file, they are mounted rw, and directly after that mounted ro. We can read and write to /data as we wish, but NOTHING important is here.
The only folder anything can run as root out of is /system/bin. Every other partition is mounted with the nosuid option, meaning code CANNOT be run as root. Simple enough. We can't run anything as the user root, or the group root.
Lets try to stay a little more on topic this time. Please don't let this become another 40 pages of complete crap. And please keep this thread about root access, any other problems should be posted in the appropriate forum.
Thanks, and lets get this root done!
I'm currently comparing superboot.img in a hex editor to the vanilla boot.img for that phone so I can better understand what he did, and how. I'll see what I can turn up, maybe we can make one for the eris.
EDIT: It seems it's not going to be so easy. There's a lot of things changed. It appears he changed something at the top of the file right after the header, and then there is some sort of (SHA1?) hash right below that, but I don't know what it's calculated from. This is beyond my skills at the moment, I think.
Are any of the fields changed from the original boot.img show up in our boot.img? Chance of searching for each field in our img and replacing with possibly what he did?
is it possible that the guy who made superboot has htc signature, or somehow decrypted it???? 8-O
Yes I guess anything is possable but I think their is a better chance of monkeys flying out of my butt.
well i guess it was time to lock the other thread as some people could not play nice..... so i guess we will use this one now..... next idea anyone, and i am guessing jman will no longer be joing us, so it looks like we are on our own.
im ready to get this done what have we got so far?
About 140 pages of failed attempts.
well i know that much i have been sitting back following from the begining now im ready to get my hands dirty, though i have no clue what im doing
binny1007 said:
well i guess it was time to lock the other thread as some people could not play nice..... so i guess we will use this one now..... next idea anyone, and i am guessing jman will no longer be joing us, so it looks like we are on our own.
Click to expand...
Click to collapse
Ok, I missed something I think. Thats what I get for not refreshing every 10 seconds What happened to jman? Or is it better off that I not ask
punk.kaos said:
Ok, I missed something I think. Thats what I get for not refreshing every 10 seconds What happened to jman? Or is it better off that I not ask
Click to expand...
Click to collapse
I don't think I'll be following these threads anymore. I try to help you guys, but in the end some of you just don't appreciate the help.
I don't claim to be an expert, and I never promised anybody that I could root their phone. I simply have information to share that I think has brought you guys to a greater understanding of your phones and the Android system. Most of you are thankful, but I really don't need to be attacked personally in these threads that don't even have anything to do with my phone.
I'd like to thank the moderator for locking down the other forum, I'd also like to thank whichever moderator deleted the message that was quite insulting to me.... I only happened to see it because it came into my email. Yes, I subscribed to the thread via email to try to keep up with you guys and offer any help I could as quickly as I could.
I'm sorry guys, I wish you luck, but I just don't need to be berated in open forum like that for trying to help the Eris owners out, so I won't be keeping up with your rooting efforts.
There are a couple of you that have been very appreciative, and please feel free to PM me.
Thanks jman and I understand, if I was in your shoes I would do the same and I reported that post almost right after it was posted hoping you would not see it. But I know for me I have a greater understanding of my phone and like I have said before Thank you very much for your help. It's a shame to see you go but we understand.
Binny
doubt this will help, its all that htc tech support would throw up at me.
http://developer.htc.com/
contains hero and adp but nothing about eris.
jmanley69 said:
I don't think I'll be following these threads anymore. I try to help you guys, but in the end some of you just don't appreciate the help.
I don't claim to be an expert, and I never promised anybody that I could root their phone. I simply have information to share that I think has brought you guys to a greater understanding of your phones and the Android system. Most of you are thankful, but I really don't need to be attacked personally in these threads that don't even have anything to do with my phone.
I'd like to thank the moderator for locking down the other forum, I'd also like to thank whichever moderator deleted the message that was quite insulting to me.... I only happened to see it because it came into my email. Yes, I subscribed to the thread via email to try to keep up with you guys and offer any help I could as quickly as I could.
I'm sorry guys, I wish you luck, but I just don't need to be berated in open forum like that for trying to help the Eris owners out, so I won't be keeping up with your rooting efforts.
There are a couple of you that have been very appreciative, and please feel free to PM me.
Click to expand...
Click to collapse
Thanks for sticking through with us. You've been extremely helpful since day one, and I would like to say thanks and basically say what Binny said above.
I haven't had a lot of time to follow the thread, but, I too, am happy that it was locked. Hopefully the Eris owners can regroup in a day or so after we all chill out. Sigh. Fingers are still crossed for root.
Has anyone been able to actually BOOT any of the images extracted from the rom.zip via fastboot in oem-78 mode? If so, and you could post how, I might have access to an image with root access. I've tried repeated times to perform "fastboot boot recovery.img" but it sends it and then sticks on "booting..." I have moved forward with the RUU at this point, but the device never actually boots into the img.
Unfortunately, I cannot not upload the image due to my job.
Also, if anyone can help with goldcard downgrading, I might be able to downgrade to an old version with root access. My downgrade continues to fail due to the bootloader version being too high. I created the goldcard per the appropriate thread and it appeared to work as the Cell South thread indicated, but still no dice on the downgrade.
If your gold card is made right it should work.... are you putting the .zip on you gold card and renameing it PB00IMG.zip?
binny1007 said:
If your gold card is made right it should work.... are you putting the .zip on you gold card and renameing it PB00IMG.zip?
Click to expand...
Click to collapse
Yes, but it still fails with error 43, I believe. "Main version check"
Did you run the simlock option in the bootloader, and it passed
binny1007 said:
Did you run the simlock option in the bootloader, and it passed
Click to expand...
Click to collapse
Yes. Perhaps goldcard doesn't work on this device like it's supposed to.
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.
Hi Guys,
First, I beg of you not to say RTFM on similar questions here regarding this. I have read them, and read them in their entirety. The problem I have is that none of them list how to get me though my issues on my Galaxy Note 3 SM-N900A.
My problem is that I (as many others) really want to upgrade to the Kit Kat OTA released from AT&T a week or so ago. The thing is, I did root my device and as everyone know's this fails any OTA updates.
My question is two fold, but first I would like to explain that I rooted my device NOT for being able to install any custom ROM's. In fact I never had an interest in doing so as I actually like the stock OS's which right now I am still running 4.3. I rooted it specifically to be able to run network / packet sniffers on my own home network as a method to learn a little more about how things go over a network, seeing what I can learn and see if I can find any vulnerabilities. I also used it to try and clean bloat ware and other programs that with out root I can not uninstall or use, such as certain fast reboot apps. So, I really had no intention of using the Root to get me a custom ROM, as I wouldn't even know where to begin.
So my questions are this. Is there anyway that I can "un do" the root in order to let the device act as if it were never rooted? Or, is there anyway to force the OTA regardless of the device being rooted. My biggest fear is losing all the apps and files that I have on my device and I have never been able to get any kind of back up app to work, especially to restore anything from them.
I had read that one can use ODIN to flash the Kit Kat ROM, but while I have installed ODIN on my laptop, I am clueless on how to use it. I tried everything, but even with the USB drivers installed and working (I know this because plugged into the USB port, I am able to browse all the files on my device, yet ODIN continues to tell me that no device has been found.
Can someone please help me to understand what I need to do? Again, I don't care if I lose Root, I care that I don't lose all the stuff I spent months installing and getting my device where I want it. I really need someone to explain somethings to me as if I were a two year old, with out scalding me and making me feel like a complete idiot. I came here because everyone I have talked to told me that you guys would be the ones that could help me, and if you can't, then I am screwed and will have to just wipe the entire device and I just can't do that. I may wind up having to buy a new device and just transfer over what ever I can, however, in the mean time that is not an option.
To this end, I come begging for some serious help since I know you guys are the literal gods of Androids. If I must take some kind of custom ROM in order to get Kit Kat, I am somewhat willing, but I do not fully understand or know what ROM I would want to install as I have never in my life seen a custom ROM and what the benefits of having one are which is kind of why I really want to stick with the stock ROM and just keep getting the updates via OTA.
I have all the faith in the world you guys can help, I just don't know if anyone is willing to help since I know similar questions have been asked, but I do not know how to use what I learned for my particular device.
Thanks very much.
EU
Dardwizzle said:
Hi Guys,
First, I beg of you not to say RTFM on similar questions here regarding this. I have read them, and read them in their entirety. The problem I have is that none of them list how to get me though my issues on my Galaxy Note 3 SM-N900A.
My problem is that I (as many others) really want to upgrade to the Kit Kat OTA released from AT&T a week or so ago. The thing is, I did root my device and as everyone know's this fails any OTA updates.
My question is two fold, but first I would like to explain that I rooted my device NOT for being able to install any custom ROM's. In fact I never had an interest in doing so as I actually like the stock OS's which right now I am still running 4.3. I rooted it specifically to be able to run network / packet sniffers on my own home network as a method to learn a little more about how things go over a network, seeing what I can learn and see if I can find any vulnerabilities. I also used it to try and clean bloat ware and other programs that with out root I can not uninstall or use, such as certain fast reboot apps. So, I really had no intention of using the Root to get me a custom ROM, as I wouldn't even know where to begin.
So my questions are this. Is there anyway that I can "un do" the root in order to let the device act as if it were never rooted? Or, is there anyway to force the OTA regardless of the device being rooted. My biggest fear is losing all the apps and files that I have on my device and I have never been able to get any kind of back up app to work, especially to restore anything from them.
I had read that one can use ODIN to flash the Kit Kat ROM, but while I have installed ODIN on my laptop, I am clueless on how to use it. I tried everything, but even with the USB drivers installed and working (I know this because plugged into the USB port, I am able to browse all the files on my device, yet ODIN continues to tell me that no device has been found.
Can someone please help me to understand what I need to do? Again, I don't care if I lose Root, I care that I don't lose all the stuff I spent months installing and getting my device where I want it. I really need someone to explain somethings to me as if I were a two year old, with out scalding me and making me feel like a complete idiot. I came here because everyone I have talked to told me that you guys would be the ones that could help me, and if you can't, then I am screwed and will have to just wipe the entire device and I just can't do that. I may wind up having to buy a new device and just transfer over what ever I can, however, in the mean time that is not an option.
To this end, I come begging for some serious help since I know you guys are the literal gods of Androids. If I must take some kind of custom ROM in order to get Kit Kat, I am somewhat willing, but I do not fully understand or know what ROM I would want to install as I have never in my life seen a custom ROM and what the benefits of having one are which is kind of why I really want to stick with the stock ROM and just keep getting the updates via OTA.
I have all the faith in the world you guys can help, I just don't know if anyone is willing to help since I know similar questions have been asked, but I do not know how to use what I learned for my particular device.
Thanks very much.
EU
Click to expand...
Click to collapse
does ur kies run? if so turn it off.
USB debugging off? turn it on.
are u in download mode of ur phone? if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen.
after that u can plug in ur phone.
Sent from somewhere under the sky, at the corner of this rounded earth.
antique_sonic said:
does ur kies run? if so turn it off.
USB debugging off? turn it on.
are u in download mode of ur phone? if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen.
after that u can plug in ur phone.
Sent from somewhere under the sky, at the corner of this rounded earth.
Click to expand...
Click to collapse
Hi antique_sonic, I would just like to clarify a couple things as well as answer your questions.
>does ur kies run? if so turn it off. <--- If you mean is it installed on my laptop and work? Yes it is, and yes it does, however, I almost never use it. Mainly because I was told that once you root a Samsung Device, Kies is no longer able to be used.
>USB debugging off? turn it on. <--- It is and has been turned on in an effort to try to sideload KitKat, but that was a hug fail. But I will leave it on for this discussion.
>are u in download mode of ur phone? <---- I have gotten here before but don't exactly know what to do once I am there since I don't know where to get a Kit Kat ROM, where to put it once I have it, or how to use anything in d/l mode.
> if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen. after that u can plug in ur phone. <--- Are these instructions for wiping the device back to the factory default? Will I lose everything currently installed and loaded on my Note 3? Or does this some how fix / allow for the OTA update to install completely because it no longer can tell the device is rooted?
Again, I must apologize because this is so greek to me.I am just trying to understand at this point what infact the instructions you gave me do, and what they are intended for. Is this just to get the USB drives to work properly? Or is this something that will help me undo root so that I would be able to install KitKat via the AT&T OTA. If now the latter, where I can I get a complete Kit Kat ROM and use ODIN to flash the ROM? This outcome would suck because I believe that this will cause me to lose everything on my device I worked so hard to get where I wanted. I have just over looked the fact that in rooting my device I there by killed my ability to keep my device updated with the latest OTA releases / patches.
Again, I appreciate you reply, but sadly I am in need of a bit more info if you could please.
Thank you so very much. I hope one day to be able to pay it forward, passing along the knowledge you have shared with me,
Regards,
EU
Dardwizzle said:
Hi antique_sonic, I would just like to clarify a couple things as well as answer your questions.
>does ur kies run? if so turn it off. <--- If you mean is it installed on my laptop and work? Yes it is, and yes it does, however, I almost never use it. Mainly because I was told that once you root a Samsung Device, Kies is no longer able to be used.
Click to expand...
Click to collapse
do check, is it running in background ? check your task manager. if so, kill the process. Kies should not run together with ODIN. Otherwise sometimes will give problem to your ODIN process.
I normally only install the USB driver only, as this is the only thing needed to connect your phone to comp (as MTP, or as ODIN connection).
Dardwizzle said:
>are u in download mode of ur phone? <---- I have gotten here before but don't exactly know what to do once I am there since I don't know where to get a Kit Kat ROM, where to put it once I have it, or how to use anything in d/l mode.
Click to expand...
Click to collapse
ok, in a very simple word. download mode is basically a state whereby your phone is ready to download system files and install the system files on your device.
This is the only state possible to get a connection to your ODIN PC to flash stock firmware, recovery (in .tar/.md5 format).
How to get the KK ROM ?
1) identify your device. which model it is. N9005? N900T? N900A? N900 blablabla?
2) goto samfirmware.com (register there if you don't have account. it is free). after that you can just find your firmware by typing on the search device textbox your device model (e.g N9005), and it will come out the list of your device firmware (normally they will show for the latest firmware list)
3) choose the firmware that you want to download (if your device N9005 international 32 gb, try to avoid the Hongkong / Taiwan firmware, as they have different PIT partition).
4) once you have the downloaded zip file from samfirmware, extract the zip, and then you will get the (.tar/.md5) file. Now you can use to flash this one over ODIN.
Dardwizzle said:
> if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen. after that u can plug in ur phone. <--- Are these instructions for wiping the device back to the factory default? Will I lose everything currently installed and loaded on my Note 3? Or does this some how fix / allow for the OTA update to install completely because it no longer can tell the device is rooted?
Click to expand...
Click to collapse
no. no. no.
This is how to go into download mode in your device
Not yet talking about factory reset.
But yes, you have to backup your internal storage, as sometimes upgrading will cost you to do factory reset, and your internal storage will be gone.
Dardwizzle said:
Again, I must apologize because this is so greek to me.I am just trying to understand at this point what infact the instructions you gave me do, and what they are intended for. Is this just to get the USB drives to work properly? Or is this something that will help me undo root so that I would be able to install KitKat via the AT&T OTA. If now the latter, where I can I get a complete Kit Kat ROM and use ODIN to flash the ROM? This outcome would suck because I believe that this will cause me to lose everything on my device I worked so hard to get where I wanted. I have just over looked the fact that in rooting my device I there by killed my ability to keep my device updated with the latest OTA releases / patches.
Click to expand...
Click to collapse
up to this point, I just remembered that you have N900A (AT&T) version. hahaha.
I go check the samfirmware, no release of KK yet at the samfirmware.
I'm sorry, I own N9005, and I never explore too much on the N900A, so I won't know what is the latest release, and where to get it other from samfirmware.
Dardwizzle said:
Again, I appreciate you reply, but sadly I am in need of a bit more info if you could please.
Thank you so very much. I hope one day to be able to pay it forward, passing along the knowledge you have shared with me,
Regards,
EU
Click to expand...
Click to collapse
no problem. you just get your latest firmware first, once you have it, you let me know, i can give you step by step in detail, on how to flash to your device.
antique_sonic said:
up to this point, I just remembered that you have N900A (AT&T) version. hahaha.
I go check the samfirmware, no release of KK yet at the samfirmware.
I'm sorry, I own N9005, and I never explore too much on the N900A, so I won't know what is the latest release, and where to get it other from samfirmware.
no problem. you just get your latest firmware first, once you have it, you let me know, i can give you step by step in detail, on how to flash to your device.
Click to expand...
Click to collapse
Sure sure, just laugh at me why don't ya!! LOL I will continue to try to find the appropriate firmware. I guess if I learned one valuable lesson in all this, it is just don't root your device if you don't plan on using custom ROM's. I had no idea that there would be no way to "unroot" your device once it's rooted. I was really hoping that you could just undo what ever is done to actually root the device, this way the OTA's will just start working again. Or that there would be a way to just force the OTA regardless of whether the device is rooted. I am not sure I truly understand why the OTA just won't install just because the device is rooted.I mean sure it adds SU to the device, and unlocks (I think) the boot partition or the boot loader, which ever, but regardless, why should the OTA package care and fail to install just because of that change?
Anyway, that's probably a discussion for another thread. I actually did find a Kit Kat zip that is like 150MB's it has a boot.img inside the zip, but it has nothing with an extension that ODIN can recognize. I would love to show you the zip, but it's too large to attach or email. The file name is 2400258.zip, but I forgot where I downloaded it from. It may be what I need to do the job, but with out someone seeing the zip I have no way of knowing if it's the files I need. I was not about to find any files with in it that are in txt readable format for me to say exactly what it is. It does have subfolders names Google and Android and the like but I am sure that is pretty useless with out seeing the full zip.
I will keep my eye on this thread and when I find something I can work with, or if you guys find anything I can work with I will come back and see where we can go next.
Thanks again bud!
Dardwizzle said:
Sure sure, just laugh at me why don't ya!! LOL I will continue to try to find the appropriate firmware. I guess if I learned one valuable lesson in all this, it is just don't root your device if you don't plan on using custom ROM's. I had no idea that there would be no way to "unroot" your device once it's rooted. I was really hoping that you could just undo what ever is done to actually root the device, this way the OTA's will just start working again. Or that there would be a way to just force the OTA regardless of whether the device is rooted. I am not sure I truly understand why the OTA just won't install just because the device is rooted.I mean sure it adds SU to the device, and unlocks (I think) the boot partition or the boot loader, which ever, but regardless, why should the OTA package care and fail to install just because of that change?
Anyway, that's probably a discussion for another thread. I actually did find a Kit Kat zip that is like 150MB's it has a boot.img inside the zip, but it has nothing with an extension that ODIN can recognize. I would love to show you the zip, but it's too large to attach or email. The file name is 2400258.zip, but I forgot where I downloaded it from. It may be what I need to do the job, but with out someone seeing the zip I have no way of knowing if it's the files I need. I was not about to find any files with in it that are in txt readable format for me to say exactly what it is. It does have subfolders names Google and Android and the like but I am sure that is pretty useless with out seeing the full zip.
I will keep my eye on this thread and when I find something I can work with, or if you guys find anything I can work with I will come back and see where we can go next.
Thanks again bud!
Click to expand...
Click to collapse
I don't like spoonfeeding too much actually.
but I find u r quite funny. no offence.
I have no idea this will work or not, but I found this as the 1st search result on Google.
http://www.droidviews.com/install-android-4-4-2-kitkat-ota-on-att-galaxy-note-3-sm-900a/
just have a look first nd don't do anything till u understand the article.
Sent from somewhere under the sky, at the corner of this rounded earth.
antique_sonic said:
I don't like spoonfeeding too much actually.
but I find u r quite funny. no offence.
I have no idea this will work or not, but I found this as the 1st search result on Google.
(I had to remove the link as the website thought I was adding it and gave me a no no warning that I can't post outside links cause I be a newbie!) BAH!!!
just have a look first nd don't do anything till u understand the article.
Sent from somewhere under the sky, at the corner of this rounded earth.
Click to expand...
Click to collapse
Hey antique_sonic, no offence taken my friend, I am a giant goof ball, but I am also someone who doesn't mind working out my own problems. It's just sometimes with things like this where I am clueless and need a little hand holding. It's nice to know that there are people like you around to help out the dopes like me My apologies for not getting back to you sooner, and I will be looking into the link you sent tonight. I haven't been feeling well lately, I have two herniated disks in my back and I have End Stage Liver disease and I am only 39, so I sometimes get a bit under the weather and am down for the count for a few days. So I do appreciate your patience with me and all the help and direction you are giving me. I try never to abuse the help as that is no way to learn, and learning is actually one of favorite hobbies! Weird huh.... So, I am off to go read the link you provided me and update the stock on my website and hope I make some more sales so I can get some money to buy a new phone when I brick this one! LMAO! Thanks again Sonic, I really appreciate everything!
Dardwizzle said:
Hey antique_sonic, no offence taken my friend, I am a giant goof ball, but I am also someone who doesn't mind working out my own problems. It's just sometimes with things like this where I am clueless and need a little hand holding.
Click to expand...
Click to collapse
No worries and yeah you should try to find first. by this way, you will learn faster, compare if someone do the spoonfeed.
Dardwizzle said:
It's nice to know that there are people like you around to help out the dopes like me My apologies for not getting back to you sooner, and I will be looking into the link you sent tonight.
Click to expand...
Click to collapse
My pleasure to help. And no worries for late reply, as I will do the same when I busy with my real life job.
Dardwizzle said:
I haven't been feeling well lately, I have two herniated disks in my back and I have End Stage Liver disease and I am only 39, so I sometimes get a bit under the weather and am down for the count for a few days. So I do appreciate your patience with me and all the help and direction you are giving me.
Click to expand...
Click to collapse
you are welcome mate. I'm sorry to read the news about your conditions. I can't say anything about this, but wish you all the best. Don't ever feel down in whichever state you are, just do the best in life, and we will never regret that 1 more day has passed.
Dardwizzle said:
I try never to abuse the help as that is no way to learn, and learning is actually one of favorite hobbies! Weird huh.... So, I am off to go read the link you provided me and update the stock on my website and hope I make some more sales so I can get some money to buy a new phone when I brick this one! LMAO! Thanks again Sonic, I really appreciate everything!
Click to expand...
Click to collapse
GOOD !!!
go and grab sales, rather than you brick the phone.
Once again, u r welcome mate.
ok, this method does not work - there was an attempt to flash a rooted system.img.ext4 image from a developer edition to a retail, it failed... with the exception of the members of this forum who verified that this method did not / does not work (thanks to all) the following set of instructions does not work...
again, sorry -
Note: I am not responsible for anything that might happen to your device. Please make a backup if possible or please make sure you know how to restore your phone back to factory using the correct stock roms. This Note 4 Developer forum does have resources to do so. Before proceeding below, please ensure you have tried to restore from stock roms via ODIN 3.09 (or correct version), as it may be the only way to recover your device.
The post here suggests (but untested / verified on a retail Verizon Note 4 NJ5) that a system.img.ext4 image, with root (Super SU), can be flashed using ODIN 3.09 to a retail device. I ask more experienced developers to try this first, and post your responses here. I will cite / note the steps which I have done below. I really hope other developers assist in the verification process - let me know if this works or not. I will pull this post if in fact this process fails
Using EFS Professional v2.1.80 Beta and a Verizon Note 4 Developer Edition SM-N910V, on the 4.4.4 version N910VVRU1ANJ5, did the following.
0. Restored the SM-N910V (Developer) to near stock - the only thing different was the recovery partition which had been previously flashed to TWRP
1. Downloaded UPDATE-SuperSU-v2.16.zip from this post (also where TWRP came from), and with my Note 4 connected to a PC, copied the zip file to the phone; rebooted into recovery, flashed Super SU with TWRP. Now it's rooted, right? restarted phone. Installed Busybox (required by EFS Professional), prompted me for root access, permission granted. Busybox ran. Good.
2. - instruction no longer available...
3. Using TWRP, reflashed my phone back to stock before root. Used ODIN 3.09 with my phone in download mode, flashed the SM-N910V_2015130_0116.tar back to my Developer edition, performed a factory reset, rebooted, did a minimal phone setup (bailed out of setup when I could) but Used the busybox.apk (stericson) to test root; installed it using the unknown resources option, ran it, it asked for root, I assume this was a sign that the ODIN flash went well and root held...
So, what remains - asking the developer community to test flashing the SM-N910V_2015130_0116.tar on a retail device using ODIN AP Mode, I do not have one to test...
Here is what I'm hoping for. That the SM-N910V_2015130_0116.tar can be successfully flashed to a retail device, which will then be fortified with root, yes. Maybe that can lead to the "promised land" where a developer, again - more talented than me, can find a weakness in the retail version, from within, to obtain root by other means; unless what I have done, is it!! If it is. Excellent...
If this does work on a retail verizon Note 4 (NJ5), excellent, glad to have helped. If there is a bounty due, ok, I suppose I could accept but not expecting it. I am more excited to give back to the community who has so given their precious time / resources... and so it goes...
Again, please let me know if this worked. I will down this thread immediately if it is detrimental to devices...
Rob
Bump for our possible savior!
Sent from my Note 4.
thanks
Subiegsr said:
Bump for our possible savior!
Sent from my Note 4.
Click to expand...
Click to collapse
Well, thanks, but not yet... And I'm just a measly Note 4 user who spent 700 bones on a device, had some willingness to try something different. actually, it was more common, right? I have seen other developers like beanstown106 (Nathan) and hsbadr do similar, in just handing us a pre-rooted system image only. Hey, if it's a minimum, great - it's a start. I cannot really take credit in that sense, but thanks for the sentiment just the same... greatly appreciated.
We really have to hope that the system.img.ext4 in that flashable package can be put onto a retail - let the games begin (keeping fingers crossed..)
thanks
Any testers yet? I will later today if no one tries before me.
Sent from my SM-N910V using XDA Free mobile app
This won't work. The reason it went okay on your device is because it's a DE with an unlocked bootloader. On retail, it won't boot.
bobbarker2 said:
This won't work. The reason it went okay on your device is because it's a DE with an unlocked bootloader. On retail, it won't boot.
Click to expand...
Click to collapse
ok, that's what we need to find out. what about the image will the retail edition not like?
comment - I remember flashing different modems on a locked note 3, that worked but at the same time I do remember flashing different boot or recovery on a note 3 and it not starting ( validating your claim here... ) - would it be like that experience?
here was my thinking:
1. the worst that'd happen is, yes the phone won't start, but not a brick per se, as Samsung unit's are pretty resilient, and a re-odin of the original system.img.ext4 ( belonging to the retail ed. ) can be easily restored, right?
2. this is an Identical version that goes on both phones, and correct me if I am wrong but the system partition can be flashed on both ( getting that sense looking at hsbadr's thread - to be clear, not that he said it would, he has not indicated that in any post, just my interpretation of what is flashed between the two phones )
lastly, if in fact it does not work, I will simply pull / close this post - with a final comment / statement and we move on.
thanks for your information, this is what we need to know...
anticloud said:
ok, that's what we need to find out. what about the image will the retail edition not like?
comment - I remember flashing different modems on a locked note 3, that worked but at the same time I do remember flashing different boot or recovery on a note 3 and it not starting ( validating your claim here... ) - would it be like that experience?
here was my thinking:
1. the worst that'd happen is, yes the phone won't start, but not a brick per se, as Samsung unit's are pretty resilient, and a re-odin of the original system.img.ext4 ( belonging to the retail ed. ) can be easily restored, right?
2. this is an Identical version that goes on both phones, and correct me if I am wrong but the system partition can be flashed on both ( getting that sense looking at hsbadr's thread - to be clear, not that he said it would, he has not indicated that in any post, just my interpretation of what is flashed between the two phones )
lastly, if in fact it does not work, I will simply pull / close this post - with a final comment / statement and we move on.
thanks for your information, this is what we need to know...
Click to expand...
Click to collapse
As bobbarker2 said two posts above it worked for you because you have a unlocked DE device. Authorization fails without the proper signature on the retail phone. This can only be attained from Samsung or Verizon. Thanks for trying but it's a no go.
EDIT: Yes, I did try to flash it on the retail version.
thanks.
howellcp said:
Any testers yet? I will later today if no one tries before me.
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
I saw bobbarker2's comment - thinking it won't work. I'd say, as long as you can reflash / recover your phone back to normal / working condition, go for it. My comment to bobbarker2 was that this may be worth a shot. I'd try it as long as I had a way to recover. I am not thinking this will lock a phone or anything like that, just make it not boot, like he claims, and a recovery of what should be on the phone will make it right...
Like I suggested to bobbarker2 - I am thinking this would flash and possibly boot (be ok) as it is just the system image, not any other file, and more so, I think it's the same system that goes on the retail and the developer. I am not knowledgeable enough to know yet (some might think dangerous enough) for sure, but just the same that's why I asked someone who has more knowledge than I, and I suspect you and bobbarker2 are better suited than I to know, plus, if it were that easy, it'd already be done this way, right? or is it the case where not too many people have a both a retail and a developer edition to find out on their own, it's a medium but recoverable risk.
just my two cents - proceed with caution.
The file won't flash. It gives an auth error in Odin.
gotcha.
Misterxtc said:
As bobbarker2 said two posts above it worked for you because you have a unlocked DE device. Authorization fails without the proper signature on the retail phone. This can only be attained from Samsung or Verizon. Thanks for trying but it's a no go.
Click to expand...
Click to collapse
ok, thanks - now I know, all in favor of closing this set of posts?
I will also pull the download too, to be safe.
ok.
WarlockLord said:
The file won't flash. It gives an auth error in Odin.
Click to expand...
Click to collapse
now I know.
thanks
sorry guys, chalk one up for too much knowledge not enough experience (referring to me )
anticloud said:
now I know.
thanks
sorry guys, chalk one up for too much knowledge not enough experience (referring to me )
Click to expand...
Click to collapse
No need to be sorry, thanks for trying.
Development has halted . . . See post #5
I am not responsible for your phone, etc, etc!
Dont want to read through? This flashable zip changes the logo you see when first turning on your phone. Not the boot animation, but before that.
The flashable zip will edit param.bin partition which on the A520W happens to be mmcblk0p9, changing the stock samsung startup splash.
One could easily port this to A520F by changing the updater-script to indicate mmcblk0p8, BE SURE TO CHECK PARTITION, check properties of 'PARAM' in /dev/block/platform/13540000.dwmmc0/by-name/ for exact partition to in updater list; as well as for any other device for port attempts and remember to check screen resolution.
To-do list:
Backup script
Uninstall script
Ports
Requests
If you get "Incorrect Pin/Password" on boot (rare):
Reboot to recovery + wipe cache and dalvik cache
You should be good to go, will be in comments later for support.
SCREENSHOT FROM FILE
Code:
https:// imgur .com/a/i1lgxIa
Remove spaces, I am too new to post links.
DOWNLOAD (Remove spaces. Feel free to examine.)
Code:
https:// drive. google .com/file/d/1OIrVv91ThDPrcPUFGCYDaJnPeT94_1gZ/view?usp=drivesdk
UPDATE I remembered this project and threw together a couple more before bed. Cheers!
Just wondered, is the splash logo all that param.bin does? I was trying to flash something last night and Odin failed at param.bin.... Just wondered if I need it at all or can I ditch it and try flashing again?
Sent from my [device_name] using XDA-Developers Legacy app
param.bin to my understanding without googling, holds certain parameters of the early boot process, not only this image.
Are you flashing forward or across versions? As of Oreo, we cant flash versions older than what is installed, to my understanding. Flash parameters are also more strict in Odin and this makes it tempermental.
Make sure you have the right odin .zip. I had the same problem and only had to get the specific version release new enough of Oreo for my carrier/device. At ~1day per download however, it got tiring a few times. Look up software versions and match installed suffix to the new flashable.
Pawprints1986 said:
Just wondered, is the splash logo all that param.bin does? I was trying to flash something last night and Odin failed at param.bin.... Just wondered if I need it at all or can I ditch it and try flashing again?
Click to expand...
Click to collapse
param.bin to my understanding without googling, holds certain parameters of the early boot process, not only this image. I have not investigated yet, will update.
It's my understanding that as of Oreo, we cant flash versions older than what is installed. Flash parameters are also more strict in Odin and this makes it tempermental.
Make sure you have the right odin .zip. I had the same problem and only had to get the specific version release new enough of Oreo for my carrier/device. At ~1day per download however, it got tiring a few times. Look up software versions and match installed software suffix seen in download mode to new flashable, or aim for a newer version suffix.
TL;DR Development halted, broke my A5. TAKE OVER, SQUAD; my new working device is now 2018 A8 (Canadian A530W & also International A530F very soon.). Catch me on that forum!
ANYWHO...
Ths file was experimentally created for the A520W Canadian variant which I had and was hoping to make a library of splash screens for all of us.
This said, my process was admittedly highly unstable and possibly kernel specific, so sorry for the risk:reward ratio (not, we know what we are doing here is custom work, not my nukes etc.) I definitely worry my arse off sometimes with my only phone being the guinea pig, so MAKE A FULL NANDROID BACKUP, ALWAYS HAVE ONE. ph logs help too to your error reports
Needless to say I got busy and hope that someone picks up the information I found to give us some dope initial splash screens as found in 'param.bin'
I am starting my work on a different device, the 2018 A8. If you have any A8 buddies point 'em my way! I'm dedicated to having this rom posted in a week or two and will need A530F (international model) to test (WHO REMEMBER TO MAKE BACKUPS & TAKE LOGS).
It was a pleasure experimenting in the A-series 2017 community and I wish yall the best of luck with future sick modz.
Feel free to take over this thread or suggest that someone knowledgeable enough do! Or learn! Bloody love this sort o modification, DONT LET IT DIE!?
Regards,
deftylefty, leaving the 2017 A series behind right when things get cool.
------------
The name's Ty D.
— they call me Tidy, 'cause that's the sort of work I do.
deftylefty said:
TL;DR Development halted, broke my A5. TAKE OVER, SQUAD; my new working device is now 2018 A8 (Canadian A530W & also International A530F very soon.). Catch me on that forum!
ANYWHO...
Ths file was experimentally created for the A520W Canadian variant which I had and was hoping to make a library of splash screens for all of us.
This said, my process was admittedly highly unstable and possibly kernel specific, so sorry for the risk:reward ratio (not, we know what we are doing here is custom work, not my nukes etc.) I definitely worry my arse off sometimes with my only phone being the guinea pig, so MAKE A FULL NANDROID BACKUP, ALWAYS HAVE ONE. ph logs help too to your error reports
Needless to say I got busy and hope that someone picks up the information I found to give us some dope initial splash screens as found in 'param.bin'
I am starting my work on a different device, the 2018 A8. If you have any A8 buddies point 'em my way! I'm dedicated to having this rom posted in a week or two and will need A530F (international model) to test (WHO REMEMBER TO MAKE BACKUPS & TAKE LOGS).
It was a pleasure experimenting in the A-series 2017 community and I wish yall the best of luck with future sick modz.
Feel free to take over this thread or suggest that someone knowledgeable enough do! Or learn! Bloody love this sort o modification, DONT LET IT DIE!?
Regards,
deftylefty, leaving the 2017 A series behind right when things get cool.
------------
The name's Ty D.
— they call me Tidy, 'cause that's the sort of work I do.
Click to expand...
Click to collapse
is this method working for A3 2017?
leo31 said:
is this method working for A3 2017?
Click to expand...
Click to collapse
Yes, however you must use the param partition from your current version of firmware for it to not require a full reset