[Q]Samsung SM-N900 bricked - Galaxy Note 3 Q&A, Help & Troubleshooting

Hello guys,
I tried to root my SM-N900 this morning. I've root my Note 2 before and i thought it would just be the same. Unfortunately as i am starting to root with Odin, i've waited for hours but Odin is still not done with the phone and the download bar progression thing didnt move an inch. So with regret i turned off the phone and now it is stuck on "firmware upgrade encountered an issue" screen. I tried to download firmwares from sammobile but failed at 99% with a message of Unknown Network Error. So with that, are there any other solution possible? I've also tried Kies, but it wouldnt recognize my phone..

@bluws just download any stock firmware for your phone and flash it later with Odin. Use Odin 3.04 or 3.07 if 3.09 failed.
tetakpatalked from Nexus 7 flo

Make sure you are using correct Ver of root, make sure kies not running in bag round when you flash threw Odin, take care of antivirus
Sent from my SM-N9005

bluws said:
Hello guys,
I tried to root my SM-N900 this morning. I've root my Note 2 before and i thought it would just be the same. Unfortunately as i am starting to root with Odin, i've waited for hours but Odin is still not done with the phone and the download bar progression thing didnt move an inch. So with regret i turned off the phone and now it is stuck on "firmware upgrade encountered an issue" screen. I tried to download firmwares from sammobile but failed at 99% with a message of Unknown Network Error. So with that, are there any other solution possible? I've also tried Kies, but it wouldnt recognize my phone..
Click to expand...
Click to collapse
Try to connect your phone from the KIES program in a mode of emergency restoration of firmware by Model phone type and Serial Number of the phone. This may take several hours. To do this, you need a good internet.

bluws said:
Hello guys,
I tried to root my SM-N900 this morning. I've root my Note 2 before and i thought it would just be the same. Unfortunately as i am starting to root with Odin, i've waited for hours but Odin is still not done with the phone and the download bar progression thing didnt move an inch. So with regret i turned off the phone and now it is stuck on "firmware upgrade encountered an issue" screen. I tried to download firmwares from sammobile but failed at 99% with a message of Unknown Network Error. So with that, are there any other solution possible? I've also tried Kies, but it wouldnt recognize my phone..
Click to expand...
Click to collapse
Did you previously disable Knox? If you didn't, that can cause random problems, read about it in the newest Chainfire's thread in recent post:
http://forum.xda-developers.com/showthread.php?p=55325329
What kind of root process did you use Odin for?
tetakpatalked from Nexus 7 flo

Ty guys i got it working just by flashing a new stock rom. Tho now i am unable to call (no mobile services). Apparently it says that there are no sim card or something like that, does the region of the firmware i downloaded have something to do with it. Im living in indonesia (xse) but downloaded the russian stock i think.

bluws said:
Ty guys i got it working just by flashing a new stock rom. Tho now i am unable to call (no mobile services). Apparently it says that there are no sim card or something like that, does the region of the firmware i downloaded have something to do with it. Im living in indonesia (xse) but downloaded the russian stock i think.
Click to expand...
Click to collapse
Good it works again now!
Maybe it is just a baseband problem? I'm sure you will find an asian baseband only and be able to flash it.
Is your IMEI number still there? If yes, make sure to create backup of it now.
tetakpatalked from Nexus 7 flo

Related

Need PIT partition file for at&t S4

