This is a dumb question but searching threads provided me with ten different ways and I wasn't sure which one to pick.
I'm currently on NE6 and have TWRP Recovery and Root. I want to upgrade to NG4 via PC Odin. How should I accomplish this and maintain root and TWRP Recovery?
Download the NG4 firmware & modem from here. Flash them both via Odin. It's good practice to do a battery pull before Odin flashing for 30 seconds, then booting into download mode. It may take a few flashes to get the bootloader to stick. Confirm bootloader after flashing by booting into your current ROM and checking 'About Device' under settings. The Baseband version should read ~NG4. If it doesn't, repeat the process (including the battery pull) until it sticks. Do a full wipe then flash Stock Root Flashable Version of G900TUVU1ANG4 (or any other NG4 variant) in TWRP.
Related
Hello,
I have a Bell Samsung Galaxy Note which had Gingerbread but could not find the OTA upgrade to ICS for some reason. It originally had ICS but flashed it back to Gingerbread since I wanted to start from scratch (using Odin). I've had numerous issues flashing it using Odin (many nand flash errors, soft brick, etc) but now I flashed it to AT&T stock, just to test if everything was working. All is good for now.
I want to upgrade it to ICS to perform the T-mo unlock trick but everytime I try to flash an Odin ICS tar, I get hit with an error at some point and the phone puts itself in Kies recovery mode (Firmware upgrade encountered an issue). Here are my questions:
1. Upon flashing an ICS tar in Odin, should I select the re-partition option in Odin (e.g. does it have a PIT file in there)? Or can I just go ahead and flash the tar file under PDA?
2. Should I do a factory wipe on top of the cache wipe in recovery before flashing an Odin tar?
3. Are there any OEM stock images/ROMs (AT&T, Bell or other) that can be flashed with a cwm/twrp recovery? All I can find are tar files, I know I can probably modify them and remove the recovery.img but would rather not as this might break things.
4. Any issues flashing through VMware Fusion on a MacBook Pro? Could this be the cause of my issues?
johnny grep said:
Hello,
I have a Bell Samsung Galaxy Note which had Gingerbread but could not find the OTA upgrade to ICS for some reason. It originally had ICS but flashed it back to Gingerbread since I wanted to start from scratch (using Odin). I've had numerous issues flashing it using Odin (many nand flash errors, soft brick, etc) but now I flashed it to AT&T stock, just to test if everything was working. All is good for now.
I want to upgrade it to ICS to perform the T-mo unlock trick but everytime I try to flash an Odin ICS tar, I get hit with an error at some point and the phone puts itself in Kies recovery mode (Firmware upgrade encountered an issue). Here are my questions:
1. Upon flashing an ICS tar in Odin, should I select the re-partition option in Odin (e.g. does it have a PIT file in there)? Or can I just go ahead and flash the tar file under PDA?
2. Should I do a factory wipe on top of the cache wipe in recovery before flashing an Odin tar?
3. Are there any OEM stock images/ROMs (AT&T, Bell or other) that can be flashed with a cwm/twrp recovery? All I can find are tar files, I know I can probably modify them and remove the recovery.img but would rather not as this might break things.
4. Any issues flashing through VMware Fusion on a MacBook Pro? Could this be the cause of my issues?
Click to expand...
Click to collapse
A few days ago I purchased a ATT i717 locked and used the TMO Radio to unlock it as described in a unlock sim thread. I then installed an ATT ROM and am actually using it with a metropcs SIM card.
I began by originally using odin to root and install touch recovery. I somehow got stuck on the SAMSUNG logo but was able to get into recovery and flash the goldie rom. Since then I have installed a kit kat rom and everything is fine.
FYI, if anyone is wondering, it was VMware Fusion causing interference - I later found a reference to it on another xda post while searching for something else but it wasn't that easy to find. I have another MacBook with Boot Camp and that one can flash through Odin without any issues. So if anyone is trying to VM their way through Odin flashing, it's a bad idea. It'll stick your phone in recovery mode. Since then I've flashed/restored many Odin files, reinstalled cwm, flashed a few roms including Custom Canadian JB, Padawan JB 4, AT&T Stock, etc.
I have a SGH-i527 that got the 4.4.2 OTA update last night. I'm not sure what I did, but I think I tried to flash the 4.2.2 via Odin when I was encountering problems with Kit Kat. Now when trying to boot, I am stuck on the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." screen.
I have tried to get Kies to go through emergency recovery but the phone never shows up there. And obviously, trying the flash the 4.2.2 firmware in odin will not work. So I am stuck. Any thoughts?
If you did flash the JB ROM after the KitKat update, you will have to flash the KitKat firmware since you cannot downgrade the bootloader and you have probably voided the warranty. Flash the KitKat update for the specific model and DO NOT try to root, flash custom recovery or downgrade to Jellybean since it will trip the Knox boot loader and you will have a brick. Hope this helps
To my understanding, there is not a KK stock rom that I can flash (at least for the i527). And since I can't flash back to 4.2.2, it looks like I'm stuck.
Why flashing 4.2.2 by Odin did not change your situation? Maybe try to flash another ROM?
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
I have purchased a galaxy nexus on the cheap to hold me over until the nexus 6 is out but if I can fix my note, I would like to.
I know there were other threads about this same issue but it seems that they are all on a different version of the note, or on a s3 or something. Not to mention, I don't see anything that I could try without asking for some help on here. Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Thanks guys!!!
amberkalvin said:
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
Click to expand...
Click to collapse
Before you tried to flash a custom ROM and things went wonky...were you on Verizon's factory stock 4.3 MJ9 firmware, or on Beanstown106’s modified 4.3 MJ9 with TWRP installed?
Does the phone still boot into stock recovery? If so, you may be able to fix the phone by doing a factory reset.
amberkalvin said:
Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Click to expand...
Click to collapse
If you were on Verizon's factory stock 4.3 MJ9, then you won't be able to Odin flash back to 4.1.2 or any earlier Android version because the bootloader has been locked down tight on 4.3 (and 4.4.2) with no current do it yourself method to unlock for those newer versions. You would want to restore the phone back to factory stock 4.3 though, if that's what version you were on before your phone got messed up. You can root the phone on 4.3 with saferoot, then use safestrap recovery to flash some custom Touchwiz ROM's.
If you were on the 4.1.2 based bootloader, (but running Beanstown106’s MJ9 firmware and TWRP), then you would want to restore your phone back to factory stock 4.1.2 and then root and unlock the bootloader again with CASUAL. This would give you the most flexibility with flashing custom kernels, ROM's, etc...
Check out Section 1b in Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. The guide has download links for the files you'll need to restore the phone back to the correct build version.
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
William31 said:
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
Click to expand...
Click to collapse
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
mattnmag said:
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
Click to expand...
Click to collapse
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
William31 said:
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
Click to expand...
Click to collapse
Cool. Glad you got it fixed.
As you know, you can root with GhettoRoot from this thread: http://forum.xda-developers.com/showthread.php?p=57238246
Then can install Safestrap from this thread: http://forum.xda-developers.com/showthread.php?p=51616723
I've never used Safestrap because I can use regular custom recoveries like CWM and TWRP. I'm still on a 4.1.2 unlocked bootloader and currently running TrentsKKRom, Build #2...which is 4.4.2 based with stock kernel, so I think it would work with Safestrap.
I'd recommend reading through the Safestrap thread thoroughly and asking questions there to make sure you get everything installed correctly. I've read that with Safestrap, you need to make a backup of your Stock ROM first and save it somewhere safe, like to your computer and on your external sd card...so you can easily restore it if needed. (I'd also make a backup of the ESF in Safestrap if it lets you, then save it somewhere safe).
After you are rooted with Safestrap, you'll have to flash custom ROM's over the stock slot in Safestrap, as the other slots apparently don't work. Again, you're limited to only using Touchwiz ROM's with the stock kernel because of the bootloader still being locked.
Check out TrentsKKRom and Alliance build 30 . (I personally like Trent's build 2 best with the S5 clean theme). I've also found Trent's ROM to be really smooth without UI lagging, the Bluetooth works good with no stuttering, and it pairs well with my Sony Smartwatch 3. (Edit: If you do try Trent's ROM, you may need to install a couple apps.... Chainfire's Supersu app to control your root permissions (at least I needed to), and the FolderMount app to fix a KitKat internal storage mounting issue).
Have fun!!
Note 3 Running Android 5.01 from Sprint.
I've had both OC5 and OH! (I think is the new one from August)
Both Firmware I try to install CWM or TW via ODIN and its unsuccessful. When I try to get into recovery it reverts to some errors while in Downloading.
Most recent attempt I re-installed stock firmware OC5. Ran OTA upgrade to newest firmware. Used CF to root and again ODIN to install CWM. Still same thing.
What am I missing here?
FYI if I use ROM Manager to install CWM it says its successful but can't book into recovery. It will just loop the bootloader so I have to use Odin to reinstall the firmware.
What ver. Of Oden you using?
Originally I used 3.07 but aftrer coming across this issue I've wiped and reinstalled the firmware and tried again using 1.85. Both versions had no luck.
Try Oden 3.10
Missing root. Try to reroot via odin, and try twrp via odin. If no go...put stock via odin and select nand erase. You may get stuxk on sprint logo when boots, go into recovery and do wipe. The reboot stock will load. Then root via odin, and install twrp or cwm via odin. This fixes all my problems...even when i thought phone was dying