I upgraded my GT-N7100 from 4.1.2 to 4.4.2 stock rom, had the "unregistered to network problem", so I rooted the phone, Installed custom recovery, then flashed many modems but all didnt work, so I decided to go back to 4.1.2, but it didnt work, got "FAIL" on odin, and "sw rev. invalid magic string" written on my phone.
I flashed the 4.4.2 again, however, this time the mobile freezes after 30 seconds after pressing the power button, tried to flash different stock 4.4.2 roms, but it keeps freezing. I cant downgrade my phone back to 4.1.2 due to the KNOX bootloader.
Is there any solution to go back to 4.1.2, by disabling the KNOX ?
Raptor 2020 said:
I upgraded my GT-N7100 from 4.1.2 to 4.4.2 stock rom, had the "unregistered to network problem", so I rooted the phone, Installed custom recovery, then flashed many modems but all didnt work, so I decided to go back to 4.1.2, but it didnt work, got "FAIL" on odin, and "sw rev. invalid magic string" written on my phone.
I flashed the 4.4.2 again, however, this time the mobile freezes after 30 seconds after pressing the power button, tried to flash different stock 4.4.2 roms, but it keeps freezing. I cant downgrade my phone back to 4.1.2 due to the KNOX bootloader.
Is there any solution to go back to 4.1.2, by disabling the KNOX ?
Click to expand...
Click to collapse
Which bootloader are you running atm?
pnxsinned said:
Which bootloader are you running atm?
Click to expand...
Click to collapse
Knox bootloader.
Raptor 2020 said:
Knox bootloader.
Click to expand...
Click to collapse
Download DN3 v5.2 ROM and install it through TWRP 2.7
manuel1992 said:
Download DN3 v5.2 ROM and install it through TWRP 2.7
Click to expand...
Click to collapse
Thanks for reply but i want to go back to official 4.1.2
Raptor 2020 said:
Thanks for reply but i want to go back to official 4.1.2
Click to expand...
Click to collapse
first do this and then go back to 4.1.2 But I think there is no way to downgrade
Related
As you'll soon discover, I'm a noob. I stupidly took the OTA update on my Samsung Galaxy S3 T-Mobile T999 from 4.1.2 to 4.3. Since doing so mine and my wife's phone (did the same thing to her also) gets in a mess after being connected to the car stereo bluetooth and prevents outgoing calls unless the phone is rebooted.
So to try to solve this, I rooted the phone and installed CM 11, so now I'm on 4.4.2. This didn't help the issue either and instead is worse at connecting to the bluetooth.
I want to get my phone back to the stock 4.1.2 rom, which I got from sammobile (PDA T999UVDMD5) or at worst back to the 4.3 stock rom (PDA T999UVUEMJC).
This morning I tried to flash T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar using ODIN 307 but it failed almost instantly with an Fail! Auth message.
I also tried to flash CM 10.1 zip on my SD card using ClockworkMod Recovery v 6.0.4.5 but again it failed almost instantly (sorry I didn't take note of the error).
So now I'm back to CM 11. So any suggestions for how to get back to either of the stock roms?
huz666 said:
As you'll soon discover, I'm a noob. I stupidly took the OTA update on my Samsung Galaxy S3 T-Mobile T999 from 4.1.2 to 4.3. Since doing so mine and my wife's phone (did the same thing to her also) gets in a mess after being connected to the car stereo bluetooth and prevents outgoing calls unless the phone is rebooted.
So to try to solve this, I rooted the phone and installed CM 11, so now I'm on 4.4.2. This didn't help the issue either and instead is worse at connecting to the bluetooth.
I want to get my phone back to the stock 4.1.2 rom, which I got from sammobile (PDA T999UVDMD5) or at worst back to the 4.3 stock rom (PDA T999UVUEMJC).
This morning I tried to flash T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar using ODIN 307 but it failed almost instantly with an Fail! Auth message.
I also tried to flash CM 10.1 zip on my SD card using ClockworkMod Recovery v 6.0.4.5 but again it failed almost instantly (sorry I didn't take note of the error).
So now I'm back to CM 11. So any suggestions for how to get back to either of the stock roms?
Click to expand...
Click to collapse
If you are getting errors in both odin and cwm, it sounds like it is a root issue. In other words, it sounds like the apps are being denied access to root and therefor cannot flash. Both odin and cwm are able to generate logs so you can tell the reason for the fail. Personally, I would recommend flasing twrp recovery instead of cwm since it seems to simplify alot and is a little better for our device. Without knowing exactly why the flash is failing, i would just recommend to try and re-root the phone again.
Did you put the phone in Downloading mode before connecting to the Odin ?
Do not try to flash 4.1.2 ever. It will brick your phone.
Perseus71 said:
Did you put the phone in Downloading mode before connecting to the Odin ?
Do not try to flash 4.1.2 ever. It will brick your phone.
Click to expand...
Click to collapse
Yes the phone was in downloading mode. I couldn't find any posts that thought that I would brick my phone for sure by downgrading so I thought I would try. Could I go back to the 4.3 Stock ROM with some degree of confidence?
Yes you can go back to 4.3 Stock.
Perseus71 said:
Yes you can go back to 4.3 Stock.
Click to expand...
Click to collapse
So I'm now back to Stock 4.3 by doing a flash via Odin. I did (stupidly) try to then go back to 4.1.2 again using Odin having put the phone in USB debugging mode first but I still got the same Auth Fail error.
Thanks for all the help.
huz666 said:
So I'm now back to Stock 4.3 by doing a flash via Odin. I did (stupidly) try to then go back to 4.1.2 again using Odin having put the phone in USB debugging mode first but I still got the same Auth Fail error.
Thanks for all the help.
Click to expand...
Click to collapse
You cannot downgrade like that once you have updated to official 4.3 firmware, no offence but why would you try it even after Perseus said not to? Anyway if you want to go back to 4.1.2 so badly just download a 4.1.2 ROM and flash it in recovery
Sent from my SGH-M919 using Tapatalk
serio22 said:
You cannot downgrade like that once you have updated to official 4.3 firmware, no offence but why would you try it even after Perseus said not to? Anyway if you want to go back to 4.1.2 so badly just download a 4.1.2 ROM and flash it in recovery
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
.
Thanks for the advice. I think I'll just quit while I'm only slightly behind now and remain on 4.3 Stock. I appreciate everyone's help and suggestions.
Downgrade from CM11 4.4.2 to 4.3 on I747
I went from 4.3 stock to CM11 on my i747 but i didnt like the update. So i am trying to go back to 4.3 however whenever i try to install the 4.3 zip file thru twrp or CWM, it fails. As far as i know there is no odin file for going back. I tried to flash rogers 4.3 file through odin (thinking i would flash at&t modem later) but that also failed.
I would appreciate any help on how to install 4.3 once 4.4.2 has been installed on an i747
You seriously need to do some reading
Sent from my SGH-T999 using Tapatalk
nitagro said:
I went from 4.3 stock to CM11 on my i747 but i didnt like the update. So i am trying to go back to 4.3 however whenever i try to install the 4.3 zip file thru twrp or CWM, it fails. As far as i know there is no odin file for going back. I tried to flash rogers 4.3 file through odin (thinking i would flash at&t modem later) but that also failed.
I would appreciate any help on how to install 4.3 once 4.4.2 has been installed on an i747
Click to expand...
Click to collapse
For One, you are on the wrong forum. This is for T-Mobile's S3 not AT&T. Second, Like @passtheknowledge said, you really need to do significant research and reading here on XDA.
Perseus71 said:
For One, you are on the wrong forum. This is for T-Mobile's S3 not AT&T. Second, Like @passtheknowledge said, you really need to do significant research and reading here on XDA.
Click to expand...
Click to collapse
I was up all night reading and trying all the suggestions that have been posted so far. Nothing worked. I would appreciate if someone can throw some light on what might be wrong.
nitagro said:
I was up all night reading and trying all the suggestions that have been posted so far. Nothing worked. I would appreciate if someone can throw some light on what might be wrong.
Click to expand...
Click to collapse
Please Read through this Thread. For Future Reference, all Odin Files for S3 in general are looked up by unique Keyword Root66. That thread is the right place for you to post errors or issues. If there's no 4.3 image for your phone there, you can post a request as well.
For your immediate Problem, there is a an alternate ATT StockMod Rom by @saranhai Please see this thread. Pay particular attention to the mandatory requirement of flashing a particular modem beforehand.
Hello! I am new to this forum but I am in a little fickle.
I have the Samsung Note 2 TMOBILE and couple weeks ago, I updated to 4.3 through regular OTA. I then rooted and flashed Cyanogenmod 11 and thus, voided my Samsung Knox Warranty bugger thing. I then attempted to go back to stock by flashing stock 4.1.1 through Odin and it worked! I tried to do OTA update again but I realized that the Samsung Knox Void kept me from reaching update services... So I was stuck at 4.1.1 Stock. From there, I was able to flash other custom roms and everything worked.
However, this is a problem for me. The 4.1.2 update from Tmobile was what enabled LTE on my note 2. So right now, I have the old baseband(?) that does not allow LTE. I even attempted to flash a non-knox 4.1.2 (which allowed LTE) through Odin and everything worked until the last second, where Odin is supposed to flash PASS..... It flashed FAIL and I was unable to update my baseband(?).
I was wondering if there is another way to enable LTE by updating to 4.1.2 in any way? Or is this completely unable due to the Samsung Knox?
Thank you in advance.
Alex9995 said:
Hello! I am new to this forum but I am in a little fickle.
I have the Samsung Note 2 TMOBILE and couple weeks ago, I updated to 4.3 through regular OTA. I then rooted and flashed Cyanogenmod 11 and thus, voided my Samsung Knox Warranty bugger thing. I then attempted to go back to stock by flashing stock 4.1.1 through Odin and it worked! I tried to do OTA update again but I realized that the Samsung Knox Void kept me from reaching update services... So I was stuck at 4.1.1 Stock. From there, I was able to flash other custom roms and everything worked.
However, this is a problem for me. The 4.1.2 update from Tmobile was what enabled LTE on my note 2. So right now, I have the old baseband(?) that does not allow LTE. I even attempted to flash a non-knox 4.1.2 (which allowed LTE) through Odin and everything worked until the last second, where Odin is supposed to flash PASS..... It flashed FAIL and I was unable to update my baseband(?).
I was wondering if there is another way to enable LTE by updating to 4.1.2 in any way? Or is this completely unable due to the Samsung Knox?
Thank you in advance.
Click to expand...
Click to collapse
try flash modem with mobile odin
cosmyndemeter said:
try flash modem with mobile odin
Click to expand...
Click to collapse
How does one flash a modem? What exactly is the modem in the note 2?
Alex9995 said:
How does one flash a modem? What exactly is the modem in the note 2?
Click to expand...
Click to collapse
how to flash modem with mobile odin
what is modem?why i need that?
zPhaph thus
cosmyndemeter said:
how to flash modem with mobile odin
what is modem?why i need that?
Click to expand...
Click to collapse
Thank you! Before I mess anything up, I just have a couple more questions. Do I just have to find the 4.1.2 modem? Or even 4.3? I already have CWM and am rimming cm 11 4.4.2. Does this mean I must downgrade first before I attempt to flash a modem?
Alex9995 said:
Thank you! Before I mess anything up, I just have a couple more questions. Do I just have to find the 4.1.2 modem? Or even 4.3? I already have CWM and am rimming cm 11 4.4.2. Does this mean I must downgrade first before I attempt to flash a modem?
Click to expand...
Click to collapse
flash the modem for that firmware you have before install cm11
hit thanks button if this help you
cosmyndemeter said:
flash the modem for that firmware you have before install cm11
hit thanks button if this help you
Click to expand...
Click to collapse
Hey man! It worked. I am finally getting LTE service after I installed the 4.3 modem. I just want to thank you so much! And I will hit the thanks button.
Alex9995 said:
Hey man! It worked. I am finally getting LTE service after I installed the 4.3 modem. I just want to thank you so much! And I will hit the thanks button.
Click to expand...
Click to collapse
:good:
Hello all!
I was on cyanogenmod earlier today and got an update on my phone and did the update but my phone got into an infinite boot screen. I reverted back to stock from this thread..http://forum.xda-developers.com/showthread.php?t=2258628 and by using the stock TAR and I was able to get back to stock firmware. However at the boot logo, I still get the warranty bit: kernal message and also I am not able to connect to wifi because I am stuck at the, "turning on wifi".
Can anyone help please? Thanks!
edit 1: the phone takes a long time to boot up compared to when I had stock firmware before..
First you need to check what android version you are on. Were you on the 4.3 OTA upgrade before you rooted and flashed CM? Were you on the MDL bootloader with the mk2 modem?
Sent from my SGH-M919 using xda app-developers app
I was on 4.3 OTA upgrade. Idk about MDL Bootloader...
flipthetomato said:
I was on 4.3 OTA upgrade. Idk about MDL Bootloader...
Click to expand...
Click to collapse
If I remember correctly you should not be able to downgrade from the OTA 4.3 to 4.2. I believe this is why you are having problems. The stock tar you flashed is only for those of us who did not take the OTA and still have the MDL bootloader. Your warranty is now void because your Knox counter was tripped by taking the OTA and flashing while on 4.3. You will need to download the 4.3 stock firmware from here http://www.sammobile.com/firmwares/3/?download=22280 and flash through Odin your issues should be solved then except your warranty. Good luck!
Sent from my SGH-M919 using xda app-developers app
So download the stock 4.3 firmware and follow the same steps on Odin?
Also, if 4.4.2 came out for my phone, could I still update?
flipthetomato said:
Hello all!
I was on cyanogenmod earlier today and got an update on my phone and did the update but my phone got into an infinite boot screen. I reverted back to stock from this thread..http://forum.xda-developers.com/showthread.php?t=2258628 and by using the stock TAR and I was able to get back to stock firmware. However at the boot logo, I still get the warranty bit: kernal message and also I am not able to connect to wifi because I am stuck at the, "turning on wifi".
Can anyone help please? Thanks!
edit 1: the phone takes a long time to boot up compared to when I had stock firmware before..
Click to expand...
Click to collapse
If you downloaded the link that said Stock Tar, then the firmware you have is outdated with bugs (MDB). Acoording to what you have said with the warranty bit, the phone will work correctly if you flash UVUEMK2 (4.3): https://www.copy.com/s/1yJkfBBGa4VwTzl/M919UVUEMK2_M919TMBEMK2_TMB.zip
Thanks for reading.
I was on stock rooted 4.3. I went back to complete stock 4.1 using odin in order to update to 4.4. i started with the first update and installed fine but wouldnt boot past the first samsung note screen. I tried to get into recovery but no success. I can get into download mode. What else can I do to get the phone booted.
thanks!
koarthur84 said:
Thanks for reading.
I was on stock rooted 4.3. I went back to complete stock 4.1 using odin in order to update to 4.4. i started with the first update and installed fine but wouldnt boot past the first samsung note screen. I tried to get into recovery but no success. I can get into download mode. What else can I do to get the phone booted.
thanks!
Click to expand...
Click to collapse
Download this and flash in odin in the ap or pda slot
http://d-h.st/iVH
terpin32 said:
Download this and flash in odin in the ap or pda slot
http://d-h.st/iVH
Click to expand...
Click to collapse
Thank You
similar
i was running slimrom 6.8 and it was working just fine. then my work email required that i encrypt the phone. phone would not encrypt. went back to stock 4.1.2 and encrypted and was running successfully. decided to OTA update and back stuck to bootscreen.
i tried other bootloaders, but this is the only that has worked. will repeat going to stock, encrypt. no more ota for me!
unless someone knows if there is an encryption friendly rom out there?
miserly said:
i was running slimrom 6.8 and it was working just fine. then my work email required that i encrypt the phone. phone would not encrypt. went back to stock 4.1.2 and encrypted and was running successfully. decided to OTA update and back stuck to bootscreen.
i tried other bootloaders, but this is the only that has worked. will repeat going to stock, encrypt. no more ota for me!
unless someone knows if there is an encryption friendly rom out there?
Click to expand...
Click to collapse
Just do the 4.4.2 updated rom like a stock touchwiz or maybe a cm rom would be able to
I have S4 with MDL bootloader, was running GE based roms...and now want to restore it to STOCK and upgrade to latest firmware. Giving it away to my father so want to make completely stock with ability to receive OTAs .
Last night flashed via Oden stock 4.2.2 (MDL) rom, modem, and restored counter to (0). Tried to upgrade from the phone to the latest firmware, but getting the error (Processing Failed). Installed Kies 2.x.x and it would not recognized the device. Please Help to install latest stock 4.4.4 rom with (0) counter
Is the error when it tries to update or when checking for updates?
when checking for updates from the phone it self, but Kies also fails to connect to the phone.
You may want to try again later. Also does your computer recognize it at all?
serio22 said:
You may want to try again later. Also does your computer recognize it at all?
Click to expand...
Click to collapse
Yes, I've installed sam. drivers ... Odin, MTP and PTP works fine... Bootloader shows Samsung Rom, (0) counter...
T1001 said:
Yes, I've installed sam. drivers ... Odin, MTP and PTP works fine... Bootloader shows Samsung Rom, (0) counter...
Click to expand...
Click to collapse
what baseband are you on?
serio22 said:
what baseband are you on?
Click to expand...
Click to collapse
MDL baseband
T1001 said:
MDL baseband
Click to expand...
Click to collapse
Hmm well not sure what the problem is then. Try to update to 4.3 via odin and then give the ota a try and see it'll work
serio22 said:
Hmm well not sure what the problem is then. Try to update to 4.3 via odin and then give the ota a try and see it'll work
Click to expand...
Click to collapse
What about bootloader? and setting the counter to 0? 4.3 will flash new bootloader with KNOX and then I'll never be able to restore to 100% stock, or I'm wrong?!
For your phone to be stock right now it would have to be on NK2 firmware. Nothing wrong with that.
Knox only matters for the first 12 months, after that it's your phone not Samsung's.
Pp.
T1001 said:
What about bootloader? and setting the counter to 0? 4.3 will flash new bootloader with KNOX and then I'll never be able to restore to 100% stock, or I'm wrong?!
Click to expand...
Click to collapse
As long as you don't root it or modify it in anyway, you'll always be 100 percent stock
PanchoPlanet said:
For your phone to be stock right now it would have to be on NK2 firmware. Nothing wrong with that.
Knox only matters for the first 12 months, after that it's your phone not Samsung's.
Pp.
Click to expand...
Click to collapse
If I flash latest firmware via Odin, will it get OTAs in the future?
Not if your rooted /custom recovery and debloated, as you remove all the T-Mobile and Samsung bloat you will not get any ota updates, ( I haven't in16 months ) . I run stock /debloated /rooted.
You can run stock rooted or find a stable custom rom to use.
Pp.
Fixed it.
Re flashed the firmware via Odin again, cleared cache and data before first boot and thats fixed it!