Hey guys. So, I've been messing around with flash able zips, and I came into a problem. I downloaded the beats audio zip made for the captivate glide, and I saw it was working for everyone else, so I decided to try it. I downloaded it, and after going to recovery, and trying to flash it, it says installation aborted error status 0. I have no idea what this means, but it'd be appreciated if someone could help me out. Thanks.
Brandon.
Related
Hey guys, this is my first post here.
just rooted a few days ago and decided today to try and flash a Froyo rom, was going to do skyraider. i read and followed the how-to for the radio update, unrooted, and placed the file on the root of my SD card. when i went to recovery when i attempt to run update.zip i get an error saying 'not found' 'authentication failed' or something very similer. searched around and didn't find much...
currently running 2.1update1
any ideas? thanks
problem solved... was naming the file update.zip.zip..heh
i believe i need to unroot my defy. as i get the status 7 error and logwrapper error. can anyone help me solve this?
If you haven't already figured it out.... The logwrapper error is all too common and can easily be fixed. It is due the the fact that you have clockwork recovery installed. One fix is to delete the file logwrapper, NOT LOGWRAPPER.BIN, next step is to RENAME LOGWRAPPER.BIN TO LOGWRAPPER. Re run update and PRESTO!
DO NOT UNDER ANY CIRCUMSTANCES JUST DELETE LOGWRAPPER, YOU WILL BOOTLOOP AND BE STUCK FLASHING A SBF AND JUMPING THRU SOME HOOOPS!
Or simply use clockwork recovery and apply Beach_Head's edited update that he has so kindly posted on these forums.... Trust me it works. But only if you are coming from 3.6.360 otherwise you should try one of the alternative methods posted by Beach_Head.
Or you do the Nandroid method, if not already on 2.2 rom then you need to flash a 2.2 boot only sbf after nandroid restore
Just wanted to thank you and Runeblade for posting this and figuring out how to make the update work.I tried to uninstall CWM to no avail. The logwrapper was still the issue. So now i have to reinstall it and the whole deal. But at least I didn't have to spend my whole night figuring it out. Only part of it. So thanks again and keep it up. The "not so great at this but just good enough to mess it up" folks like me need all the help we can get. And a sticky with instruction may help all those who are about to have issues with this when Moto releases it to the masses. I had to fumble around figuring where to look for the .bin files. Might be a good idea for someone to post a guide about how to change the file name, verbatim, and what to use to do so. Would help so folks that are not so daring or trusting and mayhaps cut down on clutter on here. Just a thought.
wow it worked !
i got mine working, i re-rooted my phone again so i could delete "logwrapper" under \system\bin using root explorer app
and after deleting logwrapper i renamed logwrapper.bin to logwrapper. i un-rooted my phone again.
(some say that you can also delete: su busybox hijack, but i didn't saw them)
downloaded the update again and it'll ask you to reboot to update , viola it worked!
----------------------------------------------------------------------------
NOTE: this solved my logwrapper and status 7 error message
i don't know if it'll work on other error messages as well , try at your own risk!
----------------------------------------------------------------------------
maybe these files were leftovers when i un-installed clockwork recovery and super one click, after a day of reading forums i finally got me an updated phone!
welcome FROYO!
Hello all,
This is my third Galaxy S2 for T-Mobile and this is the hardest phone to root, lol. For some reason when I flashed ClockWorkMod Recovery via ODIN it does not want to read any files on SD or Internal. It keeps erroring out saying "bad file". The first and second phones did this, but it would actually push the Superuser APK over anyway after boot, but this phone isn't. Renaming it doesn't help either. I've used three different versions of CWM, including the touch release and NADA...ZIP. I even tried flashing a pre-rooted ROM and it still will say "bad file". Please help. If I have to flash a rooted ROM via ODIN, I'll bite the bullet, but any suggestions will be helpful.
jonw2009 said:
Hello all,
This is my third Galaxy S2 for T-Mobile and this is the hardest phone to root, lol. For some reason when I flashed ClockWorkMod Recovery via ODIN it does not want to read any files on SD or Internal. It keeps erroring out saying "bad file". The first and second phones did this, but it would actually push the Superuser APK over anyway after boot, but this phone isn't. Renaming it doesn't help either. I've used three different versions of CWM, including the touch release and NADA...ZIP. I even tried flashing a pre-rooted ROM and it still will say "bad file". Please help. If I have to flash a rooted ROM via ODIN, I'll bite the bullet, but any suggestions will be helpful.
Click to expand...
Click to collapse
ZedoMax has created a very helpful website with videos and step by step instructions on how to root, install ROMs etc. Check out the website below, it should help you out, it really helped me out.
If you want to Root and have the option of installing ROMs, check out the link below:
http://galaxys2root.com/galaxy-s2-root/how-to-root-t-mobile-galaxy-s2-sgh-t989/
If you are only interested in Root access and don't want to install ROM's, check out the link below:
http://galaxys2root.com/galaxy-s2-root/how-to-root-galaxy-s2-newworks-on-all-galaxy-s2-variants/
Thanks. I can at least root it now. Got all the bloatware off of it. The first two phones I could put custom roms on it, but this one is a piece, lol. I even put the old firmware 2.3.5 on this one and clockwork still errors out. Shoulda kept the first one-ran smooth with Jugs rom, brought it back to the store because of the green camera issue, lol.
And I am now rocking Jug 5.0! Turned off signature verification and fixed permissions and it worked.
Hello,
from here: http://forum.xda-developers.com/showthread.php?t=2642605
Exciting new ROM I wanted to try but when I try to install it through CWM it says
set_metadata_recursive: some changes failed
E:Error in /sdcard/aosb_kk_1.2.8_vision.zip
(status 7)
Installation aborted
The install instructions, step 2, specifically mentions update recovery, and googling for this error suggests that that solved it for others, but I have the latest CWM for the G2/Desire Z: I've tried both 5.0.2.7 and 5.8.1.0, non-touch and touch. There's no where else to upgrade to, unless I'm being completely obtuse. I've tried redownloading the zip to make sure it wasn't corrupted or anything, I've formatted my system and data partitions, all the usual stuff I could think of.
Can anyone provide a little bit of assistance? I've specifically got the G2, not Desire Z, but I don't think that's made a difference in the past but it's been a while since there was a new ROM I wanted to try so I'm probably forgetting something. What about this TWRP I've read about? First try couldn't get it to work but if I did get it to work think that might let me finish the install?
Thanks!
Yes, we'll go with "obtuse". I found the developer thread with a much more up to date CWM. Pity that only such an old version is available through official channels.
Thanks.
Tearing my hair out now, I am a bit of a novice at this, but done a few phones before, it is such a minefield!!! I have googled lots and tried to fix it by following various instructions, but just can't. Can some experts please help me? Thanks!!!
I have an Xperia M, which was behaving very oddly, showing as nearly full with hardly any apps. So decided to put CM12.1 on it to see if that sorted it.
Followed official CM instructions (https://wiki.cyanogenmod.org/w/Install_CM_for_nicki) to install. Followed the process for official Sony bootload unlock, which said it had worked. Got into Cyanogen Recovery, but get odd messages when trying to do the "wipe/factory reset" step. (Odd messages like described here: http://forum.cyanogenmod.org/topic/112974-wipe-data-does-not-work/).
Tried flashing CM12.1 from SD card in Cyanogen Recovery anyway, but it didn't work. Came up with more errors along the lines of "can't mount /data".
Thought I would try to revert to stock (as described here: http://forum.xda-developers.com/showthread.php?t=2697277).
Have installed flashtool (including the drivers), downloaded an .ftf file, but when I try to follow these instructions, I point the firmware selector window at the folder I put that in and it just doesn't see it.
At the end of my tether now, anyone got any suggestions as to how I can either get CM12.1 to work (would be great!) or at least get flashed back to stock?
Thanks a lot in advance, really need some help now, have spent hours trying to do this with the help of Google!!!
I have tried flashing CWM (which worked) and using that to wipe/factory reset, and get the same errors. There seems to be something fundamentally borked that is giving me this error:
"failed to mount /dev/block/platform/msm_sdcc.1/by-name/system"
And I can never mount/format the "/data", which is related?
BUT!!!!! I think I have solved it...
...downloaded Archidroid (http://forum.xda-developers.com/xperia-m/development/rom-archidroid-v2-5-0-power-hands-t2806978), flashed the boot image for that in fastboot, that gave me TWRP, and that seemed to have extra options which successfully did a factory reset - had to do an extra "format data" which did the trick. Did the Archidroid ROM flash (what a fantastic user friendly installer!!) and it all seems to have worked - no error messages!!!
Phone restarting now, looks promising.
I hope this has worked, not really sure what I did wrong, or why Cyanogen Recovery and CWM could not fix it and TWRP could?!?!?
What fun!
Good to hear, but please post in Q&A, Help, and Troubleshooting subforum next time for these kinds of posts.
Please help!!!! I'm a noob to Sony smartphones and I did something stupid to my newly acquired C1905 sgl sim Xperia M. I tried to unlock boatloader impatiently using that app (apk) can't remember name. Anyways I've used it before on another Samsung phone and ended up in bootloops but I'm clued up on reviving Sammy's! ! And I tried it on the c1905 restarted and nothing. No LEDs no vibrations.. Nothing! ! I was impatient because I didn't have my laptop with me and seems PCs are the only way to do this on Sony's. Last night I messed and messed and the only progress after loads of forums and windows downloads I've managed to change the device (in device manager) from QHS_DOWNLOAD to the drivers recognising the device as a Sony... Will have to check again on laptop. Still no responses whatsoever from phone at all. Please help
Edit - as per device manager windows is saying "Sony Ericsson sa0101" with ADB interface driver and its working properly.
I did install loads of different driver packages. Some failed some didn't. Thanks