• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Open rom test

Leslie Ann

Android Expert
WARNING!!!!
If you don't know what to do, please do not ask, if you don't know what to do, you should not be considering this.

This very well may brick your phone.
The changes to the installer look right, but I cannot be sure until it is flashed.
Make sure you have a good backup because you may need it.

You do this to help the community, NOT get my rom first.

Trust me, be patient and you will get it, this is for testing only.
When we have it figured out, I will make sure you know.

If you brick, rant and moan, but don't say you were not warned. The community as a whole will do what they can to help you, but there is no way for me to tell you this is 100% safe or that there is even the slightest chance you can fix your phone if this does not work.






Some space to let that sink in.











Enough warnings

I need a couple things from you if you install it:
I need several things from you, and it starts with a clean system, so backup and format data, cache and dalvik. Do NOT do system, it should be done automatically, and I want to test that.

Obviously I need to know if it worked. How to test that, is look in system/app and see if there are still odex files. Normally almost every file has a matching odex, this only has one or two odex files. Second, see if the flashlight app is there and works and did any setup system start with the phone or did you have to go into system and manually setup an account?

Last, go into the play store and see if any apps update, if so, pull then out with a file manager from data/app. I need them for the rom.


Right now, this uses the updated apps from ZV5, however the boot image is ZV4. Since I can't get my phone to revert to stock or take the update, I could use someone to pull the updated boot.img. I have a guide somewhere but I can't find the dang thing. So if you know how, pull it and get me a copy please, it will make life easier for everyone.


Download
Goo.im Downloads - Downloading EXP_2.01b_Elite.zip Read below for latest link and info.
Md5-0330b7e45f0be2b54ebb2ac7af4e2145
As with all Harmonia, Gapps is not necessary.
 
Right now, this uses the updated apps from ZV5, however the boot image is ZV4. Since I can't get my phone to revert to stock or take the update, I could use someone to pull the updated boot.img. I have a guide somewhere but I can't find the dang thing. So if you know how, pull it and get me a copy please, it will make life easier for everyone.

Leslie,

There is a ZV5 stock boot.img inside a CWM-flashable zip in giantpune's kernel thread.

EDIT: Here it is - http://www.sendspace.com/file/rjfdsy
 
so i downloaded the rom and i tried to install it now its worst nothing flashed i get error in /sdcard/EXP_2.01b_Elite.zip
(status 6)
installation aborted
 
Latest test....
Goo.im Downloads - Downloading Harmonia_2.02b_Elite.zip
Yes, this is Harmonia, still highly volatile. If this fails I have another uploading now.





Currently for roms I have (Stock and Aeneas will be free to take and modify and re-release as your own):
All
ZV5 Kernel and updates
Deodexed
Busyboxed
SuperSU
Vmroms app (removable through apps)


Aeneas and Harmonia
Init.d
Boot animation support (possibly)


Harmonia
Bloat removed
Flashlight (Tesla LED, no ads, no tracking, removable through apps)
Wifi tether app(removable through apps)
Only English and Spanish
Virgin de-branded
 
Harmonia_2.02b_Elite.zip still gives status 6. Do you use windows? I know there's something weird with the script and windows newline characters, you have to convert it to UNIX. I don't remember fully what it was but if you do use windows do a quick google on it not to hard to find.
 
Harmonia_2.02b_Elite.zip still gives status 6. Do you use windows? I know there's something weird with the script and windows newline characters, you have to convert it to UNIX. I don't remember fully what it was but if you do use windows do a quick google on it not to hard to find.
Windows isn't an issue here.
 
I dont think that last '\n' is your syntax error though. One of your earlier test roms ends with a new line and that script was successfully parsed. look at line 148
 
I was looking at the wrong line. I can't even see it in gedit.

Regardless, I agree, I doubt that is the issue. I'm willing to bet it has to do with the boot.img install section.


Edit: new build going up, T-minus 5mins
 
line 148, you have an unclosed opening parentheses "assert(". it makes it to th e end of the file still waiting for you to close that up. when it get to line 189 and still doesn't see it, you get the error there.
 
Back
Top Bottom