Related
My i9000 respond to Downloading Mode (Volume Down+Home+Power) but it doesn't boot...the logo stay on and on until I decided to take off the battery.
Is there a foolproof method to recover my phone? It was locked to T-Mobile and has been unlocked to all networks and rooted - the ROM was Gingerbread 2.3 and working perfectly until I decided to "upgrade" to Jelly Bean...:silly:
I did backup the previous ROM via CWR but right now I can't access any partition...
Help!
with gazbil
Does ODIN recognize your phone when you're in download mode? If so, you should be able to flash gingerbread without losing all your data.
Skire90 said:
Does ODIN recognize your phone when you're in download mode? If so, you should be able to flash gingerbread without losing all your data.
Click to expand...
Click to collapse
thanks for your reply....
Yes Odin recognize my phone and I've tried to update using "JW4" (these 3 letters represent the end of a ROM file which isn't Gingerbread - I've followed this tip from another thread) - Odin says PASS (green box) but when I try to reboot the phone get stuck in Recovery mode (3?) - there are some errors, related to Data and Cache which I believe need to be erased from previous install but still no luck...
I'll try to post a picture of the error messages (or maybe I just copy the text here). At least the booting gives some signals now - there is a logo loop while before there was no boot whatsoever - so, things seems to improve a bit.
solved!
I've solved the problem by installing dbdata.rfs:
hope this helps others....
in the end I got into troubles because I didn't wipe data and cache before flashing the new ROM.
I'm a newbie on XDA so pardon anything that I might do "wrong"
So I was using safestrap recovery to play around with some custom roms, and I was going to switch to a new rom so I thought I was going to delete everything from Rom-Slot 1, but actually ended up going to the section where you can check off everything you want to delete from the the rom. I ended up checking all except micro SD card, and ended up deleting all the data from the stock rom by accident. I tried restarting the phone but all I see now is a stuck "Galaxy Note 3" on boot-up.
I've tried using Odin (with the BL AP CP CSC and PIT files ) to flash back and Oneclickbin.exe, but none work. They all give me a fail message shortly (or a couple minutes) after I press start
Additional notes:
Rooted with kingo root
I got the OTA update on the stock rom (The one with the black stock keyboard)
Please Help!!!
How do I fix this?!?!
UPDATE: Problem not fixed, but when I try to turn on the device, it now says:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I plugged my phone in the computer and kies can't connect to the device....
XerorebornX said:
I'm a newbie on XDA so pardon anything that I might do "wrong"
So I was using safestrap recovery to play around with some custom roms, and I was going to switch to a new rom so I thought I was going to delete everything from Rom-Slot 1, but actually ended up going to the section where you can check off everything you want to delete from the the rom. I ended up checking all except micro SD card, and ended up deleting all the data from the stock rom by accident. I tried restarting the phone but all I see now is a stuck "Galaxy Note 3" on boot-up.
I've tried using Odin (with the BL AP CP CSC and PIT files ) to flash back and Oneclickbin.exe, but none work. They all give me a fail message shortly (or a couple minutes) after I press start
Additional notes:
Rooted with kingo root
I got the OTA update on the stock rom (The one with the black stock keyboard)
Please Help!!!
How do I fix this?!?!
UPDATE: Problem not fixed, but when I try to turn on the device, it now says:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I plugged my phone in the computer and kies can't connect to the device....
Click to expand...
Click to collapse
Are you using Kies 3 or just the regular Kies?
Try putting the phone in download mode yourself, then plug into kies 3
Still no
Are you using Kies 3 or just the regular Kies?
Click to expand...
Click to collapse
I'm using Kies 3 and tried emergency recovery. It didn't work. Kies 3 actually doesn't even recognize my note 3 as a supported device, but I attempted the recovery anyway. I can get to step in the recovery where the recovery window on my computer says, "Do Not disconnect your device from the PC" but the loading bar never goes past 0%, then after a while it'll give me another fail message...
Try this
http://forum.xda-developers.com/showthread.php?t=2559715
XerorebornX said:
I'm using Kies 3 and tried emergency recovery. It didn't work. Kies 3 actually doesn't even recognize my note 3 as a supported device, but I attempted the recovery anyway. I can get to step in the recovery where the recovery window on my computer says, "Do Not disconnect your device from the PC" but the loading bar never goes past 0%, then after a while it'll give me another fail message...
Click to expand...
Click to collapse
Try this my friend (Same as above post sorry)
XerorebornX said:
I'm using Kies 3 and tried emergency recovery. It didn't work. Kies 3 actually doesn't even recognize my note 3 as a supported device, but I attempted the recovery anyway. I can get to step in the recovery where the recovery window on my computer says, "Do Not disconnect your device from the PC" but the loading bar never goes past 0%, then after a while it'll give me another fail message...
Click to expand...
Click to collapse
itmaster85 said:
Try this
http://forum.xda-developers.com/showthread.php?t=2559715
Click to expand...
Click to collapse
Problem solved!!!
Thank you so much
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
[UPDATE] .after looking around all day i have found i am able to successfully flash the n900a AP, CP, and PIT files, however the problems seems to be whenever i try to flash a Bootloader file. The update gives me the error on the phone "SW REV CHECK FAIL" FUSED 3 BINARY 2. My knox counter is still 0x0. By flashing the at&t AP, PIT, and CP files the phone now boot loops and no longer takes me to the screen requesting me to restore thru KIES. However all it does it bootloop. I try to boot into recovery and it will tell me at the top left of the screen "booting recovery" but then just turn off and go right back to the "samsung galaxy note 3 screen" Does anything have any idea here?????
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
if you have a att note 3 you might be screwed both the firmwares you list are not for our phone your best bet would be to go to a best buy or att service center and seee if they can reflash your phone
Is there a tar for the AT&T firmware? I've searched but this was all I could find.
jthornton71707 said:
Is there a tar for the AT&T firmware? I've searched but this was all I could find.
Click to expand...
Click to collapse
Yeah, it seems that the N900XXUDNA6 is not for the US Variant
"N900XXUDNA6 Android 4.4.2 KitKat official firmware update for Galaxy Note 3 SM-N900 is now rolled out by Samsung. This is the first KitKat official firmware for Galaxy Note 3 SM-N900. The firmware update rolled out in various countries including Sri Lanka, Nepal, Indonesia, Singapore, Vietnam, Kazakhstan, Ukraine, Russia, Thailand and India"
The DNA6 would be for the SM-N900 Exynos CPU devices, not the SM-N900A Snapdragon. That is probably your problem (In addition to trying to roll back to JB from KK)
Unfortunately, I dont know of any stock KitKat firmware. There is MI9 on Samfirmware's site, but that is JB not KitKat
jthornton71707 said:
Is there a tar for the AT&T firmware? I've searched but this was all I could find.
Click to expand...
Click to collapse
sorry.
B_I_N_G_E said:
sorry.
Click to expand...
Click to collapse
So after looking around all day i have found i am able to successfully flash the n900a AP, CP, and PIT files, however the problems seems to be whenever i try to flash a Bootloader file. The update gives me the error on the phone "SW REV CHECK FAIL" FUSED 3 BINARY 2. My knox counter is still 0x0. By flashing the at&t AP, PIT, and CP files the phone now boot loops and no longer takes me to the screen requesting me to restore thru KIES. However all it does it bootloop. I try to boot into recovery and it will tell me at the top left of the screen "booting recovery" but then just turn off and go right back to the "samsung galaxy note 3 screen" Does anything have any idea here?????
jthornton71707 said:
So after looking around all day i have found i am able to successfully flash the n900a AP, CP, and PIT files, however the problems seems to be whenever i try to flash a Bootloader file. The update gives me the error on the phone "SW REV CHECK FAIL" FUSED 3 BINARY 2. My knox counter is still 0x0. By flashing the at&t AP, PIT, and CP files the phone now boot loops and no longer takes me to the screen requesting me to restore thru KIES. However all it does it bootloop. I try to boot into recovery and it will tell me at the top left of the screen "booting recovery" but then just turn off and go right back to the "samsung galaxy note 3 screen" Does anything have any idea here?????
Click to expand...
Click to collapse
You could try to stop the boot, go back into Recovery and wipe cache, and wipe all data. I had an experience with my last device (SGSIII) that would boot loop sometimes when flashing back to a stock ROM.
Other than that, I dont have any other ideas
Just Googled the "SW REV CHECK FAIL" FUSED 3 BINARY 2", from what I found the Fused 3 means you were on Kit Kat, and Binary 2 basically means you are trying to downgrade to JB
It wont let me even boot into recovery. I hold the buttons and it boots back up saying "booting into recovery" like it is, then it just boot loops again.
jthornton71707 said:
It wont let me even boot into recovery. I hold the buttons and it boots back up saying "booting into recovery" like it is, then it just boot loops again.
Click to expand...
Click to collapse
The only other things I saw on that, suggested to users(on a different Samsung device) to use a jig to get it back into recovery. I am not familiar enough with the N3 yet to know if a jig will work on our devices. My guess is you messed up the bootloaders
Edit** I think that since things are so locked down that your best bet might be to try what jerrycoffman45 suggested a few posts ago
jerrycoffman45 said:
if you have a att note 3 you might be screwed both the firmwares you list are not for our phone your best bet would be to go to a best buy or att service center and seee if they can reflash your phone
Click to expand...
Click to collapse
My local at&t and best buy aren't very helpful for anything at all. ill keep googling ive been at this for 2 days now
There is no firmware to download for 4.4.2 yet so you are stuck till there is or do what I suggested you could also do a warranty exchange by calling att and you can't just go to any att store it has to be a service center
Sent from my SAMSUNG-SM-N900A using Tapatalk
---------- Post added at 05:40 PM ---------- Previous post was at 05:25 PM ----------
This might get you running
http://forum.xda-developers.com/showthread.php?t=2703006
Sent from my SAMSUNG-SM-N900A using Tapatalk
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
[UPDATE] .after looking around all day i have found i am able to successfully flash the n900a AP, CP, and PIT files, however the problems seems to be whenever i try to flash a Bootloader file. The update gives me the error on the phone "SW REV CHECK FAIL" FUSED 3 BINARY 2. My knox counter is still 0x0. By flashing the at&t AP, PIT, and CP files the phone now boot loops and no longer takes me to the screen requesting me to restore thru KIES. However all it does it bootloop. I try to boot into recovery and it will tell me at the top left of the screen "booting recovery" but then just turn off and go right back to the "samsung galaxy note 3 screen" Does anything have any idea here?????
Click to expand...
Click to collapse
Still need help?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
only fix I know
as far as I have searched, the only current fix to get to use your phone is
GUIDE/ROM[4/1][AT&T][NC2_Bootloader][ N900AUCECMGL KITKAT][Stuck Download-Mode FIX]
Phone stuck on "firmware upgrade encountered an issue screen please select recovery..
Hey guys I am in need of some urgent assistance and if anybody can help me solve this I am willing to send some funds via PayPal for the assistance.
When I turn on my phone I am prompted with this screen. It does not even boot into the Samsung splash screen and I cannot boot my phone into. The screen where you can do a factory reset.
Odin name (high speed)
Product name SM-N910t
CURRENT BINARY: CUSTOM
system Status:CUSTOM
reactivation lock : on
KNOX WARRANTY VOID:0*1 (4)
qualcom secure boot:Enable (cab)
RP SWREV:S1 T1, A1, A1, P1
secure download: enable
Then it says Phone stuck on "firmware upgrade encountered an issue screen please select recovery mode in kies and try again.
Now if I take the battery out I am still able to press the hold+power+volume down button to get my phone into download mode however I have tried to flash the firmware using Odin and the tmobile stock firmware as indicated in a thread here by our fellow xda developers but have had no luck.
I have also downloaded kies3 from the Samsung website and still no luck it doesn't even recognize my device.
I am dam near about to break out in tears because of this (lol) I know There's got to be someone an expert out here that can help me out. Sorry for the long post and I'm too sad to even come up with a catchy ending regarding a potato.
Please help !!!!
Have I bricked my note 4???
re: Note 4 issues
Pyr0x said:
Hey guys I am in need of some urgent assistance and if anybody can help me solve this I am willing to send some funds via PayPal for the assistance.
When I turn on my phone I am prompted with this screen. It does not even boot into the Samsung splash screen and I cannot boot my phone into. The screen where you can do a factory reset.
Odin name (high speed)
Product name SM-N910t
CURRENT BINARY: CUSTOM
system Status:CUSTOM
reactivation lock : on
KNOX WARRANTY VOID:0*1 (4)
qualcom secure boot:Enable (cab)
RP SWREV:S1 T1, A1, A1, P1
secure download: enable
Then it says Phone stuck on "firmware upgrade encountered an issue screen please select recovery mode in kies and try again.
Now if I take the battery out I am still able to press the hold+power+volume down button to get my phone into download mode however I have tried to flash the firmware using Odin and the tmobile stock firmware as indicated in a thread here by our fellow xda developers but have had no luck.
I have also downloaded kies3 from the Samsung website and still no luck it doesn't even recognize my device.
I am dam near about to break out in tears because of this (lol) I know There's got to be someone an expert out here that can help me out. Sorry for the long post and I'm too sad to even come up with a catchy ending regarding a potato.
Please help !!!!
Have I bricked my note 4???
Click to expand...
Click to collapse
Your phone is NOT bricked, a bricked phone is dead and you would see nothing on the screen,
it would remain black and you would not see the softkey leds light up either.
Have you tried going into Recovery Mode (not download mode)?
If you can get into into Recovery Mode select "factory reset" and
then select "reboot".
It should reboot normal more or less unless you formatted /system
before this happened.
Do you have stock recovery or twrp custom recovery?
If you had twrp installed it most likely means that you were also
rooted.
That means that you can flash a zip file custom rom if you have
one in your internal or external sdcard.
If you don't have a a zip file rom in internal or external sdcard then you will need to remove the
external sdcard and plug it into an adaptor which plugs into the computer so you can then copy
a zip file rom onto your external sdcard and replace it in your phone so you can flash the rom..
If you cannot boot into recovery then try removing the battery, wait 10 seconds and replace the
battery then hold down the home/power/volumeUP buttons all at the same time until you see tiny
blue text on the top left side of the screen.
Right before you see the blue writing you should also feel a little vibration from the phone.
If you can flash a zip file rom in twrp custom recovey make sure that you do a full and complete wipe including system, data,
cache, dalvik cache and last but not least do a factory reset before flashing or if you prefer restoring a nandroid backup..
If worst comes to worst and you don't have twrp recovery then you need to Odin flash twrp (the TAR version) before doing anything else.
Misterjunky said:
Your phone is NOT bricked, a bricked phone is dead and you would see nothing on the screen,
it would remain black and you would not see the softkey leds light up either.
Have you tried going into Recovery Mode (not download mode)?
If you can get into into Recovery Mode select "factory reset" and
then select "reboot".
It should reboot normal more or less unless you formatted /system
before this happened.
Do you have stock recovery or twrp custom recovery?
If you had twrp installed it most likely means that you were also
rooted.
That means that you can flash a zip file custom rom if you have
one in your internal or external sdcard.
If you don't have a a zip file rom in internal or external sdcard then you will need to remove the
external sdcard and plug it into an adaptor which plugs into the computer so you can then copy
a zip file rom onto your external sdcard and replace it in your phone so you can flash the rom..
If you cannot boot into recovery then try removing the battery, wait 10 seconds and replace the
battery then hold down the home/power/volumeUP buttons all at the same time until you see tiny
blue text on the top left side of the screen.
Right before you see the blue writing you should also feel a little vibration from the phone.
If you can flash a zip file rom in twrp custom recovey make sure that you do a full and complete wipe including system, data,
cache, dalvik cache and last but not least do a factory reset before flashing or if you prefer restoring a nandroid backup..
If worst comes to worst and you don't have twrp recovery then you need to Odin flash twrp (the TAR version) before doing anything else.
Click to expand...
Click to collapse
Thanks for your response!
I have tried that however whenever I turn on my my phone it takes me to the screen that I mentioned above automatically. I will try to enter recovery mode using Android SDK / ADB on Windows.
Forgive my ignorance but I don't believe I had any recovery installed which I now realize was HUGE Mistake, However I do know that my phone was rooted since I rooted it myself.
I am curious about "If worst comes to worst and you don't have twrp recovery then you need to Odin flash twrp (the TAR version) before doing anything else."
I feel like that is part of the steps I need to take to resolve this issue. Any tutorial links on this would be greatly appreciated.!
Thank you so much although I messed this up I am somewhat tech Savvy and it feels great to have support from other like minded individuals =)
im in the same boat as you...have you figured anything out yet?
systems6 said:
im in the same boat as you...have you figured anything out yet?
Click to expand...
Click to collapse
By any chance do you have Reactivation Lock: on?
If so that could be the cause of our issues.
I got stuck at this on my Note 3 once (with twrp custom recovery installed), turned out I had to flash the stock recovery before Odin restoring. Never figured out why it worked when download mode/Odin had not. Worth trying if you're completely out of ideas.
thefanum said:
I got stuck at this on my Note 3 once (with twrp custom recovery installed), turned out I had to flash the stock recovery before Odin restoring. Never figured out why it worked when download mode/Odin had not. Worth trying if you're completely out of ideas.
Click to expand...
Click to collapse
I will give this a try do you happen to have some kind of tutorial link on where to get this done?
I found the solution!!!!!!
OK GUYS I AM EXCITED TO SHARE MY SOLUTION WITH YOU ALL!!
What I did is flash twrp recovery with ODIN but it didnt work... it kept saying Get PIT Partition in the ODIN LOG.
So I tried flashing twrp recovery once again but this time I added the SM-N910T PIT Partition file I found online. But what I did is unchecked the Re-partition tab in ODIN thiss si what DID The trick!
The phone was able to go past the ODIN process and stopped on "RESET" in ODIN. So My Note 4 then Reset into Download mode and then this is where I reset ODIN flashed the Stock recovery for T-Mobile Note 4.
It took about 3 to 5 minutes to complete and I finally got that sweet SUCCESS on ODIn.
My phone then restarted and Voila! I have my note 4 in working condition once again!
THANKS EVERYONE FOR YOUR HELP AND I HOPE THIS HELPS YOU OUT AS WELL.
so i recently got a note 3 from a friend to fix for her. it boots to the samsung logo then vibrates and reboots over and over, recovery just says "booting recovery" then it goes blank and reboots to the same booting recovery screen, shes doesnt know what version it had prior to bricking. she said one day it was working then turned off and never back on again, the odin mode screen had a2, a3 on it ill post a pic later anyway i can get into download mode so i figured id just flash with odin and be good, i tried to narrow down the proper firmware with the a3, but after flashing nc2, nl1, oc1, im still stuck odin says everything passed, i tried flashing the big main file, tried flashing them in each box at the same time, even tried it with the pit file, tried flashing with odin 3.9 and 3.10.7. same result odin says passed still cant access recovery or os. any help would be greatly appreciated. thanks
Open Odin, uncheck everything except f reset time, flash rom. When you see reset on the statutes window, remove USB cable from the phone, remove battery, wait 5 seconds, replace battery, boot directly into recovery, perform a factory wipe, reboot.
does it matter what version i flash? since im not really sure what version it had prior?
I can't figure out how to upload a photo I have xda 4.0, and can't post outside links yet. Anyway
It says
Product name:N900A
Current binary: Samsung official
System status official
Knox void status 0x0
Qualcomm Secureboot enabled(csb)
Ap swrev s2 t2 a2 a3 p2
Secure download enable
Udc start
Hope that helps
Ran Odin again with the settings you said, after the battery pull the phone says recovery booting, then turned off vibrated twice then same screen again and again. Thanks for the suggestion though any our ideas? I was searching and thought I seen somewhere that to unbrick it it needs to be the same firmware it had before, but I don't know what that was.
ghost5825 said:
Ran Odin again with the settings you said, after the battery pull the phone says recovery booting, then turned off vibrated twice then same screen again and again. Thanks for the suggestion though any our ideas? I was searching and thought I seen somewhere that to unbrick it it needs to be the same firmware it had before, but I don't know what that was.
Click to expand...
Click to collapse
You should probably ask her if she had Lollipop. If she did then that narrows it down to OC1 or OC2.
She doesn't know, not very phone literate as far as software, any ideas? I read in another thread to flash a modified version of nc2 but can't seem to find that version, this is the thread http://forum.xda-developers.com/showthread.php?t=2703006
Don't know if I can't find it, kinda confusing as far as what I need, like I said I've tried everything except oc2 cant find a link I've tried googling, and that thread says Odin files but can't find a full one for oc2, there's ones for safestrap but can't find Odin