Database Users

[Q] [SOLVED] Stuck in download mode! - Bricked?

Hey guys!
When i boot my phone i get this error:
"firmware upgrade encountered an issue. please select recovery mode in kies and try again"
I can't flash access recovery or Android OS, and i can't flash from Odin (No PIT-partition error)
What to do???
I am almost panicking - my phone didn't work earlier today because of CWM, so i tried to flash TWRP from Odin, and now I am screwed again!!
It this fixable?
Please help me
Thanks in advance

First thing you need to do is stop panicing. That will only make things worse. If you start messing with your phone, then prepare yourself that these things happen.
Also, there is little usefull information in your thread. If you want help, I suggest you make more work of you topic. What rom were you on? What did you do with CWM? What version where you on? What version of TWRP?
Can't you just flash CWM again and then flash a custom rom? If not, then try:
1. Do you have knox enabled bootloader?
2. If so, then flash any stock rom with a knox bootloader.
3. If not, then flash a stock rom without a knox bootloader.
4. Root again and flash recovery again.
5. Flash custom rom.

re: odin flash
velein said:
Hey guys!
When i boot my phone i get this error:
"firmware upgrade encountered an issue. please select recovery mode in kies and try again"
I can't flash access recovery or Android OS, and i can't flash from Odin (No PIT-partition error)
What to do???
I am almost panicking - my phone didn't work earlier today because of CWM, so i tried to flash TWRP from Odin, and now I am screwed again!!
It this fixable?
Please help me
Thanks in advance
Click to expand...
Click to collapse
Be sure you have or get the official stock odin flash rom for your phone baseband/model
number from SamMobile.com. They only have official stock roms their with exact model
and basebands.
Make sure the battery is at least 50% charged.
Open odin and set it up so it's ready to flash.
Then remove the battery for 10 seconds & replace the battery then then hold/press the vol-down
and the power button at the same time until the phone is in download mode.
Connect the usb cable from computer to phone and then:
Be sure ODIN is ready to start, if it is then start the odin flash.
Have patience, after the flash it can take up to 4-5 minutes for
the phone to go thru the initial boot.
REMEMBER, only flash official and specific odin flash rom which is designed for
your phone's baseband and model number. Double check before flashing to be sure.
Also to avoid problems in the future, once you get your phone working properly
uninstall kies on your phone and in your computer.
Kies is really not required unless you plan to stay STOCK/UN-ROOTED and don't
plan to flash any custom roms, mod's, themes.
Good luck!

Solved it by using this guide:
http://forum.xda-developers.com/showthread.php?t=2265477
had to change to USB3.0-port before i could flash without getting an error.
Thanks for the help guys.

[Q] Unable to install CWM or TWRP on Note 3 after 4.4.2 update

So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!

There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.

It's impossibe to flash anything other than the leaked 4.4.2 stock because you flashed your bootloader to kitkat, no you MUST stay on sammy 4.4.2 till the devs found a solution for this. Thats why you have to read carefully be4 you flash.

silentvisitor said:
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
Click to expand...
Click to collapse
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?

sid8907 said:
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
Click to expand...
Click to collapse
This one seems to be the only one working with 4.4.2 right now.

Possible solution
The way I can suggest is to create a little update.zip file with little updater-script to remove install-recovery.sh file from device (just one line needed).
Ok, I found a zip which I am attaching below. You(or anyone) may review the script before flashing.
Place this on your external (or internal) sdcard.
In ODIN don't check Auto reboot
Flash Recovery. Remove phone when it says PASS.
Remove battery. Start in Recovery mode by pressing buttons.
You should now be in new Recovery.
Flash that zip file.
Reboot.
You should be good.

The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.

I am out of ideas.
I would suggest you to wait for someone to come up with working solution. Being too adventurous with ODIN could brick your device.

sid8907 said:
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
Click to expand...
Click to collapse
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again

Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?

radicalisto said:
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Click to expand...
Click to collapse
Thanks!!

sid8907 said:
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
Click to expand...
Click to collapse
You may have to do a little reading but I believe CM11 is now working on the KK bootloader...

sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398

sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
jp.26 said:
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
Click to expand...
Click to collapse
so.... yeah i just updated my bootloader to 4.4.2 and this drove me literally insane. ive been working on it for 4 hours now. i encountered so many problems with installing the bootloader. exact same problem as SID8907. i gotta tell you tho.... you worked some magic my friend. i tried almost everything. then i came across your link. i was like why not? so i flashed the img in odin..... anddddd :drumroll pleaseeeeee:: IT WORKED. ahhh....... so much frustration and the problem is solved!!! thank you so much JP.26 :good::laugh:

is there any word on how to fix this been looking for hours tmobile note beast dont want to put any roots down on my phone before i find a way to flash cm or a non bloated note rom would be nice.

I'll that I've managed is to root and flash twrp I found a way to turn cwm recovery into a tar file and flash through odin. But i just get into a boot loop with cwm due to the boot loader I presume but tarp works fine I just can't flash cm11. I get boot loop every time
Sent from my SM-N900T using XDA Premium 4 mobile app

im sorry but im confused here... does this all simply mean that there is not yet a working cwm for 4.4.2 yet? and that while we can root, there is no working recovery for this version?

I'm not sure myself tarp works but I can't flash cm11
Sent from my SM-N900T using Tapatalk

Phillz cwm Dev edition I think that's the name works its a themed touch cwm. This works great but still can't flash cm so gayyyy
Sent from my SM-N900T using Tapatalk

I was wondering what happened to the cmw too.
The modded cmw by Chenglu is the only one working that I know of.
Link to thread: http://forum.xda-developers.com/showthread.php?t=2454079

Galaxy S4 (GT-i9500) Major problem

Hello everyone. I used Albe95 N5+S6 Port rom for my GT-i9500 and it worked flawlessly. I had TWRP recovery. After a lot of using I thought to re-flash the rom and start using it new, so I reinstalled the Rom file on my external SD card and flashed the rom using TWRP recovery and it was a success, but then I noticed I accidentally backed up some things which I didn't wanted to I re-flashed the Rom again, but this time when I (in recovery mode) wiped the data, I chose "Advanced Wipe" or "Advanced Reset" (It was something like that I don't exactly remember. So after that I reflashed the rom and when I had to press "Reboot" a message appeared above saying "Looks like super user is not installed in your phone. Do you wish to install it?" I said Yes and the screen went blank. I tried to reboot but It didn't. I removed the battery and then put it back again and tried to get into recovvery but recovery seemed to be lost and I ended up in Samsung's own factory mode where we have options like reboot, flash using external sd card, flash using adb, enable cp logging and etc. I tried to flash back everything but nothing works. Tried Odin and tried flashing custom firmware but it fails. If I reboot Samsung Galaxy S4 GT-i9500 comes on screen and then it goes blank no boot animation or anything like that. Please help me, Your help will be highly appreciated

I used advanced wipe many times before, I'm pretty sure something else caused your dilema.
And most Odin fail messages are caused by the USB cable, PC USB ports (back ports are recommended) and Windows version.

So what should I do now?

If the problems are caused by the above mentioned, you should obviously try to change things up.

It appears that your phone is in soft-brick.
Also, you lost your TWRP.
Check your bootloader version and install the stock firmware via odin. (If you still fail in odin, As GDreaper pointed out, odin fail could cause by usb cable, port and windows version so you need to keep changing until it works)
Root the phone. Reinstall the TWRP.
Then flash the custom rom again. When you install the custom rom please follow the cooker (custom rom maker) instructions on wiping.

Thanks for your comment. I'm kind of a noob, how do I check bootloader version? and how will I know after checking my bootloader version which stock firmware to install?

Bootloader has nothing to do with it.
If you flash a stock firmware, the Bootloader will also be updated to whatever Bootloader the download firmware has.
The only situation where the Bootloader would matter is if you try to go from lollipop to kitkat, in which case it will fail.

Thank you. My device is back now.

I am glad to hear that your problem is solved.
When I was on kit-kat, I did not check my bootloader version and flash the stock firmware with older version of bootloader which tripped the knox counter on my i 9500. That was why I said to check the bootloader version before installing the stock firmware. You can use app like phone info to see the bootloader info. Then install the firmware with the same or newer bootloader.

