I have been working on flashing my wife's Nexus One to CM 6.0 but keep running into a problem where after I select the .zip file to flash and it verifies the update, it always fails due to a corrupt file with the message "E:Corrupt File: <filename here>" followed by "E:Verification failed". I tried multiple images and downloads, including Kang-O-Rama and the stripped down CM 6.0 as well as eViL's Sense ROM. All of them fail, not necessarily on the same file within the .zip either which leads me to believe it is a problem with the phone and not the images.
I have checked the md5s, they all work out and I also tried a different SD card but to no avail. Anybody know what could be causing this?
I had that problem once and finally just disabled the checksum verification. I'm not sure all recoveries have that option but if I remember correctly, it's in the same menu where you select "flash zip from sdcard".
Luckily, I never had the problem again. Whatever it was must have been due to something being messed up with the system that I had on it that day.
Thanks Fubaya, I am using Amon's RA which doesn't seem to be able to disable checksums. I'll search out a different one. Is there a preferred recovery image to be using?
Looks like the Clockwork Recovery did the trick, thanks for the pointer in the right direction!
Related
The title mostly sums it up, I have a Nexus One and unlocked the bootloader to install CM 6.0. I tried Amon's RA recovery image but kept getting file corrupted errors from the .zip files even after verifying the md5 checksums. I was able to get past that problem thanks to Fubaya in another thread pointing out that there are recovery images that allow you to ignore the checksums.
I have now been able to load ROMs from .zip off the SD card, but no matter which one I try (eViL's Sense, CM6, Kang-O-Rama or stock) or how many times I try it, I can't get it to load past the 'X' with the padlock screen at boot. It will sit there for about a minute, then reboot into recovery. I have wiped everything on the phone multiple times but no luck. It just sits there until I pop the battery out. Any idea's what could cause this problem? The recovery image does not show any errors and looks like it flashes successfully
the file corruption errors are a bit troubling.. have you tried re-installing the recovery before proceeding? perhaps the flashing itself is not being done correctly.
often times being stuck at the X can be fixed by wiping the dalvik-cache from recovery, but your problem might be deeper than that.
try putting on amonRA's recovery again and see if that makes a difference.
Uh yeah, you shouldn't be getting any checksum errors. Sounds like something isn't transferring correctly.
As I understand it as long as you have the recovery on there properly (you HAVE to install it correctly AND remove a few files if you're using the stock ROM otherwise it'll wind up at the stock recovery!) you'll "never" be able to brick your phone, with the exception of when flashing the radio apparently..
But flashing with corrupted files still doesn't seem like a great idea, so I'd figure out why this is happening. Can you pull the card out of the phone, put it in a card reader, and check the checksum with md5sum or whatever checksum the particular ROM used... md5 isn't very popular anymore, but it is fast and probably still used a lot for non-secure things, like verifying a transfer etc..
I've tried reflashing recovery multiple times and never seem to have a problem getting in there, either with Clockwork or with Amon. I also tried copying the .zip files back off of the SD card and re-checked the md5sum, it looks like the file is still unmodified so I have a hard time believing that it's corrupt. It does this with multiple SD cards as well, so I don't think its the card either.
I was able to get CM 6 to boot a couple times but the first time didn't seem to work right some error kept popping up that needed to be force closed over and over. So I reflashed and then was stuck in a boot loop with the CM logo. Since then, I have not been able to flash with anything.
Does this sound like some sort of hardware problem with the phone itself?
what radio are you running
4.06.00.12_7. I had Froyo running on here previously, and like I mentioned above, it booted into CM6 once but never came back after a second reboot. I tested and was able to make a call when it was running.
Flash the Recovery via ADB, not the SD card.
Do you still get checksum errors then?
I can't seem to get the phone to show up as an ADB device, I just get "device not found". After doing some reading, it looks like I did not enable USB debugging before flashing. Is there a way to enable this from recovery?
EDIT- Looks like the driver had uninstalled, I now have the driver back up and it shows up under ADB Device as being in recovery.
I copied the Kang-o-rama-1.0-Final.zip over via ADB and then tried to flash from SD Card from within Amon. It still shows E:Corrupt file: with a random file from within the zip as failing and then says verification failed.
Is it possible there is some sort of corruption elsewhere in the phone besides the SDCard that is causing these errors? It seems that whatever is causing the corrupt file errors (even though the .zip files pass the md5sum) is likely the root problem I am experiencing. Any ideas what else I could try to fix this?
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'm trying to install HC 3.2 from the stock Froyo install on a T-Mobile Streak 7.
I'm pretty sure I've followed all of the posts correctly, but I seem to get hung up and am hoping someone can point out the obvious (I hope) mistake.
First off, I'm using the flashing guide at:
http://forum.xda-developers.com/wiki/Dell_Streak_7/Flashing_Guide
And the files found at:
http://forum.xda-developers.com/wiki/Dell_Streak_7#Official
Specifically, I'm using these files (US 4G 514 build):
http://mirror2.streakdroid.com/manii/Streak7/514/recovery.img
http://mirror2.streakdroid.com/manii/Streak7/LG7_514_21700_30.pkg
I seem to have no problem installing the recovery image and installing the rom package on the SD card.
But, when I try to go into the Recovery mode and select to update via update.pkg, I get the message "Booting recovery kernel image" and then it just hangs.
I've downloaded both files twice in case there was a problem with one of the downloads and that did not fix it.
As a test, I installed the old recovery image:
http://mirror2.streakdroid.com/manii/Streak7/336/recovery.img
And tried to update to the 514 package, and it failed (gave the FOTA error - as expected).
Any ideas on what is going wrong? Thanks.
You can try to open your .pkg simply when device is power on - from downloads or with file manager. I installed HC official update (but i have wifi version) this way, without recovery
I cannot get it from the update section because it is a T-Mobile version.
As for running it from the file manager, it is an "unknown" type. Not sure how you can install a .pkg file direct from the OS.
Download XPlore File Manager and try Open in a system in submenu on long tap
Whenever I go to flash the viper mod, which I really want to get. It says "Unable to open zip file. Error flashing zip /sdcard/ViperOneM8_1.4.0.zip"
Here's what I've tried to do to troubleshoot the issue.
- First I tried loading it on my phone with push, same error.
- I then reboot my phone in factory settings, turn on File Sharing mode, and transfer it to the external that way. Then rebooted in recovery and tried to install. Same error.
- I then moved it from the external_sd to the internal sd. Still the same error.
I've also tried some of these steps after deleting the old copy off my phone/computer and downloading another. Same error. Also, if I let it check the md5, I get an error. So, I guess I keep getting a bad download? I'm not sure. I do know that the file opens up fine on my computer.
Only things I can think of is make sure your flashing with TWRP and not any other recovery. But it does sound like you're getting a bad download.
Sent from my 831C using Tapatalk
Disclaimer: I'm relatively new to the realm of modding the the kindle. I have a 2012 7" hd. I rooted it and loaded a 2nd bootloader and recovery via various tutorials. I attempted to to load a rom (lolipop 5.1 and corresponding gapps). The process seemed to go fine and when it booted into android the initial setup screens appeared (connect to wifi etc); but then I got a message that the setup wizard had failed. I tried "skipping" screens etc and regardless of what I did I couldn't get past that screen. I clearly either did something wrong or didn't have a good rom file. I was an idiot and didn't create a backup before flashing the new rom. So I mounted it in recovery and loaded a factory image that way and flashed back to norm. My intention was to start things over. I rooted again, went through the whole process; however, I'm seeing a weird phenomenon. When I am in windows (or ES explorer for that matter) and access the files on the sd card partition...I can load files onto there (for flashing in recovery etc); however, once I am actually in recovery and go to "install" the partition that I view in recovery is the files I had from the very first flash. I can create new files in windows or ES explorer and everything works as expected....but once in recovery, none of those folders are present...and the only zip files that are available to "install" are the ones I used the first time that didn't work. I'm clearly looking at some other partition or image in recovery than I am in windows. I have cleared cache and everything I can think of (again I'm a complete amateur). Does anyone have a suggestion of what I am doing wrong or how to resolve? Thanks in advance.
Cranky
The issue with your first problem was that it could have been a bad gapps, in the future try different gapps if you see weird problems like that, to your second problem, when flashing lollipop on a device that had ICS it'll change the directory of the SDcard, no biggie though, just search in recovery data/media/legacy or data/media/0 it should be in one of those that your files are in.
Sent from my Nexus 9 using Tapatalk
Try this.
Try to send files over using adb whilst in recovery. If you do not know how then watch this youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.