Hi guys,
a couple days ago my Razr i stopped working. After a forced reboot it stucked at the intel logo an doesn't boot further (like http://forum.xda-developers.com/razr-i/help/wont-boot-stuck-intel-screen-t3162719). I tried several things I've read in this forum (and other sites) but with no success.
My original system was Android 4.4.2 build für RetailEU and I would love to have either this back or the CM11 from Hazou (http://forum.xda-developers.com/razr-i/development/rom-unofficial-cyanogenmod-11-t2966855). Unfortunately I don't get this far.
I unlocked (successfully) my phone tried to replace the Recovery with TWRP (as described in Hazou's thread) but after a reboot I get the following error:
Code:
E:fail to write to /tmp/kernel
E:fail to create kernel file /tmp/kernel
failed to enter recovery mode, error code -1
The only Recovery I was able to install was CWM 6.0.1.9 but unfortunately this version doesn't allow me to install the CM11 as I get the error:
Code:
set_metadata_recursive: some changes failed
A change in the updater script as suggested here http://android.stackexchange.com/qu...et-set-metadata-recursive-some-changes-failed doesn't work either.
Any suggestions how I can get my phone back to live?
Related
I tried using this guide to root and have a nandroid backup.
Code:
http://forum.xda-developers.com/showthread.php?t=698059
I tried almost like 100 times and in between I got the process installed , I mean I was able to Flash without any error and G.O.T Mode was installed in the recovery. I then performed a nandroid backup . But due to a silly mistake I happened to delete the necessary G.O.T files from the root folder.
And since then I am not getting it right.
I am holding the D-Pad up button in order to catch the boot and its taking me to the bootloader screen and the result is been displayed as "PASS"
But still it gives me EOCD Marker and Installation aborted error.
What am I suppose to do ?
Are you booting in recovery mode? Cause from your post you are saying you booted in bootloder mode
Power + x
Edit: eocd marker error = you did not flashed vulnerable recovery ...
Sent from my Milestone using Tapatalk
OTA updated miletone overwrites new recovery because of checksum mismatch.
fix:
rm -f /system/etc/install-recovery.sh
search for Disable_recovery_check_by_OTA.zip for OR script
Hi,
I have a problem with my Moto G 2014 XT1068 which is described in topic: forums.androidcentral.com/moto-g-2013/391289-something-seriously-wrong-my-moto-g.html#post3668518
I can't do these steps, because dialog window shows up all the time, and i cant go further.
I have disabled usb debugging option and can't disable ART runtime.
First of all "Factory" in bootloader doesn't work. Wipe and factory reset via stock recovery has no effect; old android remains, the same using TWRP:
"E:Unable to open 'cache/recovery/.version' but ends successfully
and PHilz.
I've tried to flash many roms using many recoveries( TWRP - few versions up to 2.8.5 because 2.8.6 has display flickering bug, few Philz, and few others that also flicker) and fastboot and msfastboot(both on linux).
When i flash via fastboot or mfastboot using xml.zip roms everything looks ok, there are no errors, but flashing has no effect - I have still old ROM with old issue.
When i flash via different recoveries always some errors appears. For example flashing latest CM 12.1 nightly
via TWRP i get:
"E:Error executing updater binary in zip '/sideload/package.zip'
or via stock recovery (ADB sideload) get:
"(...)
Verifying update package...
E:Failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Partition erase in fastboot despite "OKAY" message in CLI has no effect. As i understand this should remove all files from partitions.
This problem showed up when i discharged battery to 0% and turned on the phone.
Have you any ideas what should i try more?
Thanks in advance.
Hi,
I've tried other things to back my phone to life, like turn on usb debugging or even delete files, all via adb shell in recovery, but it is impossible. In TWRP or PhilzTouch I remount partitions with rw privileges, it look like I'm able modifying files via vi and cat to check results but when remount one more time old files still exist, so it is like there is some buffer? (maybe some security lock?), when try rm -rf files it shows up that i can't delete because it read only... (but mount says rw). After remount partitions with rw privileges wipe /data in twrp ended successfully but has no effect.
Do you know why everything looks ok, but it is not? Of course android boots up but is useless and after few minutes phone turns off.
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Sounds like you both have a failed eMMC. If that is the case, and I'm certain it is, there is nothing that can be done to "save" or "restore" your devices.
Sent from my XT1031
hi, maybe any1 has already found a solution?
dihcar said:
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Click to expand...
Click to collapse
I have exactly the same issue with my XT1063. Reading a lot for a solution, traying all without success.
Hopping someone can help us!
Dear forum,
I'm struggling to get CM 11 (or any other stable CM MOD) installed on my Galaxy S.
Trying to go back to factory settings, my rooted phone got bricked.
After struggling with the USB drivers via zadig I finally managed ODIN (very flaky tool !) to recognise the deive. I managed to repartition the phone using the PIT file s1_odin_20100512.pit (from google code)
I then started following the guidelines for installing CM on the device and flashed the phone (using Heimdal) with semafore 2.7.4. When going in recovery mode, it gave errors related to the mount points (missing .fstab). Any action from the recovery mode (data wipe, format, etc.) was resulting in errors related to the mount points...
Digging around pointed me to the Replicant recovery image as this would resolve the problem. Which it did. It now states CWM-based recovery v6.0.4.6 and operates without errors when mounting unmounting etc.
Now, when in recovery mode and pushing (adb) any MOD (CM, replicant, etc.) I always get an error stating:
E:Error in storage sdcard0 update.zip
(status 0)
Installation aborted.
I've been spending hours on combinations, rebooting reconnecting, re-wiping, toggling signature verif, sideloading vs pushing, etc. etc. and searching the Internet for answers.
So far I have not found a root cause or way to avoid the error and continue with the ROM installation.
Any idea what is causing the error message in the ROM zip files with Status 0 ?
After a fresh reboot in recovery and going to Advanced-show log, I can see:
Code:
I:Skipping execution of extendedcommand, file not found...
I:Cannot load volume misc
I:Can't partition non mmcblk device: devices platform s3c-sdhci.0 mmc_host mmc0
All hints are welcome.
Thanks
So I don't know what has happened but I can't flash even a single custom rom. The problem occurs in TWRP as well as CWM. Also I am on the stock partition. Tried the modified partition too. The problem is still occuring no matter what I try. The following case is of SOKP. Every other rom also has the same problem. Even after trying it via adb the problem persists.
After I select the zip file in the recovery mode,the installation starts. After that, it says:
Patching system image unconditionally...
blkdiscard failed: Invalid argument
E : Error in/data/media/0/SOKP-L_5.1.1-LMY48B-R3-20150525-cancro.zip
(Status 7)
Installation aborted.
Have you checked whether your bootloader is locked or not (because of that damned MIUI MM)? Try sending through fastboot:
Code:
fastboot oem device-info
If the "Device unlocked" comes out as false, then unlock it first by sending through fastboot:
Code:
fastboot oem unlock
It'll wipe all the content of your phone though...
shivam0909 said:
So I don't know what has happened but I can't flash even a single custom rom. The problem occurs in TWRP as well as CWM. Also I am on the stock partition. Tried the modified partition too. The problem is still occuring no matter what I try. The following case is of SOKP. Every other rom also has the same problem. Even after trying it via adb the problem persists.
After I select the zip file in the recovery mode,the installation starts. After that, it says:
Patching system image unconditionally...
blkdiscard failed: Invalid argument
E : Error in/data/media/0/SOKP-L_5.1.1-LMY48B-R3-20150525-cancro.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Extend your partition first, you'll be fine then. There is manual tutorial in Mi3 General sub forum.
Hello everyone. My problem is bootloop. I searched this forum before I post my own problem. Im trying to solve bootloop problem for 2 days. So I learned couple things. I had no idea what was fastboot and adp before.
Let me tell you what caused bootloop. I was using 6.0.1 firmware and my phone started working slowly. So I thought maybe new update fix that. I updated my phone and it was still slow. Then I looked that up on the internet. Some people said wipe your cache that might fix slow working zenfone. I put my phone on recovery mode and wiped cache and it caused bootloop. I started to search for my new problem. Found one with cmd command flashall. It turned my phone firmware to 1.17.40.1234 from 21.40.1220.2179. And then I downloaded raw ze550kl rom for my current firmware which is 1.17.40.1234. Extracted recovery.img boot.img and system.img
and used following commands :
fastboot devices
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system.img
fastboot commands worked with no problem and then I switched to recovery mode again and used this command:
adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip.If I tried to use raw rom as i mentioned before ,cmd says *cannot read. So I used this firmware from asus website.
last command causes this error on pc
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip
loading: 'ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip'adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
Total xfer: 0.00x
and on my phone this error shows up
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
Bootloop problem still exists so I tried to use different method which was flashtools. I got "Run flash image script failured" error. I tried to fix it but no luck.
Lastly I tried to apply update from sdcard but my phone cant read on sdcard for some reason and that sdcard is being used my little brother(it works).
What can I do to revive my phone ? Please help me.
Ankeroth said:
Hello everyone. My problem is bootloop. I searched this forum before I post my own problem. Im trying to solve bootloop problem for 2 days. So I learned couple things. I had no idea what was fastboot and adp before.
Let me tell you what caused bootloop. I was using 6.0.1 firmware and my phone started working slowly. So I thought maybe new update fix that. I updated my phone and it was still slow. Then I looked that up on the internet. Some people said wipe your cache that might fix slow working zenfone. I put my phone on recovery mode and wiped cache and it caused bootloop. I started to search for my new problem. Found one with cmd command flashall. It turned my phone firmware to 1.17.40.1234 from 21.40.1220.2179. And then I downloaded raw ze550kl rom for my current firmware which is 1.17.40.1234. Extracted recovery.img boot.img and system.img
and used following commands :
fastboot devices
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system.img
fastboot commands worked with no problem and then I switched to recovery mode again and used this command:
adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip.If I tried to use raw rom as i mentioned before ,cmd says *cannot read. So I used this firmware from asus website.
last command causes this error on pc
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip
loading: 'ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip'adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
Total xfer: 0.00x
and on my phone this error shows up
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
Bootloop problem still exists so I tried to use different method which was flashtools. I got "Run flash image script failured" error. I tried to fix it but no luck.
Lastly I tried to apply update from sdcard but my phone cant read on sdcard for some reason and that sdcard is being used my little brother(it works).
What can I do to revive my phone ? Please help me.
Click to expand...
Click to collapse
First download latest official build and don't do any edit or repack of zip .. Copy that ROM in the SD card make sure SD card works or format SD card into fat32 file system and copy ROM in it .. Go to phone recovery .. Hit update from SD card choose the zip wait till it flash if u still fail comment here .. I will give u alternatives