Odin froze - Galaxy Note II Q&A, Help & Troubleshooting

I pulled out an old samsung galaxy note 2. The t-mobile model sgh-t889 i believe. i was trying to upgrade it to android 4.4. I found somewhere saying the official at&t roms work for this phone. I tried the most recent one. I317-UCUCNJ2-Stock.tar.md5. this was the file I used. Odin failed almost at the end. Now the phone is frozen in odin with a complete blue bar. Any ideas? i want to flash the tmobile stock rom again but i don't want to make the situation worse?

Hopefully, a locked att bootloader was not flashed to the phone.
All you can do at this point would be to power off the phone, boot into download mode, and try flashing the latest stock rom from sammobile.com.

Related

[Q] Trying to Downgrade to 4.1.2

Hello,
I'm trying to downgrade my Canadian Note 2 (SGH-i317M) from 4.3 back down to 4.1.2 but I'm having some issues.
First off, the Sammobile.com firmware site doesn't even have the file available anymore. I tried getting it for Virgin Mobile, but it says the file isn't found so I guess they deleted it off their servers. Since it should be exactly the same for any of the 3 carriers and their subsidiaries I tried flashing a Telus version and a Bell version but both failed to flash in Odin.
After the failed flash I get the yellow firmware failed text screen and it telling me to do an emergency recovery in Kies, which of course I can't do.
So, does anyone know why the flashing is failing?
Thanks
http://forum.xda-developers.com/showthread.php?t=2618447
Looks like you have to do the battery pull/boot into recovery/factory reset steps described in the thread linked above.
I have the same problem. I have i317m though. I got 4.1.1 but can't get rid of the modified status, nor will it accept 4.1.2. Done that how to 5 times. Darn knoc had to mess up the fun.
Try installing 4.1.1 via odin

[Resolved] Possibly bricked, help?

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 already regret trying to add custom ROM.

