Recenttly i got a note 2 sch-i317 phone. It was runing the stock 4.3 update from att.
I am on tmobile, so i downgraded the phone to 4.1.1 and unlocked it.
Life is good and the phone is working fine.
then i get the great idea of upgrading back to 4.3 via the OTA update. And there starts all of my issues.
Orignaly i was under the impression i had used a stock att 4.1.1 to downgrade. now looking back i used a rooted version. i dont remember where i found it but here is the name of the file: root66_ATT_I317UCALJ2.tar.md5 (and i had to do a factory reset to get it to boot correctly)
Now here is the issue.
I can not get back into the recovery menu. However i can get into the Download mode.
Tried to flash TW recovery
Tried to flash CWM recovery
Tried to flash I317UCAMA4_I317ATTAMA4_ATT firmware
Tried to flash I317UCALJ2_I317ATTALJ2_ATT Firmware
i installed Kies and installed the usb driver it came with.
At first it did not detect my phone. now it detects my phone. but during the emergency repair, it downloads and extracts the new firmware but sits at 0% (and times out) when it pushes the firmware.
Im at a lost. i have spent 14+ hours in the past 2 days working on this, and i am burning out. help
re-flashed I317UCALJ2_I317ATTALJ2_ATT Firmware
and followed this
http://forum.xda-developers.com/showpost.php?p=49098941&postcount=2
and my phone works again
Woo Hoo !!!!
More goodness here.
http://forum.xda-developers.com/showthread.php?t=2618447
Related
Hello there,
I've previously used Odin to install several versions on several phones, so at leas I know some very basics, like, using Odin and what not.
Here's my problem. I rooted my 4.3, it gave me some trouble, and the main reason I wanted it rooted was to get backups for my apps. Turns out I can back up my data with carbon "rooted-unrooted" so I decided to ditch the root since it was giving me some hassle with the security update thing and titanium was not working properly. "had to do some other stuff and I was kind of tired.
Turns out I tried to install my other official firmware I had "4.1". Sadly, upon using Odin with it, it now says that I'm trying to install an unsupported version and won't proceed... I'm stuck in here because I cannot restart by pressing up+power because it gives me an error and says I need to restart in download mode.
I was wondering if installing a fresh copy of 4.3 would fix this. Yet I've been unable to find any actual official files... yeah... I know this sounds pathetic, but... I've been herer for an hour + and have not found either a solution or the original 4.3 file or whichever file I would need for this.
Decided to turn unto this community which has helped me a lot in the past to solve all my previous issues.
So... How do I install a fresh 4.3 or how do I get out of this mess? My cell phone doesn't turn on, it just tells me the following:
Firmware Upgrade Encountered an issue. Please select recovery mode in Kies & try again.
I had 4.3 installed with all the security crap on it, so when I go to download mode and install 4.1, it says that the verison is unsopported...
Thank you all in advance.
Download Mr Robinson's 4.3 rooted ROM from here.
Flash it via ODIN and you should be good to go.
Your phone is already on 4.3 bootloader and it is not letting you downgrade to any version below it.
I recently installed CyanogenMod 11 on my S3 about a month ago. Yesterday, I got a notification on my phone stating that an update was available for CyanogenMod. I let it install and when the phone rebooted, it was stuck on the bootloader for at least an hour or two. I figured that I must've bricked the phone. I can still get into recovery mode and download mode.
So, I tried to reinstall the stock AT&T GS3 ROM as I had never particularly liked CyanogenMod. I thought this would be a great time to reinstall the stock ROM. I factory reset the phone and flashed the stock ROM (which I downloaded from another thread) using Odin. It automatically rebooted, the Samsung logo flashed for a second and the CyanogenMod bootloader showed up and it has not gone away since. So, what have I done wrong here and is there a way to save my phone? Any help would be greatly appreciated.
Where did you get the ROM you flashed? Did your phone have the 4.3 bootloader? What about Knox?
If your phone has the 4.3 bootloader, you cannot flash the 4.3 ROM via Odin as it was never released as a complete ROM, only as an update. THis might help: http://forum.xda-developers.com/showthread.php?t=2658486
So This is my first time posting on any forum site for help, and i was refereed to XDA by my roommate. so what happened is a few months ago i asked my roommate to root my galaxy s3 SGH-I747, after he rooted it through odin and all seemed well, BUT we never could get the phone to recognize the root and was still unable to access any root functions. so after a few different attempts we gave up. i assumed that my roommate had removed the root (bad call) but never gave it any thought. a few days ago at&t started bugging me with a software update. i just hit ignore and it would pop up again in a few hours and the icon would never go away. so i gave in and started the update. i didnt pay the phone any attention while it "updated" but later that morning i went to turn it back on and it would get to the Samsung screen then the next screen but after that it goes black and vibrates. i showed it to my roommate and he informed me that it was never restored back to official frimware like i had previously assumed. and that it never should have received the update bc it was still on a custom frimware. we tried flashing the stock frimware back on the phone and every time it would fail the nand write. i believe it was updated to 4.4.2 before i received the update from AT&T and we tried many different ways too restore it i even tried the recovery in Kies 3 but all it says is "connecting" then connection failed. so far nothing has worked. i believe that the update contained android 5.0 and maybe that is the reason none of the other ways we tried worked. i have been researching for hours trying to find a similar case but nothing matches, and i cant find a single working solution that doesn't involve possible making it worse. i can access both the recovery and download modes. please any information or help would be greatly appreciated.
Flash a custom recovery such as Philz Touch via Odin, install cm10.2 via your custom recovery. This should get the phone booted so you can determine the bootloader version on your phone. The NAND error is due to the fact that you are trying to downgrade the bootloader in Odin. Don't flash anything with Odin until you determine the bootloader. Doing so could hard brick your phone.
audit13 said:
Flash a custom recovery such as Philz Touch via Odin, install cm10.2 via your custom recovery. This should get the phone booted so you can determine the bootloader version on your phone. The NAND error is due to the fact that you are trying to downgrade the bootloader in Odin. Don't flash anything with Odin until you determine the bootloader. Doing so could hard brick your phone.
Click to expand...
Click to collapse
firstly, thanks for the fast help. i did as you advised and flashed philz touch 6.15.4 which is the latest version from what i understand. that worked flawlessly. the problem now, is with cm10.2 every time ive tried to install it i get an error in /storage/sdcard1/cm-10.2.0-d2att.zip.
im sure im doing everything correctly. any ideas?
Try flashing an older CM11 ROM for the d2lte.
audit13 said:
Try flashing an older CM11 ROM for the d2lte.
Click to expand...
Click to collapse
thanks so much man youve been a big help that worked.
I had TWRP 2870
i was running cm 11 cough made
everything was fine for a few days then realized that i could only receive text messages and my lte was always dropping out. So I verified my APN setting with my wife's i317 and made all adjustments as needed but no help. so i just got fed up with it all and reinstalled from a backup that i made of stock 4.4.2 everything worked then last night my phone received an OTA from AT&T but because I had TWRP it would not install. I am assuming that it was the stage freight update so (all the trouble began) I used a back to stock recovery using a back to stock sticky that i found and it worked it took me all the way back to stock recovery and 4.1.2 I think and then after installing all necessary updates I went to about device and check for updates and it downloaded a update I don't remember the file size but under 500 megs. then it restarted and installed it then rebooted and it would not go past the samsung logo I have tried everything but a pit file or something like that the only thing i have access to is download mode. when I tried going back to stock 4.4.2 using odin3 v.1.85 and flashed I317-UCUCNE5-Stock.tar odin says all is good and I get very happy but the stupid phone wont boot it gets stuck at the same samgung logo for 30mins. help me. please! Im stuck using the captivate untill i get this fixed.
And you cannot boot into recovery using the 3 button combo ??
If yes ....wipe data...factory reset the device...and wipe the cache as well...g
Edit:
The Update will put the device to UCUCNJ1 official and will lock you into the Knox bootloader as well.
The only 4.1.2 reverts from this point forward cannot contain the bootloader image or softbrick will occur....g
Picked up a Note 2 T889 a few days ago. The phone was on 4.3 stock when I got it.
I flashed a 4.3 rom, but when it finally started up, there was no SIM card recognized - even though the phone worked fine before I flashed the rom. Being the quick thinker I am, I downloaded the 4.3 stock and attempted to flash it through Odin without any success. The firmware will lock up when it tries to flash the modem, soft bricking the phone, which I can get around by re-starting the install-recovery-then-everything-else process over.
I tried grabbing the modem.bin and flashing that straight from the stock package, but the phone still says no SIM. When I put the SIM in another phone, it works fine. I've done everything I can think of (short of putting stock back on, because again, stock won't work for some reason) to try and solve the issue. At this point, I'd deal with having stock on the phone if I could get it to recognize the SIM.
I'm going insane trying to get it solved and I know it's something simple.. Anyone?
Thanks in advance.