I'm using g800hq(Turkey Version) and when I try flash a rom with twrp, it gives error 7. I tried everything. Can anyone help me?
umutcatakoglu said:
I'm using g800hq(Turkey Version) and when I try flash a rom with twrp, it gives error 7. I tried everything. Can anyone help me?
Click to expand...
Click to collapse
Be carefull, this error is fired by a safty-mechanism who checks, if the rom is for this device. If error 7 shows up, this check somehow failed.
If you sure that this rom is compatible and meant for your device you can try this:
https://forum.xda-developers.com/showthread.php?t=2522762
Related
Hi guys, I'm experiencing a message "error updating binary zip" thing while trying to flash a liquid smooth rom on my nexus 6. Please help me. Thanks
You might need to update TWRP; what version do you have installed? It should be listed at the top in recovery.
trieo007 said:
Hi guys, I'm experiencing a message "error updating binary zip" thing while trying to flash a liquid smooth rom on my nexus 6. Please help me. Thanks
Click to expand...
Click to collapse
Download this App from PlayStore and you'll be able to find the latest TWRP here It'll automatically flash the recovery and give a try to flash the ROM again
Tried it now and I still have the error while flashing. My version is 2.8.5
trieo007 said:
Tried it now and I still have the error while flashing. My version is 2.8.5
Click to expand...
Click to collapse
Might be they use an old update binary in the zip. Ask in the ROM thread.,
Hello, I'm new to these forums and have come to them under some unfortunate circumstances.
I went to update my device (MOTO G 2014) and had an error (cant remember what it said), anyway I rebooted my device and it wouldnt load after the 'BOOT LOADER UNLOCKED' warning screen. I went into TWRP and went to reset my device and wiped the system. (feel like an idiot, then again I am..) So then I downloaded all the USB drivers and Android SDK along with adb+fastboot and attempted to sideload. during the sideload I got this error..
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
EDIT: the error is no showing up at * failed to write data 'protocol fault (no status)
I have swapped USB ports and tried a different USB cable, does anybody have any tips or do I have a paperweight on my hands?
Thanks in advance
Flash stock firmware.
motofirmware.center
Sent from my XT1031
If I understand, right now you have wiped system, and bootloop in Motorola logo.
If you can boot in recovery, then transfer a ROM to an microsd and flash from there.
UPDATE: managed to put 3 ROMs onto my sdcard but only one of them actually allows me to install it, but after I install it I am stuck at the boot screen, guessing I got the wrong ROM for my model, cm doesn't flash, it just says 'Failed!' and so does the most recent one from the website previously linked. Any tips? Model is XT1072. I have been sat at the boot screen for around 15-20 minutes, is it taking so long because of me clearing the dalvik cache?
PJT95 said:
UPDATE: managed to put 3 ROMs onto my sdcard but only one of them actually allows me to install it, but after I install it I am stuck at the boot screen, guessing I got the wrong ROM for my model, cm doesn't flash, it just says 'Failed!' and so does the most recent one from the website previously linked. Any tips? Model is XT1072. I have been sat at the boot screen for around 15-20 minutes, is it taking so long because of me clearing the dalvik cache?
Click to expand...
Click to collapse
Lemme guess u tried to flash "titan" CM and not "thea" one?
LuK1337 said:
Lemme guess u tried to flash "titan" CM and not "thea" one?
Click to expand...
Click to collapse
I have tried both, both are returning the same error
"E: error executing updater binary in zip"
Is this something to do with my TWRP being at v2.7.1.1?
PJT95 said:
I have tried both, both are returning the same error
"E: error executing updater binary in zip"
Is this something to do with my TWRP being at v2.7.1.1?
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3088800
get this recovery.
LuK1337 said:
http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3088800
get this recovery.
Click to expand...
Click to collapse
Thanks for your help and thank you to everyone else who replied to the thread. To anybody else who will maybe see this thread and who are stuck with the same errors, I fixed this by simply flashing the latest recovery using 'fastboot flash recovery [NameOfRecovery].img' then proceeded to install the ROM compatible with my device which I downloaded to my external SD Card.
Again, thanks
Hello, i have a bricked asus memo pad 7 (me176cx), when i try to install the factory firmware (UL-K013-WW-12.10.1.33-user.zip) the cwm and the twrp2 give me a error "unable to mount /factory" and i can't install the rom.
How can i fix that?
Thanks
PD: sorry for my caveman english (?)
kitsunezero said:
Hello, i have a bricked asus memo pad 7 (me176cx), when i try to install the factory firmware (UL-K013-WW-12.10.1.33-user.zip) the cwm and the twrp2 give me a error "unable to mount /factory" and i can't install the rom.
How can i fix that?
Thanks
PD: sorry for my caveman english (?)
Click to expand...
Click to collapse
Hello,
I have reported this thread to be moved to right Q&A inorder to get expertise help
-Vatsal
I never had to mount those partitions when installing that ROM when I bricked mine. I just wiped all caches and installed from zip. Are you doing this?
paulgiro said:
I never had to mount those partitions when installing that ROM when I bricked mine. I just wiped all caches and installed from zip. Are you doing this?
Click to expand...
Click to collapse
I'm a idiot http://forum.xda-developers.com/memo-pad-7/general/5-0-brick-solution-asus-memo-pad-7-t3134814,
I didn't read this "This package is for "K013" devices; this is a "K013_1"." I was bricked for a week because of a random device "name change?" Well here are the steps I took to make a flashable lollipop that wouldnt brick me. What you are doing here is telling the script that does the update that it does not need to verify your tablet model since it is wrong anyways.
Now i follow the steps and my tablet is boot, i'm waiting.
EDIT: Still bricked, now i can enter in fastboot mode but when i power on the tablet, after the logo, the screen is black
I have the same problem and can't find any solution yet :crying::crying:
sidane12 said:
I have the same problem and can't find any solution yet :crying::crying:
Click to expand...
Click to collapse
i can install the original firmware, but now still bricked with the same error
kitsunezero said:
i can install the original firmware, but now still bricked with the same error
Click to expand...
Click to collapse
try to format all partitions and shutdown, then boot into bootloader and load temp recovery and reflash .33 then boot android normally if still doesnt work, then reinstall once more but without wiping any partitions, if it decides to boot to bootanimation but its stuck there you need to simply make a reboot and then it should boot.
Ruben Craveiro said:
try to format all partitions and shutdown, then boot into bootloader and load temp recovery and reflash .33 then boot android normally if still doesnt work, then reinstall once more but without wiping any partitions, if it decides to boot to bootanimation but its stuck there you need to simply make a reboot and then it should boot.
Click to expand...
Click to collapse
how can i do that? can you make a tutorial please ><?
kitsunezero said:
how can i do that? can you make a tutorial please ><?
Click to expand...
Click to collapse
Load temp recovery select wipe, advanced wipe, format all, reboot to bootloader, load temp recovery, install, reboot normally, if it boots but its on bootloop just make another rebokt and itshould boot
Hi, I tried to flash back to OOS 3.5.4 from Leaked 4.0, but it keep stuck in "patching system image unconditionally". now no matter rom i flash, it keeps getting stuck.
I tried formatting /system but it doesn't work
Please help, thanks!
weihan1102 said:
Hi, I tried to flash back to OOS 3.5.4 from Leaked 4.0, but it keep stuck in "patching system image unconditionally". now no matter rom i flash, it keeps getting stuck.
I tried formatting /system but it doesn't work
Please help, thanks!
Click to expand...
Click to collapse
Try flashing the stock recovery and adb sideload the rom, I had the same problem but sideloading the rom in stock recovery worked for me!
noahvt said:
Try flashing the stock recovery and adb sideload the rom, I had the same problem but sideloading the rom in stock recovery worked for me!
Click to expand...
Click to collapse
Thanks for reply, but i keep getting error * cannot read 'oos.zip' * when i am trying to sideload
Edit: now i get "failed to read command: Invalid argument" error
weihan1102 said:
Thanks for reply, but i keep getting error * cannot read 'oos.zip' * when i am trying to sideload
Click to expand...
Click to collapse
Had that as well, go into device manager and find your device when it's in adb sideload. Right click on it and uninstall it and make sure you check the checkbox on the dialog that will show up. Then restart your pc. That's what ended up working for me!
weihan1102 said:
Hi, I tried to flash back to OOS 3.5.4 from Leaked 4.0, but it keep stuck in "patching system image unconditionally". now no matter rom i flash, it keeps getting stuck.
I tried formatting /system but it doesn't work
Please help, thanks!
Click to expand...
Click to collapse
I recommend you to buy an otg USB i think its the best choice to resolve all these crappy things.
In amazon Is very cheap.
Adb sideload fails For me always..
managed to flash back to oos 3.5.4 using this guide
http://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
thanks
When am flashing to install custom rom its showing "ERROR 1". How can i fix this error? please help me.
satheesh556677 said:
When am flashing to install custom rom its showing "ERROR 1". How can i fix this error? please help me.
Click to expand...
Click to collapse
How to Fix TWRP Error 1 on any Android Device
In this comprehensive tutorial, we will show you the steps to fix the TWRP Recovery Error 1 on any Android device, rooted or non-rooted.
www.droidwin.com
Hellera said:
How to Fix TWRP Error 1 on any Android Device
In this comprehensive tutorial, we will show you the steps to fix the TWRP Recovery Error 1 on any Android device, rooted or non-rooted.
www.droidwin.com
Click to expand...
Click to collapse
i need boot image file, am using miuisr calyx rom so how to get this boot image file.
satheesh556677 said:
i need boot image file, am using miuisr calyx rom so how to get this boot image file.
Click to expand...
Click to collapse
Simply extract it from the calyx rom zip
Hellera said:
Simply extract it from the calyx rom zip
Click to expand...
Click to collapse
suppose if i want to install other custom rom incase its shows error 1 , as i want to extract that rom to get boot img file, then use twrb to extract the img right?