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

Root [Boost Mobile] [ROM] Update.Zip

Snake X said:
so wait, what makes it an actual rom vs nandroid/update.zip? I don't quite understand the packaging of roms completely

edit:

It supports galaxy SII skyrocket only?
Click to expand...
Its deodexed for starters.
and if you edit the files inside the zip (ei exchanging /system/app/launcher.apk with say .../zeam.apk) you can change/add/remove apps as you like.
 
Lordvincent 90 said:
this is step one,
next de-odexing (for themeability)
then enable init.d support(?) -this is for scriptability
and maybe port over the power/notification widgets?

i would love to see a CTMod-like variant of the stock rom on this phone :D

baby steps ;)
Click to expand...


i THINK i enable that in the kitchen....talking about init.d support.

Having problems with the apk multi-tool so i can edit it to have crt animations? Maybe you can help solve it for me? Problem is its keeps telling me i dont have java..but i KNOW i do? i path where i have java installed still gives me that problem???
 
903Tex said:
Yea i posted it lol! Did it work for what you were trying to do?

And somebody can you test the rom? Its deodex
Click to expand...
Ohh so its already deodexed. So long as it works I guess I'll be doing something else then. thanks.

Somebody please try it out. thanks.
 
Rally 517 said:
I'm still learning all this is new. I'm usually the Ginny pig. Lol
Click to expand...


lol! I would try it dont have phone anymore! Tried to buy another one today, but they are sold out EVERYWHERE!!! Found one radioshack that had it got to get up early in morning to go get it! If nobody tried it by tonight in the morning ill know lol!
 
While installing the update I get " assert failed: write_raw_image("/tmp/boot.img"

E:Error in /sdcard/arthur_signed.zip
(status 7)
Installation aborted.
 
Stlouizsin said:
While installing the update I get " assert failed: write_raw_image("/tmp/boot.img"

E:Error in /sdcard/arthur_signed.zip
(status 7)
Installation aborted.
Click to expand...


Guess it needs to be a update not a updater script? ill have a new file in a minute up! You do have a backup made right?
 
I'd make a rom of my device but I'd be highly illegal :D (swype, lp sense ui mod, paid apps, etc cant be distributed)

oh not to mention the personal info thats stored on it
 
i got this

assert failed:write-raw-image("/tmp/boot.img",
e:error in /sdcard/arthur-signed.zip
(status 7)
installation aborted


sorry i didnt see the other post
 
903Tex said:
i THINK i enable that in the kitchen....talking about init.d support.

Having problems with the apk multi-tool so i can edit it to have crt animations? Maybe you can help solve it for me? Problem is its keeps telling me i dont have java..but i KNOW i do? i path where i have java installed still gives me that problem???
Click to expand...

Do you have this:
Java SE Downloads
 
How did you deodex email.apk? It failed for me, so I tossed it and replaced it with an email.apk from another rom. Haven't tested it yet...
 
I tried converting the updater-script to update-script using the rom kitchen. Unfortunately it didn't work. Update-scripts are no longer supported in CWM. But I guess you know that and are working on a solution. Anyways, once you do, can you provide your corrected script as a separate download? Show mercy on my slow interwebz.

Doesn't it have to be fully deodexed or fully odexed? At least that's what I got out of the kitchen when I deodexed my files. If email.apk is really necessary, maybe it doesn't have to be that email.apk ;)
 
Can anybody flash the zip and do the following below?


Another thing to do is to grab the "recovery.log" file immediately after you flash the bad ROM (BEFORE the first reboot!!). This shows a log of the activity during the current recovery menu session (i.e. during the flash). This log may also show errors that were not caught when you were flashing the ROM
  1. you can usually find it under /tmp/recovery.log or /cache/recovery.log or /cache/recovery/last_log with ADB. Try to copy it to a location where you can view it. e.g. Type from your computer: "adb shell", followed by "cat /tmp/recovery.log > /sdcard/recovery.log". Alternatively, from your computer you can do: "adb pull /tmp/recovery.log", which will copy it to your computer.
  2. Open up recovery.log with a text editor, but don't use Notepad, because it will put everything on one line instead of multiple lines.
  3. Check recovery.log for any errors that occurred during the flashing process.
Remember, you must grab the recovery log output immediately after flashing and before you reboot. If you had rebooted afterwards, then the flashing's log information would have been cleared and you will need to flash again to get the log output.
 
Try it without the recovery img in the zip and with lines referencing it removed from updater
 
Lordvincent 90 said:
http://androidforums.com/triumph-all-things-root/452974-help-status-7-cwm-recovery.html

Not for this phone, but says bootimg is going to wrong location when the above message isdisplayed
Click to expand...


Yea i think i found the fix! I work on it first thing in the morning. Going to go buy device in the morning

So when you see the download link then you will know that it works 100%

SORRY EVERYBODY FOR THE WAIT! never had this problem with other roms i made with kitchen?!?!
 
.
mavrikmeercat said:
The updater-script and update-binary is what takes all the know-how.

Thanks to some info from Davegrow, depending on what generates your update-binary (Updatezip Creator, UOTK, Android Kitchen) may all have different versions of the EDIFY binary and that directly affects what syntax you can use for your mount points to /system, /data, /cache, /sd-ext, and such.

So, say you want to format /system before installing a ROM. The base language for the Transform Ultra would be:



But might not be the way it is for your binary. it may be a variation of those arguments.

arguments are the things inside ( ).
ext4= type of file system for the TU
EMMC= Type of Partition for the TU
dev/block/mmcblk0p15= mount point for /system in the TU
/system=name of the partition

Some binaries only call for two arguments to format like this:

Or


And some might call for three like this:

Or


Also from what I gather, if your binary calls for say two arguments then the mount command calls for three.. (always one more for mount) but I could be wrong on this. not much to go on. Bits and pieces of info only

(More info required from the community)
Click to expand...
 
You must log in or register to reply here.
Back
Top Bottom