When I started this project I guess I thought I knew more than I did. I had installed Cyanogen on multiple other devices, but this one got me. I apologize profusely, I'm not usually one to ask for help but I promise I've been scouring these forums and the web for about 8 hours straight now to no avail. (In all likelyhood I'm just an idiot). Anyway, I'll spell out my problem as best I can.
Basically what I want as a final result is CM 10.1 RC2 Jelly Bean 4.2.2 on my HTC One X at&t. Right now, I'd just like to be able to install any rom at all. I currently don't have anything working and I believe accidentally wiping "system" did that.
When I try to flash it from CWM it just stops and says (Status 7). It seems every rom I try to install comes up with some error there.
Could rooting be a problem? I tried installing several superuser.zip files I could find online. One seemed to work, though I think it's an old one. The latest one I tried came up with error (status 0).
Do I need s-off? I've been trying the "All in one" tool for that but with no luck. I also tried installing SuperUser with the same tool, but it said "Device not found", even though I could reach it via adb fast boot.
Finally, when I try to boot normally it bootloops between the "HTC quietly brilliant" screen, and the same one with the red text that says "this build is for development purposes only. Do not distribute..."
It's 3 in the morning and I should probably get a little sleep before work tomorow. Thanks a ton for reading!
I have the same problem! My phone doesnt have a rom on it at all after this.. When i go to cmd and try to flash a rom, it says something like "cannot open filename.img"
First things first. What firmware and hboot versions are you on?
Secondly, try using TWRP recovery instead of CWM. It can be found here. Flash it using fastboot with the following command:
fastboot flash recovery recoveryfilename.img (whatever the exact recovery filename is)
Then do:
fastboot erase cache
fastboot reboot-bootloader
Thirdly, where are you downloading cm from? You should only get it from here.
Sent from my Evita
---------- Post added at 07:17 PM ---------- Previous post was at 06:54 PM ----------
PS. flashing a superuser.zip while you have no OS installed will do absolutely nothing.
Sent from my Evita
I think everyone with the evita should be s-off. it helps get rid of many annoyances with this phone. also nothing is being done that uses s-off that is really that dangerous.
You should be supercid,s-off,latest ruu 3.17 or 3.18(at&t) then flash recovery and then flash supersu zip to get stock rooted, or you can just wipe the phone and flash a custom rom. i currently use cwm and havent had trouble with it. you can get latest unofficial cwm builds here http://goo.im/devs/mdmower
I just achieved S-OFF yesterday via Facepalm and everything was fine until i tried to install a new rom. I get the same error with illusion or CM nightly and I may have done something wrong....idk. It says something about the bootloader. Here it is :
Installing update...
assert failed: getprop("ro. bootloader") == "2.15.4444" | | get prop("ro. boootloader") == "2.13.0000"
E: Error in /sdcard/ .....(my folders)..../cm-10.1-20130807-nightly-ville.zip
(Status 7)
Installation aborted.
I know they both have the 3.4 kernel but I didnt see anyone that actually couldnt install the rom. And in the PACman development thread it says the kernel isnt working only if you are on a lower hboot than 1.14, and i am exactly on 1.14. I dont know if this has anything to do with it....
Edit: right after i wrote this i flashed elementalx and now the phone reboots 1 time and then it stops at the white htc screen with the red sentences. Same thing for recovery, after few seconds the screen turns black and it reboots..
Hi guys, I'm getting kind of frustrated with the installation of KitKat KangBang. I'm running on an i9505 with PhilZ Touch 5 with the CWM Base version at v6.0.4.4. Whenever I get to around 50% of the ROM install, I get the "set_metadata_recursive: some changes failed" error. I've tried several different recoveries and I get the same thing every time. What am I doing wrong?
EDIT: I'm dumb. I'm running on M919, not i9505. Lock it up!
RE.
Just update your CWM Recovery.
Hi,
I need some help. Firstly I'm quite a noob so please go easy on me, have only flashed/rooted a couple of phones before this...both with pretty much no issues.
I flashed the CM 9.1 A while back to improve it, and decided I wanted to change it due to few bugs annoying me too much...such as the restarts, crazy battery life and most annoyingly of all calls only being able to be heard on loudspeaker! Buts can't seem to get any other rom to flash - tried 2 - samsation v6.0 kerneldev101 & MikTouch- 0.7-signed.
When trying to flash firstly 'samsation v6.0' i encountered an error code '"assert failed: getprop("ro.product.device") == "pyramid"
E:\Error in /storage/sdcard0/samsation v6.0.zip
(status 7)
Installation aborted.
and to try and overcome this I opened the updater script from rom zip and deleted the line 'assert(getprop("ro.product.device") == "pyramid" || getprop("ro.build.product") == "pyramid");'.....after reading in forums it could be this. After this line is deleted the flash attempt is 'opening update package...installing update...installation aborted'
I then tried MikTouch 0.7 and it came up with the 'status 7' error, so I deleted the first line of the updater script and now I am getting a 'status 4' error...even if I try to flash thru rom manager - CWM app.
Driving me crazy! Any help much appreciated.
even tried a different SD card to see if that makes a difference....and nope
installed new CWM - V6.0.4.6 after reading that may be the prob. no difference
To be honest it all P'd me off so much just went and bought myself the Moto G instead...but would still like to fix this one and get it even back to a stock like ROM so at least it functions properly but without all the bloatware.
Use TWRP instead of CWM. This should fix the issue.
Tried it thru the twrp app and it just launches into cwm recovery and does same status 4 error
Thanks for replying though!
Sent from my XT1032 using xda app-developers app
'Cwm-based recovery v6.0.4.6
--Installing: /storage/sdcard0/MikTouch-0.7-signed.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /storage/sdcard0/MikTouch-0.7-signed. Zip
(Status 4)
Installation aborted
Sent from my XT1032 using xda app-developers app
I didn't mean the app found on Play Store. I meant the actual TWRP recovery.
You'll have to connect your phone to your PC, boot into bootloader, and flash the TWRP recovery, which will replace the existing CWM recovery.
Moto g looks like a great phone for the price, but I would want to fix my double shot too.
First off, the getprop errors you were getting were saying you were trying to flash a ROM for sensation on your doubleshot, not a good idea, don't delete getprop from updater-script no matter what the internet says, this is a good warning
Don't use an app for flashing, use recovery
But before you proceed any further I would suggest to boot into bootloader and write down every thing from that screen here, word for word
Then you will be sure to get the exact links and info, I wouldn't do anything until then, not to say @abe5 is having you bad info, he is correct, but I have a feeling there may be more info needed here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Bootloader info
Hi,
OK thanks to both of you for your help! ...I guess I would rather check/be sure than do something worse to my phone.
Your right Moto G is great phone..I am pretty impressed so far...for the price. Only let down is the camera....I miss the doubleshot great camera...but you cant have it all....well not for £130
OK SO INTO BOOTLOADER..... (front screen reads as follows - hope this is what you mean?!)
***UNLOCKED***
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.45.0013
MICROP-0353
RADIO-11.16.3504.20_2
eMMC-boot
NOV 21 2011,20:20:47
FASTBOOT
VOL UP.... ETC ETC
.....
fickleama said:
Hi,
I need some help. Firstly I'm quite a noob so please go easy on me, have only flashed/rooted a couple of phones before this...both with pretty much no issues.
I flashed the CM 9.1 A while back to improve it, and decided I wanted to change it due to few bugs annoying me too much...such as the restarts, crazy battery life and most annoyingly of all calls only being able to be heard on loudspeaker! Buts can't seem to get any other rom to flash - tried 2 - samsation v6.0 kerneldev101 & MikTouch- 0.7-signed.
When trying to flash firstly 'samsation v6.0' i encountered an error code '"assert failed: getprop("ro.product.device") == "pyramid"
E:\Error in /storage/sdcard0/samsation v6.0.zip
(status 7)
Installation aborted.
and to try and overcome this I opened the updater script from rom zip and deleted the line 'assert(getprop("ro.product.device") == "pyramid" || getprop("ro.build.product") == "pyramid");'.....after reading in forums it could be this. After this line is deleted the flash attempt is 'opening update package...installing update...installation aborted'
I then tried MikTouch 0.7 and it came up with the 'status 7' error, so I deleted the first line of the updater script and now I am getting a 'status 4' error...even if I try to flash thru rom manager - CWM app.
Driving me crazy! Any help much appreciated.
even tried a different SD card to see if that makes a difference....and nope
installed new CWM - V6.0.4.6 after reading that may be the prob. no difference
To be honest it all P'd me off so much just went and bought myself the Moto G instead...but would still like to fix this one and get it even back to a stock like ROM so at least it functions properly but without all the bloatware.
Click to expand...
Click to collapse
Don't use CWM above 6.0.2.5 for flashing an older ROM. 6.0.4.6 is designed for KitKat and will fail older ROMs.
everything looks good on bootloader so the issue is with recovery or rom.zip
personally i think its the rom.zip, but I also recommend TWRP recovery
so i would download twrp (without dumblock) from HERE
and flash with fastboot, also do some erasing in fastboot for good mesure
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
the md5sum for recovery is listed next to download, be sure it matches use command line on linux or this for windows
but what i really think is the problem is the roms, bad download or whatever, the status 4 and status 7 are related to updater script, so either you playing with them messed them up or they were corrupt from the start
md5sum for MikTouch-0.7-signed.zip should be BAE9153946B02251621547DBFB537387
if not re download
now it is possible that the newer recoveries f\wont flash older roms, like Fuzi0719 said, but in theory they should and i have not had issues myself
but if need be weekends has posted older recoveries HERE be sure to thank him
flash with fastboot if you TWRP fails you
also when i see this --Installing: /storage/sdcard0/MikTouch-0.7-signed.zip
make me wonder, if i am correct the path on this phone is just /sdcard/MikTouch-0.7-signed.zip
but i cant recall as it has been months since i used my doubleshot, its just how i remember even the newer recoveries find sdcard path here
so maybe for good measure take everything important off sdcard and format to fat32
then put new rom on the root freshly formatted sdcard (not in any folders) before you flash
hope it all works out, if there is an issue let us know!
well I spent the whole evening mucking about with it and I have conquered it. Thanks guys for all the help...couldn't have done it without you!
After firstly having to switch to an older laptop as win 8.1 not compatible with htc drivers ...
I flashed TWRP and tried to flash new rom (miktouch 0.7) again through that, said failed. then tried to install the current ROM CM9.1 just out of interest which it also 'failed'
then considered the cwm comment about version, so flashed cwm 5.5.0.4. thru Hasoon 2000's ALL in 1 kit I still had. I then tried to reflash the current CM9.1 again, and it went through.....At the same time it occurred to me about me having 'messed' with the script files of MikTouch 0.7 ...maybe being the cause, so luckily, I had an original copy of the rom zip (kept justin kase lol) and then tried this method.
I now don't know if it was the script file or the cwm version number but hallelujah it WORKED. I honestly thought I was stuck on cm9.1 forever, I've spent so much time reading/trying to flash anything else!
Can't thank you all enough, whatever it was, I think I have overcome it now! phew.
:cyclops: :victory:
I'm having issues flashing any rom. I'm on stock rooted, s-off lollipop 5.0.1 and any time I attempt to flash a ROM it gets aborted with a symlink error status 7 message. Any thoughts on what could be causing it? I've tried TWRP and CWM and neither of them work. Thanks
UPDATE: Disregard this thread. I switched back to TWRP and it went fine. No clue what the difference was. Thanks anyways