Hi Guys,
I had rooted my phone using motochopper then yesterday I received OTA update. Everything seems to be fine then later I started getting Samsung Text-to-Speech engine has stopped working everytime I opened Gallery. It was very frustrating, so I did factory Reset. After Factory reset when I go to last screen to startup my phone(Learn about Key Features:Air view, Air gesture) and click Finish. I get "Unfortunately Settings has stopped" error. I found the stock firmware here hxxp://galaxys4root.com/galaxy-s4-stock-firmware/ But every time I use Odin I get PIT Partition not found.
Please help guys, I am stuck, don't know what to do now. :crying:
You can get the stock firmware from the "Development" section and also a step-by-step guide how to do it...search the development section for it. You can also find a lot of information about the issue you are having with the "stopped settings" error, again you can search for the info. I would also suggest you research ODIN to make sure you have the correct boxes checked so you don't hard brick your phone. Good luck.
i had the same exact issue and tried ODIN. didint work. i used to KIES to restore my firmware and it works again! try using KIES.
scott14719 said:
You can get the stock firmware from the "Development" section and also a step-by-step guide how to do it...search the development section for it. You can also find a lot of information about the issue you are having with the "stopped settings" error, again you can search for the info. I would also suggest you research ODIN to make sure you have the correct boxes checked so you don't hard brick your phone. Good luck.
Click to expand...
Click to collapse
I checked all appropriate settings for ODIN before upgrading the firmware. I got the same error all the time. I will research "Stopped Settings" error and let you know if I find anything. Thanks for the quick response.
kuraijay said:
i had the same exact issue and tried ODIN. didint work. i used to KIES to restore my firmware and it works again! try using KIES.
Click to expand...
Click to collapse
Hi I am choosing "Firmware upgrade and initialization" option to download the firmware. I put my phone into recovery mode as per steps mentioned and click "Start Upgrade" it takes around 40-50 minutes to download the firmware, then after sometime I get failed to connect to the phone. It's weird the "Start Upgrade" option is only enabled after I properly connect the cable and Kies have recognized the phone. Then why after some time it would say failed to recognized please try again?
zukaa12 said:
Hi I am choosing "Firmware upgrade and initialization" option to download the firmware. I put my phone into recovery mode as per steps mentioned and click "Start Upgrade" it takes around 40-50 minutes to download the firmware, then after sometime I get failed to connect to the phone. It's weird the "Start Upgrade" option is only enabled after I properly connect the cable and Kies have recognized the phone. Then why after some time it would say failed to recognized please try again?
Click to expand...
Click to collapse
weird mine never said enter recovery. what i did was plugged in my phone and i did the ""Firmware upgrade and initialization" then it gose through all the agreements and downloads the firmware. then it'll auto boot in to download mode for the install. are you using the stock usb? which port are you using on your computer? is KIES up to date? do you have the right drivers?( then again i think kies will install them but just in case) try already being in download mode.
also you can try this http://forum.xda-developers.com/showthread.php?t=2261232
I tried same at&t stock firmware but this time I used Odin 3.0.7 like Adam recommended in another post to upgrade and it worked like a charm. Before I was using Odin 1.8.5 and I was getting Missing PIT partition error all the time.
Thanks all for the quick response.
kuraijay said:
i had the same exact issue and tried ODIN. didint work. i used to KIES to restore my firmware and it works again! try using KIES.
Click to expand...
Click to collapse
I get different errors trying to flash stock ROM in Odin too. Missing PIT error mostly. Now phone is stuck at bad upgrade screen. Kies won't detect phone to use that method to restore either. Any other suggestions??
stumpmuncher said:
I get different errors trying to flash stock ROM in Odin too. Missing PIT error mostly. Now phone is stuck at bad upgrade screen. Kies won't detect phone to use that method to restore either. Any other suggestions??
Click to expand...
Click to collapse
Read the post above yours. Use the latest Odin 3.0.7.
-Sent from my Samsung Galaxy Note II using Tapatalk 2
What NOT to do with a new S4
RMXO said:
Read the post above yours. Use the latest Odin 3.0.7.
-Sent from my Samsung Galaxy Note II using Tapatalk 2
Click to expand...
Click to collapse
Did. Wouldn't have appealed for help without first making sure I followed the OP's instructions perfectly. I know the rules. I read the other posts before posting. I'm here for 2 things: To learn how to get the most potential out of my devices and to contribute from my experiences when I can. Thanks for your prompt reply though...
EDIT: solution to my stuck phone problem was solved by visit to ATT store for replacement. I can tell you what happened to my 7 day old device that brought it to the point where it would not load through Kies or Odin:
Eager to remove Samsung & ATT bloat stuff, I rooted using motochopper then used Titanium Backup to remove all ATT related apps & some of the Samsung apps. I got the unlock icon on lock screen as others have after root. I removed Superuser and replaced with SuperSU. Unlock icon went away and phone status went back to official. This is when I started noticing the Samsung text-to-speech program would frequently FC during the launch of few apps. Internet would also FC during certain operations. I read of others having success installing the stock ROM with ODIN and decided to give it a try. At first I got the no PIT error then finally after a few repeated attempts it moved past that point but then failed for some other reason during installation. I did notice a little activity on the progress bar on my device during Odin flash, but when the flash failed, that was it. My device was locked up. My PC & Kies would detect the device but could never connect or mount the device. My guess is that some of the Samsung apps I deleted were tied to the Samsung engines and the lack of their presence somehow caused FCs. Comments and questions appreciated.
Got the same Odin Mode Recovery Kies problem, No Pit fixed with ODIN 3.07 used PDA and loaded normal firmware.

