[Q] Forgot to enable USB Debugging before update - Galaxy S 4 Q&A, Help & Troubleshooting

Hello guys,
I updated my Galaxy S4 I9500 to 4.3 Jellybean officially.
Had troubles while operating the updated versions, like slow typing, notification bar not sliding etc
I then tried to downgrade using 4.2.2 firmware, but i hurry i forgot to Enable USB Debugging before Odin start
The operation "NAND writing failed" and my phone is now stuck at
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried Kies, but failed. Then tried Kies manually, by entering Model number and Serial Number but that process doesnt also works.
I have downloaded many softbrick recoveries but fails, as i did not enable USB Debugging.
Kindly get me out of this soft brick.
Thanks in advance.

Related

HELP: I bricked my Note 3 (N900). Forget to enable USB debugging before flashing!

I have just bricked my newly-bought Note 3 (N900).
I wanted to flash the latest version of Note 3 via Odin 3.08 (from 4.3 to 4.4.2). I made a big mistake as I didn't enable the "USB DEBUGGING" mode before go to download mode.
I clicked start in Odin and it show FAIL!!!
After I restart the phone all I see on the screen is the message "Firmware upgrade encountered an issue Please select recovery mode in Kies & try again."
I tried to recover it through Kies, but the it shows the phone is not connected or not support. Meaning the Kies cannot communicate with the phone at all.
I also tries to flash in Odin many times, but it still fails.
Please!!! Can anyone here give me some solution.
Thanks.
boycam said:
I have just bricked my newly-bought Note 3 (N900).
I wanted to flash the latest version of Note 3 via Odin 3.08 (from 4.3 to 4.4.2). I made a big mistake as I didn't enable the "USB DEBUGGING" mode before go to download mode.
I clicked start in Odin and it show FAIL!!!
After I restart the phone all I see on the screen is the message "Firmware upgrade encountered an issue Please select recovery mode in Kies & try again."
I tried to recover it through Kies, but the it shows the phone is not connected or not support. Meaning the Kies cannot communicate with the phone at all.
I also tries to flash in Odin many times, but it still fails.
Please!!! Can anyone here give me some solution.
Thanks.
Click to expand...
Click to collapse
make sure kies is not running then try odin again
jaythenut said:
make sure kies is not running then try odin again
Click to expand...
Click to collapse
I tried many time already, but still fail. I think because the usb debugging mode was not enable at the first place.
Thank anyway.
boycam said:
I tried many time already, but still fail. I think because the usb debugging mode was not enable at the first place.
Thank anyway.
Click to expand...
Click to collapse
Usb debugging has nothing to do with it failing when you're using odin. Try a different version of odin.
A simple reflash via Odin 1.85 or 3.07/3.04 will fix it.
boycam said:
I have just bricked my newly-bought Note 3 (N900).
I wanted to flash the latest version of Note 3 via Odin 3.08 (from 4.3 to 4.4.2). I made a big mistake as I didn't enable the "USB DEBUGGING" mode before go to download mode.
I clicked start in Odin and it show FAIL!!!
After I restart the phone all I see on the screen is the message "Firmware upgrade encountered an issue Please select recovery mode in Kies & try again."
I tried to recover it through Kies, but the it shows the phone is not connected or not support. Meaning the Kies cannot communicate with the phone at all.
I also tries to flash in Odin many times, but it still fails.
Please!!! Can anyone here give me some solution.
Thanks.
Click to expand...
Click to collapse
USB Debugging has nothing to do with odin flash, make sure while flashing below steps.
1. Update boot loader is selected in odin.(Edit:for single file not required)
2. Disable antivirus.
3. make sure note 3 drivers are installed.
4. kies not running in bag round.
5.Clear Factory Data & Catch before flash.
if all of those step fail..
try to flash ur rom on other computer or laptop
Sent from my SM-N900 using XDA Premium 4 mobile app
radicalisto said:
A simple reflash via Odin 1.85 or 3.07/3.04 will fix it.
Click to expand...
Click to collapse
Thankx man itis worked:good::good:
jdomadia said:
USB Debugging has nothing to do with odin flash, make sure while flashing below steps.
1. Update boot loader is selected in odin.(Edit:for single file not required)
2. Disable antivirus.
3. make sure note 3 drivers are installed.
4. kies not running in bag round.
5.Clear Factory Data & Catch before flash.
Click to expand...
Click to collapse
tried flashin with diff odin versions, was not working, tried ver 1.85, cause it lets you select update boot loader.......and BAM,,it worked on my tmobile tab 4, now i c.an wipe the tears off the key board, thanks, didnt do # 5 tho, was rooting the tab with cf auto.
markap99 said:
tried flashin with diff odin versions, was not working, tried ver 1.85, cause it lets you select update boot loader.......and BAM,,it worked on my tmobile tab 4, now i c.an wipe the tears off the key board, thanks, didnt do # 5 tho, was rooting the tab with cf auto.
Click to expand...
Click to collapse
You've indeed saved my day... I've been searching high and low, installing various versions of Odin3, downloading tonnes of tar, tarmd5, zip, etc.!
Pardon me for my ignorance, but I never intended to root my cell phone in the first place. I was merely following what Kies suggested, "A New Firmware, Wanna Upgrade?" Oh, truly? Gee, thanks! And **** it, it screwed up my GT-N7000, saying "Firmware upgrade encountered an issue..." and my cell phone never saw the daylight again, regardless how I started it, factory-reset mode wasn't possible at all, only download mode could be started up. Tried with various methods of Odin3 on multiple ROMS, to no avail, until I read your short reply. BAM! (As you put it...)
Thanks a bunch, mate!
I have a similar issue with my sm n900. Lost my imei and baseband, i needed to flash a custom rom to get my baseband before working on the imei, after flashing via odin phone boots to samsung logo then goes blank. And recovery says E failed to mount efs . But i need to use adb on my pc. So how can i possibly enabe usb debugging in order for adb to find my device?
Flashing a stock ROM from sammobile.com via Odin does not require USB debugging. Flashing a stock ROM will flash everything, including modem, bootloader, and recovery.
My N900 Bricked
I am unable to Go to download mode not even the charging symbol too
no Luck at all phone is not starting need a Unbrick or help me how to get it sorted
galaxy Note 3 Sm N900
Tried to open the phone to short the wire but the shorting mentioned in all the imagees doesnt match the design of the phone internal
can some one tell me which points to short to start the phoen in Ext sd mode
or any help would help

