I have search these forums for an answer to this, but cannot find a answer to this exqact question and don't want to start installing ROMs unless I really have to.
I rooted my UK uynbranded Tab using Z4 root a while back. I saw gingerbread is now available in my region so tried to update, but Kies is telling me an update is available but refusing to update my tab. I unrooted the Tab using Z4 root and tried again, but still without success.
Currently my version reports:2.6.32.9 [email protected] #1, build FROYO.XWJJ7, baseband P1000XXJK5
Do I really need to reflash to a stock ROM?
If I must, could someone please recommend a tutorial to help me, I see several guides but no idea which is the right one for my circumstances.
Thanks
Gary
Okay, I am new to this locked bootloader and safestrap stuff so please bare with me.
I am on an official 4.4.2 NC2 rooted Att Note 3.
The question is: Can I install the roms that are based off the leaked firmware? It seems pretty stupid but ooooh well.
I assume I can since the leaked update is still "signed" or whatever it is called.
kenscivic said:
Okay, I am new to this locked bootloader and safestrap stuff so please bare with me.
I am on an official 4.4.2 NC2 rooted Att Note 3.
The question is: Can I install the roms that are based off the leaked firmware? It seems pretty stupid but ooooh well.
I assume I can since the leaked update is still "signed" or whatever it is called.
Click to expand...
Click to collapse
Hey,
If you heard of any success stories why not? The only thing, if someone unlocked the bootloader tomorrow (Which i don't see happening anytime soon), you might be locked because with every firmware, I feel they try to lock down the device more, so if someone is close, you might be stuck!
Since you're on NC2, if it is based on the NC2 you should be fine, just make sure you backed up everything. Because I had an issue with restoring to stock NC2 read thread below.
http://forum.xda-developers.com/note-3-att/help/nc2-odin-firmware-available-t2800677/post53806285
You can always make a slot and install the rom without touching the stock. Safestrap should not modify your modem and firmware "Odin does".
matteosaeed said:
Hey,
If you heard of any success stories why not? The only thing, if someone unlocked the bootloader tomorrow (Which i don't see happening anytime soon), you might be locked because with every firmware, I feel they try to lock down the device more, so if someone is close, you might be stuck!
Since you're on NC2, if it is based on the NC2 you should be fine, just make sure you backed up everything. Because I had an issue with restoring to stock NC2 read thread below.
http://forum.xda-developers.com/note-3-att/help/nc2-odin-firmware-available-t2800677/post53806285
You can always make a slot and install the rom without touching the stock. Safestrap should not modify your modem and firmware "Odin does".
Click to expand...
Click to collapse
I have not read any stories about it. Thank you for the quick reply! It is greatly appreciated
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 Just wanted some advice. Im on 6.01 Overdrive rooted but would like to go back to stock as I feel I'm not using any rooted featured and also I'm getting problems with Oculus etc.
My Question is what's the best Firmware to flash in Odin that if I decide to go rooted again it won't block me or upgrade my bootloader. I'm on Baseband PE3 at present.
Do I need to wipe anything? Or is an Odin Flash enough. Thanks
I use epg2. You can flash the dev base for that. I pulled the boot.img from it and flashed over to remove root. The 910t had guides to get you back to lp from anything before pj2. Haven't bothered upgrading past that point.
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?