[Q] S4 not starting,please help me out!

Hey guys,please help me out.Today while Rooting International Galaxy S4 with CF-Auto-Root via odin,the odin encountered a problem and ended eventually interrupting the Root process.when I turn on the phone it says ''Firmware Upgrade encountered a problem.Use Kies to recover it.''
So i downloaded the official Jellybean 4.2.2.When I started installing this firmware via odin,its always getting stuck at Setup connection and eventually says Failed.This is happening again and again.I tried using different USB ports and using different PC,but still no success.
Please help me out guys,please.
nsnarayan10 said:
Hey guys,please help me out.Today while Rooting International Galaxy S4 with CF-Auto-Root via odin,the odin encountered a problem and ended eventually interrupting the Root process.when I turn on the phone it says ''Firmware Upgrade encountered a problem.Use Kies to recover it.''
So i downloaded the official Jellybean 4.2.2.When I started installing this firmware via odin,its always getting stuck at Setup connection and eventually says Failed.This is happening again and again.I tried using different USB ports and using different PC,but still no success.
Please help me out guys,please.
Click to expand...
Click to collapse
Option 1, Make sure no Kies is running in the background and try flashing using odin 3.07/04
Option 2, uninstall kies restart the system and re do the process of updating the firmware / try diffrnt ports and cable if possible
Option 3, If this does not work try latest firmware that should work
123hiten said:
Option 1, Make sure no Kies is running in the background and try flashing using odin 3.07/04
Option 2, uninstall kies restart the system and re do the process of updating the firmware / try diffrnt ports and cable if possible
Option 3, If this does not work try latest firmware that should work
Click to expand...
Click to collapse
Thanks for the reply bro,but some people say this can be solved with Pit file,but how do i download the pit?My friend is saying download it from My signature.
Now where is signature and how do I do it?
http://forum.xda-developers.com/showthread.php?t=2318447
In that link,the person said see my signature to download it,where is his signature and how do I do it?
nsnarayan10 said:
http://forum.xda-developers.com/showthread.php?t=2318447
In that link,the person said see my signature to download it,where is his signature and how do I do it?
Click to expand...
Click to collapse
I did it guys,I only flashed my phone with Pit file and nothing else.My phone is now booted!

How boned am I?