[Q] Did I just brick my s4?

Hi, I have a rooted galaxy s4 LTE with android 4.3, and was going to update to 4.4.2 via odin 3.09, but during the middle of the installation, I heard a usb disconnection sound, and a red light saying fail appeared on odin. I waited a while, but nothing, and when I restarted my phone, I got that message "firmware upgrade encountered an issue. please select recovery mode in kies and try again" with some odin console messages on top.
I don't know why I can't recover with kies, nothing shows up on the list, and I tried to flash again with odin, using the same rom, but it failed.
what should I do?
I downloaded the official rom from sammobile.
thanks in advance
fael097 said:
Hi, I have a rooted galaxy s4 LTE with android 4.3, and was going to update to 4.4.2 via odin 3.09, but during the middle of the installation, I heard a usb disconnection sound, and a red light saying fail appeared on odin. I waited a while, but nothing, and when I restarted my phone, I got that message "firmware upgrade encountered an issue. please select recovery mode in kies and try again" with some odin console messages on top.
I don't know why I can't recover with kies, nothing shows up on the list, and I tried to flash again with odin, using the same rom, but it failed.
what should I do?
I downloaded the official rom from sammobile.
thanks in advance
Click to expand...
Click to collapse
i had the same problem before! it was the usb ports in my pc ! i changed pc, i used my laptopt and everything were ok! just test another usb port or another pc using odin and original rom and everything should be ok! Dont panic ur phone is ok
remember always to run odin as administrator
hey! yeah, apparently it was those front usb ports, both of them weren't working properly, when I connected to another usb behind the computer it worked fine installing the same rom through odin.
phew!
thanks

[Q] at&t s4 brick need help guys desperately

hi xda guys this is my story
i have an at&t samsung s4 on android 4.2 i have tried to update it via wifi to 4.4
but no use. a message appear say's " your device is up to date "
i have tied "loki way" it failed
i have tried "odin tool way' it failed it won't complete the proses
i have tried samsung kais it fail's too a message says no update for this device
***** i managed to root the device
and then i found the safestrap apk i have insert the TWRP recovery
i have made a backup in case something go's wrong
and i have tries to flash a clean google s4 4.4.4 rom
**** and then the the phone stuck of samsung logo and vibrate often .the TWRP is lost
**** i have tried to recover the the via samsung kias it made it wors
now it have message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
i have tried via odin using the official firmware that i have downloaded. but did not work olso
i have tried the kais recovery mode but i did not get the recovery code
help my friend what should i do
nead you help desperately
any help
any help any one
:fingers-crossed:
You need to go to the at&t section on xda. This section is not for your phone.
Because you don't give any details about the Odin error, I can't help you further.
Most Odin errors can be solved by:
- Other cable
- Other usb port
- Other pc.

Help s4

I recently got the update for lollipop on samsung kies 3.
I have an i9500 s4.
I got into my pc and had gone through the process and for some random reason my samsung kies popped out an error and the firmware upgrade failed so i had to do emergency recovery. Now the problem is that the emergency software recovery isnt working properly and so my phone has one error screen which i have posted as an attachment. Kindly help me through this process as i need this phone crucially.
Flash ROM via Odin (with pit)
thanks for replying
please give me a link to a detailed tutorial (with pit)
and my my phone is not rooted.
Everything you need is in the general section
Reply with help (SOS)
i tried flashing a lollipop firmware with odin v3.10.6 for about 20 times.
all i get is a xmit data write fail.
my phone can't start or go into recovery mode, all it can go to is download mode.
is there a way where i can reset my device completely or just upgrade to lollipop.
my s4 is a gt i9500 and it isn't rooted.
please get me a solution and a decent one.
Thanks for all the help in advance. please help :crying:
Sounds like you have a bad connection
Change your cable and USB connection
thanks dsa i got the fix

bricked N900 android 5.0 with activation lock

soft bricked the phone (on android 5.0) while trying to root it, when I tried to flash it via odin, I kept on getting a failed message after NAND Write.
after some searching, I realized the reactivation lock was on before I bricked it. I can get into download mode, but not the recovery. it gives a message "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
is there anyway to revive it?
What is the error message or log from Odin?
You can still flash the phone with Odin even on the "firmware upgrade encountered an error" message.
Have you tried using different USB cables or USB ports? I recommend using the USB 2.0 ports if possible.
The error message is something like
"Nand write"
"Failed".
Already tried 3 different cables and two different computers. Based on my research, it looks has to be related to reactivation lock.

Categories

Resources