Related
Alright, so I updated my phone when the first OTA update was released, and it installed successfully no problems. After this I got into rooting my phone so that I could get rid of the AT&T crapware, use launcher pro, and enable sideloading for apps. I thought that I would check for another update since rumors were swirling about 2.2, and to my surprise it detected a package to download. I was able to download it, however it wouldn't finish installing on the phone and said that it could not be installed. Thinking that this was due to my root, I used Odin to flash back to stock and retry the install, and it still didn't work. So, after that I reverted back to the root, and decided to go and check the firmware and baseband version What is confusing to me is that for "firmware version" it says that I have "2.1-update1", but my baseband version still says "1897UCJF6" instead of "JH7". Now when I try to install whatever supposed update that is available, it downloads and then gets stuck at 50% in the progress bar when trying to install. So I guess my question is, should I be worried about this? Is this the current version, and does it just say "JF6" because of my root? Also, will I need to unroot if I want to install the 2.2 update whenever it comes out?
I apologize for the novel, I'm just trying to be as informative about my situation as possible. Any help with this would be greatly appreciated.
Thanks
JF6 is the stock firmware and JH7 was the ota update.
Sent from my Captivate
Alright thanks, but why is my phone still displaying "2.1-update1" if I still have the stock firmware? Is it because of the root that it is displaying JF6 instead of JH7?
goosefraba91 said:
Alright thanks, but why is my phone still displaying "2.1-update1" if I still have the stock firmware? Is it because of the root that it is displaying JF6 instead of JH7?
Click to expand...
Click to collapse
JH7 was also considered 2.1-update1
there is not an official 2.2 yet
Okay well thanks, I think I'm about to just flash to a 2.2 ROM, I'm tired of waiting on samsung for 2.2
i need help with the rooting of my phone
bosoxtm said:
i need help with the rooting of my phone
Click to expand...
Click to collapse
View this topic:
http://forum.xda-developers.com/showthread.php?t=739304
I have gone back and forth between 5.1.1, 5.0.1, and 4.4.4 roms by using odin to flash the COG2, COD6, or ANK4 firmware first, then using odin to flash autoroot and TWRP. Then use TWRP to flash the desired rom. I have no problem going from lollipop to kitkat and back. I have used the COG2 firmware for all the 5.1.1 roms, like Texxodus, Resurrection, Slim, CM12, etc. I have used COD6 for 5.0.1 like Alliance, I have used ANK4 for Firekat. I have never had a problem reverting between any of them.
Why is DOK2 different? Does it trip some kind of hardware switch, like knox? If I was on it and used odin to flash, say, the kitkat firmware, what happens? Does odin no longer work when you're on DOK? Does it crash? Does the flash appear to work but it stays on DOK? Does it flash the firmware but bootloop? Does it brick the phone? I always thought that odin flashed firmware to the lowest level so that as long as you could connect the phone to a PC and had a good firmware load, you could restore it.
I am sorry to belabor this, but nothing I have read has explained this. All you get is that once you are on DOK2, you can't go back, but no one seems to know why and no one appears to have tried using Odin to flash a previous firmware and can answer the questions in the previous paragraph.
phoneturf said:
I have gone back and forth between 5.1.1, 5.0.1, and 4.4.4 roms by using odin to flash the COG2, COD6, or ANK4 firmware first, then using odin to flash autoroot and TWRP. Then use TWRP to flash the desired rom. I have no problem going from lollipop to kitkat and back. I have used the COG2 firmware for all the 5.1.1 roms, like Texxodus, Resurrection, Slim, CM12, etc. I have used COD6 for 5.0.1 like Alliance, I have used ANK4 for Firekat. I have never had a problem reverting between any of them.
Why is DOK2 different? Does it trip some kind of hardware switch, like knox? If I was on it and used odin to flash, say, the kitkat firmware, what happens? Does odin no longer work when you're on DOK? Does it crash? Does the flash appear to work but it stays on DOK? Does it flash the firmware but bootloop? Does it brick the phone? I always thought that odin flashed firmware to the lowest level so that as long as you could connect the phone to a PC and had a good firmware load, you could restore it.
I am sorry to belabor this, but nothing I have read has explained this. All you get is that once you are on DOK2, you can't go back, but no one seems to know why and no one appears to have tried using Odin to flash a previous firmware and can answer the questions in the previous paragraph.
Click to expand...
Click to collapse
Try it and report back. The bootloader can never be downgraded once it has been updated but I have heard of people odining back to kitkat from 5.1.1 and them getting it to work. Not sure how it was done but they did it.
DeeXii said:
Try it and report back. The bootloader can never be downgraded once it has been updated but I have heard of people odining back to kitkat from 5.1.1 and them getting it to work. Not sure how it was done but they did it.
Click to expand...
Click to collapse
You say the bootloader can never be downgraded once it has been updated. Okay, that's what everyone says. But is it true? No one seems to know. And if it is true, why? I find this very odd that no one knows.
My current favorite rom is Alliance since for me it has the best battery life and the least lag of the roms I have tried, so I don't want to take a chance that I can no longer run it if I flash DOK2 and don't like it.
phoneturf said:
You say the bootloader can never be downgraded once it has been updated. Okay, that's what everyone says. But is it true? No one seems to know. And if it is true, why? I find this very odd that no one knows.
My current favorite rom is Alliance since for me it has the best battery life and the least lag of the roms I have tried, so I don't want to take a chance that I can no longer run it if I flash DOK2 and don't like it.
Click to expand...
Click to collapse
go here for your answers
http://forum.xda-developers.com/not...-solution-to-emmcread-write-problems-t3281179
My understanding is that it's part of a new "security policy", I believe implemented by Tmo. My source of this info isn't related directly to my Note 4, but last month I Jumped my tablet to a new Samsung Galaxy Tab S2 that came loaded with 5.1.1. The day after picking it up I got a notification for a firmware update, still 5.1.1 (small size), screenshot of the "release notes" attached below. I didn't take the update and froze updates in TiBu. There's not a whole lot of development for that device yet and I think that I would have lost root if I had taken it.
I'm all for "security", but disabling users' ability to downgrade firmware hardly seems like much of a contribution to that end. IMO this is a disappointing development, and has much greater potential to affect "power users" vs. "regular users" as I doubt that a regular user downgrading the firmware on their device to their determent is something that even happens... ever.
jazzmachine said:
My understanding is that it's part of a new "security policy", I believe implemented by Tmo. My source of this info isn't related directly to my Note 4, but last month I Jumped my tablet to a new Samsung Galaxy Tab S2 that came loaded with 5.1.1. The day after picking it up I got a notification for a firmware update, still 5.1.1 (small size), screenshot of the "release notes" attached below. I didn't take the update and froze updates in TiBu. There's not a whole lot of development for that device yet and I think that I would have lost root if I had taken it.
I'm all for "security", but disabling users' ability to downgrade firmware hardly seems like much of a contribution to that end. IMO this is a disappointing development, and has much greater potential to affect "power users" vs. "regular users" as I doubt that a regular user downgrading the firmware on their device to their determent is something that even happens... ever.
Click to expand...
Click to collapse
Canadian note 4 dont seem to have the security lock on them since i rolled back to 5.0.1 bootloader but yes it wont let u roll back to any other 5.1.1 bootloader
U can try to download canadian BOE2 firmware and flash that since tmobile nd canada r pretty mch the same
This can be very dangerous so be cautious
phoneturf said:
I have gone back and forth between 5.1.1, 5.0.1, and 4.4.4 roms by using odin to flash the COG2, COD6, or ANK4 firmware first, then using odin to flash autoroot and TWRP. Then use TWRP to flash the desired rom. I have no problem going from lollipop to kitkat and back. I have used the COG2 firmware for all the 5.1.1 roms, like Texxodus, Resurrection, Slim, CM12, etc. I have used COD6 for 5.0.1 like Alliance, I have used ANK4 for Firekat. I have never had a problem reverting between any of them.
Why is DOK2 different? Does it trip some kind of hardware switch, like knox? If I was on it and used odin to flash, say, the kitkat firmware, what happens? Does odin no longer work when you're on DOK? Does it crash? Does the flash appear to work but it stays on DOK? Does it flash the firmware but bootloop? Does it brick the phone? I always thought that odin flashed firmware to the lowest level so that as long as you could connect the phone to a PC and had a good firmware load, you could restore it.
I am sorry to belabor this, but nothing I have read has explained this. All you get is that once you are on DOK2, you can't go back, but no one seems to know why and no one appears to have tried using Odin to flash a previous firmware and can answer the questions in the previous paragraph.
Click to expand...
Click to collapse
I have been try a lot of time for use odin to flash cog2 or cod6 from dok2. And it allway fail in odin. And you will receive a notice in the download mode screen like that o"Odin fai, binary =2>1". So you can't flash succesfull in odin.
And evething can't change. I have read 5.1.1 plicy and it also said that we can't downgrade from t mobile phone.lol
Perhaps development can recompile bootloader without tmo security and use Canadian firm to patch.
I just upgrade from COG2 to DOK2. Is there any difference? Which is better?
I have the N910T.
Dok2 has been reported to have improved performance and battery life than cog2 but cannot be downgraded.
Bruce lee roy said:
Dok2 has been reported to have improved performance and battery life than cog2 but cannot be downgraded.
Click to expand...
Click to collapse
I see. My cook ROM say use DOK2. I didnt know about the downgrade. I guess its ok and thanks for the info.
Hi Everyone,
I am kind of lost in the upgrade process.
6 months ago, my Samsung Note 3 (USA AT&T) phone was working perfectly fine, but just with OLD firmware. ,then due to urge on upgrading, i searched so many sites and found a link somewhere on droidviews.com (as my firmware was NJ1 or something, website said i need to upgrade to NC2, and then to OC1), this process messed up my phone call receiving & making capabilities.
Most of the time callers see me unreachable and I am unable to call them as i get "emergency calls only"....I still don't have a way out from this issue. Some places I read i need to install right CSC / modem etc, I even tried this thread by reflashing using ODIN & N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar. Even after this, i still have calls related issues same as above.
Can someone guide me to right direct (or) did i totally messed up with this? BTW, i am now in INDIA, using Airtel services...
I believe nj1 firmware is newer than nc2.
The Odin files came from here: https://forum.xda-developers.com/note-3-att/general/100-stock-lollipop-5-0-n900aucueoc1-t3069609 ?
audit13 said:
I believe nj1 firmware is newer than nc2.
The Odin files came from here: https://forum.xda-developers.com/note-3-att/general/100-stock-lollipop-5-0-n900aucueoc1-t3069609 ?
Click to expand...
Click to collapse
Thanks. I tried flashing to OC1, still same problem. my calls are mostly not working. Is there a way i can go back to original 4.3 stock rom that came with Note3 AT&T? or is there a way i can get current AT&T rom (latest) to try with?
Good part is, i can go between 4.4.3 and 5.0 as i have original stock roms downloaded. But bad part is, my calls still failing...
appreciate any clue/help.
Where did you get the stock ROM? AT&T never released full firmware for the 900a.
There is no way to go back fully to 4.3 since the phone bootloader can be downgraded to 4.3.
audit13 said:
Where did you get the stock ROM? AT&T never released full firmware for the 900a.
There is no way to go back fully to 4.3 since the phone bootloader can be downgraded to 4.3.
Click to expand...
Click to collapse
Hi, i downloaded NC2 & OC1 stock firmwares from XDA only. they are loading up fine (using ODIN). But my calling problem remains same.
So, Yesterday, i tried rooting the phone and installed AllianceROM. then i went into series of issues like "unfortunately NFC has stopped", "unfortunately settings has stopped" etc... then followed the instruction to wipe/factory reset, 3 to 4 times and disabled NFC services etc. As of now, phone works fine, but still need to check the calling function for a week...
thanks for your time.
audit13 said:
Where did you get the stock ROM? AT&T never released full firmware for the 900a.
There is no way to go back fully to 4.3 since the phone bootloader can be downgraded to 4.3.
Click to expand...
Click to collapse
Are we SOL with 900a? I was in the wrong forum earlier and was ready to use update to 7...until I realized it wasn't for me.
Dying on Lollipop (where I landed after the 7 fallout)
I re-read my post and noticed that I made an error: the bootloader on an n900a CANNOT be downgraded.
You cannot flash any ROM to the phone using TWRP, you must use flashfire. Only ROMs based on the stock Samsung ROM can be flashed to the n900a.
audit13 said:
I re-read my post and noticed that I made an error: the bootloader on an n900a CANNOT be downgraded.
You cannot flash any ROM to the phone using TWRP, you must use flashfire. Only ROMs based on the stock Samsung ROM can be flashed to the n900a.
Click to expand...
Click to collapse
We can flash roms using safestrap and flashfire
So I had a botched situation caused by me when flashing a custom Rom (Rom/instructions is great, I went off the reservation myself) and had a soft brick.
I had decided at that point to just revert back to stock and not play around until things stabilize with Eng more. However, I couldn't.
The last stock referenced topic is with an outdated firmware and being 950U1 rather than just U. Downloading updated firmwares (or even attempting that one blindly) resulted in "Device dismatch".
I was then basically forced to (and successfully) go to SamPWN but that wasn't my initial intention.
Does anyone have an updated guide on how we can go back to stock without EngBoot, and specifically also states which CSC file is needed?
uaktags said:
So I had a botched situation caused by me when flashing a custom Rom (Rom/instructions is great, I went off the reservation myself) and had a soft brick.
I had decided at that point to just revert back to stock and not play around until things stabilize with Eng more. However, I couldn't.
The last stock referenced topic is with an outdated firmware and being 950U1 rather than just U. Downloading updated firmwares (or even attempting that one blindly) resulted in "Device dismatch".
I was then basically forced to (and successfully) go to SamPWN but that wasn't my initial intention.
Does anyone have an updated guide on how we can go back to stock without EngBoot, and specifically also states which CSC file is needed?
Click to expand...
Click to collapse
I may not have the answer, but check these guys and ask questions there, you should get an answer.
https://forum.xda-developers.com/tm.../guide-how-to-convert-to-100-stock-t-t3615957
And this link if from an unlocked S8 forum, but it has some info that you can find useful.
https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817
Charkatak said:
I may not have the answer, but check these guys and ask questions there, you should get an answer.
https://forum.xda-developers.com/tm.../guide-how-to-convert-to-100-stock-t-t3615957
And this link if from an unlocked S8 forum, but it has some info that you can find useful.
https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817
Click to expand...
Click to collapse
Download latest firmware for your phone, download Odin. Then flash them.
mweinbach said:
Download latest firmware for your phone, download Odin. Then flash them.
Click to expand...
Click to collapse
As I stated, I've attempted this and it failed. Plus it doesn't explain which file for the CSC had it worked anyhow. Downloading the latest results in the model dismatch. So can't JUST download and flash. But thanks for atleadt trying.
@charkata thanks for the links, I'll check them out and see how that goes.
uaktags said:
As I stated, I've attempted this and it failed. Plus it doesn't explain which file for the CSC had it worked anyhow. Downloading the latest results in the model dismatch. So can't JUST download and flash. But thanks for atleadt trying.
@charkata thanks for the links, I'll check them out and see how that goes.
Click to expand...
Click to collapse
Not the home version. And try using modified Odin.
mweinbach said:
Not the home version. And try using modified Odin.
Click to expand...
Click to collapse
I'll give it a go, going to try to do it in an hour or so and see if it'll work with the PrinceC version.
Is there any chance (in your or anyone elses opinion) that the mismatch could be the result of the custom rom being based on U1 rather than just U?
uaktags said:
I'll give it a go, going to try to do it in an hour or so and see if it'll work with the PrinceC version.
Is there any chance (in your or anyone elses opinion) that the mismatch could be the result of the custom rom being based on U1 rather than just U?
Click to expand...
Click to collapse
No, it can't modify hardware based model number.
uaktags said:
So I had a botched situation caused by me when flashing a custom Rom (Rom/instructions is great, I went off the reservation myself) and had a soft brick.
I had decided at that point to just revert back to stock and not play around until things stabilize with Eng more. However, I couldn't.
The last stock referenced topic is with an outdated firmware and being 950U1 rather than just U. Downloading updated firmwares (or even attempting that one blindly) resulted in "Device dismatch".
I was then basically forced to (and successfully) go to SamPWN but that wasn't my initial intention.
Does anyone have an updated guide on how we can go back to stock without EngBoot, and specifically also states which CSC file is needed?
Click to expand...
Click to collapse
You should be able to just completely reflash the stock TMB firmware with the modded Odin without an issue...am I understanding correctly that this did not work? Download the Prince Comsey modded Odin. It has a .ini file that you need to open w/ a text editor like notepad++, and edit UMS=0 to UMS=1 -this allows you to also flash the userdata file included in the TMB firmware, along w/ the normal BL, AP, CP & CSC.
Make sure you downloaded the correct firmware for the S8 (G950U), not S8+ (G955U).
https://updato.com/firmware-archive-select-model?record=F9F75B5C6CF011E7963AFA163EE8F90B
Did this work? Can anyone confirm? If not, I'm going to try it this weekend and hopefully I'll remember to reply here with results.
Flashed at&t firmware with odin but can't update software past July 1st sec uodate.
Hey guys. I picked a note 9 Verizon unlocked version and was having issues using it on at&t, volte obv not working hd voice calls not working and various other signal issues. I decided to flash to the at&t firmware with odin to fix it. First thing I did was flash the unlocked firmware, factory reset, then flashed at&t firmware. Everything is working just like I bought the at&t note 9 but I'm stuck on July security patch and the update is not recognized. Is there anyway to fix this ? Thanks in advance!
What happens when you try to update; it downloads the update but failing to install due to an error (what's the error) or not finding the updates at all? If latter try with Samsung smart switch install both on the phone and computer
It doesn't find any update ota or on smartswitch. Not sure maybe just need to wait longer, unless someone else has some bright ideas lol
Clo292311 said:
It doesn't find any update ota or on smartswitch. Not sure maybe just need to wait longer, unless someone else has some bright ideas lol
Click to expand...
Click to collapse
What build number are you running? If you managed to get yourself stranded on a build not officially pushed by ATT, then you're stuck until you Odin to something else. Current ATT is ARI5.
I am on ARG6 build. Is there something you know of I can flash that would be better?
@CrazyApe18
Clo292311 said:
I am on ARG6 build. Is there something you know of I can flash that would be better?
Click to expand...
Click to collapse
I'm not sure there is a path using update zips to get you current. I just looked and I can't see a way to get current from there. Somewhere on here an ARI5 Odin image (with no HOME_CSC) has been posted. That would get you to current ATT software. Once there, you would get OTA updates. I'm not sure how you got off the update track.
Edit: Here's the link to the Odin image you'd want: https://drive.google.com/file/d/1bKlJ-2ikGRsOd3JkDIFvjHGJX6XnrtEH/view?usp=sharing - courtesy of @Venom0642
@CrazyApe18 thank you for that link. Do I need to find a HOME_CSC file to add into that to flash it correctly?
Clo292311 said:
@CrazyApe18 thank you for that link. Do I need to find a HOME_CSC file to add into that to flash it correctly?
Click to expand...
Click to collapse
No, you don't need one. However, without HOME_CSC (and there isn't one that I'm aware of), your device will factory reset when you Odin this build. So make a full Smart Switch backup before doing it.
Oh that's fine I full wipe after odin anyways usually. Thanks so much !!
If you don't have an ATnT sim installed, it wont give you updates.
CrazyApe18 said:
I'm not sure there is a path using update zips to get you current. I just looked and I can't see a way to get current from there. Somewhere on here an ARI5 Odin image (with no HOME_CSC) has been posted. That would get you to current ATT software. Once there, you would get OTA updates. I'm not sure how you got off the update track.
Edit: Here's the link to the Odin image you'd want: https://drive.google.com/file/d/1bKlJ-2ikGRsOd3JkDIFvjHGJX6XnrtEH/view?usp=sharing - courtesy of @Venom0642
Click to expand...
Click to collapse
hey @CrazyApe18, i have a note 9 att locked on build number N960USQS2CSGB. I'm having an issue finding a current pie version to flash with odin. Basically I removed a bunch of things with adb a while back and wanted to restore back to factory. I pushed adb uninstall to things like the att update software, if I'm not mistaken a factory reset wouldn't restore this. I'm wanting to flash and then update to the new android version. I was wondering if you could point me in the right direction. I downloaded your link just in case it could help me. I'm familiar with odin, just having a hard time finding the firmware and SAMMOBILE is very slow for non paying users. I appreciate any help you can give me.
just realized that the version in your link is pre Pie. any idea where i can get a fairly recent pie firmware?