I recomend to Update drivers, Windows, Bootloader install Samsung Kies and Install TWRP again, After stock

Might have Bricked S7 Edge SM-935FD. Need Help to recover

Hello guys
My phone is Galaxy S7 Edge Duos- SM935FD. I seem to have bricked the device.
Below are the actions I have performed.
1. Flashed TWRP using ODIN as described on https://www.the***********.com/root-samsung-galaxy-s7-edge/
2. Booted successfully into the OS. Found superuser app installed.
3. When I went to back to Flash ROM i erased multiple things such as internal storage/dalvik/cache/system after which device got stuck in bootloop. Showing NO OS.
4. I tried flasing Custom ROM Zip files through OTG. The process failed showing package corrupt and still stuck in bootloop.
I can enter recovery/download mode however cant seem to get the device booted. How can I get the device to work either Custom or stock ROM.
I will be going through some threads in the meantime, your guidance is very much appreciated.

Flash stock rom with Odin: This shouldnt be posted on Development Forum but rayher questions and Answers.
Find what your Stock Firmware for your phone is using Sammobile and flash stock then re do rooting and TWRP Process

zzThrain is right -- I wouldn't risk flashing custom ROMs at this stage, especially because many contain new bootloaders or other stuff that might make this even worse for you. Just pick up the relevant Samsung stock ROM file (from, for example, SamMobile) and see if it boots normally again. Once it does, re-do the process *after checking all MD5s of the files you used* -- I, too, have had it happen before that a download went corrupted and I flashed it. If all is well, get into Download Mode and let Odin rip.

rixon.d9 said:
Hello guys
My phone is Galaxy S7 Edge Duos- SM935FD. I seem to have bricked the device.
Below are the actions I have performed.
1. Flashed TWRP using ODIN as described on https://www.the***********.com/root-samsung-galaxy-s7-edge/
2. Booted successfully into the OS. Found superuser app installed.
3. When I went to back to Flash ROM i erased multiple things such as internal storage/dalvik/cache/system after which device got stuck in bootloop. Showing NO OS.
4. I tried flasing Custom ROM Zip files through OTG. The process failed showing package corrupt and still stuck in bootloop.
I can enter recovery/download mode however cant seem to get the device booted. How can I get the device to work either Custom or stock ROM.
I will be going through some threads in the meantime, your guidance is very much appreciated.
Click to expand...
Click to collapse
Go to recovery mode & transfer rom to phone using pc. wipe cache, delvikcache, data only. No need to wipe internal sd. Install rom & reboot.
if you phone goes to recovery or download mode, no need to worry. If it doesn't go to neither recovery nor download mode, them your phone might have probably bricked.

It's my pleasure to help you if you still facing this problem

zzThrain said:
Flash stock rom with Odin: This shouldnt be posted on Development Forum but rayher questions and Answers.
Find what your Stock Firmware for your phone is using Sammobile and flash stock then re do rooting and TWRP Process
Click to expand...
Click to collapse
Hi
I tried flashing stock rom from sammobile. I could find for SM-935FD hence downloaded SM-935F.
It got stuck at 90% showing System in ODIN.
From the ZIP file which is the file that needs to be flashed among below ? I tried AP.
AP_G935FXXU2DRB6_CL12365438_QB16944063_REV00_user_low_ship_meta.tar
BL_G935FXXU2DRB6_CL12365438_QB16944063_REV00_user_low_ship.tar
CP_G935FXXU2DRAG_CL648265_QB8691891_SIGNED.tar
CSC_OJV_G935FOJV2DRAG_CL12785220_QB16560277_REV00_user_low_ship.tar
HOME_CSC_OJV_G935FOJV2DRAG_CL12785220_QB16560277_REV00_user_low_ship.tar
Now when I try again it immediately shows FAIL. Am i Flashing the right stock rom ?

It Worked. Thanks to all who helped.
I wasn't running ODIN as Admin and also was using an slightly older version V3.10.7.

Need help unbricking.

