I had stock rom installed when I was facing "cant connect to camera issue", which itself was a hardware issue-solved by changing the camera in service center. Now, when I wanted to update my phone to cm13 or lineage or even to install supersu and twrp, I'm unable to do so with error, "signature verification failed". My device is not rooted, getting detected in adb, fastboot mode. Tried installing cwm/twrp recovery in fastboot mode but my phone restarts again with stock recovery not with twrp or cwm. A thread said I should restart phone from fastboot directly into recovery..when I tried the same with vol up+ vol down + power button, yu followed by a blank screen appears and nothing happens. I searched various posts from xda, but cant seem to find a solution. Hope one of you guys could help me out. Thanks.
Related
i have unlock root, and install cmw with my a701. first i tried CyanogenMod, after that Evil Purgatory ROM...
after that i tried to back to stock rom. after several day struggling in "assert failed: getprop("ro.product.device")", finally i can pass the error...
but after i run the update.zip, they ask me about flash recovery (i answer yes), and rood device (i answer no), after reboot, the device stuck in iconia tab logo, (after acer, animation, then iconia tab logo). after the i tried to run the recovery, but it always stuck in "recovery verified failed..."
i have no idea how to enter fastboot or adb.
there's nothing i can do to the device right now...
any idea how to enter fastboot or adb, or fix my a701?
please help me, i already search all around xda, cannot find the solution, every solution need to enter adb mode or fastboot mode...
I have the exact same problem now. Has anyone found a solution to this?
Many thanks
EDIT: FIXED! For anyone experiencing a similar problem, I managed to recover mine by powering on, holding Volume + (one dot) and repeatedly switching the rotation lock switch. This gave the messaging wiping user data, and wiping cache, and it rebooted as it should! Good luck.
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
So I received my Yuphoria about a week ago. Decided to attempt rooting, unlocked the bootloader but I cannot seem to get a custom recovery to run on it, be it CWM or TWRP.
When I try to hotboot the image in fastboot mode, as soon as I enter the fastboot boot recovery command, my PC loses connection to the phone and a message pops up saying "USB device not recognised".
When I try to flash the recovery images, it is always successful. However, when I boot into the recovery, it always loads up the stock recovery, which is strange since the flash was successful.
Any solutions to this problem?
EDIT 1: Tried it with multiple PCs. Same problem for each one.
tirtha2shredder said:
So I received my Yuphoria about a week ago. Decided to attempt rooting, unlocked the bootloader but I cannot seem to get a custom recovery to run on it, be it CWM or TWRP.
When I try to hotboot the image in fastboot mode, as soon as I enter the fastboot boot recovery command, my PC loses connection to the phone and a message pops up saying "USB device not recognised".
When I try to flash the recovery images, it is always successful. However, when I boot into the recovery, it always loads up the stock recovery, which is strange since the flash was successful.
Any solutions to this problem?
EDIT 1: Tried it with multiple PCs. Same problem for each one.
Click to expand...
Click to collapse
its not strange. its the way it works. after flashing custom recovery DO NOT REBOOT THROUGH FASTBOOT. just pull out the usb cord. remove and reinsert the battery and then press the volume down and power button together. You will boot into recovery. I will recommend twrp.
enrique_fire said:
its not strange. its the way it works. after flashing custom recovery DO NOT REBOOT THROUGH FASTBOOT. just pull out the usb cord. remove and reinsert the battery and then press the volume down and power button together. You will boot into recovery. I will recommend twrp.
Click to expand...
Click to collapse
Thank you! that worked perfect!
Hi which method did you use to root yu50101a? if possible can you share a link as well
:crying:I am also facing the same problem . i also have yu5010a but cannot root it . twrp or cwm not correctly flashing.just tell me if anyone have any solution .
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.
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..