Database Users

Odin vs. Kies...

Hi Everyone,
I just laid my hands on the new Galaxy S. I was thinking before porting all my data into it, I will be upgrading it to the Froyo then transfer all the data. I read through the forums/guides, i found there are two ways of doing it. One is Odin and the other is Kies. Since this is my first step into the Android world, i would like to know which one is better and the preferred method of upgrading the phone's OS.

I have same ques. too.. And which is best rom for my sgs..
Sent from my GT-I9000M using XDA App

Depends on what you want to do with your phone and what risks you are prepared to take. There is always a risk flashing your phone will 'brick' it i.e. make it unusable. If you flashed via Kies as this is official Samsung you're covered for a replacement phone by the warranty.
Odin is an unofficial program supporting unofficial upgrades, i.e. brick you're phone with this and if you don't know what you're doing you're stuffed. People at Xda are helpful but it can mean the death of you're phone.
Advantages - you choose the ROM / software you want. No bloat-ware from carrier. Generally cooked ROM's have sorted the 'lag' problem which slows most versions of the Galaxy S (even on Froyo 2.2). They are generally upgraded faster too but don't seem as common for Galaxy S as for HTC phones (someone please feel free to contradict me). ROM Manager app from the market should be able to download Cyanogen mod (supposed to one of the best) when it's finished for the Galaxy S.
I couldn't get Odin to work on Win7 64bit so I went for the official 2.2 update via Kies then used a 'lagfix' downloaded via the market (which also invalidates your warranty...). RyanZA (OCLF on market) worked for me really well on Android 2.1 but haven't tried version 2 with Froyo 2.2. I used a Voodoo oneclick lagfix but there's something going on between the developers and it was removed from the market. You may still be able to get the apk app file to install from SD card if you Google it but I can't find it. I used this and it worked really well.
Anyway, if you know this already my apologies. There's lots of other's here who know much more than I do but thought I'd share my limited experience so far.

