Related
Cannot boot into download or recovery mode
Hi, my samsung Tab2 is stuck at the "Firmware upgrade encountered an error" screen. No matter which combination of buttons I press, I cant get into download or recovery. I've tried flashing with Odin, it shows successful but nothing has changed. I tried the ADB command but it says "Waiting for device". When I plug in the tab to the charger (or when I connect it to the PC) it comes on automatically with the "Firmware upgrade encountered an error" screen. Is it a power button thing or is it something else ?
Thanks.
Sachin
Flash the CWM recovery via Odin, and restart. now you can go to the recovery mode and install ROM from sd card.
Dont try to flash any other recovery file, working with CWM only.
Hi,
Thanks for the reply. Unfortunately, I've already tried that, Odin shows it is successful but when i restart, nothing seems to have changed, the same upgrade error comes back.
sachin
Hi,
I have this old Galaxy Ace Plus phone which doesn't boot. It had an old SlimRom on it and I installed the stock firmware over it by odin.
The phone starts boots to the 'SAMSUNG' logo that appears in the middle of the screen just before the homepage screen and vibrates sort of 'prrrr prrrr prr prr prr' and reboots and the same thing continuously.
Since then it won't boot and won't even go to recovery mode. When I press the recovery mode combo it does nothing 'black blank screen and no sound or vibration activity as if the phone is switched off completely'.
As per a few threads I saw to fix the bootloop you need to go to recovery and flash a file but because I can't go to recovery I am stuck.
However I can go to the download mode.
Here is what I have tried so far..
Re-downloaded and reinstalled the stock firmware
Tried to flash different recovery's.
Tried different ODIN versions (all say passed/OK)
Reboot manually after odin flash directly to recovery mode
Played with battery and some buttons
Tried different location stock firmwares
Nothing so far..
Is there anything else I can try ?
Thanks.
have you tried with the last firmware for ace plus ??
zyxw-androidiani said:
have you tried with the last firmware for ace plus ??
Click to expand...
Click to collapse
Thanks for the reply.
All the Ace plus firmwares on sammobile are 2.3.6
I have tried of a few regions but all are failing at the same boot loop.
hmm.. have you tried to flash TWRP ??
ps: are you sure that you can't go on recovery ? the combo is volume - volume + home button + power button (on/off) and when you will see the logo "samsung" you must leave the power button but don't leave the other.
Yes i have tried the correct combo. However i will search and try to flash twrp.
Will let you know.
Thanks.
Sent from my GT-I9500 using XDA Free mobile app
https://www.dropbox.com/s/iqiqs14g2ei6skx/twrp-build-3-06052013-trebon.tar.md5?dl=0 try to flash this twrp via odin
Do you use Odin 1.85 or another version?
zyxw-androidiani said:
https://www.dropbox.com/s/iqiqs14g2ei6skx/twrp-build-3-06052013-trebon.tar.md5?dl=0 try to flash this twrp via odin
Do you use Odin 1.85 or another version?
Click to expand...
Click to collapse
Thanks for the link, I have flashed it and it says RES OK and green color so I assume its fine. However the phone doesn't accept my recovery button combo ( Vol-Up + Vol-Down + Power + Home ). I think its scrap now.
Yes, I use Odin 1.85
maybe you have got a problem with one of button ?
zyxw-androidiani said:
maybe you have got a problem with one of button ?
Click to expand...
Click to collapse
I think so....I had the same problem some days ago....and I think it's an hardware problem (the power button)
You can also try to connect the phone on the pc via usb and try with adb commands
-write on cmd (terminal) adb shell and if you get
* daemon not running. starting it now on port 5037 * ( the port number maybe can change)
* daemon started successfully *
-now write adb reboot recovery and the phone must reboot into recovery
When i use my mo it ll reboot
sorry, but what do you mean with mo ?
I was trying a new ROM after installing mobile odin (pro) and superSu. However after failed installation the tab is restarting in recovery mode only ( screen shot attached). It is neither detected by odin nor can I install any apk as it is not booting further. I have wiped all data and caches and also have the recovery image (cwm and one supplied by mobile odin) but both are showing signature verification failed due to stock <3e>. So if somehow I can bypass the signature verification , I can load the backup. In short--
1. Tab not detected in PC ( via ODIN) , which was perfectly detected earlier. So no method via PC possible.
2. Tab not going beyond recovery mode, so no APK installation is possible.
3. It can read from SD card in recovery mode , but every image ( I know they are good, as used them earlier) is showing " Signature verification failed" and aborting.
4. I have a working CWM image but cannot install it due to reason 3 ( probably <3e> is the culprit).
I have searched the forum as far as I could but found all solutions are either PC based or APK based.
When you are in recovery, is the tab detected via adb from pc?
bukaida said:
I was trying a new ROM after installing mobile odin (pro) and superSu. However after failed installation the tab is restarting in recovery mode only ( screen shot attached). It is neither detected by odin nor can I install any apk as it is not booting further. I have wiped all data and caches and also have the recovery image (cwm and one supplied by mobile odin) but both are showing signature verification failed due to stock <3e>. So if somehow I can bypass the signature verification , I can load the backup. In short--
1. Tab not detected in PC ( via ODIN) , which was perfectly detected earlier. So no method via PC possible.
2. Tab not going beyond recovery mode, so no APK installation is possible.
3. It can read from SD card in recovery mode , but every image ( I know they are good, as used them earlier) is showing " Signature verification failed" and aborting.
4. I have a working CWM image but cannot install it due to reason 3 ( probably <3e> is the culprit).
I have searched the forum as far as I could but found all solutions are either PC based or APK based.
Click to expand...
Click to collapse
Signature verification fails because you are on stock recovery. Also have you tried booting in to download mode then plugging the USB cable to your tablet, then pressing volume up to start the download mode, then plugging the other end to your PC while odin is running? It should get detected
Power+ Vol up and Power + Vol down both are going to recovery mode. Plus getting an error 'logo_espresso7.jpg' draw failed at initial screen. Is there any <3e> compatable recovery without signature verification failed that can be run from sd card directly?
Ps: This happened when I tried to install "crdroid-5.1.1-20151103-p3110" via mobile ODIN pro.
The Tab is not detected in ADB server either.
bukaida said:
Ps: This happened when I tried to install "crdroid-5.1.1-20151103-p3110" via mobile ODIN pro.
Click to expand...
Click to collapse
The rom was meant to be installed with twrp or other custom recovery and not via mobile odin.
john99ap said:
The rom was meant to be installed with twrp or other custom recovery and not via mobile odin.
Click to expand...
Click to collapse
Yeah, the fault is mine, lack of knowledge. But what now? Can I recover my Tab ?
please help.
[Solved Problem]
The problem is solved. I finally could figure out that the culprit was the external volume down key ( not letting me go to download mode). So I opened the back cover as the last option and press the soft points corresponding to volume down and power together with two tooth-peaks. And voila , it issued the warning screen, and pressed up and it went to download mode. Connected with odin, flashed and load cwm recovery . Now that <3e> kernel is also gone.
Ps. It was weird about the Vol key behavior as it was working fine in both side in recovery mode during selection.
bukaida said:
The problem is solved. I finally could figure out that the culprit was the external volume down key ( not letting me go to download mode). So I opened the back cover as the last option and press the soft points corresponding to volume down and power together with two tooth-peaks. And voila , it issued the warning screen, and pressed up and it went to download mode. Connected with odin, flashed and load cwm recovery . Now that <3e> kernel is also gone.
Ps. It was weird about the Vol key behavior as it was working fine in both side in recovery mode during selection.
Click to expand...
Click to collapse
if you want to install the latest roms, you should update to the latest common twrp from android-andi http://andi34.github.io/recoveries_tab2.html
cwm recovery is outdated and causing issues with the latest roms
Is twrp safe to run from mobile odin? Will it automatically overwrite installed cwm?
bukaida said:
Is twrp safe to run from mobile odin? Will it automatically overwrite installed cwm?
Click to expand...
Click to collapse
install twrp as zip with your current cwm. its the easiest way. twrp will replace cwm, yes.
Hi,
I have S8 Plus SM-G955F in Germany.
Dont knwo what exactly happend, but my phone was just still running fine (bootloader is unlocked) and I rebooted but then was stuck at "Installing system updates" screen which appear before getting into recovery. However, it does not enter into recovery and reboots after few seconds into "installing updates" mode which then fails.
It does not boot up into Android.
All I can access to is Download Mode.
I flashed "BL_G955FXXU1AQF7_CL11544126_QB13847503_REV00_user_low_ship.tar" Bootloader and rebooted and now it is stuck in Samsung boot logo. If I press Vol up + Bixpy Button + Power nothing happends, it does not even start to load Recovery mode.
I now downloaded following stock firmware through SamFirm: "SM-G955F_1_20171214140840_hlcm4r582t_fac.zip.enc4" (3332 MB)
but when trying to flash it in odin I get FAILED !!! Also if I try to flash TWRP recovery "twrp-3.1.0-1-dream2lte.img" I get FAILED in Odin I now also tried to flash "AP_G955FXXU1AQH3_CL12050265_QB14545623_REV00" firmware using this tutorial: https://www.youtube.com/watch?v=2y0ZZxcNVnE which also FAILED. I think I am completely bricked !!
Please help, phone is completeley useless now
Thanks!
tobyffm said:
SM-G955F_1_20171214140840_hlcm4r582t_fac.zip.enc4" (3332 MB)
Click to expand...
Click to collapse
I had the same problem with downloading stock firmware. My problem was that I couldn't download from SamMobile because of server maintenance. So I downloaded from here. An with this tool there's the option to decrypt the file automatically. I forgot to tick this option and had a .enc4-file like you have there. The problem could decrypt this file and then I could unzip it and use it with odin.
So that's your problem: you are trying to use an encrypted file. But you have to use an decrypted file.
Maltonator said:
I had the same problem with downloading stock firmware. My problem was that I couldn't download from SamMobile because of server maintenance. So I downloaded from here. An with this tool there's the option to decrypt the file automatically. I forgot to tick this option and had a .enc4-file like you have there. The problem could decrypt this file and then I could unzip it and use it with odin.
So that's your problem: you are trying to use an encrypted file. But you have to use an decrypted file.
Click to expand...
Click to collapse
Hi,
thank you! But its actually not my problem. Samfirm decrypted and I got the zip with the BL, AP, CSC, CP files in it. But ODIN fails everytime anyway and I have no idea what I could still do now.
tobyffm said:
Hi,
thank you! But its actually not my problem. Samfirm decrypted and I got the zip with the BL, AP, CSC, CP files in it. But ODIN fails everytime anyway and I have no idea what I could still do now.
Click to expand...
Click to collapse
But you flashed all four files at the same run together?
Maltonator said:
But you flashed all four files at the same run together?
Click to expand...
Click to collapse
Yes, like the howto video described.
tobyffm said:
Dont knwo what exactly happend, but my phone was just still running fine (bootloader is unlocked) and I rebooted but then was stuck at "Installing system updates" screen which appear before getting into recovery.
Click to expand...
Click to collapse
But this happens with my phone to if I press volume up.
tobyffm said:
If I press Vol up + Bixpy Button + Power nothing happends, it does not even start to load Recovery mode.
Click to expand...
Click to collapse
But you have to press Vol down
Maltonator said:
But this happens with my phone to if I press volume up.
But you have to press Vol down
Click to expand...
Click to collapse
Usual behaviour was this: Vol up, bixpy and Power -> Recovery mode which fist starts with "Installing update..." then failed and then it goes into some black recovery mode where you can choose Apply update.zip etc. right? However, in my case this black screen with more commands did not show up, before it was rebooting again by itself.
Now I cannot even get into this "installing updates" mode before recovery, because "Vol up, bixpy and Power" does not bring any action.
Vol down, Bixpy and Power still works and brings me to Download Mode. But it doesnt help me, because once I tr to flash any firmware in Download Mode, it FAILS in Odin, so I am completely stuck, hope you understand
tobyffm said:
Usual behaviour was this: Vol up, bixpy and Power -> Recovery mode which fist starts with "Installing update..." then failed and then it goes into some black recovery mode where you can choose Apply update.zip etc. right? However, in my case this black screen with more commands did not show up, before it was rebooting again by itself.
Now I cannot even get into this "installing updates" mode before recovery, because "Vol up, bixpy and Power" does not bring any action.
Click to expand...
Click to collapse
But why do you boot in recovery mode?
tobyffm said:
Vol down, Bixpy and Power still works and brings me to Download Mode. But it doesnt help me, because once I tr to flash any firmware in Download Mode, it FAILS in Odin, so I am completely stuck, hope you understand
Click to expand...
Click to collapse
Download mode is the only mode you need for restoring stock firmware.
Try this guide. (Spoiler "Flashing Standard Firmware:")
Yesterday I did it with this one too and it worked flawlessly. But I used Odin v3.12.3 not as said in the guide V3.12.7.
Maltonator said:
But why do you boot in recovery mode?
Download mode is the only mode you need for restoring stock firmware.
Try this guide. (Spoiler "Flashing Standard Firmware:")
Yesterday I did it with this one too and it worked flawlessly. But I used Odin v3.12.3 not as said in the guide V3.12.7.
Click to expand...
Click to collapse
it automatically loaded into recovery before, I was not able to boot into Android, it loaded recovery (but without black screen with more commands) automatically by default and rebooted, loaded recovery again and rebooted, loaded recovery againd and rebooted etc...all I could to to interrupt this was loading download mode.
However, thanks for the link, but it does describe what I did already. And yes, I also used Odin 3.12.3 already because in the video tutorial I linked some posts before they said also, I need to use that version.
However, it simply does not work. Odin FAILS everytime
I am not doing anything wrong, I am sure. The only thing could be that the Firmware I downloaded is still wrong, even I cannot imagine this.
tobyffm said:
I am not doing anything wrong, I am sure. The only thing could be that the Firmware I downloaded is still wrong, even I cannot imagine this.
Click to expand...
Click to collapse
Yes that's the only thing that comes on my mind too if you think everything else is right. Download another firmware file maybe from a different provider than SamMobile.
Or try using different USB-Port, USB-Cable and/or different PC.
Maltonator said:
Yes that's the only thing that comes on my mind too if you think everything else is right. Download another firmware file maybe from a different provider than SamMobile.
Or try using different USB-Port, USB-Cable and/or different PC.
Click to expand...
Click to collapse
Did already, did not help. I think maybe there is something realldy bricked, so flashing stock firmware wont be possible at all anymore?! Is this possible somehow?
btw: Just managed to load into TWRP, randomly it does load twrp, dont know how, because if I press the keys for loading into recovery, it actually does not do anything, but currently I see twrp.
Is see anything I can try from there? btw: formated data (incl. internal storage) earlier already, but it did not change anything.
But any idea what I can try to flash from TWRP maybe? Is there a way to flash stock firmware from TWRP somehow?
I found a backup in twrp, I am currently trying to restore it...
tobyffm said:
But any idea what I can try to flash from TWRP maybe? Is there a way to flash stock firmware from TWRP somehow?
I found a backup in twrp, I am currently trying to restore it...
Click to expand...
Click to collapse
Google found this. But I don't know if this works. I only flashed custom ROMs via TWRP. Stock ROMs always via Odin.
Maltonator said:
Google found this. But I don't know if this works. I only flashed custom ROMs via TWRP. Stock ROMs always via Odin.
Click to expand...
Click to collapse
Puuuuh, I was able to fix phone with hat TWRP backup I found!
Thanks for your efforts anyway, much appreciated!
tobyffm said:
Puuuuh, I was able to fix phone with hat TWRP backup I found!
Thanks for your efforts anyway, much appreciated!
Click to expand...
Click to collapse
Glad it worked! :good:
tobyffm said:
it automatically loaded into recovery before, I was not able to boot into Android, it loaded recovery (but without black screen with more commands) automatically by default and rebooted, loaded recovery again and rebooted, loaded recovery againd and rebooted etc...all I could to to interrupt this was loading download mode.
However, thanks for the link, but it does describe what I did already. And yes, I also used Odin 3.12.3 already because in the video tutorial I linked some posts before they said also, I need to use that version.
However, it simply does not work. Odin FAILS everytime
I am not doing anything wrong, I am sure. The only thing could be that the Firmware I downloaded is still wrong, even I cannot imagine this.
Click to expand...
Click to collapse
My mistake, sorry - I posted in the wrong place- sorry. (I do hope you find a way to get t his fixed) good luck
I just ran into this thread: https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
It looks like you're not the only one...
You know, you might want to try and remove the more current apps you installed and see if that is causing the loop, and if that does not work, just dirty flash over what you have. For me, a lot of time a dirty flash will solve the issue, as it overwrites the OEM software, and in that manner, takes my phone OS back to normal/new state, while leaving my data.
I'm on a G900W8 with the latest software update and I just tried to install the latest TWRP through Odin using download mode (vol up, home and power) and while it seemed like it worked it didn't actually and now I cannot get into download mode whatsoever. It just says "installing system update" which fails after a few seconds and sends me to "no command" screen.
If I hit vol up and power to get into the next menu it says
Code:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API:3
# MANUAL MODE v1.0.0#
Successfully verified dmverity hash tree
E:Failed to clear BCB message: failed to find /misc partition
The phone boots and I can use adb commands to "apply update from ADB" in the recovery menu but I can't figure out how I can use this to fix anything. I have tried factory reset which worked but it did not fix my issue I still cannot access download mode or figure out any way to install TWRP or even get my regular recovery working again..
Does Odin still detect it when it reaches the no command screen? I had the same thing happen to a Samsung tablet but Odin still detected it after the 'installing system update' message and I was able to do a stock firmware flash.
Beanvee7 said:
Does Odin still detect it when it reaches the no command screen? I had the same thing happen to a Samsung tablet but Odin still detected it after the 'installing system update' message and I was able to do a stock firmware flash.
Click to expand...
Click to collapse
No it doesn't unfortunately my PC recognizes it but it says the device has malfunctioned and is not recognized. If I boot it up Odin will recognize it fine but I cannot install anything that way since the actual system is running at that point.
Try to find and flash popper combination rom
maybe this site help https://www.mobileheadlines.net/samsung-galaxy-s7-combination-rom/
I have same problem like you
I flash combination rom
lets its boot up
go do download mode again
and flash proper firmware
jaqjacek said:
Try to find and flash popper combination rom
maybe this site help https://www.mobileheadlines.net/samsung-galaxy-s7-combination-rom/
I have same problem like you
I flash combination rom
lets its boot up
go do download mode again
and flash proper firmware
Click to expand...
Click to collapse
OK but how do you flash that without being able to use Odin in download mode?
On my S7 to go to download mode is combination Vol Down + home + power.
Vol up is for recovery
jaqjacek said:
On my S7 to go to download mode is combination Vol Down + home + power.
Vol up is for recovery
Click to expand...
Click to collapse
Oh man I'm an idiot lol. I'll try this tonight... Thanks
Similar problm
Cordtus said:
I'm on a G900W8 with the latest software update and I just tried to install the latest TWRP through Odin using download mode (vol up, home and power) and while it seemed like it worked it didn't actually and now I cannot get into download mode whatsoever. It just says "installing system update" which fails after a few seconds and sends me to "no command" screen.
If I hit vol up and power to get into the next menu it says
Code:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
Block-Based OTA
Supported API:3
# MANUAL MODE v1.0.0#
Similar problem but upto Block-based OTA showing ..
Click to expand...
Click to collapse
Similar problem but upto Block-based OTA showing i flashed stock formware after factory reset still showing above problem my device if galaxy j4 sm-j400f
And also when i boot it stuck on samsung logo for long time..