Hi all,
I'm using TWP and running SpeedRom 7.8 and when I try to flash faux123 kernel v22 it keeps failing. The error is:
assert failed: write_raw_image("/tmp/newboot.img", "b
E:Error in /tmp/sideload/package.zip
(Status 7)
Any ideas?
Thanks
Use 4EXT recovery.
Dark Nightmare said:
Use 4EXT recovery.
Click to expand...
Click to collapse
I changed my recovery to 4EXT and booted into it, cleared both caches and it still wouldn't flash the kernel. Same error as before. It also seems that somewhere while trying to flash the kernel and it failing it took out my wifi, so it no longer works.
mestguy182 said:
I changed my recovery to 4EXT and booted into it, cleared both caches and it still wouldn't flash the kernel. Same error as before. It also seems that somewhere while trying to flash the kernel and it failing it took out my wifi, so it no longer works.
Click to expand...
Click to collapse
In 4EXT. Go though the settings and enable SmartFlash.
hasoon2000 said:
In 4EXT. Go though the settings and enable SmartFlash.
Click to expand...
Click to collapse
I tried that and it didn't work. I'm going to do a full wipe, reinstall speedrom and then install the kernel and see what happens.
***Update*** Doing a fresh install worked. Thanks for the help.
mestguy182 said:
I tried that and it didn't work. I'm going to do a full wipe, reinstall speedrom and then install the kernel and see what happens.
***Update*** Doing a fresh install worked. Thanks for the help.
Click to expand...
Click to collapse
As I noted in my last post doing a fresh install worked. Just throwing out there that I went back to the stock kernel because the battery life was horrible using Faux's
Related
I am trying to swich ROMs. I am currently on Jellybro and really want to try Helly Bean. Has anyone tried/had issues going from Jellybro to Helly Bean? I followed the flash instructions and I am getting a status 7 error. Any ideas how to fix? I've searched the Helly Bean thread in the development forum, but I'm too much of a n00b to figure out what they are saying most of the time. Do I need to start from scratch (Odin back to stock)?
If I have to Odin, I'll do some more searching to figure out how to get from stock to Helly Bean.
Thanks in Advance!
Check this out. Seemed to work with previous build.
I just tried the Glitch kernel fix and I am still getting the same status 7 error: symlinks failed. I got the same error last week, but I had assumed it was the updater.sh script as described by hurtz777.
It always fails on the vibrant install, the initial and the base work just fine. Do I need to reflash the glitch kernel after the base installation?
Any other ideas?
HellsBells said:
I just tried the Glitch kernel fix and I am still getting the same status 7 error: symlinks failed. I got the same error last week, but I had assumed it was the updater.sh script as described by hurtz777.
It always fails on the vibrant install, the initial and the base work just fine. Do I need to reflash the glitch kernel after the base installation?
Any other ideas?
Click to expand...
Click to collapse
Did you follow the steps directly.
1.flash base
2.reboot recovery.
3.flash helly bean initial
4.flash hellybean xxx(device name)
5. Flash add on.
6. Go into advanced. Fix permissions.
7. Reboot
Sent from my SGH-T959 using xda app-developers app
skinzy98 said:
Did you follow the steps directly.
1.flash base
2.reboot recovery.
3.flash helly bean initial
4.flash hellybean xxx(device name)
5. Flash add on.
6. Go into advanced. Fix permissions.
7. Reboot
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Yes, but it gives me the status 7 in step 4. I did a factory reset, wiped cache/dalvik, flashed glitch kernel, flashed initial, reboot recovery, flashed base, flashed vibrant rom, then i get the status 7 error about half-way through the install.
What about formatting system partition?
Sent from my SGH-T959 using xda premium
rcsredmage said:
What about formatting system partition?
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
I thought about starting over completely. Reformat everything and reflash stock with Odin and start with a blank phone. I don't want to loose any info but at this point I don't think I care anymore.
I have Titanium back up, but if I reformat, it will not reinstall my apps correct? If you can't tell, I'm new to the game here.
Reflash your kernel.. trust me
asvantypography said:
Reflash your kernel.. trust me
Click to expand...
Click to collapse
Still getting the error. I flashed the glitch kernel, flashed initial, reboot, flashed base, flashed glitch, flashed base again, then flashed vibrant rom and boom... status 7 error some symlinks failed.
WTF this is frustrating...
Reflash the kernel then flash the rom
asvantypography said:
Reflash the kernel then flash the rom
Click to expand...
Click to collapse
Same error. ugh...
Youre supposed to wipe data, wipe dalvik cache and cache, format system, and then install the initial package. After that, reboot recovery, then flash the base. After that, flash the file made for your device (hellybean vibrant 0807) and then flash the addon. After all that, reboot. I dont think you're supposed to get a status 7 error, because thats how the developer says to do it.
+1 ^^^^
sent from my magic box to yours
They have been getting a status seven on that thread. They said it was a sy link error. I can't remember how to fix it though
Sent from my SGH-T959 using xda app-developers app
Actually that was on some of the earlier builds such as 0804 and 0805 and perhaps 0806 as well. 0807, I can say that it is working. I just checked the thread, and another user reported that he was on 0807 and it runs fine. Just putting this out there for you all to know.
Hobbesfed said:
Youre supposed to wipe data, wipe dalvik cache and cache, format system, and then install the initial package. After that, reboot recovery, then flash the base. After that, flash the file made for your device (hellybean vibrant 0807) and then flash the addon. After all that, reboot. I dont think you're supposed to get a status 7 error, because thats how the developer says to do it.
Click to expand...
Click to collapse
That's what I did, but I can't get past the vibrant flash file. I get the status 7 error in the middle of the install (symlinks failed).
I didn't format the system partition. I can try doing that too. I won't lose my backups or apps (titanium backup) will I? I suppose i could back them up to the external SD and remove it.
I'll try that this evening. I'll let you know how it goes.
Thanks for everyone's input.
i googled the problem and i got here .. i had the same issue with captivate, rebooting after installing the base solved the issue for me .. don't forget to fix permissions after flashing the addons
bobo122 said:
i googled the problem and i got here .. i had the same issue with captivate, rebooting after installing the base solved the issue for me .. don't forget to fix permissions after flashing the addons
Click to expand...
Click to collapse
Same error.
I haven't gotten around to formatting the system partition yet. That will only affect the OS right, it won't delete any other data?
i fixed it with flashing stock kernel from odin..
Sent from my GT-P1000 using xda app-developers app
It Worked!
I finally got it! Formatting the system partition is what did it! Thanks for everyone's suggestions!
Now to play a bit...
I got my S3 a while ago and only recently decided to install a custom rom. I installed the CM10.1 nightly build and I've been happy with it and all, but upon seeing MIUI on my friend's phone I decided to flash MIUI. Now, when I tried flashing through recovery it hung for a min or so at "opening update package" and then gave me an error saying "E: Can't open /external_sd/miuiandroid_m0_jb-3.1.25.zip (bad) Installation aborted". I have tried re-downloading the rom and all, I've tried wiping cache/dalvik cache and even a factory reset and nothing's worked so far.
This happens no matter what rom I try to flash over CM. Has anyone had this happen and does anyone know how to fix it?
b0sanac said:
I got my S3 a while ago and only recently decided to install a custom rom. I installed the CM10.1 nightly build and I've been happy with it and all, but upon seeing MIUI on my friend's phone I decided to flash MIUI. Now, when I tried flashing through recovery it hung for a min or so at "opening update package" and then gave me an error saying "E: Can't open /external_sd/miuiandroid_m0_jb-3.1.25.zip (bad) Installation aborted". I have tried re-downloading the rom and all, I've tried wiping cache/dalvik cache and even a factory reset and nothing's worked so far.
This happens no matter what rom I try to flash over CM. Has anyone had this happen and does anyone know how to fix it?
Click to expand...
Click to collapse
Never happened to me. I can suggest a method that's not been tested, although theoretically there should be no problem implementing.
Although, have you tried flashing some AOSP mods? I'm getting a feeling something might be wrong with your recovery. If that is the case, try flashing siyah and hijack the recovery using stweaks. Then try installing roms again.
Are you installing from the internal or external sd? try the internal, and check the md5
Glebun said:
Are you installing from the internal or external sd? try the internal, and check the md5
Click to expand...
Click to collapse
Tried both internal and external, I get the same thing. I'm pretty sure that it's not corrupted since this is the same file that my friend used to flash his s3 to miui.
xcly said:
Never happened to me. I can suggest a method that's not been tested, although theoretically there should be no problem implementing.
Although, have you tried flashing some AOSP mods? I'm getting a feeling something might be wrong with your recovery. If that is the case, try flashing siyah and hijack the recovery using stweaks. Then try installing roms again.
Click to expand...
Click to collapse
I have not, will try it.
Edit: Flashed an AOSP rom and it worked fine, then MIUI, the install worked but now MIUI is just hanging on the boot screen.
Edit 2: Okay I got it working, I had to do a factory reset and it just started working.
Thanks for your help guys
Hi everyone,
Someone knows how to turn off my phone, everytime I use the Power off option the phone is rebooted. Also I tryed using a halt comnand but the phone was rebooted too.
What's wrong?
This happened to me using CM9 and now CM10 (nightly version and TNT)
Thanks.
ecallejas said:
Hi everyone,
Someone knows how to turn off my phone, everytime I use the Power off option the phone is rebooted. Also I tryed using a halt comnand but the phone was rebooted too.
What's wrong?
This happened to me using CM9 and now CM10 (nightly version and TNT)
Thanks.
Click to expand...
Click to collapse
Back-up your data, full wipe, reflash your rom, reflash gapps, restore data.
Christiaan91 said:
Back-up your data, full wipe, reflash your rom, reflash gapps, restore data.
Click to expand...
Click to collapse
No Christiaan91, it doesn't work, I reflashed the rom & apps. The problem continues. Thanks Anyway!
Try boot into CWM and power off it from recovery.
Or you can flash another kernel, maybe is a kernel issue.
_FreaK_ said:
Try boot into CWM and power off it from recovery.
Or you can flash another kernel, maybe is a kernel issue.
Click to expand...
Click to collapse
No, boot into CWM didn't work.
Also yesterday I installed AOKP with Android 4.2.2, and the problem persist.
Maybe this is a kernel issue, as you mentioned.
Thanks anyway
Hello.
I have only been able to install ViperX+ 1.08 ROM successfully. I wanted to experience other ROMs in comparison and have found ROMs specifically for this model, HTC One X Plus International, only to have them fail to fully install successfully. I have read up here on how to go about it and followed the steps dutifully but to no avail.
Does it make a difference on which Recovery you have installed for it to be successful or not? I currently have the latest TWRP 2.5.0.0 for my model. I have tried installing CyanogenMod and AOKP. CyanogenMod never makes it pass the installation because it fails right after attempting to install. AOKP installs but hang at the opening picture, and yes, I tried flashing the boot.img in Fastboot thinking that would solve it but it continued hanging anyway. Anyone have any help they can offer me? Thanks.
Jussi31 said:
Hello.
I have only been able to install ViperX+ 1.08 ROM successfully. I wanted to experience other ROMs in comparison and have found ROMs specifically for this model, HTC One X Plus International, only to have them fail to fully install successfully. I have read up here on how to go about it and followed the steps dutifully but to no avail.
Does it make a difference on which Recovery you have installed for it to be successful or not? I currently have the latest TWRP 2.5.0.0 for my model. I have tried installing CyanogenMod and AOKP. CyanogenMod never makes it pass the installation because it fails right after attempting to install. AOKP installs but hang at the opening picture, and yes, I tried flashing the boot.img in Fastboot thinking that would solve it but it continued hanging anyway. Anyone have any help they can offer me? Thanks.
Click to expand...
Click to collapse
The aokp uses the 4.2 kernal so you will have to instal that. But I'm not sure on the recovery .. maybe it might be worth trying clockwork as if the twrp you are useing is especially for the viper Rom? Have a go at installing the different recovery maybe that will help and double check what you have to do to install on the thread hope this helps
Ilike the viper Rom... But if I get time tomorrow I will try for myself ... If no one else helps you out by the time I do it I will update you on how I done it and any problems I faced maybe I will end up in the same situation.
Sent from my HTC One X+ using xda premium
Appreciate it. Insofar as the Recovery is concerned, the initial Recovery that I installed from the All-In-One kit when installing ViperX+ is different from the one I have now. Unless it is just a newer version, I now have Venom TWRP 2.5.0.0., just FTR. Thanks again, I will be interested to hear what happens for you.
Jussi31 said:
Appreciate it. Insofar as the Recovery is concerned, the initial Recovery that I installed from the All-In-One kit when installing ViperX+ is different from the one I have now. Unless it is just a newer version, I now have Venom TWRP 2.5.0.0., just FTR. Thanks again, I will be interested to hear what happens for you.
Click to expand...
Click to collapse
TWRP is the ideal solution for our HOX+ - at least as of now.
I hope you are doing the following:
1. Wiping Data & System.
2. Installing boot.img.
The Venom customized TWRP does not have any issues because I also used it for some time (as of now I am back on the official TWRP).
You can download the lastes verison from here:
http://techerrata.com/browse/twrp2/enrc2b
And install it using Hox+ All in one toolkit by hasoon.
Make sure you wipe data & system before you install the ROM.
I also changed from ViperX 1.08 to ARHD, InsertCoin & Elegancia.. no issues
Hmmm. I'll have to putz around with it some more and see what happens. Thanks.
Here's a brief summary of what I attempted to do.
I wiped Delvik Cache; I wiped Cache; I did Factory Reset; I wiped System.
Next I tried installing CyanogenMod and received the following error messages:
assert failed: getprop
E: error executing updater binary in zip
Error flashing zip
So I wiped everything again and tried installing AOKP. It successfully installs. I try rebooting prior to flashing boot.img. It hangs on horse picture opening screen. So I flash the boot.img in Fastboot and reboot after erasing cache. When rebooting it hangs on opening white screen.
I'm baffled. What am I doing wrong?
Jussi31 said:
Here's a brief summary of what I attempted to do.
I wiped Delvik Cache; I wiped Cache; I did Factory Reset; I wiped System.
Next I tried installing CyanogenMod and received the following error messages:
assert failed: getprop
E: error executing updater binary in zip
Error flashing zip
So I wiped everything again and tried installing AOKP. It successfully installs. I try rebooting prior to flashing boot.img. It hangs on horse picture opening screen. So I flash the boot.img in Fastboot and reboot after erasing cache. When rebooting it hangs on opening white screen.
I'm baffled. What am I doing wrong?
Click to expand...
Click to collapse
I guess your recovery is not able to detect that your phone is one x+.. that's why assert failed error.. try changing the recovery( maybe CWM) and try again
Through trial-and-error, and reading hard, I figured out I had to install a compatible Kernel. I then was able to install, successfully, AOKP and it seems to work very smoothly. I'm just learning the ins-and-outs of everything. Thanks for your help.
Jussi31 said:
Through trial-and-error, and reading hard, I figured out I had to install a compatible Kernel. I then was able to install, successfully, AOKP and it seems to work very smoothly. I'm just learning the ins-and-outs of everything. Thanks for your help.
Click to expand...
Click to collapse
:good::good::good:
that is cool!
I recently changed from pauls recovery to twrp and tried to wipe and flash new rom however now im stuck. twrp seems to have wiped some stuff but not all and the rom just boot loops. any help is welcome asap.
I get this message. E:error opening '/data/data/com.google.android.g and E:error: I/O error
patrickliebl said:
I recently changed from pauls recovery to twrp and tried to wipe and flash new rom however now im stuck. twrp seems to have wiped some stuff but not all and the rom just boot loops. any help is welcome asap.
I get this message. E:error opening '/data/data/com.google.android.g and E:error: I/O error
Click to expand...
Click to collapse
I was having problems with TWRP recently (and periodically in the past). It would give errors and not flash/wipe/etc. I switched to the latest CWM and it's been working great so far. Just a thought it you cannot find a solution. I couldn't.
Good luck.
I got this from trying to use TB, and it corrupted a file. I switched recoveries a couple of time wiping internal, and data, switched back to twrp, and been solid ever since. It is the way TB messes up. I don't blame twrp for my mistake. Even posted in nebula about it.
Sent from my SCH-I605 using Tapatalk