I've looked all over no one can solve this error for me!. I had a sensation and just started to cook my own custom roms from RUU's. I had no issues at all everything was going smooth! Now I have an HTC Raider (Vivid) and Im trying to make a custom rom from my local RUU... No matter what I get status 0... Ive tried different recoveries, changing updater script, using the binary thats in the CWM thread. Im at a total loss! I will be sharing this rom with the community when it is finished.. I think it will be an improvement over virtuous... thanks alot.
Related
Hi guys. I would like to adress a seroise issue that some of the nexus owners have.
I am one of them.
Most of the roms on the forum are not flashable due to a status 7 error. I got the same error using amon ra and clockwork recovery.
I underatand that the issu happend because i have some bad blocks or that the immages are bigger and could not be flashed. I can asure you that this is how i got my phone from google and i bought it on the first day it was availble online.
At this mpment i am seeking a solution that can solve my problem so i will be able to flash any rom ( rodriguez, enomether, cm6 , or evil nexus).
I was able to fflash some of the roms but i would really wanna be on the cutting edge.
probally a solution is to split the roms into 2 updates.zip.
i do not expect the prnogrammers to do it only for a small number of people but if you will be able to help me out and explain how to i will really appriciate this.
I am really desperate and need your help.
Thank you
Hay... Any one?
Are you bootloader-unlocked? try re-flashing a new recovery. That's all I can really think of. Splitting the update won't do anything, to the best of my knowledge.
Of course.
I flashes AMON RA 1.08 and clockworks.
Same deal. Nothing helps. I cannot install CM6 but I can install kang-o-rama that is based on CM6.
I am also able to flash emonther official but not the micromod that is based on that rom.
The rom just need to be smaller.
Extracted file "/system/xbin/tune2fs"
minzip: Extracted file "/system/xbin/upgrade_fs"
minzip: Extracted file "/system/xbin/vfp-crasher"
minzip: Extracted file "/system/xbin/wlan_cu"
failed to write boot partition from /tmp/boot.img
E:Error in /sdcard/MM-720p-WM950-MusEQ-v2.2.zip
(Status 7)
Installation aborted.
Failure at line 7:
install_zip SDCARD:/MM-720p-WM950-MusEQ-v2.2.zip
OK. This is what I have found out.
I cant flash the boot.img separately .
It has to be lower than 2.5. Thats why I am able to flash KANG O RAMA> couse its image is 2.35
I need a method in which the images will be lower.
How come some of the developers are unknown to this and some do?
Some of the Nexuses came out with bad blocks in the boot partition. It limits their ability to use custom ROMs, since custom ROMs usually include more options, newer kernels etc, which in turn makes the boot.img grow in size. Nothing much to do. Some of the ROM developers account for these devices and try to make boot.img smaller, some don't - or can't.
Micromod changes the original TheOfficial kernel to another one, with another boot.img - that's why you're unable to flash it.
OK, What can I do then?
What I wrote in the other thread, in General section - change the kernels of the customized ROMs based on Enomther or CM6 sources back to their original ones.
I don't know what the problem is... Clearly... That's why I'm here... But I can not flash any ROMs that have Sense UI in them, and I can not unroot my phone. I have clockwork recovery, and I've tried flashing every ROM with Sense UI and I always get an error message... something about an error on line 77, and when I try to unroot, I ALWAYS get a USB connection error.... If anyone can help me with either of these problems... I would very much appreciate it. Thank you.
I used RA recovery to flash sense. Works most of the time
Sent from my HERO200 using XDA App
So im sure this will get bumped to some where else but im desperate. I have been useing roms for a while now since dec 2009 and was wondering if anyone has a fix for my issue. If i try to RUU to re-root and start fresh to fix other random issues (hopefully) i get to about half way through the RUU and it gives an error (140) bootloader error, says im useing the wrong boot loader. im on a cdma hero that was using fire rats mod and aospcm mod then aosp 9.9.2 then cm 6 and i have tried 3 recoveries cwm 3.0.0.5 cwm 2. somthing (has puke green text) and then the amon RA and still same issue i thought flashing new recovery got rid of firerats mod. any ideas or help with this would be appreciated
What version of RUU are you using?
http://forum.xda-developers.com/showthread.php?t=694572
the one from this post as well as the latest direct off sprint site
This is what I have used in the past on my Sprint Hero when running into Error 140 issues. It works like a charm.
http://forum.xda-developers.com/showthread.php?t=843544
I just put 1.0.0.0 in the new_region_version.txt
Give it a shot and let us know if it worked for you too.
so flash this then try running the RUU again should clear 140 error
jlengvarsky said:
so flash this then try running the RUU again should clear 140 error
Click to expand...
Click to collapse
Yup
8char
got an error when trying to flash it made no sense i followed the instruction but wouldnt flash. have you ever seen an error
You could try the ruu in zip format. You can find in the hero dev section. You can get back to stock with that in no time. Good luck
Yea it's me again with the
" Modified Hero"
hey everyone i found some threads about this ( well similar but nothing like it) i just got my vivid and had to root it and get a new rom so i could overclock it and get all the goodies. i came from the inspire and before that htc winmo phones. ive always rooted and flashed roms so im no noob but im so stumped here. i rooted it and everything went fine ( even though i felt it was a little more difficult than rooting my inspire) then i downloaded a rom and tried to flash the same way ive always done it with my inspire and my GFs samsung fascinate and her thunderbolt and it successfully flashes then it bootloops. so i tired another rom. same thing. so i reverted back to the stock att rom. then out of nowhere i cant get to recovery. through hboot or anything. i then installed rom manger and installed cwm. still nothing i cant get to that either. so i cant flash roms and cant get to recovery. i really dont know whats going on. can anybody shed some light on the situation? thanks in advance.
You can flash recovery ...just see the super guide thread
Sent from my HTC Raider X710e using XDA App
flash it through hboot or adb?
Just fastboot flash ...if you see the super guide thread it has a zip file to flash recovery...it should have all necessary details...
Hope it helps
Sent from my HTC Raider X710e using XDA App
alright man im doing that now thanks for the input
Hi all,
I have been around a long time though i have never had trouble like this before..
i got a Incredible S PG32130 - HBOOT 2.0000.00 - Australian Delivered OPTUS002
I tried to follow the downgrade path so i could get S-OFF found here:
http://forum.xda-developers.com/showthread.php?t=1373697
Everything went fine so i proceeded with the older RUU flash to get back to 1.13 so can then run revoutionary..
Though the older RUU flash failed leaving the device hanging quietly brilliant.
Tried a few methods to get it back online to no avail.
So i htcdev unlocked the bootloader.. worked fine. still couldnt flash anything though. so put on CWM Recovery 5.0.2.0 which also worked fine..
I could then install custom ROMS.. So i tried IceColdSandwich though that wouldnt boot.. flashed the X4 kernel without issue.. so i assume it's cause the radio is still old and from what i gather i cant flash a new radio without S-OFF (i have tried through CWM and via Fastboot and via PG32IMG autoload in the bootloader and all fail.
So i tried an AOSP GB ROM still no luck.. Though neither of these would actually flash. get an communication error.. (could that be because ADB is not working? - am i missing a driver?)
And even tried a of legit WWE and CM7 both fail to install as well.
RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed
From my limited knowledge Radio is independent of AOSP/Sense/GB/ICS though Kernel is dependant. Though the only thing i havent been able to flash is the radio.. will the wrong radio stop you booting?
What are my options here to get S-OFF? I cant adb the device no matter what i do though i do have working recovery and fastboot.
Little help would be greatly appreciated.
damn..
http://forum.xda-developers.com/showthread.php?t=1337105
this fixed me.. the manual flashing of the boot.img was the problem..
ffs.. i have spent hours and read so many guides and that one was the only one that mentioned that you had to manually flash boot.img.
thanks all.
Sage said:
damn..
http://forum.xda-developers.com/showthread.php?t=1337105
this fixed me.. the manual flashing of the boot.img was the problem..
ffs.. i have spent hours and read so many guides and that one was the only one that mentioned that you had to manually flash boot.img.
thanks all.
Click to expand...
Click to collapse
Do you still require s-off? What error message did the ruu return when it failed?
the RUU error is simply USB Connection ERROR though this happens after it has erased and sent the package to the phone.
I think it maybe due to not being able to use ADB.. so prob a driver issue. either way i dont really need S-OFF and after the hours i have spent on this i am reluctant to play more
It aint even my phone! Mine is Sensation which is already S-OFF'd
Thanks for the offer though.