I am guessing that the the Kies (I haven't installed it yet), needs a steady internet connection.
The Odin wont need it, since i am already downloading all the data to my PC.
If this is correct... i think i should try out the Odin, as my internet connection is too unreliable and gets disconnected every so often.
Also,
1. How would the Samsung people know that I have used Odin or Kies?
2. If I have installed Lagfix and i uninstall lagfix before taking it to Customer Service would they be able to find out?
Pretty newbie questions, but i hope you will clarify!

hell_storm2004 said:
I am guessing that the the Kies (I haven't installed it yet), needs a steady internet connection.
The Odin wont need it, since i am already downloading all the data to my PC.
If this is correct... i think i should try out the Odin, as my internet connection is too unreliable and gets disconnected every so often.
Also,
1. How would the Samsung people know that I have used Odin or Kies?
2. If I have installed Lagfix and i uninstall lagfix before taking it to Customer Service would they be able to find out?
Pretty newbie questions, but i hope you will clarify!
Click to expand...
Click to collapse
First Kies completes the download before flashing your phone the same as Odin and your phone stores a record of the latest ROM / Kernal installed on it. It's under 'Settings' - 'About Phone'... See Firmware, Baseband and Kernal and Build Number.
Some lagfixes do have uninstalls so should be OK if uninstall works.

Ok. I'll go for Froyo with Kies. When Gingerbread becomes official then i'll take on Odin.
I'll have to look into lagfix. I have no clue which one's come with uninstall and which one's don't!

Personally I prefer Odin over Kies. Kies has bricked my phone twice and I have had issues getting Kies to recognise my phone. Before you decide to upgrade with either method make sure your 3 button combo works, if not then you really need to get this working as its your saving grace should something go wrong during or after a flash!

hell_storm2004 said:
Ok. I'll go for Froyo with Kies. When Gingerbread becomes official then i'll take on Odin.
I'll have to look into lagfix. I have no clue which one's come with uninstall and which one's don't!
Click to expand...
Click to collapse
Always disable or uninstall a lagfix prior to upgrading.

sean2476 said:
3 button combo
Click to expand...
Click to collapse
What is that???

3 button combo puts your phone into download and/or recovery mode. Vol up/ down Home key followed by power button [holding all 3 at once] Vol up for recovery mode. Vol down for download mode. If this doesn't work then forget flashing until you get it working.

imho Heimdall is the way to go. I wouldn't even install Kies.

Now that is new!
I only knew of two. Now in comes Hiemdall? This is confusing. Now I am from India. I have to check what my Operator is giving me! I may have to do Odin out of force rather than choice.

You may also need to ' root' your phone too before you can apply any of these changes as otherwise the phone is locked down. Look for an app called z4root on xda. It opens up your phone to these other apps (there are other ways of rooting but they can be quite involved for someone new to Android).

If you want to use Odin or Heimdal, & dont want to install Kies, check my signature for Samsung Drivers.
Install them & connect your phone to PC via USB & check if its recognized.

A forewarning & a suggestion.
Kies is known to F**k up phones into unusable state. & so is Odin. Heimdal is pretty geeky for most people.
If you endup with a bricked phone, you can always act stupid & convince the service centre guys that Kies was the culprit. I have Bricked 2 of my friend's phones & have gotten them a brand new replacement from Samsung.

hell_storm2004 said:
Now that is new!
I only knew of two. Now in comes Hiemdall? This is confusing. Now I am from India. I have to check what my Operator is giving me! I may have to do Odin out of force rather than choice.
Click to expand...
Click to collapse
Before you attempt anything switch off your phone completely, hold Vol up + Menu + Power buttons in that order. when the phone shows the samsung splash screen, release the power button for a second while still holding the other two. Again press it back & hold all three till it lands you in the recovery mode.
If your phone can do this, you can take any risk.

Also PM rahulrulz & kalpik, they seem friendly & helpful & knowledgable.

Ok fellas! Its game on now... First let me read through everything. I think I have to read through Hidemall now as well. I like geeky stuff. Its just that this is something completely new for me! About the other people you mentioned, I don't know them! Since at least we are formally acquainted... I would PM you!!

MIUI rom - Questions, Issues, Bugs, Problems, Complaints

Hi to all,
I created this thread here is for existing users, potential users, interested users and experienced users or any casual visitors who wants to know more about the rom. Well, SGS users will ask why create a thread just for this, when there is another one over at the development section. The answers are listed as follows:
To reduce the number of posts in the other thread (reduce spamming) thereby not bogging down the developers with issues that can be solved by the users. And they can spend their time to concentrate what they do best, which is improving the MIUI Rom.
To consolidate questions, problems, bug reports, comments in one place. As you can see from the other thread, many a times, some of the posts which benefits the users were consumed by newer posts. While there is a SEARCH function, I can understand it can sometimes be a challenging task just to sieve through the searched posts results. I know we can't eliminate users posting repeated issues, but at least this will attempt to reduce those posts.
To allow new xda members who are on MIUI but unable to post their ideas, comments, etc. This is also an important avenue to allow new xda members to have a voice. While they may be new, they might have tips, tricks and also can help to resolve issues. Issues brought up can be shared by everyone too.
To allow the developers concentrate on improving the MIUI rom. Who doesn't want a better MIUI? Of course the developers doors will always be open, and will help out whenever they can, but wouldn't it be better for us to let them concentrate on what they do best, and what we want best?
So, to make it successful, I need you guys to help one another out, like what I have seen over the other thread.
This thread belongs to all of you, and I am sure that there is active participations in here.
MIUI has a pretty long history. However, for our device, MIUI has just evolved. Likewise, the user base has just started to grow. There will be times when even the most experienced user or developer will get stumped too, and not able to come up with a solution to resolve. We can see from the other thread that there are diverse views regarding battery life, sdcard issue, etc etc. We will not know since the usage pattern of each individual is as good as your fingerprint. No one is alike. Therefore we seek your understanding that issues not solved immediately will be looked into seriously by the team. There will always be limitations for every rom, regardless what base they come from.
All we ask is whether this rom fits your usage or not. And the only way for you is to try it out. Feel it, experience it, and judge for yourself if this rom fits you, can you live with the shortcomings of the rom. If you decide that this rom doesn't fit your daily needs, you can just simply flash to another rom that fit your needs better. And you can at least tell yourself that I have tried but it is not suitable.
Is this thread some form of advertising? Well, again different interpretations for different people. We will not go into that as we believe the QUALITY OF THE ROM WILL SPEAK FOR ITSELF.
One thing that can be said though, credits goes to the cm7 team, the official MIUI developers too. And each day, we can see breakthroughs. I do foresee a bright future for this rom here.

FAQ Section​
[Written by Galnet, g00ndu and me]
Before asking for help, please read through post 1 to post 4. Most of the issues have been addressed in this 4 posts. By doing so, you are helping to keep this thread clean.
1. APP RELATED:​
1.1 Apps crashing all the time!
Simply enter recovery mode and do a Format on Data, System, Cache
1.2.1 Apps restored from backup not working
I would always flash from clean and redownload all your apps from market. I know you can backup and restore, but to me this causes alot of issues which people bring up all the time. If you want a clean install and avoid any issues in the long run, then 15 - 20 minutes of redownloading isn't as bad as hours of issues!
Also, if you want to try to restores apps using Titanium Backup, restore "APP ONLY," restoring data causes problems.
1.2.2 3rd party apps force closing
Turn off compatibility mode. Settings > Programs Tab > Manage Applications > All Tab > Select app > Turn off OR IF IT STILL FORCE CLOSES Settings > Programs Tab > Manage Applications > All Tab *again* > Select app > Clear Data > Uninstall and then reinstall using Market.
1.3 Apps not installing
Clear market cache and try again.
1.4 Can't See Paid Apps in Market
Download SGS-Tools and select Market Fix and apply then reboot.
1.5 Downloading from Market Not working
Goto Downloads Press Menu Key and switch Settings to WiFi or Mobile network.
1.6 Searching not working
Simply enter search advanced settings and turn off searching within SMS (Mentioned on Original Post)
2. HARDWARE RELATED:​
2.1 SD-CARD Not working or other issues with Camera or Sensors
When flashing if you don't see the Cyanogen Logo after the Samsung one when turning the phone on to enter recovery (After flashing cm7-galaxys-initial-kernel.tar) , then STOP flashing process as you have done something wrong or are trying to install coming from a JVK rom. Downgrade to Froyo or if need be JM1 and start the process over.
Also, camera is not working properly (known bug) – poor saturation and multiple lines running through image.
2.2 External SD card not detected
If your external sd card is not detected even when the kernel had corrected the issue, you most likely has the 2.3.3 bootloaders. You may flash the bootloader (definitely not recommended) or you can restart using EZBase rom or follow galnet's guide in his site.
2.3 Auto rotation/accelerometer not working
If your auto rotation/acceleromter is not working (despite having it enabled in Settings > Common Tab > Display Settings > Auto-rotate screen) then hard reboot (completely switch off device, wait 10+ seconds, and then switch device back on)
2.4 High Battery Drain
Known CM7 bug that is not fixed yet.
2.5 Battery only reports ~96% on full charge
This is a function implemented on ALL 2.2.1+ ROMS (including MIUI, which is based off CM7 2.3.3) so that the battery of the devices do not overcharge. Samsung ROMS falsely report 100% charge, but in actual fact, it also charges to ~96% and that if you watch closely, after a few minutes, the battery will rapidly drop back down to ~96% and stablise.
http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
2.5 Battery has stopped charging
Battery is known to stop charging when it gets too hot. This is to protect the battery and phone from exploding.
2.6 Phone turns on when I insert charger
This is a known bug (or function LOLS) which is present in the Nexus S ROMS and because the SGS MIUI ROM is a derived from the MIUI Nexus S ROM, SGS will also have this bug/function.
3. ETC:​
3.1 Where do I start?
Have a look at Galnet's MIUI Guide and note that you can start from ANY Froyo ROM (Stock and Custom) as long as your device has a Froyo Bootloader.
3.2 Flashing from JVK to MIUI
You must first downgrade the firmware to Froyo (which MUST include a Froyo Bootloader - check in zip via WinRar for boot.bin and sbl.bin) It has been found that the Gingerbread bootloader has caused major problems. It is recommended that you downgrade to Eclair JM1 then upgrade to JS5 (files are avaliable on Galnet's Website) and then follow Galnet's MIUI guide to flash MIUI.
Note that flashing/using any Gingerbread modems such as JVK will not cause problems, it is only the Gingerbread bootloader that is causing problems.
3.3 IMEI SCREWED!
Flash back to JS5 or another Official Rom and it will be restored!
3.4 FLASH AT OWN RISK
If you don't have a clue what you are doing or ODIN is a strange word, then please go over to Galnet's MIUI guide and read it before flashing, make sure you understand the risks and note that the developers are not always available to answer your questions instantly!
3.5 Applying a downloaded theme:
Move theme file anywhere onto your phone's memory (should have a .mtz file extension) > Open Theme Manager > Press on Capacitive Menu Button > Import Theme > Locate and Select the theme you added onto your phone's memory
Alternatively, you can directly move the theme (.mtz) file to sdcard/MIUI/theme/
3.6 (SOME) Themes not changing lockscreen
Check that the theme supports MIUI Gingerbread 1.4.8, older MIUI FROYO themes will not work.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
COPY AND PASTE:
(Insert FAQ here)
In the future, please refer to the MIUI FAQ Section[/URL ] before posting.

TIPS AND TRICKS
1. Download seems to get stuck forever. Download only works with wifi.
To fix, open up the Download App, click menu, select toggle 3g /wif. This normally will work. If it doesn't work, try for 2 or 3 times. Remember to cancel the download from the app. If it still doesn't work, reboot and try again. The best fix will be to boot into recovery, and do a wipe / factory reset and reboot. Before downloading, go to the download app to activate the 3g / wifi toggle.
2. Speaker phone is too loud (Thanks to Ekin)
Goto DSPManager > Phone Speaker > Enable equalizer
Then drag all the zeros on the graph down to about -3.0 but keep them all roughly the same. This will lower the volume on the loudspeaker for everything, fixing your problem. When you want to watch a movie and want to make it louder, go back here and just swipe it to disable. So its only one swipe to get it on/off. In order to keep the settings, you need to hit the Back button for it to register correctly.
Raising it/enabling bass boost seems to kill the quality a little bit, so I recommend not to do those.
I have a Nokia headset that I use, and its a little quite so I do the same trick (except I raise the "headset" equalizer) and this nifty trick is basically the same as the voodoo sound hack which takes proper use of the high-quality sound card inside the Hummingbird.
3. Choppy / Laggy graphics and interface (Thanks to whitesox311)
In the settings under battery options....it has " power saving mode" on automatically....if you disable this it gets rid of all the issues. Also, if you leave "Hi-res graphics" turned off in the launcher settings it vastly improves smoothness.
4a. How to get Swype to work (Thanks to Prototype159)
Download the swype installer.
Follow the directions all the way til the end.
Hit the finish button. Reboot.
If it didn't work, clear data and uninstall swype and the swype installer. Try again.
If you change the kernel, you will have to redo it again.
4b. How to get Swype to work (Thanks to agha123)
Follow the instructions to the tee on this web page ,
http://www.androidpeek.com/2010/12/get-swype-keyboard-working-on-miui-rom/
5. Screenshot (Thanks to hacksome)
Pressing Menu + Volume DOWN -->> Screenshot!

reserved
Sent from my GT-I9000

Hmm...good timing. I have some questions on my own.
I have been reading the installation procedures for a while. This particular line intrigues me
6: Pull out the USB cable and start (in download mode) with 3-button-combo in recovery mode (waiting until samsung logo appears)
How do I start recovery mode within download mode? I don't want to take any risks but wish to understand fully on what I will be doing before I commit.
Another question: Assuming that later I decided MIUI is too buggy, is there a backtrack procedure? Usually I will just reflash with ODIN to a stock rom(eg: JPY) to rid of all the lagfixes etc then to maybe Doc's rom for example.
Since this is a ASOP sort of ROM in GB. how do I go about it?
Noob questions I know but I rather be noob now then to beg for help around later

i dont have the maps application in my rom. After installation i dont see any maps app.

mystifiyer said:
Hmm...good timing. I have some questions on my own.
I have been reading the installation procedures for a while. This particular line intrigues me
6: Pull out the USB cable and start (in download mode) with 3-button-combo in recovery mode (waiting until samsung logo appears)
How do I start recovery mode within download mode? I don't want to take any risks but wish to understand fully on what I will be doing before I commit.
Another question: Assuming that later I decided MIUI is too buggy, is there a backtrack procedure? Usually I will just reflash with ODIN to a stock rom(eg: JPY) to rid of all the lagfixes etc then to maybe Doc's rom for example.
Since this is a ASOP sort of ROM in GB. how do I go about it?
Noob questions I know but I rather be noob now then to beg for help around later
Click to expand...
Click to collapse
It means exactly that. In download mode hold the 3 buttons (vol up, power & home) and release all keys when the Samsung logo appears. After about 5 seconds you will see recovery mode.
You can easily backtrack. In Odin use a fw that has all three files and tick repartition. I use jpu.
Sent from my GT-I9000 using XDA App

sxi200 said:
It means exactly that. In download mode hold the 3 buttons (vol up, power & home) and release all keys when the Samsung logo appears. After about 5 seconds you will see recovery mode.
You can easily backtrack. In Odin use a fw that has all three files and tick repartition. I use jpu.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
@mystifyer,
this is the same answer i will give. it is correct.
thanks sxi200.
Sent from my GT-I9000

vivekrk44 said:
i dont have the maps application in my rom. After installation i dont see any maps app.
Click to expand...
Click to collapse
maps can be downloaded from market.
Sent from my GT-I9000

This is new! I didn't know we can do that!
Shall give it a try this Friday Thanks for the explanation
Another question:
I understand also that ASOP roms don't have the very good codec support. Fair enough. Some threads I seen has mentioned of Moboplayer. I gave it a try. Works well enough in hardware acceleration mode but software decoding mode looks really slow.
Now my question is: Does software decoding mode works better in ASOP roms than say a generic lagfixed rom?

vivekrk44 said:
i dont have the maps application in my rom. After installation i dont see any maps app.
Click to expand...
Click to collapse
Download from Market.

mystifiyer said:
This is new! I didn't know we can do that!
Shall give it a try this Friday Thanks for the explanation
Another question:
I understand also that ASOP roms don't have the very good codec support. Fair enough. Some threads I seen has mentioned of Moboplayer. I gave it a try. Works well enough in hardware acceleration mode but software decoding mode looks really slow.
Now my question is: Does software decoding mode works better in ASOP roms than say a generic lagfixed rom?
Click to expand...
Click to collapse
wow, this one i dont really know. i am not sure if there were bemchmarks being made on that or not.
not a good comparison, but still say this. i ran quadrant for this two roms, and the framerate for samsung is better in 3D, and not much different on 2D.
dont forget samsung did not release the sourcecode, and cyanogenmod do it from scratch. but nevertheless it is still good in aosp.
Sent from my GT-I9000

Prasad007 said:
Download from Market.
Click to expand...
Click to collapse
tks buddy, glad you are here too.
Sent from my GT-I9000

g00ndu said:
tks buddy, glad you are here too.
Sent from my GT-I9000
Click to expand...
Click to collapse
Likewise.

No problem. I will know it after I try this Friday. I can share it then, provided nothing goes wrong.
Quite a fair bit of adventurous users tend to dive in straight without checking the cons of a ASOP rom, only to regret and then flash back. I don't really want to fall in this category.
Multimedia is big for me as I watch alot of animes. This codec problem might give me abit of a headache with the software decoding and probably missing code support.
I think I asked enough. Shall camp here and explore other users' problems.
Thanks for the feedback. Appreciate it.

Did the galnet's instructions and the result is the same. so tired by the way

dr.bahaeddin said:
Did the galnet's instructions and the result is the same. so tired by the way
Click to expand...
Click to collapse
I've PM'ed you, I advise you do a 3 file install of JP2 via ODIN to make sure all your files on the phone aren't corrupted.
Once you have got Froyo installed then please get back to us. (Boot into Froyo and make sure it's all working correctly)

galnet said:
I've PM'ed you, I advise you do a 3 file install of JP2 via ODIN to make sure all your files on the phone aren't corrupted.
Once you have got Froyo installed then please get back to us. (Boot into Froyo and make sure it's all working correctly)
Click to expand...
Click to collapse
got your message man downloading right now. maybe my internal sd makes files corrupted?

dr.bahaeddin said:
got your message man downloading right now. maybe my internal sd makes files corrupted?
Click to expand...
Click to collapse
Pass mate, but if you have a felling this could be the case then format the internal sd, after installing Froyo and then copy the required MIUI files back across to your internal sd and then try to proceed in flashing MIUI again.

galnet said:
Pass mate, but if you have a felling this could be the case then format the internal sd, after installing Froyo and then copy the required MIUI files back across to your internal sd and then try to proceed in flashing MIUI again.
Click to expand...
Click to collapse
ok now i'm on JP2 everything works fine.

[ATTN] - 3991 and 4349+ VIEWSONIC-RECALLED BOOTLOADER INFO here - UPD 5/8/11

Updated 05/08/11
ATTENTION - IF YOU ARE ON STOCK 4349+ or any MOD BASED OFF 4349+ USING THE NEW RECALLED BOOTLOADER! READ PLEASE!
Starting with the most recent but recalled update to Tap N Tap Viewsonic has introduced a new Bootloader being called the 1.2 bootloader. This bootloader is not compatible with mods or Roms based off of the Viewsonic Current Bootloader being called the 1.1 bootloader! This bootloader provides absolutely no known advantage other than being able to boot any new STOCK kernels. If you would like to use any of our stable ROM's (i.e. Vegan 5.1.1, Vegan GingerEdition and currently CM7) using Viewsonics currently supported and shipping bootloader (1.1) you must Downgrade your bootloader and TNT Version before you flash a new kernel or a new ROM.
Please download the following downgrade update.zip and place it on your sdcard renaming it to "update.zip".
http://www.gtabdevs.com/releases/4349_Downgrade.zip
Then power down your device. And power back up while holding the power button and vol + till your display says "recovery key detected" in the top left corner.
Using the volume keys to navigate up/down in the menu highlight "Apply Internal update.zip" if you copied the update.zip to the internal memory or "Apply External SDCard update.zip" if you happened to place it on an external SDCard and then inserted it before booting to recovery. Now select the menu choice using the menu key.
This process will take a few minutes. You will see a Box with an arrow and a progress bar while it applies the update.... when it is finished it will reboot to make the changes. Once the changes are complete your tablet will boot into Tap N Tap version 3588.
You are now free to follow all the tutorials about installing CWM and/or Kernels/Roms.
Thank you and good luck.
Be aware. I am not connected with Viewsonic in any way. I make no assertions as to the validity nor the safety of anything in this post. Do anything above at your risk.

That is a handy utility to have. Thanks!

How do we check if the bootloader is locked? I'm curious if the bootloader.bin in 3991 (which is based off the same branch) has this same issue.
Thanks!

Strange. One step forward and two steps back for Viewsonic. But, maybe, this means there is still some interest from Viewsonic for our tablet and chance for further development (maybe even Honeycomb).

roebeet said:
How do we check if the bootloader is locked? I'm curious if the bootloader.bin in 3991 (which is based off the same branch) has this same issue.
Thanks!
Click to expand...
Click to collapse
If it too will not boot any other kernel besides a stock kernel built specifically for their new bootloader. That bootloader.bin also appears to be locked.

gojimi said:
If it too will not boot any other kernel besides a stock kernel built specifically for their new bootloader. That bootloader.bin also appears to be locked.
Click to expand...
Click to collapse
Does that mean it's locked, or does that mean that we just don't have the new source code to build custom kernels? I just want to distiguish because, if it's the latter, we can just ask them to release that like they did the 1.1-based source. EDIT: Already tweeted them. I see "1.1" in the source that's there, and we know that this is "1.2", so maybe there's new source code to be requested? Not sure.
I know that we can check for a locked bootloader with something like fastboot, but I don't think that works here. That's why I was asking.
Thanks again!

gojimi said:
If it too will not boot any other kernel besides a stock kernel built specifically for their new bootloader. That bootloader.bin also appears to be locked.
Click to expand...
Click to collapse
what could the thinking possibly be to locking the bootloader on a product like ours?
I'm seriously asking, besides being dicks, what would the reasoning be?

roebeet said:
Does that mean it's locked, or does that mean that we just don't have the new source code to build custom kernels? I just want to distiguish because, if it's the latter, we can just ask them to release that like they did the 1.1-based source.
I know that we can check for a locked bootloader with something like fastboot, but I don't think that works here. That's why I was asking.
Thanks again!
Click to expand...
Click to collapse
By all means ask for their new source... though I do not believe at this point they are required to give... maybe they are. So for the purposes of everyone else's understanding this is a LOCKED bootloader in the sense that we are LOCKED to their kernel...... nothing ever stays locked forever.... this is not however LOCKED in the terms that a select few who already know what's going on with this bootloader typically use the term LOCKED. Take it as you will.

snapz54 said:
what could the thinking possibly be to locking the bootloader on a product like ours?
I'm seriously asking, besides being dicks, what would the reasoning be?
Click to expand...
Click to collapse
To be honest they are probably tired of all the people calling viewsonic support with issues that are not on OFFICIAL viewsonic software... most companies try to do something to deter this activity in some regards.

Does nv flash still works to downgrade everything?

gojimi said:
To be honest they are probably tired of all the people calling viewsonic support with issues that are not on OFFICIAL viewsonic software... most companies try to do something to deter this activity in some regards.
Click to expand...
Click to collapse
I understand this for "most companies" but Viewsonic is the company that openly linked on their product page that XDA is the place to be if you need support or any real use from your gtab.
We had to fight them to finally stop doing that. It doesn't really add up.
The only thing this does if it works is effectively pull the plug on the life support that was pumping any further life into the tablet.
We still have great "legacy" roms and infrastructure that make the tablet great. but moving forward all this does is concentrate our efforts towards them. releasing a workable open solution keeps us busy tinkering with it for months. Locking things down only sends us back to twitter and the like but now we have more members thanks to the new OD, TD, and amazon users.

I thought VS said they were going to work with the devs. Didnt they contact you guys? I thought they would of asked or told you guys what the best way for them to go would be. Did this never happen?

Pazzu510 said:
Does nv flash still works to downgrade everything?
Click to expand...
Click to collapse
Yes, maybe. I had to NVflash mine because I accidentally flashed CWM over 4349 while i was playing in the 4349 recovery screen. The NVflash process worked, but for some reason my touch screen was borked (no touches were registered). Couldn't do anything. In the past a couple restarts with calibration.ini on the external SD would clear that for me, but didn't this time. I ended up doing NVflash with CWM as part9.img and then repartitioned with CMW and NVflashed again with stock recovery part9.img. Screen was still borked but cleared up with a couple restarts with calibration.ini on an external SD. So the answer is yes you can, but it may not be as smooth as you are used to. Of course it may work fine for you.
Matt

jasco13 said:
Yes, maybe. I had to NVflash mine because I accidentally flashed CWM over 4349 while i was playing in the 4349 recovery screen. The NVflash process worked, but for some reason my touch screen was borked (no touches were registered). Couldn't do anything. In the past a couple restarts with calibration.ini on the external SD would clear that for me, but didn't this time. I ended up doing NVflash with CWM as part9.img and then repartitioned with CMW and NVflashed again with stock recovery part9.img. Screen was still borked but cleared up with a couple restarts with calibration.ini on an external SD. So the answer is yes you can, but it may not be as smooth as you are used to. Of course it may work fine for you.
Matt
Click to expand...
Click to collapse
I've nvflashed back to 1105 at least a dozen times since last night (was doing upgrade / downgrade scenarios). So far, so good.

The bootloader is provided by viewsonic I think, it may be the key for some chipset feature, some other brand of tablet like the adam already has the same exact one
it's probably not locked but only doing something different like you said!

if I had to guess, they didn't lock it to be pricks...odds are it is locked to prevent people from flashing our current kernels to this to avoid messing things up...
so here's prolly how we'll be structuring our ROMs/Kernels now...1.1-based Froyo ROM; 1.2-based Froyo ROM; 1.1-based Froyo Kernel; 1.2-based Froyo Kernel and so on for GB if we're lucky HC in the future.
It's going to be a pain in the butt in the short-term, but long-term it'll only benefit current and future gTab owners as a whole if we stick to the 1.2 path alongside the vendor. This will keep confusion to a minimum, features to a maximum, and upgradability easy.
Thanks to all devs for their future support even through some of the PITA times

i have no options to choose between, aka no menu when i do all that, it just goes to a box picture and then reboots and loads normally.

Edited...You can't fix stupid

iamnottypingthis said:
i have no options to choose between, aka no menu when i do all that, it just goes to a box picture and then reboots and loads normally.
Click to expand...
Click to collapse
There is no menu. It takes you back to 3588 and the ability to flash all current roms.

So this "rollback" is jsut a stock 3588 image, or is it something different?

Is this it, is this the root for retail we have been waiting for, maybe?

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.

How to Convert N986U1 Android 11One UI 3.0 Beta to Official Carrier N986U Android 11 (ATT,TMB,SPR,VZW,USC,etc.)

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.