Related
I tried to downgrade the ota 4.3 update, i didnt know you couldnt upgrade..
Now im stuck at the Firmware upgrade encountered an issue screen..
Kies 2 will start saying "connecting" but thats as far as it gets.. then Kies 3 says that the device thats plugged in isnt compatible with kies 3.
IDK what to do xD
Johnnysauur said:
I tried to downgrade the ota 4.3 update, i didnt know you couldnt upgrade..
Now im stuck at the Firmware upgrade encountered an issue screen..
Kies 2 will start saying "connecting" but thats as far as it gets.. then Kies 3 says that the device thats plugged in isnt compatible with kies 3.
IDK what to do xD
Click to expand...
Click to collapse
Place your cell in Download mode, then use Odin to insert the official android 4.3 package.
andyistic said:
Place your cell in Download mode, then use Odin to insert the official android 4.3 package.
Click to expand...
Click to collapse
You wouldn't happen to have a dl link for official would you?
Johnnysauur said:
You wouldn't happen to have a dl link for official would you?
Click to expand...
Click to collapse
Start up Kies (no cellphone connected), then go to Tools / Firmware Upgrade
It will ask you for the model number, so put that in.
Then it will ask you for either the serial number or MEID, so put that in, too.
Then it should download a big-ass android package (around 1.5 gigabytes).
After the package is decrypted, copy it from the temp directory to some safe place on your local hard drive.
Use Odin in Download Mode to install this package.
The package should end with .tar.md5
If you accepted the official OTA 4.3 update, and you tried to revert your bootloader back to before KNOX... you're lucky since that should have completely hard-bricked your phone. I think, given to your description and assuming you've got the KNOX bootloader now, your best bet would be to try to repair the install by doing what I think is referred to as a "dirty" flash... which basically means you don't format or wipe your data before you attempt another installation of the same version.
I don't know for sure though, so don't take my word without someone who knows more verifying or refuting this.
Good luck, I'll be interested in seeing what you wind up working out.
-Zen
FallenZen said:
If you accepted the official OTA 4.3 update, and you tried to revert your bootloader back to before KNOX... you're lucky since that should have completely hard-bricked your phone. I think, given to your description and assuming you've got the KNOX bootloader now, your best bet would be to try to repair the install by doing what I think is referred to as a "dirty" flash... which basically means you don't format or wipe your data before you attempt another installation of the same version.
I don't know for sure though, so don't take my word without someone who knows more verifying or refuting this.
Good luck, I'll be interested in seeing what you wind up working out.
-Zen
Click to expand...
Click to collapse
I downloaded the mk3 modem, and flashed it in odin, it fixed the softbrick. i rooted it with cf-auto and it went through no issue. disabled knox no problem, and now got cwm working.
Hey,
So I had a friend ask me to unlock her S3, no biggie, I did it with another one (That hadn't been updated and was running 4.1.1 or something)
Following instructions online, I tried to upload a .md5 file via Odin but had the wrong version of Odin, and it failed to load. Now my download screen is showing SW REV CHECK FAIL : Fused 1 > Binary 0
As well, turning the phone on only results in "There was a problem updating the Firmware. Please run recovery mode in Kies."
Which is all fine and dandy, except Kies doesn't connect to the phone. It freezes on "Connecting..." and does not go any further.
Any help? I found another thread about it and am trying to use philz through Odin 3.07 and then flash through an external HDD the CM11.
Do you remember what stock ROM was on the phone before you used Odin?
Does the download screen say anything about warranty bit?
audit13 said:
Do you remember what stock ROM was on the phone before you used Odin?
Does the download screen say anything about warranty bit?
Click to expand...
Click to collapse
No clue.
Says Warranty Bit : 0
This five minute thing is a tad annoying...
Would be good to note, it is still under Warranty, and samsung offered to have it sent and fixed, however the phone is kind of needed ASAP.
I'm pretty tech-saavy, but I use Apple products generally and this is a touch foreign to me.
Odin failed to write Philz, just says WriteFail
This leads me to believe that the phone has least a 4.3 loader on the phone; therefore, you cannot unlock the phone using the free method as there is no way to get the stock 4.1.1 modem on your phone.
Is it an i747 from ATT? If it is, there is no stock ROM that can be flashed in Odin to restore the phone as ATT never released a full firmware flash for 4.3 or 4.4.2.
Any warranty left on the phone?
audit13 said:
This leads me to believe that the phone has least a 4.3 loader on the phone; therefore, you cannot unlock the phone using the free method as there is no way to get the stock 4.1.1 modem on your phone.
Is it an i747 from ATT? If it is, there is no stock ROM that can be flashed in Odin to restore the phone as ATT never released a full firmware flash for 4.3 or 4.4.2.
Any warranty left on the phone?
Click to expand...
Click to collapse
She doesn't even care if it's unlocked anymore, as long as we can get it working again.
I'm in Canada, so I'm assuming it is AT&T.
I believe the old OS was Jellybean 4.3. There is warranty, however she doesn't want to wait the length needed for that.
Brad90 said:
She doesn't even care if it's unlocked anymore, as long as we can get it working again.
I'm in Canada, so I'm assuming it is AT&T.
I believe the old OS was Jellybean 4.3. There is warranty, however she doesn't want to wait the length needed for that.
Click to expand...
Click to collapse
Wait, you have an i747m or i747? Big difference as cross-flashing the bootloader could hard brick the phone.
audit13 said:
Wait, you have an i747m or i747? Big difference as cross-flashing the bootloader could hard brick the phone.
Click to expand...
Click to collapse
SGH-i747M
I don't like the sounds of Hard Brick...
Brad90 said:
SGH-i747M
I don't like the sounds of Hard Brick...
Click to expand...
Click to collapse
Are you sure? Is that what it says at the top of the download screen? If it does, this is easier to fix.
audit13 said:
are you sure? Is that what it says at the top of the download screen? If it does, this is easier to fix.
Click to expand...
Click to collapse
"odin mode"
product name : Sgh-i747m
You can download the full firmware for the phone from sammobile.com. Search for the sgh-i747. The search results should inlcude the 4.3 and 4.4.2 firmware for the i747m. Make sure you match the firmware with the carrier.
If the phone had the 4.4.2 ROM, you cannot flash the 4.3 ROM.
audit13 said:
You can download the full firmware for the phone from sammobile.com. Search for the sgh-i747. The search results should inlcude the 4.3 and 4.4.2 firmware for the i747m. Make sure you match the firmware with the carrier.
If the phone had the 4.4.2 ROM, you cannot flash the 4.3 ROM.
Click to expand...
Click to collapse
I'll assume there's no way to check, should I try one before the other? Will doing so screw it up further?
How much warranty is left on the phone? I'm asking because there are different ways to restore the phone.
audit13 said:
How much warranty is left on the phone? I'm asking because there are different ways to restore the phone.
Click to expand...
Click to collapse
I'm not overly sure when she purchased it.
Samsung support said the IMEI was still covered by Warranty and to just send it in, but if there's a way to do it today I would like to.
Well, to be as safe as possible, you could try flashing the 4.4.2 Kit Kat ROM from sammobile for her carrier. You may have to register to download the ROM.
Who is the carrier?
Koodoo is her carrier, i'm download both the 4.3 and 4.4.2 at the moment.
So try the 4.4.2 first?
If you go with the 4.4.2 and it flashes properly, you will not be able to go back to 4.3. I recommend using Odin 3.07.
If you try to flash 4.3 and it fails, this tells me you probably have the 4.4.2 bootloader and modem on the phone.
Whenever you flash a ROM, there is always the possibility that something will go wrong. Just be prepared to deal with any possible issues. Don't panic, we're here to help.
When using Odin, do not check anything except F.Reset Time. When you see the word Reset in the status windows, disconnect the USB cable, pull the battery, boot into recovery, wipe cache and data, reboot the phone.
audit13 said:
If you go with the 4.4.2 and it flashes properly, you will not be able to go back to 4.3. I recommend using Odin 3.07.
If you try to flash 4.3 and it fails, this tells me you probably have the 4.4.2 bootloader and modem on the phone.
Whenever you flash a ROM, there is always the possibility that something will go wrong. Just be prepared to deal with any possible issues. Don't panic, we're here to help.
When using Odin, do not check anything except F.Reset Time. When you see the word Reset in the status windows, disconnect the USB cable, pull the battery, boot into recovery, wipe cache and data, reboot the phone.
Click to expand...
Click to collapse
Okay. So going to test with 4.4.2 once it's done downloading.
I had Auto Reboot checked before. When I turn on the phone, I can either set it in Downloading... mode or the error screen, I have absolutely nothing else. Is that the recovery screen I should be using?
To use Odin, you must boot into download mode.
When the file downloads, open Odin, connect the phone in download mode, click on the PDA button, browse to the downloaded 4.4.2 file, select it, click start.
How long does it sit on ID:0/003> SetupConnection..
Before it says reset? I'm attempting this with 4.4.2 under PDA with only F. Reset Time checked.
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
GreatGrizzwald said:
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
Click to expand...
Click to collapse
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
http://www.sammobile.com/
absinthesummer said:
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
Thank you very much for the advice. I am downloading the firmware now. baseband version is showing i317ucama4. Right now the phone is not activated with AT&T, is there a way I could test if I will be able to get cellular data before going to AT&T and activating it?
Click to expand...
Click to collapse
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
absinthesummer said:
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Click to expand...
Click to collapse
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
1425
rangercaptain said:
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
Click to expand...
Click to collapse
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
GreatGrizzwald said:
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
Click to expand...
Click to collapse
It sounds like the phone was updated previously to either 4.3 or 4.4.2, which have Knox and that pesky counter. Technically you can't directly downgrade, so be sure you're downloading firmware that is 4.3 or higher. I didn't realize sammobile only went to MA4 for US AT&T. (In a pinch you can use Canadian firmware, but we have other links for stock firmware). Also, don't worry too much about Kies. It can be helpful, but honestly I could never get my note 2 recognized by kies either.
When I get back from taking my kids to school, I'll gather some links that will help you revive this phone Links below:
@GreatGrizzwald:
More recent links to stock firmware: STOCK PACKAGES TO MK6 This is LJ2 (4.1.2), MK6 (4.3) and up. He's got all the stock firmwares, available for flashing either in recovery on via odin. I've highlighted the one I would use in the attached screenshot (MK6- ODIN)
He also has a thread for NE5 (The latest firmware, 4.4.2) HERE
So if MK6 doesn't work, try NE5. One of those two has to work. You're dad already updated to either 4.3 or 4.4.2, I don't know which so start with 4.3 (MK6) and if it doesn't work try 4.4.2 (NE5)
On those two threads, he has a TON of links that will be helpful to you in getting back to stock also.
And here's a reference page with some useful links: One Stop Shop
This one is dedicated to downgrading back to LJ2 (4.1.2) from 4.3+, it MIGHT come in handy for you: Downgrade Instructions
If you have trouble with the stock firmware, you can also try Chainfire's CF Auto Root. It's stock firmware but it's rooted. Try the other firmwares by Zen Arcade first though CF AUTO ROOT
We'll get it going for you The stock firmware will re-flash the modem and all the configuration files so you're data should work again. Then you can do whatever you want, root, recovery, flash other stuff, or leave it stock. You got this
---------- Post added at 07:51 AM ---------- Previous post was at 07:09 AM ----------
GreatGrizzwald said:
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
Click to expand...
Click to collapse
Also you have to figure out if it's software or hardware. I'm inclined to believe it's software so I think if you get it back to stock you'll be good. If it was hardware, it wouldn't even recognize a sim being inserted (recently repaired an htc one mini with this problem, it needed a new Sim tray, thankfully it was only $20).
But it sounds more like a bad flash corrupted some of those important files and configurations controlling data connections, it's all good, if it's software it can definitely be fixed. If it were hardware it could still be fixed it would just be a bit more time consuming.
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Thank you for all this, I will start working with it today. You have been a huge help.
GreatGrizzwald said:
Thank you for all this, I will start working with it today. You have been a huge help.
Click to expand...
Click to collapse
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
1100
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
GreatGrizzwald said:
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
Click to expand...
Click to collapse
That is great news! I'm so glad it's working for you. Enjoy your (new-to-you) note 2 and keep those files on hand in case you need them in the future!
absinthesummer said:
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
Click to expand...
Click to collapse
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
GreatGrizzwald said:
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
Click to expand...
Click to collapse
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
absinthesummer said:
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
Click to expand...
Click to collapse
Awesome, that makes a lot more sense now. Thanks again.
Hey I forgot you don't have custom recovery. Anyway, I sent you PMs,and you can do a search of this very forum- use the search term "update" or "ota" and you will find a LOT of threads on boot failures after OTA. Most people got their phones back.
If you can't get into DL mode (Vol-, Home, Power), try getting into the stock recovery (Vol+, Home, Power) because you should/could be able to factory reset the device from there. Also hold the button combo longer than usual. If one recovery option (DL mode) isn't working, than theoretically the other should still be accessible, through which you can adb sideload to the device or try factory reset. I know it's frustrating, but you're not the first nor the last to have an OTA go wrong ;/ We'll get ya back up & running.
You're not the only one in trouble after that update: http://forum.xda-developers.com/galaxy-note-2-att/help/todays-update-soft-bricked-phone-t2939649
I know that a lot of people are gonna say to read several other similar threads, but having gone through all of that I still don't get it.
THE SITUATION:
My Samsung Galaxy Note 2 GT-n7100 is :
1) Stock Android 4.1.2 Rooted
2) Modified with Xposed
3) TWRP (Latest, updated regularly)
4) Never been updated ever. Like never ever.
THE A-HOLE PROBLEM:
I honestly never bothered to flash anything on my note 2, since I have all the stuffs working perfectly as it is. Until the god-damn son of a gun WIFI started acting like a sissy she-dog. The problem is that the WIFI keeps on disconnecting itself and reconnecting itself automatically, wierdly enough, only when an app tries to access it. I hope everyone can understand how horrible it is, especially when you are talking dirty to your girlfriend over a whatsapp call and it keeps dropping, just like my errection.
All jokes aside, this has been driving me mad. In-case you need the details, here is what I did to solve my annoying problem :
1) Factory reset.
2) Reboot.
3) Phone works fine. Wifi works fine. Does not disconnect or reconnect. Seems like problem solved.
Then, the camel-crap happens.
4) Open Google play store, it updates. Play services updated. Need it to access the google services.
5) Open any internet enabled app.
6) Wifi switches on/off automatcally.
7) I tear my gonads off.
Side-Note : I also turned off the wifi power saving mode using *#0011#. I also made all the necessary changes in the wifi settings menu.
THE QUESTION:
Since I have never updated, my bootloader, etc are still stock. I read a thread that if I dont update the bootloader, future flashing will not work. I have no earthly clue so as to what the heck am I supposed to do.
I need some simple directions, to the point if possible. I have taken a full nandroid backup, just to be safe.
I think only a CFW now can solve this weird problem of mine. So, any help will be appreciated.
Newer roms require up-to-date bootloaders and modems. The easiest way to update both would be to flash the latest stock ROM from sammobile.com in Odin. Make sure you back up your data before flashing.
audit13 said:
Newer roms require up-to-date bootloaders and modems. The easiest way to update both would be to flash the latest stock ROM from sammobile.com in Odin. Make sure you back up your data before flashing.
Click to expand...
Click to collapse
Okay. But, what about the filthy Knox ? Also, what about my root? Also, what about Knox ? Hmm, I wrote knox twice. Now, thrice.
Simply put, knox is poo. I dont want that. So, how do I get the latest knick-knacks without knox. Is it possible to flash the latest bootloader, modem etc.
Sorry for using "noobish". I hate that language too, but when it comes to 40k phones, I get a bit nervous. Hope you can help. Or someone else.
Regards,
TheBasterd.
If you flash the latest bootloader, you'll get Knox.
Personally, I have never found Knox to interfere with flashing custom ROMs.
audit13 said:
If you flash the latest bootloader, you'll get Knox.
Personally, I have never found Knox to interfere with flashing custom ROMs.
Click to expand...
Click to collapse
So, here is the thing. If I go here : http://forum.xda-developers.com/galaxy-note-2/development/rom-resurrection-remix-5-6-0-t3278709 and downloaded the ROM, did all the stuff the ROM maker says and flash it.
Without the latest bootloader and other poo, you are saying that my flash will be unsuccessful ?
That ROM will probably need an updated bootloader and modem to connect to a cell network, detect a sim, and wifi.
If you want to, you can flash the ROM and see what happens.
audit13 said:
That ROM will probably need an updated bootloader and modem to connect to a cell network, detect a sim, and wifi.
If you want to, you can flash the ROM and see what happens.
Click to expand...
Click to collapse
Hey audit, thanks for sticking around and helping me bro. I really appreciate that.
So, I took your advice and have put the ROM from Sammobile.com for the latest bootloader and the modem stuffs.
Hope that will work. Also, when I flash the ROm, wont I loose my root ?
Yes, you'll lose root but it doesn't matter if you don't intend to use a stock ROM.
audit13 said:
Yes, you'll lose root but it doesn't matter if you don't intend to use a stock ROM.
Click to expand...
Click to collapse
Allright ! That was easy. Done and done. Thanks audit. (Thanks hitted)
Now, I will ensure a painless future for all noobs like me by making a tutorial. This thread can be marked as fixed. Thanks audiot bro.
It's great that you resolved the issue.
We're all here to help and learn from each other.
Hi Guys,
When trying to downgrade/flash below firmware via Odin I'm getting error:
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 2, BINARY: 1
Or if BL disabled following some recommendations:
KERNEL REV. CHECK FAIL. DEVICE:2, BINARY:1
Current version: (got via OTA)
G960FXXU2BRG6
Service provider OXM_XEF_00_0025 ... XEF/XEF, XEO/DBT - but this has probably nothing to do with that.
Returning to:
DBT-G960FXXU1BRE5
History of the phone is that I've received it on Saturday (manufactured on May 21), dual SIM + SD Card was working, got notification about OTA, and did proceed (silly me), got message that "no downgrade" will be possible - thought that it is for normal user, not the one with Odin magic, though have a feeling it has something to do with that. It was unusual message though thought it is something new on S(, but not really blocking me to downgrade with Odin.
Is there any way to downgrade? I really need to do that as thanks to Samsung I cannot use dual SIM + SD Card, described here:
https://forum.xda-developers.com/ga...o-sim-card-t3822368/post77193881#post77193881
Thanks!
When trying to downgrade/flash below firmware via Odin I'm getting error:
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 2, BINARY: 1
same problem, my S9 Plus is AFG cant intall only can update with DBT file but his current AFG no
Make sure you're using ODIN 3.13.x
You cannot downgrade the bootloader you can only flash firmware with an equal or higher BL version
G960FXXU2BRG6 <<< BL version 2
Check in Download mode what version yours says
*Detection* said:
Make sure you're using ODIN 3.13.x
You cannot downgrade the bootloader you can only flash firmware with an equal or higher BL version
G960FXXU2BRG6 <<< BL version 2
Check in Download mode what version yours says
Click to expand...
Click to collapse
Many thanks, that makes sense. I do remember message prior OTA apply "you won't be able to downgrade" but thought it was meaning that normal user won't be able to downgrade unless Odin would be used. Tough luck.
The worst part is that this is the first "U2" version for S9, so there's no path for me.
One more question - when "BL" was deselected and I've left only AP, CP, CSC - it resulted in message:
KERNEL REV. CHECK FAIL. DEVICE:2, BINARY:1
It is still in effort to downgrade the rest outside of BL, but does it seem I'm stuck on this firmware as the lowest on my phone now?
On technical side, these are all partitions on internal SDcard/memory. Why would it not be possible to overwrite it? Is it re-partitioning thing or something else? I'm trying to understand from where the limitation comes.
p.s. did some reading on bootloader process of Samsung and whilst it is clever and nice for Common Criteria, it should be possible to unlock it as in the past (Superboot tool). The good bootloader lecture is here: https://www.sciencedirect.com/science/article/pii/S1742287618300409 (S7 based).
Have you tried the patched Odin 13.3.1
https://www.google.com.au/amp/s/for...id/software/patched-odin-3-13-1-t3762572/amp/
batfink1 said:
Have you tried the patched Odin 13.3.1
https://www.google.com.au/amp/s/for...id/software/patched-odin-3-13-1-t3762572/amp/
Click to expand...
Click to collapse
What are risks using that Odin version and pushing AP?
Should I try to push BL too?
Apologies if I'm overly cautious it is that I don't want to brick the phone.
Honestly, I'm a take your balls in your hand kind of guy.
I'm a computer technician and if I spent all my time wringing my hands being cautious I'd never get anything done.
It's pretty hard to HARD BRICK these phones as long as you don't go faffing around with the partitions option in Odin.
God I've brought mine to the brink of death and back again.
Just out of curiosity, do you have a way of taking a photo of your Odin/Download mode screen... I'll try to post mine.
I'm rooted and running a customised stock based rom on BRE5
My Odin screen
batfink1 said:
Honestly, I'm a take your balls in your hand kind of guy.
I'm a computer technician and if I spent all my time wringing my hands being cautious I'd never get anything done.
It's pretty hard to HARD BRICK these phones as long as you don't go faffing around with the partitions option in Odin.
God I've brought mine to the brink of death and back again.
Just out of curiosity, do you have a way of taking a photo of your Odin/Download mode screen... I'll try to post mine.
I'm rooted and running a customised stock based rom on BRE5
Click to expand...
Click to collapse
Well... sometimes it is better to be safe than sorry... (at least this is my take), like with that unfortunate upgrade.
If you're that brave, why don't you upgrade to the latest one and then try to downgrade?
Attached is Download mode screenshot.
batfink1 said:
My Odin screen
Click to expand...
Click to collapse
Interestingly, your model shows 6GB, mine 4GB, but it doesn't matter...
Thanks... I'll debating if to give it a shot with that custom Odin version. Did you try it? Should BL be included?
I said brave, not freaking insane... Mine is rooted and working perfectly
I honestly DON'T want to go through the 17 days of possibly having to wait for the RMM STATE again haha
---------- Post added at 06:25 PM ---------- Previous post was at 06:21 PM ----------
Mines an S9+, they have 6 gig compared to the S9 which only has 4 gig.
I didn't try it, no.. I just know the modded version exists.
I'm having the same problem
Hi guys I'm having the same problem with kernel rev check fail.
I had a brand firmware and tried to make it no-brand, but something went wrong.
Now when trying to flash a no-brand firmware, Odin stops during system.img
What can I do? Do I have to reinstall the same branded old firmware that I had?
Thanks!
Ma5terDevil said:
Hi guys I'm having the same problem with kernel rev check fail.
I had a brand firmware and tried to make it no-brand, but something went wrong.
Now when trying to flash a no-brand firmware, Odin stops during system.img
What can I do? Do I have to reinstall the same branded old firmware that I had?
Thanks!
Click to expand...
Click to collapse
Just a thought - your non-brand might be of an older release than branded software. In worst case you're stuck on working branded soft?
i tried, i doesn't work either with/without BL
batfink1 said:
Have you tried the patched Odin 13.3.1
https://www.google.com.au/amp/s/for...id/software/patched-odin-3-13-1-t3762572/amp/
Click to expand...
Click to collapse
i tried, i doesn't work either with/without BL selected. so i guess the modified odin did not fit for the new firmware.
I Tried
Me too being the grab your balls by the hand person that likes to boldly go where no man has gone before, attempted the patch version of Odin on my s9 in an attempt to put the TMO firmware on to get RCS chat. Using BL AP CL and CSC all did not work. I got the same stupid message regarding the downgrade. I then tried AP and CSC alone. Same issue. Finally, I tried just CSC. It gave a similar error but it was difference in the sense that it says [cache]fused 2 > Binary 1.
It's super annoying that you can't move from u1 to u (unlocked to carrier) without having to do all this crap.
Hey all, dunno if you resolved the kernel error but I was getting the same thing on my S8 (SM-G950F) and ended up checking if anyone at the Samsung store could fix it (they could). Have a look at this post I wrote up, hopefully it's somewhat useful.
https://forum.xda-developers.com/showpost.php?p=77580177&postcount=18
Same problem I got. No matter if I use modded or normal ODIN... Even if I do not flash Boot, I got the message Kernel Rev. check fail...
To me, this is almost criminal from Samsung... I pay 800 Euro for the phone and I like to run a different system. I think there is no law against using a Computer (which in fact it is) with an Operating system of my choice.
To me, a restriction of "liberty".
joe535 said:
Same problem I got. No matter if I use modded or normal ODIN... Even if I do not flash Boot, I got the message Kernel Rev. check fail...
To me, this is almost criminal from Samsung... I pay 800 Euro for the phone and I like to run a different system. I think there is no law against using a Computer (which in fact it is) with an Operating system of my choice.
To me, a restriction of "liberty".
Click to expand...
Click to collapse
ODIN is a Samsung INTERNAL tool, you're not even meant to be using it
And you do have the freedom to run whatever OS you want, you have that choice the day you choose to buy a new phone, otherwise read the smallprint, pretty sure you agreed to Samsungs terms when you bought the phone
I don't get why people buy Samsung phones knowing how locked down they can be, knowing they don't run vanilla Android, knowing about KNOX, and then complain when they can't do anything with them.... if I wanted to mod my phone without any problems I wouldn't be buying Samsung
Anyway, honestly I accidentally updated my spare S9 to U2 forgetting it can't be rolled back and I had a little bit of trouble finding a firmware that ran fine with gravity box, but now I'm running a custom BRI3 rooted with magisk running gravity box where 99% of features work including lock screen security.
So unless the U2 bootloader is effecting you in some way... Does it matter if you can't roll back.
Well, the hardware of Samsung I actually do like.. But the software policy I do not.
For sure, never again I will buy Samsung