Hello,
I tried to flash custom ROM, but something somewhere went terribly wrong.
I did read some guides on flashing before attempting this and did make some precutions as well.
Such as creating ROM backup with CWM and copying efs folder with Root browser.
Unfortunately I didn't succeed with the flash. Now the phone can turn on, but there is no network service, and IMEI number is missing.
I tried to go back to my original ROM, but that didn't fix the problem.
I tried to gather as much information as possible, but it seems that information on this device is a bit outdated. For example, I wanted to try to flash back to stock ROM with odin, but most links with stock ROM are down. The one that isn't down only provides .7z file instead of md5,tar file that is required by odin.
The device works, just can't connect to mobile network.
Is there something I could do?
Before flashing anything else, what baseband and bootloader is on the phone? The imei may be missing because the ROM is too new for the phone's current bootloader/modem combination.
Bootloader version is T999UVDLJA
Baseband version is UKNKOWN
I have finally found stock ROM in tar.md5 format, which is compatible with ODIN.
The t999 is the aws version of the s3 according to this: http://www.gsmarena.com/samsung_galaxy_s_iii_t999-4804.php
This forum is for the i747 and i747m (the AT&T and Rogers) version of the s3.
If the t999 is like the i747, do not flash any ROM via Odin that tries to downgrade the bootloader as this may brick the phone.
This makes just even more complicated.
When I go to settings -> About device, under model number I have SGH-I747.
When I double check this with Samsung phone info app, under model number I have SGH-I747.
In the same Samsung phone info app under PDA version I have I747UCDLK3 and under CSC version I have I747ATTDLK3
t999 only appears when I enter Download mode via volume down + home button + power button.
What does the label under the battery say about the model #?
Label under the phone is SGHT999.
Wow, this phone is weird...
I read on the forums that there is chance to restore firmware of the phone with KIES, so I tried that. At first I entered SGH-I747 model number and serial number of the phone and it failed. But after that I entered SGH-T999 model number and serial number of the phone and KIES started to update the phone.
At the moment I have android V4.3
Bootloader T999UVUENC2
Baseband T999UVUENC2
PDA version T999UVUENC2
CSC version T999MBENC2
Phone seems to be unrooted, IMEI number is visible, I can call again, but the phone's factory mode is on.
It seems that I had a SGH-T999 which somehow was tricked int thinking that it is SGH-I747.
At the moment I would just like to have a stock ROM for this phone without all the T-Mobile apps, would that be possible?
Does everything see to work?
The easiest way to root and remove apps would be to flash a custom recovery, install supersu and titanium backup. Then use titanium backup to remove the apps.
Yes, at the moment everything works.
I can call, receive sms, use wi-fi as well as mobile data.
The only problem is that phone has factory mode on Yellow text on black background. And it is heavily loaded with T-Mobile applications.
So I guess this phone is T999 then, right? How could it be that everywhere it had I747?
By custom recovery you mean custom ROM?
You need a custom recovery such as TWRP: http://forum.xda-developers.com/showthread.php?t=1809313
Download the tar version that can be flashed via Odin.
Download supersu and copy it to the phone. Flash recovery, boot directly into recovery without letting the phone boot the ROM, flash supersu, reboot. Install Titanium Backup from the Play store, remove the apps.
Thank you for sticking with me in this thread!
Could you please explain a little bit more what is TWRP? From the link provided I understand that is is a application that helps with custom rom flashing and backing up roms?
Shouldn't I do this at first - http://forum.xda-developers.com/showthread.php?t=1771687
Boot into download mode. Do you see anything about warranty bit 1? If you do, that means you have already tripped the counter.
Root is not required to flash a custom recovery.
If you are only interested in root, follow the other thread. If you want to be able to flash custom ROMs and backup the rom, you need a custom recovery which will definitely trip the counter.
Do you have any warranty left on the phone?
Yes, there is 1 next to warranty bit. What does it mean for me that I have tripped the counter?
At the moment I would just like to get rid of factory mode and remove those unwanted T-mobile APPS. I think I will be done with Flashing for quite some time
I don't have any warranty on the phone, It has been in the family for quite some time.
It would be 0 if the counter wasn't tripped.
To bring it right back to stock, you could flash one of the prerooted ROMs from the other thread. Just make sure you are flashing a rom that has the same bootloader that is currently on your phone. Hopefully, the stock rom will remove the factory mode.
I understand that the counter is only important if you need warranty, yes?
I actually just found a way how to remove the factory so that is one more thing less to worry about
And I rooted the phone with odin using the link few posts back.
Now for the final question, I understand that this rom is something along the lines that I'm looking for? http://forum.xda-developers.com/showthread.php?t=2501303
The ROM looks nice as long as you are running the correct bootloader and modem.
Installing a custom ROM only requires a custom recovery. There is no need to root or remove apps from the existing ROM since you are going to wipe the existing ROM before installing the new ROM.
I read through the thread and I understand that I have to flash T999UVUEMJC modem before flashing the ROM.
I'm not sure where the bootlaoder of this rom is mentioned. Only place where boot loader of my device T999UVUENC2 is mentioned is in change log "-Rebased to T999UVUENC2".
The official T-mobile firmware is here: http://www.sammobile.com/firmwares/database/SGH-T999/
Notice the last few letters in the firmware PDA?
Based on your post on the first page (post #7) you are on the NC2 bootloader and modem, which are compatible with the rom you are wanting to flash. (See the second line under the Disclaimer banner.) NC2 is the most current firmware for the T999 listed on the page Audit linked to.
(one explanation for how your device was reporting i747)
Is it possible that someone else flashed the i747 rom to this phone? Either someone doing you a favor or a previous owner? I747 roms will work on the T999, I frequently see people commenting on doing so successfully. You just need to have comparable bootloaders and modems. That and if the rom dev didn't accommodate the device in the updater-script the user must edit the script himself. In the unofficial cm12.1 thread for the i747 people were doing this often.
So the bootloader version is always the same as the modem version?
I understand that in my case I don't need to flash T999UVUEMJC modem, since the one I have at the moment is newer?
That is definitely possible, although, how it came to be I will never know, since I personally didn't buy the phone. But this would explain a lot.
Could you please take a look at this thread, I created steps I plan to do in order to flash the above mentioned ROM. It would really put my heart at ease http://forum.xda-developers.com/galaxy-s3-t-mobile/help/one-rom-flashes-please-double-check-t3111443

Tmobile Note II thinks its an ATT - Bricked?

Hello everyone, so long story short I accidentally flashed my Tmobile Note II SGH T889 with the ATT rom (I317UCALJ2_I317ATTALJ2_ATT.zip) while trying to go back to stock. Now in download mode my phone reads as if it's an ATT model, I'm not even sure how an ATT firmware flash passed on odin. Phone wont boot and I cannot access recovery mode as it just spits " Firmware upgrade encountered an issue." I cant upload a pic due to external links, but the phone says "Product Name: SGH-I317" when in download mode, or are as my phone reads "ODIN MODE".
I've tried flashing every version of the stock Tmobile roms via odin 3.12 and all of them fail at the very end. I don't know what to do anymore. Any insight into this is much appreciated, thank you!
Update: I managed to flash TWRP through odin, but flashing stock MD7 through custom recovery still lands me in a bootloop.
Was the phone purchased new or used? Do you recall see the T889 model # in download mode before flashing?
It was given to me used by a family member. It was in functioning condition but running very buggy so I wanted to flash stock and go from there. I do not recall seeing the SGH-T889 model # in download beforehand as I really wasn't expecting to make such a foolish mistake. The phone is unquestionably an SGH-T889 though, confirmed by the back cover and the IMEI sticker behind the battery.
The only way to really confirm that the phone is a T-Mobile note 2 would have been to boot int download mode. Since the att firmware flashed in Odin with no errors, I'm inclined to believe that the phone motherboard was actually from an att note. I have never seen Odin allow such cross flashing.
Maybe open the phone and examine the motherboard to confirm model number?
I could open the phone and search for the model number on the mobo, but why on earth would the back sticker read as an SGH-T889? This is a funky situation.
It could be a frankenphone. The motherboard from a t889 will fit in a i317 amd i317m and vice versa.

I need 4.1.1 firmware for Koodo i-317M

Hello guys,
For some reason, my phone shows that my SIM is locked ( I was on RR 6.0). I need to flash the 4.1.1 firmware for Koodo to unlock the SIM.
Can anyone send me a link for this firmware?
Thank you!
You don't need Koodo to unlock the sim. Just flash the stock LJ2 firmware with Odin and use the dialler menu to permanently network unlock the phone.
https://forum.xda-developers.com/showthread.php?t=2014982
Maybe this will work: http://rapidgator.net/file/0207e341...yos.com/samsung-galaxy-note-2-stock-firmware/
I know it's been a long time, but did this procedure actually WORK? AFAIK, Koodo Note 2s never came with less than KitKat, and we all know that Samsung has blocked downgrading though its bootloader starting then.
The reason I ask is I'm looking for a spare phone for mine as a backup and can't seem to find one on which I can load my Jellybean 4.1.2 CM based phone image.
Well this an interesting post, I have a similar problem, I have 2 exact Note 2 phones one with custom firmware (4.1.1) one without, I would like to copy/clone the stock firmware to my other (as I somehow managed to delete the stock firmware on it)
Now I have made a backup with TWRP and copied it to the other phone but TWRP refuses to install it, it tries to install and gets most of the way but at the very end I get the 255 error "install failed"
Why can't I copy/ install this backup?
Do I need to to use some other recovery software or make a backup some other way.
Thanks
Old faithful said:
I know it's been a long time, but did this procedure actually WORK? AFAIK, Koodo Note 2s never came with less than KitKat, and we all know that Samsung has blocked downgrading though its bootloader starting then.
The reason I ask is I'm looking for a spare phone for mine as a backup and can't seem to find one on which I can load my Jellybean 4.1.2 CM based phone image.
Click to expand...
Click to collapse
The note 2 sgh-i317m was used by Telus, Rogers, and Bell.
This downgrade method works. I've used it to network unlock four note 2 models.
The stock 4.1.1 firmware from sammobile.com did not contain a bootloader file which allowed me to flash it using Odin on a phone running a stock 4.4.2 rom.
audit13 said:
The note 2 sgh-i317m was used by Telus, Rogers, and Bell.
This downgrade method works. I've used it to network unlock four note 2 models.
The stock 4.1.1 firmware from sammobile.com did not contain a bootloader file which allowed me to flash it using Odin on a phone running a stock 4.4.2 rom.
Click to expand...
Click to collapse
Man, if this really works it's going to solve all my problems. Are you saying you can flash the 4.1.x ROM on top of the the 4.4.2 bootloader (presumably one could deselect the bootloader from the 4.1.x ROM if it was included - sorry I'm quite rusty at this, haven't used Odin in years), so that the phone may be running ICS or JB despite having a 4.4.2 encrypted (locked) bootloader?
The idea is being able to load Clockworkmod recovery and from it, the rooted 4.1.2 backup on my external sd card...
Sorry if it's been asked before and if I may be confused - Thing is, I haven't done this type of tweaking in 5 years
I could flash a stock 4.1.1 ROM from sammobile.com on top of a stock 4.4.2 ROM because the stock 4.1.1 ROM didn't contain a bootloader. I did this to use the menu method to network unlock the sgh-i317m; however, the phone cannot stay on a stock 4.1.1 ROM with a 4.4.2 bootloader because the phone cannot connect to a cellular network with this 4.1.1 ROM/4.4.2 bootloader combination. After I unlocked the phone, I either re-flashed a stock 4.4.2 ROM or a new custom ROM.
The bootloader on the Canadian Note 2 was never locked the way it was with some USA carriers.
audit13 said:
The bootloader on the Canadian Note 2 was never locked the way it was with some USA carriers.
Click to expand...
Click to collapse
Are you saying the Koodo/Rogers.... 4.4.2 Note 2 bootloader is NOT locked on our phones, ergo, that I could downgrade to 4.1.1 including its bootloader successfully?! If so I'm set, I could purchase a used one on kijiji and simply reload my old Bell based ROM backup on it I simply look for a way to load my 5 year old Rooted ROM onto a newer version of the phone. I have on it apps that won't run on 4.4.2 that I sorely miss on my tablet (which runs 4.4.4)
The bootloader is not locked which allows for the installation of TWRP and cwm but it cannot be downgraded.
audit13 said:
The bootloader is not locked which allows for the installation of TWRP and cwm but it cannot be downgraded.
Click to expand...
Click to collapse
In other words it does allow for installing the 4.1.1 ROM for unlocking the phone, but it can't can't actually be used with the 4.1.1 ROM... What if I simply reinstalled the 4.4.2 modem, wouldn't that work?
I now I'm asking quite a lot - but in my case if I haven't been able to find a used phone that hadn't been at some point 'upgraded' and consequently became shackled (I've been looking for over a year now) in which case I might as well mourn it and move on to a new phone and start the fight for freedom all over again Honestly, I've grown tired of having to fight for the basic right of ownership against the relentless push for slavery that is the general trend in technology, to force people away from freedom of using the software they prefer and force them into a system where they must follow the dictates of corporate giants so perfectly exemplified by the cell phone, computer and browser based service industry.
Like Frederick Douglass famously said "Power concedes nothing without a demand. It never had and never will"... In other words if you want freedom and true control, you MUST FIGHT the providers and the manufacturers whose prime interest is to keep you enslaved
Installing the 4.4.2 modem will install but the stock 4.1.1 dialer doesn't work with a 4.4.2 modem and 4.4.2 bootloader from what I recall. It's been a long time since I had a note 2.

Categories

Resources