Yesterday I tried root my S8 (SM-G950FD) and I made the mistake of not allowing system modifications before flashing because I misinterpreted a guide. I flashed the no-verity zip and Magisk. The phone booted successfully and magisk was installed. Then I went to reboot into recovery to change some TWRP settings IE: Brightness. Then my phone said "Only officially released binaries are allowed to be flashed." That left me unable to boot my phone and also made it unable to boot into recovery. The only thing I can boot my phone into is download mode. I've tried flashing some stock roms that are 7.0 to remove the prenormal lock but they failed. I happened to make a TWRP backup before flashing but I can't use TWRP because of the official binary stuff. I'm wondering if I use the nand erase all option if that will let me flash the 7.0 stock roms then boot into TWRP and restore my backup or if they is way to convert the backup into something that Odin can flash. Does anybody know any confirmed methods to solve my problem?

Unbrick-me said:
Yesterday I tried root my S8 (SM-G950FD) and I made the mistake of not allowing system modifications before flashing because I misinterpreted a guide. I flashed the no-verity zip and Magisk. The phone booted successfully and magisk was installed. Then I went to reboot into recovery to change some TWRP settings IE: Brightness. Then my phone said "Only officially released binaries are allowed to be flashed." That left me unable to boot my phone and also made it unable to boot into recovery. The only thing I can boot my phone into is download mode. I've tried flashing some stock roms that are 7.0 to remove the prenormal lock but they failed. I happened to make a TWRP backup before flashing but I can't use TWRP because of the official binary stuff. I'm wondering if I use the nand erase all option if that will let me flash the 7.0 stock roms then boot into TWRP and restore my backup or if they is way to convert the backup into something that Odin can flash. Does anybody know any confirmed methods to solve my problem?
Click to expand...
Click to collapse
You will need to flash the same or higher version of Android to fix official binary error. Use default settings in Odin.
You cannot.flash earlier versions of Android if your bootloader is lower than what is on your phone ( 5th number from right of firmware name ). If in doubt flash the latest version.

Then I went to reboot
Click to expand...
Click to collapse
And i same problems "Only officially released binaries are allowed to be flashed"
---------- Post added at 10:31 PM ---------- Previous post was at 10:30 PM ----------
Then I went to reboot
Click to expand...
Click to collapse
And i same problems "Only officially released binaries are allowed to be flashed"

spawnlives said:
You will need to flash the same or higher version of Android to fix official binary error. Use default settings in Odin.
You cannot.flash earlier versions of Android if your bootloader is lower than what is on your phone ( 5th number from right of firmware name ). If in doubt flash the latest version.
Click to expand...
Click to collapse
Ok so in few minutes from now the rom will be finished downloading. When that is done what version of Odin should I use and what files should place in Odin. I know this may seem stupid to ask but I'm not going to let myself make anymore stupid decisions after not installing the rmm bypass.

Quick Update, the rom finished downloading. I wasn't able to flash it. It gave me the error that the Bootloader had: 4 and the binary had 3... I was able to flash cp by itself tho and that set the system status to samsung official but the binary status is still custom. That made it so my phone only booted into a "Update failed screen use smart switch" screen ( I've tried smart switch before it doesn't detect my device). I can still get it back into recovery and flash old cps to get it to turn off without bootlooping into the smart switch screen. I'm wondering if I flash csc to factory reset if that will help at all. Guys what do I do??

Excuse my language but I ****ING DID IT!!! I don't know this worked but I am going to roughly call my process. So flashing the stock rom initially failed. I flashed then CP which for some reason always works and then AP which began but failed. This set the binary text to "Samsung Official", system status was still ****ed as custom. So I restored the cp and ap(?) from the crgb oreo files posted here. Then I flashed cp that passed, then csc which passed and then tried AP. After some time... It passed. The phone rebooted. The official binary bull**** was gone from the bootscreen and the phone booted into recovery. It installed some sys update stuff up to 30$ then erased some things which took awhile. Then the phone booted into initial setup and I now have ACCESS TO MY PHONE AGAIN!!!
For anyone interested in what FW I flashed PM me.