Database Develop

[Q] Problems with corrupted files when flashing

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!

[Q] Stuck at Padlock with X screen after repeated flash attempts

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?

[Q] HELP! :( Semi Bricked. Tried EVERYTHING

Ok
Please forgive me I have spent up to 7 hours today searching and trying but to no luck.
So I didnt realise what i was doing and Semi Bricked my Phone. I edited build.prop and saved it in MyExplorer(name?) to try and turn off the camera sounds and when I rebooted, it just gets stuck on the galaxy S 2 screen, boot loop.
I'm on SGSII (Australia) Stock Vodafone's ICS 4.0.3 Rooted.
I have CWM installed but tried a few things:
- I can get into Download MOde (no idea what to do here)
- I can get into CWM mode 5.0.2.7 Recovery mode but cant do anything still.
- I tried various Edify script builders to try and put the original build.prop back in but get multiple Status 0 errors whenever I try update.zip from the SD card.
- I tried rebuilding the backup on there and changing the build.prop file on there and trying to restore but MD5 check fails. Even tried rebuilding the MD5 file with the modified files and still no luck. MD5 files fails.
Would anyone have any suggestions and how to resolve this without a flash or wipe? I didnt back recent backup and will lose everything.
I am coming to a point where I really am wanting to back to Apple
There are 2 build.props attached. One is the bad one that stopped me from booting up and I found another one that was named .bak (extension taken off) I found in the same directory (/SYSTEM)
If anyone can help me build an update.zip to push in via CVM I would greatly be in your debt (I tried for 4 hours with no luck)

If you have recovery and download mode yet nothing is lost.
In first, do saved your apps ?
If you had saved them or if it doesn't matter to you, reflash a rom via recovery
LINK HERE:
http://download.cyanogenmod.com/get/jenkins/2773/cm-9-20120615-NIGHTLY-galaxys2.zip
Flash it GoogleApps folder
http://goo.im/gapps/gapps-ics-20120317-signed.zip
The rom that I attached to the reply is a CM9 ICS version, it's quitly stable and we can have some settings on it.
If it doesn't work reflash with Odin (it's with software who use the Download Mode)
http://hotfile.com/dl/149514867/aea2f22/I9100XXLPQ_I9100OXALPQ_XEO.zip.html
Instructions
-Unzip the Rom Folder ( I9100XXLPQ..........)
-Open the included Odin
-Put your phone on Download Mode
-Click PDA and select I9100_CODE_I9100XXKP*_CL*_REV02_user_low_ship.tar.md5
-Click PHONE and select MODEM_I9100XX*_REV_02_CL*.tar.md5
-Click CSC and GT-I9100-MULTI-CSC-OXA*.tar.md5
-Click Start and don't touch anything still the colored case become green
-And now your phone resurrects
Reply me of results

thanks for your reply
unfortunately i didnt save my apps and havent got backups of my data either
i cant reach the file via ADB either, when i run ADB (have KIES installed and worked before) - adb devices.
nothing shows up when the phone is stuck on "Samsung GS2" screen.
do you have any recommendations around keeping my data there?

If you find the exact same software your on now to download you could try flashing that in cwm without wipes I think that would work i think it replaces all system stuff so it will work, worth a try
Sent from my GT-I9000 using xda premium

understood thanks
what if i just want to flash build.prop via update.zip?
i tried so many methods but it always fails. is anyone able to create a update.zip for me?

i used a GUI script creator to try and update it via CWM recovery mode but it doesnt seem to like it.
If i turn off signature verification, it gives me a (status 0) error saying : E: Error in /sdcard/update.zip
and if i turn on verification toggle, it says E: signature verification failed
can anyone help?

calum96 said:
If you find the exact same software your on now to download you could try flashing that in cwm without wipes I think that would work i think it replaces all system stuff so it will work, worth a try
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
i know there are 2 types of ROMS right? the nonwipes and wipes. i really dont want the wipe versions.
the one i downloaded is 1G which i'd imagine is the wipe version if i were to upgrade via odin?
http://www.androidaddicted.com/firm...-vodafone-australia-firmware-update-1267.html

Can you mount any sd on your pc, because you can the recovery mount trick to access to your data.
When you are in the recovery menu, go to mount and storage and click on "mount usb storage" and the internal and external sd will appear on your pc.

you are posting in galaxy s thread....repost in galaxy s2 thread

I don't think so but then again I don't own a s2 but you can select advanced restore: restore data then flash a compatible ROM, then restore the data if you worried but as I said before flashing the same ROM shouldn't remove user data
Sent from my GT-I9000 using xda premium

[Q] Problems with rooting! Don't hate me

Hello all, sorry for creating another "Having trouble with root!" thread but the reading I have done hasn't been of much help. I began rooting my HTC One using QBKing77 (on youtube)'s method. All was going well, I successfully unlocked the bootloader and installed TWRP. however whenever I go into TWRP i cannot backup my data. I get an error message that says backup failed. In the 'log' screen it says 'failed to mount data', or something along those lines. when i try to install superSU, which i copied onto my internal storage, it doesnt show at all. In fact, the folders i see are different, meaning I'm not in the actual storage that i usually see when i connect my phone to USB. So, i tried to mount the phone while on TWRP, and I saw the superuser zip file i transfered, but i cannot do anything with it. i tried to add it while mounted as i can see the folders, but it would not let me. i attached some screenshots. Hope i can get this resolved. Thanks in advance!

Looks like you used the wrong version of twrp you should use this one.
http://techerrata.com/browse/twrp2/m7wls

[Q] Can't install ROM, unable to ADB push

*SOLVED*
I was having some cell issues so i decided to Wipe and that i may aswell update my ROM to insertcoin 4.0.5, after wiping internal storage I copied the zip over, wiped system, data and caches and tried flashing the ROM.
:"Unable to open zip file"
"Error flashing zip"
I tried using ADB to push a new zip but nothing shows up in adb devices, under device manager i get a yellow triangle by my "One" and updating within device manager doesnt work, and neither did reinstalling the latest htc sync manager.
can anyone help me?

n00b1c1d3 said:
I was having some cell issues so i decided to Wipe and that i may aswell update my ROM to insertcoin 4.0.5, after wiping internal storage I copied the zip over, wiped system, data and caches and tried flashing the ROM.
:"Unable to open zip file"
"Error flashing zip"
I tried using ADB to push a new zip but nothing shows up in adb devices, under device manager i get a yellow triangle by my "One" and updating within device manager doesnt work, and neither did reinstalling the latest htc sync manager.
can anyone help me?
Click to expand...
Click to collapse
"Unable to open zip file"
"Error flashing zip"
This probably means you just need to use a different recovery to install the Rom. What recovery did you use?

ok nevermind, after ages of searching i came across this http://forum.xda-developers.com/showthread.php?p=43378118#post43378118, seemed sketchy but figured i'd try, managed to communicate in adb after, successfully pushed the rom and it installed ok.