This evening, due to some slightly buggy behavior that I attribute to removing too many things during a recent "debloat session", I attempted to restore my rooted N3 to stock using the most current firmware and Odin. Something went very wrong and the flash failed. My N3 now advises that "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again". So I tried Kies Emergency Device Recovery, but Kies will not connect to my phone in any screen I am able to access. The phone will only boot to the Odin Mode screen. I can't get to the recovery, either.
I've tried Kies in both Windows 7 and Mac OS Mavericks, tried different cables and USB ports, updated Kies as well as drivers, but I'm not making any headway.
I've tried using Kies option to upgrade the firmware, but my N3 doesn't have the S/N printed anywhere on the phone. I'm away from home, but I have a call in to a friend to get the S/N off the box... But I'm not holding my breath that this path will succeed.
I'd bite the bullet and go to Sprint, but as I'm sure you are aware, a rooted Note 3 clearly shows 0x1 under Knox Warranty Void on the Odin Mode screen (which again, is the only screen I can access).
I'm well and truly stuck. Are there any options I'm missing? Something I've overlooked?
nathanotis said:
This evening, due to some slightly buggy behavior that I attribute to removing too many things during a recent "debloat session", I attempted to restore my rooted N3 to stock using the most current firmware and Odin. Something went very wrong and the flash failed. My N3 now advises that "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again". So I tried Kies Emergency Device Recovery, but Kies will not connect to my phone in any screen I am able to access. The phone will only boot to the Odin Mode screen. I can't get to the recovery, either.
I've tried Kies in both Windows 7 and Mac OS Mavericks, tried different cables and USB ports, updated Kies as well as drivers, but I'm not making any headway.
I've tried using Kies option to upgrade the firmware, but my N3 doesn't have the S/N printed anywhere on the phone. I'm away from home, but I have a call in to a friend to get the S/N off the box... But I'm not holding my breath that this path will succeed.
I'd bite the bullet and go to Sprint, but as I'm sure you are aware, a rooted Note 3 clearly shows 0x1 under Knox Warranty Void on the Odin Mode screen (which again, is the only screen I can access).
I'm well and truly stuck. Are there any options I'm missing? Something I've overlooked?
Click to expand...
Click to collapse
Hi mate try and flash this rom it's like a super rom it fixes anything http://forum.xda-developers.com/showthread.php?t=2461929
It's got me out of trouble a few times
jaythenut said:
Hi mate try and flash this rom it's like a super rom it fixes anything http://forum.xda-developers.com/showthread.php?t=2461929
It's got me out of trouble a few times
Click to expand...
Click to collapse
These seem to be only 9005 and 900 ROMS, ie, not for the N900P (Sprint).
nathanotis said:
These seem to be only 9005 and 900 ROMS, ie, not for the N900P (Sprint).
Click to expand...
Click to collapse
Oh bugger
What about Cwm can you flash that then flash a custom rom
nathanotis said:
...
I've tried using Kies option to upgrade the firmware, but my N3 doesn't have the S/N printed anywhere on the phone.
...
Click to expand...
Click to collapse
My N9005 (and to be honest every single original Samsung phone that I have seen in last year, and the number is pretty big) have BOTH the IMEI and the SN written on a sticker under the battery.
xclub_101 said:
My N9005 (and to be honest every single original Samsung phone that I have seen in last year, and the number is pretty big) have BOTH the IMEI and the SN written on a sticker under the battery.
Click to expand...
Click to collapse
I know where it's *supposed to be*, but the only numbers on said sticker are; DEC, HEX, Model and FCC ID (which I tried, just in case). There is NOTHING else on that sticker.
jaythenut said:
Oh bugger
What about Cwm can you flash that then flash a custom rom
Click to expand...
Click to collapse
Last night I tried flashing the most current firmware and when that failed, I tried an older copy I have that has worked before. Neither succeeded and both result in the Odin screen on the phone saying: "sw rev check fail fused 2 binary 1" (which I've been googling but found no working answers yet).
The message Odin gives is "FAIL! (Auth)". I've read this morning about how the most current firmware (MI3) removes root and plugs some security holes. Some think it won't be rootable...
Is this my problem?
nathanotis said:
This evening, due to some slightly buggy behavior that I attribute to removing too many things during a recent "debloat session", I attempted to restore my rooted N3 to stock using the most current firmware and Odin. Something went very wrong and the flash failed. My N3 now advises that "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again". So I tried Kies Emergency Device Recovery, but Kies will not connect to my phone in any screen I am able to access. The phone will only boot to the Odin Mode screen. I can't get to the recovery, either.
I've tried Kies in both Windows 7 and Mac OS Mavericks, tried different cables and USB ports, updated Kies as well as drivers, but I'm not making any headway.
I've tried using Kies option to upgrade the firmware, but my N3 doesn't have the S/N printed anywhere on the phone. I'm away from home, but I have a call in to a friend to get the S/N off the box... But I'm not holding my breath that this path will succeed.
I'd bite the bullet and go to Sprint, but as I'm sure you are aware, a rooted Note 3 clearly shows 0x1 under Knox Warranty Void on the Odin Mode screen (which again, is the only screen I can access).
I'm well and truly stuck. Are there any options I'm missing? Something I've overlooked?
Click to expand...
Click to collapse
this happened with me too "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again".
If you can still go to ODIN/Download mode everything is fine.
Just download the latest firmware for your phone, old firmware won't do as you can not downgrade bootloader. Then flash it in ODIN.
vikas724 said:
this happened with me too "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again".
If you can still go to ODIN/Download mode everything is fine.
Just download the latest firmware for your phone, old firmware won't do as you can not downgrade bootloader. Then flash it in ODIN.
Click to expand...
Click to collapse
I can get into Odin mode, so that's great news... Unfortunately I tried to flash the most current firmware and got the same result. The failure message in Odin is "Fail (Auth)". at the same time the device says something in red text about a "SW REV" issue.
I'm downloading the most current FW again from Samsung. (WHY DOES IT TAKE SO LONG?!) I'll post back when I try again.
I'm back up and running! I had downloaded a firmware ending in mi3, the MOST current is mj4, which flashed over to my N3 without issue.
Thanks all for the assist.
nathanotis said:
I know where it's *supposed to be*, but the only numbers on said sticker are; DEC, HEX, Model and FCC ID (which I tried, just in case). There is NOTHING else on that sticker.
Click to expand...
Click to collapse
Sprint is CDMA right? CDMA phone got no IMEI.
It got the same purpose of IMEI called MDN or something. But it got NO IMEI.
Try latest stock ROM, coz if you're on newer bootloader, it wont allow you to flash downgrade....

[Help] OMG! Did i Brick my new note 3!? :(

Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck.
Do you know what Region the phone was originally? I had a similar issue and I had to get the Hong Kong (in my case) version of a stock ROM and flash that to get things working again. Not all partitions are the same - you might need a PIT file to match your original region and then flash the ROM.
What info do you get in DL mode?
Journyman16 said:
Do you know what Region the phone was originally? I had a similar issue and I had to get the Hong Kong (in my case) version of a stock ROM and flash that to get things working again. Not all partitions are the same - you might need a PIT file to match your original region and then flash the ROM.
What info do you get in DL mode?
Click to expand...
Click to collapse
Yes the phone is for AT&T so it's US. When I go into DL mode Knox counter is still 0x0. Is there a certain firmware I need then to match with the AT&T model? Or a pit?
jthornton71707 said:
Yes the phone is for AT&T so it's US. When I go into DL mode Knox counter is still 0x0. Is there a certain firmware I need then to match with the AT&T model? Or a pit?
Click to expand...
Click to collapse
Go to Sammobile and see if you can find the version you had, sounds like an older JB if kingo app didn't trip Knox. Reflash that using ODIN.
I don't know if there was a problem with American bootloader, see if there's an AT&T Note 3 forum. Might find answers there...
jthornton71707 said:
Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck.
Click to expand...
Click to collapse
Hi mate,
if you are stuck, maybe you can try this.
http://forum.xda-developers.com/show....php?t=2701062
it's a way to unbrick your software.
and if the older owner of your N3 said it's on the latest firmware of kitkat.
maybe your problem is the firmware in the sammobile were before the firmware you have install on your device via OTA update.
Yours firmware came throw out via OTA update and with some reason you can't see any latest firmware USA N900A in sammobile.
try the method in the link and reply if you have been successful.
cumps
Ik Knox is 0×0,then u can try samsung service centre ?
Sent from my SM-N900 using XDA Premium 4 mobile app

Galaxy S4 wont boot!

So I recently got a Galaxy S4 last night, I rooted it with Kingoroot and it worked great. I then went to sleep and left it alone to wake up to it trying to install a AT&T update and then turning off and booting to a screen that says "Samsung Custom" and does the same processs again.
I have spent more than 2 hours trying to fix this with no avail.
I tried to install stock 4.2.2 but I receive as Fail in Odin which I learned is because you can't install older Android OSes.I then tried to install stock recovery because when I try to boot to recovery it tries to install the update again.
No luck.
I heard of something called a MF3 and downloaded the files but not sure how to use them...
I can still get into Download Mode
This is my main phone so I really need help.
I've read people got soft brick while updating their phones rooted with kingroot!
Try flashing the stock kernel
Google everything before you make sensitive changes in your phone!
Although rooting isnt that sensitive these days!
Sent from my MT27i using XDA Free mobile app
Piyush jaiswal said:
I've read people got soft brick while updating their phones rooted with kingroot!
Try flashing the stock kernel
Google everything before you make sensitive changes in your phone!
Although rooting isnt that sensitive these days!
Sent from my MT27i using XDA Free mobile app
Click to expand...
Click to collapse
After playing around with it, It I am now hit with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I connect to Kies and It claims the Galaxy S4 isnt supported.
PCiE said:
After playing around with it, It I am now hit with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I connect to Kies and It claims the Galaxy S4 isnt supported.
Click to expand...
Click to collapse
Use this guide. You can stop at section 2 if you want to stay at Kitkat or go to section 3 if you want to update to Lollipop.
You can definitely install older versions, but you have to start with a full ROM like NB1. My guess is you flashed an incremental update like NC1, NJ4, etc. so Odin failed. When you Odin though, make sure Kies is completely closed or better yet, uninstall it as they hate each other
PS: This is assuming you have AT&T S4. I have no clue about other variants.

Categories

Resources