I just got this new Verizon Z2 tablet and it won't update from android kitkat. It always says "Error during DM session" any known solutions to this?
If you have Verizon and a compatible sim it will update. I suppose you could flash the image with flash tool.
Related
Hi,
I believe my nexus 5x is "soft bricked" or in a "boot loop" (sorry newb here). The phone will restart and turn off during the boot animation. I am able to get into recovery mode and have attempted to use adb sideload to apply the latest 7.1.1 OTA zip from google's website. During that process (50% through) it said I could not update it because I needed to load a current or newer version. I realized I am on beta 7.1.1 NPF26F but am unable to locate the OTA zip for this.. I did download one online (seemed legit) but got an error E: signature verification failed, E: error 21. At this point I am a bit lost and unsure what to do.. any help would be appreciated.
Mike
Is your bootloader unlocked? If so, then just install the whole system update, not just the OTA. This will get your off of the beta and onto the official update as well.
es0tericcha0s said:
Is your bootloader unlocked? If so, then just install the whole system update, not just the OTA. This will get your off of the beta and onto the official update as well.
Click to expand...
Click to collapse
I do not believe my bootloader is unlocked. I tried to go through the " fastboot oem unlock " steps today but I need to turn on USB debugging on the device (which I cannot do) to even have that option. Will I need to wait until the OTA.zip is released or is there another way ?
http://storage.googleapis.com/andro.../preview/bullhead-npf26f-factory-0e9ab286.zip
is this the factory image or the OTA?.. guessing by the size its the factory image. I am unaware how to flash this if my USB debugging is LOCKED. Please help
I have a Chinese version MI Box. Model: MDZ-09-AA (AK). And I want to flash with US version firmware. I downloaded the rom and booted into recovery mode and when update, it showed me an error message with "signature verification failed". Then I tried to root it via RootKing, but after multiple tries, I still can't manage to install it successfully - it just ended with installation failure message. Am I missing anything here? Can someone give some pointers? Thx
The rom I used: http://en.miui.com/thread-323779-1-1.html
Can someone help?
http://miui.vn/forum/threads/cai-dat-firmware-global-cho-mi-box-3s-mdz-19-aa.50835/
Hi Guys,
samsung/gts311texx/gts3llte
8.0.0/R16NW/T825XXU2BRL2
really struggling with my TabS3 which is about 1.5years old. Had sent it to Samsung for repair but they sent it back without repairing the problem.
was fine until a few weeks ago the battery had died within a few hours of charging. I charged again and noticed it was just bootlooping but was occasionally giving a blue screen error saying no command then in recovery was showing failed to verify diverity hash tree
It hasnt been possible to get into android to enable OEM unlock due to bootlooping issues
was running stock firmware and not rooted
I tried to reinstall stock firmware from samfirmware via Odin but was just giving an error when flashing AP
now when booting its giving " an error has ocurred while updating the device software. use the emergency recovery function in the smart switch pc software"
in recovery giving error dm-verity verification failed... E:failed to mount system (invalid argument)
any ideas? £20 reward if helps get it sorted!
NI3K said:
Hi Guys,
samsung/gts311texx/gts3llte
8.0.0/R16NW/T825XXU2BRL2
really struggling with my TabS3 which is about 1.5years old. Had sent it to Samsung for repair but they sent it back without repairing the problem.
was fine until a few weeks ago the battery had died within a few hours of charging. I charged again and noticed it was just bootlooping but was occasionally giving a blue screen error saying no command then in recovery was showing failed to verify diverity hash tree
It hasnt been possible to get into android to enable OEM unlock due to bootlooping issues
was running stock firmware and not rooted
I tried to reinstall stock firmware from samfirmware via Odin but was just giving an error when flashing AP
now when booting its giving " an error has ocurred while updating the device software. use the emergency recovery function in the smart switch pc software"
in recovery giving error dm-verity verification failed... E:failed to mount system (invalid argument)
any ideas? £20 reward if helps get it sorted!
Click to expand...
Click to collapse
Just a couple of thoughts. Do you know what error you were getting in Odin? Are you using the latest version of odin, 3.13, and try downloading the stock firmware from updato.
Sent from my [device_name] using XDA-Developers Legacy app
using odin 3.13, when trying to flash its showing no errors in odin just FAIL! (Auth) and tablet screen showing secure check fail: aboot [1]eMMC write fail: aboot
Internal memory issue maybe? tried a version from updato, similar story
NI3K said:
using odin 3.13, when trying to flash its showing no errors in odin just FAIL! (Auth) and tablet screen showing secure check fail: aboot [1]eMMC write fail: aboot
Internal memory issue maybe? tried a version from updato, similar story
Click to expand...
Click to collapse
Are you flahing the same firmware version that's on your device, BLR2? aboot is the bootloader and it looks like it's failing trying to write that. If your flashing an earlier version of firmware you'll get that error. But it could also be caused if eMMC is bad. When you sent it to Samsung did they do anything to it, or tell you anything that might be wrong? When you boot into the bootloader what does it say about FRP lock?
Edit, also, if you're not, run Odin as administrator.
Sent from my [device_name] using XDA-Developers Legacy app
FRP lock: On
I'm not completely sure which firmware was on the device, was assuming BLR2. Done a successful flash in Odin (using BLR2) but still only boots to recovery giving error -
#fail to open recovery_cause (no such file or directory)#
No support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed
Samsung only told me its a non EU device but couldnt tell where it originated from and that they can't help as components are different from EU devices
any ideas?
NI3K said:
FRP lock: On
I'm not completely sure which firmware was on the device, was assuming BLR2. Done a successful flash in Odin (using BLR2) but still only boots to recovery giving error -
#fail to open recovery_cause (no such file or directory)#
No support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed
Samsung only told me its a non EU device but couldnt tell where it originated from and that they can't help as components are different from EU devices
any ideas?
Click to expand...
Click to collapse
Ok, so you don't know what country the device came from? And I assume you're in the EU? There's a few things to try. Have you tried Samsung's smart switch program, Google it. I haven't had luck with their software but maybe it'll work. And might identify your device.
Also, try flashing just the bootloader with Odin. I assume you're trying to flash just the AP binary. Try flashing just the bootloader. Choose BL in Odin and the BL file from the stock firmware. Don't flash anything else. See if that will flash and then boot.
I believe the device was from China but seems to have been running UK software as thats the only firmware that will load without a dev_error
Smart switch didnt identify it as a device which could be repaired
tried flashing bootloader only, same issue of bootlooping or automatically booting to recovery.
I have flashed to older android version T825XXU2BRJ1 but exactly the same issue of bootlooping/recovery
Even im facing same problem without any solution.
I'm so sorry that this happened. I would've tried to help you IF ONLY MY TAB WASN'T HARD BRICKED
I have an Infinix hot 6x phone that after an OTA update, got stuck in boot loop, I have never tried rooting the phone or installing custom rom. After the boot loop issue, I tried installing an update and a stockrom through SD card via recovery mode and I got "wrong footer, signature verification failed" error for both update and stock rom files. I need help.
jamescndubuisi said:
I have an Infinix hot 6x phone that after an OTA update, got stuck in boot loop, I have never tried rooting the phone or installing custom rom. After the boot loop issue, I tried installing an update and a stockrom through SD card via recovery mode and I got "wrong footer, signature verification failed" error for both update and stock rom files. I need help.
Click to expand...
Click to collapse
The error indicates that both the OTA and the Stock ROM you're trying to flash aren't signed by OEM/Carrier. Where did you fetch them from?
I got them from two random websites on the internet. Please can you send me a link to a signed and verified one, preferably the OTA because it's smaller in size? Thanks
jamescndubuisi said:
I got them from two random websites on the internet. Please can you send me a link to a signed and verified one, preferably the OTA because it's smaller in size? Thanks
Click to expand...
Click to collapse
Contact Infinix CS: https://www.infinixmobiles.in/
I can't get an email to send a message to or a number in my country to call. The link is for India
Today my phone just boot looped. Can get to TWRP. But, I want to update A14 to 15, since it might allow the phone to start again. I flash stock Boot A14, that seem to work. Then, I try to flash the update to A15. TWRP gives me this error: fec_open "/dev/block/dm-10" failed bad address.
E2004: my_region.01000100 partition fails to recover.
What does this error mean? and, is there anything else I can do or try?
turns out i have an EU phone, with indian sowftware on it? Is it possible to flash it back to EU? And, how can i check the current version of the firmware in terminal ?
update: ok, it looks I am on version 11. Is there any link available to the boot.img from A10 and the incremental update to A11 (not the telegram link, does not work with a broken phone)? Both Indian and EU? Hope that redoing the update fixed the bootloop