I have used UOT before on stock/rooted/bootstrap with success every time. Now that I'm finally unlocked on Joker/skinny with jokers CWM V3 I get installation aborted errors every time. I turned off CM theme previews and I've tried both edify and amend scripting. Any suggestions?
Sent from my MB855 using xda premium
fendergrab said:
I have used UOT before on stock/rooted/bootstrap with success every time. Now that I'm finally unlocked on Joker/skinny with jokers CWM V3 I get installation aborted errors every time. I turned off CM theme previews and I've tried both edify and amend scripting. Any suggestions?
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
I assume you are using your framework from the current rom and not the stock one from before.
What error do you get? Have you imported the update-binary file from your current rom to the one UOT produced?
Use bootstrap to install UOT themes, they will fail with clockwork mod. You can have both bootstrap and cwm installed at the same time. And use amend scripting and turn off theme previews.
Sent from my MB855 using Tapatalk 2
Lancerz said:
Use bootstrap to install UOT themes, they will fail with clockwork mod. You can have both bootstrap and cwm installed at the same time. And use amend scripting and turn off theme previews.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
I have used CWM to install UOT package without any problems on stock rom. Had to lightly modify the package though.
Im using the framework.res and systemui for my current setup, so I know its not that. CWM says "can't open sd card/UOT 10283... installation aborted". I also unzipped the theme and inserted the update.binary from joker/skinny and then rezipped it. I did it using win.rar, so I may have done it wrong. Im not getting the status 0 error at all though.
Sent from my MB855 using xda premium
It takes 2 seconds to install bootstrap recovery and you won't have any problems flashing UOT themes.
Sent from my MB855 using Tapatalk 2
Related
I've been on MIUI 1.6.24.1 and it's been working great. I tried upgrading to 1.7.1 and every time i try to flash I get installation aborted. I've downloaded it multiple times and I'm using CWM 3.x red recovery. Has anyone else had this problem or have any suggestions?
I think you have to use the yellow recovery. Not sure, though.
Sent from my SCH-I500 using XDA App
So how would I go about getting yellow on my phone? I can't seem to find a download.
You should already have it, open up terminal emulator and type su then type reboot recovery and that should get you to the yellow recovery.
Sent from my I500 using XDA App
I just tried that. It booted me into orange and when I tried to flash I got the same status 7 installation aborted.
Look at the first post in the cm7 waiting room thread in the general section, they talk about what to do to fix that.
Sent from my I500 using XDA App
OK will do. Thanks for your help.
Sent from my SCH-I500 using XDA App
I rooted my 3vo and ive tried flashing several roms but twrp says signature verification failed and wont let me flash any roms at all. Any ideas?
Sent from my PG86100 using XDA App
Uncheck signature verification
I tried that that i come up with a side load error. This isnt my first time rooting an android device. This is just confusing as hell
Sent from my PG86100 using XDA App
darkkarny717 said:
I tried that that i come up with a side load error. This isnt my first time rooting an android device. This is just confusing as hell
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
from the other posts i've seen, the sideload error is given when the ROM is using an older depreciated scripting language called amend (update-script). the ROM needs to use the newer scripting language called edify (updater-script).
i personally haven't experienced this but i also havent tried loading any older amend coded ROMs.
you can view which scripting language the ROM .zip file you're using has by viewing which file is located in META-INF/com/google/android/ . if the file is update-script, its the older depreciated amend language. if the file is updater-script, it is the newer edify language.
hopefully that is the correct solution and works for you!
edit: did a bit more research and saw a thread semi dedicated to this issue:
http://forum.xda-developers.com/showthread.php?t=1194245
seems it occurs not only from using the older depreciated scripting language amend, but using the newer edify scripting language, the update-binary file needs to be using api v3, which is the latest.
sorry the error in the recovery isn't more straight forward and helpful. hopefully this makes sense. essentially the developer needs to use the latest version of edify scripting in their ROM.
So would switching to another custom recovery work out this issue. Ive seen a lot of buzz that twrp is still kind of buggy. I love the way they have it srt up but i rooted to flash roms and if its the recovery preventing that ill switch.
Sent from my PG86100 using XDA App
i have been using twrp since release with very little issues...it is a very nice recovery.
are you downloading the roms from your phone or pc? i have had unsuccessful flashes when downloading rom from the phone.
i have flashed all synergy roms, virus, avalaunch and a few others with twrp with no problems.
let us know what you find.
Switched recovery and still nothing. This sucks i wanna flash the viper rom but this damn **** wont work. Anyone else have success in flashin viper rc1.3
Sent from my PG86100 using XDA App
Finally got it just went thru rom manager and flashed cwm
Sent from my PG86100 using XDA App
I want to flash ICS to my phone but i cant boot into recovery. I Odin'd The froyo EBO1 and havent done changes after that. its on 2.2.1 and kernel 2.6.32.9. i continue to get blue screen recovery and the error triangle when i try to apply Zip or boot into recovery from ROM Manager. the clockwork is version 3.0.0.8 i believe. is there any conflict with that version & 2.2? if so what is my solution to get into clockwork and flash it
This is my error message,
E: failed to verify whole-file signature
E: signature verification failed
Installation Aborted
Help is greatly appreciated. thanks
Rom Manager v4.8.06*
Sent from my SCH-I500 using XDA App
xdapadogx said:
I want to flash ICS to my phone but i cant boot into recovery. I Odin'd The froyo EBO1 and havent done changes after that. its on 2.2.1 and kernel 2.6.32.9. i continue to get blue screen recovery and the error triangle when i try to apply Zip or boot into recovery from ROM Manager. the clockwork is version 3.0.0.8 i believe. is there any conflict with that version & 2.2? if so what is my solution to get into clockwork and flash it
This is my error message,
E: failed to verify whole-file signature
E: signature verification failed
Installation Aborted
Help is greatly appreciated. thanks
Click to expand...
Click to collapse
Go to the general section and find Droidstyle's guide. It will give you exact steps on what you need to do.
Sent from my SCH-I500 using XDA App
Search the general forum?
Sent from my SCH-I500 using XDA App
Yeah I can't link on the app. But its in general section. Its 6 parts. ICS has its on section if im not mistaken.
Sent from my SCH-I500 using XDA App
Yeah I'm on my phone also. Thanks man ill check when I log onto the comp tomorrow. Give thanks when I log on too
Sent from my SCH-I500 using XDA App
Here is that link for you...
http://forum.xda-developers.com/showthread.php?t=1238070
The simple answer is you need to replace your stock recovery with a modified 2e or 3e recovery that clockworkmod is compatible with.
Since you are on 2.1, I believe you will need the 2e, but it may be easier for you to Odin to froyo and use a 3e recovery instead.
heres a video on how to do it.
Just search around for the modded recovery. Any should do.
Thats not correct...you need cwm4 for mtd to flash ics.
Yeah i used your guide in the generals, Droidstyle. worked like a charm. makes me feel dumb that i had such a hard time
What droidstyle said. Odin cwm4 and enter it with three finger method immediately after you re-insert in your battery and flash away. ICS is very functional especially for alpha build and quite stunning visually.
Sent from my SCH-I500 using xda premium
Yeah it its I'm surprised at how smooth it is. I know mms doesn't work outgoing, but I can receive. That's normal right
Sent from my SCH-I500 using XDA App
I want to install cynogenmod but when i try to install the zip mod files in recovery mode i got this error
error in sdcard/update.zip (Status 0)
pls help
You need to read the rules and make a search. I know search results may not make sense but the answer is out here.
Most likely it is somthing wrong with the file. Or try custom file in recovery. Depending on version.
what is ur recovery version ?
what is the rom ?
I started with 0.8 i think and roms, alot difrent ones latest cm7pro v20. GingerDX are nice to.
You must notice that there is a difference betwen x10 mini and pro it differs alot
Sent from my U20i using XDA App
Beside that don't say the mount error?
Also try without rename the rom to update.zip.
Sent from my U20i using Tapatalk
using mimmi
nosoyted said:
Beside that don't say the mount error?
Also try without rename the rom to update.zip.
Sent from my U20i using Tapatalk
Click to expand...
Click to collapse
I have same problem with a friend's phone it says mount error with cwm using nAa kernel 11. What could it be?
Sent from my U20i using xda premium
Don't use the update feature, use install zip or custom rom, don't remember exactly right now. The update.zip didn't work for me so i haven't used it after that.
Sent from my U20i using XDA App
Do this:
1. Re/Boot to recovery of course.
2. Intall zip from sdcard
3. Choose zip from sdcard
4. Choose the name of the zip file for your rom
5. Wait
6. Reboot
7. Wait again because it takes time.
8. See if it works.
This steps will only work work if your phone is rooted (of course it is because you have recovery), unlocked bootloader (if the rom requires it), flashed the correct kernel (again if the rom requires it)
demoniacs said:
Do this:
1. Re/Boot to recovery of course.
2. Intall zip from sdcard
3. Choose zip from sdcard
4. Choose the name of the zip file for your rom
5. Wait
6. Reboot
7. Wait again because it takes time.
8. See if it works.
This steps will only work work if your phone is rooted (of course it is because you have recovery), unlocked bootloader (if the rom requires it), flashed the correct kernel (again if the rom requires it)
Click to expand...
Click to collapse
I have tried this method with xrecovery aswell and still the problem persists, although the version is old it still should have worked. Any other ideas?
Sent from my U20i using xda premium
mibuwolf said:
I have tried this method with xrecovery aswell and still the problem persists, although the version is old it still should have worked. Any other ideas?
Sent from my U20i using xda premium
Click to expand...
Click to collapse
Any solutions?
Sent from my U20i using xda premium
download the zip again
demoniacs said:
download the zip again
Click to expand...
Click to collapse
I did state that everything works on my phone perfectly so its clearly not the zips.
Sent from my U20i using xda premium
It could be a missmatch of cwm/xrecovery versions. An old cwm/xrecovery cannot install a 'new' cwm/xrecovery zip, neither can you really use a zip designed for cwm on xrecovery.
As said before, zips can also be corrupt for various reasons. They are big files and servers can stutter information or cause a few false bits here and there. Redownloading them can test that theory.
Sent from my U20i using Tapatalk
obsidian_eclipse said:
It could be a missmatch of cwm/xrecovery versions. An old cwm/xrecovery cannot install a 'new' cwm/xrecovery zip, neither can you really use a zip designed for cwm on xrecovery.
As said before, zips can also be corrupt for various reasons. They are big files and servers can stutter information or cause a few false bits here and there. Redownloading them can test that theory.
Sent from my U20i using Tapatalk
Click to expand...
Click to collapse
tried with old xrecovery + old rom minicm6 and stil nothing same problem.
Sent from my U20i using xda premium
mibuwolf said:
tried with old xrecovery + old rom minicm6 and stil nothing same problem.
Sent from my U20i using xda premium
Click to expand...
Click to collapse
Always says installation aborted.
Sent from my U20i using xda premium
Can no1 give me a right answer as to why xrecovery and cwm give me error 'recovery seems bad' installation aborted.
Sent from my U20i using xda premium
Hi Everyone,
I just rooted my friend's Note and I'm attempting to flash the latest CM10 nightly. I'm using the CWM-based Touch Recovery v5.5.0.4. Every attempt to flash CM10 has lead to the (status 7) error, in which the assert has failed. I've attempted to remove the assert from the script and the installation is simply aborted in CWM. (I feel like doing this is more of a work-around then a fix though, since I'd potentially have to do it every time I flash a new CM rom). Just wondering if this has happened to anyone else and if there is a fix out there. I've done a good amount of searching and haven't found anything.
Thanks in advance.
Update.
Sounds like an outdated recovery to me
Sent from my SAMSUNG-SGH-I717 using xda premium
Installed ROM manager. Update recovery, retry
Sent from my SAMSUNG-SGH-I717 using xda premium
Thanks everyone. I actually tried using ROMManager and it wasn't flashing the update for me. Key part I didn't explain :-/ Anyhow, I found the newest CWM and flashed the .img through terminal. Problem solved.
Thanks!
I had problems with this too I had to download the twrp kernel and then it worked fine.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
TWRP is the ****....
I hate CWM NOW !...g
I'm ok with CWR but the rom manager app causes a few problems.
rangercaptain said:
I'm ok with CWR but the rom manager app causes a few problems.
Click to expand...
Click to collapse
Last year over in the inspire threads,, we affectionately began to call it rom "mangler"..
Koush did okay, but the turning point for me, was buying the touch version, then trying to get the app to flash the recovery back to the device.
It shows the I717 as unsupported, yet the CWM website has it.
But every time I try to download it ...I get garbled jibberish..
Hence TWRP ...version 2.3.2.3...and it's flawless
I think koush likes the money..
He has never replied to one pm or email I've sent ....g
Have to agree that twrp is the awesome choice. I've had cwm fail more than once to restore for me. Twrp is faster and drains the battery less. And as a shameless self promotion .. My American twrp theme is so sexy .. You'll want to go into recovery everyday.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Bubbajoe40356 said:
Have to agree that twrp is the awesome choice. I've had cwm fail more than once to restore for me. Twrp is faster and drains the battery less. And as a shameless self promotion .. My American twrp theme is so sexy .. You'll want to go into recovery everyday.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
I do already ...LOL