In case you have "error 7" or "error 6" while installing ROM , to save you trouble let me just point you to the right direction. I found out that a core problem is in differently set partitions between different ROMs and in that case not even editing the "update script" and deleting "assert" lines will be of no help. So, after hours of trial and error I stumbled upon the solution suggested by our fellow members an all credits go to them.
Read This:
http://forum.xda-developers.com/showpost.php?p=57424509&postcount=1403
Than Go To
http://forum.xda-developers.com/xperia-sp/development/flashtool-flashing-stock-roms-pc-t2825808
Once I followed these instructions and flash stock ROM via recovery I was able to flash custom ROM later.
Related
I've been trying to flash the latest nightly or the RC2 and it keeps failing.
I've tried with both recovery-RA-nexus-v2.0.0.img (Amon_Ra) and recovery-clockwork-2.5.0.7-passion.img (Clockwork).
I've tried using radio-4.06.00.12_7.img, FRG83-radio-5_12_00_08.zip, FRG33-radio-5_08_00_04.zip.
I've tried update-cm-6.1.0-RC2-N1-signed.zip and cm_passion_full-274.zip.
I've tried formatting my microSD card.
I've tried downloading each of the files I've mentioned at least twice.
Every time I try to flash either RC2 or any nightly, I get this:
Code:
Welcome to CyanogenMod-6.1.0-RC2-N1!
assert failed: write_raw_image("/tmp/boot.img",
"boot")
E:Error in /sdcard/update-cm-6.1.0-RC2-N1-signed
.zip
(Status 7)
Installation aborted.
On Amon_Ra I did 'Wipe ALL userdata', and it still didn't work.
On HBOOT I did CLEAR STORAGE as well.
I can use adb and fastboot if needed. But the ROMs just don't seem to want to install .
I'm confused and I've googled around but I haven't found any solution.
I was using RC1 previously, if it's relevant.
Any help is greatly appreciated! I don't really like bothering people, but I just can't figure out what to do. I tried searching, I always try searching .
I had a problem flashing stuff with amon 2.0 . I went back to amon 1.9 alpha and everything flashed with no problem. I never used clockwork so i dont know with that. Hope this helps.
After doing some more research I tried
Code:
fastboot boot boot.img
And it let me boot into RC2. I even rebooted and it seems to be working... According to the log, I have some bad sectors.
I tried doing
Code:
fastboot flash boot boot.img
But it gave me an error.
I dont use cmd for anything unless absolutely needed. I just do straightfoward download to sd root and flash through recovery. Maybe the rc2 file your using is bad.
you mentioned bad sectors and such so try downloading a rc2 file from a different site, might work. Try using a different version recovery as well. That could help as well.
u gotta r00t ur gibson first
I am having the same problem.
The bootloader is definately unlocked. I am pretty sure it is rooted as I can use titanium backup and give it root access.... What is the issue?
Maybe it is something related with your HBOOT version. I have mine 0.33.0012 and I have the same error you have. Really my error is in another rom based on 6.1.0RC2 and it seems it is related with the size of the kernel.
Previous kernel was near 1.2MB smaller than this one and maybe HBOOT 0017 manages better internal memory to give space to bigger kernel. Maybe updating HBOOT to 0017 solves this issue.
I am also looking into this problem here at xda to see what experts say
It isn't something as simple as not formating the SD card correctly is it?
No, Status Error 7 means that an image write failed, this is typically because the image doesn't fit on the partition and all of your symptoms point to this. Bad blocks on the /boot partition will cause this.
Old but relevant info I posted some time ago: http://forum.xda-developers.com/showpost.php?p=6851045&postcount=1556 (don't use the files on that page!).
Now, the CM stock kernel is really, really small... so if that doesn't fit then you may have a major challenge installing any custom rom...
I've verified my rom (Kang-o-rama) works on most phones with bad blocks on boot, I spent a lot of time making this so but still, if you have too many bad blocks it will not fit.
One of my users got his Nexus replaced because he had so many bad blocks no kernel would fit once he'd removed the stock one...
Code:
fastboot boot boot.img
Doesn't write the kernel to /boot so you won't encounter the problems (just don't reboot).
Code:
fastboot flash boot boot.img
Attempts to actually write the image.
I think you're in replacement zone actually... if you wipe your current /boot partition you may never get another kernel on there. Be careful.
I keep on getting this error when trying to flash a custom ROM into my phone. Is there a way to manually apply the ROM?
I tried booting into recovery then conecting my phone through usb and running the following commands through cmd: "adb push update.zip /sdcard/update.zip". then it tells me if I want to push "update.zipj", but once I press enter it gives me, "error: device not found"
Here's the cmd log:
Code:
C:\Users\Admin>cd\
C:\>cd\android\android-sdk\tools
C:\Android\android-sdk\tools>adb devices
List of devices attached
000000000000 recovery
C:\Android\android-sdk\tools>adb push update.zip /sdcard/update.zip
protocol failure
C:\Android\android-sdk\tools>
C:\Android\android-sdk\tools>adb push update.zip /sdcard/update.zipj
error: device not found
C:\Android\android-sdk\tools>
Am I doing the manual flashing corrrectly? I figured manually flashing the ROM would stop the error from coming up. Could someone either show me or point me in the right direction on how to fix this error and/or possibly how to manually flash the ROM in detail. I've already searched and I keep seeing threads with people asking for similar problems but with no real answer.
any help is appreciated.
1. adb push does not flash a ROM - just copies the file to the SD card
2. Looks like you are in recovery and you cannot push a file, unless you mount the SD card in recovery
Not sure what you mean "manually apply the ROM". ROM flash has to be manual, there's nothing automatic about it.
And, if you had really searched... I am sure you would have found atleast 10 references on how to flash a ROM.
Anyways, here's a link that will give you enough information to just about do anything with your CDMA Hero: http://forum.xda-developers.com/showthread.php?t=1063843. BTW, this is a sticky right at the top of where you posted this question...
BOOM. lol. Also the status 0 is an improper mount command, or you have a bad version of busybox. What zip were you trying to flash out if curiosity? And are you rooted, if so how did you do it?
What I meant when I said "manually" I meant to do it through command prompt instead of Rom manager or through recovery. And I was mainly searching for a fix for the status error I was getting. Which there is no info about that in the link you posted, however it does help with flashing my Rom through command prompt. :]
@il duce It's called "nfx speedy kingdom". I've been using the salsa builds in the development section, but I came across this Rom and it says it has everything working including Bluetooth so I wanted to test it out. Ill try using the tutorial on flashing roms without an sdcard and see if it works.
1. By the looks of it, adb is not recognizing your device... so, first and foremost you will have to setup everything properly for adb to connect
2. Even if adb recognizes the device, to the best of my knowledge, you cannot flash anything through adb, you must have confused it with fastboot. And, that too is possible only if you have engineering spl
One of the links from the thread you linked to show how to push the rom to system/data and use cmd to flash it from there, but the rom I'm trying to flash is over 300mb so it doesn't fit :/
I guess I'll try contacting the dev and see if he knows of a solution, might be that the file isn't correctly packed or signed?
edit: flashing using RA recovery it gives me the following:
Code:
E:Missing file:
system/lib/libvoAMRWBDec.so
E:Verification failed
Installation aborted
Does that mean it's the ROM that's corrupted?
Dude wtf... thats an evo rom.
Also, andy is correct 100%. Cease and desist before you bork your phone.
o_o he has it under heroc roms.
http://sprint.hero.ptyork.com/?cat=1
Edit: Sorry everyone for the questions, I just pm'd nfinitefx and he cleared out everything for me.
I am getting ready to jump into flashing for the first time. I am having difficulty through trying to get into CWM Recovery. I need to do a nandroid backup of my stock Froyo with all the settings in order to avoid headaches if something goes haywire. I have tried several times and failed. I have the current version of CWM Recovery 2.5.1.2. Each time I Reboot into Recovery I get into the blue screen, not the red CWM. I have also done the Reinstall Packages option as instructed on other theads and sites. Still to no avail.
Also when I try the Backup Current ROM, I confirm the file name, hit OK I get yellow messaging stating:
update media
Appling Multi-CSC
Installing Multi-CSC
Install default apk-files
etc.
When I choose reboot system now the last thing stated before reboot is Phone is Reset. If I choose reinstall packages I get, in yellow,
Install from sdcard
Finding, opening and verifying update package
Followed by, in red,
E: failure to verify whole file signature
E: signature verification failed
Installation aborted.
I appreciated any assistance/guidance to clear this problem up so I can get started flashing. I have done quite a bit a reading and thought I was ready. Hopefully this is a minor problem and does not indicate I need to do a lot more reading before I jump into the world of flashing.
Maxmusic said:
I am getting ready to jump into flashing for the first time. I am having difficulty through trying to get into CWM Recovery. I need to do a nandroid backup of my stock Froyo with all the settings in order to avoid headaches if something goes haywire. I have tried several times and failed. I have the current version of CWM Recovery 2.5.1.2. Each time I Reboot into Recovery I get into the blue screen, not the red CWM. I have also done the Reinstall Packages option as instructed on other theads and sites. Still to no avail.
Also when I try the Backup Current ROM, I confirm the file name, hit OK I get yellow messaging stating:
update media
Appling Multi-CSC
Installing Multi-CSC
Install default apk-files
etc.
When I choose reboot system now the last thing stated before reboot is Phone is Reset. If I choose reinstall packages I get, in yellow,
Install from sdcard
Finding, opening and verifying update package
Followed by, in red,
E: failure to verify whole file signature
E: signature verification failed
Installation aborted.
I appreciated any assistance/guidance to clear this problem up so I can get started flashing. I have done quite a bit a reading and thought I was ready. Hopefully this is a minor problem and does not indicate I need to do a lot more reading before I jump into the world of flashing.
Click to expand...
Click to collapse
How to flash a gingerbread rom Captivate (MobileTechVideos) on youtube will help you a whole lot with your issue. I really believe watchin this video is gonna help u!!! Good luck!
try re-downloading the update.zip (cwm.zip). and make sure its named update.zip and make sure it is in the main directory on your sd , (not in a folder).
You could try aio toolbox it has a cwm installer. with a simple clean & guide
really?? it was too hard to look at the sticky roll-up that contains all the info you need?
http://forum.xda-developers.com/showthread.php?t=1161102
my youtube comments are making sense more and more now....
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!
Hi, I saw some threads saying some stuff about the Huawei GT3, but they didnt helped me so Im posting this thread.
I have a huge Problem with my phone.
(Im a Newbie btw)
I wanted to root my phone so I installed TWRP and rebooted (TWRP works btw), now it said "Encryption unsuccessfull"
I looked up on YouTube to look how to fix this and ended up deleting my complete OS
Now I downloaded the Firmware of my Phone and looked how to install it with TWRP and ADB.
When I try to install the "update.zip" File with TWRP it says something like this :
[2017-11-14 08:00:21 623] E:unknown command [errno]
dload_format_userdata,line=527: dload_format_userdata ok!
script aborted: update_huawei_pkg_from_ota_zip: update package from zip failed
update_huawei_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
I:Install took 0 second(s).
Error installing zip file '/data/update.zip'
I also tried to delete the "assert" parts in the updater-script file but it also didnt work.
Now I heard about the "dload" Method but I have some questions about that
1. Where is the dload folder exactly
2. When I try to move the folder cointaining the "update.zip" to as expample root It says not enough space on device (which Is not true) or something like this :
Running command: 'mv "/data/update.zip" "/root"'
mv: write error: No space left on device
mv "/data/update.zip" "/root" process ended with ERROR: 1
Do I maybe have the wrong ROM or something?
Please help me . (or try )
Check the dload guide in my signature. You will know everything. Let me know if any questions or doubts, will help. Dont worry twrp error is normal as these zips shouldn't be flashed with twrp
shashank1320 said:
Check the dload guide in my signature. You will know everything. Let me know if any questions or doubts, will help. Dont worry twrp error is normal as these zips shouldn't be flashed with twrp
Click to expand...
Click to collapse
Hi! Thanks for your reply!
I bought myself a Micro-SD card and extraced the ZIP like in your tutorial, and its working!
Its installing right now!
But I wanted to say something..first thank you very much and second the Russian Website you provided gave me the wrong package, this was the right one :
skyneel.com/huawei-gt3-nougat
niclasdriver said:
Hi! Thanks for your reply!
I bought myself a Micro-SD card and extraced the ZIP like in your tutorial, and its working!
Its installing right now!
But I wanted to say something..first thank you very much and second the Russian Website you provided gave me the wrong package, this was the right one :
skyneel.com/huawei-gt3-nougat
Click to expand...
Click to collapse
There are many ways to get firmware but the best part it worked and successful. Enjoy buddy.